Profiles on WebSphere Application Server
|
||
Job manager
|
Network Deployment
|
Provides management capabilities for multiple
stand-alone application servers, administrative agents, and deployment managers |
Cell
|
Network Deployment
|
Provides two profiles: a
deployment manager and a
federated application server profile |
Secure proxy
|
Network Deployment
|
Provides a secure proxy configuration-only profile
only for use with a DMZ secure proxy server |
Administrative agent
|
Network Deployment
|
Provides management capabilities
for multiple
stand-alone application servers |
Custom (managed)
|
Network Deployment
|
Creates and federates a node that contains no
predefined application server definitions |
Deployment manager
|
Network Deployment
|
Provides management
capabilities for multiple
federated nodes |
Application server
|
All
|
Runs your applications;
functions
independently from other application servers |
Common command-line tools:-
• In directories:
– <was_root>\bin
– <profile_root>\<profile_name>\bin
Command
|
Function
|
removeNode
|
Remove a node from a cell
|
cleanupNode
|
Cleans up a node configuration from the cell repository
|
startManager
|
Start the deployment
manager
|
stopManager
|
Stop the deployment manager
|
startNode
|
Start the node agent
|
stopNode
|
Stop the node agent
|
syncNode
|
Synchronize a node with
the cell configuration
|
addNode
|
Add a node to a cell
|
• addNode
The addNode command incorporates (integrate) an application server
installation into a cell.
Depending on the size and location of the new node you
incorporate into the cell, this
command can take a few minutes to complete.
• syncNode
The syncNode command
forces a configuration synchronization to occur between the
node and the deployment
manager for the cell in which the node is configured.
• removeNode
The removeNode command returns a node from a Network
Deployment distributed administration cell to a stand-alone application server
installation. The removeNode command removes the node-specific configuration
from the cell. This command does not uninstall any applications that are
installed as the result of running an addNode command.
When a node is removed from a cell, the profile
reverts to the configuration it had
before it is federated into a cell. Any applications
or configuration changes that were made
while it was part of a cell are lost.
Restores stand-alone configuration of the node from
a backup.
The node can be removed through the deployment manager administrative
console.
Expand System administration. Click Nodes. Select the node to remove
and click
Remove Node.
A node can be
cleaned up through the deployment manager administrative console.
Expand System administration. Click Nodes. Select the node to clean up and click
Force Delete.
• cleanupNode
The cleanupNode command
cleans up a node configuration from the cell repository.
Use this command to
clean up a node if you have a node that is defined in the cell
configuration, but the
node no longer exists.
• startNode
The startNode command reads the configuration file for
the node agent process and
constructs a launch command.
• stopNode
The stopNode command
reads the configuration file for the Network Deployment node
agent process and sends
a Java Management Extensions (JMX) command that tells
the node agent to shut
down.
By default, the stopNode command waits for the node agent to complete shutdown
before it returns control to the command line.
• startManager
The startManager starts the deployment manager.
• stopManager
The stopManager stops
the deployment manager.
It sends a Java Management Extensions (JMX)
command to the manager to shut down.
By default, the stopManager command
waits for the manager to complete the shutdown process before it returns
control to the command line.
· Managed nodes
- Node agent or administrative agent is used to manage
its servers.
- Application server process runs within the
deployment manager cell.
· Unmanaged nodes
- Node agent and
administrative agent does not manage its servers.
- A stand-alone
application server is an unmanaged node.
-
Commonly used for web servers.
• Synchronize
Synchronize requests that a node synchronization
operation performs by using the
normal synchronization optimization algorithm.
This
operation is fast, but might not fix problems from manual file edits that occur on the
node.
It is still possible for the node and cell configuration to be
out of synchronization after this operation is performed.
• Full Resynchronize
Full Resynchronize
clears all synchronization optimization settings and completes
configuration
synchronization anew, so there is no mismatch between node and cell
configuration after
this operation is performed. This operation can take longer than the
Synchronize operation.
• syncNode command
The syncNode command forces a configuration
synchronization to occur between the
node and the deployment manager for the cell in which
the node is configured.
The node agent server runs a configuration
synchronization service that keeps the node
configuration that is synchronized with the master
cell configuration.
If the node agent is unable to run because of a problem in the node
configuration, you can use the syncNode command to complete a synchronization.
When
the node agent is not running in order to force the node configuration back
in sync with the cell configuration.
If the node agent is running and you want to run the
syncNode command, you must first
stop the node agent.
Was terminology : https://drive.google.com/open?id=1w-ws79l-hgPg2YCB1XMW4_AqkeNsBBUt
