Use the Jolt Repository Editor to add, modify, test, export, and delete Oracle Tuxedo service definitions from the Repository based on the information available from the Oracle Tuxedo configuration file. The Jolt Repository Editor accepts Oracle Tuxedo service definitions, including the names of the packages, services, and parameters.
The Jolt Repository is used internally by Jolt to translate Java parameters to an Oracle Tuxedo type buffer. The Repository Editor is available as a downloadable Java applet. When an Oracle Tuxedo service is added to the repository, it must be exported to the Jolt server to ensure that the client requests can be made from a Jolt client.
If you are using the JDK 1.3 appletviewer to start the Jolt Repository Editor, you will not be able to connect to a remote machine, only to a local host JSL. This is due to a security restriction imposed in the JDK 1.3 appletviewer. Also, for JDK 1.2, you must use the -nosecurity option in the appletviewer if you are connecting to a remote machine JSL.
Complete the appropriate steps to start the Repository Editor.
Packages provide a convenient method for grouping services for Jolt administration. (A service consists of parameters, such as pin number, account number, payment, rate, term, age, or Social Security number.)
You use the Packages window to perform the following:
View packages and services
Export or unexport services
Access Package Organizer to:
Create a new package
Click the Packages button in the Jolt Repository Editor logon window to display the available packages. When you select a specific package from the display list, its services within that package are displayed.
Figure 4-5 contains a sample Packages window. The BANKAPP package is selected, and the services within the BANKAPP package is displayed.
A service is a definition of an available Oracle Tuxedo service. Services include parameters such as pin number, account number, payment, and rate. Adding or editing a Jolt service does not affect an existing Oracle Tuxedo service.
You use the Services Window to add, edit, or delete services.
Figure 4-6 is an example of a Services window with the BANKAPP package selected, and the display list of services and parameters available for this package (parameters are detailed later).
A service contains parameters, which may be a pin number, account number, payment, rate, term, age, or Social Security number. Figure 4-7 shows a Services window displaying a selected service and its parameters.
Adding or editing a parameter does not modify or change an existing Oracle Tuxedo Service.
Figure 4-7 Sample Services Window with Parameters List
Instructions for Viewing a Parameter
Select Services from the Repository Editor Logon window.
The Services window opens and displays the list of available packages.
Select a package.
The list of available services for the selected package is displayed.
In the preceding figure, BANKAPP is the selected package.
Select a service.
The list of available parameters for the selected service is displayed.
In the preceding figure, INQUIRY is the selected service.
View the parameters for a selected service in the Parameters display list.
In the preceding figure, ACCOUNT_ID, FORMNAM, SBALANCE, and STATLIN are the available parameters for the INQUIRY service.
This section includes the necessary steps for setting up a package and its services:
Saving your work
Adding a package
Adding a service
Adding a parameter
Saving Your Work
As you create and edit services and parameters, it is important to regularly save information to avoid losing input. Clicking Save Service in the Edit Services window can prevent the need to re-enter information in the event of a system failure.
When you add or edit the parameters of a service, you must select Add before choosing Back from the Edit Parameters window and returning to the Edit Services window.
If adding a new service or modifying an existing service in the Edit Services window, be sure to select Save Service before choosing Back. If you select Back before you save the modified information, a warning is briefly displayed on the status line at the bottom of the window.
Adding a Package
When you need to add a new group of services, you create a new package before adding the services. The Package Organizer Window and the following procedure show how to add a new package, BALANCE, to the Packages listing.
Figure 4-8 Package Organizer Window
Instructions for Adding a Package
Click Packages in the Repository Editor Logon window to display the Packages window.
Select Package Organizer to display the Package Organizer window, similar to that shown in the figure Package Organizer Window.
Figure 4-10 shows an example Edit Services window with STRING selected as the buffer type for the service SIMPAPP.
Figure 4-10 Edit Services Window: Select STRING Buffer Type
Adding a Parameter
Clicking New under the label Parameter level actions in the Edit Services window is displayed in the Edit Parameters window. Review the features in Figure 4-11. Use this window to enter the parameter and screen information for a service.
Figure 4-11 Edit Parameters Window: Add a Parameter
Adding a Parameter Window Description
Adds the field name (for example, asset, inventory).
Lists data type choices:
string—null-terminated character array
carray—variable length 8-bit character array
Radio button choices for direction of information:
Input—information is directed from the client to the server.
Output—information is directed from the server to the client.
Both—information is directed from the client to the server, and from the server to the client.
Number of times that an identical field name can be used. If 0, the field name can be used an unlimited number of times. Occurrences are used by Jolt to build test screens; not to limit information sent or retrieved by Oracle Tuxedo.
This button is disabled when the window is launched.
Clears the fields of the window.
Is disabled while new parameters are added.
Adds new parameters to the service. The parameters are saved when the service is saved.
Returns the user to the previous window.
Instructions for Adding a Parameter
Select Field Name to activate the field, and type the field name.
If the buffer type is FML or VIEW, the field name must match the corresponding parameter field name in FML or VIEW.
Select the data type.
Specify a direction by selecting the input, output, or both radio buttons.
Select the Occurrences text field to activate it, and then enter the number of occurrences.
Select Add to append the information. Add does not save the parameter.
In the Edit Services window, click Save Service to save the parameter as a part of the service.
If you do not click Save Service before you click Back, the parameters are not saved as part of the service.
Click Backto return to the Edit Services window.
Selecting CARRAY or STRING as a Parameter Data Type
If CARRAY or STRING is the selected buffer type for a new service, only CARRAY or string can be added as the data type for the accompanying parameters.
In this case, only one parameter can be added. It is recommended that you use the parameter name “CARRAY” for a CARRAY buffer type, and the parameter name “STRING” for a STRING buffer type.
Figure 4-12 is an example of the Edit Parameters window with string as the selected data type for the parameter. The Data Type defaults to string and does not allow you to modify that particular data type. The Field Name can be any name.
Figure 4-12 Edit Parameters Window: string Data Type
Grouping Services Using the Package Organizer
The Package Organizer moves services between packages. You may want to group related services in a package (for example, WITHDRAWAL services that are exported only at a certain time of the day can be grouped together in a package).
Use the Package Organizer arrow buttons to move a service from one package to another. These buttons are useful if you have several services to move between packages. The packages and services display listings to help track a service within a particular package.
Figure 4-13 is an example of a Package Organizer window with a service selected for transfer to another package.
Figure 4-13 Package Organizer Window
Package Organizer Window Description
Packages (left display list)
Lists packages containing services in the selected package.
Packages (right display list)
Lists packages available as destinations for the selected service.
Services (left display list)
Lists available services for the selected package.
Services (right display list)
Lists available services of the highlighted package that you moved.
Moves services (one service at a time) to the package highlighted on the left.
Moves services (one service at a time) to the package highlighted on the right.
Adds the name of a new package.
Returns user to the previous window.
Instructions for Grouping Services with the Package Organizer
In the Packages window, click Package Organizer.
In the Package Organizer window, select the package containing the services to be moved from the Packages left display window.
Select the service to be moved from the Services left display window.
In the previous figure, INQUIRY is the selected service in the BANKAPP package.
Select the package to receive the service from the Packages right display window.
The previous figure shows the selected service, INQUIRY, and the selected package, BANK, to which the INQUIRY service will be moved.
Figure 4-14 Example of a Moved Service
To move the service between the packages, select the left arrow (¨) or right arrow ().
These keys are activated only when both packages (left and right are displayed) and a service are selected. The keys are only active in the direction of the package where the service is to be moved. The previous figure, Example of a Moved Service, shows that the INQUIRY service has been moved to the BANK package on the right.
You cannot select the same package in both the left and right display lists.
Modifying Packages, Services, and Parameters
You can make the following changes to packages, services, and parameters:
Edit a service
Edit a parameter
Delete a parameter, service, or package
Editing a Service
You can edit an existing service name or service information, or access the window to add new parameters to an existing service. For a description of the Edit Services window, see Adding a Service Window Description. Figure 4-15 is an example of the Edit Services window.
Figure 4-15 Edit Services Window
Instructions for Editing a Service
Follow these steps to edit a service:
From the Services window, select the package containing the service that requires editing.
The services available for the selected package are displayed.
Select the service to edit.
The parameters available for the selected service are displayed.
Click Edit to display the Edit Services window, as shown in the previous figure.
Type or select the new information, and click Save Service.
Editing a Parameter
All parameter elements can be changed, including the name of the parameter.
If you create a new parameter using an existing name, the system overwrites the existing parameter.
Figure 4-16 is an example of the Edit Parameters window.
This section describe how to delete a package. Before deleting a package, all the services must be deleted from the package. The Delete option is not enabled until all components of the package or service are deleted.
The system does not display a prompt to confirm that items are to be deleted. Be certain that the parameter, service, or package is scheduled to be deleted or has been moved to another location before selecting Delete.
Deleting a Parameter
Determine which parameters to delete and follow these steps:
In the logon window, click Services to display the Services window.
In the Services window, select the package and service that contain the parameter you want to delete.
Click Edit to display the Edit Services window.
Select the parameter you want to delete from the Parameters display list.
Under Parameter Level Actions, click Delete.
Deleting a Service
Determine which services to delete and follow these steps:
Make certain that all parameters within this service are deleted before selecting this option.
Select the package containing the service you want to delete.
Select the service you want to delete.
Delete is enabled.
Click Delete. The service is deleted.
Deleting a Package
Determine which packages to delete and follow these instructions. Make sure all services contained in this package are deleted or moved to another package before selecting this option.
In the Repository Editor Logon window, click Packagesto display the Packages window.
Select a package.
The package is deleted.
Making a Service Available to the Jolt Client
To make a service available to a Jolt client, you export it. All services in a package must be exported or unexported as a group. A service is made available by using the Export and Unexport radio buttons.
Determine which services are being made available or unavailable to the Jolt client. Services are exported to ensure that the Jolt client can access the most current service definitions from the Jolt server.
Figure 4-17 shows the Packages window, where you can export and unexport services.
Figure 4-17 Packages Window: Export and Unexport Buttons
Follow these steps to export or unexport a service:
From the Repository Editor Logon window, select Packages to display the Packages window.
Select a package.
The Export and Unexport buttons are enabled.
To make the services in the selected package available, click Export.
To make the services in the selected package unavailable, select Unexport.
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 Oracle Tuxedo server is running for the service being tested.
Although 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.
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.
Figure 4-19 is an example of a Service Test window with both writable and read-only text fields.
Figure 4-19 Sample Service Test Window
Service Test Window Description
The following table describes the Service Test window options.
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.
Displays the name of the tested service (read-only).
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.
Runs the test with the data entered.
Clears the text entry field.
Lists additional parameter fields, if applicable.
Lists previous parameter fields, if applicable.
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
Figure 4-20 shows a typical Repository Editor service flow test.
Consult Table 4-6 if you encounter problems while using the Repository Editor.
Table 4-6 Repository Editor Troubleshooting
A parameter is incorrect
Edit the service.
The Jolt server is down
Check the server. The Oracle Tuxedo service is down. You do not need to edit the service.
You receive any error
Make sure the browser you are running is Java-enabled:
For Internet Explorer, make sure the version is 3.0 (or later).
If running Netscape Navigator, check the Java Console for error messages.
If running appletviewer, check the system console (or the window where you started the appletviewer).
You cannot connect to the Jolt Server (after entering Server and Port Number)
Make sure that:
Your Server name is correct (and accessible from your machine). Check that the port number is the correct port. A JSL or JRLY must be configured to listen on that port.
The Jolt Server is up and running. If any authentication is enabled, check that you are entering the correct usernames and passwords.
If the applet was loaded through HTTP, make sure that the Web server, JRLY, and the Jolt server are on the same machine. (To do this, enter the server name into the Repository Editor that refers to the same machine name as the one used in the URL to download the applet).
You cannot start the Repository Editor
If you are running the editor in a browser and downloading the Repository Editor applet through HTTP, make sure that:
The browser is Java-enabled.
The Web server is running and accessible.
The RE.html file is available to the Web server.
The RE.html file contains the correct <codebase> parameter. Codebase identifies where the Jolt class files are located.
If running the editor in a browser (or appletviewer) and loading the applet from disk, make sure that:
The browser is Java-enabled.
The RE.html file exists and is readable.
The RE.html file is Java-enabled.
The RE.html file contains the correct <codebase> parameter (this is where the Jolt class files are installed on the local disk).
CLASSPATH is set and points to the Jolt class directory.
You cannot display Packages or Services even though you are sure they exist
Make sure that the Jolt Repository Server is running (JREPSVR).
Make sure that the JREPSVR can access the repository file.
Make sure that the configuration of JREPSVR: verify CLOPT parameters and verify that jrep.f16 (FML definition file) is installed and accessible (follow installation documentation).
You cannot save changes in the Repository Editor
Check permissions on the repository file. The file must be writable by the user who starts JREPSVR.
You cannot test services
Check that the service is available.
Verify the service definition matches the service.
If Oracle Tuxedo authentication is enabled, check that you have the required permissions to execute the service.
Check if the application file (FML or VIEW) is specified correctly in the variables (FIELDTBLS or VIEWFILES) in the ENVFILE. All applications FML field tables or VIEW files must be specified in the FIELDTBLS and VIEWFILES environment variables in the ENVFILE. If these files are not specified, the JSH cannot process data conversion and you receive the message “ServiceException: TPEJOLT data conversion failed.”
Check the ULOG file for any additional diagnostic messages.