JetNet/Oracle Tuxedo Guide


Appendix A . Administration Utilities

This chapter describes command-line utilities that can help you develop and manage a Panther application. Utilities are listed in alphabetical order. Utility descriptions are organized into the following components, as applicable:

To get a command-line description of a utility's available arguments and command options, type the utility's name with the -h switch. For example:

rbconfig -h

This yields the following output:

Usage: rbconfig [-f] [<binary file>]
-f      Output file may overwrite an existing file.

clnt2svr

Converts a two-tier application to a JetNet three-tier application

clnt2svr [-frv] sourceLib [-p prefixString]

-f
Replace existing libraries.

-p prefixString
Assign the specified prefixString to the client and server libraries. For example, if the prefix specification is bank, the client library is assigned the name, bankcl.lib, and the server library is banksv.lib. If a string is not provided, the library names default to cl.lib and sv.lib, respectively.

-r
Retain the unnamed JPL procedure on the service component. This can be useful if the unnamed procedure declares variables or carries out any initialization required for the service component.

-v
Output (verbose) the name of the each screen as it is processed and lists the properties that are being changed.

sourceLib
Name of source library that contains screens built with two-tier architecture functionality.

Description

The clnt2svr utility converts any two-tier JAM or Panther application that uses the transaction manager to a three-tier application.

Before running the utility, make sure your two-tier client screens, or source, reside in a library. To store screens in a library, run the formlib utility.

The clnt2svr utility creates a three-tier client library and a server library from a single source two-tier library. The utility makes two copies of each screen from the specified library and moves one of the copies to the new client library (cl.lib) and moves the other as a service component to the new server library (sv.lib). The source library remains unchanged and intact.

Certain property values are set on the copies while other properties that are pertinent only to a client screen are removed from the corresponding service component in order to avoid unnecessary processing on the server.

Three-tier Client Screens

The client screens in cl.lib have the model property (under Transaction) set to jetrb1, the request broker transaction model. The client screens use the model to submit service requests to the server. The server is then responsible for the database interaction by the transaction manager.

Service Components

The service components in the sv.lib are stripped of the following screen-level property values (if they were set on the source client screen):

The following properties associated with widgets on service components are stripped of values or changed:


rb2asc

Converts a binary JetNet configuration file to ASCII and vice versa

rb2asc -a[ -f] [asciiFile cfgFile]
rb2asc -b[ -f] [asciiFile]

-a

Convert binary files to ASCII

-b

Convert ASCII files to binary.

-f

The output file can overwrite an esisting file.

asciiFile

The name of the ASCII fil, either the target of ASCII conversion (with -a option) or the source of binary conversion (-b option). If you omit this argument, the default is broker.asc in the current directory

cfgFile

The name of the configuration file is to convert to ASCII. If you omit this argument, the default is one of the following in this order.

-

  1. The configuration file specified by the environment variable SMRBCONFIG.
  2. The configuration file specified by the environment variable TUXCONFIG.
  3. broker.bin in the current directory.

Description

The rb2asc utility lets you convert a binary JetNet configuration file to ASCII and vice versa. Use this utility in order to put a configuration file under source control or to compare different files.


rbboot

Starts a Panther application

rbboot [-a] [cfgFile]

-a

Start up only administration servers.

cfgFile

The name of the JetNet configuration file. If you omit this argument, the default is one of the following, in this order

  1. The configuration file specified by the environment variable SMRBCONFIG.
  2. The configuration file specified by the environment variable TUXCONFIG.
  3. broker.bin in the current directory.

Description

rbboot starts all Panther application components such as servers, as defined in cfgFile. If you omit specifying a configuration file, rbboot checks whether envi ronment variables SMRBCONFIG or TUXCONFIG are set; if not, it looks for broker.bin in the current directory.

Before starting an application, verify the following conditions:


rbconfig

Creates a JetNet configuration file

rbconfig [-f] [cfgFile]

-f

Overwrite cfgFile if it already exists. If you omit this option and cfgFile exists, rbconfig issues an error message and exits.

cfgFile

The name of the new configuration file. If you omit this argument, the default is one of the following, in this order:

  1. The configuration file specified by the environment variable SMRBCONFIG.
  2. The configuration file specified by the environment variable TUXCONFIG.
  3. broker.bin in the current directory.rbconfig creates a minimal

Description

JetNet configuration file that you can use as a starting point for application development. You can subsequently edit this file through the JetNet manager.

rbconfig creates a single-machine configuration that is enabled for workstation connections. No servers are defined. With this configuration, you can activate the application and connect to it from a PC workstation. You must define servers in order to make this a working application.


rblisten

Starts the listener process

rblisten -p portNum [-h host]

-p portNum

The port number to be used by the listener process. This argument and the port number that the configuration file specifies for host's Listener Port property must be the same.

-h host

The name or IP address (in dot notation) of this host's network address where the listener awaits a message from the master machine to begin the boot process. If you omit this argument, rblisten uses the machine's default host name.

Description

rblisten starts the listener process on the current machine. This process must be running on each machine that is defined in an application's JetNet configuration before you boot the application. At boot time there is no bridge process to receive communication. Instead, each listener process on the non-master and backup mas ter machines awaits a message from the master machine to begin the local boot process. The master machine uses the port number in each machine's Listener Port property to address its listening process (refer to page 3-15 ). Consequently, the port numbers supplied to rblisten and specified in the JetNet configuration file must match.

Starting a listener process on the master machine is optional when booting an application from that machine. However, the master machine must have a listener process in order to restart it from another machine.

rblisten authenticates most service requests by reading a file with a list of passwords and checking that any process requesting a service contains at least one of the passwords found in the file. If a file named .adm/tlisten.pw in the application directory is not found, the passwords are obtained from the file $SMBASE/udataobj/tlisten.pw. A zero-length or missing password file disables password checking which generates a warning in the ULOG file. Panther installs a default tlisten.pw in $SMBASE/udataobj/tlisten.pw with the password Panther.

Note: Add the appropriate call to rblisten to the system startup scripts file of each machine (for example, on SUN workstations /etc/rc.local) so that the utility runs automatically when the machine reboots.


rbshutdown

Shuts down a Panther application

rbshutdown [-f] [cfgFile]

-f

Forcibly deactivates the application and disconnects all clients connected to it. If you omit this option and the application has clients connected to it, rbshutdown leaves the application active and issues an error message.

cfgFile

The name of the JetNet configuration file. If you omit this argument, the default is one of the following, in this order:

  1. The configuration file specified by the environment variable SMRBCONFIG.
  2. The configuration file specified by the environment variable TUXCONFIG.
  3. broker.bin in the current directory.

Description

rbshutdown shuts a Panther application and all associated application components such as servers as defined in cfgFile. If you omit specifying a configuration file, rbshutdown tries to get SMRBCONFIG or TUXCONFIG from the environment; if neither is set, it looks for broker.bin in the current directory. Use the -f option to ensure shutdown of an application that has clients connected to it.

Note: If a server is still booting when rbshutdown is invoked, the utility can time out before the servers are available for shutdown. Run rbshutdown again after all servers have finished booting.