|
|
The following sections describe how to use AquaLogic Service Bus services from BEA Tuxedo:
To use AquaLogic Service Bus services from Tuxedo, you must configure a new proxy service using the AquaLogic Service Bus Console. For more information about proxy services, see Proxy Services: Creating and Managing 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:
For detailed procedural information, see Using the AquaLogic Service Bus Console.
You must be in a session to edit resources.
A message at the top of the page indicates that the project was added successfully.
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 service types. |
Endpoint URI - Enter a service name that corresponds to the endpoint URI on the Tuxedo server where the service was deployed.
Field Table Classes – Optional. 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. Enter the name of the class or classes describing the VIEW/VIEW32 buffer received or sent. These are used for the VIEW/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 handled in the same manner as VIEW/VIEW32 buffers. |
| Note: | If an incoming request contains VIEW buffers, then specify the corresponding VIEW classes 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 – From the drop-down list, select a local access point that is associated with the WTC Export service. The drop-down list contains local access points configured in WTC. You cannot create a proxy service without an associated local access point.
If no local access points exist or to create a new one, select New. Enter the corresponding Local Access Point Name and Local Network Address in the adjacent fields. Upon validation of the endpoint, the access point is added to the WTC configuration for each WTC server. If no WTC server exists, one is created.
You can enter an existing access point name after selecting the New option. This causes the existing information to be updated with the new parameters. You can change only the host name and port number.
Remote Access Point – This field appears only when you select New in the Local Access Point field. From the drop-down list, select a remote access point to be associated with the newly created local access point. If none exist or to create a new one, select New. Enter the corresponding Access Point Name and Network Address in the adjacent fields.
The remote access point will also be the authentication principal for the WTC connection for inbound requests. Optionally, you can create a user with the same access point ID in the default security realm to allow incoming calls. To do so, select Yes from the Create User? drop-down list. The password will be randomly generated using a temporary variable to avoid security issues.
| Note: | Access points and users are not deleted by the transport when the endpoints are removed, since they may be used by multiple endpoints. To remove access points, use the WebLogic Server Administration Console. |
Reply Buffer Type – From the drop-down list, select the type of buffer that the remote Tuxedo client will receive. This field is enabled if the Response Required field is selected.
Reply Buffer Subtype – This field is enabled if the Request Buffer Type value is VIEW or VIEW32. Enter the buffer subtype with which to associate the reply buffer.
Response Required? – Select the check box if this service is expected to send a response. The default status is selected. However, if the service type is Messaging Service and the response type is None then it is not selected; 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:
None: (default) The order of fields may not be respected.
Ordered: The fields will be presented with all their occurrences in the correct order.
Ordered and Grouped: If the fields are logically structured as records, the fields will be ordered by occurrence and also grouped by record.
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 Handlers 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 creating, editing, and viewing message flows, see Proxy Services: Message Flows in the 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 a proxy service and edit the message flow by:
Edit Message Flow icon in the row of the proxy service you created in Add a Proxy Service.
The Edit Message Flow page displays the default message flow configuration which consists of a single 
Proxy Service icon that signifies the starting node for the service. This is the minimum configuration of a message flow. The behavior of the message flow is sequential.
Proxy Service icon and select Add Route.
Route Node icon, then click Edit Name and Description. Change the name and description, as desired, then click Save.In the message flow, the name of the node changes to display the Route Node name.
Route Node icon and select Edit Route.
On the Edit Stage Configuration page, the only object displayed is the 
Add an Action icon.
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.
Add an Action icon, then select Add an Action > Communication > Routing.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 you created—a Route Node.
The Service Browser displays the proxy services and business services that you created.
The display updates to show routing to the business service.
The configuration is completed and ready to test.
Once 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 the text representation of FML buffers. For more information on the ud and ud32 commands, see 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, see the BEA Tuxedo documentation.
|