You can create WebSphere® Application
Server Community Edition complete
life-cycle management servers and expression-based dynamic clusters.
You can deploy managed applications to those servers and dynamic clusters.
Before you begin
- Determine the version of WebSphere Application
Server Community Edition that
you want to run:
- For complete life-cycle management, use WebSphere Application
Server Community Edition Version 2 or later.
- Additional steps are required to enable Java Management Extensions (JMX) security in WebSphere Application
Server Community Edition Version 2.1. For more
information, read about configuring JMX security for WebSphere Application Server Community
Edition Version 2.1 servers.
- If you are using WebSphere Application
Server Community Edition Version
1 (all releases), you can only use assisted life-cycle management.
For information about configuring assisted life-cycle servers, read
about configuring assisted lifecycle WebSphere Application Server Community
Edition.
.
- Install the WebSphere Application
Server Community Edition runtime
environment to the nodes on which you want to run servers. You can
either use the installation wizard that is included in WebSphere Application
Server Community Edition, or you can configure
the centralized installation manager to install the runtime environment.
- Federate your nodes into the cell. Read the topics on the addNode command
and adding, managing, and removing nodes for more information.
Procedure
- Configure the middleware descriptors so that you can run
discovery to find the WebSphere Application
Server Community Edition runtime
environment. If you use the centralized installation manager
to install WebSphere Application
Server Community Edition, you
can skip this step. In the administrative console, click . The discovery service uses middleware descriptors
to define where to look for the runtime environment. Verify that the
middleware descriptors contain the correct installation locations
for your environment. The default values:
- C:\Program Files\IBM\WebSphere\AppServerCommunityEdition
- /opt/IBM/WebSphere/AppServerCommunityEdition
- Run discovery to find the WebSphere Application
Server Community Edition runtimes on the nodes
that you want to host servers. If you use the centralized
installation manager to install WebSphere Application
Server Community Edition, you can skip this step.
Discovery runs automatically when the node agent starts. Discovery
also runs at a predefined time interval that you can specify in the
middleware descriptor. However, you can also invoke discovery with
the following steps:
- In the administrative console, click .
- Select the nodes that you want to run through discovery,
and select the Run discovery operational action.
- Click Run.
- Verify that the discovery service found the runtime
environment. In the administrative console, click .
If any runtime environments exist, then properties that begin with WASCE strings
are displayed.
Only the default installation location is listed in the wasceRuntime middleware
descriptor. You can modify the middleware descriptor so that the discovery
looks for the correct installation location.
- Create WebSphere Application
Server Community Edition deployment
targets. The deployment target is where you deploy the WebSphere Application
Server Community Edition application. You can
create individual WebSphere Application
Server Community Edition servers
or dynamic clusters.
- Create a WebSphere Application
Server Community Edition server.
- In the administrative console, click . Choose Create
a new server instance, and select the WebSphere
Application Server Community Edition server type. You
can also click .
- Select the node on which you want the WebSphere Application
Server Community Edition server to run. This
node must have the WebSphere Application
Server Community Edition runtime.
- Choose the WebSphere Application
Server Community Edition server
template.
- Confirm and save the WebSphere Application
Server Community Edition server.
- Create a WebSphere Application
Server Community Edition dynamic
cluster.
- In the administrative console, click .
- Choose the WebSphere Application
Server Community Edition server
dynamic cluster type, and name the dynamic cluster.
- To create a dynamic cluster with complete life-cycle management,
choose Automatically define cluster members with rules.
Define a membership policy to identify which nodes host the WebSphere Application
Server Community Edition servers in the dynamic
cluster. These nodes must have the WebSphere Application
Server Community Edition runtime environment
installed. The default membership policy follows:
node_property$IS_WASCE_DISCOVERED = 'TRUE'
This
membership policy looks for WebSphere Application
Server Community Edition Version
2.0 and later runtimes. If you want to specify a specific version,
you might use the following membership policy:
node_property$WASCE_2.0.0 IS NOT NULL
This
policy defines membership as all nodes that run
WebSphere Application
Server Community Edition Version 2.0.0. The group
of nodes that you define must have the exact same version of
WebSphere Application
Server Community Edition installed. For example,
you cannot combine Version 1 and 2 servers in the same dynamic cluster.
- Select the server template for the WebSphere Application
Server Community Edition runtime environment
that you are using.
- Specify other dynamic cluster properties.
- Save your WebSphere Application
Server Community Edition dynamic
cluster.
Results
The new server displays in the list on the administrative console page. If you see an error status
icon (

), the creation process did not complete. This error can occur
because of problems in the
WebSphere Application
Server Community Edition server
runtime environment. Delete the server and try creating the server
again.
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
- Deploy applications to your WebSphere Application
Server Community Edition servers and dynamic
clusters. For more information, read about deploying WebSphere Application Server Community
Edition applications.
- Stop discovery from examining the installation location that you
used to create your managed servers.
- If you used discovery to find the WebSphere Application
Server Community Edition runtime environment,
you can disable discovery globally or you can remove the specific
installation location from the middleware descriptor.
- If you installed the WebSphere Application
Server Community Edition runtime
environment with the centralized installation manager, discovery was
not needed to register the configuration. Do not include centralized
installation manager paths in the discovery paths in the middleware
descriptor. If you used the default centralized installation manager
installation location, you must globally disable discovery or change
the default discovery location to a different path.
For more information, read about configuring middleware descriptors.
Do not use the WebSphere Application
Server Community Edition console
to edit your complete lifecycle servers, except for functions that
are not available with Intelligent Management .
Using the WebSphere Application
Server Community Edition console
can cause unexpected results. For example, if you edit the server
port numbers in the WebSphere Application
Server Community Edition console,
the port value that is configured for Intelligent Management is overridden with
the new value.