Copyright © TIBCO Software Inc. All rights reserved.
Copyright © TIBCO Software Inc. All rights reserved.


Chapter 5 Administering iProcess Engine Server Processes : Using the iProcess Server Manager to Administer Server Processes

Using the iProcess Server Manager to Administer Server Processes
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:
Start and stop processes (specifically BG, BGPREDICT, DLMGR, IAPJMS, SPO, and DIRECTOR)
Hawk Requirements
If you are planning to use the iProcess Server Manager, you must have TIBCO Hawk installed on:
Enabling the iProcess Server Manager
Windows
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.
Alternatively, you can use the following command to install, remove, start or stop the service:
   SWDIR\bin\smserv.bat action TIBCO_ROOT
where:
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:

 
   smserv.bat install C:\tibco
   smserv.bat start C:\tibco

 
UNIX
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:
  smstart
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:
  smstop
Configuring Tomcat JSP Web Server to Support HTTPS
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.

 
JAVA_HOME\bin\keytool -genkey -alias alias_name -keyalg RSA -keystore keystore file_path

 
You are prompted to specify some personal information.
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:

 
<!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
<Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS"
keystoreFile="keystore file_path"
keystorePass="keystore file_password"/>

 
3.
See the Tomcat documentation for more information.
Configuring TIBCO Hawk Security for iProcess Server Manager
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:
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:
HawkSecurityString=MySecurity.class
The file can be found at:
SWDIR\tomcat\webapps\ipsvrmgr\WEB-INF\classes
\iprocesshawk.properties
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.
Starting the iProcess Server Manager
To start the iProcess Server Manager:
1.
UNIX/Linux: Make sure you have run the smstart script, which are located in the SWDIR/bin directory (see UNIX).
2.
   http://machine:port/
where
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.
For example:
   http://titan:8080/
When you first start the iProcess Server Manager, it opens with the Configuration pane displayed:
Figure 1 iProcess Server Manager Configuration Panel
Configuring the iProcess Server Manager
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.
2.
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.
4.
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.
Controlling Processes
To view the Process Control pane, expand iProcess Management > Control.
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:
Expanding a process shows the instances of that process:
Using the buttons at the bottom of the page, you can do the following:
Example
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: 
Viewing Process Statuses
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.
View the Process Summary
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:
Viewing the iProcess Engine Log Files
To view log files related to iProcess Engine, click the Log Viewer button. The Log Viewer pane is displayed:
To view a log file, do the following:
1.
2.
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.
6.
You can use the following buttons for navigation:
Customizing the iProcess Server Manager
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:
<!-- page refresh interval in seconds -->
<refresh>5</refresh>
Connecting to a Different Server
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.
After a short delay, the details of the requested node should be displayed in the Configuration pane.

Copyright © TIBCO Software Inc. All rights reserved.
Copyright © TIBCO Software Inc. All rights reserved.