Interstage Application Server V6.0 Operator's Guidesoftware.fujitsu.com/jp/manual/fm_e/b23j32k08/0610m02/01/np_isg.pdf · Sun, Solaris, Java, and other trademarks ... This document

Interstage Application Server

V6.0 Operator's Guide

Operator's Guide

ii

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

iii

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

• Linux

Operator's Guide - Preface

iv

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 This appendix explains linkage with Systemwalker.

v

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

Operator's Guide - Table of Contents

vi

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 Component Transaction Service Resource File ...................................................................4-9 Database Linkage Service Resource File ..........................................................................4-10


vii

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


viii

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

Resource Restore/Import.........................................................................................................4-95 Stopping the Service...........................................................................................................4-97


ix

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


x

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 Activity Monitoring by Systemwalker CentricMGR Linkage...........................................................G-4


xi

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

Index


xii

1-1

Chapter 1 Interstage Operation Using the Interstage Management Console

This chapter explains Interstage operation using the Interstage Management Console.

Chapter 1: Interstage Operation Using the Interstage Management Console

1-2

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

1-3

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 Management Console.


1-4

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

1-5

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.


1-6

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.


1-7

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 as follows:

Before # ---- Configuration for SSL ---


1-8

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


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. # scsmakeenv -n IS-Console-SSL-Cert -f c:\temp\csr.txt -c


1-9

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


1-10

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 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


Other Changes

1-11

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."


1-12

2-1

Chapter 2 Operating Applications

This chapter describes how to operate applications using WorkUnits

Chapter 2 : Operating Applications

2-2

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.

[process-id] is the process ID of the relevant application process.


2-3

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.


2-4


It takes a long time to do the garbage collection: TIME={0} AVERAGE={1}


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}


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}


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}


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}


SIZE: Perm area size that was needed when a warning occurred

OutOfMemory may occur because of a Perm area shortage.

The utilization of the Perm area exceeds 90%.


2-5


The garbage collections are run with short intervals: TIME={0} INTERVAL={1}


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.

JavaVM operation time (msec) Indicates the time during which JavaVM has been running.


2-6

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:

− Current, minimum, and maximum parameters for JavaVM Perm area information (Kbytes)

Starting and Stopping WorkUnits

2-7

− 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.


2-8

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.

3-1

Chapter 3 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.

Chapter 3: Performance Monitoring

3-2

The Performance Monitoring Tool The Performance Monitoring Tool provides the commands shown in Figure 3-1 (Windows) and 3-2 (Solaris OE).

Figure 3-1 Performance Monitoring Tool Commands

The Performance Monitoring Tool

3-3

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.


3-4

Functions of the Performance Monitoring Tool This section describes the functions of the Performance Monitoring Tool

Function 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

Name of method to be monitored and signature (type of method argument and return value)


3-5

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.


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.


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.


3-6

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 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 Time (maximum/average/minimum)

The processing time for the EJB application, Light EJB container or EJB container of IJServer.


3-7

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.

Figure 3-3 Installation Procedure


3-8

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.

Figure 3-5 Monitoring Operation


3-9

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.

Figure 3-7 Deleting the Performance Monitoring Tool


3-10

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.

Figure 3-9 Starting the Performance Monitoring Tool


3-11

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.


3-12

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.

• Add the SNMP service with "Management and Monitor Tool" in the "Windows component wizard."


3-13

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-14

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 programs, change the Performance Monitoring Tool port number during Interstage installation. Then, reboot the system.


3-15

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.


3-16

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 ispmakeenv command are not measured.


3-17

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.


3-18

4. Display the List of Object Names and Check the Instance Number of the Object to be Monitored Make the following settings on the Get MIB Data screen and click the Retrieve button. − Choose Not check Polling Interval.

− Specify DUMP as the Request Type.

− Specify “ispSumObjectName” in the MIB (performance information measurement item) to be displayed.

Specify the MIB according to the following procedure:

Click the Browse button to display the MIB Tree screen.

On the MIB Tree screen, expand the tree structure by double-clicking the options internet, private, enterprises, fujitsu, application, aplNetWork, aplNetFunction, aplInterstage, isPerformanceinf, ispSummaryTable, and ispSummaryTableEntry in that order. The performance information items that can be displayed in real-time monitoring will appear on the display. Click ispSumObjectName.

Click the Add button on the Get MIB Data screen.

5. Set the Reference Value

− On the System Monitoring screen, choose Policy | Setting Policy | Node | MIB State change to display the MIB State Change screen.

− Click the Add button on the MIB State Change screen to display the Threshold Details screen.

− Specify the MIB name (the display item name of the performance information to be monitored), instance number, and threshold value (reference value) on the Threshold Details screen. See Step 4) for how to specify the MIB name.

− Choose On on the MIB Monitoring screen.

6. Display the Real-time Display Screen (Performance Information) Make the following settings and click the Retrieve button. − Set the polling time to 5 minutes or more.

− Specify GET as the Request Type.

− Specify the instance number of the object to be monitored.

When the list of object names is displayed, the following number appears. Specify this number as the instance number.

“ispSumObjectName : “ispSumObjectName. number: object-name”

− Specify the display item name of the performance information to be displayed in the MIB Name field. See Step 4) for how to specify the MIB name.

1. Activate Systemwalker CentricMGR (Job Monitor).

2. Select the Application Server to be Monitored Choose Monitor for Select function on the Job Monitor screen, and choose Node list for Select tree. A job server list will be displayed. Click the name of the job server to be monitored.


3-19

3. Display the Get MIB Data screen Choose Tools | Specific Object | Get/Set MIB Data | Get MIB Data on the Job Monitor screen menu to display the Get MIB Data screen.

4. Display the List of Object Names and Check the Instance Number of the Object to be Monitored Make the following settings on the Get MIB Data screen and click the Retrieve button. − Choose Not check Polling Interval.

− Specify DUMP as the Request Type.

− Specify “ispSumObjectName” in the MIB (performance information measurement item) to be displayed.

Specify the MIB according to the following procedure:

Click the Browse button to display the MIB Tree screen.

On the MIB Tree screen, expand the tree structure by double-clicking the options internet, private, enterprises, fujitsu, application, aplNetWork, aplNetFunction, aplInterstage, isPerformanceinf, ispSummaryTable, and ispSummaryTableEntry in that order. The performance information items that can be displayed in real-time monitoring will appear on the display. Click ispSumObjectName.

Click the Add button on the Get MIB Data screen.

5. Set the Reference Value

− On the Job Monitor screen, choose Policy | Setting Policy | Node | MIB State change to display the MIB State Change screen.

− Click the Add button on the MIB State Change screen to display the Threshold Details screen.

− Specify the MIB name (the display item name of the performance information to be monitored), instance number, and threshold value (reference value) on the Threshold Details screen. See Step 4) for how to specify the MIB name.

− Choose On on the MIB Monitoring screen.

6. Display the Real-time Display Screen (Performance Information)

Make the following settings and click the Retrieve button.

− Set the polling time to 5 minutes or more.

− Specify GET as the Request Type.

− Specify the instance number of the object to be monitored.

When the list of object names is displayed, the following number appears. Specify this number as the instance number.

“ispSumObjectName : “ispSumObjectName. number: object-name”

− Specify the display item name of the performance information to be displayed in the MIB Name field. See Step 4) for how to specify the MIB name.

Table 3-1 shows the performance information items that can be displayed in real-time monitoring. The display item name in this table means the item name of the performance information displayed by the Network Control Manager.


3-20

Table 3-1 Performance Information Items

Performance Information Item Name

Unit Display Item Name Meaning

Object name - IspSumObjectName Object name of the application for which performance information is measured

Maximum request processing time

ms IspSumExecTimeMax Maximum processing time (within a polling time) required for processing the object

Minimum request processing time

ms IspSumExecTimeMin Minimum processing time (within a polling time) required for processing the object

Averaged request processing time

ms IspSumExecTimeAve Averaged processing time (within a polling time) required for processing the object

Maximum request processing wait time

ms IspSumWaitTimeMax Maximum time (within a polling time) from the time of a client request to the initiation of a server application

Minimum request processing wait time

ms IspSumWaitTimeMin Minimum time (within a polling time) from the time of a client request to the initiation of a server application

Averaged request processing wait time

ms IspSumWaitTimeAve Averaged time (within a polling time) from the time of a client request to the initiation of a server application

Number of requests received

Number IspSumRequestNum Accumulated number of processes from the time of starting the performance monitoring up to the timing of this object.

Number of requests awaiting processing

Number IspSumWaitReqNum Maximum number of requests waiting for processing of this object, within the polling time.

Note

1. Unless the list of object names is to be displayed, always specify “GET” as the acquisition method when displaying performance information. If DUMP is specified for real-time display, an enormous amount of communications may be required between Systemwalker CentricMGR and the Performance Monitoring Tool, resulting in a heavy load on the network as well as on the application server.

2. When there is no object for which performance information can be displayed, “NONE” will be displayed as the object name.


3-21

Outputting the Performance Log File and Analyzing the Performance Information

When the threshold value is exceeded during real-time monitoring and there is a possibility of performance abnormality analyze the detailed information saved as the performance log file.

Use the ispreport command to output a performance log file report. This command converts the performance information saved as the performance log file into CSV format and outputs it to the standard output. If the performance log file is to be converted into CSV format and output as a file, specify the output destination file name as below when executing the ispreport command.

“ispreport option > output-destination-file-name”

When the ispreport command is executed, performance information in the performance log file will be converted one record at a time and output to the standard output in the following format.

1) Line format

“D1,D2,D3, D4,D5,D6, D7,D8,D9, D10,D11,D12,D13, D14,D15,D16,D17,D18,D19,D20,D21”

2) Output items in each line

Table 3-2 shows a list of output items in each line. Items D1 to D21 in the “Item No.” column correspond to those shown in 1).

For EJB application

Table 3-2 Output Items

Item No. Performance Information Item Name

Unit Meaning

D1 Data collection start date - Date the performance information measurement for the record was started

D2 Data collection start time - Time the performance information measurement for the record was started

D3 Data collection end date - Date the performance information measurement for the record was finished

D4 Data collection end time - Time the performance information measurement for the record was finished

D5 For an EJB application:

EJB application name

For Light EJB container:

Light EJB container name/EJB application name

- EJB application name, or Light EJB container name / EJB application name by which performance information is measured.

D6 Method name + signature - Name of method to be monitored and signature (type of method argument and return value).

D7 Process ID - Process ID of the EJB application for which performance information is being measured.


3-22


Unit Meaning

D8 Thread ID - ID of a thread in which the method to be monitored operates.

D9 Maximum request processing time

ms Maximum processing time of the method to be monitored in the thread within the interval time

D10 Minimum request processing time

ms Minimum processing time of the method to be monitored in the thread within the interval time

D11 Averaged request processing time

ms Averaged processing time of the method to be monitored in the thread within the interval time

D12 Maximum request processing wait time

ms Maximum wait time for processing from receiving a request from a client application to starting the method processing within the interval time

0 is always output if the EJB application or Light EJB container is a message-driven Bean.

D13 Minimum request processing wait time

ms Minimum wait time for processing from receiving a request from a client application to starting the method processing within the interval time.


D14 Averaged request processing wait time

ms Averaged wait time for processing from receiving a request from a client application to starting the method processing within the interval time.


D15 Number of processes Number Number of operations of the method to be monitored in the thread within the interval time

D16 Number of requests received Number Accumulated number of operations of the EJB application or Light EJB container within the interval time.

D17 Number of requests awaiting processing

Number Accumulated number of operations of the EJB application or Light EJB container within the interval time



3-23


Unit Meaning

D18 Number of EJB object (Session)

Number Number of the current EJB objects (difference between the executed create methods and executed remove methods)

D19 Maximum Passivate number for Entity

- Maximum number of instance pooling in the EJB application or Light EJB container (process) within the interval time

D20 Maximum size of memory area used in VM

K byte Maximum size of memory area used in VM for the EJB application or Light EJB container.

Becomes 0 if the method is not processed within the interval time.

D21 Averaged size of memory area used in VM

K byte Averaged size of memory area used in VM for the EJB application or Light EJB container.


Stopping the Application Execute the isstopwu command to start the WorkUnit.

Stopping the Performance Monitor Performance Monitor is stopped with the ispstop command. When this command is executed, performance information is extracted and output on a performance log file stop.

Deleting the Performance Monitoring Environment This section describes the deletion of the performance monitoring tool.

Deleting the Performance Monitoring Environment

Use the ispdeleteenv command to stop the Performance Monitoring Tool and delete the performance monitoring environment. Delete the performance monitoring environment after performance monitoring has stopped. If you do not do this, performance information will not be collected after the performance monitoring environment is deleted. To restart performance monitoring, create a new performance monitoring environment after restarting Interstage.

Stopping Interstage

Execute the isstop command to stop Interstage.


3-24

Deletion from the SNMP Service

Execute the ispunsetagt command to delete the Performance Monitoring Tool from the SNMP service. After executing the ispunsetagt command, use the Services dialog box to restart the SNMP service. This operation is required only when the Performance Monitoring Tool has been registered in the SNMP service by using the ispsetagt command.

• Windows NT®

Click [SNMP] for "Control Panel" "Services" and then execute [Stop] and [Start].

• Windows® 2000

Click [SNMP Service] for " Administrative Tools" "Services" and then execute [Stop] and [Start].

Analyzing the Performance Information and Taking Action This section describes the method of analyzing the performance information collected in the performance log file and real-time monitoring, as well as the method for taking action.

Real-time monitoring is only available in the Windows (R) version and the Solaris OE version.

Function of Outputting Log Information to the Performance Log File This section describes the performance information that can be collected using the function of outputting log information to the performance log file, the evaluation method, and the method for taking action.


1) Collectable performance information

The function of outputting log information to the performance log file allows the accumulated information to be output in CSV format, by executing the ispreport command.

The performance information is described below.

Line format

“D1,D2,D3, D4,D5,D6, D7,D8,D9, D10,D11,D12,D13, D14,D15,D16.D17,D18,D19,D20,D21”

Output items in each line

Table 3-3 shows a list of output items in each line. Items D1 to D21 in the “Item No.” column correspond to those shown in 1).


3-25

EJB application (21 items)

For outputting the EJB application performance information, add the "-k EJBAPL" option to the ispreport command.



Unit Meaning

D1 Data collection start date - Date the performance information measurement for the record was started

D2 Data collection start time - Time the performance information measurement for the record was started

D3 Data collection end date - Date the performance information measurement for the record was finished

D4 Data collection end time - Time the performance information measurement for the record was finished

D5 For EJB application(for an old version compatible environment):

EJB application name

For Light EJB container(for an old version compatible environment):

Light EJB container name/EJB application name

For EJB container of IJServer:

IJServer name/EJB application name

- EJB application name, Light EJB container name / EJB application name or IJServer name/EJB application name by which performance information is measured.

D6 Method name + signature - Name of method to be monitored and signature (type of method argument and return value)

D7 Process ID - Process ID of the EJB application for which performance information is being measured

D8 Thread ID - ID of a thread in which the method to be monitored operates

D9 Maximum request processing time

ms Maximum processing time of the method to be monitored in the thread within the interval time

D10 Minimum request processing time

ms Minimum processing time of the method to be monitored in the thread within the interval time


3-26


Unit Meaning

D11 Averaged request processing time

ms Averaged processing time of the method to be monitored in the thread within the interval time

D12 Maximum request processing wait time

ms Maximum wait time for processing from receiving a request from a client application to starting the method processing within the interval time

0 is always output if the EJB application, Light EJB container or EJB container of IJServer is a message-driven Bean.

D13 Minimum request processing wait time

ms Minimum wait time for processing from receiving a request from a client application to starting the method processing within the interval time


D14 Averaged request processing wait time

ms Averaged wait time for processing from receiving a request from a client application to starting the method processing within the interval time


D15 Number of processes Number Number of operations of the method to be monitored in the thread within the interval time

D16 Number of requests received Number Accumulated number of operations of the EJB application or Light EJB container within the interval time

D17 Number of requests awaiting processing

Number Accumulated number of operations of the EJB application or Light EJB container within the interval time


D18 Number of EJB object (Session)

Number Number of the current EJB objects (difference between the executed create methods and executed remove methods)

D19 Maximum Passivate number for Entity

- Maximum number of instance pooling in the EJB application or Light EJB container (process) within the interval time


3-27


Unit Meaning

D20 Maximum size of memory area used in VM

K byte Maximum size of memory area used in VM for the EJB application, Light EJB container or EJB container of IJServer .


D21 Averaged size of memory area used in VM

K byte Averaged size of memory area used in VM for the EJB application, Light EJB container or EJB container of IJServer.


The ispreport command outputs the interval time information in units of operations for each process. The output information consists of information for each process in units of operations and in units of objects.

The following is an example of output using the ispreport command.

Example

Example of monitoring the performance of the Light EJB container equipped with one EJB application with multiple methods and EJB applications with multiple methods (for an old version compatible environment).

The examples of performance information output when the performances of the EJB application EJBAPL001 and Light EJB container EJBCONT001 are monitored are shown below. EJBAPL001 has three methods. EJBCONT001 is equipped with one EJB application EJBAPL002 with three methods.


3-28

2) Evaluation and action

Reference each item in the following.

• Evaluation by operation (D8-D10, D14)

D8-D10 and D14 indicate the request processing time for the operation (indicated in D6 for the process indicated in D7) and the number of times the operation has been executed. With this information, a process can be evaluated for each operation.

• Evaluation by object (D11-D13, D15, D16)

D15 and D16 indicate the number of requests received, and the number of requests awaiting processing, for the object indicated in D5. With this information each object can be evaluated.

The methods of evaluating performance information and the actions to be taken are listed in Table 3-4.

If a performance abnormality was detected, take appropriate action using Table 3-4 as a reference.

Table 3-4 Performance Items Details

Item No. Performance Information Details Action

1 In all the time slots when performance monitoring was performed, the maximum request processing time is long and the averaged request processing time is close to the maximum request processing time.

If the request processing time is longer than the target value, one or both of the following causes can be assumed:

- The server application has a performance problem.

- System workload is too high.

Review the server application and system from the above viewpoints.

In a particular time slot, the maximum, minimum, and averaged request processing times are long.

2

In a particular time slot, the maximum, minimum, and average request processing wait times are long

In a particular time slot, system workload is high.

Check the workload status by measuring performance information of other server applications.

Although the maximum request processing time is long, the averaged request processing time is short and close to the minimum request processing time.

3

Although the maximum request processing wait time is long, the averaged request processing wait time is short and close to the minimum request processing wait time.

One or both of the following causes can be assumed:

- System work load have temporarily become high.

- Under a particular condition, the server application has a performance problem.


4 In all the time slots when performance monitoring was performed, the maximum request processing wait time and average request processing wait time are long.

Processing capacity of the server application is insufficient for the number of requests from the client. Take action to increase the processing capacity, such as increasing the process multiplicity in the WorkUnit definition.


3-29


5 In a particular time slot, the number of processes and the number of requests waiting to be processed are high.

In a particular time slot, the number of requests to the server application has increased.

If the processing capacity of the server application is insufficient for the number of requests from the client, take action to increase the processing capacity such as increasing the process multiplicity in the WorkUnit definition.

6 In all the time zones that carried out performance surveillance, the maximum demand processing waiting time and average demand processing waiting time are long.

The throughput of server application is insufficient to the number of demands from a client. Please carry out management which improves the throughput of server application, such as raising the degree of process multiplex by WorkUnit definition.

7 In the specific time zone, the number of processes and the number of the waiting demands for processing have increased.

The number of demands to the server application is increasing in the specific time zone. When the throughput of server application is insufficient to the number of demands from a client, please perform management which improves the throughput of server application, such as raising the degree of process multiplex by WorkUnit definition.

8 Number of EJB objects is larger than the number of client connections.

The number of EJB objects has increased. The remove method may not be executed for a create method.

Reexamine the client application.

9 Number of Passivate is too large. The Entity initial instance counts are insufficient.

Increase the Entity initial instance counts in accordance with the increased number of Passivate.

10 Size of memory area used in VM is too large.

Memory leakage may have occurred.

Reexamine the server application considering whether objects should be deleted or other actions should be taken.

11 Number of requests waiting to be processed is large, but average wait time for request processing is short.

Use the isinfobj command periodically to check the status of waiting queues and loading state within the interval time.


3-30

Performance Information Collected by the Network Control Manager with the Real Time Monitoring Function

This section describes the performance information that can be collected by the real time monitoring function, the method of evaluating it, and the various actions available.

1) Collectable performance information

The types of information that can be collected by using the real-time monitoring function are summarized below.


Performance Information Item Name

Unit Meaning

Object name - Object name of the application for which performance information is measured

Maximum request processing time

ms Maximum processing time within the time required for processing the object

Minimum request processing time

ms Minimum processing time within the time required for processing the object

Averaged request processing time

ms Average processing time within the time required for processing the object

Maximum request processing wait time

ms Maximum time within a poling time from the time of request by the client to the initiation of the server application

Minimum request processing wait time

ms Minimum time from the time of request from by the client to the initiation of the server application

Averaged request processing wait time

ms Average time from the time of request by the client to the initiation of the server application

Number of requests received Number Accumulated number of processes, from the time of starting the performance monitoring to the timing of this object.

Number of requests awaiting processing

Number Maximum number of requests waiting for processing of this object, within the polling time.


3-31

2) Evaluation and action

The method of evaluating the performance information collected with the real time monitoring function, and the method for taking action, are listed in Table 3-6.

If a performance abnormality was detected, take appropriate action using Table 3-6 as reference. Also, use the performance information output to the performance log file as a guide for evaluation.

Table 3-6 Performance Item Details


1 In each of the time slots when performance monitoring is performed, the maximum request processing time is long. The average request processing time is close to the maximum request processing time.

If the request processing time is longer than the target value, one or both of the following causes can be assumed:

- There is a performance problem in the server application

- System workload is too high


In a particular time slot, the maximum, minimum, and average request processing times are long.

2

In a particular time slot, the maximum, minimum, and average request processing wait times are long

In a particular time slot, the system workload is high.

Check the workload status by measuring performance information of other server applications.

Although the maximum request processing time is long, the average request processing time is short and close to the minimum request processing time.

3

Although the maximum request processing wait time is long, the averaged request processing wait time is short and close to the minimum request processing wait time.

One or both of the following causes can be assumed:

- System workload has temporarily become high

- Under a particular condition, there is a performance problem in the server application


4 In all the time slots when performance monitoring was performed, the maximum request processing wait time and average request processing wait time are too long.

Processing capacity of the server application is insufficient for the number of requests from the client. Take action to increase the processing capacity, such as increasing the process multiplicity in the WorkUnit definition.


3-32


5 In a particular time slot, the number of processes and requests waiting to be processed are high.

In a particular time slot, the number of requests to the server application has increased.

If the processing capacity of the server application is insufficient for the number of requests from the client, take action to increase the processing capacity such as increasing the process multiplicity in the WorkUnit definition.

Warnings Regarding the Evaluation of the Performance Information There are a number of caveats about evaluating the performance information, which are shown below.

• If the server application is terminated abnormally during processing, its request is not reflected in the performance information.


3-33

Managing the Performance Log Files Make sure that there is enough disk space to create performance log files before starting the Performance Monitoring Tool. Use the following formula to estimate the required disk space.

Disk space required =

shared-memory-size-specified-when-starting-performance-monitoring-tool

x (time-from-when-performance-monitoring-tool-is-started-until-stopped

÷ time-interval-specified-when-starting-performance-monitoring-tool)

Back up the performance log files and delete unnecessary files at regular intervals. Otherwise, the disk may be getting full. If the backed up and deleted files are to be output as a report, store these files in a folder and output a report with these files specified.

Performance log files will be created in the following folders.

• The folder specified in the ispmakeenv command parameter

• The folder specified in the ISP_LOG environment variable

Performance log files will be created in the folder specified in either the ispmakeenv command or the ISP_LOG environment variable according to the naming convention shown below. If both of them are specified, the folder name specified in the ispmakeenv command will take priority. If neither of them is specified, the folder name “TD_HOME\isp\log” will be used as the default folder name. “TD_HOME” is the interstage-installation-folder\td.

Performance log file name: ispYYYYMMDD.log

YYYYMMDD is a file creation date.

YYYY: Year

MM: Month (01 to 12)

DD: Day (01 to 31)

The Performance Monitoring Tool creates a performance log file for the date when it is activated. If the Performance Monitoring Tool has been operated over several days, performance log files for these days will be created on the daily basis.

Note

After executing the ispmakeenv command, do not delete performance log files that are being created by the Performance Monitoring Tool. Otherwise, performance information may not be stored correctly. Use the ispdeleteenv command to delete performance log files.


3-34

4-1

Chapter 4 Maintenance (Resource Backup)

This chapter explains system maintenance and how to back up resources to protect against resource deterioration or destruction and how to restore resource files from backup copies. This is necessary to protect resources before carrying out system maintenance, moving applications, or performing similar operations.

The operations described above can also be executed collectively.

Note

The descriptions in this chapter are based on the assumption that "C:\Interstage" is the installation directory of Interstage.

Chapter 4: Maintenance (Resource Backup)

4-2

Backing Up and Restoring Resources This section describes the procedures for backing up resources and for restoring backed up resources in the event of system maintenance and Interstage maintenance, and in an emergency such as when Interstage resources are damaged.

Note

The backup and restore procedures described in this section can only be executed on the same system. If the resources are moved to another system or if system information (such as hostname, IP address) is modified even within the same machine, resources cannot be restored using the backup/restore procedure described here. For details on moving resources, refer to Moving Resources to Another Server.

The applicable resources for backup/restore are only those files that define the application environment and that are held by Interstage. User applications are not applicable resources, and should be saved as required.

Outline and Applicable Resources The backup/restore procedure assists in restoring the application environment when an emergency such as damage to Interstage resources occurs.

The backup/restore procedure for Interstage resources involves backing up (saving) the resource files in the backup directory and restoring the resource files as required (Figure 4-1).

Figure 4-1 Interstage Backup/Restore Procedure

When backing up resources, it is better to save the resources to a removable medium that is not usually accessed rather than to accessible disks on the server system.

Backing Up and Restoring Resources

4-3

To save the latest resource files, execute a backup in the event of updating the resource files.

When upgrading the version or edition of Interstage, backup/restore is not required because the Interstage installer supports the existing resources. However, backing up resources is recommended in case of an emergency.

Note

When saving resources stored in the backup directory on the hard disk to removable storage media in the UNIX system, save the resources in archive format (using the tar or cpio command). If the resources are saved with their original file system format (by copying the file), the authority attribute of the file may be changed.

Applicable Resource

Backup and restore can be executed for the resources shown below. For information about backing up or restoring the following resource collectively, refer to Collective Maintenance.

Interstage Setup Resource File

Interstage system definition C:\Interstage\td\etc\isdef\isconf.txt Interstage operation environment definition C:\Interstage\td\etc\isreg\isinitdef.txt Interstage setup resource C:\Interstage\td\var\iscom\isegintr.dat C:\Interstage\td\var\iscom\iseiinfo.dat C:\Interstage\td\var\iscom\iseiippinfo.dat C:\Interstage\td\var\iscom\iserodcn.dat C:\Interstage\td\var\iscom\isei_odenvfile C:\Interstage\td\var\iscom\iscmd.lock

Interstage system definition /etc/opt/FSUNtd/isdef/isconf.txt Interstage operation environment definition /etc/opt/FSUNtd/isreg/isinitdef.txt Interstage setup resource /var/opt/FSUNtd/iscom/isegintr.dat /var/opt/FSUNtd/iscom/iseiinfo.dat /var/opt/FSUNtd/iscom/iseiippinfo.dat /var/opt/FSUNtd/iscom/iserodcn.dat /var/opt/FSUNtd/isei_odenvfile /var/opt/FSUNtd/iscom/iscmd.lock Profile file (*1) /opt/FJSVisas/etc/profile/default.txt


4-4

Interstage system definition /etc/opt/FJSVtd/isdef/isconf.txt Interstage operation environment definition /etc/opt/FJSVtd/isreg/isinitdef.txt Interstage setup resource /var/opt/FJSVtd/iscom/isegintr.dat /var/opt/FJSVtd/iscom/iseiinfo.dat /var/opt/FJSVtd/iscom/iseiippinfo.dat /var/opt/FJSVtd/iscom/iserodcn.dat /var/opt/FJSVtd/iscom/isei_odenvfile /var/opt/FJSVtd/iscom/iscmd.lock Profile file (*1) /opt/FJSVisas/etc/profile/default.txt

(*1) Backup is done only when a file exists.

Interstage Operation Tool Resource File

Environment definition file of Interstage Operation Tool C:\Interstage\gui\etc\config Web server environment definition file for Interstage Operation Tool C:\Interstage\F3FMwww\etc\conf\F3FMisgui.dat

Environment definition file of Interstage Operation Tool /etc/opt/FJSVisgui/config Web server environment definition file for Interstage Operation Tool /etc/opt/FJSVisgui/FJSVisgui.dat

Environment definition file of Interstage Operation Tool /etc/opt/FJSVisgui/config Interstage HTTP Server environment definition file for Interstage Operation Tool /etc/opt/FJSVisgui/httpd_FJSVisgui.conf


4-5

CORBA Service Resource File

CORBA Service (ORB)

