Sample transaction pathway

This section provides the high-level steps on how to install the product and import a sample transaction pathway. This sample assumes that you are using just one BTM agent extension for the test, and provides a simple transaction pathway that you can use and modify to see the various features and how they relate to one another.

This sample exists on all service sets so use commands based on your specific operating system.

Prerequisites

  • This sample requires a supported installation of WebSphere MQ, a queue manager and one queue defined for use by the sample. You must have authority to stop, install and start a WebSphere MQ exit and run the WebSphere MQ utilities amqsget and amqsput.
  • You need to know the following information:
  • The host of the WebSphere MQ installation.
  • The name of the WebSphere MQ queue manager to be used.
  • The name of the WebSphere MQ queue to be used.

Before you begin

  • Start the BMC services.
  • Distribute, install, and start the TMTM Extensible Agent on the host of the WebSphere MQ installation.
  • Distribute, install and start the TMTM Configuration Agent on the host of the WebSphere MQ installation.
  • Distribute and install the WebSphere MQ Exit in your queue manager.

To use the sample transaction pathway

  1. Edit the Samples\PutGetTP_Translation.txt from the installation directory and replace the following values with ones that match your environment. Refer to Exporting and importing Monitor Console environmental components with the CLI for more information.
    • [Model Host] TEST1=
    • [Host] TEST1=
    • [WebSphere MQ Queue] QUEUE=
    • [WebSphere MQ Queue Manager] ^QMGR$=
  2. Access the BTM tab and create a profile named "Sample BTM Profile".
    • Select a user or group in the Access Control List for Edit/Generate/Promote/Import and Deploy.
    • Move the host of the WebSphere MQ installation from the Available Hosts list to the Selected Hosts list.
  3. Unlock the profile and leave the BTM tab so you can import the model.
  4. Import the transaction pathway from the installation directory using mqsimport:

    mqsimport -p BMCSOFTWARE --profile ".", --model "." -–promote-translate-file Samples\PutGetTP_Translation.txt Samples\PutGetTP.zip SA -b

    If you changed the SA password from its default, replace BMCSOFTWARE with the valid SA password.

    This command imports:
    • a transaction pathway called PutGetTxnPathway
    • two activity implementations: amqsget and amqsput
    • a message format called SampleMsgFormat
  5. Generate the transaction pathway.
  6. Deploy the transaction pathway.
  7. From the InstallDir\Samples transfer amqsput.txt to the host of the WebSphere MQ installation. This is a sample message that matches the message format imported.
  8. Enter amqsput QUEUE QMGR < amqsput.txt
  9. Enter amqsget QUEUE QMGR

On the Operations tab, open the logical view to see the transactions in the transaction table. Select a transaction from the table and click the details button to see how the pathway lights up to show you the status and path taken. Expand the Physical tree to see how payload and labels are used. 

Was this page helpful? Yes No Submitting... Thank you

Comments