This is an archive related to a previous version of Esri Maps for IBM Cognos. If you need the current version go to http://doc.arcgis.com/en/maps-for-cognos/.
Esri Maps for IBM Cognos architecture
Esri Maps for IBM Cognos is web-based software that integrates maps and data into IBM Cognos Business Intelligence (BI) reports. Architecturally, Esri Maps for IBM Cognos offers the following benefits:
- Parallels the IBM Cognos architecture
- Ready for the enterprise
- Leverages existing systems (that is, no need for additional hardware)
The end result is that Esri Maps for IBM Cognos integrates directly with the IBM Cognos BI architecture. It leverages in-place security, deployment capabilities, scalability, and content promotion.
Esri Maps for IBM Cognos contains a gateway component (EM4C Gateway), a dispatcher component (EM4C Dispatcher), and has its own content server (EM4C Server).
EM4C Gateway
EM4C Gateway exists in the web tier and is installed on all IBM Cognos Gateway servers. In an IBM Cognos deployment, there will be one EM4C Gateway for each IBM Cognos Gateway.
The EM4C Gateway component is used to serve up static files such as images, cascading style sheets (CSS), and JavaScript resources. In addition to serving static files, this component also appends items to the IBM Cognos Report Studio toolbox.
EM4C Dispatcher
The EM4C Dispatcher component acts as a plug-in to the IBM Cognos Report Service. This is used to bridge the communication between the BI Bus and other EM4C components.
At runtime, the EM4C Dispatcher sends prompt values and context information to the EM4C Server. This ensures both proper security and proper use of any selected user prompts.
EM4C Server
EM4C Server is also responsible for handling the synchronization of IBM Cognos report elements at runtime by sending requests to the Cognos Dispatchers and processing the results. It is also responsible for the administration and configuration of Esri Maps for IBM Cognos content. This is done through the Esri Maps Designer interface, which is accessed from IBM Cognos Connection.
EM4C Server can be installed on any server as long as it meets the minimum requirements for a computer in an IBM Cognos deployment. No IBM Cognos components need to be installed. EM4C Server is a lightweight component, however, and is often installed on one or more computers in the application tier of an IBM Cognos deployment for failover.
If your deployment includes more than one EM4C Server, one is configured as the proxy (or primary) server and is responsible for load balancing between other EM4C Servers. This proxy maintains an affinity cache that directs subsequent requests to the appropriate EM4C Server.
Example Esri Maps for IBM Cognos deployment
The following illustrates an example Esri Maps for IBM Cognos deployment:
- EM4C Gateway is installed on the IBM Cognos Gateway server. If there is more than one IBM Cognos Gateway in this example, EM4C Gateway would be installed once per IBM Cognos Gateway.
- EM4C Dispatcher is only installed on the IBM Cognos Dispatcher servers where the report and/or presentation service is running.
- If IBM Cognos Dispatcher is installed more than once on any given server (that is, a dispatcher that listens on a different port number), EM4C Dispatcher would be installed once for every dispatcher that is running the report and/or presentation service.
- EM4C Dispatcher does not get installed onto an IBM Cognos Dispatcher server that is only running Content Manager.
- EM4C Server can be installed anywhere in the application tier. There is no requirement that EM4C Server be installed on the same hardware as other IBM Cognos components (although it usually is because it is a lightweight component). There is no requirement that you have the same number of EM4C Servers as EM4C Dispatchers (even though the illustration below shows it this way). Last, the EM4C Server can be installed and configured more than once on any given server (not illustrated).
