Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3033
  • Last Modified:

WebSphere Jython script to list node status

I am trying to put together a jython script that will stop the nodes on the server, and then list the status of the server to verify it stopped.
Ideally, the script would attempt to stop, check the status, then IF they are stopped, continue, if they are not stopped, try and terminiate.

This is a small piece of a larger script which will do the following with all of the correct checks in place to ensure everything is being deployed correctly.
Stop nodes
Uninstall application
Save
Install application
Save
Wait for files to be built
Restart Node Agent
Ripple-Start the cluster
0
rwskas
Asked:
rwskas
  • 6
  • 4
  • 3
2 Solutions
 
HonorGodCommented:
There are a couple of different ways to stop an AppServer:

- AdminControl.stopServer( serverName, nodeName );  # A couple of variations exists

- Get the MBean of the specific server, then;

  AdminControl.invoke( mbean, 'stop' );

The former "waits" for the AppServer to stop, but the latter doesn't.

However, the former writes message to the display (i.e., stdout), but the latter doesn't.

Which do you prefer?
0
 
HonorGodCommented:
This book

Title: WebSphere Application Server Administration using Jython
 Pub: http://www.ibmpressbooks.com/bookstore/product.asp?isbn=0137009526

Includes some sample programs
- From the publisher website
  Click on the "Download" links
  Right click on the "Sample scripts" and "save as"

- Unzip the file, and locate "StopCell.py" in the Chapter 10

It uses technique #1 above.
If you want to see code for technique #2, let me know...
0
 
Radek BaranowskiFull-stack Java DeveloperCommented:
what do you mean exactly ? you  say you want to stop 'nodes' when in reality you should stop servers on nodes (as HonorGod wrote) then do the app change, sync nodes and then bring servers up. in my opinion you should not try to restart nodeagents, as then you may compromise environment consistency. anyway, when working on DMgr side, you install apps to master config repository, and you need then send the thing out to nodes via nodeagents with appropriate wsadmin commands like:

nodeID = AdminConfig.getid('/Cell:xfinwas1Cell01/Node:XCRYPTO1PRENode01/')
print "Synchronizing node: " + nodeID
Sync1 = AdminControl.completeObjectName('type=NodeSync,node=XCRYPTO1Node01,*')
AdminControl.invoke(Sync1, 'sync')
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
rwskasAuthor Commented:
Hmmm... I Suppose that would be why my script is not deploying correctly... I haven't had much time to test, but basically the files I would be expected to be built never show up.

So.. What is the CORRECT process to uninstall/reinstall an application?

@HonorGod
Thanks for the refrence! I have downloaded and will review the StopCell.py script in Chapter 9
0
 
Radek BaranowskiFull-stack Java DeveloperCommented:
in general - the process is simple and you do it as you try to (I suppose). the diference may come from environment you try to do it on.
on standalone server you install/uninstall (deploy) into servers config repository,and the server is the one you actually run application on.
in network deployment/cluster you install (deploy) application into master config repository on deployment manager, and through synchronization you deliver this runtime config change to the servers, that are actually running this application.
usually, dMgr is not used to run any business applications, just for management

as far as I know, all necessary files are either built during deployment, or - at latest - during server startup (in cluster)
0
 
HonorGodCommented:
To add to what baranello stated.

We have 3 different scenarios:

1. A simple/single stand-alone AppServer
    Use the AdminApp.install() method
    http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/rxml_adminapp.html#rxml_adminapp__cmd7

2. A Federated (unclustered) AppServer = 1 AppServer managed & administered by/with a deployment manager
    Use the AdminApp.install() method

3. A Cluster - 1 or more AppServers managed & administered by/with a deployment manager
    Use the AdminApp.install() method
    Synchronize:
    http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/txml_sync.html
0
 
rwskasAuthor Commented:
So we have a few different clusters, across 4 different physical servers. Each cluster however, has its own 'version' of the build, as each cluster performs different/specfic actions.

Rigth now, we manually (through the websphere gui console) uninstall / install the application on each of the 4 physical servers. Each cluster is a single node, some have only one application server, while some have 4.

At what point do I need to use the sync commands?
0
 
Radek BaranowskiFull-stack Java DeveloperCommented:
after using AdminApp.install() in wsadmin on DMgr.
0
 
rwskasAuthor Commented:
before or after the Admin...save() ?
0
 
HonorGodCommented:
The AdminConfig.save() will save the configuration information (i.e., the xml files).
That should be done first.
0
 
rwskasAuthor Commented:
Just to make sure I have this..
If I want to stop the application servers, and have the script WAIT for the server to actually stop, I would use
AdminControl.stopServer( serverName, nodeName )

Then I would uninstall the application
AdminApp.uninstall('myapp')

Then save
AdminConfig.save()

Then deploy the new app
AdminApp.install(....)

Then save
AdminConfig.save()

Then syncronize
AdminControl.invoke(Sync1, 'sync')

Does that sound correct to affectively reinstall an application?
0
 
HonorGodCommented:
The save after uninstall is not required unless you aren't going to install something.

Other than that, yes.
0
 
HonorGodCommented:
Thanks for the grade & points.

Good luck & have a great day.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 6
  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now