Agent Scheduler Configuration Settings

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. Configuring Advanced Options for Mapping and Spatial Information 20-3 To manually edit the settings for configuring map views: 1. Open the instanceconfig.xml file for editing, as described in Section 3.6, Where Are Configuration Files Located? 2. Search for the SpatialMaps section, in which you must add the following elements: ■ ColocatedOracleMapViewerContextPath — Specifies the context path of the MapViewer instance that is co-located with Oracle BI EE. The default value is mapviewer. ■ RemoteOracleMapViewerAbsoluteURL — Specifies the URL of the remote MapViewer instance. This element has no default value. If this element has no value, then the system assumes that the map rendering engine is the co-located MapViewer instance such as mapviewer. If this element has a value, then the co-located MapViewer acts as proxy for all requests for the remote server. The following example shows a sample value: RemoteOracleMapViewerAbsoluteURLhttp:remoteserver:9704mapviewer RemoteOracleMapViewerAbsoluteURL ■ MaxRecords — Specifies the maximum number of records that can be included in a layer on the map. The setting applies to all layers on the map and overrides the MaxVisibleRows element that applies to data cubes. The default value is 500. If the format for a layer causes this value to be exceeded, then a warning message is displayed. The parent element is LayerDataLayout. ■ MaxColumns — Specifies the maximum number of slices and bars generated for pie and bar graphs on the map. The setting applies to all layers on the map and overrides the MaxVisibleColumns element that applies to data cubes. The default value is 300. If the format for a layer causes this value to be exceeded, then an error message is displayed instead of the map. The parent element is LayerDataLayout. ■ SyndicatedOracleMapViewerContextPath — Specifies the URL of the MapViewer instance for embedding maps in external pages. For details and an example, see Section 20.4, Configuring Maps for External Consumption. 3. Include the elements and their ancestor elements as appropriate, as shown in the following example. ServerInstance SpatialMaps ColocatedOracleMapViewerContextPathmapviewerColocatedOracleMapViewer ContextPath RemoteOracleMapViewerAbsoluteURLRemoteOracleMapViewerAbsoluteURL LayerDataLayout MaxRecords600MaxRecords MaxColumns400MaxColumns LayerDataLayout SpatialMaps ServerInstance 4. Save your changes and close the file. 5. Restart Oracle Business Intelligence.