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.
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)
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
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.
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?
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 .