Your InfoSphere® MDM Collaboration Server system is a three-tier Java Platform, Enterprise Edition application. In a typical production system, the web and application tiers are combined on one or more physical systems application servers.
The application server machine runs a Java™ application server, typically WebSphere® Application Server. Your system does not run within the context of the Java application server, but as separate processes. The third tier, the data store, is an RDBMS on a separate physical system.
The application server communicates with the data store by using JDBC over the underlying network, which is usually TCP/IP over Ethernet. Users interact with the system over the network with HTTP, either through a web server such as Apache or directly with the Java application server.
The system consists of seven services:
- admin service
- rmiregistry
- eventprocessor
- scheduler
- queuemanager
- workflowengine
- appsvr service
The appsvr process is the Java Platform, Enterprise Edition application server. The admin service and rmiregistry services must be run on each system. You can implement load sharing by instantiating one or more of each of the remaining four services on the same or separate physical machines except for the workflowengine service.
An installation can have only one workflowengine service.
Optimizing the application server tier involves optimizing the server hardware for the chosen application server and tuning the Java application server.
You must tune your system for your environment and system demands:
An example of a typical system configuration where all services exist on one physical machine:
In clustered environments, tuning involves the placement and number of the services on multiple physical machines.
- The system binary files that are stored in the $TOP directory and the document store, in the $TOP/public_html directory, are required to exist on a shared file system such as NFS.
- The Java application server must be installed on local storage where all application servers use the same UID and GID to access the shared file system.
- In cases where there is a separate web tier, for example, the system uses Apache or some other web server that passes requests to the Java application server. The load that is placed on the system by the web server can be assumed to be negligible.
An example of a clustered system configuration with multiple machines with multiple services:
