1. Working with Oracle Smart View for Office
  2. Data Source Connections
  3. Managing Connection URL Mappings
  4. About Managing Connection URL Mappings

About Managing Connection URL Mappings

Connection URL mappings allow you to migrate from one environment to another environment. Administrators configure mappings that replace old connection URLs with new URLs. The mappings can be managed from the Private Connections drop-down menu by selecting the Manage URL Mappings option.

After mapping, private and named connections are immediately migrated to the new URLs when Microsoft Excel is reopened. The new mappings persist even if a mapping is deleted. Any saved workbooks with functions using these private connections will continue to use the new URLs.

Working with Saved Workbooks Containing Ad Hoc Grids

  • You configure the remapping of a URL only once, and then restart Microsoft Excel. Any workbook you open that used the old URL will automatically start using the new URL. The application and cube name and the outline must remain the same for refresh and other operations to complete successfully.

    To summarize, once a mapping is created, then restart Excel, open a workbook, refresh, and then save the workbook. Thereafter, the workbook will always use the new URL. Subsequently, anytime you open a workbook that uses the new mapping, be sure to perform a refresh and save on that workbook.

  • As a best practice, in ad hoc sheets in saved workbooks, you must perform a refresh and save the workbook for the new URL to persist. After the refresh and save, the mapping can be deleted, for both named and unnamed connections, and the new URL will continue to be used.
  • If you are planning to delete the mapping but still want unnamed connections in a saved sheet to use a new URL, then you must activate each sheet and refresh it before saving the workbook. As a best practice, Oracle recommends using the Refresh All Worksheets command and then saving the workbook.
  • If a mapping is deleted before the sheets were refreshed and saved, then the old URL will be used.
  • If a mapping is deleted after the sheets were refreshed and saved, then the new URL will continue to be used.

Limitations

  • Oracle Business Intelligence Enterprise Edition and Oracle Analytics Cloud are not supported.
  • Oracle Hyperion Financial Management: Mappings will work only if the cluster name and application are same in the new and old environment.
  • Oracle Essbase on-premises and Essbase cloud: Sheets created in the cloud environment do not work in the on-premises environment. Alternatively, sheets created in the on-premises environment do not work in the cloud environment.
  • Nested URL mapping is not supported.
  • Ensure that you enter the correct URL. URL entries are not validated, so it is possible to enter an incorrect URL entry.