Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Not under consideration
Workspace App Connect
Created by Guest
Created on Mar 19, 2022

Migration of Integration node from ACE11 to ACE12

Hi Team, Currently our Integratoin nodes are running with ACE 11.0.0.16 and there is a plan to migrate these nodes to ACE 12 version. As per the instructions and guidlines from IBM portal it seems we need to add --delete-existing-node parameter when we are doing inplace migration. It seems when we need to roll back the version in case of any issues we face in migration , in this scenario when we run mqsirestorebroker there could be possibilities of corrupting the config or binary files? In this scenario it would be very difficult to go for migration for PROD. We just want to check and if it is possile to do in-place migration and create a command to implement this migration.
Idea priority Medium
  • Admin
    Ben Thompson
    Mar 23, 2022

    RFE Review. Thank you for taking the time to submit this idea for enhancement. Due to ACEv11 introducing the new option of running independent integration servers (which should be used when running ACE as part of a container based architecture), we decided to rebrand our migration command so that it could be used to assist all migration situations - including those which involved in-place migration of an integration node, and also those involving a period of parallel execution of an old and a new integration node, and also those involving splitting apart a set of node-owned integration servers as separate independent integration servers. The mqsiextractcomponents command is helpful for all these scenarios. If you are intending on running the integration node on the same machine before and after the migration, and have the integration node take the same name both before and after the migration (ie what is often referred to as "in place" migration) then you can use the mqsiextractcomponents command to achieve this with the "--delete-existing-node" option. This option deletes an existing node before creating the new node by writing the extracted configuration and resources. This option is required if "--target-integration-node" names an integration node that already exists. In this situation, if you were to want to revert back and "undo" the migration for any reason, then you should do so using the back-up file which you will generate using the mqsibackupbroker command prior to executing the mqsiextractcomponents command. You can restore from this backup. Examples of the commands to execute are as follows:


    IIBv10: mqsistop YourExistingIntegrationNodeName

    IIBv10: mqsibackupbroker YourExistingIntegrationNodeName -d C:\temp

    ACEv12: mqsiextractcomponents --backup-file "C:\temp\YourExistingIntegrationNodeName_220323_150916.zip" --source-integration-node YourExistingIntegrationNodeName --target-integration-node YourExistingIntegrationNodeName_043390866 --delete-existing-node

    ACEv12: mqsistart YourExistingIntegrationNodeName


    To delete the migrated node and revert back the migration ...


    ACEv12: mqsistop YourExistingIntegrationNodeName

    IIBv10: mqsirestorebroker YourExistingIntegrationNodeName -d "C:\temp" -a YourExistingIntegrationNodeName_220323_150916.zip

    IIBv10: mqsistart YourExistingIntegrationNodeName


    This is exactly the same capability as previously offered through mqsimigratecomponents.