Previous Topic: JCAPS Messaging (Native)Next Topic: Oracle Steps


JCAPS Messaging (JNDI)

The JCAPS Messaging (JNDI) step lets you send and receive messages from topics and queues. You can also receive, change, and forward an existing message.

JCAPS Messaging (JNDI) supports all the common message types including Empty, Text, Object, Bytes, Message, and Mapped (Extended).

The JCAPS Messaging (JNDI) step is configured using a single DevTest editor regardless of the messaging requirements. The input options vary on the messaging requirements. The editor only allows valid configurations, so when you enable some features others can become inactive.

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. Other parameters may be required, depending on your environment. Get these parameters from the developers of the application.

Detailed information about parameters and fields for JCAPS Messaging can be found in JMS Messaging (JNDI).

Default Step Names: The default JCAPS Messaging (JNDI) step name uses the following convention: JCAPS queuename publish. If there is not a publish queue name, the default step name is JCAPS queuename subscribe. If another step uses the default step name, DevTest appends a number to this step name to keep it unique. You can change step names at any time.