The TIBCO Direct JMS step lets you send messages and receive messages from topics and queues without using the JNDI libraries. You can also receive, change, and forward an existing message.
All the common message types including Empty, Text, Object, Bytes, Message, and Mapped (Extended) are supported.
The TIBCO Direct JMS step is configured using a single editor regardless of the messaging requirements. Input options vary on the messaging requirements. The editor only allows valid configurations. Enabling some features can make other unavailable.
The default TIBCO Direct JMS step name uses the following convention: EMS queuename publish. If there is not a publish queue name, the default step name is EMS queuename subscribe. If another step also uses the default step name, DevTest appends a number to the step name. You can change step names at any time.
Prerequisites: Using DevTest with this application requires that you make one or more files available to DevTest. For more information, see Third-Party File Requirements in Administering.
Parameter Requirements: This step requires the connection parameters and the subject names that are used in the application under test. DevTest, by default, uses the TIBCO_SERVER property in the JNDI Server URL. This property must be added to your configuration if you plan to use it. Your environment may require other parameters. Get these from the application developers.
For more detailed information about parameters and fields, see JMS Messaging (JNDI).
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|