The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

PPM 8.0 Clustered Environment High Level Steps

Highlighted
Jamie Pick
Regular Collector

PPM 8.0 Clustered Environment High Level Steps

To perform the PPM 8.0 upgrade on two clustered JVMs, we followed the upgrade guide but kept running into problems starting the JVMs. Could someone please share the high level steps to successfully upgrade from 7.5 to 8.0?

In other words, something like:
1. Perform upgrade on primary JVM
2. Perform upgrade on secondary JVM
3. Sync ports and server.conf
4. Run kUpdate and kRun

Or
1. Perform upgrade on primary JVM
2. Copy directory to secondary JVM
3. Run kUpdate and kRun

Thanks!

Jamei
4 REPLIES
Erik Cole
Honored Contributor

Re: PPM 8.0 Clustered Environment High Level Steps

We did it the second way.

1-Temporarily modify server.conf to be a non-clustered server.
2-Perform 8.0 upgrade.
3-Get it up and running okay.
3a-Install service pack, and repeat #3
4-Copy directory to create second JVM.
5-Install new 8.0 cluster-related parameters in server.conf.
6-kUpdateHtml.
7-Run as cluster.
Jamie Pick
Regular Collector

Re: PPM 8.0 Clustered Environment High Level Steps

Hey Erik -

Nice. We'll try this in our new environment where we'll be fine tuning the clustered install.

Thanks for the information.

Jamie
Jim Esler
Honored Contributor

Re: PPM 8.0 Clustered Environment High Level Steps

We did our upgrade from 6.0 to 7.5 using the basic process that Erik did, but we skipped steps 1 and 5. We upgraded the primary server and only started it until all of the upgrades were complete and the second server was cloned.
Jamie Pick
Regular Collector

Re: PPM 8.0 Clustered Environment High Level Steps

Quick follow-up question Erik...

We successfully got two JVMs upgraded using the high-level steps previously described. They both successfully started as stand-alone. To switch them to clustered, we made the necessary server.conf changes and ran kClusterDeploy.sh script. Did you do this as well, to switch your newly upgraded stand-alone instances to clustered?

Thanks,

Jamie
//Add this to "OnDomLoad" event