This topic describes how to change the cell protocol information,
define custom properties for the cell, and add additional nodes.
Before you begin
Before you can configure cells, you must install the WebSphere Application
Server Network Deployment product.
About this task
When you create a deployment manager profile, a cell is created.
A cell provides a way to group one or more nodes of your Network Deployment
product. You define the nodes that make up a cell, according to the specific
criteria that make sense in your organizational environment. You probably
do not need to configure the cell again.
Administrative configuration
data is stored in XML files. A cell retains master configuration files for
each server in every node in the cell. Each node and server also have their
own local configuration files. Changes to a local node or to a server configuration
file are temporary, if the server belongs to the cell. While in effect, local
changes override cell configurations. Changes to the master server and master
node configuration files made at the cell level replace any temporary changes
made at the node when the cell configuration documents are synchronized to
the nodes. Synchronization occurs at designated events, such as when a server
starts.
To view information about and to manage a cell, use the settings page for a cell.
Procedure
- Access the settings
page for a cell. Click System Administration > Cell from the
navigation tree of the administrative console.
- If the protocol that the cell uses to retrieve information from
a network is not appropriate for your system, select the appropriate protocol.
By default, a cell uses Transmission Control Protocol (TCP). If you want
the cell to use User Datagram Protocol, select UDP from the list for Cell
Discovery Protocol on the settings page for the cell. It is unlikely
that you need to change the cell protocol configuration from TCP.
- Click Custom Properties and define any name-value pairs
that your deployment manager needs.
- Click New.
- Specify a name and value for the custom property.
The
IBM_CLUSTER_RIPPLESTART_NOTIFICATION_TIMEOUT custom property:
Specify
a value, in milliseconds, to indicate the amount of time the ripplestart function
waits for processes to shut down before restarting them. If you attempt a
ripplestart and the processes have not shutdown before the start operation
begins, one or more of the processes will not restart.
Property |
IBM_CLUSTER_RIPPLESTART_NOTIFICATION_TIMEOUT |
Data type |
integer |
Default |
300000 milliseconds (5 minutes) |
The com.ibm.websphere.management.launcher.options
custom property:
Specify a value of displayServerInFront to
display the name of the cell, node, and server in front of the output for
the ps -ef command. Use of this property is intended to help you identify
the process ID of a server. The property has no impact on the server process.
Property |
com.ibm.websphere.management.launcher.options |
Data type |
String |
Default |
None |
- When you install the WebSphere Application Server Network Deployment
product, a node may have been added to the cell. You can add additional nodes
on the Node page. Click Nodes
to access the Node page, which you use to manage nodes.
Both
Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6)
are now supported by WebSphere Application Server, but there are restrictions
that apply to using both IPv4 and IPv6 in the same cell. Note that when you
add a node to a cell, the format in which you specify the host name is based
on the version of IP the node will be using. For details, see IP version considerations for cells.
WebSphere
Application Server on other platforms has support for Internet Protocol Version
4 (IPv4) and Internet Protocol Version 6 (IPv6). However, the i5/OS platform
supports IPv4 only. When you add a node to a cell, the format in which you
specify the host name is based on the version of IP that the node is using.
For details, see IP version considerations for cells.
Results
Depending on which steps you performed, you changed the cell protocol
information, defined custom properties for the cell, and added additional
nodes.
What to do next
You can continue to administer your Network Deployment product by
doing such tasks as managing nodes, node agents, and node groups.