member start_service command

In Windows installations, the member start_service command installs and starts a Windows service for the specified member. It also starts the heartbeat process.

Usage notes

If you use the member start_service command to start a member on Windows, you cannot use the member start command to restart the member.

After you start AS4 Microservice by using the member start_service command, you can stop and restart the application by using the Windows services controller.

This command also starts the heartbeat process, which periodically checks whether members are still active. The heartbeat process starts when one or more members are started.

You can stop the heartbeat process with the following tools:

member stop command
member softstop command
Windows services controller, which automatically stops the rest of the members on the node

If your cluster has at least two catalog servers, and you stop all of your catalog servers, you must restart at least two catalog servers before the data grid is available. If you stop all of your catalog servers except one, the data grid is still available.

Environment

Windows 2008

Authorization

You must use the Run as administrator option to run this command.

Syntax

execute member start_service <member type> [--reinstall_service] [--login_user <username>] [--startup_type <automatic|manual>]

Option descriptions

member type

One or all of the four member types:

catalog
container
operational
informational
all

--reinstall_service

Forces the service to be installed. If the service is already installed, the service is deleted and then reinstalled.

--login_user <username>

Runs the service as a specific user. If the login_user option is used and the service is installed, you are prompted for the user's password. If the login_user option is not used, the default user is LocalSystem. If the login_user option is used, make sure that the user has the permission to log on as a service.

--startup_type <automatic|manual>

Indicates whether the service is started automatically or manually. If the manual parameter is used, the service starts only when it is requested to start. If the startup_type option is not used, the default parameter is manual.

Examples

Example: Starting all member types as Windows services after an installation.

This command starts all member types as Windows services after an installation in the C:\AS4 Microservices directory:

execute member start_service all
Adding Service: Catalog17443
        Server Name: catalog
        B2BAC Home: C:\AS4 Microservices\Members\bin\cmd_lib\..\..\
        Start Args: member start
        Restart: 1
IBM AS4 Microservices - Catalog17443 service successfully added.
Starting Service: Catalog17443
Successfully started service.

Adding Service: Container18443
        Server Name: container
        B2BAC Home: C:\AS4 Microservices\Members\bin\cmd_lib\..\..\
        Start Args: member start
        Restart: 1
IBM AS4 Microservices - Container18443 service successfully added.
Starting Service: Container18443
Successfully started service.

Adding Service: Operational9443
        Server Name: operational
        B2BAC Home: C:\AS4 Microservices\Members\bin\cmd_lib\..\..\
        Start Args: member start
        Restart: 1
IBM AS4 Microservices - Operational9443 service successfully added.
Starting Service: Operational9443
Successfully started service.

Adding Service: Informational19443
        Server Name: informational
        B2BAC Home: C:\AS4 Microservices\Members\bin\cmd_lib\..\..\
        Start Args: member start
        Restart: 1
IBM AS4 Microservices - Informational19443 service successfully added.
Starting Service: Informational19443
Successfully started service.