Testing the database protocol

This calls the engine command line to test the specified database protocol thread. Under advanced security mode, the security server controls access to the command line.

  1. Open the Select Source Thread menu to select the source thread. This lists all database protocol threads under the current site. If the selected thread is a Database Inbound protocol, then the Outbound Options group is disabled. The command line also runs the thread read action and converts the result to the VRL data.
  2. If required, then select Update Database to update, insert, and delete data in the database through the generated command.
  3. Specify the testing data file in Choose Data File, or click the folder button to open a file browser to select the data file. By default, the file browser locates on the $HCISITE folder.
    If the selected thread is a Database Outbound protocol, then specify the name of the input data file here. The format of the testing data file must conform to the VRL file of the database table schema defined in the Database Outbound protocol. Generally, it is a text file with each row corresponding to one row in the database table. The columns are separated by a comma.
    To maintain security, browsing is restricted to within the $HCIROOT hierarchy.
  4. 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.
  5. Open the Detail level menu to select from a list of detail levels for the test output that is reported in the Result pane. Detail levels go from 0 (raw, unparsed data) to 4 (most detail). The default detail level is 1.
  6. 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 the length of the first message. It reads that many characters into a message, and 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.
  7. Specify the encoding in the Encoding field, or click the arrow to open a list of different encodings. These 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 -e encoding option is added to the corresponding command line.
  8. Specify a file name in which to store the result in the Save To field, or click the folder button to open a file browser.
    If the selected thread is a Database Outbound protocol, then based on the thread outbound SQL statement, the command line reads the testing data file. It then generates a list of SQL statements with filled values.
  9. If required, then select Grep to filter the output.
  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.