CHAPTER 17 This chapter discusses how to use the ACE XML Gateway with the TIBCO Rendezvous (TIB/RV) and WebSphere MQSeries messaging services. It covers these topics: About Messaging Support in the ACE XML Gateway, page 17-179 Adding a Messaging Server, page 17-179 Adding TIBCO Rendezvous Services, page 17-181 Defining MQSeries Services, page 17-182 About Messaging Support in the ACE XML Gateway The ACE XML Gateway can act as a message consumer or producer for messaging platforms, including WebSphere MQ, TIB/RV, and JMS. Using the mediation features in the ACE XML Gateway, you can map message between messaging protocols to other protocols, such as HTTP or SOAP. This chapter contains information specific using the ACE XML Gateway with the native formats of TIB/RV and WebSphere MQ. For general information on using the ACE XML Gateway with messaging sources, see Chapter 16, Working With JMS Traffic. Also, see Configuring JMS Mediation section on page 16-175 for information about mediating between messaging formats and others. An important difference between messaging services exposed by the ACE XML Gateway compared to other types of services is that you do not have to set up consumer provisioning for messaging handlers. The access control for a message handler is implied by its consumer interface settings, which specify provider resource and filtering properties, such as queue name, subject name, or topic, on which the handler accepts messages. Adding a Messaging Server The TIBCO and MQSeries server types are intended to be used if the message format is native TIBCO or MQSeries. These servers also support JMS. However, to route JMS traffic where the underlying implementation is TIBCO or MQSeries, create a JMS-type server rather than a TIBCO or MQSeries server. Note This section describes adding a TIB/RV or MQSeries server. For information on JMS, see Working With JMS Traffic, page 16-167 17-179
Adding a Messaging Server Chapter 17 To add a messaging server: Step 1 Step 2 Step 3 While logged into the ACE XML Manager as an Administrator or Privileged user with Routing role, set the active subpolicy to the one in which you want to add the server definition. Click the Messaging Servers link in the navigation menu. In the Messaging Servers page, use the controls on the page to add a new server definition, edit an existing server definition, or remove an existing server definition, as follows. To add a TIB/RV server: a. Click the Add a New TIB/RV Server button. b. Configure the following settings on the New Server page: TIB/RV Settings Name Daemon Service Network Description The name that identifies this server in the ACE XML Manager's console. This should be a descriptive name that is unique across TIB/RV server objects in the policy. The name of the TIB/RV daemon on the server, in host:port format. The host value can be the fully qualified domain name of the TIB/RV server or its IP address. The port value is a whole number specifying any unused port over which both the server and client communicate. In a standard TIB/RV-enabled application, the rvd daemon listens for TIB/RV messages on port 7500; however, the client and server can communicate on any port as long as they both use the same port and no other listener is using that port. Ports 8200 through 8299 are reserved for use by the ACE XML Manager, and should not be used here. Optional. To use a TIB/RV service other than the default, type the new value into this field. This numeric value provides a way to segregate network traffic without regard to subject; for example, two clients on the same network could use a queue named request.queue without encountering naming conflicts if the clients specify different service numbers. If you're not sure what value this field should have, leave it blank to use the default TIB/RV service. Optional. To use a TIB/RV network parameter other than the default, type the new value into this field. If you're not sure what value this field should have, leave it blank to use the default TIB/RV network. To add an MQSeries server: a. Click the Add a New MQSeries Server button, at the top of the MQSeries Servers section. b. Configure the following settings in the New Server page: MQSeries Settings Name Host Description The name that identifies this server in the ACE XML Manager's console. This should be a descriptive name that is unique across MQSeries server objects in the policy The MQ server to use, by its fully qualified domain name or its IP address. 17-180
Chapter 17 Adding TIBCO Rendezvous Services MQSeries Settings Port Channel Queue Manager Description The MQ server port to use. The default value is port 1414. You can use this field to specify an alternate port if, for example, a firewall won't permit connections on the default port. The MQ client channel to use. The MQ queue manager. Step 4 Click Save Changes to commit the changes to the working policy. After creating the server definitions, you can configure the service routing objects that use the server, as described in the following sections. Adding TIBCO Rendezvous Services The ACE XML Gateway supports TIBCO Rendezvous (TIB/RV) as a source and destination message format. Note TIBCO Rendezvous support in the ACE XML Gateway is a separately licensed feature of the ACE XML Gateway. If you want to enable TIBCO Rendezvous support but do not have the appropriate license level, contact your support representative. To have the ACE XML Gateway receive or publish TIBCO Rendezvous messages, you create a TIB/RV handler or service descriptor. Handlers can receive messages on a particular subject published to a TIBCO provider, while service descriptors publish messages to the provider. The ACE XML Gateway supports asynchronous and synchronous messaging mode in asynchronous mode (or fire-and-forget mode), a response is not expected from the backend service and not generated for the service requestor. In synchronous mode (or publish-reply), a response is expected from the backend service and passed back to the consumer. To add TIB/RV message management to your policy, first create the server object that represents the external service provider. For details see Working with Messaging Servers section on page 14-157. You can then configure the messaging service definitions, as follows. Configuring the TIB/RV Handler Configuring a TIB/RV handler is similar to configuring other Gateway handlers. For general information on configuring handlers, see Creating Handlers section on page 5-42. Also, much of the information applicable to JMS messaging also applies to TIB/RV. For details, see Chapter 16, Working With JMS Traffic. However, for a TIB/RV handler, a few differences exist. When creating the handler, choose either of the following protocol options: TIB/RV Request-Reply to have the ACE XML Gateway return a configurable response to a message initiator. TIB/RV Fire-and-Forget to not return a response to the message initiator. 17-181
Defining MQSeries Services Chapter 17 In the consumer interface settings, specify a TIBCO server as the source of messages, and specify the Subject on which to listen. The subject is a property of the Service Interface settings for the handler. When set up to listen on a particular Subject, the ACE XML Gateway can receive and validate messages transmitted on the network. For request/reply handlers, you can also configure message specifications for the response message. The message specification in either case can ensure that a particular argument is present in a message, or it can validate the argument content or type. Configuring the TIB/RV Service Descriptor As with setting up a RIB/RV handler, setting up a service descriptor for TIB/RV consists of choosing from either of the TIB/RV protocol options, depending on whether the destination is set up for synchronous or asynchronous messaging. Specify the Subject for messages sent by the service descriptor. As with the handler, you can specify rules and requirements for the messages sent by the service descriptor and returned in response to a message. To do so, configure the request and response message specification. Defining MQSeries Services You can set up the ACE XML Gateway to receive or publish IBM WebSphere MQ (MQSeries) messages by creating a MQSeries handler or service descriptor. MQ Series handlers receive MQ Series messages on a particular queue, while service descriptors publish messages to a queue. To manage WebSphere MQ traffic with the ACE XML Gateway, first create the server object that represents the external WebSphere MQ message service provider. For details see Working with Messaging Servers section on page 14-157. Next, create the handlers and service descriptors that receive and publish messages to the message provider, as described in the following sections. Configuring the MQSeries Handler Configuring an MQSeries handler is similar to configuring other Gateway handlers. For general information on configuring handlers, see Creating Handlers section on page 5-42. Also, see Chapter 16, Working With JMS Traffic, for more information on how to use the ACE XML Gateway with messaging services. For an MQSeries handler, when creating the handler choose MQ Series Request-Reply as the protocol of the handler. In the consumer interface settings, choose an MQSeries server as the server, and specify the Queue of the messages which you would like the handler to receive. The ACE XML Gateway can validate messages received on the queue. For the handler, you can also specify the response message requirements. Configuring the MQSeries Service Descriptor As with setting up a MQSeries handler, setting up an MQSeries service descriptor consists of choosing the MQ Series Request-Reply as the protocol of the service descriptor. 17-182
Chapter 17 Defining MQSeries Services Depending on your application, you may need to avoid using MQ Series Request-Reply service descriptors with Gateway clusters. In MQSeries request-reply, response messages are configured to be sent to a specified, static reply queue. Since all Gateways in a cluster will listen on the same reply queue, it s possible for a reply to a request issued from one Gateway in the cluster to be received by another Gateway in the cluster. In the Service Interface page, configure the following MQSeries-specific settings: Queue. The queue on which messages are published from the service descriptor. Reply Queue. The name of the queue on which the response is expected from the Tibco server. Default Response Encoding. The encoding format of the response messages generated by the backend application. The ACE XML Gateway can automatically detect the format (when none (auto-detect) is selected). However, if the application is designed to return a specific encoding, you can set the encoding as a response requirement here. As with the handler, you can specify rules and requirements for the messages sent by the service descriptor and returned in response to a message. To do so, configure the request and response message specification. 17-183
Defining MQSeries Services Chapter 17 17-184