Server default information C:\Interstage\ODWIN\etc\boa.env CORBA Service environment definition information C:\Interstage\ODWIN\etc\config Implementation repository C:\Interstage\ODWIN\etc\impl.db Host information C:\Interstage\ODWIN\etc\inithost Initial service C:\Interstage\ODWIN\etc\init_svc Queue control information C:\Interstage\ODWIN\etc\queue_policy CORBA Service environment setting information C:\Interstage\ODWIN\var\odenvfile SSL environment definition file (Note) C:\Interstage\ODWIN\etc\ssl.env

Server default information /etc/opt/FSUNod/boa.env CORBA Service environment definition information /etc/opt/FSUNod/config Implementation repository /etc/opt/FSUNod/impl.db Host information /etc/opt/FSUNod/initial_hosts Initial service /etc/opt/FSUNod/initial_services Queue control information /etc/opt/FSUNod/queue_policy CORBA Service environment setting information /var/opt/FSUNod/odenvfile SSL environment definition file (Note) /etc/opt/FSUNod/ssl.env

Server default information /etc/opt/FJSVod/etc/boa.env CORBA Service environment definition information /etc/opt/FJSVod/etc/config Implementation repository /etc/opt/FJSVod/etc/impl.db Host information


4-6

/etc/opt/FJSVod/etc/initial_hosts Initial service /etc/opt/FJSVod/etc/initial_services Queue control information /etc/opt/FJSVod/etc/queue_policy CORBA Service environment setting information /etc/opt/FJSVod/var/odenvfile SSL environment definition file (Note) /etc/opt/FJSVod/ssl.env

Note

This file can only be the target when the SSL linkage function is used.

The slot information directory and the certificate operation control directory are not included.

Naming Service

Naming service registration information C:\Interstage\ODWIN\etc\CosNaming\* Naming service environment definition information C:\Interstage\ODWIN\etc\nsconfig

