Appendix A. Administration Utilities

rbconfig -h

Usage: rbconfig [-f] [<binary file>]

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.

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.

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.

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):

• JPL Procedures—The unnamed procedure is removed unless the -r option is used.

• Entry and Exit Functions.

• Menu and Menu Script Name.

• Pointer (cursor specification).

• Wallpaper Pixmap (screen background).

• Icon (image displayed when screen is iconified).

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

• Active, Inactive, and Armed Pixmap specifications are removed.

• Drop-Down Source for option menus/combo boxes is changed from External Screen to Constant Data since the lists do not need to be populated from an external screen.

Converts a binary JetNet configuration file to ASCII and vice versa

rb2asc -a[ -f] [asciiFile cfgFile]

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.

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.

Starts a Panther application

rbboot [-a] [cfgFile]

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.

rbboot starts all Panther application components such as servers, as defined in cfgFile. If you omit specifying a configuration file, rbboot checks whether environment 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:

• All machines have the executables for which their servers are configured.

• Each machine has SMRBCONFIG set to the same value as its Local JetNet Configuration File property (refer to page 3-14).

• In a multi-machine application, the listener process is running on each machines. Start the listener process with rblisten.

  Note: If an application takes more than two minutes to start up, rbboot times out and posts an error message. When this happens, rbboot exits without booting any other application servers. To boot the rest of the application, run rbboot again.

Creates a JetNet configuration file

rbconfig [-f] [cfgFile]

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

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.

Starts the listener process

rblisten -p portNum [-h host]

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 master 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.

Shuts down a Panther application

rbshutdown [-f] [cfgFile]

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.

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.