5.3.4 Starting HCSC server
This subsection describes the prerequisites and method to start HCSC servers.
- Organization of this subsection
(1) Prerequisites
When you start a HCSC server, if the HCSC server, the service adapter, or the business process fails to start, the service adapter and the business process as well as the user-defined reception and standard reception might change to the stopped status. In such cases, you need to remove the cause of the error and restart the service adapter and the business process as well as the user-defined reception and the standard reception.
For details on how to start the service adapter and business process, see "5.3.6 Starting Service Adapters", or "5.3.7 Starting Business Processes". For details on how to start the receptions, see "5.3.8 Starting user-defined receptions", and "5.3.9 Starting standard receptions".
(2) Starting method
The methods to start the HCSC server are as follows:
(a) When using screens
Procedure to start the HCSC server by using screens in the operating environment is as follows:
-
In the tree view, double-click the HCSC server to be started.
Information on the selected HCSC server is displayed in the editor area.
-
In the editor area, select the [Operations] tab.
The Operations page displays information on operations of the HCSC server you selected in step 1.
For details on the Operations page of an HCSC server, see "4.4 Operations Page" in "Service Platform Reference Guide".
-
Check the contents displayed in the Operations page, and click the [Start] button of "HCSC-Server".
A dialog box confirming startup of the HCSC server is displayed.
-
Check the information displayed in the dialog, and click the [OK] button.
HCSC server startup processing begins. Log information during startup processing is output in the console view.
If you click the [Cancel] button, the system returns to the Operations page without executing startup processing.
When HCSC server startup processing is completed, a dialog indicating the execution result is displayed.
-
Check the dialog that displays the execution result.
- If startup processing is successful:
-
Click the [OK] button to return to the Operations page.
On the Operations page, the operating status of HCSC server changes to. [Start status]. Also, the [Start] button is disabled and the [Stop] button is enabled.
- If startup processing fails
-
The contents of error are displayed in the dialog. Take appropriate action by referencing the message ID displayed in the detail information.
(b) When using commands
To start the HCSC server, execute the cscsvstart command or the cscutil command in the operating environment. To start HCSC servers in the cluster as a batch, or to start a logical server, execute the cscsvstart command.
Use the cscsvstart and cscutil commands in the following cases:
-
cscsvstart command
To start the HCSC server in the operating environment in which the corresponding repository exists
-
cscutil command
To start the HCSC server in an environment (for example, execution environment directly operating in JP1) in which the cscutil command can be used and the corresponding repository does not exist.
The method of executing each command is as follows:
- In case of the cscsvstart command
-
Execute the cscsvstart command in the operating environment.
For details on the cscsvstart command, see "cscsvstart (Starting an HCSC server)" in "Service Platform Reference Guide".
The execution format of the cscsvstart command is as follows:
- To start all HCSC servers in the cluster in a batch
-
Execute the command by specifying the cluster name. All HCSC servers in the cluster specified in the -cluster option are started in a batch (the logical server does not start).
cscsvstart -user <login-user-ID> -pass < login-password > -cluster <cluster-name >
To start logical servers concurrently with HCSC servers in the cluster, specify the -system option. However, logical servers must be registered in the HCSC-Manager definition files.
For details on registering logical servers, see, "5.3.1(1) Preparation before starting operations".
cscsvstart -user <login-user-ID> -pass <login password> -cluster <cluster name> -system
Furthermore, if you want to start only the logical server without starting the HCSC server, specify the -logical option.
cscsvstart -user <login user ID> -pass <login password> -cluster <cluster name> -logical <logicalservername>
- To start each HCSC server one by one
-
Execute the command by specifying the HCSC server name. The HCSC server specified with the -csc option is started (the logical server is not started).
cscsvstart -user <login user ID> -pass <login password> -csc <HCSC server name>
To start the HCSC server and the logical server at the same time, specify the -system option.
cscsvstart -user <login user ID> -pass <login password> -csc <HCSC server name> -system
Furthermore, if you want to start only the logical server without starting the HCSC server, specify the -logical option.
cscsvstart -user <login user ID> -pass <login password> -csc <HCSC server name> -logical <logicalservername>
- In case of the cscutil command
-
Execute the cscutil command in the operating environment. Specify server in the -target option and start in the -operation option.
For details on the cscutil command, see "cscutil (Various operations)" in "Service Platform Reference Guide".
The execution format of the cscutil command depends on whether you use the property definition file.
- When you do not use the property definition file
-
In the -props option, specify the HCSC server name and J2EE server name.
cscutil -user <login user ID> -pass <login password> -mng <Manager name> -target server -operation start -props "CSCSrvName=<HCSC server name>, J2EESrvName=<J2EE server name>"
You can use the cscrepls command to check the Manager name, the HCSC server name, and the J2EE server name that are specified in the cscutil command. For details on the cscrepls command, see "cscrepls (Displaying the repository information)" in "Service Platform Reference Guide".
- When using the property definition file
-
Specify the name of the property definition file in the -propfile option. The property definition file must be created beforehand in the J2SE property file format.
cscutil -user <login user ID> -pass <login password> -mng <Manager name> -target server -operation start -propfile <proeprtydefinitionfilename>