Appendix E.1 Procedure for starting a system
This section explains a procedure for starting a system.
- Note
- In a system, depending on the system configuration, there are cases when only the Application Servers are started, while in some cases the integrated naming scheduler servers, and session failover servers are also started with the Application Servers.
- When you start an integrated naming scheduler server and a session failover server with the Application Server, take note of the following:
- When you use the session failover server, start it before you start the Application Server.
- You can start the integrated naming scheduler server in any order.
The procedure for starting an Application Server, an integrated naming scheduler server, and a session failover server is explained below.
Note that as a prerequisite, the related products such as database, LDAP directory server, and EIS must already be started. When you use a database, LDAP directory server, and EIS, start them in advance, as required.
- Organization of this subsection
- (1) Flow of starting an Application Server
- (2) Flow of starting an integrated naming scheduler server
- (3) Flow of starting a session failover server
(1) Flow of starting an Application Server
This point explains the flow of starting the Application Server that you use in the system.
Here, the flow of starting an application server is explained for a standard system configuration, and for a configuration using CTM.
The following figure shows the flow of starting an Application Server:
Figure E-1 Flow of starting an Application Server (in UNIX)
![[Figure]](figure/zu0a1015.gif)
Steps 1 to 11 of the figure are explained below:
- Specifying environment variables
Specify environment variables. For details on setting environment variables, see E.2 (1) Specifying environment variables when a system is started.
- Starting a PRF daemon
Start a PRF daemon using the cprfstart command. For details on starting a PRF daemon, see E.2 (2) Starting a PRF daemon.
- Starting the Smart Agent
If you are not using CTM, this operation is not required.
Start the Smart Agent using the osagent command. For details on starting the Smart Agent, see E.2 (3) Starting the Smart Agent.
- Starting the CTM domain manager
If you are not using CTM, this operation is not required.
Start the CTM domain manager using the ctmdmstart command. For details on starting the CTM domain manager, see E.2 (4) Starting the CTM domain manager.
- Invoking the CORBA Naming Service
We recommend that you invoke the CORBA Naming Service for a J2EE server as an in-process, when you start the J2EE server.
For details on invoking the naming service as an out-process, see E.2 (5) Invoking the CORBA Naming Service.
- Starting a CTM daemon
If you are not using CTM, this operation is not required.
Start a CTM daemon using the ctmstart command. For details on starting a CTM daemon, see E.2 (6) Starting a CTM daemon.
- Starting an SFO server
This operation is not required if you do not start SFO server. Additionally, this operation is also not required if you do not start an SFO server within the Application Server.
Specify the -nosecurity option in the cjstartsv command, and start an SFO server. Additionally, if SFO server applications are not running when an SFO server is started, start SFO server applications using the server management command (cjstartapp).
For details on starting SFO servers and applications, see E.2 (7) Starting an SFO server.
- Starting a J2EE server
Start a J2EE server using the cjstartsv command. For details on starting J2EE servers, see E.2 (8) Starting a J2EE server.
- Starting a resource
This operation is not required if you are not using any resources.
Additionally, this operation is also not required if you are using resource adapters included in the J2EE application.
Start a resource using server management commands. For details on starting resources, see E.2 (9) Starting a resource.
- Starting a J2EE application
Start a J2EE application using server management commands. Note that in the case of a J2EE application containing resource adapters, all the resource adapters included in the J2EE application are started at the same time. For details on starting a J2EE application, see E.2 (10) Starting a J2EE application.
- Starting a Web server
For details on starting a Web server, see the manual on the Web server you are using.
Note that the timing of starting the Web server depends on the mode of system operation, but you can start the Web server in this order for controlling the reception of requests in the J2EE application. After starting the Web server, the reception of requests in the J2EE applications from the Web client starts. For details on starting a Web server, see E.2 (11) Starting a Web server.
Furthermore, if you are using an in-process HTTP server, you need not start a Web server.
(2) Flow of starting an integrated naming scheduler server
The following figure shows the flow of starting an integrated naming scheduler server:
Figure E-2 Flow of starting an integrated naming scheduler server (in UNIX)
![[Figure]](figure/zu0a1025.gif)
Steps 1 to 6 shown in the figure are as follows:
- Specifying environment variables
Specify environment variables. For specifying the environment variables, see E.2 (1) Specifying environment variables when a system is started.
- Starting a PRF daemon
Start a PRF daemon using the cprfstart command. For details on starting a PRF daemon, see E.2 (2) Starting a PRF daemon.
- Starting the Smart Agent
Start the Smart Agent using the osagent command. For details on starting the Smart Agent, see E.2 (3) Starting the Smart Agent.
- Starting the CTM domain manager
Start the CTM domain manager using the ctmdmstart command. For details on starting the CTM domain manager, see E.2 (4) Starting the CTM domain manager.
- Invoking the CORBA Naming Service
Invoke the global CORBA Naming Service for CTM. For details on invoking the CORBA Naming Service, see E.2 (5) Invoking the CORBA Naming Service.
- Starting a CTM daemon
Start a CTM daemon using the ctmstart command. For details on starting a CTM daemon, see E.2 (6) Starting a CTM daemon.
(3) Flow of starting a session failover server
The following figure shows the flow of starting a session failover server:
Figure E-3 Flow of starting a session failover server (in UNIX)
![[Figure]](figure/zu0a1035.gif)
Steps 1 to 3 in the figure are explained below:
- Specifying environment variables
Specify environment variables. For details on specifying environment variables, see E.2 (1) Specifying environment variables when a system is started.
- Starting a PRF daemon
Start a PRF daemon with the cprfstart command. For details on starting a PRF daemon, see E.2 (2) Starting a PRF daemon.
- Starting an SFO server
Start an SFO server by specifying the -nosecurity option in the cjstartsv command. Additionally, if SFO server applications are stopped when an SFO server is started, start SFO server applications using the server management command (cjstartapp).
Note that we recommend you to disable the settings of the Explicit Memory Management functionality using SFO servers.
For details on starting SFO servers and applications, see E.2 (7) Starting an SFO server.
- Note
- You can only execute the SFO server applications in an SFO server. Do not execute other applications in the SFO server.