D.1 Procedure for starting a system

This section explains a procedure for starting a system.

Important note

In some system configurations, you need to start not only the application server, but also the integrated naming scheduler server.

If you need to start the application server and the integrated naming scheduler server, note the following:

You can start the integrated naming scheduler servers in any order.

The following describes the procedure for starting the application server and the procedure for starting the integrated naming scheduler server.

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

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

Steps 1 to 10 of the figure are explained below:

Setting the environment variables used during system startup

Specify environment variables. For details on setting environment variables, see D.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 D.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 D.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 D.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 D.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 D.2 (6) Starting a CTM daemon.
Starting a J2EE server

Start a J2EE server using the cjstartsv command. For details on starting J2EE servers, see D.2 (7) 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 D.2 (8) 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 D.2 (9) 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 D.2 (10) Starting a Web server.

To Page Top

(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 UNIX)

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

Setting the environment variables used during system startup

Specify environment variables. For specifying the environment variables, see D.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 D.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 D.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 D.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 D.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 D.2 (6) Starting a CTM daemon.

To Page Top