Naming service registration information /etc/opt/FSUNod/CosNaming/* Naming service environment definition information /etc/opt/FSUNod/nsconfig

Naming service registration information /etc/opt/FJSVod/etc/CosNaming/* Naming service environment definition information /etc/opt/FJVSod/etc/nsconfig

Load Balancing Function (Enterprise Edition only)

Load balancing function registration information C:\Interstage\ODWIN\etc\LBO\* Loading balancing environment definition information C:\Interstage\ODWIN\etc\nslbo.conf


4-7

Load balancing function registration information /etc/opt/FSUNod/LBO/* Loading balancing environment definition information /etc/opt/FSUNod/nslbo.conf

Load balancing function registration information /etc/opt/FJSVod/etc/LBO/* Loading balancing environment definition information /etc/opt/FJSVod/etc/nslbo.conf

Interface Repository

Interface repository environment information C:\Interstage\ODWIN\etc\irconfig C:\Interstage\ODWIN\etc\irpth Interface repository data (*1) C:\Interstage\TD\var\IRDB\irobf.qfl C:\Interstage\TD\var\IRDB\irobf.qfp C:\Interstage\TD\var\IRDB\irobftran

Interface repository environment information /etc/opt/FSUNod/irconfig /etc/opt/FSUNod/irpth /etc/opt/FSUNod/obfconfig Interface repository data (*1) /opt/FSUNtd/var/IRDB/irobf.qfl /opt/FSUNtd/var/IRDB/irobf.qfp /opt/FSUNtd/var/IRDB/irobftran

Interface repository environment information /etc/opt/FJSVod/etc/irconfig /etc/opt/FJSVod/etc/irpth /etc/opt/FJSVod/etc/obfconfig Interface repository data (*1) /opt/FJSVtd/var/IRDB/irobf.qfl /opt/FJSVtd/var/IRDB/irobf.qfp /opt/FJSVtd/var/IRDB/irobftran


4-8

(*1) The Interface Repository data file can be saved in an arbitrary location.

The above pathname represents the isinit command and the default path created when the Interface Repository is constructed (defined by "IR path for DB file" in the Interstage operation environment definition file). The default path, when constructed by the odadmin_ex/odadmin command, is as follows:

Windows®: C:\Interstage\ODWIN\IRDB

Solaris OE: /opt/FSUNod/IRDB

Linux: /opt/FJSVod/IRDB

Note

The file that specifies the cache object (file set by the parameter select cache obj of the irconfig file) is excluded from the backup subject. Back up or restore the file if necessary.

Event Service Resource File

Event Service configuration information C:\Interstage\ESWIN\etc\group\essystem.cfg Event channel operation environment (*1) C:\Interstage\ESWIN\etc\group\esgrpX.grp Event channel group control information C:\Interstage\ESWIN\etc\group\esmnggrp.db Unit definition file File with def extension under the control of C:\Interstage\ESWIN\etc\def

Event Service configuration information /etc/opt/FJSVes/group/essystem.cfg Event channel operation environment (*1) /etc/opt/FJSVes/group/esgrpX.grp Event channel group control information /etc/opt/FJSVes/group/esmnggrp.db Unit definition file File with def extension under the control of /etc/opt/FJSVes/def

(*1) esgrpX.grp exists only during static generation and application of the event channel. (X is a number.)

Portable-ORB Resource File

Portable-ORB environment definition information C:\Interstage\PORB\etc\config (*1) Host information C:\Interstage\PORB\etc\initial_hosts (*1) Initial service


4-9

C:\Interstage\PORB\etc\initial_services (*1) Keystore file A file under the storage directory specified in [keystore storage location] of porbeditenv command (arbitrary) Embedded certificate control information - When specifying a storage directory in -rl option in executing porbMngCert command (Specified storage directory)\removelist - When not specifying a storage directory in -rl option in executing porbMngCert command (The current directory in executing porbMngCert command) \removelist

Portable-ORB environment definition information /etc/opt/FJSVporb/config (*1) Host information /etc/opt/FJSVporb/initial_hosts (*1) Initial service /etc/opt/FJSVporb/initial_services (*1) Keystore file A file under the storage directory specified in [keystore storage location] of porbeditenv command (arbitrary) Embedded certificate control information - When specifying a storage directory in -rl option in executing porbMngCert command (Specified storage directory)/removelist - When not specifying a storage directory in -rl option in executing porbMngCert command (The current directory in executing porbMngCert command) /removelist

(*1) In the situation in which Portable-ORB is downloaded, PORB_HOME is located under the document root folder of Web server. For details, refer to Development of Applications (Java Language) in the J2EE User's Guide.

Component Transaction Service Resource File

Setup information C:\Interstage\extp\etc\td001.rsc All files under C:\Interstage\td\var\td001\ (*1) User created APM C:\Interstage\extp\bin\extp_apm*.*

Setup information /var/opt/FJSVisas/system/default/FSUNextp/td001/def/* (*1) User created APM /opt/FSUNextp/bin/extp_apm*.*


4-10

Setup information /var/opt/FJSVisas/system/default/FSUNextp/td001/def/* (*1) User created APM /opt/FSUNextp/bin/extp_apm*.*

(*1) This directory can vary depending on the setup contents of "TD path for system " in the Interstage operation environment definition.

Database Linkage Service Resource File

System environment setup file C:\Interstage\ots\etc\config Tuning information setup file C:\Interstage\ots\etc\ots.ini sysconfig file C:\Interstage\ots\etc\sysconfig (*1) RMP property C:\Interstage\ots\etc\RMP.properties system information file C:\Interstage\ots\systeminfo\system (*2) Setup information All files under C:\Interstage\ots\etc\repository (*3)

System environment setup file /opt/FSUNots/etc/config sysconfig file /opt/FSUNots/etc/sysconfig (*1) RMP property /opt/FSUNots/etc/RMP.properties system information file /opt/FSUNots/systeminfo/system (*2) Setup information All files under /opt/FSUNots/etc/repository (*3)

System environment setup file /opt/FJSVots/etc/config sysconfig file /opt/FJSVots/etc/sysconfig (*1) RMP property /opt/FJSVots/etc/RMP.properties system information file /opt/FJSVots/systeminfo/system (*2)


4-11

Setup information All files under /opt/FJSVots/etc/repository (*3)

(*1) This file is generated by the otssetup command. It contains the information specified in the setup information file.

(*2) This file contains information required for the Database Linkage Service to operate.

(*3) The resource definition file registered by the otssetrsc command and other files are stored. These files are located on a shared disk in a cluster environment.

Note

To back up the resources of the Database Linkage Service, the CORBA Service resource file must also be backed up at the same time. For details, refer to CORBA Service Resource File.

Interstage HTTP Server Resource File

Environment definition file of the Interstage HTTP Server C:\Interstage\F3FMihs\conf\httpd.conf Password file (arbitrary) File created by the htpasswd command (only if user authentication is performed)

Environment definition file of the Interstage HTTP Server /etc/opt/FJSVihs/conf/httpd.conf Password file (arbitrary) File created by the htpasswd command (only if the user authentication is performed)

InfoProvider Pro Resource File

InfoProvider Pro environment definition file Environment definition file under C:\Interstage\F3FMwww\conf\

InfoProvider Pro environment definition file User specification (Usually, under /etc/opt/FSUNprovd)


4-12

Security control file Specified by authfile item of InfoProvider Pro environment definition file File that describes relation between data type and file extension Specified by content-type item of InfoProvider Pro environment definition file Extended CGI definition file Specified by gai-gw item of InfoProvider Pro environment definition file Session control Extension definition file Specified by ext-gw item of InfoProvider Pro environment definition file Error status file Specified by statusfile item of InfoProvider Pro environment definition file Filter application Specified by filter-file item of InfoProvider Pro environment definition file Password control file Specified by PasswdFile item of security control file Group control file Specified by GroupFile item of security control file IP GROUP control file Specified by IPGroupFile item of security control file User control file Specified by UserFile item of protect path setup block of security control file Client certificate condition file Specified by ClientCert item of protect path setup block of security control file Directory server information control file Specified by DirServFile item of security control file When -t all option is specified by ippbackup, ipprestore command, the following content files also become applicable target of this function. Public page All files under the folders that are specified by acstop item and link item of InfoProvider Pro environment definition file CGI application All files under the folders that are specified by cgi-path-idnt item of InfoProvider Pro environment definition file Open page of extension CGI All files under the folders that are specified by gw-acstop item of extension CGI definition file Extended CGI startup command excmd item of extension CGI definition file Extended CGI Error status file Specified by statusfile item of extension CGI definition file Returned HTML document when the end script of extended CGI is executed Specified by logout item of extension CGI definition file Open page of session control Extension All files under the folders that are specified by gw-acstop item of session control Extension definition file Session control Extension Error status file Specified by statusfile item of session control Extension definition file Returned HTML document when the end script of session control Extension is executed Specified by logout item of session control Extension definition file


4-13

J2EE Common Resource Files

Interstage J2EE common resource files All files in C:\Interstage\J2EE\def All files in C:\Interstage\J2EE\etc All files in C:\Interstage\J2EE\var

Interstage J2EE common resource files All files in /etc/opt/FJSVj2ee/def All files in /etc/opt/FJSVj2ee/etc All files in /etc/opt/FJSVj2ee/var

IJServer Resource Files

IJServer environment definition file environment definition file under [J2EE common directory]\IJServer\{IJServer name]\ directory Web application Data under [J2EE common directory]\ijserver\[IJServer name]\webapps directory EJB application Data under [J2EE common directory]\ijserver\[IJServer name]\ejbapps directory J2EE application client Data under [J2EE common directory]\ijserver\[IJServer name]\client directory J2EE common resource Data under [J2EE common directory]\ijserver\[IJServer name]\common directory client distribution Data under [J2EE common directory]\ijserver\[IJServer name]\distribute directory CORBA/SOAP client geteway file Data under [J2EE common directory]\ijserver\[IJServer name]\soapgw directory Top priority path Data under [J2EE common directory]\ijserver\[IJServer name]\ext directory Servlet Service environment definition file Data under C:\Interstage\F3FMjs4\conf directory C:\Interstage\F3FMihs\conf\workers2.properties


4-14

IJServer environment definition file environment definition file under /var/opt/FJSVj2ee/deployment/ijserver/[IJServer name]/ directory Web application Data under /var/opt/FJSVj2ee/deployment/ijserver/[IJServer name]/webapps directory EJB application Data under /var/opt/FJSVj2ee/deployment/ijserver/[IJServer name]/ejbapps directory J2EE application client Data under /var/opt/FJSVj2ee/deployment/ijserver/[IJServer name]/client directory J2EE common resource Data under /var/opt/FJSVj2ee/deployment/ijserver/[IJServer name]/common directory client distribution Data under /var/opt/FJSVj2ee/deployment/ijserver/[IJServer name]/distribute directory CORBA/SOAP client geteway file Data under /var/opt/FJSVj2ee/deployment/ijserver/[IJServer name]/soapgw directory Top priority path Data under /var/opt/FJSVj2ee/deployment/ijserver/[IJServer name]/ext directory Servlet Service environment definition file Data under /etc/opt/FJSVjs4/conf directory /etc/opt/FJSVjs4/conf

Interstage JMS Resource File

JNDI definition file C:\Interstage\JMS\etc\fjmsjndi.ser.* JMS nonvolatile file (*1) C:\Interstage\JMS\etc\fjmsmng.ser.* C:\Interstage\JMS\etc\dsub\fjmsdsubXXXX.ser C:\Interstage\JMS\etc\dsub\lock\.XXXX Cluster environmental definition file (*2) C:\Interstage\JMS\etc\ fjmscluster.ser

JNDI definition file /etc/opt/FJSVjms/fjmsjndi.ser.* JMS nonvolatile file (*1) /etc/opt/FJSVjms/fjmsmng.ser.* /etc/opt/FJSVjms/dsub/fjmsdsubXXXX.ser /etc/opt/FJSVjms/dsub/lock/.XXXX Cluster environmental definition file (*2) /etc/opt/FJSVjms/fjmscluster.ser


4-15

JNDI definition file /opt/FJSVjms/etc/fjmsjndi.ser.* JMS nonvolatile file (*1) /opt/FJSVjms/etc/fjmsmng.ser.* /opt/FJSVjms/etc/dsub/fjmsdsubXXXX.ser /opt/FJSVjms/etc/dsub/lock/.XXXX

(*1) fjmsdsubXXXX.ser and .XXXX are existent only when JMS applications run in nonvolatile operation mode. (X is a digit.)

(*2) fjmscluster.ser is existent only in a cluster environment.

Servlet Service for Interstage Management Console Resource File

JServlet environment definition file C:\Interstage\F3FMjs2su\conf\jswatch.conf Servlet gateway environment definition file C:\Interstage\F3FMjs2su\conf\jsgw_apapi.conf Servlet container environment definition file C:\Interstage\F3FMjs2su\conf\jscontainer.xml

JServlet environment definition file /etc/opt/FJSVjs2su/jswatch.conf Servlet gateway environment definition file /etc/opt/FJSVjs2su/jsgw_apapi.conf Servlet container environment definition file /etc/opt/FJSVjs2su/jscontainer.xml

SOAP Service Resource File

Web service information management file user-specified- optional directory\server-config.wsdd Web service environment setting file Under C:Interstage\F3FMsoap\etc Under C:Interstage\F3FMsoap\conf All files under a user-specified optional directory


4-16

Web service information management file user-specified- optional directory/server-config.wsdd Web service environment setting file Under /etc/opt/FJSVsoap/etc Under /etc/opt/FJSVsoap/conf All files under a user-specified optional directory

InfoDirectory Directory Service Resource File

DSA Database folder that is created by the control tool client (*) Property file of control tool client C:\Interstage\Id\Mgr\etc\techmgr\* SSL environment C:\Interstage\Id\Dir\ldap\sslconfig.cfg Web connector environment C:\Interstage\Id\Dir\web\infodir.conf C:\Interstage\Id\Dir\web\infodir.fmap C:\Interstage\Id\Dir\web\infodir.at C:\Interstage\Id\Dir\web\ldapfriendly C:\Interstage\Id\Dir\web\ldapfriendly.modify

DSA Database directory that is created by the control tool client (*) Property file of control tool client /opt/FJSVdirs/etc/techMgr/* SSL environment /opt/FJSVildap/etc/sslconfig.cfg Web connector environment /opt/FJSVidweb/infodir.conf /opt/FJSVidweb/infodir.fmap /opt/FJSVidweb/infodir.at /opt/FJSVidweb/ldapfriendly /opt/FJSVidweb/ldapfriendly.modify

(*): This is the folder that is specified as the "DIB installation directory" when creating DSA with the control tool client.


4-17

Interstage Certificate Environment Resource File

Interstage Certificate Environment All files under C:\Interstage\etc\security

Interstage Certificate Environment All files under /etc/opt/FJSVisscs/security

Old Version Servlet Service Resource File

JServlet environment definition file C:\Interstage\F3FMjs2\conf\jswatch.conf Servlet gateway environment definition file -When the Web server in use is Web Server Storage location (directory): Specified by Web server environment definition file (arbitrary) Filename: Specified by Web server environment definition file (arbitrary) -When the Web server in use is Internet Information Server C:\Interstage\F3FMjs2\conf\jsgw.conf -When the Web server in use is Interstage HTTP Server Storage location (directory): Specified by Interstage HTTP Server environment definition file (arbitrary) Filename: Specified by Interstage HTTP Server environment definition file (arbitrary) JServlet container environment definition file An arbitrary file specified by user (Specified by item [containername].containerconf of Jservlet environment definition file) JServlet property file C:\Interstage\F3FMjs2\conf\jservlet.properties Web application In an arbitrary directory specified by user (Specified by tag Context attribute docBase of Servlet container environment definition file) Web application environment definition file Web application folder \WEB-INF\web.xml

Jservlet environment definition file /etc/opt/FJSVjs2/jswatch.conf Servlet gateway environment definition file -When the Web server in use is InfoProvider Pro Storage location (directory): Specified by InfoProvider Pro environment definition file (arbitrary)


4-18

Filename: Specified by InfoProvider Pro environment definition file (arbitrary) -When the Web server in use is Sun ONE Web Server(iPlanet Web Server) Storage location (directory): Specified by obj.conf file of Sun ONE Web Server(iPlanet Web Server) Filename: Specified by obj.conf file of Sun ONE Web Server(iPlanet Web Server) -When the Web server in use is Interstage HTTP Server Storage location (directory): Specified by Interstage HTTP Server environment definition file (arbitrary) Filename: Specified by Interstage HTTP Server environment definition file (arbitrary) Servlet container environment definition file An arbitrary file specified by user (Specified by item [containername].containerconf of Jservlet environment definition file) JServlet property file /etc/opt/FJSVjs2/jservlet.properties Web application In an arbitrary directory specified by user (Specified by tag Context attribute docBase of Servlet container environment definition file) Web application environment definition file Web application directory /WEB-INF/web.xml Session recovery environment definition file /etc/opt/FJSVjs2/jssr_system.properties

Session Registry Server Resource File (Enterprise Edition Only)

System information definition file /etc/opt/FJSVjs2sr/conf/jssr_system.properties Session information definition file /etc/opt/FJSVjs2sr/services/session/conf/jssr_session.properties Registry information definition file /etc/opt/FJSVjs2sr/conf/jssr_registry.properties System persistence information definition file Storage location : /etc/opt/FJSVjs2sr/conf/ File name: Specified by registry.cluster.properties of the system information definition file Session persistence information definition file Storage location : /etc/opt/FJSVjs2sr/services/session/conf/ File name: Specified by session.serialize.properties of the session information definition file

Jservlet environment definition file /etc/opt/FJSVjs2/jswatch.conf Servlet gateway environment definition file Storage location (directory): Specified by Interstage HTTP Server environment definition file (arbitrary) Filename: Specified by Interstage HTTP Server environment definition file (arbitrary Servlet container environment definition file


4-19

An arbitrary file specified by user (Specified by item [containername].containerconf of Jservlet environment definition file) JServlet property file /etc/opt/FJSVjs2/jservlet.properties Web application In an arbitrary directory specified by user (Specified by tag Context attribute docBase of Servlet container environment definition file) Web application environment definition file Web application directory /WEB-INF/web.xml

Backup Procedure This section explains Interstage resource backup procedures.

It explains on the assumption that it backs up to a folder for backup resources storing called X:\Backup.

It explains on the assumption that it backs up to a directory for backup resources storing called /backup.

Stopping the Service

Log in with Administrator authority and use the isstop command to stop all services and the server application. isstop -f

Use the isstop command to stop all services and the server application. isstop -f

Note

Services that are not stopped by the isstop command must be stopped using a separate stopping operation. For more information on how to stop Interstage, refer to Terminating Interstage in Chapter 2.

Creating a Backup Resource Directory Create a directory used to store Interstage backup resources. Interstage backup resources are stored under this directory.

mkdir X:\Backup


4-20

mkdir /backup

Note

Ensure in advance that the disk on which a backup resource directory is to be created has enough free space. The size of disk space required for storing backup resources is the total sum of the amounts of backup resources shown in Outline and Applicable Resources.

Backing Up Interstage Setup Resource This section explains the setup resource backup procedure that is created on Interstage initialization using the isinit command.

Backup Command

The following command is used for backing up the Interstage setup resource:

C:\Interstage\td\bin\iscbackupsys.exe

/opt/FSUNtd/bin/iscbackupsys

/opt/FJSVtd/bin/iscbackupsys

The iscbackupsys command must be executed while Interstage is stopped.

Backup Procedure

An example is shown below when the resource backup destination folder is "X:\Backup ".

Execute the iscbackupsys command. iscbackupsys X:\Backup

An example is shown below where the resource backup destination directory is /backup/isc.


4-21

Execute the iscbackupsys command. iscbackupsys /backup/isc

Notes

• If the path of the backup directory includes a space, the path must be enclosed in double quotes when it is specified for a command parameter.

• The iscbackupsys command creates an ISC folder under the backup folder and backs up Interstage setup resources under the ISC folder. If an ISC folder already exists, delete it before executing this command.

• If Interstage is running, enter the isstop -f command to stop it in advance. For a cluster system, stop it according to the cluster system stop procedure.

• Back up the environment definition file of the InfoProvider Pro that is defined in the Interstage operation environment definition, using the procedure in Backing Up Interstage HTTP Server Resource.

• The iscbackupsys command creates an "isc" directory under the backup directory and backs up Interstage setup resources under the "isc" directory. If a directory or file named "isc" already exists, delete it before executing this command.

• If Interstage is running, enter the isstop -f command to stop it in advance.

Backing Up Interstage Operation Tool Resources This section explains the Interstage Operation Tool resource backup procedure.

Backup Command

The following command is used for backing up the Interstage Operation Tool resource:

C:\Interstage\gui\bin\isguibackup.bat


4-22

/opt/FJSVisgui/bin/isguibackup

The isguibackup command must be executed when Interstage is stopped. For command details, refer to the Reference Manual (Command Edition).

Backup Procedure

Before the isguibackup command is executed, a directory must be created in the resource backup directory for operation tool resource storage.

An example is shown below where the Interstage installation path is "C:\Interstage" and the resource backup destination folder is "X:\Backup\isgui".

1. Create the folder for storing operation tool resources. mkdir X:\Backup\isgui

2. Execute the isguibackup command. C:\Interstage\gui\bin\isguibackup C:\Interstage X:\Backup\isgui

Notes

• Start backup while the folder for storing operation tool resources is empty.

• If the path of the backup folder or Interstage install folder includes a blank, the path must be enclosed in double quotes when it is specified for a command parameter.

• When Interstage is running, stop Interstage using the isstop -f command.

• If any message is output before the command termination message is output, execution of the command has ended with failure. In such a case, execute the command again following the contents of the output message and Note during execution of this command.

• If the environment definition of the Interstage Operation Tool is not customized, this backup operation need not be performed.

An example is shown below where the resource backup destination directory is /backup/isgui.

1. Create a backup directory. mkdir /backup/isgui

2. Execute the isguibackup command. isguibackup /backup/isgui


4-23

Notes

• Perform the backup only when the directory under the backup directory is empty.

• If the backup directory contains a blank, the parameter must be enclosed in " " (double-quotation marks).

• If Interstage is running, stop Interstage with the isstop -f command.

Use the cp or other command to copy the resource files of the Interstage operation tool to the backup directory.

The following shows an example of operation assumed when the resource backup directory is /backup/isgui:

Create a backup directory to store the resource files of the Interstage operation tool. mkdir /backup/isgui

2. Use the cp or other command to copy the resource files of the Interstage operation tool to the backup directory. cp /etc/opt/FJSVisgui/config /backup/isgui cp /etc/opt/FJSVisgui/httpd_FJSVisgui.conf /backup/isgui cp /etc/opt/FJSVisgui/magic /backup/isgui cp /etc/opt/FJSVisgui/mime.types /backup/isgui

Notes

• Implement the backup only when the directory under the backup directory is empty.

• When Interstage is running, stop Interstage with the isstop -f command

• This backup operation need not be executed if the Interstage Operation Tool has not been customized.

Backing Up CORBA Service Resource This section explains the CORBA Service resource backup procedure.

Backup Command

The following command is used for backing up the CORBA Service resource:

C:\Interstage\ODWIN\bin\odbackupsys.exe


4-24

/opt/FSUNod/bin/odbackupsys

/opt/FJSVod/bin/odbackupsys

The odbackupsys command must be executed when the CORBA Service is stopped.

Backup Procedure

An example is shown below where the backup destination path is X:\Backup\OD.

The odbackupsys command is executed, and the CORBA Service resource file is backed up. odbackupsys X:\Backup

An example is shown below where the backup destination path is /backup/FSUNod.

The odbackupsys command is executed, and the CORBA Service resource file is backed up. odbackupsys /backup

An example is shown below where the backup destination path is /backup/FJSVod.

The odbackupsys command is executed, and the CORBA Service resource file is backed up. odbackupsys /backup

Note

The odbackupsys command creates a directory under the specified backup destination path and makes a backup copy of the CORBA Service resources under the directory. If the following directory already exists, perform the operation after deleting the directory.

Windows®: OD

Solaris OE: FSUNod

Linux: FJSVod


4-25

Notes

When using the SSL linkage function, save the following resources in the backup directory:

• Slot information directory (directory specified in -sd option of odsetSSL command)

• Operation control directory (directory specified in -ed option of odsetSSL command)

• SSL environment definition file (ssl.env file) (on Windows (R) system or Solaris OE system)

Backing Up Event Service Resource This section explains the backup procedure for the Event Service resource.

Backup Command

The following command is used for backing up the Event Service resource:

C:\Interstage\ESWIN\bin\esbackupsys.exe

/opt/FJSVes/bin/esbackupsys

The esbackupsys command must be executed when the Event Service is stopped.

Backup Procedure

An example is shown below where the backup destination path is X:\Backup\ES.

Execute the esbackupsys command to back up the Event Service resource. esbackupsys -d X:\Backup

An example is shown below where the backup destination path is /backup/FJSVes.

Execute the esbackupsys command to back up the Event Service resource. esbackupsys -d /backup


4-26

Notes

• The esbackupsys command creates a directory under the specified backup destination path and makes a backup copy of the Event Service resources under the directory. If the following directory already exists, perform the operation after deleting the directory.

Windows®: ES

Solaris OE/Linux: FJSVes

• The unit refers to a definition file with the extension "def" under the following directory during backup. If a unit definition file under a different directory is specified in "esmkunit -uf" when creating a unit, the unit is not selected for backup. Make a copy of the unit under the following directory before backup or store it in the backup storage directory after backup. When restoring (executing the esrestoresys command), the unit is created based on the unit definition file under the following directory. If an incorrect unit definition file exists, the restore operation fails. Do not store any unused definition files under the following directory during backup: Windows®: C:\Interstage\ESWIN\etc\def

Solaris OE/Linux: /opt/FJSVes/etc/def

Backing Up Portable-ORB Resource This section explains the Portable-ORB resource backup procedure.

Backup Procedure

An example is shown below where the backup destination path is X:\Backup\PORB.

1. Create a backup directory. mkdir X:\Backup\PORB

2. Copy the Portable-ORB resource to the backup directory using the copy command (or Explorer). (Note) copy PORB_HOME\etc\config X:\Backup\PORB copy PORB_HOME\etc\initial_hosts X:\Backup\PORB copy PORB_HOME\etc\initial_services X:\Backup\PORB

An example is shown below where the backup destination path is /backup/porb.(For Solaris)

1. Create a backup directory. mkdir /backup/porb


4-27

2. Copy the Portable-ORB resource to the backup directory using the cp command. (Note) cp PORB_HOME/etc/config /backup/porb cp PORB_HOME/etc/initial_hosts /backup/porb cp PORB_HOME/etc/initial_services /backup/porb

Note

When downloading the Portable-ORB, when multiple PORB_HOME were specified, all must be backed up. When doing so, change the backup destination path so that overwriting will not take place.

Notes

When using the SSL linkage function, make copies of the following resources to the backup directory: Refer to Portable-ORB Resource File for the details of the following file:

• Keystore file

• Embedded certificate control information.

Backing Up Component Transaction Service Resource This section explains the backup procedure for the Component Transaction Service resource.

Backup Command

The following command is used for backing up the Component Transaction Service resource:

C:\Interstage\td\bin\tdbackupsys.exe

/opt/FSUNtd/bin/tdbackupsys

/opt/FJSVtd/bin/tdbackupsys

The tdbackupsys command must be executed while Interstage is stopped.

Backup Procedure

An example where the resource backup destination folder is X:\Backup\ is shown below.

Execute the tdbackupsys command. tdbackupsys X:\Backup\


4-28

Notes

• After creating the "TD" and "EXTP" folders under the control of the backup folder, the tdbackupsys command backs up the Component Transaction Service resource under the control of each folder. Execute the command after deleting each folder when "TD" or "EXTP" folder already exists.

• If the path of the backup folder includes a blank, the path must be enclosed in double quotes when it is specified for a command parameter.

• If Interstage is running, stop Interstage using the isstop -f command. Stop the cluster system by the method of stopping the cluster system.

• It is necessary to back up the Interstage setup resource and the CORBA Service resource before the Component Transaction Service resource is backed up.

An example where the resource backup destination directory is /backup/td is shown below.

Execute the tdbackupsys command. tdbackupsys /backup/

Notes

• If the backup directory contains a space, the parameter must be enclosed in " " (double-quotation marks).

• The Interstage setup resource and CORBA Service resource must be backed up before the Component Transaction Service resource is backed up.

• If Interstage is running, stop Interstage with the isstop -f command. Stop the cluster system using the cluster system stopping method.

• After creating the "FSUNtd" and "FSUNextp" directories under the control of the backup directory, the tdbackupsys command backs up the Component Transaction Service resource under the control of each directory. If the "FSUNtd" or "FSUNextp" directories already exist, delete them before executing this command.

• After making the "FJSVtd" directory and "FJSVextp" directory under the control of the backup directory, the tdbackupsys command backs up the component transaction service resource under the control of each directory. Execute the command after deleting the directory when the "FJSVtd" or "FJSVextp" directory already exists.

• When Interstage is running, stop Interstage with the isstop -f command.


4-29

Backing Up Database Linkage Service Resource This section explains the Database Linkage Service resource backup procedure.

Backup Command

The following command is used for backing up the Database Linkage Service resource:

C:\Interstage\ots\bin\otsbackupsys

/opt/FSUNots/bin/otsbackupsys

/opt/FJSVots/bin/otsbackupsys

The otsbackupsys command must be executed only when Interstage is stopped.

Backup Procedure

An example where the resource backup destination folder is "X:\Backup" is shown below.

Execute the otsbackupsys command. otsbackupsys X:\Backup\

Notes

• After creating the "OTS" folder under the control of the backup folder, the otsbackupsys command backs up the Database Linkage Service resource under the control of "OTS" folder. Execute the command after deleting "OTS" folder when "OTS" folder already exists.


• If Interstage is running, stop Interstage using the isstop -f command. Stop the cluster system by the method of stopping the cluster system.

• It is necessary to back up the Interstage setup resource and the CORBA Service resource before the Database Linkage Service resource is backed up.

An example where the resource backup destination directory is “/backup/ots" is shown below.

Execute the otsbackupsys command.


4-30

otsbackupsys /backup/

Notes

• After creating the "FSUNots" directory under the control of the backup directory, the otsbackupsys command backs up the Database Linkage Service resource under the control of the "FSUNots" directory. If the "FSUNots" directory already exists, delete it before executing this command.

• If the path of the backup directory includes a blank, the path must be enclosed in double quotes when it is specified for a command parameter.

• If Interstage is running, stop Interstage using the isstop -f command. Stop the cluster system using the cluster system stopping method.

• The Interstage setup resource and CORBA Service resource must be backed up before the Database Linkage Service resource is backed up.

Backing Up Interstage HTTP Server Resource The following explains the backup procedure for Interstage HTTP Server resources.

Backup Procedure

The following shows an example when the backup destination path is X:\Backup\IHS.

1. Create a backup directory. mkdir X:\Backup\IHS

2. Use the copy command (or Explorer) to copy the Interstage HTTP Server resources to the backup directory. copy C:\Interstage\F3FMihs\conf\httpd.conf X:\Backup\IHS copy Password file X:\Backup\IHS (*1)

The following shows an example when the backup destination path is /backup/FJSVihs.

1. Create a backup directory. mkdir /backup/FJSVihs

2. Use the cp command to copy the Interstage HTTP Server resources to the backup directory. cp /etc/opt/FJSVihs/conf/httpd.conf /backup/FJSVihs cp Password file /backup/FJSVihs (*1)

*1) Only if a password file is created using the htpasswd command for user authentication.


4-31

Note

To back up the content, and when a file used in setting the environment other than httpd.conf and the password file exists, save the corresponding file to the backup directory.

When using the SSL linkage function, save the following resources to the backup directory:

• Slot information directory (directory specified in SSLSlotDir directive of httd.conf file)

• Operation control directory (directory specified in SSLEnvDir directive of httd.conf file)

• User PIN control file (directory specified in SSLUserPINFile directive of httd.conf file)

Backing Up InfoProvider Pro Resource This section explains the InfoProvider Pro resource backup procedure.

For backing up InfoProvider Pro resources, execute the ippbackup command.

Backup Command

The following command is used for backing up the InfoProvider Pro resource:

C:\Interstage\F3FMwww\Program\ippbackup.exe

/opt/FSUNprovd/bin/ippbackup

The ippbackup command must be executed while Interstage is stopped.

Backup Procedure

When two or more environment definition files are to be backed up, change the environment definition file and backup destination path and repeat the following operations.

An example under the following conditions is shown below.

• The filename of the applicable environment definition file is F3FMwww.dat.

• The path for the backup folder is X:\Backup.

Execute the ippbackup command to back up the InfoProvider Pro resource.

• In the case of backing up only the environment definition information C:\Interstage\F3FMwww\Program\ippbackup -f F3FMwww.dat -d X:\Backup


4-32

• In the case of backing up the environment definition information and contents C:\Interstage\F3FMwww\Program\ippbackup -f F3FMwww.dat -d X:\Backup -t all


• The filename of the environment definition file is /etc/opt/FSUNprovd/HTTPD.conf.

• The path for the backup directory is /backup.

Execute the ippbackup command to back up the InfoProvider Pro resource.

• To back up only the environment definition information: /opt/FSUNprovd/bin/ippbackup -f /etc/opt/FSUNprovd/HTTPD.conf -d /backup

• To back up the environment definition information and contents: /opt/FSUNprovd/bin/ippbackup -f /etc/opt/FSUNprovd/HTTPD.conf -d /backup -t all

Notes

When using the SSL linkage function, save the following resources to the backup directory:

• Slot information directory (directory specified in the slot information directory definition item of the SSL environment definition file)

• Operation control directory (directory specified in the operation control directory definition item of the SSL environment definition file)

Backing Up J2EE Common Resource File A procedure for backing up the J2EE common resource files is explained.

Backup Command

Use the following command to back up the J2EE common resource file:

C:\Interstage\J2EE\bin\j2eebackup.exe

/opt/FJSVj2ee/bin/j2eebackup

The j2eebackup command can only be executed while Interstage is stopped.


4-33

Backup Procedure

The following is an example of operation when the backup destination path is X:\Backup.

1. Confirm that the directory in which the jar command is stored is contained in the environment variable PATH. (*1)

2. Execute the j2eebackup command to back up the J2EE common resource file. C:\Interstage\J2EE\bin\j2eebackup -d X:\backup

The following is an example of operation when the backup destination path is /backup.

1. Check that the directory in which the jar command is stored is contained in the path set in the environment variable PATH. (*1)

2. Execute the j2eebackup command to back up the J2EE common resource file. /opt/FJSVj2ee/bin/j2eebackup -d /backup (*2)

(*1) This check is required because the j2eebackup command uses the jar command for internal processing.

(*2) The example here shows a situation in which the resources of a default system are backed up. For the Solaris OE version, the j2eebackup command for backup of resources of systems other than the default system would have the following format: opt/FJSVj2ee/bin/j2eebackup -d /backup -M <system-name>

Backing Up IJServer Resource File A procedure for backing up the IJServer resource files is explained.

Backup Command

Use the following command to back up the IJServer resource file:

C:\Interstage\J2EE\bin\ijsbackup.exe

/opt/FJSVj2ee/bin/ijsbackup


4-34

Backup Procedure

The following is an example of operation when the backup destination path is X:\Backup.

Execute the ijsbackup command to back up the IJServer resource file. C:\Interstage\J2EE\bin\ijsbackup -d X:\Backup

The following is an example of operation when the backup destination path is /backup.

Execute the ijsbackup command to back up the IJServer resource file. /opt/FJSVj2ee/bin/ijsbackup -d /backup

Note

Before backing up the IJServer resource file, it is necessary to backup the following:

• Interstage setup resources

• CORBA Service resources

• Component Transaction Service resources

• J2EE Common resources

Backing Up Interstage JMS Resource A procedure for backing up the Interstage JMS resource is explained.

Backup Command

The following command is used for backing up the Interstage JMS resource.

C:\Interstage\JMS\bin\jmsbackup.exe

/opt/FJSVjms/bin/jmsbackup

The jmsbackup command must be executed while JMS applications are stopped.


4-35

Backup Procedure

An example of an operation when the backup destination path is X:\Backup is shown below.

Enter the jmsbackup command to back up the Interstage JMS resource. jmsbackup -d X:\Backup

An example of operation when the backup destination path is /backup is shown below.

Enter the jmsbackup command to back up the Interstage JMS resource. jmsbackup -d /backup

Note

The jmsbackup command creates a directory under the specified backup destination path and makes a backup copy of the Interstage JMS resources under the directory. If the following directory already exists, perform the operation after deleting the directory.

Windows®: JMS Solaris OE/Linux: FJSVjms

Backing Up Servlet Service for Interstage Management Console Resources This section describes the procedure for backing up the resources of the Servlet Service for Interstage Management Console.

Backup Procedure

The following shows an example when the path of the backup folder is X:\Backup.

Execute the jsbackup command to back up the environment definition file. C:\Interstage\F3FMjs2su\bin\jsbackup X:\Backup

The following shows an example when the path of the backup directory is /backup.

Execute the jsbackup command to back up the environment definition file. /opt/FJSVjs2su/bin/jsbackup /backup

Backing Up SOAP Service Resources The SOAP Service resource backup procedure is explained.


4-36

Backup Command

The following command is used for backing up the SOAP Service resource.

For each environment definition file (excluding the resource file of the Servlet Service): C:\Interstage\F3FMsoap\bin\issoapbackup.exe

For each environment definition file (excluding the resource file of the Servlet Service): /opt/FJSVsoap/bin/issoapbackup

Backup Procedure

Execute the issoapbackup command to back up the resource file of the SOAP Service in the backup directory.

The issoapbackup command is always used when executing a backup for the following directories:

• Interstage installation directory C:\Interstage\F3FMsoap\etc.

• Interstage installation directory C:\Interstage\F3FMsoap\conf.

An example that assumes the following conditions is shown below:

• The backup directory path is X:\Backup\SOAP.

• Web service information management file is located in C:\Interstage\F3FMsoap\deploy\server-config.wsdd.

Example

1. Create a backup directory. mkdir X:\Backup\SOAP

2. Stop Interstage operation control Servlet service and Servlet service. C:\Interstage\F3FMjs2su\bin\jssvstop C:\Interstage\F3FMjs2\bin\jssvstop

3. Execute the issoapbackup command to back up the environment definition file. Although the following example writes the command on two lines, actually write it on a single line. C:\Interstage\F3FMsoap\bin\issoapbackup -d X:\Backup\SOAP C:\Interstage\F3FMsoap\deploy\DeploydServices.db


4-37

Execute the issoapbackup command to back up the resource file of the SOAP Service in the backup directory.

The issoapbackup command is always used when executing a backup for the following directories:

• "/etc/opt/FJSVsoap/etc" directory

• "/etc/opt/FJSVsoap/conf" directory

An example that assumes the following conditions is shown below:

• The backup directory is /backup/SOAP.

• Web service information management file is located in /opt/FJSVsoap/deploy/server-config.wsdd.

Example

1. Create a backup directory. mkdir /backup/SOAP

2. Stop Interstage operation control Servlet service and Servlet service. /opt/FJSVjs2su/bin/jssvstop /opt/FJSVjs2/bin/jssvstop

3. Execute the issoapbackup command to back up the environment definition file. Although the following example writes the command on two lines, actually write it on a single line. /opt/FJSVsoap/bin/issoapbackup -d /backup/SOAP /opt/FJSVsoap/deploy/server-config.wsdd

Note

Also back up the resource file of the IJServer, as the SOAP Service is a Web application. For details, refer to Backing Up IJServer Resource File.

Backing Up InfoDirectory Resource This section explains the InfoDirectory resource backup procedure (when using InfoDirectory).

Backup Procedure

An example where the backup destination path is X:\Backup\ID is shown below.

1. Create a backup folder. mkdir X:\Backup\ID mkdir X:\Backup\ID\etc

2. Save DSA. Use Explorer to copy the DSA database storage folder under the backup folder.


4-38

3. Use the copy command to copy the property file of the control client to the ETC folder under the backup folder. copy C:\Interstage\Id\Mgr\etc\techMgr\* X:\Backup\ID\etc

4. When SSL is used in InfoDirectory, use the copy command to copy the SSL environment file to the ldap folder under the backup folder. mkdir X:\Backup\ID\ldap copy C:\Interstage\Id\Dir\ldap\sslconfig.cfg X:\Backup\ID\ldap

5. When Web connector is used, use the copy command to copy the Web connector environment to the web folder under the backup folder. mkdir X:\Backup\ID\web copy C:\Interstage\Id\Dir\web\infodir.conf X:\Backup\ID\web copy C:\Interstage\Id\Dir\web\infodir.fmap X:\Backup\ID\web copy C:\Interstage\Id\Dir\web\infodir.at X:\Backup\ID\web copy C:\Interstage\Id\Dir\web\ldapfriendly X:\Backup\ID\web copy C:\Interstage\Id\Dir\web\ldapfriendly.modify X:\Backup\ID\web

An example where the backup destination path is /backup/id and the DIB installation directory is /opt/dib is shown below.

1. Create a backup directory. mkdir /backup/id

2. Save DSA. Use the cp command to copy the DSA database storage directory to the dib directory under the backup directory. mkdir /backup/id/dib cp -r /opt/dib/dsa /backup/id/dib

3. Use the cp command to copy the property file of the control client to the etc directory under the backup directory. mkdir /backup/id/etc cp -r /opt/FJSVdirs/etc/techMgr /backup/id/etc

4. When SSL is used in InfoDirectory, use the cp command to copy the SSL environment file to the ldap directory under the backup directory. mkdir /backup/id/ldap cp /opt/FJSVildap/etc/sslconfig.cfg /backup/id/ldap


4-39

5. When Web connector is used, use the cp command to copy the Web connector environment to the web directory under the backup directory. mkdir /backup/id/web cp /opt/FJSVidweb/infodir.conf /backup/id/web cp /opt/FJSVidweb/infodir.fmap /backup/id/web cp /opt/FJSVidweb/infodir.at /backup/id/web cp /opt/FJSVidweb/ldapfriendly /backup/id/web cp /opt/FJSVidweb/ldapfriendly.modify /backup/id/web

Note

Before saving DSA, ensure that DSA has stopped.

Backing up Interstage Certificate Environment Resources This section explains the procedure for backing up the Interstage Certificate Environment resources.

Backup Procedure

An example of the operation to be performed when the backup destination path is X:\Backup\scs is shown below:

1. Create a backup directory. mkdir X:\Backup\scs

2. Use the xcopy command (or Explorer) to copy the Interstage Certificate Environment resources to the backup directory. xcopy /E C:\Interstage\etc\security X:\Backup\scs

An example of the operation to be performed when the backup destination path is /backup/scs is shown below:

1. Create a backup directory. mkdir /backup/scs

2. Use the cp command (or Explorer) to copy the Interstage Certificate Environment resources to the backup directory. cp -rp /etc/opt/FJSVisscs/security /backup/scs

Note

The Interstage Certificate Environment can be accessed from the group specified during environment configuration. For this reason, back up also system information on the user accounts and groups.


4-40

Backing Up Old Version Servlet Service Resource This section explains the old version Servlet Service resource backup procedure.

Backup Command

The following commands are used for backing up the old version Servlet Service resource:

Each environment definition file (except for Web application environment definition file): C:\Interstage\F3FMjs2\bin\jsbackup.exe Web application (including Web application environment definition file): C:\Interstage\JDK13\bin\jar.exe (When JDK1.3 is installed at "C:\Interstage\JDK13") xcopy command (JRE)

Each environment definition file (except for Web application environment definition file ): /opt/FJSVjs2/bin/jsbackup Web application (including Web application environment definition file ): /opt/FJSVawjbk/jdk13/bin/jar (When JDK1.3 is installed at "/opt/FJSVawjbk/") tar command (JRE)

Backup Procedure

When there are multiple web applications, execute item 3 described below (web application backup) with different backup file names (directory names) specified.


Conditions


• The storage folder of the servlet gateway environment definition file is C:\Interstage\F3FMjs2\conf

• The storage folder of the Web application is C:\Interstage\F3FMjs2\webapps\sample

• The backup folder of the Web application is X:\Backup\F3FMjs2\webapps

• The backup file name of the Web application is sample.war (JDK)


4-41

Example

1. Execute the jsbackup command to back up the environment definition file. C:\Interstage\F3FMjs2\bin\jsbackup X:\Backup

2. Create a backup directory of the Web application. mkdir X:\Backup\F3FMjs2\webapps

3. Back up the web application.

For JDK

Execute the jar command to back up the Web application in the backup folder. C:\Interstage\JDK13\bin\jar cvfM X:\Backup\F3FMjs2\webapps\sample.war C:\Interstage\F3FMjs2\webapps\sample

For JRE xcopy /E /K /I C:\Interstage\F3FMjs2\webapps\sample X:\Backup\F3FMjs2\webapps\sample

Note

If the Servlet gateway environment definition file has been stored in an C:\Interstage\F3FMjs2\conf, execute steps 1, 2, and 3 above. Then, use the operational example below to back up the Servlet gateway environment definition file.

When there are multiple servlet gateway environment definition files, execute the item 2 described below with different backup file names specified.

Conditions

• The Servlet gateway environment definition file is C:\tmp\F3FMjs2\conf\jsgw.conf

• The backup folder of the Servlet gateway environment definition file is X:\Backup\F3FMjs2\conf.

Example

1. Create the backup folder of the Servlet gateway environment definition file. mkdir X:\Backup\F3FMjs2\conf

2. Execute the copy command to back up the Servlet gateway environment definition file. copy C:\tmp\F3FMjs2\conf\jsgw.conf X:\Backup\F3FMjs2\conf


Conditions



4-42

• The storage directory of the servlet gateway environment definition file is /etc/opt/FJSVjs2.

• The storage directory of the Web application is /opt/FJSVjs2/webapps/sample.

• The backup directory of the Web application is /backup/FJSVjs2/webapps.

• The backup file name of the Web application is sample.war (JDK).

• The backup file name of the Web application is sample.tar (JRE).

Example

1. Execute the jsbackup command to back up the environment definition file. /opt/FJSVjs2/bin/jsbackup /backup

2. Create a backup directory of the Web application. mkdir /backup/FJSVjs2/webapps

3. Back up the web application.

For JDK

Execute the jar command to back up the Web application in the backup directory. /opt/FJSVawjbk/jdk13/bin/jar cvfM /backup/FJSVjs2/webapps/sample.war /opt/FJSVjs2/webapps/sample

For JRE

Execute the jar command to back up the Web application in the backup directory. tar cvf /backup/FJSVjs2/webapps/sample.tar /opt/FJSVjs2/webapps/sample

Note

If the Servlet gateway environment definition file has been stored in a directory other than /etc/opt/FJSVjs2, execute steps 1, 2, and 3 above. Then, use the following procedure to back up the Servlet gateway environment definition file.

When there are multiple servlet gateway environment definition files, execute the item 2 described below with different backup file names specified.

Conditions

• The Servlet gateway environment definition file is /tmp/FJSVjs2/conf/jsgw.conf.

• The backup directory of the Servlet gateway environment definition file is /backup/FJSVjs2/conf.

Example

1. Create the backup directory of the Servlet gateway environment definition file. mkdir/backup/FJSVjs2/conf


4-43

2. Execute the cp command to back up the Servlet gateway environment definition file. cp /tmp/FJSVjs2/conf/jsgw.conf /backup/FJSVjs2/conf

Refer to Session Registry Server Resource File (Enterprise Edition Only) to restore the environment definition file of the Session Registry server (provided only for Enterprise Edition) using the cp command.

Starting Up Services

Log in with Administrator authority. Start up the services that were stopped in "(1) Stopping Services" with the isstart command. isstart

Start up the service that was stopped with the isstart command. isstart

Note

Services that cannot be started by the isstart command must be started by a separate startup operation. For more information on how to start Interstage, refer to Starting Interstage in Chapter 2.

Restore Procedure This section describes the procedure for restoring Interstage resources (that have been backed up previously) in an emergency situation, such as when resources are damaged.

Note

Before starting the restore procedure, check the following:

• Reinstallation of Interstage, if required, has been completed.

• All services and server applications have been stopped.

• All of the resources (user resources, user applications) used to run Interstage have been allocated in the same directory configuration as the original configuration before backup. This is necessary because the Interstage installation directory cannot be restored.


4-44

Stopping Services

Log in with Administrator authority. Stop all services of Interstage and the server application using the isstop command. isstop -f

Log in as a superuser. Stop all services of Interstage and the server application using the isstop command. isstop –f

Note

Services that are not stopped by the isstop command must be stopped by a separate stopping operation. For more information on how to stop Interstage, refer to Terminating Interstage in Chapter 2.

Restoring Interstage Setup Resource This section explains the setup resource restore procedure that is created when Interstage initialization is performed using the isinit command.

Restore Command

The following command is used for restoring the Interstage setup resource:

C:\Interstage\td\bin\iscrestoresys.exe

/opt/FSUNtd/bin/iscrestoresys

/opt/FJSVtd/bin/iscrestoresys

The iscrestoresys command must be executed when Interstage is stopped.


4-45

Restore Procedure

An example of operation when the resource backup folder is X:\Backup\ is shown below.

Execute the iscrestoresys command. iscrestoresys X:\Backup\

An example of operation, where the resource backup destination directory is /backup, is shown below.

Execute the iscrestoresys command. iscrestoresys /backup

Notes


• Restore the environment definition file of InfoProvider Pro that is defined in the Interstage operation environment definition using the procedure outlined in Restoring Interstage HTTP Server Resources.

• If Interstage is operating, use the isstop -f command to stop Interstage in advance. For a cluster system, stop it according to the cluster system stop procedure.

• If Interstage is operating, use the isstop -f command to stop Interstage in advance.

Restoring Interstage Operation Tool Resource This section explains the Interstage Operation Tool resource restore procedure.

Restore Command

The following command is used for restoring the Interstage Operation Tool resource:

C:\Interstage\gui\bin\isguirestore.bat

/opt/FJSVisgui/bin/isguirestore


4-46

The isguirestore command must be executed while Interstage is stopped. For command details, refer to the Reference Manual (Command Edition).

Restore Procedure

For the isguirestore command, specify the path of the folder in which the operation tool resources were backed up.

An example is shown below. The example assumes that the Interstage installation path is C:\Interstage, the resource backup folder is X:\Backup, and the operation tool resource folder is X:\Backup\isgui.

When restoring to environment that is already initialized by Interstage

1. Execute the isguirestore command. C:\Interstage\gui\bin\isguirestore C:\Interstage X:\Backup\isgui mode1

When restoring to environment immediately after reinstallation of Interstage


Notes


• If any message is output before the command termination message is output, execution of the command has ended with failure. In such a case, execute the command again following the contents of the output message and Notes during execution of this command.

• If the environment definition of the Interstage Operation Tool is not customized and backup operation has not been performed, this restore processing need not be performed.

For the isguirestore command, specify the path of the directory in which the operation tool resources were backed up.


Execute the isguirestore command. isguirestore /backup/isgui

Notes

• If the backup directory contains a blank, the command parameter must be enclosed in " " (double-quotation marks).

• This restore operation does not need to be executed if the Interstage Operation Tool has not been customized or if backup has not been executed.

• The Interstage Operation Tool resource of an extended system cannot be backed up and restored. Manually copy the environment definition file of the Interstage Operation Tool.


4-47

Use the cp or other command to copy the source file of the resource files of the Interstage operation tool in the backup directory to the original directory.

The following shows an example of operation assumed when the resource backup directory is /backup/isgui: Use the cp or other command to copy the resource files of the Interstage operation tool in the backup directory to the original directory. cp /backup/isgui/config /etc/opt/FJSVisgui cp /backup/isgui/httpd_FJSVisgui.conf /etc/opt/FJSVisgui cp /backup/isgui/magic /etc/opt/FJSVisgui cp /backup/isgui/mime.types /etc/opt/FJSVisgui

Note

This restore operation need not be executed if the Interstage Operation Tool has not been customized or backup has not been executed.

Restoring CORBA Service Resource This section explains the CORBA Service resource restore procedure.

Restore Command

The following command is used for restoring the CORBA Service resource:

C:\Interstage\ODWIN\bin\odrestoresys.exe

/opt/FSUNod/bin/odrestoresys

/opt/FJSVod/bin/odrestoresys

The odrestoresys command must be executed in the state that the CORBA Service is stopped.

The odrestoresys command can restore the CORBA Service (ORB) resource, the naming service resource, the loading balance resource, and interface repository resource by specifying the option.

Restore Procedure


The odrestoresys command is executed, and the CORBA Service resource file is restored.


4-48

odrestoresys -r X:\Backup


The odrestoresys command is executed, and the CORBA Service resource file is restored. odrestoresys -r /backup


The odrestoresys command is executed, and the CORBA Service resource file is restored. odrestoresys -r /backup

Note

When using the SSL linkage function, restore the following backed up resources to the directory specified by odsetSSL command.

• Slot information directory (directory specified in -sd option of odsetSSL command)

• Operation control directory (directory specified in -ed option of odsetSSL command)

• SSL environment definition file (ssl.env file) (on WindowsR system or Solaris OE system).

Restoring Event Service Resource This section explains the Event Service resource restore procedure.

Restore Command

The following command is used for restoring the Event Service resource:

C:\Interstage\ESWIN\bin\esrestoresys.exe

/opt/FJSVes/bin/esrestoresys

The esrestore command must be executed when the Event Service is stopped.

Restore Procedure

When restoring Event Service resources, the CORBA Service resource must already have been restored.


4-49

An example is shown below where the backup destination path is X:\Backup\ES.

The directory for the backup is specified by the esrestoresys command, and the Event Service resource is restored. esrestoresys -d X:\Backup

An example is shown below where the backup destination path is /backup/FJSVes.

The directory for the backup is specified by the esrestoresys command, and the Event Service resource is restored. esrestoresys -d /backup

Restoring Portable-ORB Resource This section explains the Portable-ORB resource restore procedure.

Restore Procedure

An example is shown below where the backup destination path is X:\Backup\PORB.

1. Copy the Portable-ORB resource file of the backup directory to the original PORB_HOME directory using the copy command (or Explorer). copy X:\Backup\PORB\config PORB_HOME\etc copy X:\Backup\PORB\initial_hosts PORB_HOME\etc copy X:\Backup\PORB\initial_services PORB_HOME\etc

An example is shown below where the backup destination path is /backup/porb.

Copy the Portable-ORB resource file of the backup directory to the original PORB_HOME directory using the cp command. cp /backup/porb/config PORB_HOME/etc cp /backup/porb/initial_hosts PORB_HOME/etc cp /backup/porb/initial_services PORB_HOME/etc

Note

When using the SSL linkage function, make a copy of the following backed up resources to the original directory: Refer to Portable-ORB Resource File for the details of the following resources:

• Keystore file

• Embedded certificate control information


4-50

Restoring Component Transaction Service Resource This section explains the Component Transaction Service resource restore procedure.

Restore Command

The following command is used for restoring the Component Transaction Service resource:

C:\Interstage\td\bin\tdrestoresys.exe

/opt/FSUNtd/bin/tdrestoresys

/opt/FJSVtd/bin/tdrestoresys

The tdrestoresys command must be executed while Interstage is stopped.

Restore Procedure

An example is shown below where the resource backup destination folder is "X:\Backup\".

The tdrestoresys command is executed. tdrestoresys X:\Backup\

Notes


• Stop Interstage by using the isstop -f command. when Interstage is operating.

• It is necessary to restore the Interstage setup resource and the CORBA Service resource before the Component Transaction Service resource is restored.

An example is shown below where the resource backup destination directory is /backup/td.

Execute the tdrestoresys command. tdrestoresys /backup


4-51

Notes

• If the backup directory contains a space, " " (double-quotation marks) must be used to enclose the parameter.

• The Interstage setup resource and CORBA Service resource must be restored before the Component Transaction Service resource is restored.

• If Interstage is running, stop Interstage using the isstop -f command.

• If Interstage is running, stop Interstage using the isstop -f command.

Restoring Database Linkage Service Resource This section explains the Database Linkage Service resource restore procedure.

Restore Command

The following command is used for restoring the Database Linkage Service resource:

C:\Interstage\ots\bin\otsrestoresys.exe

/opt/FSUNots/bin/otsrestoresys

/opt/FJSVots/bin/otsrestoresys

The otsrestoresys command must be executed when Interstage is stopped.

Restore Procedure

An example is shown below where the resource backup destination folder is "X:\Backup\".

The otsrestoresys command is executed. otsrestoresys X:\Backup\


4-52

Notes


• Stop the cluster system by the method appropriate to it.

• It is necessary to restore the Interstage setup resource and the CORBA Service resource before the Database Linkage Service resource is restored.

• To restore resources (using the isinit or otssetup command) to an environment in which set up of the Database Linkage Service has not been implemented, a system log file must be created after import. To regenerate a system log file, execute the otsmklog command. If setup has already been completed, it is not necessary to execute the otsmklog command.

An example is shown below where the resource backup destination directory is /backup/.

Execute the otsrestoresys command. otsrestoresys /backup/

Notes

• If the backup directory contains a space, the command parameter must be enclosed in double quotes ("").

• It is necessary to restore the Interstage setup resource and the CORBA Service resource before the Database Linkage Service resource is restored.

• If Interstage is running, stop Interstage using the isstop -f command. Stop the cluster system using the cluster system stop method.

• The Interstage setup resource and CORBA Service resource must be restored before the Database Linkage Service resource is restored. To restore resources (using the isinit or otssetup command) to an environment in which set up of the Database Linkage Service has not been implemented, a system log file must be created after import. To regenerate a system log file, execute the otsmklog command. If setup has already been completed, it is not necessary to execute the otsmklog command.

Restoring Interstage HTTP Server Resources The following explains the restore procedure for Interstage HTTP Server resources.

Restore Procedure

The following shows an example when the backup destination path is X:\Backup\IHS.


4-53

Use the copy command (or Explorer) to copy the Interstage HTTP Server resources in the backup directory to the original directory. copy X:\Backup\IHS\httpd.conf C:\Interstage\F3FMihs\conf copy X:\Backup\IHS\ password file any directory (*1)

The following shows an example when the backup destination path is /backup/FJSVihs.

Use the cp command to copy the Interstage HTTP Server resources in the backup directory to the original directory. cp /backup/FJSVihs/httpd.conf /etc/opt/FJSVihs/conf cp /backup/FJSVihs/ password file any directory (*1)

*1) If a password file is created using the htpasswd command for user authentication, copy the password file to the storage directory of the password file specified in the AuthUserFile directive of the httpd.conf file.

Note

When the content and the file used in setting the environment (other than httpd.conf ) and the password file were backed up, restore the corresponding files.

When using the SSL linkage function, restore the following backed up resources to the path specified in the corresponding directive of httpd.conf file:

• Slot information directory (directory specified in SSLSlotDir directive of httd.conf file)

• Operation control directory (directory specified in SSLEnvDir directive of httd.conf file)

• User PIN control file (file specified in SSLUserPINFile directive of httd.conf file)

Restoring InfoProvider Pro Resource (Windows® and Solaris Only) This section explains the InfoProvider Pro resource restore procedure.

To restore the InfoProvider Pro resource, execute the ipprestore command.

Restore Command

The following command is used for restoring the InfoProvider Pro resource.

C:\Interstage\F3FMwww\Program\ipprestore.exe

/opt/FSUNprovd/bin/ipprestore

The ipprestore command must be executed while Interstage is stopped.


4-54

Restore Procedure

When there are two or more environments to restore, modify the backup destination path and repeat the following operation.


• The filename of the applicable environment definition file is F3FMwww.dat.


Restore the InfoProvider Pro resource by executing the ipprestore command.

• When restoring only the environment definition information: C:\Interstage\F3FMwww\Program\ipprestore -d X:\Backup

• When restoring the environment definition information and contents (usable only when the -t all option is specified at backup): C:\Interstage\F3FMwww\Program\ipprestore -d X:\Backup -t all

An example (assuming the following conditions) is shown below.

• The filename of the applicable environmental definition file is /etc/opt/FSUNprovd/HTTPD.conf.


Restore the InfoProvider Pro resource by executing the ipprestore command.

• When restoring only the environment definition information: /opt/FSUNprovd/bin/ipprestore -d /backup

• When restoring the environment definition information and contents (usable only when the -t all option is specified at backup): /opt/FSUNprovd/bin/ipprestore -d /backup -t all

Note

If the executable file to be restored is already present, it will not be restored. To restore a current file, delete the target file and then perform the restoration. For details, refer to the Reference Manual (Command Edition).


4-55

Note

When using the SSL linkage function, restore the following resources to the path specified in the corresponding definition item of the SSL environment definition file:

• Slot information directory (directory specified in the slot information directory definition item of the SSL environment definition file)

• Operation control directory (directory specified in the operation control directory definition item of the SSL environment definition file)

Restoring J2EE Common Resource File The procedure for restoring the J2EE Common resource file is explained.

Restore Command

Use the following command to restore the J2EE common resource file:

C:\Interstage\J2EE\bin\j2eerestore.exe

/opt/FJSVj2ee/bin/j2eerestore

The j2eerestore command can only be executed while Interstage is stopped.

Restore Procedure

The following is an example of operation when the backup destination path is X:\Backup:

1. Check that the directory in which the jar command is stored is contained in the environment variable path. (*1)

2. Execute the j2eerestore command to restore the J2EE common resource file. C:\Interstage\j2ee\bin\j2eerestore -d X:\backup

The following is an example of operation when the backup destination path is /backup:

1. Confirm that the directory in which the jar command is stored is contained in the environment variable path. (*1)

2. Execute the j2eerestore command to restore the J2EE common resource file. /opt/FJSVj2ee/bin/j2eerestore -d /backup (*2)


4-56

(*1) This check is required because the j2eerestore command uses the jar command for internal processing.

(*2) The example here shows a situation in which resources are restored to a default system. For the Solaris OE version, the j2eerestore command to restore resources to a system other than the default system has the following format: /opt/FJSVj2ee/bin/j2eerestore -d /backup -M <system name>

Restoring IJServer Resource File The procedure for restoring the IJServer resource file is explained.

Restore Command

Use the following command to restore the IJServer resource file:

C:\Interstage\J2EE\bin\ijsrestore.exe

/opt/FJSVj2ee/bin/ijsrestore

Restore Procedure

The following is an example of operation when the backup destination path is X:\Backup:

Execute the ijsrestore command to restore the IJServer resource file. C:\Interstage\j2ee\bin\ijsrestore -d X:\backup

The following is an example of operation when the backup destination path is /backup:

Execute the ijsrestore command to restore the IJServer resource file. /opt/FJSVj2ee/bin/ijsrestore -d /backup


4-57

Note

Before restore the IJServer resource file, it is necessary to restore the following:

• Interstage setup resources

• CORBA Service resources

• Component Transaction Service resources

• J2EE Common resources

Restoring Interstage JMS Resource The procedure for restoring the Interstage JMS resource is explained.

Restore Command

Use the following command to restore the Interstage JMS resource:

C:\Interstage\JMS\bin\jmsrestore.exe

/opt/FJSVjms/bin/jmsrestore

Note: The jmsrestore command must be executed while the JMS application is stopped.

Restore Procedure

An example of operation when the backup destination path is X:/Backup is shown below.

Enter the jmsrestore command, with the backup folder specified, to restore the Interstage JMS resource. jmsrestore -d X:\Backup

An example of operation when the backup destination path is /backup is shown below.

Enter the jmsrestore command, with the backup directory specified, to restore the Interstage JMS resource. jmsrestore -d /backup


4-58

Restoring Servlet Service for Interstage Management Console Resources This section describes the procedure for restoring the resources of the Servlet Service for Interstage Management Console.

Restore Procedure

An example is shown below where the path of the backup folder is X:\Backup.

Execute the jsrestore command to restore the environment definition file. C:\Interstage\F3FMjs2su\bin\jsrestore X:\Backup

An example is shown below where the path of the backup directory is /backup.

Execute the jsrestore command to restore the environment definition file. /opt/FJSVjs2su/bin/jsrestore /backup

Restoring SOAP Service The procedure for restoring the SOAP Service resource is explained.

Restore Command

The following command is used for restoring the SOAP Service resource. It is required for each environment definition file (except for the Servlet Service resource file): C:\Interstage\F3FMsoap\bin\issoaprestore.exe

The following command is used for restoring the SOAP Service resource. It is required for each environment definition file (except for the Servlet Service resource file): /opt/FJSVsoap/bin/issoaprestore

Restore Procedure

Use the issoaprestore command to restore the SOAP Service resource file in the backup directory into the original directory.

An example under the following conditions is shown below:

• The backup directory is X:\Backup\SOAP.


4-59

• Web service information management file is located in C:\Interstage\F3FMsoap\deploy\server-config.wsdd.

Example

1. Stop Interstage operation control Servlet service and Servlet service. C:\Interstage\F3FMjs2su\bin\jssvstop C:\Interstage\F3FMjs2\bin\jssvstop jscontdisp

2. Execute the issoaprestore command to restore the environment definition file. C:\Interstage\F3FMsoap\bin\issoaprestore -a c -d X:\Backup\SOAP

Use the issoaprestore command to restore the SOAP Service resource file in the backup directory into the original directory.

An example under the following conditions is shown below:

• The backup directory is /backup/SOAP.

• Web service information management file is located in /opt/FJSVsoap/deploy/server-config.wsdd.

Example

1. Stop Interstage operation control Servlet service and Servlet service. /opt/FJSVjs2su/bin/jssvstop /opt/FJSVjs2/bin/jssvstop

2. Execute the issoaprestore command to restore the environment definition file. /opt/FJSVsoap/bin/issoaprestore -a -d /backup/SOAP

Note

Because the SOAP Service is a Web application, restore the IJServer resource file as well. For details, refer to Restoring IJServer Resource File.

Restoring InfoDirectory Resource This section explains the InfoDirectory resource restore procedure.


4-60

Restore Procedure

An example is shown below where the backup destination path is X:\Backup\ID.

1. Restore DSA. Use Explorer to copy back to the directory under the original folder.

2. Copy the property file of the control client to the original folder using the copy command. copy X:\Backup\ID\etc\* C:\Interstage\Id\Mgr\etc\techMgr

3. When SSL is used, copy the SSL environment file back to the original folder using the copy command. copy X:\Backup\ID\ldap\sslconfig.cfg C:\Interstage\Id\Dir\ldap

4. When Web connector SSL is used, copy the Web connector environment back to the original folder using the copy command. copy X:\Backup\ID\web\infodir.conf C:\Interstage\Id\Dir\web copy X:\Backup\ID\web\infodir.fmap C:\Interstage\Id\Dir\web copy X:\Backup\ID\web\infodir.at C:\Interstage\Id\Dir\web copy X:\Backup\ID\web\ldapfriendly C:\Interstage\Id\Dir\web copy X:\Backup\ID\web\ldapfriendly.modify C:\Interstage\Id\Dir\web

An example is shown below where the backup destination path is /backup/id and the DIB installation directory is /opt/dib.

1. Restore DSA. Use the cp command to copy back to the directory under the original directory. cp -r /backup/id/dib/dsa /opt/dib

2. Copy the property file of the control client to the original directory using the cp command. cp -r /backup/id/etc/techMgr /opt/FJSVdirs/etc

3. When SSL is used, copy the SSL environment file back to the original directory using the cp command. cp /backup/id/ldap/sslconfig.cfg /opt/FJSVildap/etc

4. When Web connector is used, copy the Web connector environment back to the original directory using the cp command. cp /backup/id/web/* /opt/FJSVidweb

Note

When restoring DSA, be sure to stop DSA beforehand.


4-61

Restoring Interstage Certificate Environment Resources This section explains the procedure for restoring the Interstage Certificate Environment resources.

Restore Procedure

An example of the operation to be performed when the backup destination path is X:\Backup\scs is shown below:

Use the xcopy command (or Explorer) to copy the Interstage Certificate Environment resources from the backup directory back to the original directory. xcopy /E X:\Backup\scs C:\Interstage\etc\security

An example of the operation to be performed when the backup destination path is /backup/scs is shown below:

Use the cp command to copy the Interstage Certificate Environment resources from the backup directory back to the original directory. cp -rp /backup/scs/security /etc/opt/FJSVisscs

Note

Restore the resources back to the original directory, which was used before backup, with the same authority.

The Interstage Certificate Environment can be accessed from the group specified during environment configuration. For this reason, restore also system information on the user accounts and groups as needed.

Restoring Old Version Servlet Service Resource This section explains the old version Servlet Service resource restore procedure.

Restore Command

The following commands are used for restoring the old version Servlet Service resource.

Each environment definition file(except for Web application environment definition file): C:\Interstage\F3FMjs2\bin\jsrestore.exe Web application(including Web application environment definition file):


4-62

C:\Interstage\JDK13\bin\jar.exe(When JDK1.3 is installed at "C:\Interstage\JDK13") xcopy command (JRE)

Each environment definition file (except for Web application environment definition file): /opt/FJSVjs2/bin/jsrestore Web application (including Web application environment definition file): /opt/FJSVawjbk/jdk13/bin/jar (When JDK1.3 is installed at "/opt/FJSVawjbk/") tar command (JRE)

Restore Procedure


When there are two or more Web applications, perform step 2 above for each of them.

Conditions


• The backup folder of the Web application is X:\Backup\F3FMjs2\webapps

• The backup name of the Web application is sample.war (JDK)

• The storage folder of the Web application is C:\Interstage\F3FMjs2\webapps\sample

Example

1. Execute the jsrestore command to restore the environment definition file. C:\Interstage\F3FMjs2\bin\jsrestore X:\Backup

2. Restore the Web application.

For JDK, execute the jar command to restore the web application C:\Interstage\JDK13\bin\jar xvf X:\Backup\F3FMjs2\webapps\sample.war

For JRE, execute the xcopy command to restore the Web application. xcopy /E /K /I X:\Backup\F3FMjs2\webapps\sample C:\Interstage\F3FMjs2\webapps\sample

Note

To restore a Servlet gateway environment definition file stored in a location other than C:\Interstage\F3FMjs2\conf, execute steps 1 and 2 above. Then, use the following procedure to restore the Servlet gateway environment definition file.


4-63


Conditions

• The backup filename of the Servlet gateway environment definition file is X:\Backup\F3FMjs2\conf\jsgw.conf.

• The storage folder of the Servlet gateway environment definition file is C:\tmp\F3FMjs2\conf.

Example

Execute the copy command to restore the Servlet gateway environment definition file. copy X:\Backup\F3FMjs2\conf\jsgw.conf C:\tmp\F3FMjs2\conf

Conditions


• The Web application backup directory is /backup/FJSVjs2/webapps/

• The Web application backup filename is sample.war (JDK).

• The Web application backup filename is sample.tar (JRE).

• The Web application storage directory is /opt/FJSVjs2/webapps/sample.

Example

1. Execute the jsrestore command to restore the environment definition file. /opt/FJSVjs2/bin/jsrestore /backup

2. For JDK, execute the jar command to restore the Web application. /opt/FJSVawjbk/jdk13/bin/jar xvf /backup/FJSVjs2/webapps/sample.war - For JRE tar xvf /backup/FJSVjs2/webapps/sample.tar

Note

To restore a Servlet gateway environment definition file that has been stored in a directory other than /etc/opt/FJSVjs2, execute steps 1 and 2 above. Then, use the following procedure to restore the Servlet gateway environment definition file.


Conditions

• The backup filename of the Servlet gateway environment definition file is /backup/FJSVjs2/conf/jsgw.conf.

• The storage directory of the Servlet gateway environment definition file is /tmp/FJSVjs2/conf.

Example

Execute the cp command to restore the Servlet gateway environment definition file.


4-64

cp /backup/FJSVjs2/conf/jsgw.conf /tmp/FJSVjs2/conf

Refer to Session Registry Server Resource File (Enterprise Edition Only) to restore the environment definition file of the Session Registry server (provided only for Enterprise Edition) using the cp command.

Starting Up the Services

Log in with Administrator authority. Start up the services that were stopped by "(1) Stopping Services" using the isstart command. isstart

Start up the services that were stopped previously by "(1) Stopping Services" using the isstart command. isstart

Notes

• Services that cannot be started by the isstart command must be started using their own startup operation. For more information on how to start Interstage, refer to Starting Interstage in Chapter 2.

• If service startup fails after importing the resource, check whether there is a shortage of the imported resources or an error in the importing procedure before taking the action in the output message.

Moving Resources to Another Server

4-65

Moving Resources to Another Server This section explains copying (moving) the Interstage resources or moving the application environment to another server.

Resources can be exported from the server (movement source server) in which the Interstage application environment is configured, and imported into the copy destination server (destination server). The copy destination server can configure the equivalent application environment without prior initialization of the Interstage application environment.

Note

When moving resources, the destination server must have the same system configuration as that of the movement source server.

• Operating system

• Interstage version level

• Interstage installation path

• Interstage services used

• Storage path of user application and resource files

The files that can be moved are the files held by Interstage for defining the application environment. User applications cannot be moved. Move them by other appropriate means.

InfoDirectory resources cannot be moved to other servers. Specify the required setup in the respective servers.


4-66

Overview and Applicable Files Movement of resources to other servers is performed to copy the Interstage environment that is configured on one server machine to another server machine, setting the same configuration in the destination servers. The destination servers do not need the Interstage initial setting or the initial setting of other services, and the environment configuration does not need to be set in each server. Setting of the server application environment in multiple machines can therefore be accomplished in a short period of time.

Use the following procedure to move resources:

1. Export the resources to the backup disk from the source server.

2. Copy the resources that are saved in the backup disk to the destination server.

3. Import the resources that are saved in the backup disk of the destination server.

Figure 4-2 shows an overview of moving resources to another server.

Figure 4-2 Moving Resources to Another Server

Applicable Resources

The files that can be moved are the same as the case of backup restoration. Refer to Outline and Applicable Resources

To transfer the following resources/files to the other server collectively, refer to Collective Maintenance.


4-67

Resource Exporting Procedure The Interstage resource export procedure is the same as the backup procedure on the same machine. Refer to Backup Procedure.

Resource Importing Procedure This section explains the importing procedure of the destination server when importing Interstage resources.

This explanation assumes that the backup resource storage folder of X:\Backup already exists.

This explanation assumes that the backup resource storage directory of /backup already exists.

Note

Perform the resource importing procedure after confirming the following:

• Interstage installation has been completed.

• The Interstage installation directory and any resources (such as user resources and user applications used in the Interstage application) that cannot be restored have already been configured in the same folder configuration as in the resource exporting server.

• All services and all server applications have been stopped.

Stopping Services

Log in with Administrator authority. Stop all of the Interstage services and server applications using the isstop command.

Stop all of the Interstage services and server applications using the isstop command (or other appropriate commands). isstop -f

Note

Services that are not stopped by the isstop command must be stopped by a separate stopping operation. For more information on how to stop Interstage, refer to Terminating Interstage in Chapter 2.


4-68

Importing Interstage Setup Resource This section explains the setup resource importing procedure that is created at the time of Interstage initialization using the isinit command.

Import Command

The following command is used for importing the Interstage setup resource.

C:\Interstage\td\bin\iscrestoresys.exe

/opt/FSUNtd/bin/iscrestore

/opt/FJSVtd/bin/iscrestore

The iscrestoresys command must be executed while Interstage is stopped.

Import Procedure

An example is shown below. The example assumes that the resource backup folder is X:\Backup\ and the host name used by the CORBA Service is hostname.

Execute the iscrestoresys command. iscrestoresys -h hostname X:\Backup\

Notes


• If Interstage is running, enter the isstop -f command to stop it in advance. For a cluster system, stop it according to the cluster system stop procedure.


4-69

An example is shown below where the resource backup destination directory is /backup/isc.

Execute the iscrestoresys command. iscrestoresys -h hostname /backup

In the Interstage setup resource import, the following items (that are definition items of the Interstage operating environment definition) can be customized using the restore definition file.

• Corba Host Name (host name that operates the CORBA Service)

• Corba Port Number (port number used for CORBA communication)

• IR Path for DB file (directory in which the database used in the Interface Repository is created)

• TD path for system (directory in which the operating environment of the Component Transaction Service is created)

• InfoProviderPro Definition (environment definition file name and identifier of the Web server)

• SSL Port Number (port number used for SSL linkage)

Create a restore definition file that describes the definition information after any definition content changes for the definition items above, then specify the file in the -f option of the iscrestoresys command. Describe the restore definition file in the same way as the Interstage operating environment definition. A restore definition file example and operational example using a restore definition file are shown below.

• Import conditions

− Change Corba Host Name to host1.

− Change Corba Port Number to 8003.

− Change IR Path for DB file to "/IRPATH".

− Change TD path for system to "/TDPATH".

• Restore definition file (/BKUP/rest.txt) Corba Host Name=host1 Corba Port Number=8003 IR Path for DB file=/IRPATH TD path for system=/TDPATH

• Command execution example Execute the iscrestoresys command. iscrestoresys -f /BKUP/rest.txt /backup


4-70

Notes

• If the backup directory contains a blank, " " (double-quotation marks) must be used to enclose the parameter.

• If Interstage is running, enter the isstop -f command to stop it in advance. Stop cluster systems according to the cluster system stop procedure.

Importing Interstage Operation Tool Resource The Interstage Operation Tool resource importing procedure is explained.

Import Command

The following command is used for importing the Interstage Operation Tool resource.

C:\Interstage\gui\bin\isguirestore.bat

/opt/FJSVisgui/bin/isguirestore

The isguirestore command must be executed while Interstage is stopped. For details of the command, refer to the Reference Manual (Command Edition).

Import Procedure

For the isguirestore command, specify the path of the folder into which the operation tool resource was exported.

An operation example is shown below. The example assumes that the Interstage installation path is C:\Interstage, the resource backup folder is X:\Backup, and the operation tool resource folder is X:\Backup\isgui.


2. When the following items are specified in the Web server environment definition file for the Interstage Operation Tool, use an editor to modify the setup values to the appropriate values to suit each importing machine.

− Host name (definition name:hostname)

− IP address (definition name:IP-address)

Notes



4-71

• If any message is output before the command termination message is output, execution of the command has ended with failure. In such a case, execute the command again following the contents of the output message and Note during execution of this command.

• If the environment definition of the Interstage Operation Tool is not customized and no exporting has been performed, this import operation need not be performed.


1. Execute the isguirestore command. isguirestore /backup/isgui

2. When the following items are specified in the Web server environment definition file (/etc/opt/FJSVisgui/FJSVisgui.dat) for the Interstage Operation Tool, modify the setup values to the appropriate values for each importing machine using an editor or similar. Host name (definition name:hostname) IP address (definition name:IP-address)

Note

If the backup directory contains a blank, " " (double-quotes) must be used to enclose the command parameter.

Importing CORBA Service Resource The section explains importing the CORBA Service resource.

Import Command

The following command is used for importing the CORBA Service resource.

C:\Interstage\ODWIN\bin\odrestoresys.exe

/opt/FSUNod/bin/odrestoresys

/opt/FJSVod/bin/odrestoresys

The odrestoresys command must be executed in the state that the CORBA Service ("OD_start") is stopped. Confirm the state of service by "Service" of system control panel.


4-72

By specifying the option, the odrestoresys command can be imported by changing the hostname and the portnumber set in the CORBA Service resource file (the file under the control of config, inithost/initial_hosts, init_svc/initial_services, impl.db, and the CosNaming directory). Or, change the destination of the storage in the database of the interface repository service resource. The procedure when not changing these settings, it is the same as the restoration procedure on the same machine. Refer to Restoring CORBA Service Resource.

When using the SSL linkage function, execute the odsetSSL command corresponding to the import destination SSL environment.

Import Procedure


The odrestoresys command is executed, and the CORBA Service resource file is imported. odrestoresys -h hostname -p 8002 -irpath X:\Interstage2\TD\var\IRDB X:\Backup


The odrestoresys command is executed, and the CORBA Service resource file is imported. odrestoresys -h hostname -p 8002 -irpath /opt2/FSUNtd/var/IRDB /backup


The odrestoresys command is executed, and the CORBA Service resource file is imported. odrestoresys -h hostname -p 8002 -irpath /opt2/FJSVtd/var/IRDB /backup

Importing Event Service Resource The importing procedure of the Event Service resource is the same as the restore procedure on the same machine. Refer to Restoring Event Service Resource.

Importing Portable-ORB Resource The Portable-ORB resource importing procedure is the same as the restore procedure on the same machine. Refer to Restoring Portable-ORB Resource.

Importing Component Transaction Service Resource This section explains the importing procedure for the Component Transaction Service resource. Refer to Restoring Component Transaction Service Resource.


4-73

Importing Database Linkage Service Resource This section explains the procedure for importing the Database Linkage Service resource. Before importing the Database Linkage Service resource, Importing CORBA Service Resource must be completed. However, the following notes apply.

Notes

• If resources are imported to an environment where the Database Linkage Service is not set up by the isinit or otssetup command, a system log file must be created after importing. Use the otsmklog command to recreate a system log file. If the service has already been set up, the otsmklog command need not be executed.

• In a cluster environment, specify a path on the shared disk for REPOSITORY in the C:\Interstage\ots\systeminfo\system file to copy the C:\Interstage\ots\etc\repository directory to the specified directory on the share disk. Do this after the otsrestoresys command ends normally.

• On normal termination of the otsrestoresys command in a cluster environment, copy the REPOSITORY of the /opt/FSUNots/systeminfo/system file and the /opt/FSUNots/etc/repository which was specified as the shared disk for the whole directory, to the directory specified in shared disk path.

Importing Interstage HTTP Server Resource The procedure for importing the Interstage HTTP Server resource is the same as the restore procedure on the same machine. Refer to Restoring Interstage HTTP Server Resources. When using the SSL linkage function, refer to the Security System Guide and restructure the SSL environment setting.

After the restore, set the following setting in the environment definition file (httpd.conf) of the Interstage HTTP Server:

• Set the host name (or IP address) of import destination to ServerName directive. If there is another directive that sets the host name (or IP address) of export origin, set the host name (or IP address) of import destination to the corresponding directive.

• If the port number setting are different between the export origin and import destination, set the port number of import destination to the directive that sets the port number.

Importing InfoProvider Pro Resource (Windows® and Solaris Only) The procedure for importing the InfoProvider Pro resource is the same as the restore procedure on the same machine. Refer to Restoring InfoProvider Pro Resource (Windows® and Solaris Only). When using the SSL linkage function.

After the restore, set the following setting in the environment definition file of the InfoProvider Pro:

• Hostname (definition name:hostname)

• IP address (definition name:IP-address)

Importing J2EE Common Resource File The procedure for importing the J2EE common resource file is the same as the restore procedure on the same machine. Refer to Restoring J2EE Common Resource File.


4-74

Importing IJServer Resource File The procedure for importing the IJServer resource file is the same as the restore procedure on the same machine. Refer to Restoring IJServer Resource File.

Importing Interstage JMS Resource The procedure for importing the Interstage JMS resource is the same as the restore procedure on the same machine. Refer to Restoring Interstage JMS Resource.

Importing Servlet Service for Interstage Management Console Resources The procedure for importing the resources of the Servlet Service for Interstage Management Console is the same as the restore procedure on the same machine. Refer to the Restoring Servlet Service for Interstage Management Console Resources.

Importing SOAP Service Resource The procedure for importing the SOAP Service resource is the same as the restore procedure on the same machine. Copy the service resource file from the backup folder. Refer to Restoring SOAP Service.

Importing Interstage Certificate Environment Resources The procedure for importing the Interstage Certificate Environment resources is the same as the restore procedure on the same machine. Refer to Restoring Interstage Certificate Environment Resources.

Notes

The Interstage Certificate Environment resources can be accessed from the group specified during environment configuration. For this reason, match the system information on user accounts and groups with that on the import source machine. Alternatively, create a group for accessing the Interstage Certificate Environment and redefine it using the scsmakeenv command.

Importing Old Version Servlet Service Resource The old version Servlet Service resource importing procedure is the same as the restore procedure on the same machine. Refer to Restoring Old Version Servlet Service Resource. After performing the import, check the setting for the IP address.

Starting Up Services

Log in with Administrator authority. Use the isstart command to start up the services that were stopped in "(1) Stopping Services".

Log in as a superuser. Use the isstart command to start services that were stopped previously. isstart


4-75

Notes

• Services that cannot be started using the isstart command must be started by a separate startup operation. For more information on how to start Interstage, refer to Starting Interstage in Chapter 2.

• If startup of the service fails after importing the resource, check if there is a shortage of the imported resources or an error in the importing procedure before taking the action described in the output message.


4-76

Collective Maintenance The samples of a batch file (Windows(R)) and a Shell script (Solaris OE and Linux) for executing Backing Up and Restoring Resources and Moving Resources to Another Server collectively are provided. Users are able to operate collectively when specifying the procedures suitable for respective environments to a batch file (Windows(R)) and a Shell script (Solaris OE and Linux).

Correct the sample batch file (Windows(R)) and the Shell script (Solaris OE and Linux) if necessary.

In some cases, additional operations may be required in each service after collective maintenance. See respective service procedures of Backing Up and Restoring Resources and Moving Resources to Another Server for details.

Resource Backup/Export The sample collective procedures for Interstage resource backup and export are provided.

C:\Interstage\sample\backup_restore\isbackup.bat

/opt/FJSVisas/sample/backup_restore/isbackup

isbackup describes the procedures of Interstage backup and export as an instruction.

Each process has a comment in the format shown below according to the processing content. #============================================ # Number Explanation of alphanumeric characters #============================================

Collective Maintenance

4-77

Process Outline

Explanation of each process outline

Comment Process content

:DEFINITION_PART Backup target definition

:PROCEDURE_PART Main process


0. Environment Check Authorization check.

1. check the input parameter Command parameter check.

2-1. set the restore CO Command name variable definition.

2-2. set the section name list Backup target variable definition.

2-3. get the file line and set line = 0

2-4. check the def file format

2-5. check sub-routines

Syntax analysis of backup target resource files6.

3. MAIN Main process

4. Sub-Routines Backup process of backup target resources

Backup/Export Process of Backup Target Resources

Backup/export process is delimited using the format shown below at each backup target resource. ## Service name START : (Backup process description) ## Service name END

Service names (changeable) correspond to the backup resources as listed below.

Service name Backup target resources

ISCOM Backup of Interstage setup resources

GUI Backup of Interstage Operation Tool resources

OD Backup of CORBA service resources

ES Backup of Event service resources

PORB Backup of Portable-ORB resources

TD Backup of Component Transaction service resources

OTS Backup of Database Linkage Service resources


4-78

Service name Backup target resources

IPP Backup of InfoProvider Pro resources

IJServer Backup of IJServer resources

JS2 Backup of old version Servlet service resources

EJB Backup of EJB service resources

InfoDir Backup of InfoDirectory service resources

SOAP Backup of SOAP service resources

JMS Backup of Interstage JMS resources

J2EE Backup of J2EE common resources

IHS Backup of Interstage HTTP server resources

JS2SU Backup of Servlet Service for Interstage Management Console resources

ISSCS Backup of Interstage Certificate Environment resources

Operation Procedures

Procedures of resource backup/export using the isbackup command are described below.


Log in with Administrator authority, and use the isstop command to stop all the Interstage services and server applications.

Use the isstop command to stop all the Interstage services and server applications. isstop -f

Note

Services that are not stopped by the isstop command must be stopped by using a separate stopping operation. For more information on how to stop Interstage, refer to Terminating Interstage.

Backup/Export Target Resource Definition

Define Interstage backup target resources in the batch file.

Use the following syntaxes to define the target resources:

Define Interstage backup target resources in the backup target definition file.


4-79

The backup target definition file can be created with an arbitrary name according to the following syntaxes:

For details, refer to Backup Procedure and Resource Exporting Procedure.

The sample of the backup target resource definition file is provided below.

Define Interstage backup target resources in the batch file.

/opt/FJSVisas/sample/backup_restore/sample.def

Define Interstage backup target resources in Shell.

Description Format

Write one definition on a single line in the batch file rem [Section name] set definition name = Definition value

Write one definition on a single line in the definition file. [Section name] definition name = Definition value

Write one definition on a single line in the shell. # [Section name] set definition name = Definition value

Note

• Write "[", "]", and "=" in en-size characters.

• When writing a comment, write # after the definition value. Do not specify # at the top of a line.


4-80

Definition Item List

Backup target items are listed below.

• Section names or definition names cannot be omitted.

• Definition values are indicated as below. o: required -: can be omitted x: cannot be specified

Section name

Explanation of section name

Definition name

Definition value

Explanation Remarks

INST_DIR Directory o

Interstage installation directory

Change according to the installation environment.

Common Specifies basic information in operation.

COMMON_PATH

Directory o

Specifies a directory that stores the backup/export resources.

ISCOM Species Interstage setup resource-related items.

ISCOM_TARGET

on or off o

An operation target when specifying "on." Not an operation target when specifying "off."

GUI Specifies Interstage operation tool-related items.

GUI_TARGET on or off o


OD Specifies CORBA service-related items.

OD_TARGET on or off o


ES Specifies event service-related items.

ES_TARGET on or off o



4-81

Section name


Definition name

Definition value

Explanation Remarks

PORB Specifies Portable-ORB-related items.

PORB_TARGET

on or off o

An operation target when specifying "on." Not an operation target when specifying

TD Specifies component transaction service-related items.

TD_TARGET on or off o


OTS Specifies database linkage service-related items.

OTS_TARGET

on or off o


IPP_TARGET on or off o


IPP_OPTION_1

1 or 2 o

Specifies operation target resources.

1. Environment definition information

2. Environment definition information and content

IPP Specifies InfoProvider Pro-related items.

IPP_SOURCE_1

File name o

Specifies InfoProvider Pro environment definition file.

Required specifying in pairs. (*6)

IJServer Specifies IJServer related items.

IJSERVER_TARGET

on or off o


JS2 Specifies old version Servlet service-related items.

JS2_TARGET on or off o



4-82

Section name


Definition name

Definition value

Explanation Remarks

JS2_OPTION 1 , 2 or 3 o



2. Web application

3. Environment definition information and Web application

JS2_CMD_1 jar or xcopy

When 1 is specified to jar or xcopy JS2_OPTION:

-

When other than 1 is specified to JS2_OPTION:

o

Specifies the command used for backup.

SORCE_DIR_1

Directory

When 1 is specified to directory JS2_OPTION:

-

When other than 1 is specified to directory JS2_OPTION:

o

Specifies the directory that stores the operation target application.

Required specifying in pairs. (*6


4-83

Section name


Definition name

Definition value

Explanation Remarks

EJB_TARGET on or off o


EJB Specifies EJB service-related items.

EJB_EJBAPP Directory

o

Specifies the folder that stores EJB application.

INFODIR_TARGET

on or off o


InfoDir Specifies InfoDirectory service-related items.

INFODIR_SOURCE

Directory

o

Directory that created backup target DSA

Multiple directories can be specified. (*8)

SOAP_TARGET

on or off o


SOAP Specify SOAP service-related items.

SOAP_SOURCE

File path

-

Specifies backup target files such as Web service information control file and security environment setup.


JMS Specifies Interstage JMS-related items.

JMS_TARGET

on or off o


J2EE Specifies J2EE shared resource-related items.

J2EE_TARGET

on or off o



4-84

Section name


Definition name

Definition value

Explanation Remarks

IHS_TARGET on or off o


IHS_OPTION 1 or 2 Specifies the operation target resources from below.


2. Environment definition information and password file.

IHS Specifies Interstage HTTP Server-related items.

IHS_PASSWD_SOURCE

File path

When the file path IHS_OPTION is 1.:

-

When the file path IHS_OPTION is other than 1:

o

Specifies the backup target password file.

JS2SU Specifies Interstage operation control Servlet service-related items.

JS2SU_TARGET

on or off o


ISSCS Specifies Interstage Certificate Environment-related items.

ISSCS_TARGET

on or off An operation target when specifying "on." Not an operation target when specifying "off."


4-85

Section name


Definition name

Definition value

Explanation Remarks

host Hpst namex

Specifies only in restore or import.

path Directory o



target_server x Specifies only in restore or import.

target on or off o



source File path

x



target on or off o


target on or off o


Specifies "on" whenever [EJB] section target is "on."

port Port number

x



db_path Directory

x



target on or off o



4-86

Section name


Definition name

Definition value

Explanation Remarks


target on or off o



target on or off o




target on or off o


target on or off o


option 1 or 2 o





source File name o




target on or off o



4-87

Section name


Definition name

Definition value

Explanation Remarks

target on or off o


option 1 , 2 or 3 o



2. Web application


cmd jar or tar

When 1 is specified to jar or tar option:

-

When other than 1 is specified to option:

o


JS2 Specifies old version Servlet service-related items.

source_dir Directory

When 1 is specified to directory option:

-

When other than 1 is specified to directory option:

o




target on or off o



4-88

Section name


Definition name

Definition value

Explanation Remarks

ejbapp Directory

o


The default directory is the operation target when omitted. (*7)

target on or off o



source Directory

o



target on or off o



source File path

-




target on or off o


(*4)


target on or off o


(*5)


4-89

Section name


Definition name

Definition value

Explanation Remarks

target on or off o


option 1 or 2 Specifies the operation target resources from below.



passwd_source

File path

When the file path option is 1.: -

When the file path option is other than 1:

o



passwd_target Directory

x



target on or off o



ISSCS_TARGET


*1 : Multiple backup target directories can be specified to [JS2] section.


4-90

To specify multiple directories, change :DEFINITION_PART and :PROCEDURE_PART of the batch file. In this batch file, two files are defined as samples, and the second file has a comment. Therefore, remove the comment in using the file. For the third file (and after), copy and change the corresponding parts and then execute the batch process.

Example

:DEFINITION_PART ... rem [JS2] set JS2_TARGET=on set JS2_OPTION=3 set JS2_CMD_1=jar set SOURCE_DIR_1=%INST_DIR%\F3FMjs2\webapps\sample rem======================================= rem EXAMPLE - more files can be specified here rem======================================= rem set JS2_CMD_2=xcopy rem set SOURCE_DIR_2=%INST_DIR%\F3FMjs2\webapps\debug rem====================================== ... :PROCEDURE_PART ... rem [JS2] ... rem======================================= rem EXAMPLE rem======================================= rem IF "%JS2_OPTION%" == "2" ( rem FOR %%I IN ("%SOURCE_DIR_2%") DO ( rem IF /I "%JS2_CMD_2%" == "JAR" ( rem PUSHD "%%~dpI" rem IF ERRORLEVEL 1 ( rem goto ERROR_RTN rem ) ELSE ( rem ECHO. rem ) rem ... rem========================================

[JS2] target = on option = 3 cmd = jar source_dir = /opt/FJSVjs2/webapps/sample1 cmd = tar source_dir = /opt/FJSVjs2/webapps/sample2 ...


4-91

*2 : For [SOAP] section, SOAP_SOURCE can be specified for Windows(R) or Linux, and multiple files or directories can be specified in source for Solaris OE. When specifying multiple files or directories, space-delimiter is required.

If a file name contains a space, it must be enclosed in " " (double-quotation marks).

Example

:DEFINITION_PART ... rem [SOAP] set SOAP_TARGET=on set SOAP_SOURCE=%INST_DIR%\F3FMsoap\etc\DeployService\server config.wsdd %INST_DIR%\F3FMsoap\etc\DeployService\server-config2.wsdd

[SOAP] target = on source = /opt/FJSVsoap/deplay /opt/FJSVsoap/deplay/file.db

*4 : For [JMS] section, the following path to CLASSPATH must be specified for backup.

CLASSPATH=/opt/FJSVj2ee/lib/isj2ee.jar:/opt/FJSVjms/lib/fjmsprovider.jar

*5 : For [J2EE] section, the directory that stores jar command must be included in the environment variable PATH because jar command is used in the internal process.

*6 : For [IPP] section, multiple backup target files can be specified.

To specify multiple files, change :DEFINITION_PART and :PRPCEDURE_PART of the batch file. In this batch file, two files are defined as samples, and the second file has a comment. Therefore, remove the comment in using the file. For the third file and after, copy and change the corresponding parts and then, execute the batch process.

The backup file is created in the following directory under the directory that stores resources:

Example

Folder storing resources\IPP\environment definition file name\ :DEFINITION_PART ...


4-92

rem [IPP] set IPP_TARGET=on set IPP_OPTION_1=1 set IPP_SOURCE_1=F3FMwww.dat rem====================================== rem EXAMPLE - more files can be specified here rem====================================== rem set IPP_OPTION_2=2 rem set IPP_SOURCE_2=F3FMwww2.dat rem===================================== ... :PROCEDURE_PART rem [IPP] ... rem====================================== rem EXAMPLE rem====================================== rem MD %COMMON_PATH%\IPP\%IPP_SOURCE_2% rem IF ERRORLEVEL 1 ( rem goto ERROR_RTN rem ) ELSE ( rem ECHO. rem ) rem ... rem======================================

Directory storing resources/IPP/environment definition file name/ [IPP] target = on option = 1 source = /opt/FSUNprovd/conf/HTTPD.conf option = 2 source = /opt/FSUNprovd/conf/HTTPD2.conf ...

*7 : For [EJB] section, the following directories are the operation targets when ejbapp is not defined:

Default system /opt/FJSVj2ee/var/deployment/deployed/ejbapp

Extended system /var/opt/FJSVisas/system/extended system name/FJSVj2ee/var/deployment/deployed/ejbapp

*8 : For [InfoDir] section, multiple DSA directories can be specified. To specify multiple directories, space-delimiter is required. If the directory contains a space, the command parameter must be enclosed in " " (double-quotation marks).


4-93

Example

:DEFINITION_PART ... rem [InfoDir] set INFODIR_TARGET=on set INFODIR_SOURCE=%INST_DIR%\dib\DSA1 %INST_DIR%\dib\DSA2

[InfoDir] target = on source = /opt/dib/dsa1 /opt/dib/dsa

[Supplement]

Backup only the sections with definition value of "on."

Interstage Resource Backup/Export Perform collective backup/export of Interstage resources.

The sample of backup target resource definition file with the name of backupdef.txt is shown below.

isbackup

isbackup backupdef.txt

Notes

• Be sure that the disk for creating a directory for storing backup resource has enough free space. The disk space required for storing backup resource is the total sum of the amounts of backup target resources shown in Outline and Applicable Resources.

• Back up the SSL resource when the CORBA Service resource is the backup target, and SSL is used by the CORBA Service. Refer to Note in Backing Up CORBA Service Resource for details.

• For environment variable PORB_HOME, the installation directory "/opt/FJSVporb" of Portable-ORB must be specified (Solaris OE only). The operation targets are under the installation directory of Portable-ORB only. The resources for downloading operation of Portable-ORB or SSL operation are not the operation targets. For these non-target resources, see Backing Up Portable-ORB Resource and Exporting Protable_ORB REsources backup/export.


4-94

• When old version Servlet service resource is the backup target, the Servlet gateway environment definition file stored in the following directory is the backup target in Interstage resources collective backup: When the Servlet gateway environment definition file is stored in other directory than the following directory, perform the Interstage resource collective backup, and then manually execute the backup of Servlet gateway environment definition file: See Backing Up Old Version Servlet Service Resourcefor the backup procedures.

C:\Interstage\F3FMjs2\conf

/etc/opt/FJSVjs2

• For Interstage HTTP Server, back up or export the respective corresponding files when the content backup is required and when other files than httpd.conf and password file are used in setting the environment. Moreover, back up the SSL resource in addition when you use SSL (Only back up). Refer to Note in Backing Up Interstage HTTP Server Resource for details.

• If isbackup has an error, an error message is output at the erroneous point. If the command described in isbackup has an error, respond according to the output message of the command.

• isbackup uses the following commands: If the commands have an error, check the command output message, and also check the method of using the command.

− iscbackupsys

− isguibackup

− odbackupsys

− esbackupsys

− tdbackupsys

− otsbackupsys

− jsbackup

− jar

− issoapbackup

− jmsbackup

− j2eebackup

− ijsbackup

− jsbackup

• If an error occurs in isbackup, delete the directory of the backup destination, and execute isbackup again.


4-95

Resource Restore/Import The sample procedures of the collective Interstage resource restore and import are shown below.

Restore C:\Interstage\sample\backup_restore\isrestore.bat

Import C:\Interstage\sample\backup_restore\isimport.bat

/opt/FJSVisas/sample/backup_restore/isrestore

The procedures of Interstage restore and import are described as an instruction in isrestore and isimport.

Each process has a comment in the format shown below according to the processing content. #============================================ # Number Explanation of alphanumeric characters #============================================

Process Outline

Explanation of each process outline


:DEFINITION_PART Restore target definition

:PROCEDURE_PART Main process


0. Environment Check Authorization check.

1. check the input parameter Command parameter check.

2-1. set the restore CO Command name variable definition.

2-2. set the section name list Resotore target variable definition.

2-3. get the file line and set line = 0

Syntax analysis of restore target resource files6.


4-96


2-4. check the def file format

2-5. check sub-routines

3. MAIN Main process

4. Sub-Routines Restore process of backup target resources

Restore/Import Process of Resotore Target Resources

Restore/import process is delimited using the format shown below at each backup target resource. ## Service name START : (Restore process description) ## Service name END

Service names (changeable) correspond to the restore resources as listed below.

Service name Restore target resources

ISCOM Restore of Interstage setup resources

GUI Restore of Interstage Operation Tool resources

OD Restore of CORBA service resources

ES Restore of Event service resources

PORB Restore of Portable-ORB resources

TD Restore of Component Transaction service resources

OTS Restore of Database Linkage Service resources

IPP Restore of InfoProvider Pro resources

IJServer Restore of IJServer resources

JS2 Restore of old version Servlet service resources

EJB Restore of EJB service resources

InfoDir Restore of InfoDirectory service resources

SOAP Restore of SOAP service resources

JMS Restore of Interstage JMS resources

J2EE Restore of J2EE common resources

IHS Restore of Interstage HTTP server resources

JS2SU Restore of Servlet Service for Interstage Management Console resources

ISSCS Restore of Interstage Certificate Environment resources

Operation Procedures

Procedures of resource backup/export using the isrestore command are described below.


4-97


Log in with Administrator authority, and use the isstop command to stop all the Interstage services and server applications.

Use the isstop command to stop all the Interstage services and server applications. isstop -f

Note

Services that are not stopped by the isstop command must be stopped by using a separate stopping operation. For more information on how to stop Interstage, refer to Terminating Interstage.

Restore/Import Target Resource Definition

Define Interstage restore target resources in the batch file.

Use the following syntaxes to define the target resources:

Define Interstage restore target resources in the backup target definition file.

The restore target definition file can be created with an arbitrary name according to the following syntaxes:

For details, refer to Restore Procedure and Resource Importing Procedure.

The sample of the restore target resource definition file is provided below.

Define Interstage restore target resources in the batch file.

/opt/FJSVisas/sample/backup_restore/sample.def

Define Interstage backup target resources in Shell.


4-98

Description Format

Write one definition on a single line in the batch file rem [Section name] set definition name = Definition value

Write one definition on a single line in the definition file. [Section name] definition name = Definition value

Write one definition on a single line in the shell. # [Section name] set definition name = Definition value

Notes

• Write "[", "]", and "=" in en-size characters.

• When writing a comment, write # after the definition value. Do not specify # at the top of a line.


4-99

Definition Item List

Restore target items are listed below.

• Section names or definition names cannot be omitted.

• Definition values are indicated as below. o: required -: can be omitted x: cannot be specified

Section name


Definition name

Definition value

Explanation Remarks

HOST Host nameo

Specifies the import destination host name.

Effective at import only

INST_DIR Directory o

Interstage installation directory

Change according to the installation environment.


COMMON_PATH

Directory o



ISCOM_TARGET

on or off o


GUI_TARGET on or off o



GUI_MODE mode1 or mode2 o

Specifies mode 1 when restoring to the Interstage initialized environment. Specifies mode 2 when restoring to the environment immediately after reinstallation of Insterstage.


4-100

Section name


Definition name

Definition value

Explanation Remarks

OD_TARGET on or off o


OD_PORT Port number o

Specifies the port number used for CORBA communication.



OD_DBPATH Derectory o

Specifies when changing the database directory used in the interface repository during importing.



ES_TARGET on or off o



PORB_TARGET

on or off o



TD_TARGET on or off o



OTS_TARGET

on or off o



4-101

Section name


Definition name

Definition value

Explanation Remarks

IPP_TARGET on or off o


IPP_OPTION_1

1 or 2 o





IPP_SOURCE_1

File name o




IJSERVER_TARGET

on or off o


JS2 Specifies old version Servlet service related items.

JS2_TARGET on or off o


JS2_OPTION 1 , 2 or 3 o



2. Web application



4-102

Section name


Definition name

Definition value

Explanation Remarks

JS2_CMD_1 jar or xcopy

When 1 is specified to jar or xcopy JS2_OPTION:

-

When other than 1 is specified to JS2_OPTION:

o


SORCE_DIR_1

Directory


-

When other than 1 is specified to directory JS2_OPTION:

o



TARGET_DIR_1

Directory


-

other than:

o

Specifies the upper directory of the directory that stores Web application in restore destination.


4-103

Section name


Definition name

Definition value

Explanation Remarks

EJB_TARGET on or off o


EJB_EJBAPP Directory

o



EJB_EJBAPP_TARGET

Directory o

Specifies upper directory of the folder that stores EJB application in restore destination.

INFODIR_TARGET

on or off o



INFODIR_SOURCE

Directory

o



SOAP_TARGET

on or off o



SOAP_DRIVE Drive name -

Specifies the drive name in restore destination. The restore resource that is specified in SOAP_SOURCE of the backup batch file is not restored when omitted.


JMS_TARGET

on or off o

An operation target when specifying "on." Not an operation target when specifying.


4-104

Section name


Definition name

Definition value

Explanation Remarks


J2EE_TARGET

on or off o


(*5)


IHS_TARGET on or off o


IHS_OPTION 1 or 2 Specifies the operation target resources from below.



IHS_PASSWD_SOURCE

File path


-

When the file path IHS_OPTION is other than 1:

o


IHS_PASSWD_TARGET

Directory


-

other than:

o

Specifies the directory of the restoration place of a password file.


4-105

Section name


Definition name

Definition value

Explanation Remarks


JS2SU_TARGET

on or off o



ISSCS_TARGET


Section name


Definition name

Definition value

Explanation Remarks

host Hpst name

Restore: -

Import: o

Specifies the import destination host name.

path Directory o



target_server

current or others

o

Specifies "current" for restoration.

Specifies "other" for export operation.


target on or off o



target on or off o



4-106

Section name


Definition name

Definition value

Explanation Remarks

target on or off o



port Port number

Restore: -

Import: x



db_path Directory

Restore: -

Import: x



target on or off o



target on or off o



target on or off o




target on or off o



target on or off o



4-107

Section name


Definition name

Definition value

Explanation Remarks

option 1 or 2 o




source File name o




target on or off o


JS2 Specifies old version Servlet service related items.

target on or off o


option 1 , 2 or 3 o



2. Web application



4-108

Section name


Definition name

Definition value

Explanation Remarks

cmd jar or tar

When 1 is specified to jar or tar option:

-

When other than 1 is specified to option:

o


source_dir Directory

When 1 is specified to directory option:

-

When other than 1 is specified to directory option:

o



target on or off o



ejbapp Directory

o


The default directory is the operation target when omitted. (*7)


4-109

Section name


Definition name

Definition value

Explanation Remarks

target on or off o



source Directory

o



target on or off o



source File path

-




target on or off o


(*4)


target on or off o


(*5)


target on or off o



4-110

Section name


Definition name

Definition value

Explanation Remarks

option 1 or 2 Specifies the operation target resources from below.



passwd_source

File path

When the file path option is 1.:

-

When the file path option is other than 1:

o



target on or off o



ISSCS_TARGET


*1 : For [JS2] section, multiple restore target directories can be specified.

To specify multiple directories, change :DEFINITION_PART and :PROCEDURE_PART of the batch file. In this batch file, two files are defined as samples, and the second file has a comment. Therefore, remove the comment in using the file. For the third file and after, copy and change the corresponding parts and then, execute the batch process.


4-111

Example

:DEFINITION_PART ... rem [JS2] set JS2_TARGET=on set JS2_OPTION=3 set JS2_CMD_1=jar set SOURCE_DIR_1=sample set TARGET_DIR_1=%INST_DIR%\F3FMjs2\webapps rem======================================= rem EXAMPLE - more files can be specified here rem ====================================== rem set JS2_CMD_2=xcopy rem set SOURCE_DIR_2=debug rem set TARGET_DIR_2=%INST_DIR%\F3FMjs2\webapps rem ====================================== ... :PROCEDURE_PART ... rem [JS2] ... rem====================================== rem EXAMPLE rem ====================================== rem IF "%JS2_OPTION%" == "2" ( rem IF /I "%JS2_CMD_2%" == "JAR" ( rem PUSHD "%TARGET_DIR_2%" rem IF ERRORLEVEL 1 ( rem goto ERROR_RTN rem ) ELSE ( rem ECHO. rem ) rem ……………… rem ======================================

[JS2] target = on option = 3 cmd = jar source_dir = /opt/FJSVjs2/webapps/sample1 cmd = tar source_dir = /opt/FJSVjs2/webapps/sample2 …… *2 : For [SOAP] section, multiple files or directories can be specified in source (on Solaris OE) and SOAP_SOURCE (on Linux). When specifying multiple files or directories, space-delimiter is required.


4-112

Example

[SOAP] target = on source = /opt/FJSVsoap/deplay /opt/FJSVsoap/deplay/file.db

*4 : For [JMS] section, the following path to CLASSPATH must be specified for restore.

CLASSPATH=/opt/FJSVj2ee/lib/isj2ee.jar:/opt/FJSVjms/lib/fjmsprovider.jar

*5 : For [J2EE] section, the directory that stores jar command must be included in the environment variable PATH because jar command is used in the internal process.

*6 : For [IPP] section, multiple restore target files can be specified.

To specify multiple files, change :DEFINITION_PART and :PROCEDURE_PART of the batch file. In this batch file, two files are defined as samples, and the second file has a comment. Therefore, remove the comment in using the file. For the third file and after, copy and change the corresponding parts and then, execute the batch process. The restore file is created in the following directory under the directory that stores resources:

Example

Folder storing resources\IPP\environment definition file name\ :DEFINITION_PART ... rem [IPP] set IPP_TARGET=on set IPP_OPTION_1=1 set IPP_SOURCE_1=F3FMwww.dat rem ======================================= rem EXAMPLE - more files can be specified here rem ======================================= rem set IPP_OPTION_2=2 rem set IPP_SOURCE_2=F3FMwww2.dat rem ======================================= ... :PROCEDURE_PART ... rem [IPP] ... rem======================================= rem EXAMPLE rem ====================================== rem IF "%IPP_OPTION_2%" == "1" (


4-113

rem ECHO %INST_DIR%\F3FMwww\Program\ipprestore.exe -d %CO MMON_PATH%\IPP\%IPP_SOURCE_2% rem %INST_DIR%\F3FMwww\Program\ipprestore.exe -d %COMMON _PATH%\IPP\%IPP_SOURCE_2% rem IF ERRORLEVEL 1 ( rem goto ERROR_RTN rem ) ELSE ( rem ECHO. rem ) rem ……………… rem =======================================

Directory storing resources/IPP/environment definition file name/ [IPP] target = on option = 1 source = /opt/FSUNprovd/conf/HTTPD.conf option = 2 source = /opt/FSUNprovd/conf/HTTPD2.conf ...

*7 : For [EJB] section, the following directories are the operation targets when ejbapp is not defined:

Default system /opt/FJSVj2ee/var/deployment/deployed/ejbapp

Extended system /var/opt/FJSVisas/system/extended system name/FJSVj2ee/var/deployment/deployed/ejbapp

*8 : For [InfoDir] section, multiple DSA directories can be specified. To specify multiple directories, space-delimiter is required. If the directory contains a space, the command parameter must be enclosed in " " (double-quotation marks).

Example

:DEFINITION_PART ... rem [InfoDir] set INFODIR_TARGET=on set INFODIR_SOURCE=%INST_DIR%\dib\DSA1 %INST_DIR%\dib\DSA2


4-114

[InfoDir] target = on source = /opt/dib/dsa1 /opt/dib/dsa

[Supplement]

Restore only the sections with definition value of "on."

Interstage Resource Restore/Import Perform collective backup/export of Interstage resources.

The sample of backup target resource definition file with the name of backupdef.txt is shown below.

Restore isrestore.bat

Import isimport.bat

isrestore backupdef.txt

Note

• Restore the SSL resource when the CORBA Service resource is the restore target, and the SSL resource is backed up. Refer to the Note in Restoring CORBA Service Resource for details.

• For environment variable PORB_HOME, the installation directory "/opt/FJSVporb" of Portable-ORB must be specified (Solaris OE only). The operation targets are under the installation directory of Portable-ORB only. The resources for downloading the operation of Portable-ORB or SSL operation are not the operation targets. For these non-target resources, see Backing Up Portable-ORB Resource and Importing Portable-ORB Resource to restore/import.

• When old version Servlet service resource is the restore target, restore the Servlet gateway environment definition file after collectively restoring Interstage resources if restoring the Servlet gateway environment definition file backed up manually in Interstage resource collective backup. Refer to Restoring Old Version Servlet Service Resource for details.

• When backing up other files used for setting the environment other than content, httpd.conf, and password file in Interstage HTTP Server, restore the corresponding files. Moreover, restore the SSL resource when the SSL resource is backed up (Only at restore). Refer to the Note in Restoring Interstage HTTP Server Resources for details. Also, when importing Interstage HTTP Server resources, set up the following in the Interstage HTTP Server environment definition file (http.conf) after executing the isrestore command:


4-115

− Set the host name (or IP address) of import destination to the ServerName directive. If there is another directive that sets the host name (or IP address) of export origin, set the host name (or IP address) of import destination to the corresponding directive.

− If the port number setups are different between export origin and import destination, set the port number of import destination to the directive that sets the port number.

• If isrestore detects an error, an error message is output at the erroneous point. If the commands described in isrestore have an error, respond according to the output message of the command.

• isrestore uses the following commands: When the command have an error, check the output message of the command, and also check the method of using the command.

− iscrestoresys

− isguirestore

− odrestoresys

− esrestoresys

− tdrestoresys

− otsrestoresys

− jsrestore

− jar

− issoaprestore

− jmsrestore

− j2eerestore

− ijsrestore

− jsrestore


4-116

A-1

Appendix A Configuration of Interstage Management Console

This appendix explains the configuration and environment setup of the Interstage Management Console.

Appendix A: Configuration of Interstage Management Console

A-2

Configuration of Interstage Management Console The Interstage Management Console consists of the following resources.

Web Browser The Interstage Management Console runs on a Web browser.

Refer to "Notes on using Interstage Application Server" for information on the Web browsers on which the Interstage Management Console can run.

Services

Interstage Operation Tool Service This is a service for the Interstage Management Console. This service must be active when the Interstage Management Console is used.

This service automatically starts when the server starts.

Interstage Operation Tool (FJapache) Service This is a Web server for the Interstage Management Console. This service must be active when the Interstage Management Console is used.


Interstage JServlet (Operation Management) Service This is a Servlet service for the Interstage Management Console. This service must be active when the Interstage Management Console is used.


Interstage JMX Service This is a service that runs as the operation base for the Interstage Management Console

The Interstage JMX service runs under control of "Interstage Operation Tool" that is a Windows service.

Configuration of Interstage Management Console

A-3

Environment Files The following environment definition files must be set up to use the Interstage Management Console. The user need not recognize the setup of these environment files because it is performed automatically during installation.

• The following file under Interstage HTTP Server for Interstage Management Console:

− httpd.conf

• The following files under Interstage JServlet for Interstage Management Console:

− jsgw_apapi.conf

− jswatch.conf

− jscontainer.xml

Customizing Interstage Management Console Environments This section explains the procedure for customizing the Interstage Management Console environments.

Changing the Port Number To use the Interstage Management Console, the port number for the Interstage Management Console is necessary. The port number setting can be changed by editing the httpd.conf file. [Interstage-install-folder]\GUI\etc\httpd.conf

Change the number following "Port" to suit the Interstage Management Console used. Port number 12000 is set by default. (Port number 12000 is also set when SSL encrypted communication is enabled.) Port 12000

Changing the Automatic Update Interval The Interstage Management Console automatically updates the screen display. The interval at which it updates the display can be defined. Define the interval as follows:

1. Log in to the Interstage Management Console.

2. Click Interstage Management Console in the tree view.

3. Click the environment setup tab and specify the time value (seconds) for automatic update interval. The values that can be specified range from 10 to 3600.


A-4

Interstage JMX Service The Interstage JMX service customization items are as follows:

• Number of the port through which the Interstage JMX service accepts requests.

This is the number of the port through which the Interstage JMX service accepts requests from the Interstage Management Console. Customize it by specifying the value for the rmi attribute at the "port" tag in the isjmx.xml file. The default is 12200.

• Installation path of JDK/JRE used by Interstage JMX service.

This is the installation path of JDK or JRE used by the Interstage JMX service. Customize it by specifying the value for the java.home attribute at the "server" tag in the isjmx.xml file. This installation path is automatically set during Interstage installation.

• Optional information specified for the java process of Interstage JMX service.

This is the optional information specified for the java process to be used by the Interstage JMX service. Customize it by specifying the value for the options attribute at the "server" tag in the isjmx.xml file.

• Maximum number of MBeans that can be registered for Interstage JMX service.

This is the maximum number of MBeans that can be registered for Interstage JMX service. MBeans are resource information managed by the Interstage JMX service. Customize the maximum number by specifying the value for the max attribute at the "registry" tag in the isjmx.xml file. An integer from 1 to 2147483647 can be specified. The default is 100000.

• Time-out time for communication by Interstage JMX service

This is the duration after which a time-out occurs during communication by Interstage JMX service. Customize it by specifying the value for the rmi attribute at the "time-out" tag in the isjmx.xml file. An integer from 0 to 10080 can be specified. The unit is minutes. The default is 60. If 0 is specified for this parameter, no time-out occurs during communication by the Interstage JMX service. Even if a time-out occurs during communication by the Interstage JMX service, the requested processing continues on Interstage.

To customize these values, first customize the isjmx.xml file, which is the environment definition file for the Interstage JMX service, and then restart the Interstage Operation Tool service and Interstage JServlet (Operation Management) service. [Interstage-install-folder]\jmx\etc\isjmx.xml

Content of isjmx.xml <?xml version="1.0" encoding="MS932"?> <isjmx> <port rmi="12200" internal="12210"/> <server java.home="c:\interstage\jdk13" options="-Xmx256m" /> <registry max="100000" /> <timeout rmi="60" /> </isjmx>

Configuration of Interstage Management Console

A-5

Troubleshooting the Interstage Management Console This section explains the action to be taken if an error occurs during operation of the Interstage Management Console.

• If the Interstage JMX service (Interstage Operation Tool service) fails, restart Windows service Interstage Operation Tool.

• If an error occurs in the Interstage JMX service, a message indicating the error cause is output to the event log. Take action according to the message.

• If the Interstage JMX service is stopped and restarted during job operation, statistical information may not be displayed correctly in the following windows of the Interstage Management Console:

− IJServer: Monitor

− Web application: Monitor

− EJB application: Monitor

If the statistical information provided by IJServer, Web applications, and EJB applications is to be used, do not stop the Interstage JMX service during job operation.

• If the automatic start of WorkUnits is enabled in the WorkUnit definition when the machine starts, statistical information may not be displayed correctly in the following windows of the Interstage Management Console:

− IJServer: Monitor

− Web application: Monitor

− EJB application: Monitor

If this symptom occurs, add the environment variable IS_JMX_SERVICE_WAIT_TIMEOUT to the system environment variables and set the following value in it. The setting is validated when the machine starts next.

− Value obtained by adding 180 to the time interval between the output times of messages td11001 and is20701


A-6

B-1

Appendix B isconfig.xml

This appendix describes the isconfig.xml for Interstage definition. If the definition in the isconfig.xml is updated, Interstage may be restarted.

Appendix B: isconfig.xml

B-2

Synopsis <configuration> <definition name>value</definition name> </configuration>

Definition Parameter AutoConfigurationMode defines auto extension of the tuning parameters. <configuration> <AutoConfigurationMode>AUTO</AutoConfigurationMode> </configuration>

AUTO: The auto extension is valid.

MANUAL: The auto extension is not valid.

The default is AUTO.

C-1

Appendix C Interstage Operations by Interstage Integrated Commands

This appendix describes Interstage operations by Interstage integrated commands

Appendix C : Interstage Operations by Interstage Integrated Commands

C-2

Interstage Environment Setup Interstage requires a definition file to be set up for each service.

The definitions and settings required in these service definition files are generated automatically when the items below are defined in the Interstage environment setup procedure.

Some services are dependent on the operating mode specified, and others are not. For details, refer to Initializing Interstage.

• System scale (number of clients connected)

• Application status (services executed on server device)

The environment setup procedure below is illustrated in Figure C-1.

1. Generating the Interstage System Definition File

2. Registering Interstage System Definition File

3. Initializing Interstage

4. Customizing the Interstage Operating Environment Definition

5. Designing the Naming Service and Interface Repository

Figure C-1 Environment Setup Procedure

Interstage Environment Setup

C-3

Generating the Interstage System Definition File The Interstage System Definition file contains system information for running Interstage. This information is used to generate the environment definition file for each service.

1. Define the system scale. Define the system scale (scale-value in isgendef command), by referring to the number of clients connected. Refer to Tables C-1 and C-2 for details.

Table C-1 System Scale Definition

isgendef command:scale-value Number of Clients Connected

small 1 – 5

moderate 6 – 10

large 11 – 50

super 51 – 100

Table C-2 System Scale Definition

isgendef command:scale-value Number of Clients Connected

small 1 - 50

moderate 51 - 100

large 101 - 500

super 501 - 1000

Note In a system constructed on the multilayer model, the number of connected clients needs to be noted.

"super" cannot be specified as the system scale.

2. Execute the isgendef command. When the isgendef command is executed, an Interstage System Definition file is generated automatically according to the system scale indicated. Example Generating Interstage System Definition when system scale is "large". isgendef large

The Interstage System Definition generated by isgendef is stored in the following file:


C-4

C:\INTERSTAGE\td\etc\isdef\isconf.txt

/opt/FSUNtd/etc/isdef/isconf.txt

/opt/FJSVtd/etc/isdef/isconf.txt

The timeout period for server applications can be a customized value in the generated Interstage System Definition file. This should be done before the definition file is registered by the isregistdef command in the next step of the procedure. If the isgendef command is re-issued, then the customized value will be overwritten and become invalid. For details of the values set in the Interstage System Definition file by the isgendef command, refer to the Reference Manual (Command Edition).

Note

If the isgendef command is run when the Interstage environment has already been set up, the Component Transaction Service is set up again the next time the isinit command is run. In this case, the WorkUnit definitions must be reregistered.

In addition, the operating system must be customized to suit the system scale. For details of the customization, refer to the Tuning Guide.


C-5

Registering the Interstage System Definition File The Interstage System Definition file is registered in the system when Interstage is initialized or when one of the services is invoked.

(1) Execute the isregistdef Command Execute the isregistdef command. The following definition files are generated automatically from the contents of the Interstage system definition file, and registered in their assigned folders.

Interstage Operating Environment File

Referred to when Interstage is initialized (when isinit command is executed).

Environment Definitions for Services

• Operating environment file for CORBA Service

• Environment definition for Database Linkage Service

These definitions are referred to when the respective services are invoked. isregistdef

The definition files are saved in the folders shown in Table C-3.

Table C-3 Location of Definition Files

Definition File Folder

Operating environment file for CORBA Service C:\INTERSTAGE\ODWIN\etc\config

Interstage operating environment definition C:\INTERSTAGE\td\etc\isreg\isinitdef.txt

Environment definition for Database Linkage Service C:\INTERSTAGE\ots\etc\config

The definition files are registered as shown in Table C-4.


Definition File Registered file

Operating environment file for CORBA Service /etc/opt/FSUNod/config

Interstage operating environment definition /opt/FSUNtd/etc/isreg/isinitdef.txt

Environment definition for Database Linkage Service /opt/FSUNots/etc/config

The definition files are registered as shown in Table C-5.


C-6


Definition File Registered file

Operating environment file for CORBA Service /etc/opt/FJSVod/etc/config

Interstage operating environment definition /opt/FJSVtd/etc/isreg/isinitdef.txt

Environment definition for Database Linkage Service /opt/FJSVots/etc/config

The values recorded in the service environment definitions and the Interstage operating environment definition vary depending on the system scale.

For details of the isregistdef command and the values set in each definition file, refer to Interstage Operating Environment Definition in Appendix E, the Reference Manual (Command Edition), and the Tuning Guide.

For information on changing a value to be set or on customization values when executing the isregistdef command, refer to Interstage Operating Environment Definition in Appendix E, and the Tuning Guide.

(2) Define the Environment for each Service Any customization of the service environment should be carried out before initializing Interstage (before executing the isinit command). For details, refer to Table C-6.

The service environment definitions are customized for the following purposes:

Table C-6 Use of Customized Service Environment Definition Files

Definition file Use

Operating environment file for CORBA Service

Make the following setting concerning the CORBA Service:

Set the network environment and host information required for linking applications between the client and the server.

When performing tuning in accordance with the resources used by applications, such as the concurrency of applications and the number of connections to be used

When setting the timeout monitoring time in accordance with the application processing time

When using the security function

When using the maintenance function


C-7

Definition file Use

Environment definition for Database Linkage Service

Make the following setting concerning the Database Linkage Service:

When changing the concurrency of the functions provided by the Database Linkage Service

When changing the timeout time of each transaction

When changing the number of retries in the event of abnormality

When changing the size of the trace log

When changing JDK to be used to start the Resource Manager for JTS

For details of the service environment definitions and the Interstage operating environment definition, refer to the Tuning Guide.

Note

If TD path for system is modified when the Interstage environment has already been initialized, the Component Transaction Service is set up again the next time the isinit command is run. In this case, the WorkUnit definitions must be reregistered.

Before executing the isregistdef command, stop Interstage (in forced termination mode of all services).

Initializing Interstage Initialize Interstage in the following manner.

Determining the Services to be Initialized The Interstage integrated command can initialize the following services.

• CORBA Service

• Naming Service

• Interface Repository

• Interface Repository for EJB

• Event Service

• Component Transaction Service

• Servlet Service

• CORBA/SOAP Client Gateway

• Database Linkage Service

• Load Balance Option

• WWW Server


C-8

Select services to be operated with the Interstage integrated command from the above services.

Initialize the services to be operated with the Interstage integrated command.

Determining the Operating Mode Based on the services to be initialized, determine the operating mode.

The operating modes include the following three types:

TYPE1:

The CORBA Service, Naming Service, Interface Repository, and Component Transaction Service are initialized.

TYPE2:

The Database Linkage Service is initialized in addition to services in TYPE1.

TYPE3:

The CORBA Service Server and Component Transaction Service are initialized. For the Naming Service and Interface Repository, the services referenced by another server are referenced.

By combining with the setting of the Interstage operating environment definition, both or either of the Naming Service and Interface Repository can be initialized. For the Naming Service not to be initialized, the service referenced by another server is referenced.

Whether to use the services that are not included in the above can be specified by customizing the Interstage operating environment definition.

Customizing the Interstage Operating Environment Definition Table C-7 shows the relation between the operating mode for each service and the Interstage operating environment definition.

Table C-7 Operating Modes and the Interstage Operating Environment

Operating Mode

TYPE1 TYPE2 TYPE3

Interstage operating environment definition

Remarks

CORBA Service YES YES YES N/A

Naming Service YES YES YES" YES"

TYPE3 is specified, and can be initialized by setting the definition (*1).

Interface Repository YES YES YES" YES"

TYPE3 is specified, and can be initialized by setting the definition (*2).

Event Service N/A N/A N/A YES'

Choose whether to use the service by setting the definition

Component Transaction Service YES YES YES N/A


C-9

Operating Mode

TYPE1 TYPE2 TYPE3

Interstage operating environment definition

Remarks

Database Linkage Service NO YES NO N/A This service can be used

only with TYPE2.

WWW Server N/A N/A N/A YES'


Servlet Service N/A N/A N/A YES'


CORBA/SOAP Client Gateway N/A N/A N/A YES'


YES : Initialized

YES' : Can be initialized by setting the Interstage operating environment definition

YES" : Reference the remote server

NO : It cannot be initialized

N/A : There is no specification method

*1: When the Naming Service is initialized, it is set to use the extended function.

*2: Whether to use the Interface Repository for EJB should be specified with the parameter of the isinit command. The contents of initialization shall conform to the setting of the Interface Repository.

The services that are not dependent on the specification of the operating mode include:

• Event Service

• Load Balance option

• WWW Server

• Servlet Service

• CORBA/SOAP Client Gateway

For the operating mode of the above services, determine which method is to be used.

Operation integrated as Interstage

The services can be operated with the isstart, isstop, and isstat commands and the Interstage Operation Tool, together with the services specified in the operating mode.

Operation for each service

The services can be operated with the isstart, isstop, and isstat commands and the Interstage Operation Tool.

For the environment set-up and operation of each service and function, use the function of each service.

To perform operations integrated with Interstage, customize the Interstage operating environment definition for the service to be initialized.


C-10

The Interstage operating environment definition is stored in the following file.

C:\INTERSTAGE\td\etc\isreg\isinitdef.txt

/opt/FSUNtd/etc/isreg/isinitdef.txt

/opt/FJSVtd/etc/isreg/isinitdef.txt

The concrete customizing method is shown below.

Naming Service and Interface Repository

When the operating mode is TYPE3, the Naming Service and Interface Repository can be used in the following manner:

• The Naming Service and Interface Repository operated in another server are referenced.

• The Naming Service operated in another server is referenced.

• The Interface Repository operated in another server is referenced.

When referencing the Naming Service and Interface Repository operated in another server, the Interstage operating environment definition defines its server name and port number.

Definition examples are shown below.

Example

Example of setting another server host (Host A) for both the Naming Service and Interface Repository. NS USE=remote NS Host Name=HostA NS Port Number=8002 IR USE= remote IR Host Name=HostA IR Port Number=8002

Example

Example of setting another server host (Host A) for the Naming Service and setting the local server for the Interface Repository. NS USE=remote NS Host Name=HostA NS Port Number=8002 IR USE=local IR Host Name= IR Port Number=


C-11

Example

Example of setting the local server for the Naming Service and setting another server host (Host A) for the Interface Repository. NS USE=local NS Host Name= NS Port Number= IR USE=remote IR Host Name= HostA IR Port Number=8002

Note

• When using the EJB Service in TYPE3 mode, the Interface Repository needs to be operated on the local host. Register the Interface Repository in the Interstage operating environment definition so that it can be used on the local host. Refer to Interstage Operating Environment Definition in Appendix D for details.

• On the server operating the Naming Service and Interface Repository, do not edit the inithost file.

• When the Naming Service and Interface Repository are operated on another server, use the same port number.

• If the same server name as the server to be specified when referencing the Naming Service and Interface Repository operated in another server is defined in the inithost file, delete the server name defined in the inithost file.

Event Service

Whether to use the Event Service or not can be specified, and various customizing operations can be performed. By executing the essetcnf command after the initialization of Interstage is completed, the configuration information of the Event Service can be changed.

The definition example is shown below.

Example

Example of using the Event Service Event Service=yes Event maximum Process=2 Event maximum Connection=5 Event Auto Disconnect=no

Note

To initialize Interstage again after an event channel is generated by the esmkchnl command, delete the event channel with the esmkchnl command before initializing Interstage. For details on the esmkchnl command, refer to the Reference Manual (Command Edition).


C-12

WWW Server Service

Specify the WWW server on which the Interstage integrated command is to be operated. Prepare a WWW server environment definition file beforehand and then register the environment definition file of the WWW server.

Example

When registering the WWW server environment definition file "Websv.dat" with the identifier "Websv": InfoProvider Pro=yes InfoProvider Pro Definition=Websv.dat:Websv

When registering the WWW server environment definition file "/wdef/Websv.dat " with the identifier "Websv": InfoProvider Pro=yes InfoProvider Pro Definition=/wdef/Websv.dat:Websv

Servlet Service

Specify whether to operate the Servlet Service with the Interstage integrated command.

Example

Using the Servlet Service Servlet=yes

CORBA/SOAP Client Gateway

Specify whether to operate the CORBA/SOAP Client Gateway with the Interstage integrated command.

Example

Using the CORBA/SOAP Client Gateway SOAP Client GW=yes

Database Linkage Service

The Database Linkage Service enables the Database Linkage Service setup mode and Database Linkage Services to be customized. Two types of setup mode can be selected: Where the OTS system, and where the resource control program is started.

Example

Using the Database Linkage Service


C-13

OTS Path for system log=d:\otslog OTS Setup mode=sys

OTS Path for system log=/dev/rdsk/c1t0d0s7 OTS Setup mode=sys

In addition to the above, the operating mode can be customized by the Interstage operating environment definition. For the concrete setting method, refer to the Reference Manual (Definition Edition) and Customization with the Interstage Operating Environment Definition.

Executing Initialization Execute the isinit command to initialize Interstage. isinit TYPE1 | TYPE2 | TYPE3 | type1 | type2 | type3 [ EJB | ejb ]

When using EJB, specify EJB with the isinit command. The Interface Repository for EJB is added to the initialization targets.

To operate Interstage with the multi-server and to link EJB applications between servers, only one server can contain the Naming Service amongst the servers containing EJB applications to be linked.

Note

• If the service constituting Interstage is terminated during the operation of Interstage; Interstage is terminated abnormally. However, the WWW Server, Servlet Service, and CORBA/SOAP Client Gateway operate according to the operation status monitoring mode. For details on the operating status monitoring mode, refer to Customization with the Interstage Operating Environment Definition.

• TYPE2 is provided only in the Enterprise Edition.

• Before executing the isregistdef command, stop Interstage (in forced termination mode of all services).

• When the Naming Service is initialized, it is set to use the extended function. When operating an application created with Interstage of V2.0L20 or before, it is necessary to set the extended function of the Naming Service so that it is not used. In this case, customize the nsconfig file not to use the extended function of the Naming Service. For details on the nsconfig file, refer to the Tuning Guide.

• When the Naming Service is initialized, it is set to use the extended function.

Re-initialization Timing

Initialization has to be performed again in the following cases.


C-14

When changing the system scale

When it is necessary to change the pre-determined system scale due to the increase in the number of clients, perform initialization after making a change. For a detailed procedure, refer to Changing the System Size.

When changing the operating mode

When changing the operating mode, specify the new operating mode and perform initialization. For a detailed procedure, refer to Changing the System Operation Pattern.

When changing the definition

When the definition of the service required in the operating mode and the Interstage operating environment definition are changed, specify the operating mode that is the same as the existing operating mode in the isinit command and perform initialization.

Interstage must be initialized in the situations shown in Figure C-2.

Figure C-2 When Interstage Must be Initialized

• Interstage cannot be started until initialization has been completed.

• The defined values are stored in the system once Interstage has been initialized.

Note

When the following operation is performed in states where the Interstage environment has already been initialized, the Component Transaction Service is set up again when the isinit command is executed. In this case, re-registration of the WorkUnit is required.

• The isgendef command was executed.

• "TD path for system" of the Interstage operating environment definition was changed.

• Though the isinit command was executed, its result was an error.

Customization with the Interstage Operating Environment Definition In the Interstage operating environment definition, the following customization can be performed in addition to the customization of the service used.


C-15

Host Names Used by the CORBA Service

When multiple IP addresses (or host names) have been set for the machines, the IP addresses used by the CORBA server applications can be set for restricted operations.

For example, requests can be accepted from only one LAN card when multiple LAN cards exist on a single machine. In addition, when an object reference of a server application is generated, the IP address of the host name set here is incorporated and used at client access.

Port Numbers Used by the CORBA Service

Create settings when the port number used in CORBA communication is to be customized.

The default port number is 8002.

Example

Setting 8003 as the port number used for CORBA communication Corba Port Number=8003

Port Numbers Used by the CORBA Service

Make settings when the port number used in CORBA communication is to be customized.

When these definition items are not specified, the values of the following definition items are valid.

(1) Setting value of the definition item “IIOP port” in the operation environment file (config) in CORBA Service.

(2) Port number of odserver defined in /etc/services.

Setting value of (1) has a priority in the above (1) and (2).

Example

Setting 8003 as the port number used for CORBA communication Corba Port Number=8003


C-16

Load Balance

Specify whether to use the load balance. A definition example is shown below.

Example LBO USE=yes

Operating Status Monitoring Mode

Specify the operating status monitoring mode of Interstage. The operating status monitoring mode defines what operation is to be performed when a service constituting Interstage stops during the operation of Interstage. In mode2, the definition change operation can be performed by stopping the web server, Servlet Service, and CORBA/SOAP Client Gateway during operation of Interstage, and after changing the definition, restarting the stopped service. For this purpose, the start and stop commands of each service are used.

There are two types of operating status monitoring modes as shown below.

MODE1

When a service constituting Interstage stops, stop Interstage.

• If any of the other services stops, the operation of Interstage stops.

MODE2

If a service constituting Interstage stops during the operation of Interstage, Interstage operates in the following manner:

• Even if the Naming Service, Interface Repository, WWW Server, Servlet Service, or CORBA/SOAP Client Gateway stops, the operation of Interstage continues.

• If any of the other services stops, the operation of Interstage stops.

Example IS Monitor Mode=mode1

If you want to stop Interstage itself when one of the services in Interstage stops, select MODE1.

In mode1, Interstage must be stopped before WWW servers or applications are added or deleted when the use of the WWW and Servlet services has been set in the Interstage operating environment definition. If you do not want to stop other services in Interstage when replacing these definitions, select MODE2.


C-17

Designing the Naming Service and Interface Repository The means of using the Naming Service and Interface Repository are shown below.

When Operating with One Server

Place the Naming Service and Interface Repository on a local server. The operating mode is TYPE1 or TYPE2.

When Operating with Two or More Servers

When the Naming Service and Interface Repository are Shared by Multiple Servers

When the Naming Service and Interface Repository are shared by multiple servers, place the Naming Service and Interface Repository on one server and initialize the other servers so that they can reference the server on which the Naming Service and Interface Repository are placed. The operating mode in this case is as follows.

A) When placing the Naming Service and Interface Repository on one server

The server on which the Naming Service and Interface Repository are placed is TYPE1 or TYPE2 and the other servers are TYPE3.

B) When placing the Naming Service and Interface Repository on a separate server

All the servers are TYPE3. For the server on which the Naming Service and Interface Repository are placed, define the Naming Service and Interface Repository on the local server in the Interstage operating environment definition.


C-18

When the Naming Service and Interface Repository are Shared

Place the Naming Service and Interface Repository on the local server. The operating mode is TYPE1 or TYPE2.

Figure C-3 Types of Operating Mode

Starting Interstage

C-19

Starting Interstage The procedure for starting Interstage depends on the application status. Refer to Figure C-4 for details.

Figure C-4 Starting Interstage


C-20

Starting up a Database Management System If you are employing database linkage, start up the database management system to be used by the application.

For more information on the database management system, refer to the appropriate manual.

Starting Interstage According to Application Status Interstage is started up using the isstart command.

The isstart command starts up the services that are specified by the operating mode and the Interstage operating environment definition when setting the Interstage environment. Services that are not specified by the operating mode and the Interstage operating environment definition are not started up by the isstart command. Start them up individually using the startup command of each respective service. isstart

This command can only be used by users belonging to the Administrators group.

Notes

• Do not use the individual start/stop command for individual services started with the isstart command. Refer to isstart in the Reference Manual (Command Edition) for details.

• Specify the CORBA/SOAP client server operating environment before starting the CORBA/SOAP client server. Refer to the SOAP Service User’s Guide for details.

• If the Component Transaction Service is started by the isstart command, the following implementation repository ID is registered in the implementation repository. This information is not deleted even if the Component Transaction Service is stopped. Do not delete this information as it is required at the next startup.

− FUJITSU-Interstage-TDLC

− FUJITSU-Interstage-TDRC

• Specify the WWW Server operating environment before starting the WWW Server. Refer to the WWW Server User’s Guide for details.

• Before starting Interstage, perform tuning as required for the functions to be used. For details, refer to the Tuning Guide.

• It takes time to start the Interface Repository when the amount of interface information is large or if "logging=yes" is defined to config in the CORBA Service operating environment file. If it takes a minute or more to start the Interface Repository, Interstage will fail to start. In this case, set the environment variable IS_ISV_SVCCTRL_TIMER before executing the isstart command.

Starting Interstage

C-21

Set the variable to the difference (in seconds) between the is20102 message output time and the od20001 message output time, plus 90 seconds. For example, if the is20102 message is output at 10 o'clock and the od20001 message at 10 o'clock and 10 seconds, set 100 as the environment variable IS_ISV_SVCCTRL_TIMER. IS_ISV_SVCCTRL_TIMER=100 export IS_ISV_SVCCTRL_TIMER This event is determined by the content of the is20102 message output. If the is20102 message is output, refer to Messages to determine the cause and take the appropriate measure.

• Note that users fail to activate Interstage if it takes more than one minute to start the naming service. On this condition, set the environment variable IS_ISV_SVCCTRL_TIMER before executing isstart command. Set the number of seconds (from this message output to od30102 message output) + 90 to IS_ISV_SVCCTRL_TIMER. For example, when is20102 is output at 10:00:00 and od30102 is output at 10:00:10, set 100 to the environment variable IS_ISV_SVCCTRL_TIMER. IS_ISV_SVCCTRL_TIMER=100 export IS_ISV_SVCCTRL_TIMER This event is determined by the content of the is20102 message output. If the is20102 message is output, refer to Messages to determine the cause and take the appropriate action.

Starting the Resource Manager The Resource Manager is started up for each database (each interface if using Oracle).

Specify the Resource Manager name and the resource definition name in the otsstartrsc command.

Example

Starting the Resource Manager (resource1.exe) otsstartrsc -pg C:\temp\ots\resource1.exe -n resource1

C:\temp\ots\resource1.exe: Name of Resource Manager (full path specification)

resource1: name of resource definition file

Example

Starting the Resource Manager (resource1) otsstartrsc -pg /home/ots/resource1 -n resource1

/home/ots/resource1: Name of Resource Manager (full path specification)

resource1: Name of resource definition file


C-22

Example

Starting the Resource Manager of JTS otsstartrsc -j

Starting WorkUnits After starting up Interstage, you can start and terminate WorkUnits repeatedly until Interstage is terminated.

Start a WorkUnit by specifying the WorkUnit name in the isstartwu command. isstartwu TDSAMPLE1

Starting Interstage Automatically when Booting the Machine

Not only can Interstage be started with the isstat command and with the Interstage Operation Tool, it can also be started automatically when booting a machine.

This section describes the method of constructing the environment and the operating method when Interstage is started automatically when booting a machine.

This section also explains settings when Interstage is not started automatically when booting the machine.

Method of Constructing the Environment To start a task when starting the operation, it is necessary to perform the following operations automatically.

• Automatic start of Interstage

• Automatic start of the application

The procedure for constructing the environment for automating the above operations is shown on the following page.

Automatic Start of Interstage

To start Interstage automatically when booting the machine, it is necessary to customize the settings of the Windows services. The setting method is shown below.

Setting Window Services

Open "Service" in the control panel.

Set the "Startup type" for the "Service" of the Windows service, the service target of the Interstage integrated command, as shown in Table C-8.

Starting Interstage

C-23

Table C-8 Setting Windows Services

Windows Service Name Setting Description

Interstage. Auto Service of Interstage system

Interstage API. Manual Service dedicated to cluster system

F3FMwww. Auto Service for WWW server (InfoProvider Pro)

OD_start. Manual Service for CORBA Service

InterfaceRep_Cache Service. Manual Service for Interface Repository (standard interface)

InterfaceRep_Cache_e Service. Manual Service for Interface Repository (value interface)

Naming Service. Manual Service for Naming Service

EventService. Manual Service for Event Service

EventFactory. Manual Service for Event Factory

Transaction Director. Manual Service for Component Transaction Service

Interstage JServlet. Manual Service for Servlet Service

CORBA_SOAP ClientGW. Manual Service for CORBA/SOAP Client Gateway

When using this method, take care of the following.

• For a service not supported by the Interstage integrated command, set it in accordance with the automatic start method of the service in question.

• To operate Interstage in a cluster system, do not use the above method. Instead follow the start method of the cluster system.

• Except when starting Interstage automatically when booting the machine, start Interstage with the Interstage integrated command or the Interstage Operation Tool.

• When the machine is stopped, it is first necessary to stop Interstage with the Interstage integrated command or the Interstage Operation Tool.

Automatic Start of an Application

Before starting an application automatically, it is necessary to create an application that performs the following operation and registers it as a Windows service.

(1) Check that the Startup of Interstage is Complete

The start status of Interstage can be checked by issuing an Interstage operation API (ISOPenv function). To synchronize an application with the completion of the start of Interstage, issue Interstage operation APIs (ISOPenv function) repeatedly from the application until the start of Interstage is completed.

(2) Starting the Application

The WorkUnit can be started by issuing an Interstage operation API (ISOPoperate function). Start the application using Interstage operation API.

For the registered Windows service, set the "Startup type" in "Service" to "Auto."


C-24

Operating Method Perform the following operations when booting the machine.

1) Automatic start of Interstage

2) Automatic start of the application

If the environment is constructed in accordance with "Method of Constructing the Environment," the above operations are performed automatically when the machine is booted.

Operating Method when not Starting Automatically

Setting Window Services

Open "Service" in the control panel.

Set the "Startup type" for the "Service" of the Windows service (the service target of the Interstage integrated command) as shown in Table C-9.

Table C-9 Setting Windows Services

Windows Service Name Setting Description

Interstage Manual Service of Interstage system

Interstage API Manual Service dedicated to cluster system

F3FMwww Auto Service for WWW server (InfoProvider Pro)

OD_start Auto Service for CORBA Service

InterfaceRep_Cache Service Auto Service for Interface Repository (standard interface)

InterfaceRep_Cache_e Service

Auto Service for Interface Repository (value interface)

Naming Service Auto Service for Naming Service

EventService Auto Service for Event Service

EventFactory Auto Service for Event Factory

Transaction Director Manual Service for Component Transaction Service

Interstage Jservlet Manual Service for Servlet Service

CORBA_SOAP ClientGW Manual Service for CORBA/SOAP Client Gateway

Starting Interstage or WorkUnit from the RC Procedure

To activate Interstage and WorkUnit on booting a machine, use the RC procedure. When activating Interstage and WorkUnit from RC procedure, users must set the start procedure to /etc/rc2.d.

Starting Interstage

C-25

Example #!/sbin/sh # INTERSTAGE start procedure # Set Environment Variable IS_ISV_CONSOLE_OUTPUT=OFF export IS_ISV_CONSOLE_OUTPUT # Execute Start Command isstart isstartwu TDSAMPLE1 isstartwu TDSAMPLE2


C-26

Terminating Interstage The procedure for terminating Interstage also depends on the application status. Figure C-5 shows these procedures.

Figure C-5 Terminating Interstage

Terminating Interstage

C-27

Terminating WorkUnits All WorkUnits are terminated by the isstopwu command. isstopwu TDSAMPLE1 Note

If a WorkUnit is stopped where the pop-up dialog indicating an application error is output, no-response may occur. In this case, a no-response is released by closing the pop-up dialog.

Terminating Resource Manager The Resource Manager is closed down by specifying the resource definition name in the otsstopprsc command, for each database (each interface if using Oracle).

Example

Terminating the OTS Resource Manager normally otsstoprsc -n resource1

resource1: name of resource definition.

Example

Terminating the JTS Resource Manager normally otsstoprsc -j


C-28

Terminating Interstage According to Application Status Using the isstop command, you can simultaneously shut down all the services that were started with the isstart command. isstop

There are three modes for terminating Interstage with the isstop command:

• Normal termination

• Forced termination of active services

• Forced termination of all services

Note

• The isstop command stops the WWW Server and the Servlet Service together. If the isstart command was used to start all the services together, do not use the individual service commands to stop them.

• If an error occurs during the termination process and the services are not shut down, the isstop command process is halted and the operating status is unchanged. Remove the cause of the error and then repeat the termination procedure.

• When an Interstage service is suspended using the "control panel" or the netstop command, the thing which the isstop command of the forced termination of active services designation is thrown into is considered.

• Terminate Interstage in forced stop mode (isstop -f mode) before shutting down the Windows (R) system.

Terminating the Database Management System If you have been using database linkage, terminate the database management system used by the application. For information on how to terminate the database management system, refer to the appropriate manual.

Customization by the ismodifyservice Command

C-29

Customization by the ismodifyservice Command By using the ismodifyservice command, it is possible to add services and delete unnecessary services. Customization can be carried out easily by executing this command.

The services that can be added/deleted using this command are as follows:

• Functions whose service is set up:

− Interface Repository (Standard interface, Value interface) (*1)

− Naming Service (*1)

− Event Service

(*1) Setup or reference destination change to another server

• Addition to or deletion from the monitoring target of the Interstage Integrated Command:

− WWW Server (Windows® and Solaris (TM) Operating Environment only) In this document, Solaris(TM) Operating Environment is hereafter abbreviated as Solaris OE.

− Servlet Service

− CORBA/SOAP Client Gateway

The following explains the procedure for adding/deleting a service.

Adding/Deleting a WWW Server (Windows® and Solaris OE Only)

Example

If the web server identifier is WWWSV and a web server whose environment definition file name is webconf.dat is added: ismodifyservice -a IPP WWWSV webconf.dat

Example

If the web server identifier deletes the web server of WWWSV: ismodifyservice -d IPP WWWSV

Adding/Deleting the Servlet Service

Example

If the Servlet Service is added: ismodifyservice -a Servlet


C-30

Example

If the Servlet Service is deleted: ismodifyservice -d Servlet

Adding/Deleting the Event Service

Use the Event Service to use asynchronous communication (Event Service, Notification Service, and JMS).

Example

If the Event Service is added: ismodifyservice -a ES

Example

If the Event Service is deleted: ismodifyservice -d ES

Adding/Deleting the CORBA/SOAP Client Gateway

Example

If the CORBA/SOAP Client Gateway is added: ismodifyservice -a SOAPCLGW

Example

If the CORBA/SOAP Client Gateway is deleted: ismodifyservice -d SOAPCLGW

Adding/Deleting the Database Linkage Service

To add the Database Linkage Service, specify the operation pattern type2 in the isinit command and execute the command.

Example

If the Database Linkage Service is added: isinit type2

To delete the Database Linkage Service, specify an operating format other than type2 and execute the isinit command.

Customization by the ismodifyservice Command

C-31

Example

If the Database Linkage Service is deleted: isinit type1

Note

Moreover, the ismodifyservice command does not have any influence on the resources of services other than the service for operation except for the following cases.

• When Naming Service and the reference place host of Interface Repository are changed, it is necessary to re-register the information registered into these.


C-32

Changing the System Operation Pattern The procedure shown in Figure C-6 is used to change the system operation status.

Figure C-6 Changing the System Operation Status

Note

The Naming Service and Interface Repository on the home server are deleted if the operation status is changed from TYPE1 or TYPE2 to TYPE3, and the Naming Service or Interface Repository on another server are used. Please make back-ups where necessary. For the operating mode and the placement of the Naming Service and Interface Repository, refer to Initializing Interstage.

Changing the System Operation Pattern

C-33

1) Terminate Interstage

Shut down Interstage using the isstop command (forced termination of all services). isstop –f

-f: Forced termination of all services

2) Customize the Interstage Environment Definition

Customize the Interstage operating environment definition for the service(s) to be initialized as required.

3) Initialize Interstage

Issue the isinit command, specifying the new application status.

When this command is issued, the services making up the application status specified by the isinit parameter are initialized and Interstage is enabled. The initialized Interstage environment is saved in the system until the next initialization operation. isinit TYPE1 | TYPE2 | TYPE3 | type1 | type2 | type3 [EJB|ejb]

In Table C-10, only the service patterns marked with O may be specified as the application status (TYPEn). Those marked with X cannot be specified.

Table C-10 Application Status Types

Application status OD NS IR TD OTS

TYPE1/type1 O O O O X

TYPE2/type2 O O O O O

TYPE3/type3 O ∆ ∆ O X

O: Initialize

∆: Reference the remote server

X: Cannot be initialized

OD : CORBA Service

NS : Naming Service

IR : Interface Repository

TD : Component Transaction Service

OTS : Database Linkage Service


C-34

Notes

1. To use the EJB Service, specify the EJB option as well as the application status.

2. When using the isinit command in the timing other than the initial installation, registration resources of a service that matches the following conditions may be deleted. You are advised to back up all Interstage resources beforehand. For details on backup procedures, refer to Chapter 4, Maintenance (Resource Backup). Resources other than those listed below will be inherited if the -f option is not specified.

− Service excluded from setup

− A service whose definition item in the Interstage environment definition has been changed (If any definition item of the Naming Service, Interface Repository, Event Service, or Load Balance Option is changed, the registered information of these four services is deleted)

4) Start Interstage

Start up Interstage using the isstart command. isstart

Changing the System Size

C-35

Changing the System Size The system scale is changed by the procedure shown in Figure C-7.

Figure C-7 Changing the System Scale

Note

To change the system size, OS tuning is required. For details, refer to the Tuning Guide.


C-36

1) Terminate Interstage

Shut down Interstage using the isstop command (forced termination of all services). isstop –f

-f = Forced termination of all services

2) Generate the Interstage System Definition

Use the isgendef command to set the new system scale and generate the Interstage System Definition. isgendef small | moderate | large | super

The scale-value variable (mandatory parameter) specifies one of the system scales shown in Table C-11 or C-12.

Table C-11 System Scales

Scale-Value System Scale (Number of Clients) Remarks

Small 5 or less Small system

Moderate 6 - 10 Medium-sized system

Large 11 - 50 Large system

Super 51 - 100 Ultra-large system

Table C-12 System Scales

Scale-Value System Scale (Number of Clients) Remarks

Small 5 or less Small system

Moderate 51 - 100 Medium-sized system

Large 101 - 500 Large system

Super 501 - 1000 Ultra-large system

"super" cannot be specified as the system scale.

Changing the System Size

C-37

3) Register the Interstage Definition

Use the isregistdef command to register the Interstage System Definition generated by the isgendef command. A definition for each service and an Interstage operating environment definition will be generated when isregistdef is issued. isregistdef

The Interstage operating environment definition is stored in the following file.

TD_HOME\etc\isreg\isinitdef.txt

/opt/FSUNtd/etc/isreg/isinitdef.txt

/opt/FJSVtd/etc/isreg/isinitdef.txt

Note

1. This command can only be executed by users with Administrator authority belonging to the local group.

2. Some commands are prohibited whilst the isregistdef command is being executed.

4) Customize Interstage Operation Environment

If the application status is TYPE2, specify the system log file in the OTS Path for System Log statement of the Interstage environment definition file. Refer to Initializing Interstage for details regarding application status.


Initialize Interstage using the isinit command. In the isinit command, specify the same application status that was set before the current system change. isinit TYPE1 | TYPE2 | TYPE3 | type1 | type2 | type3 [EJB|ejb]

6) Start Interstage



C-38

7) Re-register Definition Information

Re-register the definition information in the new business system. An example of re-registration is given below.

Definition file name : "sample.wu" isaddwudef sample.wu

Changing the Naming Service/Interface Repository Settings

C-39


The procedure shown in Figure C-8 is used to change the reference location for the Naming Service and Interface Repository.

Figure C-8 Changing the Service Reference Location

Examples of the procedure for changing the server referenced by the Naming Service and Interface Repository, as well as the procedure for changing the server referenced by the Interface Repository, are both shown below.


C-40

Changing Reference Location for the Naming Service and Interface Repository

In the system configuration illustrated in Figure C-9, HostB changes the reference location from HostA to HostC.

Figure C-9 Changing the Reference Location from HostA to HostC

1) Set Server Name and Port Number of the Naming Service and Interface Repository

The server name and port number for referencing the Naming Service and Interface Repository are registered in the Interstage environment definition. Define the server name and port number to be changed, in the Interstage environment definition.

Example

Setting the reference locations to Host C

C:\INTERSTAGE\td\etc\isreg\isinitdef.txt NS USE=remote NS Host Name=HostC NS Port Number=8002 IR USE=remote IR Host Name=HostC IR Port Number=8002

/opt/FSUNtd/etc/isreg/isinitdef.txt NS USE=remote NS Host Name= NS Port Number= IR USE=remote IR Host Name=HostC IR Port Number=8002


C-41

/opt/FJSVtd/etc/isreg/isinitdef.txt NS USE=remote NS Host Name=HostC NS Port Number=8002 IR USE=remote IR Host Name=HostC IR Port Number=8002


Initialize Interstage as TYPE3. isinit type3

3) Start Interstage


Changing Reference Location for Only the Naming Service to the Home Server

In the following system configuration, only the reference location of the Naming Service in HostB is changed from HostA to the home server, HostB. The reference location for the Interface Repository is changed to HostC.

Figure C-10 Changing the Reference Location for Only the Naming Service to the Home Server

1) Set Server Name and Port Number of the Naming Service and Interface Repository

The server name and port number for referencing the Naming Service and Interface Repository are registered in the Interstage environment definition. Set the Naming Service to “local”.

Example

Setting the reference location for the Naming Service to the home server and the reference location for the Interface Repository to HostC.


C-42

C:\INTERSTAGE\td\etc\isreg\isinitdef.txt NS USE=local NS Host Name= NS Port Number= IR USE=remote IR Host Name=HostC IR Port Number=8002

/opt/FSUNtd/etc/isreg/isinitdef.txt NS USE=local NS Host Name=HostC NS Port Number=8002 IR USE=remote IR Host Name=HostC IR Port Number=8002

/opt/FJSVtd/etc/isreg/isinitdef.txt NS USE=local NS Host Name=HostC NS Port Number=8002 IR USE=remote IR Host Name=HostC IR Port Number=8002


Initialize Interstage as TYPE3. isinit type3

3) Start Interstage



C-43

Changing Reference Location for the Interface Repository In the following system configuration, the reference location of the Interface Repository in HostB is changed from HostA to HostC.

Figure C-11 Changing Interface Repository Reference Location

1) Setting the Server Name and the Port Number of the Naming Service and Interface Repository

The server name and port number for referencing the Naming Service and Interface Repository are described in the Interstage environment definition. Define the server name and the port number to be changed in the Interstage operating environment definition.

Example

Set the reference location of the Interface Repository to HostC.

C:\INTERSTAGE\td\etc\isreg\isinitdef.txt NS USE=remote NS Host Name=HostA NS Port Number=8002 IR USE=remote IR Host Name=HostC IR Port Number=8002

/opt/FSUNtd/etc/isreg/isinitdef.txt NS USE=remote NS Host Name=HostA NS Port Number=8002 IR USE=remote IR Host Name=HostC IR Port Number=8002


C-44

/opt/FJSVtd/etc/isreg/isinitdef.txt NS USE=remote NS Host Name=HostA NS Port Number=8002 IR USE=remote IR Host Name=HostC IR Port Number=8002

2) Initializing Interstage

Initialize Interstage in TYPE3 isinit type3

3) Starting Interstage

Use the isstart command to start Interstage. isstart

Change by the CORBA Service Operating Environment Definition

C-45

Change by the CORBA Service Operating Environment Definition

To perform tuning using the CORBA Service operating environment file (config), Interstage needs to be restarted.

The following shows the procedure for changing the CORBA Service operating environment file (config).

Example > isstop -f (Edit the CORBA Service operating environment file (config)) > isstart


C-46

D-1

Appendix D Interstage System Definition

The Interstage system definition is described in the following format.

The Interstage system definition file is C:\Interstage\td\etc\isdef\isconf.txt.

The Interstage system definition file is /opt/FSUNtd/etc/isdef/isconf.txt.

The Interstage system definition file is /opt/FJSVtd/etc/isdef/isconf.txt.

Note

Upon completion of structuring the application environment, creating a backup copy of the resources is recommended for the possible crash of resources.

For details of the procedure for creating a backup copy, refer to Chapter 5, Maintenance (Resource Backup).

Appendix D: Interstage System Definition

D-2

Syntax The Interstage system definition file has the following structure. If a syntax error occurs in the file, the contents of the file are ignored.

• Statement

• Comment line

• Blank line.

Statement A statement is a line for setting the information, and is specified in the following format:

Keyword: Setup information \n

A statement consists of a keyword, a colon (:), and the setup information. The statement description rules are as follows:

• To omit a statement, either delete the applicable statement, or omit only the setup information.

• A statement and a comment cannot exist on the same line.

The components of a statement are detailed as follows:

Keyword The keyword is a registered identifier, and conforms to the following rules:

• Keywords consist of alphanumeric characters and spaces, and must begin with an alphanumeric character.

• Keywords are not case sensitive.

• Multiple successive spaces in a keyword are treated as a single space.

• Spaces or tabs at the beginning of the line are ignored.

= Equal The equal sign separates the keyword from the information, and conforms to the following rules:

• An en-size equal must be specified.

• Spaces or tabs before or after the colon are ignored.

Setup information The setup information defines the settings for the keyword, and conforms to the following rules:

• Any equal signs = included in the setup information are treated as literal characters.

• Setup information ends with a space, tab, line feed “\n”, or EOF.

• Setup information is case sensitive.

• Only one character string can be specified in setup information.

Syntax

D-3

• Spaces or tabs must be enclosed in double quotation marks.

• There can be only one setup information item per statement. To include more than one setup information item, write a new statement.

• All statements are analyzed in the same way.

Examples The following examples show valid statements:

keyword=Information \n

KEYWORD= Information \n

KeyWord =Information \n

Keyword = “Information Area” \n

The following examples show invalid statements causing syntax errors:

# Two types of setup information are specified.

Keyword = Information Area\n

# A statement and a comment are written on the same line. \n

Keyword = Information #This is a statement\n

# The ending double quotation mark is missing.

Keyword = “START Information.\n

# Keyword and setup information are specified on two lines.

Keyword = “START Information.\n

Information END” \n

Note

Specifying an unregistered keyword will cause a syntax error.

Comment Line A comment line is used by the programmer to insert non-executable yet useful information, and is described in the following format:

# comment \n

A comment is preceded by the single byte hash character (#). All text following the # is ignored.

Blank Lines Blank lines can be inserted, but they are ignored during analysis.

Appendix D: Interstage System Definition

D-4

Interstage System Definition File Syntax The isgendef command generates an Interstage system definition, based on the system scale specified at scale-value.

The following example shows the Interstage system definition for a small scale-value:

#Interstage System Definition for small

System Scale=small

The Interstage system definition file has the following structure.

System Scale Sets the system scale specified by the scale-value of the isgendef command. Editing is not required.

E-1

Appendix E Interstage Operating Environment Definition

Interstage operating environment definition is described in the following format.

Interstage operating environment definition file is C:\Interstage\td\etc\isreg\isinitdef.txt.

Interstage operating environment definition file is /opt/FSUNtd/etc/isreg/isinitdef.txt.

Interstage operating environment definition file is /opt/FJSVtd/etc/isreg/isinitdef.txt.

Note

Upon completion of structuring the application environment, creating a backup copy of the resources is recommended for the possible crash of resources.

For details of the procedure for creating a backup copy, refer to Chapter 5, Maintenance (Resource Backup).

Appendix E: Interstage Operating Environment Definition

E-2

Syntax The syntax of the Interstage operating environment definition is the same as that for the system environment definition.

Refer to the Syntax section of System environment definition for details.

Interstage Operating Environment Definition File Syntax

E-3


The Interstage operating environment definition file is generated by the isregistdef command, based on the Interstage system definition.

Except for Corba Host Name, IR Host Name, NS Host Name, IR USE, NS USE, OTS path for system log, OTS Host, OTS Port, OTS Locale and InfoProvider Pro Definition, the isregistdef command automatically sets default values. These default values must, however, be modified according to specific requirements.

Refer to the isinit command for operation modes.

The following is an example of the Interstage operating environment definition file.

Corba Host Name= Corba Port Number= IR DB=ObjectFile IR path for DB file=TD_HOME\var\IRDB IR DB size=10 IR USE = IR Host Name= IR Port Number=8002 NS USE = NS Host Name= NS Port Number=8002 NS jp=no LBO USE=no TD path for system=TD_HOME\var OTS Multiple degree=5 OTS Recovery=2 OTS path for system log= OTS maximum Transaction=5 OTS Setup mode=sys OTS JTS’s RMP Multiple degree of Process=5 OTS JTS’s RMP Multiple degree of Thread=16 OTS Participate=4 OTS Host= OTS Port= OTS Locale= Event Service=no Event maximum Process=2 Event Auto Disconnect=no Event maximum Connection=5 InfoProvider Pro=no InfoProvider Pro Definition = Servlet=no SOAP Client GW=no IS Monitor Mode=mode2


E-4

Note

TD_HOME: Interstage installation folder\td

Corba Host Name= Corba Port Number= IR DB=ObjectFile IR path for DB file=TD_HOME/var/IRDB IR DB size=10 IR USE= IR User Name = root IR Group Name = sys IR Host Name= IR Port Number=8002 NS USE= NS Host Name= NS Port Number=8002 NS jp=no NS Locale = EUC LBO USE=no TD path for system=/var/opt/FJSVisas/system/default/FSUNextp OTS Multiple degree=5 OTS Recovery=2 OTS path for system log= OTS maximum Transaction=50 OTS Setup mode=sys OTS JTS's RMP Multiple degree of Process=5 OTS JTS's RMP Multiple degree of Thread =16 OTS Participate=4 OTS Host= OTS Port= OTS Locale= Event Service=no Event Locale= EUC Event maximum Process=2 Event Auto Disconnect=no Event maximum Connection=50 InfoProvider Pro=no InfoProvider Pro Definition= Servlet=no SOAP Client GW=no IS Monitor Mode=mode2

Note


Notes

• If "remote" is specified for IR USE and NS USE, the same value must be specified for IR Port Number and NS Port Number, or an error will result.

• If "remote" is specified in IR USE and the IR Port Number is omitted; the value of NS Port Number is used for IR Port Number if "remote" is specified in NS USE. Otherwise the default value, 8002, is used for IR Port Number.


E-5

• If "remote" is specified in IR USE and NS USE and the IR Host Name is omitted, the host name specified in NS Host Name is used for IR Host Name.

Corba Host Name

Specify the name of the host on which the CORBA Service is operated.

For a machine with multiple IP addresses, set the host name corresponding to each IP address.

Set the name as a character string consisting of alphanumeric characters, minus signs, or periods, beginning with an alphabetic letter. The length must be equal to or less than 64 characters, and the name must not end with a minus sign or a period.

If this statement is omitted, the host name of the machine on which Interstage operates is set.

The maximum length of the host name that can be specified is 64 bytes.

If this statement is omitted, the name of the host that operates the CORBA Service is not specified.

To distinguish one system from another by the host name operating CORBA Service in the multi system environment, the host name (IP address) must be specified in “Corba Host Name” for every system.

Corba Port Number

Specify the port number used for the CORBA communication between client and server.

An integer value from 1 to 65535 can be specified. Set a value different from the port numbers used by other programs. A value of 1024 or higher is recommended.

If this statement is omitted, settings defined in IIOP_port of the CORBA Service operating environment file (config) become valid.

If this statement is omitted, the following definition items are valid.

(1) The setting value of “IIOP_port”, which is the definition item of the CORBA Service operating environment file (config).

(2) The odserver port number defined in /etc/services.

The setting value of (1) takes priority over that of (2).

IR DB

Set the database type to be used in the Interface Repository:

Only ObjectFile is supported.

This item is mandatory if the Interface Repository is used on the local host.

The default is "ObjectFile".


E-6

IR path for DB file

Set the storage directory for the database to be used in the Interface Repository.


Set the absolute path including drive name (it is a string).

Upper case and lower case do not need to be distinguished.

The maximum length is 200 characters.

The default is TD_HOME\var\IRDB.

Note) TD_HOME:Interstage installation folder\td

The string must start with “/” and not contain any spaces.

Maximum length is 200 bytes.

If this statement is omitted, the default value of “TD_HOME/var/IRDB" is set.


IR DB size

Specify the size of the database to be used in the Interface Repository, in MB.


A value from 1 to1024 can be specified.

A value from 1 to 2000000 can be specified.

The default is 10.

IR USE

Specify whether the Interface Repository is used on the local host or remote host.

“local”: Local host Interface Repository

“remote”: Remote host Interface Repository

Refer to Interstage Environment Setup in Environment Setup of the Operator's Guide for details of “remote” and “local”.

This statement is only valid if the operation mode is TYPE3.

Only "local" can be specified when using the EJB Service by TYPE3.

The default is “remote”.


E-7

IR User Name

Specify the administrator user name of the database used in the Interface Repository Cache Service.


The setting can be a character string up to 8 bytes long.

IR Group Name

Specify the administrator group name of the database used in the Interface Repository Cache Service.


The setting can be a character string up to 8 bytes long.

IR Host Name

The host name of the operating server on the Interface Repository is specified.

This statement must be specified if the operation mode is TYPE3 and the remote host Interface Repository is used.

The character string can contain up to 246 alphanumeric characters, a minus (-) or period (.), and must begin with an alphanumeric character, but must not end with a minus (-) or period (.).


IR Port Number

The port number of the Interface Repository is specified.

This statement must be specified if the operation mode is TYPE3 and the remote host Interface Repository is used.

An integer value from 1 to 65535 can be set.

The default is 8002.

NS USE

Specify whether the Naming Service is used on the local host or remote host.

“local”: Local host Naming Service

“remote”: Remote host Naming Service

Refer to Interstage Environment Setup in Environment Setup of the Operator's Guide for details of “remote” and “local”.

This statement is only valid if the operation mode is TYPE3.


E-8

The default is “remote”.

NS Host Name

Set the server host name that operates the Naming Service.

This statement must be specified if the operation mode is TYPE3 and the remote host Naming Service is used.

The string can contain up to 64 alphanumeric characters, a minus (-) or period (.), and must begin with an alphanumeric character, but must not end with a minus (-) or period (.).


NS Port Number

Specify the Naming Service port number.

This statement must be specified if the operation mode is TYPE3 and the remote host Naming Service is used.

An integer value from 1 to 65535 can be specified. The default value is 8002.

NS jp

This item does not mean anything.

LBO USE

Specifies whether the Load Balancing Option is used. The server on which the Load Balancing Option runs and the operating environment information are based on the settings in the Naming Service.

yes: Used

no: Not used

If yes is specified, set the Load Balancing Option environment.

The default is no.

TD path for system

Set the folder in which the Component Transaction Service operating environment is to be created. This item is mandatory.

Specify the absolute path, including drive name. Specify a character string. Upper case and lower case do not need to be distinguished.

If this statement is omitted, the default is "TD_HOME\var".

Note) TD_HOME:Interstage installation folder\td


E-9

The string must start with a slash /, and must not include spaces.


If this statement is omitted, the default value "/var/opt/FJSVisas/system/default/FSUNextp" is set.

Up to 127 characters can be specified.

OTS Multiple degree

Set the thread concurrency of the Database Linkage Service (OTS system thread concurrency).

You can specify this item if you select TYPE2 for operating mode and set "sys" for the OTS Setup mode.


If this statement is omitted, the default is 5.

Current interfaces and UserTransaction interfaces including begin, commit, and rollback can be operated concurrently by the number specified for this item.

If the maximum value is exceeded, a warning message (ots9013) is output and a value of 31 is set automatically.

Note

Because the thread concurrency of the OTS system is tuned to provide the maximum transaction processing performance, it is not necessary to change the default value.

When changing the default value, set it in such a way that the following relationships are maintained.

OTS system thread concurrency = < Resource management program concurrency (Note 1)

OTS system thread concurrency = < Maximum concurrency for one resource management program transaction

For details of the maximum concurrency for one resource management program transaction, refer to information on the Config file in the Tuning Guide.

Note 1

Obtain the concurrency in the resource management program for JTS using the following equation:

Process concurrency of the resource management program for JTS ∗ Thread concurrency of the resource management program for JTS

OTS Recovery

Set the thread multiplicity level of the Database Linkage Service recovery program.

Set the number of resource managers to be registered in the Implementation Repository and Naming Service.

You can specify this item if you select TYPE2 for operating mode and set "sys" for the OTS Setup mode.


If this statement is omitted, the default is 2.

Recovery processes can be operated concurrently by the number specified for this item.


E-10

OTS path for system log

Set the path for the system log file of the Database Linkage Service.

This item is mandatory if you select TYPE2 for operating mode and set "sys" for the OTS Setup mode.

Specify the absolute path, including drive name. Specify a character string. Upper case and lower case do not need to be distinguished.

Specify the raw device filename.

The string must start with “/” and not contain any spaces.


Point

The procedure for creating a raw device is shown below:

1. Create a partition of a raw device.

Use the fdisk command to create a partition.

2. Bind the created partition.

The following shows an example. The pound sign (#) indicates the prompt. fdisk /dev/sda Command (m for help): p Disk /dev/sda: 255 heads, 63 sectors, 1106 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sda1 1 523 4200997 83 Linux /dev/sda2 524 1106 4682947+ 5 Extended /dev/sda5 524 1106 4682947 83 Linux Command (m for help): q # # raw /dev/raw/raw1 /dev/sda5

Every time the machine starts, the binding of the partition must be performed by using the raw command. To automate this procedure, use the following method.

Write the same parameter that is passed to the raw command described above in /etc/sysconfig/rawdevices. /dev/raw/raw1 /dev/sda5


E-11

3. Give the read permission to the raw device controller and the disk partition. Give the read and write permission to the raw device. # chmod a+r /dev/rawctl # chmod a+r /dev/sda1 # chmod a+rw /dev/raw/raw1

Note

• The raw command performs the bind processing to the character device normally even if the device for the mounted system is specified. Make sure to specify the device name to the second parameter of the raw command correctly. If the device name is specified incorrectly, the system or the user property may be damaged.

• For specifying the log file of the setup information file, make sure to specify the device name that is bound to the character device using the raw command. Every time the machine starts the binding must be performed by using the raw command.

OTS maximum Transaction

Set the maximum number of Database Linkage Service transactions.

This item is mandatory if the operation type is TYPE2.

Refer to the isinit command for details of the operation type.



OTS Setup mode

Set the host, indicating whether the Database Linkage Service is operating, or only the resource control program of the Database Linkage Service is operating.

“sys”: The OTS system and the resource control program operate on the host.

"rmp”: Only the resource control program operates on the host.

When specifying “sys” and “rmp”, use lower case characters.

When “sys” is set, the following are executed: OTS system operating environment setup, the resource control program operating environment setup, and system log file creation. When “rmp” is set, only the resource control program environment setup is executed. The OTS system cannot be activated in an environment where “rmp” has been specified.


E-12

If “rmp” is set, the Naming Service of the host on which the OTS system operates must be referred to in order to achieve proper operation of the resource control program. Follow the setup method described below.

• On setting “rmp,” specify “OTS Host”, “OTS Port” and “OTS Locale” of the host on which the OTS system is operating. In this case, the Naming Service to be used is the host that “rmp” is set to, not the host on which the OTS system is operating. The Naming Services of the host on which “rmp” is set and the host on which the OTS system is operating, can both be operated independently. To enable sharing of the Naming Service with the host on which the OTS system is operating, use isinit type3 and the otssetup command. (Specify “RMP” for MODE of the setup information file.)

If this statement is omitted, the default is "sys".

Note

• A Naming Service cannot be shared between hosts that have “sys” specifications. Be sure to set a host in which one “sys” is set for one Naming Service. If “rmp” is set, a Naming Service can be shared between more than one host.

• If “rmp” is specified, the Database Linkage Service is not started, even though the isstart command is executed.

• If “rmp” is specified, the state of “ObjectTransactionService” always becomes “stop” when the isstat command is executed.

OTS JTS’s RMP multiple degree of Process

Specify the process concurrency of the JTS resource control program of the Database Linkage Service.


This statement can be omitted.

If this statement is omitted, 5 is set as the default value.

Fujitsu recommends setting the number of resources used (such as databases and resource adapters). (If the number of resources is five or less, no change is required.)

If the maximum value is exceeded, a warning message (ots9017) is output and a value of 32 is set automatically.

Note

Since the concurrency of the resource management program is tuned to provide the maximum transaction processing performance, it is not necessary to change the default value.

When changing the value, set it in such a way that the thread concurrency of the OTS system has the following relationship with the concurrency of the resource management program:


Note 1:




E-13

OTS JTS’s RMP multiple degree of Thread

Specify the thread concurrency of the JTS resource control program of the Database Linkage Service.




Normally, modification is not required.

Note

Since the concurrency of the resource management program is tuned to provide the maximum transaction processing performance, it is not necessary to change the default value.

When changing the value, set it in such a way that the thread concurrency of the OTS system has the following relationship with the concurrency of the resource management program:


Note 1



OTS Participate

Specify the maximum number of resources to participate in one transaction.

You can specify this item when you select TYPE2 for operating mode and set "sys" for the OTS Setup mode.




OTS Host

Set the host name that operates the OTS system. This item can be specified where TYPE2 is selected for operating mode and “rmp” is set in the OTS Setup mode.


When the OTS Host is specified, the OTS Port and the OTS Locale must be specified at the same time.

For information on how to use this statement, refer to OTS Setup mode.

The string can contain up to 64 alphanumeric characters, a minus (-) or period (.), and must begin with an alphanumeric character, but must not end with a minus (-) or period (.).



E-14

OTS Port

Set the port number of the CORBA Service on the node on which the OTS system operates. This item can be specified where TYPE2 is selected for operating mode and “rmp” is set in the OTS Setup mode.



When the OTS Port is specified , the OTS Host and the OTS Locale must be specified at the same time.


OTS Locale

Set the locale of the node on which the OTS system operates. This item can be specified where TYPE2 is selected for operating mode and “rmp” is set in the OTS Setup mode.

The following three types of value can be specified:

"SJIS": Shift JIS

"EUC": EUC

"UNICODE": UNICODE


When the OTS Locale is specified, the OTS Host and the OTS Port must be specified at the same time.


Event Service

Specifies whether the Event Service is used.

“yes”: used

“no”: not used

When this statement is omitted, “no” is set as a default value.

Event Locale

Not used in the International version of Interstage.

Event maximum Process

Specify the maximum number of processes of the dynamically generated event channel.



Event Auto Disconnect

When using dynamically generated event channels, specifies whether to recover connection information remaining in the event channel when an application terminates without issuing a disconnect method to the event channel.

“yes”: Recovery

“no”: No recovery


E-15

The default is “no”.

Event maximum Connection

A consumer who connects with the event channel of the mixed model dynamically generated and a numerical total values (maximum, connected number) of the supplier are set.


When this statement is omitted, “5” is set as a default value.

When this statement is omitted, “50” is set as a default value.

InfoProvider Pro

Specifies whether Web Server (InfoProvider Pro) is used.

“yes”: used

“no”: not used

When this statement is omitted, “no” is set as a default value.

InfoProvider Pro Definition

Specifies the Web Server (InfoProvider Pro) environment definition file and ID.

Make the specification as follows:

Web environment definition file name: ID

The ID must be arbitrary string of up to 8 alphanumeric characters unique in the file.

Place a colon between the file name and ID.

This statement is mandatory if the Web Server (InfoProvider Pro) is used.

This statement may be specified multiple times.


Specify the environmental definition file name of a Web server (InfoProvider Pro) with a path absolutely.

Servlet

Specifies whether the Servlet Service is used.

“yes”: Used

“no”: Not used



E-16

SOAP Client GW

Specifies whether the CORBA/SOAP Client Gateway is used.

“yes”: Used

“no”: Not used


IS Monitor Mode

Specify the monitoring mode in the Interstage operation status. There are the following two types of monitoring modes. When the services constituting Interstage are suspended during Interstage operation, each monitoring mode behaves as follows:

• "model 1":

Stops Interstage if the services that comprise Interstage have stopped.

Continues operation of Interstage even if the Naming Service and the Interface Repository has stopped. If the other services than the above two have stopped, this monitoring mode stops Interstage.

• "model 2": Continues Interstage operation even if the Naming Service, the Interface Repository service, the Web Server, the Servlet Service, or the CORBA/SOAP Client Gateway is suspended. If services other than the above-mentioned are suspended, this monitoring mode stops Interstage.

In mode2, the definition change operation can be performed by stopping the web server, Servlet Service, and CORBA/SOAP Client Gateway during Interstage operation, and restarting the stopped service after changing the definition. For this purpose, the start and stop commands of each service are used.

If this statement is omitted, "model 1" is set as the default value.

F-1

Appendix F Definition Files Used in Operating the Performance Monitoring Tool

This appendix explains the files specified by the command when using the performance monitoring tool.

Appendix F: Definition Files Used in Operating the Performance Monitoring Tool

F-2

The Specification File for Performance Monitoring (ispstart Command)

This is the file which specifies the candidate for performance monitoring of the performance monitoring tool. It is specified as a parameter of the ispstart command.

Synopsis [Section name] Application for performance monitoring : [Section name] :

Specification Item The Section name is surrounded by [] and has the description "Application for performance monitoring" following it.

The candidate for performance monitoring can be specified up to 1000 entries.

The Section name which can be specified, and the item that can be specified in the Application for performance monitoring of each section are shown in the table below.

Section name Application for performance monitoring

EJB-APPLICATION Specifies Light EJB application.

EJBCONT Specifies Light EJB container or IJServer.

Definition Example An example description of a definition file is shown below: [EJB-APPLICATION] EJBCT1 EJBCT2 [EJBCONT] myserver IJServer_Split IJServer_EJB

G-1

Appendix G Systemwalker Linkage

This chapter describes the Systemwalker linkage function.

Appendix G: Systemwalker Linkage

G-2

Operation Monitoring and Automatic Operation Using the Systemwalker Linkage Function

By using the Systemwalker linkage function, business systems (WorkUnits) constructed using Interstage and servlet containers can be monitored with centralized management. It can be used only for previous versions of Servlet service.

Linkage to Systemwalker enables the following functions:

• Operation monitoring

• Remote operation

• Automatic operation

• Allocation of applications

Refer to the Systemwalker CentricMGR Manual and the Systemwalker OperationMGR Manual for details of how to set up and run Systemwalker, the remote operation function and the application allocation function.

Note

Depending on the version level of SystemWalker used for linkage, available functions may be limited. Refer to the Installation Guide to check the range of available functions.

Overview of the Systemwalker Linkage Function Interstage provides the following functions by linking to Systemwalker CentricMGR or Systemwalker OperationMGR.

Activity Monitoring by Linkage with Systemwalker CentricMGR • Monitoring the activity status of WorkUnits and objects

The activity status of WorkUnits and objects (the operation status, definition information, and other information of WorkUnits and objects) can be monitored from the Systemwalker CentricMGR operation client in real time.

The Systemwalker CentricMGR function informs the operator of the occurrence of abnormal events in real time. By creating any recovery processing and registering it to Systemwalker CentricMGR, it is also possible to execute recovery processing automatically when an error occurs.

For further details, refer to the Systemwalker CentricMGR Manual.

• Operating status monitoring of the servlet container (previous versions of Servlet service)

The operating status of the servlet container can be monitored in real time from the Systemwalker CentricMGR operation management client. It can be used only for previous versions of Servlet service.



Operation Monitoring and Automatic Operation Using the Systemwalker Linkage Function

G-3

• The number of resident queues (number of waiting messages) for the following items can be monitored in real time:

− EJB WorkUnit application (during operation in environments compatible with previous versions)

− Light EJB container (during operation in environments compatible with previous versions)



Automatic Control by Linkage with Systemwalker OperationMGR

• Automatic execution, monitoring, and operation of WorkUnits

By registering WorkUnits as jobs in the jobnet, WorkUnits can be started automatically, monitored and operated.

The WorkUnit can be operated (started, stopped) in accordance with a schedule.

For further details, refer to the Systemwalker OperationMGR Manual.

• Exclusive control of resources between WorkUnits and batch jobs

WorkUnits and batch jobs can be executed as a group. In this case, exclusive control can be made between WorkUnits and batch jobs.

The WorkUnit can be operated (started, stopped) in accordance with a schedule.

For further details, refer to the Systemwalker OperationMGR Manual.


G-4

Activity Monitoring by Systemwalker CentricMGR Linkage

With Interstage, you can monitor the activity status of WorkUnits and objects, by linking to Systemwalker CentricMGR. This also allows you to monitor the activity status of wrapper WorkUnits.

It is also possible to monitor the operating status of servlet containers (during operation in environments compatible with previous versions)

Real-time monitoring is performed via the application monitoring menu in SystemWalker/CentricMGR.

For details about preparing for operation and details about the application monitoring menu, refer to the Systemwalker CentricMGR Manual.

Operating Status Monitoring of WorkUnits and Objects The operating status of the WorkUnit (except IJServer) and object can be monitored using Systemwalker CentricMGR.

The information that can be monitored by Systemwalker CentricMGR is listed below.

WorkUnit Information

The items in Table G-1 are displayed as the WorkUnit information.

Table G-1 WorkUnit Information

Display Item

EJB Application (in old version

compatible environments)

Remarks

Name of display 0 Name given to the WorkUnit by the user

Name of WorkUnit 0

Type 0 Type of WorkUnit

Destination node of execution 0 Name of the host that is the destination of WorkUnit

execution

Operation status 0 Operation status of WorkUnit

0: Items to be displayed


G-5

Object Information

The items in Table G-2 are displayed as the information of the object.

Table G-2 Object Information

Display Item EJB Application Remarks

Name of object 0 In the case of an EJB application, the name of the application is displayed.

Resident - Operating mode of the object:

Resident/non resident/multi object resident

Number of waiting messages

0

Accumulated number of processing

0

EJB application mode 0

STATELESS Session Bean

STATEFUL Session Bean

Bean-managed persistence Entity Bean

Container-managed persistence Entity Bean

Message_driven Bean

EJB Container

Number of instances 0 (*1)


-: Items not to be displayed

(*1) For the number of instances, the following information is displayed depending on the EJB application mode:

− STATELESS Session Bean

The number of initial start instances that was set in the execution environment definition of the EJB application of the customizing tool is displayed (during operation in old version compatible environments).

− STATEFUL Session Bean

0 is displayed.

− Bean-managed persistence Entity Bean

The number of instances set in the high-speed calling definition of the customizing tool is displayed (during operation in old version compatible environments).

− Container-managed persistence Entity Bean



G-6

− Message_Driven Bean


− EJB Container

0 is displayed.

Object Details

The items in Table G-3 are displayed as the detailed information of the object.

Table G-3 Object Detailed Information

Display Item EJB Application Remarks

Mode of the EJB application

0 STATELESS Session Bean

STATEFUL Session Bean

Bean-managed persistence Entity Bean

Container-managed persistence Entity Bean

Message_driven Bean

EJB Container

Resident - Operating mode of the object:

Resident/non resident/multi object resident

Multi level of process

0

Thread concurrency

- (*1)

DPCF communication bus

-

Number of waiting messages

0

Number of instances

0 (*2)

Accumulated number of processing

0

Maximum number of queuing

-

Number of monitor queuing

-

Number of queues to start monitoring

-



G-7

-: Items not to be displayed

(*1) Not displayed when the CORBA WorkUnit is stopped

(*2) For the number of instances, the following information is displayed depending on the EJB application mode:

− STATELESS Session Bean

The number of initial start instances that was set in the execution environment definition of the EJB application of the customizing tool is displayed (during operation in old version compatible environments).

− STATEFUL Session Bean

0 is displayed.

− Bean-managed persistence Entity Bean


− Container-managed persistence Entity Bean


− Message_driven Bean


− EJB Container

0 is displayed.

Notes

• To display the latest information, execute “Detect Application”. Refer to the Systemwalker CentricMGR Manual for details on “Detect Application”.

• To use this function, it is necessary to start Interstage using the isstart command or Interstage Management Console. Do not use the start command for individual services. When using Interstage in a cluster system, follow the operation method for the cluster system.

• If the server in which Interstage is operating is turned off or disconnected from the communication line, the system is rebooted, or the Interstage system fails, the WorkUnit will remain in “operating” status. If this happens, perform recovery work by referring to the Systemwalker CentricMGR Manual.

• If an object has termination status, the object information cannot be acquired.

• If "daemon.notice;mail.crit" is set to /etc/syslog.conf, it does not need to describe it. Interstage 3.1 or an earlier version required that daemon.notice;mail.crit be written to /etc/sys/log.conf but Interstage 4.0 and later versions do not require it. This is especially noticeable in an environment where Interstage 3.1 or earlier was used.

An example of the default statement for installation of Systemwalker CentricMGR is shown below. If the default setting is acceptable, modify the statement as shown below. If customization is required, specify an arbitrary value instead of daemon.notice;mail.crit.


G-8

For SystemWalker/CentricMGR5.0 or 5.1

*.err;kern.debug;auth.notice /var/opt/FJSVsagt/fifo/slg

For SystemWalker/CentricMGR5.2

*.warning /var/opt/FJSVsagt/fifo/slg

Be sure to insert a tab between the first parameter ("*.err;kern.debug;auth.notice"etc.) and the second parameter ("/var/opt/FJSVsagt/fifo/slg"etc.) Note that no space can be permitted.

Next, load the setting to syslogd. Follow the procedure below:

1. Check the process ID of syslogd.

2. Execute the following command:

kill -HUP process id of syslogd

Operating Status Monitoring of the Servlet Container The operating status of the servlet container (which can be used only on old versions of Servlet service) can be monitored from Systemwalker CentricMGR.

Servlet Container Information

The items shown in Table G-4 are displayed as servlet container information.

Table G-4 Servlet Container Information Display Items Display Item Servlet Container Remarks

Display name Arbitrary name given to the servlet container by the user

Arbitrary name given to the servlet container by the user

Container name 0 -

type 0 "Servlet container" is displayed.

Execution destination host 0 Host name at the servlet container

execution destination

Operation status 0 Operating status of the servlet container


Notes

• To display the latest information, execute “Detect Application”. For further details, refer to the Systemwalker CentricMGR Manual.

• To use this function, it is necessary to start Interstage using the isstart command or Interstage Management Console. Do not use the start command for individual services. When using Interstage in a cluster system, follow the operation method for the cluster system.

• If the server in which Interstage is running is turned off or disconnected from the communication line, the system is rebooted, or the Interstage system fails, the WorkUnit will remain in “operating” status. If this happens, perform recovery by referring to the Systemwalker CentricMGR Manual.


G-9

Real-time Monitoring of Application Processing Status From Systemwalker CentricMGR, the number of resident queues (number of waiting messages) for EJB WorkUnit applications and Light EJB container can be monitored in real time during operation in old version compatible environments. (IJServer is not taken as an object.)

When monitoring the number of resident queues, the following three points can be monitored:

• When the number of queues exceeds the maximum number of queues

• When the number of queues reaches an arbitrary number of monitoring queues

• When the number of queues reaches the number of queues that restarts monitoring.

When the number of target resident queues for WorkUnit applications to be monitored reaches the above points, the status transition is displayed on the screen of the Systemwalker CentricMGR operation control client.

This enables real-time response to the increase and decrease of the queues.

To monitor the number of resident queues, perform the following operation.

Define Monitoring Values

EJB WorkUnit Applications and Light EJB Container (during operation in old version compatible environments).

To monitor the processing status of EJB WorkUnit applications and Light EJB container during operation in old version compatible environments in real time, define the following information used for monitoring the number of resident queues in the WorkUnit definition.

• Maximum number of queues This is the maximum number of queues. A message is output if this number is exceeded. Once this number has been exceeded, no queue number exceeded messages are output until the number of queues exceeds the restart monitoring number of queues.

• Number of monitor queues This specifies the number of queues at which an alarm is given (message is output). A message is output when this number is exceeded. . Once this number has been reached, no queue number exceeded messages are output until the number of queues exceeds the restart monitoring number of queues.

• Restart monitoring number of queues This specifies the number of queues at which monitoring is restarted when an alarm is given. If the number of queues exceeds the number of queues monitored, monitoring of queue numbers is restarted until the number of queues reaches this value. A message is output when monitoring of numbers of queues restarts.


G-10

Automatic Control by Systemwalker OperationMGR Linkage

With Interstage, you can also automate the following system operations and management tasks, by linking to Systemwalker OperationMGR:

• Automatic execution, monitoring, and operation of WorkUnits

By registering WorkUnits as jobs in the jobnet, WorkUnits can be started automatically, monitored and operated. IJServer is not taken as an object.

• Exclusive control of resources between WorkUnits and batch jobs

WorkUnits and batch jobs can be executed as a group. In this case, exclusive control can be made between WorkUnits and batch jobs. IJServer is not taken as an object.

Preparatory steps for creating Systemwalker linkage are explained below, along with a description of the operating method.

Preparations Follow the procedure below to register the WorkUnits in a jobnet.

1. Register a project. When you are scheduling WorkUnits, you must first register a project. Register a “project name” and an “owner name” for the project.

2. Register a jobnet. Register the jobs that make up the jobnet. An execution schedule is implemented for each jobnet. If you are using WorkUnits, register one WorkUnit in each jobnet.

3. Register jobnet information. Register the jobnet information (basic information / messages / start date / calendar / application time).

4. Register a jobnet start date. Register the day on which the jobnet is to start.

5. Register start date model. Register the model of the day on which the jobnet is to start.

6. Register jobs. Register the jobs. You must record the following WorkUnit information when registering jobs: − WorkUnit name

− Comments

− Requesting host name

− Queue name

− Resource name

− Resource allocation (shared/exclusive)

Automatic Control by Systemwalker OperationMGR Linkage

G-11

Operating Method The method for monitoring and operating a jobnet during application is described below.

1. Monitoring jobnet status. During use, monitor the jobnet status in the “Job List” and “Jobnet Monitoring” windows, as with batch jobs.

2. Operating jobnet. Implement jobnet operations (forced shut-down/startup/restart/termination/cancel termination/deactivate/cancel deactivate/confirm) as required.

3. Displaying history of jobnet. The history of a jobnet can be displayed, as and when necessary.

Note

To use this function, it is necessary to start Interstage using the isstart command. Do not use the start command provided by the components.

When using Interstage in a cluster system, follow the operation method of the cluster system.


G-12

Index-1

Index

activity management, G-4

allocation of applications, G-2

analysis performance information, 3-24

application status starting Interstage, C-19

application status types, C-33

automatic control, G-10

automatic operation, G-2

backup Component Transaction Service resource, 4-27 CORBA Service resource, 4-23 Database Linkage Service resource, 4-29 Event Service resource, 4-25 IJServer resource file, 4-33 InfoDirectory resource, 4-37 InfoProvider Pro resource, 4-31 Interstage Certificate Environment Resources, 4-39 Interstage HTTP Server resource, 4-30 Interstage JMS resource, 4-34 Interstage Operation Tool resources, 4-21 Interstage resources, 4-19 Interstage setup resource, 4-20 J2EE common resource file, 4-32 Portable-ORB resource, 4-26 Servlet Service for Interstage Management

Console resources, 4-35 Servlet Service resource, 4-40 SOAP Service resource, 4-35

changing system scale, C-35

Component Transaction Service Resource File, 4-9

CORBA Service operating environment definition tuning using, C-45

CORBA Service Resource File, 4-5

CORBA_SOAP ClientGW Windows service, C-23, C-24

customization CORBA/SOAP Client Gateway, C-12 Database Linkage Service, C-12 Event Service, C-11 Servlet Service, C-12 WWW Server Service, C-12

customization Naming Service and Interface Repository, C-10

customization ismodifyservice command, C-29

customizing Interstage, C-14 load balance, C-16 Mode 1, C-16 Mode 2, C-16 operating status monitoring mode, C-16

database linkage startup, C-20

Database Linkage Service Resource File, 4-10

definition file, C-3 system scale, C-3

definition files location, C-5, C-6 usage, C-6

definitions Interstage operating environment definition, E-2 Interstage system definition, D-2

environment setup procedure, C-2

environment definition CORBA Service, C-5 Database Linkage Service, C-5

Operator's Guide - Index

Index-2

Event Service Resource File, 4-8

EventFactory Windows service, C-23, C-24

EventService Windows service, C-23, C-24

F3FMwww Windows service, C-23, C-24

IJServer Resource Files, 4-13

import Component Transaction Service resource, 4-72 CORBA Service resource, 4-71 Database Linkage Service resource, 4-73 Event Service resource, 4-72 IJServer resource file, 4-74 InfoProvider Pro resource, 4-73 Interstage Certificate Environment resources, 4-74 Interstage HTTP Server resource, 4-73 Interstage JMS resource, 4-74 Interstage Operation Tool resource, 4-70 Interstage resources, 4-67 Interstage setup resource, 4-68 J2EE common resource file, 4-73 old version Servlet Service resource, 4-74 Portable-ORB resource, 4-72 Servlet Service for Interstage Management

Console resources, 4-74 SOAP Service resource, 4-74

InfoDirectory Directory Service Resource File, 4-16

InfoProvider Pro Resource File, 4-11

initialization, C-14 isinit command, C-13

Interface Repository changing settings, C-39 designing, C-17

InterfaceRep_Cache Service Windows service, C-23, C-24

InterfaceRep_Cache_e Service Windows service, C-23, C-24

Interstage automatic start, C-22 boot-up start, C-22

constructing the environment, C-22 determining services to be initialized, C-7 environment setup, C-2 initializing, C-7 moving resources to another server, 4-65 resource backup procedure, 4-19 resource importing procedure, 4-67 resource restore procedure, 4-43 service creation, C-23, C-24 start verification, C-23 Windows service, C-23, C-24

Interstage API Windows service, C-23, C-24

Interstage Certificate Environment Resource File, 4-17

Interstage HTTP Server Resource File, 4-11

Interstage JMS Resource File, 4-14

Interstage JServlet Windows service, C-23, C-24

Interstage operating environment definition customizing, C-8 syntax, E-2

Interstage operating environment definition file syntax, E-3

Interstage Operation Tool Resource File, 4-4

Interstage operations by Interstage Integrated Commands, C-1

Interstage Setup Resource File, 4-3

Interstage system definition blank lines, D-3 comment line, D-3 statement, D-2 syntax, D-2

Interstage system definition file syntax, D-4

isconfig.xml, B-1

isgendef command, C-3

isinit command, C-13

ismodifyservice command, C-29

ispdeleteenv command, 3-3, 3-23


Index-3

ispmakeenv command, 3-3

ispreport command, 3-3, 3-21

ispsetagt command, 3-3

ispstart command, 3-3

ispstatus command, 3-3

ispstop command, 3-3

ispunsetagt command, 3-3, 3-24

isregistdef command, C-5

isstart command, C-20

isstartwu command, C-22

isstop command, C-28

isstopwu command, C-27

J2EE Common Resource Files, 4-13

jobnet, G-10

load balance, C-16

log monitoring with, 3-1, 3-4

MIB, 3-1, 3-6 monitoring with, 3-1, 3-6 Systemwalker functionality, 3-6

MIB definition file, 3-14

monitoring real-time, 3-12

moving Interstage resources to another server, 4-65

Naming Service changing settings, C-39 designing, C-17 Windows service, C-23, C-24

Network Control Manager, 3-16 collecting performance information, 3-30 functionality, 3-6

object operating status monitoring, G-4

objects monitoring activity, G-2

OD_HOME, C-5, C-6

OD_start Windows service, C-23, C-24

operating a jobnet, G-11

operating environment definition customization, C-14

operating mode, C-8 TYPE1, C-8 TYPE2, C-8 TYPE3, C-8

operating status monitoring, G-4

operating status monitoring mode, C-16

operation monitoring, G-2

OTS_HOME, C-5, C-6

otsstartrsc command, C-21

otsstoprsc command, C-27

outputting log information to performance log file, 3-24

outputting the performance log file and analyzing the performance information, 3-21

overview changing system operation status, C-32 changing system scale, C-35 real-time monitoring, 3-17

performance abnormality, 3-21

performance information, 3-24 analysis, 3-24 display, 3-18, 3-19 real time monitoring, 3-30

performance information items, 3-19

performance information tool warning, 3-32

performance log file outputting, 3-21

performance log file report, 3-21

performance log files disk space required, 3-33 managing, 3-33

performance monitoring


Index-4

installation procedure, 3-7, 3-10

performance monitoring tool commands, 3-2 creating the environment, 3-16 functions, 3-1, 3-4 information collected, 3-4 monitoring performance information, 3-1, 3-6 output log data, 3-1, 3-4 overview, 3-2 starting, 3-16

Portable-ORB Resource File, 4-8

real time monitoring Network Control Manager, 3-30

real-time monitoring, 3-1, 3-12 overview, 3-17

registering a jobnet, G-10

remote operation, G-2

resource manager terminating, C-27

Resource Manager, C-21 startup, C-21

resources backing up/restoring, 4-2

restore Component Transaction Service resource, 4-50 CORBA Service resource, 4-47 Database Linkage Service resource, 4-51 Event Service resource, 4-48 IJServer resource file, 4-56 InfoDirectory resource, 4-59 InfoProvider Pro resource, 4-53 Interstage Certificate Environment Resources, 4-61 Interstage HTTP Server resource, 4-52 Interstage JMS resource, 4-57 Interstage Operation Tool resource, 4-45 Interstage resources, 4-43 Interstage setup resource, 4-44 J2EE common resource file, 4-55 old version Servlet Service resource, 4-61 Portable-ORB resource, 4-49 Servlet Service for Interstage Management

Console resources, 4-58

SOAP Service resource, 4-58

servlet container operating status monitoring, G-8

Servlet Service for Interstage Management Console Resource File, 4-15

Servlet Service Resource File, 4-17

Session Registry Server Resource File, 4-18

SNMP service, 3-12

SOAP Service Resource File, 4-15

start Interstage, C-22

system definition file, C-3 registering, C-5

system operation status changing, C-32

system scale, C-3, C-35

system scales, C-36

Systemwalker activity monitoring, G-2 linkage function, G-2 MIB functionality, 3-6

SystemWalker MIB, 3-1

Systemwalker CentricMGR servlet container operating status monitoring, G-8

Systemwalker linkage function, G-2

Systemwalker OperationMGR linkage, G-10

TD_HOME, C-5, C-6

terminating Interstage, C-26

Transaction Director Windows service, C-23, C-24

Windows services CORBA_SOAP ClientGW, C-23, C-24 creating, C-22, C-24 EventFactory, C-23, C-24 EventService, C-23, C-24 F3FMwww, C-23, C-24 InterfaceRep_Cache Service, C-23, C-24


Index-5

InterfaceRep_Cache_e Service, C-23, C-24 Interstage, C-23, C-24 Interstage API, C-23, C-24 Interstage JServlet, C-23, C-24 Naming Service, C-23, C-24 OD_start, C-23, C-24 Transaction Director, C-23, C-24

WorkUnit monitoring activity, G-2 operating status monitoring, G-4 terminating, C-27


Index-6

Documents

Interstage Application Server V6.0 Operator's Guidesoftware.fujitsu.com/jp/manual/fm_e/b23j32k08/0610m02/01/np_isg.pdf · Sun, Solaris, Java, and other trademarks ... This document