Sending a One Way Message over JMS
The SOAP Invoke activity is used to send a one way message over JMS. The message format is a doc-literal element. Because this is a one way message, no response is expected from the server.
TIBCO Enterprise Message Service must be running.
- Procedure
- In the samples directory, select and double-click tibco.bw.sample.binding.soap.jms.OneWayDocLiteral. For more information, see Accessing Samples.
- In Project Explorer expand the tibco.bw.sample.binding.soap.jms.OneWayDocLiteral project.
- Fully expand the Processes directory and double-click JMSClient.bwp.
- Verify your TIBCO Enterprise Message Service connection.
- Fully expand the Resources directory.
- Double-click JMSConnectionResource.jmsConnResource.
- In the Basic Configuration dialog, click the Test Connection button to verify the connection.
- Click .
- At the left hand tree of Debug Configuration wizard, expand BusinessWorks Application and select BWApplication.
- Click the Applications tab and then click the Deselect All button if you have multiple applications. Select the checkbox next to tibco.bw.sample.binding.soap.jms.OneWayDocLiteral.application.
- Click
Debug.
This runs the sample in Debug mode.
- In
TIBCO Business Studio™, click the
Terminate
icon to stop the process.
The console displays messages similar to the following:
16:11:19.386 INFO [bwThread:In-Memory STWorkProcessor-2] c.t.b.p.g.L.t.b.s.b.s.j.O.Log - [Server] Received Request :: date=2016-04-21+05:30 boolean=true double=1.1 int=22 string=testStr byte=33 short=44
The expected outcome is:
[Server] Received Request :: date=2016-04-21+05:30 boolean=true double=1.1 int=22 string=testStr byte=33 short=44
Understanding the Configuration
The project comprises the following two processes:
- JMSClient
- JMSServiceProcess
The JMSClient process sends a one way request to the JMSServiceProcess through a SOAP doc-literal message.