Hitachi

uCosminexus Application Server Command Reference Guide


mngsvrctl (start, stop, or setup Management Server)

Organization of this page

Format

To start Management Server:
In Windows:
mngsvrctl start [-sync [-timeout synchronous-execution-timeout-time]]
In UNIX:
mngsvrctl start [-sync [-timeout synchronous-execution-timeout-time]] [-daemon]
To stop Management Server:
In Windows:
mngsvrctl stop [-sync [-timeout synchronous-execution-timeout-time]]
In UNIX:
mngsvrctl stop [-sync [-timeout synchronous-execution-timeout-time]]
To set up Management Server:
In Windows:
mngsvrctl setup [server-name] [-u management-user-ID] [-p management-user-password] [-np new-management-user-password] [-nu new-user-ID]
In UNIX:
mngsvrctl setup [server-name] [-u management-user-ID] [-p management-user-password] [-np new-user-password] [-nu new-user-ID]

Function

This command starts or stops Management Server or specifies the settings as required for running Management Server on the machine on which Application Server was first configured.

You can setup the management user account (management user ID and management user password) for logging in to Management Server simultaneously while performing setup, when the functionality for omitting the admin user account is disabled. If the admin user account is not specified during setup , you must specify the admin user account while starting or stopping Management Server. Also, you can change the already setup admin user account by setting a different user account.

If the functionality for omitting the management user account is enabled and if the functionality for integrating JP1 user authentication is enabled on the virtual server, you need not setup the management user account while executing this command and after starting Management Server.

For the functionality to omit the admin user account, see 4.1.15(3) Settings when the management user account is not set in the uCosminexus Application Server System Setup and Operation Guide.

To execute this command, you must have Administrator privileges (in Windows) or root permission (in UNIX). In UNIX, you can also specify the command execution permission for specific users who do not have the root permission. For details on the setup, see mngenvsetup (setup management group).

Arguments

When no arguments are specified, the command's usage is displayed.

start

Starts Management Server.

stop

Stops Management Server.

-sync

Enables the command processing and also the synchronous execution of start or stop processing for Management Server. In the following cases, a synchronous execution is executed, even if you omit this option. However, you cannot specify this option when you specify the -timeout option.

  • When stopping Management Server

  • When starting Management Server in Windows

When starting Management Server in UNIX, if you specify this option, a synchronous execution is performed as a background job and if you omit this option, a synchronous execution is executed as a foreground job.

-timeout synchronous-execution-timeout-time

Specify the waiting time (unit: seconds) from performing a synchronous execution of this command until Management Server starts or stops, with the integer 0 or from 61 through 2147483. This option is enabled when specified with the -sync option.

When you specify 0, the system continues to wait until Management Server starts or stops, without an occurrence of a timeout. When you omit this option, the synchronous execution timeout time is set as 120 (seconds).

-daemon

Starts Management Server as a daemon process. The same operations are executed as are executed when starting as a daemon process by using the daemon command. For details on the daemon command, see daemon (start daemon process).

setup

Sets up Management Server.

server-name

Specifies the name of Management Server (server name of the J2EE Server). If the server name is omitted, cosmi_m is assumed.

-u management-user-ID

Specifies the management user ID of Management Server.

-p management-user-password

Specifies the management user password of Management Server.

-np new-management-user-password

Specifies the management user password of the new Management Server.

-nu management-user-ID-after-change

Specifies the management user ID of the new Management Server.

When canceling the already specified management user password, you specify a null character ("").

Return values

0:

The command terminated normally.

1 or more:

An execution error is occurred. However if the return value is 2, it indicates that a syntax error might have occurred and if the return value is 3, the value indicates that a synchronous execution error might have occurred.

2:

A syntax error has occurred.

3:

A synchronous execution error has occurred.

Input example

Notes

Notes common to OS

  • The name of the real server for the logical J2EE server must be different from the Management Server name (server name of the J2EE server).

    If you use a same name, the following problems might occur:

    • Setup of the logical J2EE server fails if the Management Server name is set as the name of the real server for the logical J2EE server.

    • Setup of Management Server fails if you use a name that is already used as the name of the real server for a logical J2EE server.

  • When you want to access Management Server by using the management command or Smart Composer, in succession to the start of Administration Agent or Management Server, enable the synchronous execution.

Notes on setting up Management Server are as follows:

  • When you execute this command by enabling the management user account omission function, settings of the -u option, -p option, -np option, and -nu option of common arguments are disabled. In such case, a message is output and the setup process continues.

  • When you disable the management user account omission function and execute the command by specifying -nu option, when the management user ID is not specified, specification of the -u option is ignored and the management user ID specified by -nu option is set. Also, when you disable the management user account omission function and execute the command by specifying -np option, when the management user password is not set, specification of the -p option is ignored and the management user password specified by the -np option is set.

  • As Component Container sets up the J2EE server with the host name, during installation, do not set up the server name of Management Server with the host name.

  • When you want to change the server name during set up of Management Server, confirm that Management Server is stopped and then execute the mngsvrctl command.

Notes for UNIX

  • The processes operating on Management Server differ depending on the versions. The mngsvrctl and cjstartweb processes operate on versions prior to version 08-70, whereas the cjstartsv process operates on version 09-00 or later versions.

  • Before starting Management Server, setup umask 022.

    When this command is used to start Management Server, files that are affected by umask are created by the following owners and groups:

    • In AIX:

      root/system

    • In Linux

      root/root

    The following files are affected by umask:

    • Configuration information file saved on the Configuration Information Save/Restore window (user option)

    • J2EE application files (EAR files) or resource information files (mapps_logical-server-name_internal-id) created when J2EE applications or resources are imported

    • Registered J2EE application (application-display-name_registration-time)

    • Encryption/decryption key file that is created when an encryption key file is set by execution of the ssogenkey command or by repository management (user option)

    • Management Agent setup files (mngagent.logical-server-name.properties) created when the setup information is distributed to a J2EE server or batch server

    • Environment variable storage file that is set by the snapshot log function and created immediately before snapshot log collection (envinfo.txt)

    • Backup file (usrconf.cfg.bak) of the user definition file of a J2EE server or batch server created when the setup information is distributed to a J2EE server or batch server

    • Backup file (usrconf.properties.bak) of the user definition file of a J2EE server or batch server created when the setup information is distributed to a J2EE server or batch server

  • To start Management Server, first set the locale to C and then execute the command.

    An example of setting the locale to C in an environment that uses ksh is given below:

    • Setting example in AIX

      export LANG=Ja_JP or export LANG=ja_JP

    • Setting example in Linux

      export LANG=ja_JP.utf8

The precautions to be taken when you setup Management Server are as follows:

  • If you execute this command after enabling the functionality for omitting the admin user account, settings of the -u option, -p option, -np option, and -nu option of the common arguments are disabled. In such cases, a message will be output and the setup processing will be continued.

  • If you execute the command where the -nu option is specified when the management user ID is not setup after disabling the functionality for omitting the admin user account, the specification of the -u option is ignored and the management user ID specified in the -nu option is setup. Furthermore, if you execute the command where the -np option is specified when the management user password is not setup after disabling the functionality for omitting Management Server account, the specification of the -p option is ignored and the management user password specified in the -np option is setup.