Hi All,
We have to upgrade the below WAS products in WAS CLUSTER , please suggest the overview of the steps for the same  or any websites.

BPM Version:  from 7.5.1.0 to 7.5.1.2

WAS ND: from 7.0.0.15 to 7.0.0.31 

XML Feature pack : 1.0.0.10 to 1.0.0.15

Hi Hari,

  I suggest the next page to update your environment, you have all the steps

  Required fixes for the IBM Business Monitor, WebSphere Enterprise Service Bus (WESB), and IBM Business Process Manager (BPM) V7.5.1 Fix Pack 2 products
  www-01.ibm.com/support/docview.wss?uid=s...

  Hope this helps. Tell us if you need more support

Regards

Dear Gabriel,

Thank you for the info. 

I have gone through the link.

In our environment, we have two node horizontal cluster where in primary node we have dmgr/nodeagent/appserver and in the secondary node we have appserver alone.

Our plan is to upgrade in a temporary servers,which are the  clone of the two PROD servers.

Take clone of the two nodes and assign the same hostnames.

Please let me know  if these are the steps are to be followed and correct me , if i am wrong:
=============================================
1.Install IBM Installation Manager

2.Upgrading  DMGR:(in Primary Node)

       1.Backup all profiles using backupConfig
       2.Back up all of the databases that are associated with this environment.              3.Stop all of the Java processes.
       4.Install V7.5.1 Fix Pack 2 (V7.5.1.2) onto the deployment manager using                IIM/silent mode
------------------------------------------------------------
3.Upgrading managed nodes

         1. Upgrade in cluster Node-2
--------------------------------------------------------------------------

4.Upgrading Clusters:

           1.Stop the deployment manager

          2.bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName profile_name -                      Dupgrade=true -Dcluster=cluster_name

           3.generate upgrade SQL scripts for the Process Server database:
             /bin/BPMGenerateUpgradeSchemaScripts.sh -upgrade                      

           4.update the Process Server database for each cluster where the Business               Process Definition engine is configured.
               To update Process server DB:
              /BPM/Lombardi/tools/upgrade/upgrade_7x/upgrade_7x.sh              -profileName -nodeName -                           serverName

==============================================

Have a question to ask , In step-2 (Upgrading DMGR), if we upgrade dmgr in primary node, its managed nodeagent/appserver also gets updated ?

Please advice, thanks in advance.












 

Hi Hari,

  I'm not BPM technical but so points to take in mind about your approach.

[quote author=208933467 post=544260075]

Our plan is to upgrade in a temporary servers,which are the  clone of the two PROD servers.

Take clone of the two nodes and assign the same hostnames.

 [/quote]

From websphere point of view some if you clone nodes with a hostname for this nodes works you need to change the IPs and point to local host and not to a DNS because can be an IP conflict with the original nodes. I don't know if from BPM point of view you need to do something else.

[quote author=208933467 post=544260075]
Have a question to ask , In step-2 (Upgrading DMGR), if we upgrade dmgr in primary node, its managed nodeagent/appserver also gets updated ?
 [/quote]

  Steps for upgrading a network deployment environment
  Notes and restrictions when you upgrade in a network deployment environment:
  www-01.ibm.com/support/docview.wss?uid=s...
 
  If your configuration contains managed nodes that are hosted by the same installation as their deployment manager profile, the managed node configuration is updated as part of the deployment manager profile update. 


  Hope this helps

Regards,

Dear Gabriel,

Thank you for the information.

We have assigned new IP's to the cloned servers and ensure that the production environment is not affected.

We have upgraded  BPM in WAS ND , dmgr node. as root user using IBM Instalation Manager.

We tried to start teh dmgr after upgrade.

We received below error:
JVMJ9VM019E Fatal error: Unable to find and initialize required class java/lang/NoClassDefFoundError

Actually application is running as other user (bpmadm).

Is the above error is because , we have upgraded as root user instead of bpmadm.

Please advice.

