Hi Tiffanie,
There are basically two approaches if someone wants to upgrade from WMBv7, WMBv8, IIBv9 or IIBv10 software to ACEv11 software.
1. Parallel Migration:
The first approach is what we often talk about as "parallel migration". You can install ACEv11 on the same machine as earlier versions of the product. You would then typically take a branch of your source artifacts (message flows, models, BAR files etc.) in your version control system, then open your artifacts in the v11 Toolkit, and from there deploy them to your ACEv11 runtime. This approach lets you migrate gradually ... you can then structure your migration alongside testing that will give you confidence in the way the version of the software works.
2. "Big Bang" or "In-place" Migration:
In previous versions of IIB, we talk about "big bang" or "in place" migration as a process of quickly migrating EVERYTHING at once. We've offered the mqsimigratecomponents command for this purpose in previous versions. The purpose of this command is to amend the data files on disk which the product uses to store all its configuration for the artifacts which have been deployed to the runtime. The downside of this approach is that everything moves at once, and many would consider this harder to test and higher risk than doing things a step at a time. It also has the downside that this approach does not migrate your source artifacts, or leave you with an up to date BAR file built using the new version of the product. So, in general you're better advised to follow the approach of Parallel migration. Additionally, in ACEv11 we no longer have an mqsimigratecomponents command. The reason we don't have this command any more is that ACEv11 actually utilises the same formats on disk for artifacts in the builtime and the runtime. This makes things much simpler moving forward - in many cases you will be able to do "unzip and go" using the mqsibar command in the new product version. In place of the mqsimigratecomponents command, ACEv11 offers a new command instead named mqsiextractcomponents whose purpose is to allow you to extract the definitions of the runtime artifacts into suitable buildtime artifacts which are placed into the directory structure required by v11. This command will also help migrate configurable service definitions from earlier versions to policy files in v11. mqsiextractomponents is passed a zip file which is created from earlier releases by running the mqsibackupbroker command. Initially we structured the mqsiextractcomponents command to reject backups from versions prior to v10, but from ACEv11.0.0.3 the command has been amended to enable you to attempt to use it with earlier backups. The reason we relaxed this constraint was to help users who might be coming from previous releases which are already out of IBM support, but for which source code may have been lost. Whilst we have relaxed this constraint, the command has not been as thoroughly tested with versions prior to v10 so should problems be found with earlier backups, we reserve the right to not necessarily change the command to accept all forms of backup from these out of service versions. We don't expect this to impact many users but mention it here just in case, in order to set expectations correctly. Given that most folks would still have their source files, then most would be doing parallel migration in any case.
Cheers,
Ben
------------------------------
Ben Thompson
IBM UK
------------------------------
Original Message:
Sent: 01-22-2019 12:44 PM
From: Tiffanie Watkins
Subject: moving to ACE from older version
What would the process be for someone to move to ACE from an older version of the product? i.e WMB 7?
------------------------------
Tiffanie Watkins
------------------------------