Migrating from V7.x.x.x to V7.5.4.0

This topic provides information about migrating a physical appliance or virtual appliance to IBM App Connect Professional V7.5.4 from earlier V7.x.x.x releases.

Migrating a physical appliance to a virtual appliance

A physical appliance supports only V7.0.0.x, V7.5.0.1, and V7.5.1.0.

Steps for migrating:

  1. Save your Projects and User Settings from the appliance using Repository > Import/Export in the Web Management Console (WMC).
  2. In the old appliance, for the emgmt interface, configure a certificate that has SHA256withRSA (or stronger) signature algorithm.
  3. Install a fresh instance of IBM App Connect Professional V7.5.4 on the appliance and then restore with one of the following options:
    • If you don't have SHA256withRSA signature algorithm certificate configured for emgmt, restore with "Projects Only"
    • (Otherwise) Restore with "Projects and User Settings".
  4. If you restored with "Projects Only", configure Network settings and User settings manually
  5. Upload the vendor libraries (required by your projects) to the WMC.

Migrating a virtual appliance

Steps for migrating:

  • Virtual appliance V7.0.0.x, V7.5.0.x, V7.5.1.x, V7.5.2.x up to IFIX-015, V7.5.3.x up to IFIX-004:
    1. Save your Projects and User Settings from the appliance using Repository > Import/Export in the Web Management Console (WMC).
    2. In the old appliance, for the emgmt interface, configure a certificate that has SHA256withRSA (or stronger) signature algorithm.
    3. Install a fresh instance of IBM App Connect Professional V7.5.4 on the appliance and then restore with one of the following options:
      • If you don't have SHA256withRSA signature algorithm certificate configured for emgmt, restore with "Projects Only"
      • (Otherwise) Restore with "Projects and User Settings".
    4. If you restored with "Projects Only", configure Network settings and User settings manually
    5. Upload the vendor libraries (required by your projects) to the WMC.
  • Virtual appliance V7.5.2.0 IFIx-017 and higher, V7.5.3.0 IFIX-005 and higher:
    1. Save your Projects and User Settings from the appliance using Repository > Import/Export in the Web Management Console (WMC).
    2. Install a fresh instance of IBM App Connect Professional V7.5.4 on the appliance and then restore with "Projects and User Settings".
    3. Upload the vendor libraries (required by your projects) to the WMC.
Note: Have a copy or backup of all third-party vendor libraries, which are uploaded with earlier versions or get them from respective vendor sites.
For connector-specific latest changes, see the technote at https://www.ibm.com/support/docview.wss?uid=ibm10959985.
For further assistance, contact IBM Support.

Migrating a secure connector

Backward compatibility of older secure connectors from v7520, v7530, etc with v7540 versions [cloud or appliance] is not supported. You need to migrate old version secure connectors either by upgrading or by installing a new version v7540 secure connector, as outlined below:

  • Upgrading:

    To upgrade an old version secure connector, complete the following steps:

    1. Create a new secure connector in the cloud or appliance web management console, under the "Secure connectors" section.
    2. Upgrade the old version secure connector in a local machine by using the v7540 secure connector installable file, selecting the upgrade option and correctly selecting the existing secure connector path.
    3. Download the secure connector configuration file from the secure connector created in step 1, and update the configuration file (for ports and so on) of the upgraded secure connector of step 2 by using the configuration wizard, which you can invoke by the command line as described in Updating Secure Connector Configuration.
    4. Start the secure connector, and wait for the secure connector status to change to 'RUNNING' in the web management console.
    5. Deploy the secure connector projects in the web management console.
  • Fresh install:

    Install a fresh version of the secure connector in a new path. Also, make sure that the required third-party JAR files and certificates are added to successfully run secure connector projects.