Accessing the JADE Monitor

To access the JADE Monitor, perform one of the following actions

• Click the Monitor toolbar button in the JADE development environment.

• Select the Monitor command from the JADE development environment Browser File menu.

• Select the Jade Monitor program icon from your JADE program folder, to run the standalone JADE Monitor application.

• Running the JADE Monitor application from the command line, as shown in the following example.

  jade.exe path=s:\jade\system ini=s:\jade\system\jade.ini schema=JadeMonitorSchema app=JadeMonitor

The JADE Monitor sign-on dialog is then displayed. When security is set for your JADE development environment, you can sign on to the JADE Monitor only if you have the appropriate access permission. When you click the OK button and you have access permission, the JADE Monitor Summary view is then displayed.

If you want to display another view (for example, the Users view) when the monitor is initialized, specify the valid view name in the DefaultPane parameter in the [JadeMonitor] section of the JADE initialization file on the client node.

For details about:

• Setting up the JADE Monitor, see "Setting Up the JADE Monitor", later in this chapter.

• Using the JADE Monitor, see Chapter 2, "Using the JADE Monitor for System Instrumentation and Diagnosis".

• Using system instrumentation and diagnosis methods in your JADE applications to examine your JADE system, nodes, or processes, see Chapter 4, "JADE System Instrumentation and Diagnosis", of the JADE Object Manager Guide.

  In an SDS environment, the secondary database server has a node stub that represents the primary server node. This node stub does not have the full functionality of a normal client; in particular, some statistical functions cannot be carried out on the node stub (for example, getting a node’s cache statistics).

  Any attempt to do so raises exception 1265 (Environmental operation out of scope for process). You can use the value returned by the Node class nodeRole method to distinguish the node stub from standard client nodes. For the node stub, the returned value is the Node class Role_Replay constant (as opposed to the Role_Standard constant).

• The context-related help information (knowledge base) that is displayed at the lower-right of the window of each view and selected component, see "Maintaining Knowledge Base Information", in Chapter 2.