Initial Monitor Setup
In normal operation, when you start up Monitor, all of the WebObjects applications on your site are displayed under the Declared Apps heading, and the right frame shows information about the application you select. (Or if you set it up properly, you'll see a login panel and after you log in you'll see all of your WebObjects applications.) However, the first time you've started the Monitor, no applications are displayed. You need to configure the Monitor for use on your site.
To configure the Monitor application, do the following:
- Click the Options button.
- Look at the first section of the Configuration options. They should look like this:
- Local host name
- The name of the server Monitor is running on.
- Admin user name
- Protects the Monitor from being used by all users except the one specified here. If you enter a user name in this field and that user's password in the "Admin password" and "Admin password again" fields, Monitor runs in a protected mode. When you restart Monitor, it displays a login page instead of the typical first page.
- Admin password
- If you entered an administrator name, enter the administrator account's password here.
- Admin password again
- Repeat the administrator password here.
- Primary WebObjects.conf path
- The location of the public configuration file. Most of the time, this should be set to NeXT_ROOT/NextLibrary/WOAdaptors/Configuration. (You only need to change this if you move the configuration file.)
- Additional public paths
- If you have more than one server and each server has its own public configuration file, click the Add Path button and specify the location of the other configuration file(s). Servers can share the configuration file in NeXT_ROOT/NextLibrary/WOAdaptors/Configuration, so usually this setting is not necessary.
- Dedicated Monitor WebObjects.conf path
- The location of a configuration file used only by Monitor. This file is used only if you want to start multiple instances of Monitor, which is rare. See "Starting Up Multiple Monitor Instances."
- WebObjects executable name
- The executable that you want to use as the default executable for all applications you add to Monitor. By default, this is set to WODefaultApp or WODefaultApp.exe.
- Path to executable
- The path to the executable name you specified in the field above.
- Application cycling
- Default settings for the periodic shutdown of applications. For more information, see "Periodically Shutting Down the Application" in this guide.
- HTTP server host
- The host name of your HTTP server.
- Adaptor key
- The name of your WebObjects adaptor. Usually, this is WebObjects or WebObjects.exe. If you use the NSAPI adaptor or ISAPI adaptor, you may have to change the name here.
- Protocol name
- Should normally be set to http.
- Click the Save Changes button at the bottom of the page to record your changes.
- In the Main Menu area, click the Add button.
- For each application that you want to administer using Monitor, do the following:
- Type the application's name in the Application Name field. The application name is the path to the application relative to <DocRoot>/WebObjects.
- Type the path to the application executable in the Application Path field (for example C:\Next\NextLibrary\WOApps\MyApp.woa)
- Type the host name of the machine where the application is located in the Host name field.
- Click the Add to Declared Apps button.
The right frame shows configuration information.
Make sure each option has the appropriate setting as described below:
The second set of options affects the configuration file. Make sure each option has the appropriate setting as described below:
The third set of options displays default setting for each application that you'll add to the Monitor. Make sure each option has the appropriate setting as described below:
The fourth set of options you rarely have to change. They are used to build the WebObjects application URLs that you use when you click an application's hyperlink to access one of its running instances.
The right frame displays the Add Application Panel, which looks like this:
Monitor updates the port number and instance number fields for you.
- Autostarting is disabled.
- You won't get an application listing if you enter
http://localhost/cgi-bin/WebObjects/
or if you make a typo in an application URL. - If you start an application from the command line, you must use the -n option to specify an instance number.
Recall that when the public configuration file exists, autostarting is disabled. You can still start applications manually from the command line, but applications won't autostart when you type a URL in the browser.
This feature depends on autostarting, so it is disabled when autostarting is disabled.
Monitor associates an instance number with all applications that you declare in it, instead of just applications that perform load balancing among multiple instances. If you manually start an application and you want it to connect to the Monitor, you must specify the instance number that Monitor set up for you. For more information, see "Starting Up Applications From the Command Line" in this guide.
Table of Contents Next Section