Previous Topic: SonicMQ Messaging (Native)Next Topic: webMethods Steps


SonicMQ Messaging (JNDI)

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

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

The SonicMQ 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 could 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: You need the connection parameters and the subject names that are used in the application under test. DevTest, by default, uses the SONICMQ_SERVER property in the JNDI Server URL. This property must be added to your configuration if you plan to use it. There could be other parameters that are required, depending on your environment. Get these parameters from the developers of the application.

Default Step Names: The SonicMQ Messaging (JNDI) step has a default name using the following convention: Sonic queuename publish. If there is not a publish queue name, the default step name is Sonic 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.

For more detailed information about parameters and fields, see JMS Messaging (JNDI).