Hitachi

uCosminexus Service Platform Setup and Operation Guide


5.3.9 Starting standard receptions

This subsection describes the prerequisites and methods for starting the standard reception.

Organization of this subsection

(1) Prerequisites

To start the standard reception, the HCSC server must be in running status.

For details on how to check HCSC server status, see "5.3.15 Checking the HCSC server information".

(2) Starting method

This subsection describes how to start the standard reception.

Important note

If startup of the standard reception fails, eliminate the cause of the error, and forcibly stop the standard reception. Once the standard reception is in stopped status, start it again and then restart operations. For details on how to forcibly stop the standard reception, see "5.3.33 Terminating the Standard Reception".

(a) When using screens

The procedure of starting the standard reception by using screens in the operating environment is as follows:

  1. In the Tree view, double-click the HCSC server on which the standard reception is to be started.

    Information of the double-clicked HCSC server is displayed in the editor area.

  2. 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 for an HCSC server, see "4.4 Operations Page" in "Service Platform Reference Guide".

  3. Check the contents displayed in the Operations page, and, click the [Start] button of "Standard reception".

    A dialog confirming startup of the standard reception is displayed.

  4. Check the contents displayed in the dialog, and click the [OK] button.

    The process to standard reception is initiated A Log during startup process is displayed in the console view.

    If you click the [Cancel] button, the system returns to the Operations page without executing startup process.

    When the process of starting the standard reception is complete, a dialog showing the execution result is displayed.

  5. Check the dialog showing the execution result.

    If startup process is successful:

    Click the [OK] button to return to the Operations page.

    On the Operations page, the operating status of the standard reception changes to "Started status". Also, the [Start] button is disabled and the [Normal Stop] and [Planned Stop] buttons are enabled.

    If startup process fails:

    Contents of the error are displayed in a dialog. Take appropriate actions, by checking the message ID displayed in the detail information.

(b) When using commands

To start the standard reception, execute the cscrcptnstart command or cscutil command in the operating environment.

Use the cscrcptnstart command and the cscutil command in the following cases:

  • Cscrcptnstart command

    To start the standard reception in the operating environment in which the corresponding repository exists

  • Cscutil command

    To start the standard reception in an environment (for example, execution environment directly operating in JP1) in which you can use the cscutil command and the corresponding repository does not exist.

The description of how to execute each command is as follows:

When using the cscrcptnstart command

Execute the cscrcptnstart command in the operating environment.

For details on the cscrcptnstart command, see "cscrcptnstart (Starting standard receptions and user-defined receptions)" in "Service Platform Reference Guide"

Execution format of the cscrcptnstart command is as follows:

To start standard receptions of all HCSC servers in the cluster in a batch (for each cluster)

Execute the command by specifying the cluster name.

The standard receptions of all HCSC servers within the cluster specified in the -cluster option are started in a batch (all the non-started user-defined receptions are also started concurrently).

cscrcptnstart -user <login user ID> -pass <login password> -cluster <cluster name>

If you want to start only the standard reception without starting the user-defined reception, specify the -standard option.

cscrcptnstart -user <login user ID> -pass <login password> -cluster <cluster name> -standard
To start standard receptions for the HCSC server in a batch (for each HCSC server)

Execute the command by specifying the HCSC server name.

The standard reception for the HCSC server specified in the -csc option is started (all the non-started user-defined receptions are also started concurrently).

cscrcptnstart -user <login user ID> -pass <login password> -csc <HCSC server name>

If you want to start only the standard reception without starting the user-defined reception, specify the -standard option.

cscrcptnstart -user <login user ID> -pass <login password> -csc <HCSC server name> -standard
When using the cscutil command

Execute the cscutil command in the operating environment. Also, specify request_service in the -target option and specify start in the -operation option.

For details on the cscutil command, see "cscutil (Various operations)" in "Service Platform Reference Guide".

Execution format of the cscutil command differs depending 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 the J2EE server name.

cscutil -user <login user ID> -pass <login password> -mng <Manager name> -target request_service -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 specified in the cscutil command. For details on the cscrepls command, see "cscrepls (Displaying the repository information)" in "Service Platform Reference Guide"

When you use the property definition file

Specify the name of the property definition file name in the -propfile option. You must create the property definition file beforehand in the J2SE property file format.

cscutil -user <login user ID> -pass <login password> -mng <Manager name> -target request_service -operation start -propfile <property definition file name>