Testing a transaction ID

Tests a transaction ID (TRX ID) separately from the engine. This simulates getting the transaction ID on an incoming message from the source thread.

This runs any inbound TPS for the source thread before the engine retrieves the transaction ID. This is necessary because the TPS may change the message content.

  1. For Select Source Thread, click the arrow to open a list of available threads.
  2. Specify the testing data file in Choose Data File. You can also click the folder button to open a file browser to select the data file. By default, the file browser locates on the $HCISITEDIR/formats/ folder.
  3. Select the line termination format in which to save the test messages. Click the arrow to open a list of formats.
    Newline Terminated reads the data in the file until it finds a newline character, making all that data one message, and sends that to the parser. It then reads until it finds the next newline character, makes a second message, and sends that to the parser.
    Length Encoded reads the first 10 characters to determine how long the first message is, reads that many characters into a message, and then sends it to the parser.
    EOF Terminated reads the file until it gets to the end-of-file character, takes that as a message, and sends it to the parser.
  4. Specify the encoding in the Encoding field. You can also click the arrow to open a list of different encodings that identify the encoding of messages in the selected data file. The command converts the messages from the identified encoding to UTF-8 to perform the test. When you select an encoding from the list, an -x encoding option is added to the corresponding command line.
  5. For Driver Control, set the content to message metadata DRIVERCONTROL. You can input any content to set to drivercontrol using this option.
    For tests on DICOM messages, -c drivercontrol is required, where drivercontrol is {AbstractSyntax***} {TransferSyntax***}. This is required to get the TRX ID.
  6. Select how to process records.
    process all records reads the selected data file and processes all the records in it.
    process one record reads the selected data file and processes only the first record in the file.
  7. Select Inbound Type Data to test the data routes configured in the Network Configurator.
  8. Select Inbound Type Reply and select a Reply Thread to test the reply routes configured in the Network Configurator. This is available only whenInbound Type Reply is selected.
  9. Select Verbose to show verbose information. When this is checked, a -V option is added to the command line.
  10. Click Run Command to run the command shown in Preview Command to Issue.
    As the test is being configured, a command-line command and the requisite parameters are generated in Preview Command to Issue. This is for display only. A command cannot be manually entered.