E-Mail Scheduler Configuration Settings That Affect Agents

20 Configuring Advanced Options for Mapping and Spatial Information 20-1 20 Configuring Advanced Options for Mapping and Spatial Information This chapter describes advanced configuration options that you can set for map views. It includes the following topics: ■ Section 20.1, Configuring MapViewer to Support Map Views ■ Section 20.2, Manually Configuring for Map Views ■ Section 20.3, Inserting Text on a Map ■ Section 20.4, Configuring Maps for External Consumption See Chapter 13, Configuring Mapping and Spatial Information for additional information. Before configuring for map views, ensure that you are familiar with the information in the following guides: ■ Oracle Fusion Middleware Users Guide for Oracle MapViewer, which is part of the Oracle Fusion Middleware documentation library. ■ Oracle Spatial Developers Guide, which is part of the documentation library for Oracle Database.

20.1 Configuring MapViewer to Support Map Views

MapViewer is installed as part of Oracle BI Enterprise Edition and deployed in the same domain as Oracle BI EE on the web application server. The default context path of MapViewer in the application server is mapviewer. You can use the administration console in MapViewer to configure it for use with map views. You can configure a separate remote instance just for MapViewer to act as a proxy that supports the heavy processing load that maps require. If performance is not a major concern, then you can use a MapViewer instance that is co-located with Oracle BI EE as the rendering engine. The MapViewer engine can serve in the following roles: ■ Co-located MapViewer — Also known as nonproxy mode. If the MapViewer is located in the same domain as Oracle BI EE and used as the rendering engine, then all map resources such as JavaScript files and images are downloaded from that instance of MapViewer. ■ Remote MapViewer — Also known as proxy mode. If a separate remote instance of MapViewer is configured as the rendering engine, then the browser cannot communicate with the remote instance for resources. Browsers do not allow cross-domain AJAX calls for security reasons. To overcome this limitation, all 20-2 System Administrators Guide for Oracle Business Intelligence Enterprise Edition requests are first forwarded to the co-located MapViewer, which in turn communicates with the actual remote instance. Complete the following steps to configure for a remote MapViewer: – Edit the RemoteOracleMapViewerAbsoluteURL element in the instanceconfig.xml file, as described in Section 20.2, Manually Configuring for Map Views. – Edit the proxy_enabled_hosts element in the mapViewerConfig.xml configuration file for MapViewer to point to the MapViewer on the remote server, as shown in the following example: security_config proxy_enabled_hostshttp:remoteserver:9704mapviewerproxy_enabled_ hosts security_config Figure 20–1 shows the preferred architecture for map views, which provides better performance through a proxy than the default architecture that is shown in Figure 13–1 . You can store the data either in an Oracle Database or in other databases that Oracle BI EE supports. Figure 20–1 Preferred Architecture for Map Views

20.2 Manually Configuring for Map Views

Use various elements in the instanceconfig.xml file to configure map views. Before you begin this procedure, ensure that you are familiar with the information in Section 3.4, Using a Text Editor to Update Configuration Settings.