Ordering the start of Websphere AS

Hello experts,

Anyone know how to define the order of the Websphere server starting up ?
We need to start a server in priority and do not know how to do that.

I saw nothing on IBM site

Thanks in advance for your response !
Who is Participating?
HonorGodConnect With a Mentor Software EngineerCommented:
Ah!  Much better.

The stopping or recycling of a nodeagent shouldn't cause the managed server to be started, so I presume that are talking about a situation where all of the managed servers are stopped, and then the nodeagent is started, or recycled.

From the Admin console:

- Expand "Servers" (left frame)
- Expand "Server Types"
- Select "WebSphere application servers"
- Select a server name link (e.g., "server1")
- Under "Server Infrastructure" expand "Java and Process Management"
- Select "Monitoring policy"
- uncheck "Automatic restart "
- make "Node restart state" STOPPED
- click "Apply"
- click "OK"

Then, you can either use startServer.sh command scripts to start the servers in any desired order, or you can use a wsadmin script to start the servers in whatever order you want.
HonorGodSoftware EngineerCommented:
I'm sorry, you are going to be more specific about what it is you are trying to do.

Also, it would be best if you identified the specific version(s) of WebSphere being used
- What is displayed in the "Installed Product" section of the output generated by the
   versionInfo command script under WebSphere\AppServer\bin?

And what Operating System are you using?
chuchyyyAuthor Commented:
Linux x86_64  2.6.18-164.15.1.el5

When I restart the nodeagent, the servers starts one after the others in an order. I presume it follows the order of server creation.
Is there any weight to configure to custom the order of start ?
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

chuchyyyAuthor Commented:
Yes, i'm aware of Monitoring Policy.

without having to do a wsadmin script (it could be good also yes), when all servers are set to RUNNING, is there any weight, any configuration file that describe the order ?
HonorGodSoftware EngineerCommented:
no.  there isn't.

The only monitoring policy properties / attributes are:

           autoRestart : true
maximumStartupAttempts : 3
      nodeRestartState : STOPPED
          pingInterval : 60
           pingTimeout : 300

Open in new window

chuchyyyAuthor Commented:
OK. I found the solution then. STOPPED + wsadmin script.

Thanks HonorGod ;)
HonorGodSoftware EngineerCommented:
There is a "Parallel start" option for a servers "General properties", but that doesn't help with this issue.
HonorGodSoftware EngineerCommented:
Super.  Glad to be able to help.
HonorGodSoftware EngineerCommented:
Thanks for the grade & points.

Good luck & have a great day
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.