![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The iProcess Server Manager is a JSP web client application that utilizes TIBCO Hawk to provide a graphical view of the server processes on a machine or a node cluster. You can do the following from the iProcess Server Manager:
•
If you are planning to use the iProcess Server Manager, you must have TIBCO Hawk installed on:
• The machine hosting iProcess Engine. (TIBCO Hawk is distributed with this version of iProcess Engine, and can be installed when you install iProcess Engine. See TIBCO iProcess Engine Installation for more information.)
• The machines on which you want to use the iProcess Server Manager to administer iProcess Engine processes. For more information about how to install TIBCO Hawk, see TIBCO Hawk Installation and Configuration Guide.
For information on the correct version of TIBCO Hawk to be used, please see TIBCO iProcess Engine Installation.On Windows, iProcess Engine uses the iProcess nodename Web Server service (where nodename is the node name of iProcess Engine) to communicate with TIBCO Hawk. This service runs a Tomcat JSP web server that is installed as part of iProcess Engine (in SWDIR\tomcat directory.)You can install the iProcess nodename Web Server service when you install iProcess Engine. See TIBCO iProcess Engine Installation for more information.
• action is either: install, uninstall, start or stop.
• TIBCO_ROOT is the base directory for TIBCO software installations on this computer (by default c:\tibco).For example, to install and start the iProcess nodename Web Server service, use the following commands:
On UNIX, iProcess Engine communicates with TIBCO Hawk using the Tomcat JSP web server that is installed in SWDIR/tomcat.) You must start the Tomcat JSP web server by running the following script, which is located in the SWDIR/bin directory:
If you have installed the TIBCO Hawk software in a location other than the default (/opt/tibco), you must edit the smstart file, which is located in the SWDIR\bin directory, to modify the paths specified for HAWK_ROOT and RV_ROOT to reflect this.Similarly, to stop the Tomcat JSP web server, run the following script, which is located in the SWDIR/bin directory:If you want to access iProcess Server Manager by using HTTPS, you need to complete the following steps to configure the Tomcat JSP web server:
1. Get a keystore file and specify a password for it by using the keytool utility.
2. Add the HTTPS connector to the server.xml file of Tomcat.For example, add the following code in the server.xml file, which is located in the TOMCAT_HOME\conf directory:
The TIBCO Hawk Installation and Configuration Guide describes how TIBCO Hawk implements its security policy. TIBCO iProcess Server Manager can be configured to use this TIBCO Hawk policy as follows:
• TIBCO Hawk Agents can be configured to use a specific Java class to implement secure access for console applications such as iProcess Server Manager. Once a Hawk Agent has been configured with a string specifying that security class, this same string must be specified by all console applications that want to connect to this Agent and its microagents.Therefore, the iProcess Server Manager provides a file, iprocesshawk.properties, that contains an example of the security string HawkSecurityString. If you edit this string to the value required by the security model of the appropriate Hawk Agent, the Hawk Agent will read the correct value from this file and allow access.For example, if your Hawk Agent uses a security class name MySecurity.class, edit the file to read:With Trusted or TrustedWithDomain (see TIBCO Hawk Installation and Configuration Guide for details), you can use the two Hawk default security models:
• The Hawk bin directory (for example, c:\tibco\hawk\bin) needs to be added to your system path. This is because the Java files use Java Native Interface (JNI) to call a Windows DLL (HawkTrustedUserID.dll). If this directory is not on the path, the iProcess Server Manager web application will not work with either of these two security models.
• You must also add the appropriate account to the appropriate access control file used by the TIBCO Hawk Agent’s security policy, on all machines that will run the iProcess Server Manager. On Windows, this account is the SYSTEM account. On other platforms, this account is the account that is used to run the SM Start shell script.
− Windows: Make sure the iProcess nodename Web Server and TIBCO Hawk Agent services have been started (see Windows).
− UNIX/Linux: Make sure you have run the smstart script, which are located in the SWDIR/bin directory (see UNIX).
− machine is the machine where the iProcess Server Manager is installed.
− port is the port number of the machine where your iProcess Server Manager is listening to requests. The default is 8080.When you first start the iProcess Server Manager, it opens with the Configuration pane displayed:When you first start the iProcess Server Manager, it displays the Configuration pane. Configure the iProcess Server Manager for use in your environment as follows:
1. Enter the name of your Hawk Domain. By default the Hawk Domain is blank, but if you configured a different domain name, enter it here. The name specified for Hawk Domain on the master machine must also be specified on all machines in a clustered environment.
2. If when you installed TIBCO Hawk, you used the defaults for the following TIBCO Rendezvous configuration parameters, continue with the next step:
TIBCO Rendezvous Configuration Parameter However, if when you installed TIBCO Hawk, you changed TIBCO Rendezvous configuration parameters Daemon, Network or Service from the defaults, you must change the following process attributes in iProcess Engine to reflect this.
3. In the Search for nodes field, enter the name of iProcess Engine node that you want to administer and click the Search button.
4. When the iProcess Server Manager locates the node, it displays information about it as follows:
5. To find TIBCO Hawk Agents associated with the selected node, click the Browse for Agents button. If you have already browsed for agents, you can click the Load Known Agents button, which is faster than browsing. Also, if the Tomcat software times out, you need to click the Load Known Agents button.
6. The iProcess Server Manager displays the Process Control pane. Continue with the following section to learn more about controlling processes.The iProcess Management page shows information for the server you have selected. The view is hierarchical, so expand a server or a node in a cluster to show individual processes running on each. For example:
Starts the selected instance, all instances of a process, all processes on the selected server, or all processes in the node cluster. Starts the specified number of temporary instances of the selected process. Specify the number of instances in the text box to the left of the Start Temp button. These instances will not be restarted if the iProcess Engine is restarted. For example, you may want to start a new background process to cope with a short peak in demand. Stops the selected instance, all instances of a process, all processes on the selected server, or all processes in the node cluster. You can also force stop processes by selecting the Force stop check box and specifying the number of seconds after which Process Sentinels will stop waiting for processes to shut down cleanly and perform a forced stop (the default is 300 seconds). Restarts a process that is in a SUSPENDED state (one that has stopped and not been automatically restarted).To stop all processes on node staffw_103a6, highlight the node and click the Stop button. The message "Requesting Process(es) stop" appears at the bottom of the window and a red square next to each instance indicates that the instance is shutting down or has shut down:
To view the status of all processes, click the iProcess Management - View button. The Process View pane lists the currently configured processes, their status, number of instances and so on. For example:Note that the IAPJMS process is disabled, and therefore appears "greyed out." The display is refreshed every 5 seconds. You can configure the refresh interval as described in Customizing the iProcess Server Manager.To view summary information about processes, click the iProcess Management - Summary button. The Process Summary pane lists the process name, number of processes, and the parent/child relationships. For example:To view log files related to iProcess Engine, click the Log Viewer button. The Log Viewer pane is displayed:
3. Click the Get Logs button.
4. From the Log Files list, select the log file you want to view (for example, sw_error). The list contains all the log files found in the SWDIR\logs directory that matched the criteria you entered in the Log file filter field.
5. Enter the number of lines of the log file that you want to display and click either the From Top of Log button or the From End of Log button, depending on which part of the log file you want to view. You can also wrap lines by selecting the Wrap Lines check box.There are several configuration options that you can change by editing the configuration.xml file, which is located in the SWDIR\tomcat\webapps\ipsvrmgr directory. For example, to change the default refresh period (5 seconds), edit the following entry:By default, the iProcess Server Manager displays the node cluster you are part of or the individual server that you are using (if you are not part of a node cluster). You can connect to other servers as follows:
1. Click the Configuration button.
2. Enter the node name of the server you are looking for in the Search for nodes field and click the Search button.After a short delay, the details of the requested node should be displayed in the Configuration pane.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |