Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Jolt   |   Topic List   |   Previous   |   Next   |   Contents   |   Index

   Using BEA Jolt

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.

Testing a Service covers the following main topics:

• Jolt Repository Editor Service Test Window

• Testing a Service

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.

Althouth the Test button in the Edit Services window is enabled when parameters are not added to the service, the Service Test window displays unused in the parameter fields, and they are disabled. Refer to Sample Service Test Window for an example of unused parameter fields.

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.

Service Test Window Description

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.

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.

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

Instructions for Testing a Service

Follow these instructions to test a service. For troubleshooting information, see the first two entries in the Repository Editor Troubleshooting table.

1. Select Services from the Repository Editor Logon window.

   The Services window is displayed.

2. Select the package and the service to test.

3. Click Edit to access the Edit Services window.

4. Click Test to access the Service Test window.

5. Enter data in the Service test window parameter text fields.

6. Click RUN.

   The status line displays the outcome as follows:

   • If the test passed: "Run Completed OK"

   • If the test failed: "Call Failed"

     See Repository Editor Troubleshooting for additional Repository Editor troubleshooting information.

Follow these instructions if editing is required to pass the test.

1. Return to the Repository Editor Logon window and click Packages.

2. Select the package with the services to be retested.

3. Click Unexport.

4. Click Back to return to the Repository Editor Logon window.

5. Click Services to display the Services window.

6. Select the package and the service that requires editing and click Edit.

7. In the Edit Services window, edit the service.

8. Save the service, click Test, and repeat steps 5 and 6 of the Instructions for Testing a Service section.