Repository Editor Troubleshooting


	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

Consult the following table if you encounter problems while using the Repository Editor.

Repository Editor Troubleshooting

If...
Then...

A parameter is incorrect

Edit the service.

The Jolt server is down

Check the server. The BEA 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 Netscape browsers, make sure that Enable Java and Enable JavaScript are checked under Edit-->Preferences-->Advanced. Then select Communicator-->Tools-->Java Console. If the Java Console does not exist on the menu, the browser probably does not support Java.
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 user names 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 BEA 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.

If...	Then...
A parameter is incorrect	Edit the service.
The Jolt server is down	Check the server. The BEA 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 Netscape browsers, make sure that Enable Java and Enable JavaScript are checked under Edit-->Preferences-->Advanced. Then select Communicator-->Tools-->Java Console. If the Java Console does not exist on the menu, the browser probably does not support Java. 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 user names 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 BEA 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.