Getting Started-JetNet

This section describes problems you might encounter when setting up the Panther environment, or when running Panther, and tells you where to look for more information.

Error Files

The following files are used to record errors in the various Panther components. If you have problems during the setup procedure, check the directory from which you run the tutorial (proltut) for the existence of any of the files below and check its contents.

• stderr—Errors from the Panther application server are written to this file and include errors about environment variables and licensing problems.

• stdout—Includes errors specific to the application server.

• ULOG.*—Lists all middleware session activity and errors, particularly IPC resource errors. A new ULOG.* is started each day, with the date contained in the file name, in the format ULOG.ddmmyy.

• error.log—Contains errors generated by the Web application server.

If these files provide no clear direction, contact Prolifics Technical Support Services.

Setup and Connection Problems

This section describes some of the more common areas where you might encounter problems while setting up the Panther environment or using Panther, and provides hints for resolving them. If you need more assistance, contact Prolifics Customer Support.

Starting the application or servers

If you are unable to boot your application with rbboot (indicated by a FAILURE message), check the ULOG.* file in the proltut directory. Usually, a failure at this point indicates inadequate IPC resources. If the ULOG indicates IPC resource errors, refer to the JetNet Guide/Oracle Tuxedo Guide for more information.

If only the server running the proserv executable fails to start, check the stderr and stdout files.

Before attempting to restart the application, you need to shut down the servers, even if you received errors, by typing (in the window in which you ran rbboot):

rbshutdown

This utility shuts down the Panther application, including all active servers.

Activating a server

If you are unable to activate an application server using the JetNet Manager, check the following files in your proltut directory on the server, in the order in which they are listed:

stderr, stdout, and ULOG.*.

If you are unable to start the Web application server from your Web browser, check the files ULOG.* and error.log in the proltut directory.

If you have any problems that require changes to the proltut.ini file, or if error.log contains an error message indicating that you failed to connect to the server, you must stop and restart your Web application server to have the changes take effect. Shut down the server by typing:

$SMBASE/util/monitor -stop proltut

If you are unable to start a Panther client workstation when typing prodev at the command line, make sure you have applied the client environment settings to the current window by typing:

. ./setup.sh

If you receive an error message when you attempt to connect to the middleware from a PC client and cancel out of the Connect dialog, the editor workspace opens but you are not connected to the server. Check that the application and its servers are running and if not, start them up using rbboot. Once they have successfully started, choose FileOpenMiddleware Session in the editor. You will also need to open the remote libraries and remote repositories.

Connecting to the server locally

If you attempt to open a middleware session on a local UNIX client and receive the message that the TUXCONFIG file does not exist, most likely your SMRBCONFIG setting does not exactly match the Local JetNet Configuration File value in JetMan. The usual cause of this is that the value of SMRBCONFIG in setup.sh contains a symbolic link as part of your home directory location, and that JetMan used the actual disk location.

Accessing remote libraries

• If the Remote button is grayed out in the Library Table of Contents dialog box, and therefore you cannot access remote libraries, you are probably not connected to the middleware. Make sure the application and servers are running—see the section above on connecting to the server.

• The Remote button will also be grayed out if there is no file access server (devserv) running for the application. Check the status in JetMan of the file access server.

• If you attempt to open a remote library and the Library Table of Contents dialog box displays an error next to the library name, or if you get a library format error when you try to save a library member, the client machine may have timed out.
  
  If a client sits idle for a default period of 60 minutes, it is disconnected from the server; check the ULOG.* error file to verify that this is the case. If so, save any open modified screens to a local library, close the remote libraries using FileCloseLibrary, and reconnect to the application by choosing FileOpenMiddleware Session. Once you reconnect, you can open the remote libraries again; you can then open your modified screens and choose Save As to save them to the remote libraries.