JetNet/Oracle Tuxedo Guide

Appendix E. Application Setup Checklist

Once the software is installed, the following steps provide a basic Panther application server for a JetNet/Oracle Tuxedo application.

Setting Up the Application Server

Populate the Application Directory

Unix Environment

On a UNIX application server, create an application directory containing:


`setup.sh`	A setup file with the location of the Panther software installation, the license file, and the middleware configuration file at your site. For the default setup file, copy setup.sh from the config directory of your Panther installation.
`client.lib, server.lib and common.lib`	Three standard application libraries. Copies of these libraries are in the `samples/newapp` directory of your Panther server installation.
`machine.env, proserv.env and progserv.env` (if using `progserv`)	Three standard environment files: machine.env for the machine settings, `proserv.env` for the standard server, and `progserv.env` for the conversion server (only used with applications converted from two-tier). Copies of these files are in the `samples/newapp` directory of your Panther server installation.
`devserv, proserv, prodserv` (optional), and `progserv` (optional)	Symbolic links to, or copies of, the server executables: `devserv` for the development access server and `proserv` for the standard server. If needed, create links or copies of progserv for the conversion server and `prodserv` for the server with debugger available services. The server executables are located in the `util` directory of your Panther installation.
`broker.bin`	The middleware configuration file. To create a middleware configuration file, refer to page 3-2.

Windows Environment

On a Windows application server, create an application folder containing:


`client.lib, server.lib` and`common.lib`	Three standard application libraries. Copies of these libraries are in the `samples\newapp` directory of your Panther server installation.
`machine.env, proserv.env` and`progserv.env`	Three standard environment files: `machine.env` for the machine settings, `proserv.env` for the standard server, and `progserv.env` for the conversion server (only used with applications converted from two-tier). Copies of these files are in the `samples\newapp` directory of your Panther server installation.
`devserv.exe, proserv.exe, prodserv.exe` and`progserv.exe`	Copies of the server executables: `devserv.exe` for the development access server and `proserv.exe` for the standard server. If needed, copy `progserv.exe` for the conversion server and `prodserv.exe` for the server with debugger available services. The server executables are located in the `util`directory of your Panther installation.

Configure the Middleware

Create a Configuration File

The middleware configuration file determines the machines and application servers needed for the application. To create a middleware configuration file:


	Configure the environment. In Windows, check the settings of `jetman32.ini`. In UNIX, run the application's version of `setup.sh`.
	Start JetMan.
	Choose FileNewApplication.
	On the Application Configuration window, enter the application name, and choose Next.
	Check the settings for the machine type, the Panther installation, the application directory, the middleware configuration file, and the machine environment variable file.
	For remote client access, choose Networking. On the Networking window, select Workstation Listener, and choose OK.
	Choose Done, and wait for the configuration file to be completed.

Configure Each Server

Once the configuration file is created and JetMan displays the application:


	Expand the application by double-clicking on the application name or choosing ViewExpand Subtree.
	With the machine highlighted, choose FileNewServer for each type of server to add to the application. A minimum setting would have one standard server (`proserv`) and one file access server (`devserv`) for each ma chine.
	For a standard server (`proserv`):
		Enter the name: `ProservMyApp`.
		Under Server Type, select Standard.
		Choose Options.
		Under Auto Advertised Services, choose All.
		If using remote reports, choose Report.
		If using service aliasing to test services, enter the Server Alias User Name.
		Under Database Connect String, enter the command needed to connect to the database.
		Under Init Routine, enter the function to be called on initialization of the server.
		When Standard Server Details is complete, choose OK.
		When Server Configuration is complete, choose OK.
	For a file access server (`devserv`):
		Enter the name: `DevservMyApp`.
		Under Server Type, select File Access.
		When Server Configuration is complete, choose OK.

Applications which are running remote reports must have a file access server on the same machine as the standard server in order to access and distribute the report files.

Start the Application Server

To start the application server in JetMan, highlight the application and choose EditActivate. An alternative is to use the command line utility rbboot. The Status window shows the messages for each server process.

Stop the Application Server

To stop the application server in JetMan, choose EditDeactivate or, if clients are connected, EditForcibly Deactivate. An alternative is to use the command line utility rbshutdown.

Setting Up the Workstation Client

Workstation (or remote) clients set SMRBPORT and SMRBHOST in order to access the remote application server. For Windows, these settings are stored in prol5w32.ini or prol5w64.ini.

Native (or local) clients set SMRBCONFIG in order to access the middleware configuration file on the same host machine.