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 Sep 15, 2021

IIB to ACE migration: Independent resource issue

Hi


*We are aware that independent resources will ALWAYS be deployed under an application in ACE. Our team mentions that was the case with IIB7 to IIB9 migration as well and IBM provided a workaround/APAR for it.*


Currently we are planning the migration of IIB100022 to ACE110012. The migration plan we are using is “Migrating an IIB 9/10 node with multiple integration servers to ACE 11 independent integration servers by using mqsiextractcomponents”.


Currently all our flows are deployed as independent resources (both message flows & message sets). When we try to load the broker backup using miqsextract components its loading in the ACE12 Node under default application named “{EG_Name}_DefaultApplication”.


Even new deployment of independent resources are deployed under the same default application. A name for the default application automatically decided and created (if not exists) for the deployment of independent resources. We have 3500 plus flows in production and this application approach is neither a viable nor feasible solution for us.

This application/in issue is going to be a huge problem. Currently we have 3500 plus flows in production and this application approach is neither a viable nor feasible solution for us. This requires a complete design change followed by complete end to end testing.


We need to check with the product team regarding it. I am positive we cant be the only team facing this issue which would practically result in a design change.

The question is:


Is there a must for message flows to be inside an application? If so we are looking for a workaround solution for this.


References:

Migrating an IIB 9/10 node with multiple integration servers to ACE 11 independent integration servers by using mqsiextractcomponents


https://www.ibm.com/docs/en/app-connect/11.0.0?topic=migration-example-scenarios

Idea priority Urgent
  • Guest
    Reply
    |
    Sep 2, 2022

    Facing same situation, could you please share what was the outcome or solution ?

  • Admin
    Ben Thompson
    Reply
    |
    Oct 1, 2021

    Idea / RFE Review. Thank you for taking the time to raise this enhancement request but unfortunately on this occasion we do not intend to take this idea forward. Applications and libraries as groupings for artifacts deployed to the product runtime have been a core part of our architectural strategy since they were first introduced ten years ago as part of WMBv8. Since that time, we have tried to encourage the use and adoption of applications by all users who have previously used independent resources defined in integration projects. As noted, in ACEv11 and ACEv12 you can still deploy older BAR files that contain independent resources, but these are deliberately placed into the default application - whose name you can control through the server.conf.yaml file. We believe there are many advantages for the adoption of applications and libraries. Some of these are outlined in this topic from the IIBv10 documentation: https://www.ibm.com/docs/en/integration-bus/10.0?topic=overview-benefits-using-applications-libraries

    As discussed in the direct communication we had, we will continue to work with you to help you move forward with your gradual adoption of applications. Status of this idea is closed.