Table of Contents Previous Next Index

Services Layer components
SOAP Message Handler
Requests from client applications and/or Administration Console are submitted as SOAP RPC messages over an HTTP or HTTPS protocol. The SOAP Message Handler extracts the common command information from the SOAP request and sends it to the Fulfillment Engine. Replies from the engine are reformatted as SOAP responses.
Telnet Command Handler
This handler maps commands from the Telnet client into the common format used by the Fulfillment Engine. The common response format is similarly mapped into Telnet response output.
Fulfillment Engine
This processes the common request commands, sending an action to the appropriate agent or agents and processing any responses or error messages.
Application agents
These act on requests from the Fulfillment Engine to send requests to their associated server. Each agent is linked to a particular service, understanding the protocols used by that service to enable it to transform requests and responses to/from the common format. Agents are currently provided for
This agent handles sending data that is common to all the services to the User Profile Store. It uses the Locator service, which manages services that are distributed over multiple host machines.
Note FS supports both the pre-Platform and Platform versions of AgroPOP. Fulfillment Server checks the PED to see which version of AgroPOP is installed and then initializes the corresponding agent.
Provides access to the Messaging Search Engine (MSE) back-end server.
Other agents
There is also an agent that handles data for White Pages and a minor agent that allows administrators to be provisioned.
Related Topics:

Table of Contents Previous Next Index