|
|
The following sections describe how to use AquaLogic Service Bus services from BEA Tuxedo, which is an inbound example:
You must have a WTC server configured with one local access point and one remote access point. This provides access from AquaLogic Service Bus to Tuxedo services. For information on configuring WTC, refer to Configuring WebLogic Tuxedo Connector for Tuxedo Transport.
To utilize theAquaLogic Service Bus service from Tuxedo, you must configure a new proxy service using the AquaLogic Service Bus Console. For more information about proxy services, see Proxy Services in the Using the AquaLogic Service Bus Console.
Log in to the AquaLogic Service Bus Console and perform these steps in the order presented.
To complete this configuration, you will perform the tasks described in the following sections:
The Create a Proxy Service – General Configuration page displays, as shown in Figure 4-1.
Service Name – The name of the service
Service Type – Select Any XML Service (the default).
| Note: | Tuxedo Transport only supports Any XML Service and Messaging Service as Service Types. |
Endpoint URI - Enter a service name that corresponds to the endpoint URI on the server where the service was deployed.
Field Table Classes – Optional field. Enter the name of the class or classes describing the FML/FML32 buffer received. These are used for the FML/FML32-to-XML conversion routines to map field names to element names. This is a space separated list of fully qualified class names.
View Classes – Optional field. Enter the name of the class or classes describing the VIEW/VIEW32 buffer received or sent. These are used for the VIEW-to-XML or VIEW32-to-XML conversion routines to map field names to element names. This is a space separated list of fully qualified class names.
| Note: | X_C_TYPE and X_COMMON Tuxedo buffer types are handles in the same manner as VIEW/VIEW32 buffers. |
| Note: | If an incoming request contains a VIEW, then the corresponding VIEW class should be specified in the AquaLogic Service Bus CLASSPATH. |
Classes Jar – Select a JAR Resource that contains a JAR file with the FML/FML32 or VIEW/VIEW32 classes necessary for this endpoint operation
Local Access Point – Select a local access point from the drop-down list that is associated with the Export. The drop-down list contain local access points configured in WTC. A Proxy Service cannot be created if there is not an associated local access point.
Reply Buffer Type – Select from the drop-down list the type of buffer that the remote Tuxedo client will receive. This field is enabled if the Response Required field is checked.
Reply Buffer Subtype – This field is enabled if the previous Request Buffer Type value is VIEW or VIEW32. Enter the buffer subtype with which to associate the reply buffer. This field is enabled if the Response Required field is checked.
Response Required? – Select the check box if this service is expected to send a response. The default status is checked, and unchecked if the service type is Messaging Service and the response message type is None. In this case, the field is not enabled.
Request Encoding – Specify a character set encoding for requests in Tuxedo transports.
Response Encoding – Specify a character set encoding for responses in Tuxedo transports.
Transformation Style – The ordering or grouping of elements when FML or FML32 buffers are transformed into XML. Select one of the following choices:
AquaLogic Service Bus Message Flows define the implementation of proxy services. Message flows can include zero or more pipeline pairs: request and response pipelines for the proxy service (or for the operations on the service); and error handler pipelines that can be defined for stages, pipelines, and proxy services. Pipelines can include one or more stages, which in turn include actions.
For more information about configuring AquaLogic Service Bus Proxy Services, see Using the AquaLogic Service Bus Console and Modeling Message Flow in AquaLogic Service Bus in the AquaLogic Service Bus User Guide.
The following sections provide one example of how to change the routing behavior of the proxy service and edit this message flow to:
The Resource Browser pane is opened in the navigation panel and the Summary of Proxy Services project page is displayed in the console.
. A display similar to Figure 4-4 appears:The Edit Message Flow page for the proxy service you created previously is displayed. This page displays the default message flow configuration. The default configuration consists of a start node. This is the minimum configuration of a message flow. The behavior of the message flow is sequential.
In the message flow, the name of the node changes to display the route node name.
The Edit Stage Configuration page is displayed. The page contains a single link, Add an Action.
A stage is an element of a pipeline and it is a container for actions defined in a pipeline. Actions are the elements of a pipeline stage that define the handling of messages as they flow through a proxy service.
The Edit Stage Configuration page changes to display the contents of the action. The contents of the action are defined by the type of node we created—a route node.
The Service Browser displays the names of the Proxy Service and Business Service that you created.
The display updates to show routing to the Business Service.
The configuration is completed and ready to test.
Now that you have configured BEA Tuxedo to work with AquaLogic Service Bus, you can perform a test to verify that it is working correctly. If you are using XML-to-FML32 and FML32-to-XML conversions, you can test this configuration using the “ud32” Tuxedo client program that is included with BEA Tuxedo. (If you are using FML conversions, you can use the “ud” client.) ud32 reads input consisting of text representation of FML buffers. For more information, see the information on the ud and ud32 commands in the Tuxedo Command Reference.
If you are not using XML-to-FML and FML-to-XML conversions, you must develop a test client program in Tuxedo to test this configuration. To find information on this task, refer to the BEA Tuxedo documentation.
|
