Hunter T Tweed commented on Oct 10, 2011

Re: Step-by-Step Cluster Guide for IBM WebSphere Portal v7.0.0

It will recycle the DMGR only. JMX would probably work as well but I don't know how to do that offhand.

There's no harm in running 'action-cluster-recycle-dmgr-cell'.

Sandromar Ferreira commented on Oct 10, 2011

Re: Step-by-Step Cluster Guide for IBM WebSphere Portal v7.0.0

That's correct. I'm scripting the cluster process.

I've tried using:

$ ./ConfigEngine.sh action-cluster-recycle-dmgr -DPrimaryNode=true

Although, when I opened a PMR asking about that was the right approach to it, I was told that I should use JMX instead.

Then, it comes couple questions: Is it good to run ?

'./ConfigEngine.sh action-cluster-recycle-dmgr -DPrimaryNode=true' ?

Also, by running that ConfigEngine command, will it recycle every node on the cluster, or just the primary node ?

Hunter T Tweed commented on Oct 10, 2011

Re: Step-by-Step Cluster Guide for IBM WebSphere Portal v7.0.0

Sure, you can do that. The DMGR restart isn't necessary, other than just for the purpose of cleanly restarting everything having completed the full cluster setup. If you do not restart it, there will not be any functional problems that arise directly related to it.

I imagine though you're trying to script the cluster process? If so, there is a ConfigEngine command that can be used to recycle the DMGR:

./ConfigEngine.sh action-cluster-recycle-dmgr

The only catch though is that it will only work if "PrimaryNode=true" in wkplc.properties. Therefore, if you want to run it from a secondary/additional node, you'd have to do this:

./ConfigEngine.sh action-cluster-recycle-dmgr -DPrimaryNode=true

Add the -DPrimaryNode=true flag to the command sets the property to 'true' for that execution only, and would allow you to successfully run that command on any additional node.

But again, not exactly required for any technical reason at that point but if you wanted to it here or for any other future purpose, that's one way to do it.

Sandromar Ferreira commented on Oct 7, 2011

Re: Step-by-Step Cluster Guide for IBM WebSphere Portal v7.0.0

On step 18, page 50, it says:

"Restart the DMGR, both nodeagents, and both WebSphere_Portal servers."

Is it really necessary restart DMGR ?

Can I just restart all the nodes by using the following wsadmin commands?

AdminServerManagement.stopAllServers("node_name_to_restart")

AdminServerManagement.startAllServers("node_name_to_restart")

Hunter T Tweed commented on Sep 14, 2011

Re: Step-by-Step Cluster Guide for IBM WebSphere Portal v7.0.0

The order is incorrect, thanks for catching this. While ISALite can really be installed anywhere, the recommended location for it is within the profile directory. After installing Portal in binary mode, no profile exists so it does not make sense to install ISALite at this point. I'll make the change and republish today. The correct spot for installing ISALite is after federation and creating the cluster, as you noted.

Andrew A Klein commented on Sep 13, 2011

Re: Step-by-Step Cluster Guide for IBM WebSphere Portal v7.0.0

Can you confirm the order of installing the IBM Support Assistant Lite (on the second node) before federation and clustering the additional node - it seems to me that this is reversed given the destination for the support assistant's install directory. Thanks.

Hunter T Tweed commented on Jun 28, 2011

Re: Step-by-Step Cluster Guide for IBM WebSphere Portal v7.0.0

Nice catch! The temporary tablespace ICMLSUSRTSPACE4 was added a little over a month ago (v6 of the file) but I had not set the bufferpool zies to 16000. That has been updated now and republished.

Francesco M De Collibus commented on Jun 22, 2011

Re: Step-by-Step Cluster Guide for IBM WebSphere Portal v7.0.0

Sorry, I think there are a couple of error in the Appendix with db2 scripts.

We lack

CREATE USER TEMPORARY TABLESPACE ICMLSUSRTSPACE4 PAGESIZE 4 K MANAGED BY SYSTEM USING ('icmlsusrtspace4') BUFFERPOOL ICMLSVOLATILEBP4

and both bufferpools are suggested to be of twice the size in the official doc.

CREATE BUFFERPOOL ICMLSVOLATILEBP4 SIZE 16000 PAGESIZE 4 K

CREATE BUFFERPOOL ICMLSMAINBP32 SIZE 16000 PAGESIZE 32 K

The user tablespace, if not created, generates error. Would be better to correct the PDF since many specialists are using it.