WAS v8.5 > Secure applications > Authenticate users > Select an authentication mechanism > Configure LTPA and work with keys > Step 4. Manage keys from multiple cells.

Start an application server

When you start an application server, a new server process starts. This new server process is based on the process definition settings of the current server configuration.

Before beginning

Before you start an application server, verify that all of the application required resources are available. You must also start all prerequisite subsystems.

If you want server components to dynamically start as they are needed by the installed applications, verify the Start components as needed option is selected in the configuration settings for the application server before starting the application server. Selecting this option can improve startup time, and reduce the memory footprint of the application server. Starting components as they are needed is most effective if all of the applications deployed on the server are of the same type. For example, using this option works better if all of the applications are web applications that use servlets, and JSP. This option works less effectively if the applications use servlets, JSPs, and EJB.

To ensure compatibility with other WebSphere products, the default setting for this option is cleared. Before selecting this option, verify that any other WebSphere products, that you are running with this product, support this function. This procedure for starting a server also typically applies to restarting a server. The one exception might be if a server fails and you want the recovery functions to complete their processing before starting new work on that server. In this situation, you must restart the server in recovery mode.

If you create any additional application servers, we cannot start, stop, or manage these servers using the dmgr console associated with the original base server. You must either use command-line tools to perform these tasks for the additional servers, set up an dmgr console for each server, or configure an administrative agent to provide a single interface to all of your servers, including the original base server. An administrative agent makes it easier to more fully administer these unfederated application servers.

If you install a base server without a node agent, there are no dmgr console buttons for New, Delete, Templates, Start, Stop, Restart, ImmediateStop, Terminate, after you select Servers > Server Types > WASs on the dmgr console. In this environment, we can use an administrative agent and add the base server to the administrative agent. We can then control the base server through the administrative agent. See topic Administer stand-alone nodes using the administrative agent for more details.

If you create additional application servers, only use one server to modify and save configurations. There is no coordination of configuration setting between the different servers and if you modify and save configurations on multiple servers, your data might become corrupted.

When a child process starts, Java appends the runtime path to the LIBPATH environment variable to ensure that it is using the correct library paths. Because this implementation does not check to see if the runtime path already exists in the LIBPATH environment variable, existing entries might get duplicated. However, when the parent process is stopped, then started, all of the additional runtime paths that were added to the LIBPATH environment variable when child processes started are removed from the LIBPATH environment variable.

There are several options available for starting an application server.

• We can use the dmgr console to complete the following steps:

  1. Click Servers > Server Types > WebSphere application servers.

  2. Select server1 and click Start. We can view the status and any messages or logs to make sure the application server starts.

• We can use the Start menu on a Microsoft Windows operating system. For example, if you are using the Express version of the product, click Start > Programs > IBM WebSphere > Base V > n > Profiles > profile_nameStart the server. We can check the server has successfully started by checking the startServer.log file. If the server has successfully started, the last two lines of the startServer.log file reads:

  Server launched.  Waiting for initialization status.
  Server server1 open for e-business; process id is 1932.

  The startServer.log file is located in the profile_root\logs\server1 directory if we have installed your server with the default settings. The server name and process ID vary depending on your settings.

• If a Windows service has been created for the application server, optionally use the Windows Services utility to start, stop, and monitor the basic status of the server.
  1. To launch the Services utility, click Start > Settings Control Panel.

     The Control Panel folder displays.

  2. Double-click the Administrative Tools icon.

     The Administrative tools folder displays.

  3. Double-click the Services icon.

     Read about the Services utility in the Windows online help.

  Read the topic about the WASService command for information about adding and removing Windows services.

• We can issue a startServer command.

  Read the topic on the startServer command for information about the command, including such information as running the command and defining the file name for the start server log. Read the topic on using command-line tools for information such as determining from what directory to run the startServer command.

  We can check the server has successfully started by checking the start server log. If the server has started successfully, the last two lines of the start server log look like the following example:

  Server launched.  Waiting for initialization status.
  Server server1 open for e-business; process id is 1932.

Results

The specified server starts. To verify the server is in start state, in the dmgr console, click Servers > Server Types > WebSphere application servers.

What to do next

After the server starts, deploy the applications to run on this server.

If you must start an application server with standard Java debugging enabled:

1. In the dmgr console, click Servers > Server Types > WebSphere application servers.

2. Click the name of the application server with the processes to trace and debug.

3. Under Server Infrastructure, click Java and process management > Process definition.

4. Select Java virtual machine.

5. On the Java virtual machine page, select the Debug mode option to start the standard Java debugger. Set Debug mode arguments, if they are needed.

6. Click OK.

7. Save the changes to a configuration file
8. Stop the application server.
9. Start the application server again as previously described.

Subtopics

• Restart an application server in recovery mode
  When an application server instance with active transactions in progress restarts after a failure, the transaction service uses recovery logs to complete the recovery process. These logs, which each transactional resource maintains, are used to rerun any InDoubt transactions and return the overall system to a self-consistent state.

Related

Stop an application server
Manage application servers
Administer application servers
Use command-line tools

WASService command

Reference

serverStatus command
startServer command
stopServer command

+

Search Tips   |   Advanced Search