After you manually create a middleware server representation
of a WebSphere® Application
Server Community Edition server in the
administrative console, you must update a few configuration settings
so that they are defined specifically for your WebSphere Application
Server Community Edition installation. If
the middleware discovery function is enabled, you do not need to perform
these steps.
Before you begin
Before you perform this task, consider the other options
for configuring your
WebSphere Application
Server Community Edition servers:
- If you do not have an existing WebSphere Application
Server Community Edition configuration, consider
using complete life-cycle servers. By configuring complete life-cycle
servers, you can deploy managed applications and create expression-based
dynamic clusters that are made of WebSphere Application
Server Community Edition servers. For more information,
read about creating complete life-cycle WebSphere Application
Server Community Edition servers and dynamic
clusters.
- If you enable middleware discovery, representations of your existing WebSphere Application
Server Community Edition servers and applications
are automatically created. These representations are assisted life-cycle
servers and unmanaged applications. You do not need to perform any
of the additional steps in this task if middleware discovery is enabled.
To enable middleware discovery for WebSphere Application
Server Community Edition servers, click .
If the Discovery interval value is set to -1,
discovery is disabled. Change this value to indicate the interval
at which you want middleware discovery to run.
If middleware discovery is disabled, you must perform
the manual steps in this task to create a representation of your WebSphere Application
Server Community Edition in the Intelligent Management cell. As a prerequisite,
federate the node that is running the WebSphere Application
Server Community Edition server and create a
representation of the server in the administrative console.
About this task
Perform this task only if you have an existing WebSphere Application
Server Community Edition environment and you
do not want to enable middleware discovery to automatically create
a representation of your environment.
Procedure
- Update the WebSphere variables
so that they match the settings on the node that is running the WebSphere Application
Server Community Edition server. In
the administrative console, click .
Edit
the
WASCE_HOME variable, which specifies the home
directory of your
WebSphere Application
Server Community Edition installation.
Default values are set at the cell scope level:
C:\Program Files\IBM\WebSphere\AppServerCommunityEdition
/opt/IBM/WebSphere/AppServerCommunityEdition
If the home directory is different on different nodes in your
configuration, select the node scope and create the
WASCE_HOME variable
for the specific node.
- Update server operations for the WebSphere Application
Server Community Edition server to include the
user name and password.
- In the administrative console, click .
- Edit the start and stop server operations to include
the user name and password that is required to run these commands.
Results
You created a representation of your
WebSphere Application
Server Community Edition server in the administrative
console. To view all of your
WebSphere Application
Server Community Edition servers,
click .
The list of servers
that displays on this administrative console page includes all of
your complete life-cycle, assisted life-cycle, and discovered WebSphere Application
Server Community Edition servers. If you have WebSphere Application
Server Community Edition dynamic clusters defined,
the cluster members are also listed on this administrative console
page.
What to do next
- To use this configuration when you are configuring your other WebSphere Application
Server Community Edition servers, create a server
template of your current WebSphere Application
Server Community Edition server.
- To view the log files for your WebSphere Application
Server Community Edition server in the administrative
console, use the external log viewing service. This service is enabled
by default. The following directories are configured by default:
- ${WASCE_HOME}/var/logs
- ${WASCE_HOME}/catalina/logs
- ${AGENT.HOME}/logs/${WAS_SERVER_NAME}
- To edit configuration files for your WebSphere Application
Server Community Edition server, use the external
configuration service. The ${WASCE_HOME}/var/config/config.xml file
is included by default.
- After you create representations of all the WebSphere Application
Server Community Edition servers, you can add
the representations to a dynamic cluster. To cluster these servers,
each server must be running the same applications and be running the
same version of WebSphere Application
Server Community Edition.