Appendix D.1 Procedure for starting a system

The procedure for starting a system is explained in this section.

Note
Depending on the system configuration there are some cases where only the Application Servers are started, while in other cases 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 an Application Server, take note of the following:
  • When you use a session failover server, start the session failover server before you start an Application Server.
  • You can start the integrated naming scheduler server is 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 be already started. If you are using 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

The flow of starting an Application Server is explained.

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 D-1 Flow of starting an Application Server (in Windows)

[Figure]

Steps 1 to 11 shown in the figure are explained below:

  1. Specifying environment variables
    Specify environment variables. For details on specifying the environment variables, see D.2 (1) Specifying environment variables when a system is started.
  2. Starting a PRF daemon
    Start a PRF daemon using the cprfstart command. For details on starting a PRF daemon, see D.2 (2) Starting a PRF daemon.
  3. 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 D.2 (3) Starting the Smart Agent.
  4. 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 D.2 (4) Starting the CTM domain manager.
  5. Invoking the CORBA Naming Service
    We recommend that you invoke the CORBA Naming Service for the J2EE server as an in-process, when you start the J2EE server.
    For details on invoking the CORBA Naming Service as an out-process, see D.2 (5) Invoking the CORBA Naming Service.
  6. 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 D.2 (6) Starting a CTM daemon.
  7. Starting an SFO server
    If you do not start an SFO server, this operation is not required. Additionally, when you do not start an SFO server in an Application Server, this operation is not required.
    Specify the -nosecurity option in the cjstartsv command for starting an SFO server. Additionally, if an SFO server application is stopped when the SFO server is started, start the SFO server application using the server management command (cjstartapp).
    For details on starting an SFO server and applications, see D.2 (7) Starting an SFO server.
  8. Starting a J2EE server
    Start a J2EE server using the cjstartsv command. For details on starting a J2EE server, see D.2 (8) Starting a J2EE server.
  9. Starting a resource
    If you are not using any resources, this operation is not required. Additionally, when you are using a resource adapter included in the J2EE application, this operation is not required.
    Start resources using the server management command (cjstartrar or cjstartjb). For details on starting resources, see D.2 (9) Starting a resource.
  10. Starting a J2EE application
    Start a J2EE application using the server management command (cjstartapp). Note that for 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 D.2 (10) Starting a J2EE application.
  11. 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 a Web server depends on the form of system operation, but you can start the Web server in the given order for controlling the request receptions in the J2EE application. After starting the Web server, start the reception of requests in the J2EE application from Web clients. For details on starting a Web server, see D.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 D-2 Flow of starting an integrated naming scheduler server (in Windows)

[Figure]

Steps 1 to 6 shown in the figure are as follows:

  1. Specifying environment variables
    Specify environment variables. For details on specifying the environment variables, see D.2 (1) Specifying environment variables when a system is started.
  2. Starting a PRF daemon
    Start a PRF daemon using the cprfstart command. For details on starting a PRF daemon, see D.2 (2) Starting a PRF daemon.
  3. Starting the Smart Agent
    Start the Smart Agent using the osagent command. For details on starting the Smart Agent, see D.2 (3) Starting the Smart Agent.
  4. Starting the CTM domain manager
    Start the CTM domain manager using the ctmdmstart command. For details on starting the CTM domain manager, see D.2 (4) Starting the CTM domain manager.
  5. Invoking the CORBA Naming Service
    Invoke the global CORBA Naming Service for CTM. For details on invoking the CORBA Naming Service, see D.2 (5) Invoking the CORBA Naming Service.
  6. Starting a CTM daemon
    Start a CTM daemon using the ctmstart command. For details on starting a CTM daemon, see D.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 D-3 Flow of starting a session failover server (in Windows)

[Figure]

Steps 1 to 3 shown in the figure are explained below:

  1. Specifying environment variables
    Specify environment variables. For details on specifying environment variables, see D.2 (1) Specifying environment variables when a system is started.
  2. Starting a PRF daemon
    Start a PRF daemon using the cprfstart command. For details on starting a PRF daemon, see D.2 (2) Starting a PRF daemon.
  3. Starting an SFO server
    Start an SFO server by specifying the -nosecurity option in the cjstartsv command. Additionally, if an SFO server application is stopped when an SFO server is started, start an SFO server application using the server management command (cjstartapp).
    For details on starting SFO servers and applications, see D.2 (7) Starting an SFO server.
    Note
    You can only execute SFO server applications in an SFO server. Do not execute other applications in the SFO server.