Testing a Service

Test a service and its parameters before you make them available to Jolt clients. You can test currently available services without making changes to the services and parameters.

Note: The Jolt Repository Editor allows you to test an existing BEA Tuxedo service with Jolt, without writing a line of Java code.

An exported or unexported service can be tested; if you need to change a service and its parameters, unexport the service prior to editing.

This topic includes the following sections:

Jolt Repository Editor Service Test Window

Use the Run button to test the service to ensure that the parameter information is accurate. A service can only be tested when the corresponding BEA Tuxedo server is running for the service being tested.

Note: The Service Test window displays up to 20 items of any multiple-occurrence parameters. All items that follow the twentieth occurrence of a parameter cannot be tested.

The following figure is an example of a Service Test window with both writable and read-only text fields.

Sample Service Test Window

The following table describes the Service Test window options.

Note: You can enter a two-digit hexadecimal character (0-9, a-f, A-F) for each byte in the CARRAY data field. For example, the hexadecimal value for 1234 decimal is 0422.

Option	Description
Service	Displays the name of the tested service (read-only).
Parameters displayed	Tracks the parameters displayed in the window (read-only).
Parameter text fields	The parameter information text entry field. These fields are writable or read-only. Disabled if read-only.
RUN	Runs the test with the data entered.
Clear	Clears the text entry field.
Next	Lists additional parameter fields, if applicable.
Prev	Lists previous parameter fields, if applicable.
Back	Returns to the Edit Services window.

Testing a Service

You can test a service without making changes to the service or its parameters. You can also test a service after editing the service or its parameters.

Test Service Process Flow

The following figure shows a typical Repository Editor service flow test.

Test Service Flow

If Edits are Required After Testing

Follow these steps if editing is required to pass the test: