Chapter 1. WebSphere Information Integrator Content Edition V8.2.1 architecture 39
1.3.1 Configuration server
The Configuration server is responsible for reading configuration information in
from an XML file and making this information available to the WebSphere
Information Integrator Content Edition EJB components that use it. The
configuration server also communicates with the administration tool, making it
possible to update the configuration of WebSphere Information Integrator
Content Edition on-the-fly.
1.3.2 Logging server
The Logging server is an optional WebSphere II Content Edition service that
provides logged output of information, warnings, and errors that occur while
WebSphere II Content Edition is running. Any number of logging servers may be
running at one time, with each logging to one or more files. WebSphere
Information Integrator Content Edition components may be configured with
different logging properties, using the administration tool.
1.3.3 RMI Proxy Connector server
The RMI Proxy Connector server is responsible for instantiating “real” content
connectors and making them accessible to the RMI Proxy Connector. The RMI
proxy connector server runs in a separate JVM from the application server,
allowing the “real” content connector to run in an alternative JVM or use native
methods without violating the EJB specification.
The batch file RMIBridge.bat (RMIBridge.sh for UNIX®) located in the
WebSphere Information Integrator Content Edition bin directory is provided to
run the RMI proxy connector server.
1.3.4 Multi-Query Agent server
The Multi-Query Agent server is an optional service that is required only if your
application server enforces strict EJB compliance. A multi-query is a query that
can be run against multiple repositories.
To improve efficiency and robustness, each repository in a multi-query is
accessed in a separate thread of execution. The EJB Specification V1.1 prohibits
EJBs from managing threads themselves, so this threading is performed by a
multi-query agent that runs outside the context of the application server.
Multi-query agent instances are obtained from the multi-query agent factory
service.
In practice, many application servers permit EJBs to manage threads, so an
external multi-query agent may not be necessary. The application deployer can

Get WebSphere Information Integrator Content Edition: Planning, Configuration, and Monitoring Guide now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.