Starting and stopping quick reference

Start and stop servers in your application serving environment, referring to this quick guide to the administrative clients and several other tools that are provided with this product.

Procedure

  • Use commands to start and stop servers.
    Table 1. Commands to start and stop servers . Run a start or stop command that is appropriate for the target server.
    Command
    Quick start Quick reference: Issuing commands to start and stop servers

    These examples are for starting and stopping the default profile on a server. Otherwise, you might need to specify -profileName profile_name when invoking the command.

    Deployment manager

    Run the following command.

    See startManager command for details and variations

    startManager
    [AIX Solaris HP-UX Linux Windows][IBM i]Node

    Run the following command.

    See startNode command for details and variations

    startNode
    Application server

    Run the following command. See startServer command for details and variations

    startServer server
    where server is the application server that you want to start.
    Stopping the servers

    Use the same command as to start, except substitute stop for start. For example, to stop an application server, issue the command:

    stopServer server

    To start and stop application server clusters, see Starting clusters.

  • Use administrative clients and tools.
    Table 2. Opening the administrative console . Point a Web browser at the console.
    Command
    Quick start Quick reference: Opening the administrative console
    To open the console using the default port, enter this web address in your web browser:
    http://your_fully_qualified_server_name:9060/ibm/console
    Depending on your configuration, your web address might differ. Other factors can affect your ability to access the console. See Starting and logging off the administrative console for details, as needed.

    See the administrator commands that are listed in the Reference section of the documentation.

  • Use troubleshooting tools.