InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.3: Administering application servers (overview)

6.6.3: Administering application servers (overview)

An application server configuration provides information for starting and managing a server process to handle requests for enterprise applications and their components.

The WebSphere administrator configures one or more application servers with settings for:

  • Giving the server a unique name by which to manage it
  • Associating the server with a unique transport port
  • Specifying Java command line arguments and environment variables for starting the application server process
  • Enabling WebSphere security for the server
  • Associating the server with an operating system user ID and security group
  • Specifying how many times to try to start or ping the server before giving up
  • Specifying the process priority on the operating system
  • Defining standard in, standard error, standard out streams for the server runtime
  • Specifying a working directory
  • Conducting transactions
  • Specifying a workload management policy for distributing work among the server and its clones
  • Specifying tracing of the server and its child components

Each application server HTTP transport needs a unique port number and a host alias

Each application server in an administrative domain needs to have a unique port number for the HTTP transport of its Web container. Furthermore, the virtual host associated with the application server must have an aliases associated with the transport port. If there is a problem with these settings (such as two application servers with the same virtual host are trying to use the same HTTP transport port), the typical symptom is that the second application server will not start.

See virtual host administrative overview for further details and instructions.

Regenerating the WebSphere plug-in for the Web server

It is suggested you review the information about administering WebSphere plug-ins for Web servers, because you will need to regenerate the plug-in configuration each time you create a new application server.

See instructions for regenerating the plug-in using the Java-based administrative console.

Go to previous article: Configuring tracing on administrative nodes with the Java administrative console Go to next article: Application server properties

 

 
Go to previous article: Configuring tracing on administrative nodes with the Java administrative console Go to next article: Application server properties