InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.2: Administering nodes (overview)

6.6.2: Administering nodes (overview)

Administrative server node configurations provide information about machines (physical hosts) involved in the IBM WebSphere Application Server environment.

For each administrative server node, the administrator specifies properties such as:

  • Administrative name, host name, and host system type

  • WebSphere Application Server product installation root

  • Process ID of the administrative server on the node

  • Where to store deployed bean JAR files on the node

  • Where to find files that support, but are not included in, bean JAR files on the node (specify in the dependent classpath)

WebSphere Application Server supports one administrative server per physical machine. Therefore, it does not matter whether the administrator considers the physical machine or the administrative server to be the "node."

(The current exception is for the AS/400 operating system, on which the product supports multiple administrative servers on each physical machine).

A node can be in the "running" state, which indicates not only that the physical machine and operating system are running, but that the WebSphere administrative server on the machine is also running.

The administrative server must be running in order for the node to be active and operational in the administrative domain.

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 regenerating (updating) the plug-in is a task associated with the administrative node.

Go to previous article: Editing the contents of enterprise applications Go to next article: Administering nodes with the Java administrative console

 

 
Go to previous article: Editing the contents of enterprise applications Go to next article: Administering nodes with the Java administrative console