This chapter includes the following sections:
Oracle Fusion Middleware 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 must use the administration console in MapViewer to configure it for use with map views. See Configuring MapViewer .
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 permit cross-domain AJAX calls for security reasons. To overcome this limitation, all 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 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_hosts>http://remoteserver:9704/mapviewer</proxy_enabled_hosts> </security_config>
The mapViewerConfig.xml file is located in the following directory:
ORACLE_BI1\bifoundation\jee\mapviewer.ear\web.war\WEB_INF\conf
Note:
If you edit the mapViewerConfig.xml file, then your edits are overwritten when you upgrade or patch Oracle Business Intelligence. Before upgrading or patching, ensure that you make a backup copy of the mapViewerConfig.xml file. When the upgrade or patch operation is complete, copy the backed-up file to its original location. After copying the file, restart the server for MapViewer so that map views are displayed properly in analyses and dashboards in Oracle Business Intelligence.
The figure below shows the preferred architecture for map views, which provides better performance through a proxy than the default architecture that is shown in the table below. You can store the data either in an Oracle Database or in other databases that Oracle BI EE supports.
Use various elements in the instanceconfig.xml file to configure map views.
You can add any text, such as a copyright string, to the tile layer definition of a map.
The text is automatically updated on the map in Oracle BI EE when a tile layer is added or deleted or becomes invisible. The position of the text is also automatically adjusted when the user minimizes, restores, or removes the overview map.
The figure below shows an example of a copyright string on a map. The string is in the lower-right corner.
You can embed map views in external pages, such as those from Oracle WebCenter Portal, after setting the appropriate configuration options.
To embed views that are hosted in a separate web application server, you can follow the proxy rules that are outlined in the previous sections. Because of browser restrictions, install the MapViewer instance in the same application server as external pages or portals. The proxy context path of the MapViewer instance that is installed in the web application server that hosts external pages can differ from the application server that is hosting content for Oracle BI EE. In this case, set the SyndicatedOracleMapViewerContextPath element. When the server for Oracle BI Presentation Services identifies a request that originated from a third-party page, the server checks the element value to determine where to pass the proxy requests.
The following example provides sample values for this element.
<ServerInstance> <SpatialMaps> <SyndicatedOracleMapViewerContextPath>/mapviewer</SyndicatedOracleMapViewerContextPath> <RemoteOracleMapViewerAbsoluteURL>http://myserver:9704/mapviewer</RemoteOracleMapViewerAbsoluteURL> </SpatialMaps> </ServerInstance>