Using XMLink Universal Gateway

Chapter 5. Building and Accessing Enterprise Services

This chapter describes the steps for using XMLink Universal Gateway to access enterprise services.

Writing Enterprise Services

The first step is to decide what business assets will be advertised as enterprise business services. The business logic for these assets can be:

Deploying Enterprise Services

Once the code is available for these enterprise business services, it needs to be made available to XMLink Universal Gateway.

One way to do this would be to publish the service and create WSDL files to describe the input and output parameters of the service.

WebSphere Application Server has tools and wizards to help you publish services and create the WSDL and SOAP files.

Deploying the Gateway Adapter EJB

For RMI/IIOP implementations, the Gateway Adapter EJB must be installed and deployed on the EIS. In most cases, the EIS machine would be a J2EE application server, like IBM WebSphere. Follow the application server's instructions for deployment of EJBs.

Configuring the Gateway Adapter EJB

For RMI/IIOP implementations, the Gateway Adapter EJB must be configured with:

For more information on configuring the EIS machine, see "Configuring the Enterprise Information System Machine."

Configuring Services on the Gateway Tuxedo Server

On the Tuxedo server machine, you need to configure the following:

For more information on configuring the Tuxedo server machine, see "Configuring the Tuxedo Server Machine."

Advertising Services to Tuxedo Applications

Once the Gateway Tuxedo Server is installed on the Tuxedo server machine, you need to:

Calling Services from Tuxedo Application

The Tuxedo client makes service calls in the usual manner using tpcall. The Tuxedo client does not need to know where the service will actually be processed. The transfer of data to the EIS machine in order to process the enterprise services is transparent to the Tuxedo client.

Mapping Service Names

When running XMLink Universal Gateway, you need to map the service names if the same name is not used in Tuxedo and on the EIS. The following diagram illustrates how a Tuxedo service (get_cust) can be mapped to service deployed on the EIS (find_client). In this example, a different reference name is specified even though reference names can match either the Tuxedo service or the EIS service.

Figure 5-1 Mapping Service Names