A separate Event Server program is available for each PeopleTools release. This program connects to the driver shim in a Windows* socket.

Remote processing between the shim and the Event Server is also possible. This means that the Event Server can run on a different machine than the driver shim.

The Event Server can run as a DOS window on a Windows NT* machine. The screen shows debug messages as an event is processed. The information includes the status of the transaction displayed on the Event Server. This enables you to determine exactly which transaction is being processed.

DSTRACE messaging includes a detailed description of the event and event processing.

You can apply a Matching policy for both the Publisher and Subscriber channels. If an association between the User object and the PeopleSoft employee does not exist, the Metadirectory engine executes a Matching policy and requests a query to merge attributes between the two objects.

You can also query PeopleSoft for attribute values needed for data manipulation or processing within a policy without copying the data to the Identity Vault.

Command line parameters define how the Event Server is to be executed, how to connect to the driver shim, and whether the Event Server should be installed as a service. The parameters also designate the path of the PeopleSoft client environment. For more information, refer to Section 3.1, Installing the PeopleSoft Service Agent.

You can set the driver to auto-start by installing the Event Server as a Windows service and setting the auto-start flag on the driver. For more information, refer to Section 3.3, Installing the Event Server.

The driver can query the Identity Vault and PeopleSoft schemas for attributes that can be used in the Mapping policy, or query PeopleSoft for objects defined as policy objects on the Driver object.