WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

Scripting Stop/Start of WAS. Can we use IBM's Java methods v.s. Jython?

  • 1.  Scripting Stop/Start of WAS. Can we use IBM's Java methods v.s. Jython?

    Posted Wed October 22, 2014 09:04 AM
    Hello,

    I am updating WAS ND 7.0.0.27 to WAS ND 7.0.0.33 and wanted to know if it's possible to use IBM's built-in Java methods to Stop all servers before applying the FixPack, and then start all servers after applying the FixPack.

    I found that when you are calling, for example [profile_root]/bin/stopServer.sh or [profile_root]/bin/serverStatus.sh it's calling classes from .jar such as WsServerStop, etc.

    Is there a way I can use the functionality without having to connect to the dmgr SOAP port to run the AdminConfig or AdminTasks commands to stop all servers?

    Currently with ./stopServer.sh, I have to input the server name to the script. With my script i'd like to query all the servers running and stop them automatically. Using Java and it's classes seemed like a good way, but maybe someone can shed light.

    Currently, the problem we have with connecting to the dmgr, is that when i throw my script to the server where the dmgr is installed, when its stopped by the script, I am unable to connect to the dmgr from another server which is a node of that cell. My goal is to be able to throw my script on any WAS ND server and it will update WAS without caring if the dmgr is running on another node or not.

    Thanks for any info you can provide.

    Joey


Related Content