Interstage Application Server
V6.0
Trademarks
Trademarks of other companies are used in this user guide only to identify particular products or systems:
Product Trademark/Registered Trademark
Microsoft, Visual Basic, Visual C++, Windows, Windows NT, Internet Information Server, and Internet Explorer
Registered trademarks of Microsoft Corporation in the U.S.A. and other countries
Sun, Solaris, Java, and other trademarks containing Java
Trademarks of Sun Microsystems, Inc., in the U.S.A. and other countries
UNIX Registered trademark in the U.S.A. and other
countries, licensed exclusively through X/Open Company Ltd
Netscape, Netscape FastTrack Server, Netscape Enterprise Server, and Netscape Navigator
Registered trademarks of Netscape Communications Corporation in the U.S.A. and other countries
CORBA, Object Management Group, OMG, OMG IDL, IIOP, Object Request Broker, and ORB
Trademarks or registered trademarks of Object Management Group, Inc., in the U.S.A. and other countries
Interstage and ObjectDirector Registered trademarks of Fujitsu Limited
This document contains technology relating to strategic products controlled by export control laws of the producing and/ or exporting countries. This document or a portion thereof should not be exported (or re-exported) without authorization from the appropriate government authorities in accordance with such laws.
Fujitsu Limited
First Edition (November 2003)
The contents of this manual may be revised without prior notice. All Rights Reserved, Copyright © FUJITSU LIMITED 2003
Preface
Purpose of this Document
This document is the Interstage Application Server Operator's Guide.
Who Should Read this Document?
This document is intended for people operating Interstage Application Server. It is assumed that readers have a basic understanding of the following. • Basic knowledge of the Internet
• Object oriented technology
• Distributed object technology (CORBA) • Basic knowledge of relational databases
• Windows NT® or Windows® 2000 or Windows Server™ 2003
• UNIX
Organization of this Document
This document is organized as follows.• Chapter 1 - Interstage Operation Using the Interstage Management Console
This chapter explains Interstage operation using the Interstage Management Console. • Chapter 2 – Operating Applications
This chapter describes how to operate applications using WorkUnits. • Chapter 3 - Performance Monitoring
This chapter explains the performance monitoring tool. • Chapter 4 - Maintenance (Resource Backup)
This chapter describes system maintenance (resource backup). • Appendix A - Configuration of Interstage Management Console
This appendix explains the configuration and environment setup of the Interstage Management Console.
• Appendix B - isconfig.xml
This appendix describes the isconfig.xml for Interstage definition. • Appendix C - Interstage Operations by Interstage Integrated Commands
This appendix describes Interstage operations by Interstage integrated commands • Appendix D - Interstage System Definition
This appendix describes the Interstage System Definition. • Appendix E - Interstage Operating Environment Definition
This appendix describes the Interstage Operating Environment Definition. • Appendix F - Definition files used in operating the performance monitoring tool
This appendix explains the files that specify the target of the performance monitoring tool. • Appendix G - Systemwalker Linkage
Table of Contents
Chapter 1 Interstage Operation Using the Interstage Management Console
Introduction ...1-2 Starting the Interstage Management Console ...1-3 Login ...1-3 Starting and Stopping Interstage...1-4 Reconfiguring Interstage...1-5 Setting the Interstage Management Console Operating Environment ...1-6 Customizing the Connection Port Number ...1-6 Customizing SSL Encrypted Communication for the Interstage Management Console ...1-6 Enabling SSL Encrypted Communication...1-7 Disabling SSL Encrypted Communication...1-7 Changing the Certificate ...1-8 Other Changes... 1-11
Chapter 2 Operating Applications
Defining WorkUnits for Applications...2-2 Environment for Executing Applications ...2-2 Application Process Multiplicity ...2-2 Automatic Restart of Applications...2-2 Application Time-out ...2-2 Current Directory ...2-2 Environment Variables...2-3 PATH ...2-3 CLASSPATH ...2-3 Warning Monitoring...2-3 Starting and Stopping WorkUnits ...2-7 Start Time Monitoring ...2-7 Stop Time Monitoring ...2-7
Chapter 3 Performance Monitoring
The Performance Monitoring Tool...3-2 Functions of the Performance Monitoring Tool ...3-4 Function of Outputting Log Information to the Performance Log File ...3-4 Function of Monitoring the Real Time Performance Information by a Network Control Manager (Monitoring by MIB) ...3-6 Performance Monitoring Procedure...3-7 Registering to the SNMP Service ...3-12 1) Registering in the SNMP Service ...3-12 2) Copying the Performance Monitoring Tool ...3-13 3) Reading the MIB Definition File ...3-14 4) Setting the Port Number ...3-14 System Configuration Setting ...3-15 Creating a Performance Monitoring Environment ...3-16 Starting Operation of Performance Monitoring Tool...3-16 Monitoring Operations...3-17 Starting Performance Monitoring ...3-17 Starting a Business Application...3-17 Outputting the Performance Log File and Analyzing the Performance Information ...3-21 Stopping the Application ...3-23 Stopping the Performance Monitor ...3-23 Deleting the Performance Monitoring Environment...3-23 Deletion from the SNMP Service ...3-24 Analyzing the Performance Information and Taking Action ...3-24 Function of Outputting Log Information to the Performance Log File ...3-24 Performance Information Collected by the Network Control Manager with the Real Time Monitoring Function ...3-30 Warnings Regarding the Evaluation of the Performance Information ...3-32 Managing the Performance Log Files...3-33
Chapter 4 Maintenance (Resource Backup)
Backing Up and Restoring Resources...4-2 Outline and Applicable Resources...4-2 Interstage Setup Resource File ...4-3 Interstage Operation Tool Resource File ...4-4 CORBA Service Resource File ...4-5 Event Service Resource File ...4-8 Portable-ORB Resource File ...4-8
Interstage HTTP Server Resource File ... 4-11 InfoProvider Pro Resource File ... 4-11 J2EE Common Resource Files ...4-13 IJServer Resource Files ...4-13 Interstage JMS Resource File ...4-14 Servlet Service for Interstage Management Console Resource File ...4-15 SOAP Service Resource File ...4-15 InfoDirectory Directory Service Resource File ...4-16 Interstage Certificate Environment Resource File...4-17 Old Version Servlet Service Resource File ...4-17 Backup Procedure ...4-19 Stopping the Service...4-19 Creating a Backup Resource Directory ...4-19 Backing Up Interstage Setup Resource ...4-20 Backing Up Interstage Operation Tool Resources ...4-21 Backing Up CORBA Service Resource ...4-23 Backing Up Event Service Resource ...4-25 Backing Up Portable-ORB Resource ...4-26 Backing Up Component Transaction Service Resource ...4-27 Backing Up Database Linkage Service Resource ...4-29 Backing Up Interstage HTTP Server Resource...4-30 Backing Up InfoProvider Pro Resource...4-31 Backing Up J2EE Common Resource File...4-32 Backing Up IJServer Resource File ...4-33 Backing Up Interstage JMS Resource ...4-34 Backing Up Servlet Service for Interstage Management Console Resources...4-35 Backing Up SOAP Service Resources ...4-35 Backing Up InfoDirectory Resource ...4-37 Backing up Interstage Certificate Environment Resources...4-39 Backing Up Old Version Servlet Service Resource...4-40 Starting Up Services ...4-43 Restore Procedure...4-43 Stopping Services ...4-44 Restoring Interstage Setup Resource ...4-44 Restoring Interstage Operation Tool Resource ...4-45 Restoring CORBA Service Resource ...4-47 Restoring Event Service Resource ...4-48 Restoring Portable-ORB Resource ...4-49 Restoring Component Transaction Service Resource ...4-50 Restoring Database Linkage Service Resource ...4-51
Restoring Interstage HTTP Server Resources ...4-52 Restoring InfoProvider Pro Resource (Windows® and Solaris Only) ...4-53 Restoring J2EE Common Resource File...4-55 Restoring IJServer Resource File...4-56 Restoring Interstage JMS Resource...4-57 Restoring Servlet Service for Interstage Management Console Resources ...4-58 Restoring SOAP Service ...4-58 Restoring InfoDirectory Resource ...4-59 Restoring Interstage Certificate Environment Resources ...4-61 Restoring Old Version Servlet Service Resource...4-61 Starting Up the Services ...4-64 Moving Resources to Another Server ...4-65 Overview and Applicable Files ...4-66 Resource Exporting Procedure...4-67 Resource Importing Procedure...4-67 Stopping Services ...4-67 Importing Interstage Setup Resource...4-68 Importing Interstage Operation Tool Resource...4-70 Importing CORBA Service Resource...4-71 Importing Event Service Resource ...4-72 Importing Portable-ORB Resource ...4-72 Importing Component Transaction Service Resource...4-72 Importing Database Linkage Service Resource ...4-73 Importing Interstage HTTP Server Resource ...4-73 Importing InfoProvider Pro Resource (Windows® and Solaris Only)...4-73 Importing J2EE Common Resource File ...4-73 Importing IJServer Resource File ...4-74 Importing Interstage JMS Resource ...4-74 Importing Servlet Service for Interstage Management Console Resources ...4-74 Importing SOAP Service Resource ...4-74 Importing Interstage Certificate Environment Resources...4-74 Importing Old Version Servlet Service Resource ...4-74 Starting Up Services ...4-74 Collective Maintenance ...4-76 Resource Backup/Export ...4-76 Stopping the Service...4-78 Backup/Export Target Resource Definition...4-78 Interstage Resource Backup/Export...4-93
Restore/Import Target Resource Definition ...4-97 Interstage Resource Restore/Import ... 4-114
Appendix A Configuration of Interstage Management Console
Configuration of Interstage Management Console ... A-2 Web Browser ... A-2 Services ... A-2 Interstage Operation Tool Service ... A-2 Interstage Operation Tool (FJapache) Service ... A-2 Interstage JServlet (Operation Management) Service ... A-2 Interstage JMX Service... A-2 Environment Files ... A-3 Customizing Interstage Management Console Environments ... A-3 Changing the Port Number ... A-3 Changing the Automatic Update Interval ... A-3 Interstage JMX Service... A-4 Troubleshooting the Interstage Management Console... A-5
Appendix B isconfig.xml
Synopsis... B-2 Definition Parameter ... B-2
Appendix C Interstage Operations by Interstage Integrated Commands
Interstage Environment Setup ... C-2 Generating the Interstage System Definition File ... C-3 Registering the Interstage System Definition File... C-5 (1) Execute the isregistdef Command ... C-5 (2) Define the Environment for each Service ... C-6 Initializing Interstage ... C-7 Determining the Services to be Initialized ... C-7 Determining the Operating Mode ... C-8 Customizing the Interstage Operating Environment Definition... C-8 Executing Initialization ... C-13 Customization with the Interstage Operating Environment Definition ... C-14 Designing the Naming Service and Interface Repository... C-17 Starting Interstage ... C-19 Starting up a Database Management System ... C-20 Starting Interstage According to Application Status ... C-20 Starting the Resource Manager ... C-21 Starting WorkUnits ... C-22 Starting Interstage Automatically when Booting the Machine... C-22
Method of Constructing the Environment ... C-22 Operating Method ... C-24 Operating Method when not Starting Automatically... C-24 Terminating Interstage... C-26 Terminating WorkUnits ... C-27 Terminating Resource Manager...C-27 Terminating Interstage According to Application Status... C-28 Terminating the Database Management System...C-28 Customization by the ismodifyservice Command ... C-29 Changing the System Operation Pattern ...C-32 Changing the System Size... C-35 Changing the Naming Service/Interface Repository Settings... C-39 Changing Reference Location for the Naming Service and Interface Repository... C-40 Changing Reference Location for Only the Naming Service to the Home Server ... C-41 Changing Reference Location for the Interface Repository ... C-43 Change by the CORBA Service Operating Environment Definition... C-45
Appendix D Interstage System Definition
Syntax ... D-2 Statement ... D-2 Comment Line... D-3 Blank Lines ... D-3 Interstage System Definition File Syntax ... D-4 System Scale ... D-4
Appendix E Interstage Operating Environment Definition
Syntax ... E-2 Interstage Operating Environment Definition File Syntax ... E-3
Appendix F Definition Files Used in Operating the Performance Monitoring Tool
The Specification File for Performance Monitoring (ispstart Command) ... F-2 Synopsis... F-2 Specification Item... F-2 Definition Example ... F-2
Appendix G Systemwalker Linkage
Operation Monitoring and Automatic Operation Using the Systemwalker Linkage Function ...G-2 Overview of the Systemwalker Linkage Function...G-2
Operating Status Monitoring of WorkUnits and Objects ... G-4 Operating Status Monitoring of the Servlet Container ... G-8 Real-time Monitoring of Application Processing Status ... G-9 Define Monitoring Values... G-9 Automatic Control by Systemwalker OperationMGR Linkage...G-10 Preparations...G-10 Operating Method ... G-11
Interstage Operation Using the Interstage
Management Console
Introduction
The Interstage Management Console integrates the operation views for the individual services of the Interstage Application Server to enable centralized operation. The Interstage Management Console can also be used to easily define Interstage configuration and tuning.
If electronic signature or encryption processing such as SSL is to be defined from the Interstage Management Console for the following services, an Interstage certificate environment must be
configured in advance using commands. Configure an Interstage certificate environment by referring to the Security System Guide.
• Interstage HTTP Server • CORBA Service • Servlet Service • Interstage SOAP Service • Interstage JMS
Starting the Interstage Management Console
To use the Interstage Management Console, the following services must be started: • Interstage Operation Tool• Interstage Operation Tool(FJapache) • Interstage JServlet（OperationManagement)
After starting the above services, start the Web browser and specify the following URL: http://host-name:port-number/IsAdmin
host-name
Specify the host name or IP address of the server on which the Interstage Application Server is installed. port-number
Specify the port number on the Interstage HTTP Server to which the Interstage Management Console is connected. Specify the port number on the Interstage HTTP Server during installation. The default port number is 12000.
If SSL encrypted communication is to be used in operation of the Interstage Management Console, specify the following URL:
https://host-name:port-number/IsAdmin
If "Enable SSL encrypted communication" is selected for the operation mode of the Interstage Management Console during installation of Interstage, a certificate generated for the Interstage
Management Console is used. If the above URL is specified under this condition, a message dialog box indicating that there is a problem in the certificate reliability appears.
If the certificate obtained from a certification authority is to be used for SSL encrypted communication, refer to "Changing the certificate" in "Customizing Interstage Management Console."
In an environment where the Interstage Application Server is installed, selecting Start | Programs | Interstage | Application Server | Interstage Management Console will also start the Interstage Management Console.
Login
When the Interstage Management Console starts, a login window appears. Specify an arbitrary user ID registered in the OS. Administrator group authority is required to log in to the Interstage
Starting and Stopping Interstage
Select the System | Status tab on the Interstage Management Console to display the operating status of Interstage.
Select Detail | View to confirm the service to be operated.
Check the operating status of Interstage, then select Start or Stop and operate Interstage.
• If it has been defined to use the transaction service using the Interstage Management Console, performing an Interstage start or stop operation from the Interstage Management Console can also operate the transaction service (JTSRMP). However, the service cannot be operated when Interstage is started by machine booting or by Interstage integrated commands.
• If it has been defined to synchronize Web server operation with Interstage using the Interstage Management Console, performing an Interstage start or stop operation from the Interstage Management Console can also operate the Web server. However, the Web server cannot be operated when Interstage is operated by Interstage integrated commands.
• When performing an Interstage start or stop operation from the Interstage Management Console to operate the transaction service (JTSRMP) or Web server, the transaction service (JTSRMP) or Web server may fail to start. Even in this case, Interstage succeeds in starting.
Reconfiguring Interstage
Select System | Set Environment tab on the Interstage Management Console to display the Interstage environment setting window.
Change definition values as needed and select Apply.
Depending on the environment setting item that has been changed, Interstage may have to be restarted or initialized afterwards. It is recommended to back up resources in advance. Refer to "Maintenance (Resource Backup)" for more information on backing up resources.
• If Interstage is initialized using the Interstage integrated command, restart the Interstage Operation Tool service and Interstage JServlet (Operation Management) service after initialization is complete. • When the transaction service (OTS) is used, do not use the Interstage Management Console and
Interstage integrated command together. If these two functions are to be used together, note the following:
− Initialization may be performed using the Interstage integrated command in an environment in which it is defined to operate the transaction service (OTS) using the Interstage Management Console. In this case, define in advance that the transaction service (OTS) is not used, using the Interstage Management Console.
− Tuning may be performed using the Interstage Management Console in an environment in which initialization has been performed in operation mode TYPE2 using the Interstage integrated command. In this case, set up in advance the environment in operation mode TYPE1 using the Interstage integrated command.
Setting the Interstage Management Console
Operating Environment
This section explains how to customize the Interstage Management Console operating environment. The Interstage Management Console operating environment items that can be customized are as follow:
• Connection port number
• SSL encrypted communication for Interstage Management Console
Customizing the Connection Port Number
Use the following file to define the connection port number on the Interstage Management Console: Interstage-install-folder\gui\etc\httpd.conf
To change the connection port number on the Interstage Management Console, change the value defined for the following item in the above file:
Port 12000
Customizing SSL Encrypted Communication for the Interstage
Management Console
The option to use SSL encrypted communication in operation of the Interstage Management Console can be selected using "Select operation mode" during installation of Interstage.
If the operation mode selected during installation is to be changed after installation, the environment must be customized according to the procedure shown below.
If the following change is made, the "Interstage Management Console" shortcut registered in the Windows start menu is disabled. The URL registered in the Windows start menu must be changed. Example
To change "Enable SSL encrypted communication" to "Disable SSL encrypted communication" Before change: https://localhost:12000/IsAdmin
After change: http://localhost:12000/IsAdmin
If SSL encrypted communication is not used, security vulnerability such as interception of
communication data must be taken into account. If security problems are anticipated, take proper measures such as enabling SSL encrypted communication.
Enabling SSL Encrypted Communication
If SSL encrypted communication was disabled during installation of Interstage, but you now want to use SSL encrypted communication, follow the procedure below:
Enter the cmcrtsslenv Command
Define a certificate/key management environment.
"OS-install-folder\Program Files\Common Files\Fujitsu
Shared\F3FSSMEE\cmcrtsslenv.exe" -ed interstage-install-folder\gui\etc\cert
Edit the Interstage HTTP Server Definition File
Edit the Interstage HTTP Server definition file for the Interstage Management Console. The definition file to be edited is as follows:
Interstage-install-folder\gui\etc\httpd.conf Edit the file as follows:
# ---- Configuration for SSL --- AddModule mod_ihs_ssl.c SSLEnvDir "[ Interstage-install-folder]/gui/etc/cert" SSLSlotDir "[ Interstage-install-folder]/gui/etc/cert/slot" SSLTokenLabel SSLTOKEN SSLUserPINFile "[ Interstage-install-folder]/gui/etc/cert/sslssl" SSLExec on SSLVersion 2-3 SSLVerifyClient none #SSLCipherSuite RC4-MD5:RC2-MD5:EXP-RC4-MD5:RSA-RC4-MD5:RSA-RC4-SHA:RSA-EXPORT-RC4-MD5 SSLCertName SSLCERT #SSLClCACertName cli01
Restart the Interstage HTTP Server for the Interstage Management Console
Restart the following service:
"Interstage Operation Tool(FJapache)"
Disabling SSL Encrypted Communication
If SSL encrypted communication was enabled during installation of Interstage, but you now want to disable SSL encrypted communication, follow the procedure below:
Edit the Interstage HTTP Server Definition File
Edit the Interstage HTTP Server definition file as follows: Before
AddModule mod_ihs_ssl.c SSLEnvDir "[Interstage-install-folder]/gui/etc/cert" SSLSlotDir "[Interstage-install-folder]/gui/etc/cert/slot" SSLTokenLabel SSLTOKEN SSLUserPINFile "[interstage-install-folder]/gui/etc/cert/sslssl" SSLExec on SSLVersion 2-3 SSLVerifyClient none #SSLCipherSuite RC4-MD5:RC2-MD5:EXP-RC4-MD5:RSA-RC4-MD5:RSA-RC4-SHA:RSA-EXPORT-RC4-MD5 SSLCertName SSLCERT #SSLClCACertName cli01 After # ---- Configuration for SSL --- #AddModule mod_ihs_ssl.c #SSLEnvDir "[Interstage-install-folder]/gui/etc/cert" #SSLSlotDir "[Interstage-install-folder]/gui/etc/cert/slot" #SSLTokenLabel SSLTOKEN #SSLUserPINFile "[Interstage-install-folder]/gui/etc/cert/sslssl" #SSLExec on #SSLVersion 2-3 #SSLVerifyClient none #SSLCipherSuite #RC4-MD5:RC2-MD5:EXP-RC4-MD5:RSA-RC4-MD5:RSA-RC4-SHA:RSA-EXPORT-RC4-MD5 #SSLCertName SSLCERT #SSLClCACertName cli01
Restart the Interstage HTTP Server for the Interstage Management Console
Restart the following service:
"Interstage Operation Tool(FJapache)"
Changing the Certificate
The certificate used at Interstage installation or by the cmcrtsslenv command is generated by Interstage to use SSL encrypted communication on the Interstage Management Console.
If a certificate issued by an official certification authority such as VeriSign is to be used, the procedure described below must be followed. The certificate generated by Interstage can be used for test operation before service operation or for operation on an intranet.
A certificate issued by a certification authority can also be used for SSL encrypted communication using the Interstage Management Console. In an operating environment connected to an intranet or the Internet, it is recommended to use a certificate issued by a reliable certification authority.
Define an Interstage Certificate Environment
Enter the scsmakeenv command to define an Interstage certificate environment and create a certificate signing request (CSR). For more information, refer to the Security System Guide.
New Password: <---Set a password for the Interstage certificate environment.
This password becomes USER-PIN. Retype:
Input X.500 distinguished names. What is your first and last name? [Unknown]:host.domain.com
What is the name of your organizational unit? [Unknown]:xxxxx
What is the name of your organization? [Unknown]:xxxx
What is the name of your City or Locality? [Unknown]:xxxxxxx
What is the name of your State or Province? [Unknown]:xxxxxxxxx
What is the two-letter country code for this unit? [Un]:JP
Is <CN=host.domain.com, OU=xxxxx, O=xxxx, L=xxxxxxx, ST=xxxxxxxxx, C=JP> correct?
[no]:yes
SCS: Information: scs0101: A certificate signing request (CSR) has been created. <.\csr.txt>
Use the Created CSR to Request that a Certificate be Issued
Use the created CSR to request that a certificate be issued. For details of processing, refer to "Requesting Certificate Issuance" in the "Security System Guide."
Register the CA Certificate (ca-cert.cer) in the Interstage Certificate Environment
The following explanation assumes that the issued SSL server certificate exists in site-cert.cer and that the CA certificate exists in ca.cert.cer.
# scsenter -n CA-Cert -f c:\temp\ca-cert.cer Password:
Certificate was added to keystore
SCS: Information: scs0104: The certificate has been registered.
Register the SSL server certificate (site-cert.cer) in the Interstage certificate environment
The following explanation assumes that the issued SSL server certificate exists in site-cert.cer and that the CA certificate exists in ca.cert.cer.
# scsenter -n IS-Console-SSL-Cert -f c:\temp\site-cert.cer -o Password:
Certificate reply was installed in keystore
SCS: Information: scs0104: The certificate has been registered.
Create a User PIN file for the Interstage HTTP Server
In the user PIN file, specify the password for the Interstage certificate environment.
# ihsregistupin -f [Interstage-install-folder]\gui\etc\cert\upinfile -d [Interstage-install-folder]\etc\security\env\smee\slot
UserPIN: <-- Specify the password for the Interstage certificate environment.
Re-type UserPIN: <-- Specify the password for the Interstage certificate environment.
Edit the Interstage HTTP Server Definition File
Edit the Interstage HTTP Server definition file for the Interstage Management Console as follows: # ---- Configuration for SSL ---
AddModule mod_ihs_ssl.c
SSLEnvDir "C:/Interstage/etc/security/env/smee" <-- Fixed(Modify the Interstage installation folder as needed.)
SSLSlotDir "C:/Interstage/etc/security/env/smee/slot" <-- Fixed(Modify the Interstage installation folder as needed.)
SSLTokenLabel Token01 <-- Fixed
SSLUserPINFile "c:/Interstage/gui/etc/cert/upinfile" <-- User PIN file created by ihsregistupin SSLExec on SSLVersion 2-3 SSLVerifyClient none #SSLCipherSuite RC4-MD5:RC2-MD5:EXP-RC4-MD5:RSA-RC4-MD5:RSA-RC4-SHA:RSA-EXPORT-RC4-MD5 SSLCertName IS-Console-SSL-Cert <-- Nickname of SSL server certificate #SSLClCACertName cli01
Restart the Interstage HTTP Server Definition File for the Interstage Management Console
Restart the following service:
Other Changes
To change the host name of a machine on which Interstage setup is complete, follow the procedure provided in "Moving Resources to Other Servers."
Operating Applications
Defining WorkUnits for Applications
Environment for Executing Applications
A WorkUnit serves as an operating unit for applications. One WorkUnit corresponds to one IJServer. For more information about IJServer, refer to the J2EE User's Guide.
Application Process Multiplicity
Defining the process multiplicity enables the application to process requests received concurrently from clients. Define the process multiplicity in the WorkUnit definition on the Interstage Management Console.
Automatic Restart of Applications
Define automatic restart of applications in the WorkUnit definition on the Interstage Management Console.
For Web applications, define the number of abnormal terminations that occur within a given period. If the number of times an application terminated abnormally reaches the defined number, the WorkUnit terminates abnormally. All application processes in the WorkUnit are stopped and a request being processed in the relevant WorkUnit returns with an error to the client.
If the number of abnormal terminations is not reached within the specified period, the number of abnormal terminations is reset.
Application Time-out
For behavior at time-out occurrence, one of the following modes can be selected: • Forceful termination of an application, and an error message or an exception • An error messages without terminating the application
In either mode, a thread dump is automatically collected when a time-out occurs.
A thread dump is collected into the container information log (info.log). It is output twice, i.e., immediately after, and 10 seconds after, the occurrence of a time-out. If the two thread dumps for a thread show no changes, it indicates that the application running on the thread has a problem.
Current Directory
The current directory of an application process is as follows:
[interstage-install-folder]\J2EE\var\deployment\ijserver\[workunit-name]\current\[workunit-name]\[process-id]
Note:
[Interstage-install-folder] indicates the directory in which Interstage is installed. [workunit-name] is the relevant WorkUnit name.
Environment Variables
The environment variables that need to be used for application processes can be defined in the WorkUnit definition on the Interstage Management Console.
Both the environment variables included in the WorkUnit definition on the Interstage Management Console and system environment variables are valid for application processes running under control of the WorkUnit. If an environment variable included in the WorkUnit definition on the Interstage
Management Console matches one in the system environment variables, the former environment variable takes precedence.
Environment Variables other than PATH and CLASSPATH
Both environment variables included in the WorkUnit definition on the Interstage Management Console and system environment variables are valid.
If an environment variable in the WorkUnit definition matches one in the system environment variables, the former overwrites the value of the latter.
PATH
The value of a path in the WorkUnit definition on the Interstage Management Console is set before the value defined by system environment variable PATH.
CLASSPATH
The value of a classpath in the WorkUnit definition on the Interstage Management Console is set before the value defined by system environment variable CLASSPATH.
Although both values are valid, the value in the WorkUnit definition on the Interstage Management Console is given priority.
Warning Monitoring
This product provides a function that monitors the heap memory utilization by JavaVM and the Perm area to detect a heap shortage and resultant frequent collection of garbage, which leads to the
probability of job response deterioration. The function then notifies the heap area problem as a warning message (EXTP4368), which is output to the event log.
Warning messages are output based on the following standards:
Table 2-1 Output Message Standards
Detail message Meaning of warning Occurrence conditions OutOfMemoryError warning has
occurred because the Perm region is exhausted: TIME={0} SIZE={1}
TIME: Time of occurrence SIZE: Size of the Perm area whose utilization has increased rapidly
OutOfMemory may occur because the utilization of the Perm area has been increasing rapidly.
An increase in the utilization of the Perm area since the previous measurement exceeds 10% of the entire Perm area, and the utilization of the Perm area will exceed 90% if the utilization is assumed to increase at the same rate.
Detail message Meaning of warning Occurrence conditions It takes a long time to do the
garbage collection: TIME={0} AVERAGE={1}
TIME: Time of occurrence SIZE: Mean time for the past three garbage collections
It takes too much time for garbage collection.
The mean time for the past three garbage collections exceeds 5,000 milliseconds.
Inefficient garbage collections are run with the short intervals: TIME={0} WEIGHT={1}
TIME: Time of occurrence WEIGHT: Utilization of old generation immediately before garbage collection
Inefficient garbage collections have occurred at short intervals.
The past three garbage collections have been performed at intervals shorter than 20,000 milliseconds, and the utilization of the old generation heap immediately before a garbage collection is lower than 65%.
The garbage collections are run with the short intervals because of the lack of memory: TIME={0} SIZE={1}
TIME: Time of occurrence SIZE: Heap size that was needed when a warning occurred
Garbage collections have occurred at short intervals because of a memory shortage.
The past three garbage collections have been performed at intervals shorter than 20,000 milliseconds, and the utilization of heap memory immediately after a garbage collection is higher than 65%.
There are possibilities of OutOfMemoryError because of the lack of memory: TIME={0} SIZE={1}
TIME: Time of occurrence SIZE: Heap size that was needed when a warning occurred
OutOfMemory may occur because of a memory shortage.
The utilization of heap memory immediately after a garbage collection exceeds 95%.
Alternatively, the utilization of heap memory
immediately after a garbage collection exceeds 90% and the usage size of the heap has increased from the time of the previous garbage collection. This state has continued for three or more times.
There are possibilities of OutOfMemoryError because of the lack of the Perm region: TIME={0} SIZE={1}
TIME: Time of occurrence SIZE: Perm area size that was
OutOfMemory may occur because of a Perm area shortage.
The utilization of the Perm area exceeds 90%.
Detail message Meaning of warning Occurrence conditions The garbage collections are run
with short intervals: TIME={0} INTERVAL={1}
TIME: Time of occurrence INTERVAL: Garbage collection interval time
Garbage collections have occurred at short intervals.
The past three garbage collections have been performed at intervals shorter than 20,000 milliseconds.
The time information is formatted as:
year/month/day hour:minute:second.millisecond.
If the job is continued after a warning message is output, problems such as memory shortage and degraded response time may occur. To prevent these problems, tune the relevant areas based on the information about insufficient resources provided in warning messages.
The causes of errors that become problems for JavaVM are heap area and Perm area shortages. To prevent these problems, raise the current upper limits by 20% and restart operation. If a warning is still output, raise the upper limits by another 20%. Repeat this tuning until no warning is output. Repeating tuning until no warning message is output can construct a system that runs stably.
To tune the JavaVM heap and Perm areas, set the upper limits of the sizes of the heap and Perm areas in JavaVM options in the WorkUnit definition on the Interstage Management Console.
To set the upper limit of the JavaVM heap area, use the -Xmx option. Example: To set the upper limit of the JavaVM heap area to 256 bytes
-Xmx256m
To set the upper limit of the JavaVM Perm area, use the -XX:MaxPermSize option. Example: To set the upper limit of the JavaVM Perm area to 128 bytes
-XX:MaxPermSize=128m
Perform tuning in the development phase (system test) to solve potential problems in advance.
The methods for increasing the sizes of the heap area and Perm area are explained above. In addition, increasing the process multiplicity of IJServer can also solve problems.
Monitor Screen on Interstage Management Console
The monitor function of the Interstage Management Console can be used to reference JavaVM performance information. This information about the state of JavaVM can be used as reference information for solving the problem indicated in the warning message.
Table 2-2 JavaVM Performance Information
Item Explanation Process serial number Indicates the serial number of a process started by a
WorkUnit.
Process ID Indicates the process ID of JavaVM.
Container type Indicates "1VM," "Web," or "EJB" for the JavaVM container type.
Item Explanation JavaVM heap information (Kbytes) Indicates JavaVM heap information.
Current: Current value of heap information.
Minimum: Minimum value of heap information after JavaVM started.
Maximum: Maximum value of heap information after JavaVM started.
Upper limit: Upper limit of JavaVM heap size. The upper limit is almost the same as the heap size specified by the -Xmx option.
JavaVM Perm area information (Kbytes)
Indicates JavaVM Perm area information. The Perm area contains information in the Java class file.
Current: Current value of Perm area information.
Minimum: Minimum value of Perm area information after JavaVM started.
Maximum: Maximum value of Perm area information after JavaVM started.
Upper limit: Upper limit of JavaVM Perm area size. The upper limit is almost the same as the Perm area size specified by the -XX:MaxPermSize option.
Garbage collection information Indicates information on JavaVM garbage collection. Frequency: Number of times a garbage collection occurred after JavaVM started.
Total processing time (msec): Total processing time for garbage collection after JavaVM started.
Average garbage collection interval (msec): Average interval at which garbage collections have occurred after JavaVM started.
Notes
• If the utilization of the JavaVM heap or Perm area rapidly increases in a short period, a warning monitoring message may not be output. In this case, a message indicating a memory shortage is output to the event log. Take action according to the message.
• If a JavaVM other than the default JavaVM provided by Interstage Application Server V6.0L10 is used, warning monitoring cannot be used. JavaVM Perm area information and garbage collection information on the monitor screen of the Interstage Management Console cannot be used either. The minimum, maximum, and upper limit parameters for JavaVM heap information (Kbytes) are those at the time of recollection of status information.
• If a JavaVM other than the default JavaVM provided by Interstage Application Server V6.0L10 is used, the following types of information are always indicated as 0 on the monitor screen of the Interstage Management Console:
− Frequency, total processing time (msec), and average garbage collection interval (msec) parameters for garbage collection information
• If Interstage Application Server Plus Developer V6.0 is used, warning monitoring cannot be used. JavaVM Perm area information and garbage collection information on the monitor screen of the Interstage Management Console cannot be used either. The minimum, maximum, and upper limit parameters for JavaVM heap information (Kbytes) are those at the time of recollection of status information.
Starting and Stopping WorkUnits
Specify [WorkUnit] in the left frame on the Interstage Management Console. Next, select the name of the WorkUnit to be started from the WorkUnit name list in the right frame, then click the start or stop button.
For more information, refer to Help on the Interstage Management Console.
Start Time Monitoring
The time to wait until completion of WorkUnit startup can be specified. Start processing may hang or delay because of a problem in the start-time execution class or during init processing. If this occurs during the WorkUnit startup wait time, the process can forcibly be terminated to cancel start processing. The default WorkUnit startup wait time is 180 seconds. If needed, change it in the WorkUnit
environment definition from the Interstage Management Console. If you don’t want to cancel processing until start processing is complete, specify 0 for the WorkUnit startup wait time.
If the WorkUnit fails to start up after the startup wait time elapses, a thread dump is automatically collected.
A thread dump is collected into the container information log (info.log). It is output twice, i.e.,
immediately after, and 10 seconds after, the occurrence of a time-out. The cause of the error can be investigated based on changes between the two thread dumps.
Stop Time Monitoring
The time between completion of the WorkUnit forced process stop after initiation of WorkUnit forced process stop can be specified. If the forced process stop operation hangs during the WorkUnit forced process stop wait time, the process can forcibly be terminated to cancel stop processing.
The default WorkUnit forced process stop wait time is 180 seconds. If needed, change it in the WorkUnit environment definition from the Interstage Management Console. If you don’t want to cancel processing until stop processing is complete, specify 0 for the WorkUnit forced process stop wait time. If the WorkUnit fails to start up after the forced process stop wait time elapses, a thread dump is automatically collected.
A thread dump is collected into the container information log (info.log). It is output twice, i.e.,
immediately after, and 10 seconds after, the occurrence of a time-out. The cause of the error can be investigated based on changes between the two thread dumps.
Notes
This function is effective for forcibly terminating the WorkUnit.
When an ordinary WorkUnit stop operation is performed from the Interstage Management Console, the stop sequence may not be finished in 60 seconds. In this case, an error return occurs on the Interstage Management Console while stop processing continues. After some time, re-collect status information to check whether stop processing is complete. If stop processing is still not complete, it can be stopped forcibly.
Performance Monitoring
The Performance Monitoring Tool includes the function that obtains the performance information for the EJB application (for an old version compatible environment) operating on the business server and Light EJB container (for an old version compatible environment), or IJServer EJB container.
The Performance Monitoring Tool supports the following two functions. • Function of outputting log information to the performance log file
This function collects the performance information of specified objects in the performance log file. The accumulated performance information can be output in CSV format using the report output command.
• Function of monitoring the performance information in real time by a Network Control Manager (Monitoring by MIB)
By using the MIB (*2) monitoring function of a Network Control Manager such as Systemwalker
CentricMGR (*1), the performance information of the specified object can be displayed and monitored in real time.
Displaying and monitoring performance information using a Network Control Manager is called “real-time monitoring”.
Note
Performance information on IJServer type IJserver (Web + EJB [1VM]) and IJserver (Web only) cannot be obtained.
This section describes how to issue commands on the application server, and display performance information when using Systemwalker CentricMGR as a Network Control Manager.
*1) Network Control Manager is a software program for displaying and monitoring performance information on the monitor server.
*2) MIB is the abbreviation of the Management Information Base. MIB is a management information area that has been defined for managing the system and TCP/IP information.
The Performance Monitoring Tool consists of the performance monitoring logger that collects performance information, and various commands.
The Performance Monitoring Tool
The Performance Monitoring Tool provides the commands shown in Figure 3-1 (Windows) and 3-2 (Solaris OE).
Figure 3-2 Performance Monitoring Tool Commands
ispmakeenv command: Creates the performance monitoring environment and starts the performance
monitoring logger
ispdeleteenv command : Deletes the performance monitoring environment and stops the performance
monitoring logger
ispstart command : Starts monitoring performance ispstop command : Stops monitoring performance
ispstatus command : Displays performance monitoring status information. ispreport command : Outputs the performance log file report
ispsetagt command and ispunsetagt command: Registers and unregisters Performance Monitoring Tool
in SNMP service
Performance monitoring logger: Collects performance monitoring information, reports performance information to the Network Control Manager, and creates performance log files.
Functions of the Performance Monitoring Tool
This section describes the functions of the Performance Monitoring ToolFunction of Outputting Log Information to the Performance Log File
This function collects the performance information of specified objects in the transaction applications and the wrapper in the performance log file. The performance information is collected at the interval specified when creating a performance monitoring environment.
Since the accumulated performance information can be output in CSV format by executing the report output command, it is useful in the analysis of the performance information and the accumulation of statistical information.
These data items enable detailed performance analysis. The following information can be collected with this function.
EJB application (for an old version compatible environment), Light EJB container (for an old version compatible environment), or IJServer EJB container
Data collection start date
Date the performance information measurement for the record was started
Data collection start time
Time the performance information measurement for the record was started
Data collection end date
Date the performance information measurement for the record was finished
Data collection end time
Time the performance information measurement for the record was finished
EJB application name (For EJB application)
EJB application name. (Max 256 bytes)
Light EJB container name (For Light EJB container)
Light EJB container name/EJB application name. (Max 288 bytes)
IJServer name/EJB application name (for IJServer EJB container)
IJServer name/EJB application name (Max 288 bytes)
Method name + signature
Process ID
The process ID of the server application
Thread ID
ID of a thread in which the method to be monitored operates
Request Processing Time (maximum/average/minimum)
Time (in milliseconds) required for performing the method indicated under "Method name" in the thread indicated by "Thread ID." This value is used for evaluating a pair of method and signature.
Request Processing Wait Time (maximum/average/minimum)
Time (in milliseconds) from receiving a request from a client to starting the method operation. This value is used for evaluating each EJB application, Light EJB container or EJB container of IJServer. This value is not collected if the EJB application, Light EJB container or EJB container of IJServer is a message-driven bean.
Number of Times the Operation has been Executed
Maximum number of requests that wait for being processed by an EJB application, Light EJB container or EJB container of IJServer.
This value is used for evaluating each EJB application, Light EJB container or EJB container of IJServer. This value is not collected if the EJB application, Light EJB container or EJB container of IJServer is a message-driven bean.
Number of processes
Number of the method operations in the thread indicated by "Thread ID." This value is used for evaluating a pair of method and signature.
Number of Requests Received
Accumulated number of the EJB application, Light EJB container or EJB container of IJServer operations from the start of performance monitoring. This value is used for evaluating each EJB application, Light EJB container or EJB container of IJServer.
Number of EJB object (Session)
The number of the current EJB objects is output. The number of EJB objects is the difference between the number of executed create methods and executed remove methods. The output value is the maximum value within the interval time. This value is used for evaluating each EJB application, Light EJB container or EJB container of IJServer.
This value is not collected if the EJB application, Light EJB container or EJB container of IJServer is a message-driven bean.
Passivate number for Entity(maximum)
Number of instance pooling in the EJB application, Light EJB container (process) or EJB container of IJServer. The output value is the maximum value within the interval time. This value is used for evaluating each EJB application, Light EJB container or EJB container of IJServer.
Size of memory area used in VM(maximum/average)
Size (in kilobytes) of memory area used in VM for the EJB application, Light EJB container or EJB container of IJServer. This value is used for evaluating each EJB application, Light EJB container or EJB container of IJServer.
Function of Monitoring the Real Time Performance Information by a Network Control
Manager (Monitoring by MIB)
The real time monitoring function reports the performance information of the specified objects of the transaction applications and the wrapper as MIB information (*).
This function can only use the Windows (R) version and the Solaris OE version.
A Network Control Manager such as Systemwalker CentricMGR supports the MIB monitoring function. By using the function of the Network Control Manager, the following operation can be performed.
Outputting the Report of the Statistical Information
The performance information can be displayed in graph or CSV format. It is useful in the collection of statistical information.
Monitoring the Performance Abnormality
By setting the threshold value for performance information such as "Number of requests awaiting processing" and monitoring it, any abnormality in performance information can be detected in advance. This function enables prompt response to abnormal events.
* Stands for Management Information Base. In order to manage system information and TCP/IP information, the MIB is the defined management information domain.
When this function is used, the information can also be output to the performance log file at the same time. For a more detailed performance analysis such as information in units of operations, analyze the information collected in the performance log file.
For the monitoring method using MIB information, refer to the manual of the Network Control Manager. The following information can be collected with this function.
EJB application (for an old version compatible environment), Light EJB container (for an old version compatible environment), or IJServer EJB container
EJB application name (For EJB application)
The name of EJB application.
Light EJB container/EJB application name(For Light EJB container)
Light EJB container/EJB application name
IJServer name/EJB application name (for IJServer EJB container)
IJServer name/EJB application name (Max 288 bytes)
Request Processing Wait Time (maximum/average/minimum)
The time between the acceptance of a request from a client application, and the actual start of processing.
Number of Requests Awaiting Processing
The maximum number of requests that were placed in the EJB application.
Number of Requests Received
The accumulation value of the number of times by which the EJB application concerned or the Light EJB container was processed from the time of a performance monitoring start.
Performance Monitoring Procedure
The flow of the Windows (R) version
To monitor and analyze the performance of Interstage job applications using the Performance Monitoring Tool, the five phases that must be performed are:
1. Registering in the SNMP service
2. Starting the Performance Monitoring Tool 3. Monitoring
4. Stopping the Performance Monitoring Tool 5. Deleting from the SNMP service.
Each phase is explained in below.
1) Registering to the SNMP Service
Register the Performance Monitoring Tool in the SNMP service. Registers Interstage in the SNMP service.
2) Starting the Performance Monitoring Tool
Perform this operation to start the Performance Monitoring Tool.
Figure 3-4 Starting the Performance Monitoring Tool 3) Monitoring Operation
Perform this operation to measure, monitor, and analyze performance information.
Notes
• Performance monitoring can be stopped by executing the ispstop command instead of stopping the application. However, performance information will not be measured after the ispstop command is executed. To restart measuring performance information, execute the ispstart command.
• After the ispmakeenv command is executed, start the business application (WorkUnit) that
measures the performance. The performance of the business applications that are started before the execution of the ispmakeenv command are not measured.
• When a Network Control Manager such as Systemwalker CentricMGR is used to display performance information in real time, do not start or stop performance monitoring while
performance information is being displayed. Be sure to close the performance information display screen before starting performance monitoring, and perform real-time monitoring operation and display performance information after performance monitoring is started.
4) Stopping the Performance Monitoring Tool
Perform this operation to stop the Performance Monitoring Tool.
Figure 3-6 Stopping the Performance Monitoring Tool
Note
To create the performance monitoring environment again, first restart Interstage.
5) Deletion from the SNMP Service
Perform this operation when uninstalling Interstage.
Delete the Performance Monitoring Tool registered in the SNMP service.
The flow of the Solaris OE version
To monitor and analyze the performance of Interstage job applications using the Performance
Monitoring Tool, the four phases of registering in the SNMP service, starting the Performance Monitoring Tool, monitoring, and stopping the Performance Monitoring Tool must be performed. Each phase is explained in below.
1) Registering to SNMP service
Perform this operation when installing INTERSTAGE.
Register the Performance Monitoring Tool in the SNMP service.
Figure 3-8 Installation Procedure 2) Starting the Performance Monitoring Tool
Perform this operation to start the Performance Monitoring Tool.
3) Monitoring Operation
Perform this operation to measure, monitor, and analyze performance information.
Figure 3-10 Monitoring Operation
Note
• Performance monitoring can be stopped by executing the ispstop command instead of stopping the application. However, performance information will not be measured after the ispstop command is executed. To restart measuring performance information, execute the ispstart command.
• After the ispmakeenv command is executed, start the business application (WorkUnit) that
measures the performance. The performance of the business applications that are started before the execution of the ispmakeenv command is not measured.
• When a Network Control Manager such as Systemwalker CentricMGR is used to display performance information in real time, do not start or stop performance monitoring while
performance information is being displayed. Be sure to close the performance information display screen before starting performance monitoring, and perform real-time monitoring operation and display performance information after performance monitoring is started.
4) Stopping the Performance Monitoring Tool
Perform this operation to stop the Performance Monitoring Tool.
Figure 3-11 Stopping the Performance Monitoring Tool
Note
In order to create the performance monitoring environment again, restart Interstage before creating the performance monitoring environment.
Registering to the SNMP Service
After Interstage is installed, the following operation is required to perform real-time monitoring with a Network Control Manager such as Systemwalker CentricMGR. If real-time monitoring is not to be performed, the following operation need not be performed.
1) Registering in the SNMP Service
Execute the ispsetagt command to register the Performance Monitoring Tool in the SNMP service. After executing the ispsetagt command, re-start the SNMP service from the "Service" screen in Windows. The Performance Monitoring Tool can be registered in the SNMP service only when the SNMP service has been installed. Before executing the ispsetagt command, install the SNMP service.
The SNMP service is installed in Windows NT® and Windows® 2000 SNMP in the following way:
Windows NT®
• Insert the CD-ROM of the OS into the CD drive.
• Add the SNMP service with "Network" in the control panel.
• After adding the SNMP service, re-install the same version of Service Pack as the one that has already been installed.
Windows® 2000
• Insert the CD-ROM of the OS into the CD drive.
2) Copying the Performance Monitoring Tool
Copy the Performance Monitoring Tool files shown in the following tables to the indicated directories in order to enable the Network Control Manager to display performance information. Copy these files during Interstage installation. Reboot the machine when the files have been copied.
a. For Solaris 7 OE
Filename Copy source directory Copy destination directory
ispsubad7 TD_HOME/isp/lib /usr/lib/snmp
ispsuba7.acl /etc/opt/FSUNtd/snmp/conf /etc/snmp/conf ispsuba7.reg /etc/opt/FSUNtd/snmp/conf /etc/snmp/conf ispsuba7.rsrc /etc/opt/FSUNtd/snmp/conf /etc/snmp/conf b. For Solaris 8 OE and Solaris 9 OE
Filename Copy source directory Copy destination directory
ispsubad8 TD_HOME/isp/lib /usr/lib/snmp
ispsuba8.acl /etc/opt/FSUNtd/snmp/conf /etc/snmp/conf ispsuba8.reg /etc/opt/FSUNtd/snmp/conf /etc/snmp/conf ispsuba8.rsrc /etc/opt/FSUNtd/snmp/conf /etc/snmp/conf TD_HOME: Component Transaction Service installation directory
Note
When using the real-time monitoring function of the performance monitoring tool, the mandatory software must be installed and the mandatory patch must be applied. Refer to the Installation Guide for details about the mandatory software and patch.
3) Reading the MIB Definition File
To collect performance information from the Network Control Manager, the MIB definition file for performance information must be read using the Network Control Manager. Have the Network Control Manager read the MIB definition file from the machine in which Interstage has been installed, as follows: • When the Network Control Manager operates under Windows NT®/Windows® 2000
Read TD_HOME\isp\mib\ispmibNT.my
• When the Network Control Manager operates under Solaris OE Read TD_HOME\isp\mib\ispmibSol.my.
When using the Windows NT®/Windows® 2000 version of Systemwalker CentricMGR (operation management server), read the MIB definition file as follows:
• Use FTP or a similar application to copy the MIB definition file from the machine in which Interstage is installed to the machine in which Systemwalker CentricMGR is installed.
• Activate Systemwalker CentricMGR System Monitor.
• Choose Tools and then Extend MIB from the System Monitor screen to display the Extend MIB screen.
• Click the add button on the MIB Extension Operation screen to display the Select of Extend MIB File Selection screen.
• Select the MIB file from the Extension MIB File Selection screen and click the Open button. Then, click the Close button on the MIB Extension Operation screen.
When using the Solaris OE version of Systemwalker CentricMGR, read the MIB definition file as follows: • Use FTP to copy the MIB definition file from the machine in which INTERSTAGE is installed to the
job management client in which Systemwalker CentricMGR is installed. • Activate Systemwalker CentricMGR (Job Monitor).
• Choose Tools and then Extend MIB from the Job Monitor screen to display the MIB Extension Operation screen.
• Click the add button on the MIB Extension Operation screen to display the Extend MIB File Selection screen.
• Select the MIB file from the Extend MIB File Selection screen and click the Open button. Then, click the Close button on the MIB Extension Operation screen.
• Choose Policy then Distribute policy from the Job Monitor screen to display the Policy Distribution screen.
• Set the required items in the Policy Distribution screen, then click the OK button.
4) Setting the Port Number
The Performance Monitoring Tool uses a communications port to post performance information to the Network Control Manager. The default port number is 7042. If this port number is used by other
Use the following procedure to change the port number: (1) Use an editor to open the environment settings file.
Under Solaris 7 OE, the environment settings file is /etc/snmp/conf/ispsuba7.reg. This will be displayed as follows: agents = { { name = "ispsubad7" subtrees = { isPerformanceInf } timeout = 40000000 watch-dog-time = 2000000 port = 7042 } }
Under Solaris 8 OE and Solaris 9 OE, the environment settings file is /etc/snmp/conf/ispsuba8.reg. This will be displayed as follows:
agents = { { name = “ispsubad8” subtrees = { isPerformanceInf } timeout = 40000000 watch-dog-time = 2000000 port = 7042 } }
(2) Replace the “7042” part of “port = 7042” with an unused port number. (3) Save the file and close the editor.
(4) Restart the system.
System Configuration Setting
The system configuration information shown below must be modified in the system configuration information file before the performance monitoring environment is created and the Performance Monitoring Tool is started. After the modifications are made, reboot the system.
Semsys:seminfo_semmnu
Always estimate the values to be set in the above system configuration information before starting the Performance Monitoring Tool. If the estimation suggests that the settings do not need to be changed, the system configuration information need not be set again.
Refer to the Environment information in the Tuning Guide for details of how to estimate the values to be set.
Creating a Performance Monitoring Environment
Starting Operation of Performance Monitoring Tool
This section describes the construction of the environment for using the performance monitoring tool.
Starting Interstage
Execute the isstart command to start Interstage.
Creating the Performance Monitoring Environment
Use the ispmakeenv command to create a performance monitoring environment and activate the Performance Monitoring Tool.
In this case, the following two interval times are specified. • Interval time for performance log file
The interval at which the performance information is output to the performance log file. The interval can be 5, 10, 20, or 30 minutes or 1, 2, 3, or 4 hours. The default is one hour.
• Interval time for real time monitoring
The interval for collecting the performance information to be notified to the Network Control Manager. Specify the interval time when performance monitoring is executed from the Network Control Manager. The interval can be specified between 1 and 60 minutes. The default is 5 minutes.
After the command ispmakeenv is executed, start the business application (WorkUnit) that measures the performance. Performance of the business applications that are started up before execution of the
Monitoring Operations
This section describes the monitoring operation with the performance monitoring tool.
Starting Performance Monitoring
Start performance monitoring of the specific object with the ispstart command. From then on, the performance information is output to the performance log file at the interval specified in the performance monitoring tool automatic start definition file (Windows(R) Enterprise Edition or Standard Edition only) or
ispmakeenv command.
Performance information is collected until it is stopped by the ispstop command. These commands are shown in Figure 3-12.
Figure 3-12 Starting and Terminating Performance Monitoring
Starting a Business Application
Execute the isstartwu command to start the WorkUnit.
Real-time Monitoring
To display and monitor performance information using a Network Control Manager such as
Systemwalker CentricMGR, use the following procedure to display performance information on the Network Control Manager screen. This procedure is an overview of real-time monitoring operation when the Windows version of Systemwalker CentricMGR operation management server is used. When using a Network Control Manager other than Systemwalker CentricMGR, refer to the user’s guide for the Network Control Manager to be used.
1. Activate Systemwalker CentricMGR System Monitor. 2. Select the Application Server to be Monitored
Click the application server name to be monitored on the System Monitor screen. 3. Display the Get MIB Data screen
Choose Tools | Specific System | Get/Set MIB Data | Get MIB Data on the System Monitor screen menu to display the Get MIB Data screen.
