Adapter Services
Adapter services allow you to connect to the Jolt server and initiate a service on the Tuxedo server from the Integration Server.
You call adapter services from a flow or Java service to interact with the Jolt server. At design time, the adapter obtains service information about each application deployed on the Tuxedo server from the Jolt server. The adapter gets this information directly from the Jolt repository and stores it in the TuxedoConnectionFactory. From this information, you configure adapter services. The Integration Server then uses adapter connections that you defined earlier to execute the adapter services.
You configure adapter services using the template provided with the Tuxedo Adapter. The template represents a specific technique for doing work on the Jolt server, such as creating an account in an Tuxedo application. An adapter service template contains all the code necessary for interacting with the Jolt server but without the data specifications. You provide these specifications when you configure a new adapter service.
You use Digital Event Services or Designer to configure an adapter service. For more information, see the webMethods Service Development Help for your release.
Configuring a new adapter service from an adapter service template is straightforward. Using Digital Event Services or Designer, you assign the service an adapter connection. After you select the connection for the adapter service, you select the adapter service template. At this point, the adapter automatically populates the Tuxedo-specific fields in the adapter service editor tabs. You then use the editor to manipulate these fields to configure the adapter service.
The fields in the input and output signatures for an adapter service template are predefined and depend on the specific signatures of the Tuxedo service selected. The Integration Server parses Tuxedo fields that have more than one occurrence in the same Tuxedo application as an array of elements.
Important: All variables in the input signature will be rendered as java.lang.Strings and will appear as strings on the input pipeline regardless of their data type in Tuxedo. The execute() function of the Tuxedo Adapter will translate these strings to the proper input data types before passing them to Tuxedo.
Each adapter service you configure can be used as a standalone, executable entity. However, you can also incorporate your adapter services in flow services or Java services to implement business workflow. Using the Flow Service Editor in Digital Event Services or Designer, you can create intelligent business applications wrapped around the adapter services.