Hi All,

Has any one done 7.1.2/7.1.3 to wM9 upgrade or started with it? Is Over Install upgrade feasible in this upgrade?

The Guide mentions only side-by-side for 7.1.x but can we do 7.1.x → 8.2 → 9?
What are the challenges with this approach?

Thanks and Regards,
Ninad Patil

Hi Ninad,
Over Install upgrade from 7.1.3 to 9.0 is not possible directly. Only Side by Side migration is supported for this path. If you really want to use only over Install upgrade, as you mentioned you can perform it in two step process. First upgrade to 8.2.2 using Over Install and then upgrade to 90 from 8.2.2 using over Install.

Regarding the challenges, as we need to follow two step process in case of Over Install, so definitely the effort will be double as compared to 7.1.3 to 9.0 SBS approach.

Note: If your source is in 7.1.2 (Not 7.1.3), then you can not directly upgrade it to 9.0. There is no direct Upgrade path available from 7.1.2 to 9.0. You have to do a 2 phase migration which is 7.1.2 → 7.1.3 Overinstall and then from 7.1.3 → 9.0 side-by-side.

Hope this helps.

Regards
Rinku

Hi Ninad,

What ever Rinku Hazarika has given is valid information

Adding to it, to know the challenges and procedure of upgrade.login into empower and download upgrade document

Thanks a lot Rinku/Sai,

The first thing we did was to download the upgrade document and give it a read. But I want to know first hand experiences of users during upgrade.

Regards,
Ninad Patil

Since it’s side by side, you don’t face major issue

Major steps

1)Steps like first identify depericated services and create list of services that need rectification

2)Backup your current version

3)Setup new database.Move existing DB assests and run migration scripts, See document to comment few lines of migration scripts based on version

4)Install IS,MWS, …

5)Add latest fix.

6)Normalize timestamp

7)Move all packages,Move ACLs & Schedulers and other required IS assests

Hi Sai,
I am not quite sure, what do you mean by the following lines of step 3. I have the following questions. Can you please confirm?

"Setup new database.Move existing DB assests and run migration scripts, See document to comment few lines of migration scripts based on version "

Q1. Why do we need to setup a new DB?
Q2. If you are setting up a new DB, how do you move the existing DB assets to the new DB?
Q3. If you are setting up a new DB and some how moving the existing Db assets to new DB , what is the use of running the DB migration on a DB which is already in the latest version?
Q4. As per my knowledge, uses just need to use the target version Database component Configurator and migrate the existing DB to the target DB. The scripts are designed as specific to each path and user hardly needs to comment any lines of scripts (Apart from a special case of TN, where user needs to comment few lines if some specific DB fix is already applied to the source 7.1.3 DB)

Regards
Rinku

Hi Rinku,

Q1. Why do we need to setup a new DB?

New DB not required.if you had backup of existing DB, Because TN,IS, MWS,… scripts vary alot between older version to newer versions, you know webMethods have alot of dependency on transactional database esp in case of TN

So make it easier without losing existing partner information & other TN Assests, We run migration scripts on existing database

Q2.If you are setting up a new DB, how do you move the existing DB assets to the new DB?

As told in above answer new DB is not required, but we suggest clients to do because many clients using database for long time and upgrade is good time for them to update/change.

Q3. If you are setting up a new DB and some how moving the existing Db assets to new DB , what is the use of running the DB migration on a DB which is already in the latest version?

This is answered in Q1 & Q2

Q4. As per my knowledge, uses just need to use the target version Database component Configurator and migrate the existing DB to the target DB. The scripts are designed as specific to each path and user hardly needs to comment any lines of scripts (Apart from a special case of TN, where user needs to comment few lines if some specific DB fix is already applied to the source 7.1.3 DB)

I don’t understand question here migrating existing DB to Target DB. DCC is not desgined to migrate existing DB to Target DB, Running migration scripts mean existing DB will get inserted/altered with new tables as required by 9.0

To add one more point

Unlike before, Deployer 9.0 has the feasibility of deploying assets from previous version to 9.0. This is supported officially now.

From Documentation: You can import builds from projects created with Deployer version 8.2 or earlier to Deployer 9.0 for deployment . For example, you could import a build from a version 8.0 project into Deployer 9.0.

-Senthil

On Sai’s point

1)Steps like first identify depericated services and create list of services that need rectification

I was assuming that migrate utility will automatically update the deprecated services from older versions. Can you confirm this step has to be done manually?

Migration utility won’t remove/replace depericated services, we have do it maually.

HI All,

We are Planning to Migrate from wM7.1.3 to wM9 version.

Can any one suggest what is the best approach.
1.Side -by -Side Installation
2. Over-installation .

If you suggest option 1: Side -by -Side Installation what are the various advantages that we can achieve then going with Option2 Over Installation

If you suggest option 2: Over-installation what are the various advantages that we can achieve then going with Option1 Side -by -Side Installation

And also need to know the common advantages and disadvantages of both the approach.

Basically need to know the major difference between the two approach.

Any known issues while upgrading from 7.1.3 to 9

Many thanks in advance !!

Hello Everyone,

Good day…!! Hope you’re doing good…!!

Can anyone please suggest me, what are pre-requisites and post-requisites for upgrade.

Regards
Sasi KSV

Hi Sasi ,

The best way to get all in-detail information about pre-upgrade things and post-upgrade things is SAG document for Upgrading_SoftwareAG_Product . Make sure you should use the document of version to which you are upgrading assests\components .

Please let me know if any specific information you required .

Thanks
Shrikant

Hi Sasi,

I agree with Shrikant.

Additionally you should take a look at the “Supported Upgrade Pathes” documentation to see if overinstall upgrade might be possible.

But in most cases this won´t be possible.

Regards,
Holger