In a distributed server environment, the administrative console is located in
the deployment manager server, dmgr. In this case, the administrative console
provides centralized administration of multiple nodes. Configuration changes are
made to the master repository and pushed to the local repositories on the nodes
by the deployment manager. In order for the administrative console to run, the
dmgr server must be running. In order for the changes to the master repository
to be pushed to the nodes, the node agents must also be running.
The file
synchronization service is the administrative
service responsible for keeping up to date the configuration and application data files that are distributed
across the cell. The
service runs in the deployment manager and node agents, and ensures that changes
made to the master repository will be propagated out to the nodes, as necessary.
The file transfer system application is used for the synchronization
process. File synchronization can be forced from an administration client, or
can be scheduled to happen automatically.
During the synchronization
operation, the node agent checks with the deployment manager to see if any files
that apply to the node have been updated in the master repository. New or
updated files are sent to the node, while any deleted files are also deleted
from the node.
Synchronization is one-way. The changes are sent from the
deployment manager to the node agent. No changes are sent from the node agent
back to the deployment manager
You can configure the File Synchronization
service from the WAS Admin COnsole like this
Friday, February 26, 2010
Node auto synchronization
Node auto synchronization
If your
working in distributed environment then every time you make any configuration
change such as deploying application, you will have to first save that change
and then synchronize node to synchronize that change to other node. If you want
you can turn this preference on in console the changes get synchronized to all
the nodes automatically
Application Server type
Application Server type
- A stand-alone application server is an application server created through the use of an application server profile and is not federated to a cell. This is the only option in the Base and Express environments. You can also create a stand-alone application server in the Network Deployment package. However, the expectation is that you will federate the application server to a cell for centralized management in the future.
- A managed application server is one that is managed from a deployment manager. This is only possible with the Network Deployment package. A managed server can either be an application server that was created using an application server profile and subsequently federated to the cell, or it can be created directly from the deployment manager’s administrative console
following options to stop an application server:
Stopping application server
From the
administrative console, you have the following options to stop an
application server:
application server:
- Stop: quiesces the application server and stops it.
- Immediate Stop: stops the server, but bypasses the normal server quiesce process that supports in-flight requests to complete before shutting down the entire server process. This shutdown mode is faster than the normal server stop processing, but some application clients can receive exceptions.
- Terminate deletes the application server
process. Use this if immediate stop
fails to stop the server.
Restarting servers in cluster
Restarting servers in cluster
You can
restart all the servers in a cluster through WAS Admin COnsole by selecting the
server and clicking on ripple start
or you can execute the following wasadmin command
AdminControl.invoke('WebSphere:name=<clustername>,process=dmgr,platform=common,node=dmgrCellManager01,version=6.1.0.25,type=Cluster,mbeanIdentifier=cluster1,cell=dmgrCell01,spec=1.0',
'rippleStart')Restarting all the servers on particular node
Restarting all the servers on particular node
You can
restart all the servers on particular node through WAS admin console by going to
System Administration
-< node agents. Selecting the node agent of your
choice and clicking on Restart all Servers on Nodes like this
you can achieve same functionality using this wsadmin script
AdminControl.invoke('WebSphere:name=NodeAgent,process=nodeagent,platform=common,node=<nodeagentname>,diagnosticProvider=true,version=6.1.0.25,type=NodeAgent,mbeanIdentifier=NodeAgent,cell=<cellname>,spec=1.0',
'restart', '[false true]', '[java.lang.Boolean java.lang.Boolean]')
PMT
Profile Management Tool(PMT)
Profile
Management tool is a GUI tool that you can use to create profile, You can launch
it in following ways
Irrespective of how you launch the PMT tool this is the second screen that you get and rest of flow depends on type of profile that you want to create
- By going to was_home/bin/ProfileManagement/pmt.bat command
- In case of windows environment by going to Start - programs - IBM WebSphere - Application Server Network deployment v6.1 - profile management
- As a part of installation program select the launch Profile Management tool on the last page
Irrespective of how you launch the PMT tool this is the second screen that you get and rest of flow depends on type of profile that you want to create
Subscribe to:
Posts (Atom)

