Adapter services allow you to connect to the AR System Server and initiate an operation on the AR System from Integration Server. Integration Server uses adapter connections that you defined earlier to execute the adapter services. You invoke adapter services from flow or Java services to interact with the AR System Server to create, get, update, find, retrieve details, execute one of several adapter ARS Server operators, or delete entries in the AR System database. The adapter services perform these operations (for example, create, get, update, find, or delete) using the AR System Java APIs. Remedy Adapter makes synchronous calls to the AR System Server using the AR System Java APIs.

Entries in the AR System database are associated with specific AR System forms. A form defines the fields associated with an entry. At design time you configure an adapter service using templates provided with Remedy Adapter. When you configure an adapter service, you provide the form name. An adapter service template contains all the code necessary for accessing forms and obtaining fields. Each template represents a specific operation for doing work on an AR System Server, such as using the Get template to retrieve an entry from the AR System database.

You use Designer to configure the adapter service. For more information, see the webMethods Service Development Help for your release.

The input and output signatures for an adapter service are defined for you when you configure the adapter service. The input and output signatures depend on the function of the adapter service (for example, create, get, update, find, or delete) and the specific form that the adapter service is to use. For example, if you use the Create template, the input signature includes the fields from the form that you select when you configure a Create service. Similarly, if you use the Get template, the output signature includes the fields from the form that you select when you configure a Get service.