Hari,

  When you have clone the environment after changing the IPs and before applying fixpack have you tested that all "CLONED" environment is working fine?
 
  Yes you need to take in mind the files ownership and groups. If the owner is bpmadm and you apply fixpack as root the owner of the changed files files will be root. So you need to "chown"....look at you production environment the ownership and groups of WAS_HOME and BPM_HOME and change in clone environment
 
  Please put complet error or SystemOut.log?
 
  Thanks in advanced.
 
regards

Dear Gabriel,

After cloning the server, we have tested, application was working fine.

I am applying the fix pack using IBM INstallation manager.

My questions are :

1. IBM Installation manager should be installed as root/ application user? (I have installed as root ) .

2.Fix pack upgrade to be done as root/application user ?

As per your previous reply ,do i need to apply fixpack as root and change the ownerhip to application user? 

Sorry, i dont have a copy of the full error.

Actually SystemOut.log hasnt updated when i tried to start the dmgr, after the fix pack upgrade.



 

Hari,

  Your both questions have the same answer, it depends on your installation
 
  Installation Manager overview
  www-01.ibm.com/support/knowledgecenter/S...
 
  Anyway, please confirm in your production environment
 
  "look at you production environment the ownership and groups of WAS_HOME and BPM_HOME"
 
  Directory conventions
  www-01.ibm.com/support/knowledgecenter/S...
 
  Attach  your startServer.log from DMGR or try starting DMGR with -trace option
 
  starManager.sh/bat -trace
 
  Without log or more information about your exception I can help more
 
regards

Dear Gabriel,

The ownership of the Application is application user bpmadm as below:

[root@kjbpmw02]>ls -ld /app/IBM/Lombardi/WebSphere/AppServer
drwx------ 43 bpmadm appadm 4096 Apr 13 12:16 /app/IBM/Lombardi/WebSphere/AppServer

 So ,  If i m not wrong , i need to install IBM Installation Manager(IIM) with bpmadm user and then the launch the IIM with the same bpmadm user to do FIX pack upgrade.


Thank you for your assistance.

 

No, you only need to change the owner and group of /app/IBM/Lombardi/WebSphere/AppServer

In any case, have you StartServer.log? and the fixpack install log?

Regards

Dear Gabriel,

So, i need to install as root and manually change the ownership of the application directories as per the PRODUCTION.

Actually i dont have the start/stop logs now, as we have restored the server again due to the error last time.

We are going for an upgrade again now, we will udpate you the status once done.

Thank you for your advice.
 

You have several ways to do as you can see in this link.

[quote author=91692909 post=544308381] 
  Installation Manager overview
  www-01.ibm.com/support/knowledgecenter/S...

Before you install Installation Manager on your target machines, you must consider what mode you will use to deploy packages. The mode that you choose determines how you install the software. There are three modes: administrator, non-administrator, and group. The primary difference between these modes is which users can launch Installation Manager.

• Administrator mode: Installation Manager can only be installed once per machine. This mode is required for packages that require administrator or root privileges to be deployed. Also, the user who launches Installation Manager must be a member of the “Administrators” group on Windows or have root privileges on UNIX, Linux, IBM i, IBM z/OS®, and OS X operating systems.

• Non-administrator mode: Installation Manager can be installed once per user. This mode is useful when users have their own copy of an application. Those copies are managed separately by the respective user accounts. However, in this mode, packages that require administrator access cannot be installed.

• Group mode: Use this mode when you use multiple user accounts to manage the installed applications. In group mode, a group of users share packages. This mode is only available on Linux, UNIX, IBM z/OS, and OS X platforms. It is not available on Windows or IBM i. Packages must be enabled for group mode. Check the documentation for your package to determine whether the package is enabled for group mode.

 [/quote]

I proposing to change the owner and group if you continue having the issue, but if you have restore the servers then the first step is to plan your Installation manager (root, non-root, group) and then apply fixpack.

Hope this helps.

Regards

Dear Gabriel,

Thank you for your assistance, we have completed the upgradation successfully. 

great!!! glad to help

Regards