Topics: |
If you are running on Windows, go to Class Path and Service Manager Restart Issues.
Shell scripts are installed with iWay to run Service Manager on UNIX, OS/400, and z/OS systems. The shell scripts require that the JAVA command is included in your $PATH environment variable. Environment variables must be set for the user IDs that start Service Manager as explained in the iWay Installation and Configuration documentation.
The following are ways to run Service Manager:
Note: Running Service Manager normally refers to running the base configuration unless another configuration is specifically mentioned. When you installed Service Manager, a base configuration of Service Manager was created and this is used by default. Also note the following:
How to: |
When you run Service Manager as a service (daemon), it runs in the background as the user ID specified in its startup and shutdown scripts. Shell scripts to start and stop Service Manager as a service (daemon) are in the iway7/bin directory.
On UNIX, z/OS, and OS/400, the startup script is:
iway7/bin/startservice.sh
On UNIX, z/OS, and OS/400, the shutdown script is:
iway7/bin/stopservice.sh
Note: On z/OS, these scripts must be EBCDIC.
The scripts set several environment variables. On UNIX and OS/400, the installation program sets them for you. You can edit the scripts if you wish to change these settings. On z/OS, you must manually edit the scripts to set the following variables.
Is the location where iWay Service Manager is installed.
Is the user ID under which Service Manager runs. When you run the scripts as a non-super user ID (not root), you are prompted for the user ID password. On most UNIX systems, the default is root. For security reasons, you may decide not to run Service Manager as root.
Is the configuration to run. This is set to base by default.
The scripts also specify the log file for the service. By default these are:
iway7/serviceOut.txt
iway7/serviceShutdown.txt
If you create copies of the startup and shutdown scripts in order to run multiple configurations, ensure each script has a unique log file.
Note: If the JAVA command is in your $PATH variable, you usually are not required to set it in the script. However, if you run into problems, edit the script so that the full path to the JAVA command appears instead of "java."
To start Service Manager as a service (daemon):
/opt/iway7/bin
./startservice.sh
If you are not a super user, you are prompted for the password of the user ID under which Service Manager runs.
Password:
The configuration of Service Manager is started in the background and includes SOAP and HTTP listeners. A serviceOut.txt file appears in the iway7 directory and contains log information.
To stop Service Manager as a service (daemon):
/opt/iway7/bin
./stopservice.sh
If you are not a super user, you are prompted for the password of the user ID under which Service Manager runs.
Password:
Note: If you receive an error, ensure the user ID is defined in the shutdown script file.
A serviceShutdown.txt file appears in the iway7 directory and contains log information about the shutdown process.
How to: |
For debugging purposes, you can run Service Manager in the shell (or QSH) in an interactive and diagnostic (non-service) mode.
To run Service Manager in the shell as a non-service:
/opt/iway7
./iway7.sh configname
where:
Is the name of the Service Manager configuration you want to start.
Service Manager starts and messages display information about the startup process. When Service Manager has completely started, the following prompt appears:
Enter command:>
This prompt enables you to interact with Service Manager and displays diagnostic information about Service Manager processing.
Caution: If you previously ran Service Manager as a service under a user ID such as root and then run Service Manager in the shell as a different user ID, you may encounter permission problems. Files created while Service Manager ran as a service may not be readable or writable to the user ID running Service Manager in the shell.
To stop Service Manager running in the shell as a non-service:
Enter command:>
stop
quit
On non-z/OS systems, go to Class Path and Service Manager Restart Issues.
On z/OS systems, you can also start Service Manager as a batch process using JCL.
The following sample JCL starts Service Manager in batch. Substitute the appropriate job card and HFS locations on your system.
//EDABGBPX JOB (SMITH),'JAVA BPXBATCH',CLASS=A,MSGLEVEL=(1,1), // MSGCLASS=X,REGION=0M,NOTIFY=EDABG,USER=EDABG1,PASSWORD=XXXXXXX //******************************************************************** //* RUN JAVA UNDER A UNIX SYSTEM SERVICE SHELL //******************************************************************** //STEP2 EXEC PGM=BPXBATSL, // PARM='PGM /bin/sh /u/edabg1/iway7sm/iway7.sh base -c' //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //STDENV DD * JAVA_HOME=/usr/lpp/java/J1.5 PATH=/usr/lpp/java/J1.5/bin //
The following sample JCL stops Service Manager in batch. Substitute the appropriate job card and HFS locations on your system.
//EDABGBPS JOB (SMITH),'JAVA BPXBATCH',CLASS=A,MSGLEVEL=(1,1), // MSGCLASS=X,REGION=0M,NOTIFY=EDABG,USER=EDABG1,PASSWORD=XXXXXXX //******************************************************************** //* RUN JAVA UNDER A UNIX SYSTEM SERVICE SHELL //******************************************************************** //STEP2 EXEC PGM=BPXBATSL, // PARM='PGM /bin/sh /u/edabg1/iway7sm/bin/iway7sd.sh' //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //STDENV DD * PATH="/usr/local/diff/bin:.:/usr/lpp/java/J1.5 /bin:/bin::/usr/local/bin /usr/local/subin:/usr/sbin"1.5/bin' LIBPATH=/lib:/usr/lib:/usr/lpp/java/J1.5/bin:. JAVA_HOME=/usr/lpp/java/J1.5 //