Adapter Service Operation

The run time actions that occur in Integration Server and the AR System when an adapter service is invoked are basically the same for all types of Remedy Adapter services. The only difference is the operation performed in the AR System.

At run time, an Integration Server client invokes a flow or Java service on Integration Server. This flow or Java service, in turn, invokes the adapter service. The adapter service uses AR System Java APIs to interact with the AR System Server. The diagram and table below illustrate the run-time processing for an adapter service.

Step	Description
1	An Integration Server client invokes a flow service or Java service on Integration Server.
2	The flow or Java service invokes the adapter service, which you configured earlier using Designer.
3	The adapter service gets a connection from the service's connection pool, which you created and enabled earlier using Integration Server Administrator.
4	Through its connection, the adapter service interacts with the AR System Server using the AR System Java APIs to perform the operation requested by the adapter service.
5	The AR System Server performs the requested operation, interacting with the AR System database as necessary. For more information about a specific operation, see one of the following sections: Create Adapter Service Delete Adapter Service Find Adapter Service Get Adapter Service Batch Get Adapter Service Update Adapter Service ARS Server Operations Adapter Service
6	The AR System Server returns the result of the operation. See the appropriate section below for information about the outcome for a specific operation.
7	The adapter service updates results of the operation in the pipeline.