IIB to ACE

Some of the notes we’ve taken while working on a migration project from IIB to ACE. If you see anything has changed or provided incorrectly, feel free put those in the comments and we’d update this post with your comments.

  1. App Connect Enterprise v11 (first released 2018):
    1. Onpremise + Cloud
    1. IIB + App Connect Professional
    1. Local -> Toolkit ; Cloud -> Designer
  2. Integration Node is optional
  3. Integration Servers can run independently
  4. Configurable services are replaced with Policy files
  5. Local queue manager is required if Collector, Timer and Aggregate nodes are used.
  6. One Web UI can show any number of Integration Servers & Nodes
  7. Not all features available in v10 Web UI are available in ACE V11 but soon they will be available
  8. Flow and Resource Statistics are turned on by default
  9. Some mqsi commands are not available like mqsiformatlog, mqsireadlog, mqsimigratecomponents, mqsideleteconfigurableservice
  10. IIB End of Support is announced as Apr 2022
  11. ACE can run in on-premise and cloud
  12. Use TransformationAdvisor for the migration plan and impact
  13. App Connect Standard is effectively IIB standard with the addition of the Salesforce Request node whereas App Connect Enterprise is the official successor to IIB and includes the ACE V11 software, App Connect Professional V7.5.2 as well as the IBM App Connect on Cloud Service.
  14. A new administrative REST APIv2 for configuring App Connect Enterprise servers
  15. All Runtime node properties can be modified using server.conf.yml file
  16. IBM App Connect professional has 100+ connectors
  17. If there is any project created in older versions like WMB v6/v7 or anything as integration project, those would be deployed into a default Application project.
  18. Integration projects are no longer encouraged. Any attempt to subsequent redeploy independent resources will replace the entire content of the default application of an integration server with the new BAR file’s independent resources.
  19. New REST API testing utility in admin Web UI
  20. Migration
    1. Parallel Migration
      1. Install your ACEv11 environment,
      1. Configure the environment manually from scratch or reuse command scripts from IIBv10
      1. Take a branch in version control and then deploy your BAR files to the new environment
    1. Parallel Migration using extraction to help
      1. Install your ACEv11 environment
      1. Use mqsiextractcomponents to configure the v11 environment (this will help to create policies for you from config services for example) to help ensure you don’t forget configuration from your v10 system. Discard the run directory contents, because instead you are going to deploy items to the new system one by one as the next action
      1. Take a branch in version control and then deploy your BAR files to the new environment.
    1. Big Bang using extraction
      1. Install your ACEv11 environment
      1. Use mqsiextractcomponents to configure the v11 environment (this will help to create policies for you from config services for example) to help ensure you don’t forget configuration from your v10 system. Don’t discard the run directory contents
      1. Restart the integration node.
  21. There is no change in the project types. It is same as v10.
    1. Application (same as v10)
    1. Library (same as v10)
    1. Shared Library (same as v10)