Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

PPM v8.04 Cluster question

SOLVED
Go to solution
Highlighted
TurboMan
Member

PPM v8.04 Cluster question

Hi,

 

I am trying to split the services and the web access.

As one machine two nodes.

 

First of all, I changed from standalone to Cluster configuration and updated the server.config in accordance with the PPM manuel in  Services Isolation section and in Configuring a Server Cluster section.

My first question:

How do I find out if I managed to set the things up corretly?

And, 

When I run a kStatus.sh I get the first KintanaServer connected as ok, but not the second one as follows.

Checking rmi://DC2VMPPMWEB01:1099/KintanaServer
--> running (load: 0.0, mode: NORMAL)

Checking rmi://DC2VMPPMWEB01:2099/KintanaServer
--> Server is not running! (Could not connect to rmi://DC2VMPPMWEB01:2099/KintanaServer)

 

Did I do something wrong?

 

Any help is appreciated.

 

Regards

TM

8 REPLIES
Utkarsh_Mishra
Honored Contributor

Re: PPM v8.04 Cluster question

This mean that second node is not configured properly and is not running. The complete details of issue can be found at <PPM_Home>/server/<PPM_Server_Name>/log

 

For your assistance you can check this thread...

 

http://h30499.www3.hp.com/t5/ITRC-Project-and-Portfolio/how-to-add-one-JVMs/td-p/5341041

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
TurboMan
Member

Re: PPM v8.04 Cluster question

Thanks Utkarsh,

I've applied the configuration parameters but it didn't help.
I could not find any info in logs.
My server.conf for Clustering parameters are as follows.

######################################################################
# COMMON TO MACHINE FOR CLUSTER
######################################################################
com.kintana.core.server.MULTICAST_CLUSTER_NAME=PPMDEV
com.kintana.core.server.MULTICAST_IP=225.39.39.244
com.kintana.core.server.MULTICAST_PORT=9000
com.kintana.core.server.APP_SERVER_MULTICAST_PORT=9101
com.kintana.core.server.MULTICAST_NAME=APP_SERVER
######################################################################
# FOR EACH NODE
######################################################################
#com.kintana.core.server.APP_SERVER_JMX_RMI_PORTAPP_SERVER_UIL2_BINDING_PORT=8094
com.kintana.core.server.SERVER_NAME=DC2VMPPMWEB01
com.kintana.core.server.KINTANA_SERVER_NAME=DEV
com.kintana.core.server.HTTP_PORT=8082
com.kintana.core.server.EXTERNAL_WEB_PORT=8010
com.kintana.core.server.RMI_URL=rmi://DC2VMPPMWEB01:1099/KintanaServer
com.kintana.core.server.SERVICES_ENABLED=FALSE
#
###########################################
# Cluster Node specific ports - Using Set A
###########################################
com.kintana.core.server.APP_SERVER_NAMING_SERVICE_RMI_PORT=1198
com.kintana.core.server.APP_SERVER_NAMING_SERVICE_BINDING_PORT=1199
com.kintana.core.server.APP_SERVER_WEBSERVICE_PORT=8083
com.kintana.core.server.APP_SERVER_JRMP_INVOKER_RMI_PORT=4444
com.kintana.core.server.APP_SERVER_POOLED_INVOKER_BINDING_PORT=4445
com.kintana.core.server.APP_SERVER_HAJNDI_RMI_PORT=1101
com.kintana.core.server.APP_SERVER_HAJNDI_BINDING_PORT=1100
com.kintana.core.server.APP_SERVER_POOLEDHA_BINDING_PORT=4446
com.kintana.core.server.APP_SERVER_JMX_RMI_PORT=19001
com.kintana.core.server.APP_SERVER_UIL2_BINDING_PORT=8093
##########################################
@node
com.kintana.core.server.SERVER_NAME=DC2VMPPMWEB01
com.kintana.core.server.KINTANA_SERVER_NAME=NodeB
com.kintana.core.server.HTTP_PORT=9082
com.kintana.core.server.RMI_URL=rmi://DC2VMPPMWEB01:2099/KintanaServer
com.kintana.core.server.EXTERNAL_WEB_PORT=9010
###########################################
# Cluster Node specific ports - Using Set B
###########################################
com.kintana.core.server.APP_SERVER_NAMING_SERVICE_RMI_PORT=1298
com.kintana.core.server.APP_SERVER_NAMING_SERVICE_BINDING_PORT=1299
com.kintana.core.server.APP_SERVER_WEBSERVICE_PORT=8183
com.kintana.core.server.APP_SERVER_JRMP_INVOKER_RMI_PORT=4544
com.kintana.core.server.APP_SERVER_POOLED_INVOKER_BINDING_PORT=4545
com.kintana.core.server.APP_SERVER_HAJNDI_RMI_PORT=1201
com.kintana.core.server.APP_SERVER_HAJNDI_BINDING_PORT=1200
com.kintana.core.server.APP_SERVER_POOLEDHA_BINDING_PORT=4546
com.kintana.core.server.APP_SERVER_JMX_RMI_PORT=19101
com.kintana.core.server.APP_SERVER_UIL2_BINDING_PORT=8193
#com.kintana.core.server.APP_SERVER_JMX_RMI_PORTAPP_SERVER_UIL2_BINDING_PORT=8194

 

Any help is appreciated.
Regards

Utkarsh_Mishra
Honored Contributor

Re: PPM v8.04 Cluster question

Your configuration seem correct...

 

Did you get any error while statring the Server... and there some thing captured in log files...

 

 

Also try to change the RMI port for NODE B and check...

Pluse comment this in NODE B

"com.kintana.core.server.SERVER_NAME=DC2VMPPMWEB01"

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
TurboMan
Member

Re: PPM v8.04 Cluster question

Thanks,

 

Commented out "com.kintana.core.server.SERVER_NAME=DC2VMPPMWEB01" in NodeB.

Still the same,

 

You mean Changing port in com.kintana.core.server.RMI_URL in NodeB?

 

Regards

TM

Jim Esler
Honored Contributor

Re: PPM v8.04 Cluster question

Be sure to run kUpdateHtml.sh after every change to server.conf.

 

Are any errors reported or logged when you start the second node?

TurboMan
Member

Re: PPM v8.04 Cluster question

Thanks Jim,

 

I run updaetHtm all the time I am aware of that.

When I start the second node? I just run kStart, I don't know if there is another way of starting the second node?

I did not see any error in the log file,

I atteched a detail log file.

 

Thanks again

Jim Esler
Honored Contributor
Solution

Re: PPM v8.04 Cluster question

When you run kStart.sh, are you specifying the name of the node with the -name parameter? The default node name is the primary node if you do not specify another name.

TurboMan
Member

Re: PPM v8.04 Cluster question

Thanks very much Jim,

 

I didn't know that I have to explicitly start all other nodes,

I was expecting kStart.sh to start all nodes on behalf of me.

This was my mistake.

Now, I can see two java.exe in the process list and see other node is nunning as well.

 

$ ./kStatus.sh
Checking rmi://DC2VMPPMWEB01:1099/KintanaServer
--> running (load: 0.0, mode: NORMAL)

Checking rmi://DC2VMPPMWEB01:2099/KintanaServer
--> running (load: 0.0, mode: NORMAL)

 

Regards

TM

//Add this to "OnDomLoad" event