Resolving problems when migrating or importing other resources

Use the advice given here to help you to resolve common problems that can arise when you import or migrate resources other than message flows.

About this task

You see an error message when you recompile a BAR file from a previous version

Procedure

  • Scenario: You have imported a BAR file with your resources from a previous version, and you then choose to refactor those resources to applications and libraries. You try to recompile a BAR file after the resources have been migrated to applications and libraries, but you see an error message similar to the following example: 
    TotalPurchaseOrderFlow.msgflow belongs in an application or library and should be deployed within that container and not independently.
Create a new BAR file and select the application or library in the Prepare tab of the BAR editor, then select Build and Save.
To deploy the resource separately from the application or library, it must be moved into a Message Broker project.
  • Explanation: If you have reorganized your imported resources into applications and libraries, you cannot rebuild the original BAR file. If a message flow from your original BAR file has been moved into an application in IBM® Integration Bus, you must deploy the flow with the new container, or move it to an integration project, from which you can deploy it separately.
  • Solution: Create a new BAR file and add the application or library that contains the resources that you want to deploy. To deploy a resource like a message flow on its own, move the flow to an integration project, then deploy the flow separately.

The mqsimigratecomponents command fails with database error BIP2322

About this task

Procedure

  • Scenario: The mqsimigratecomponents command fails with database error BIP2322: The 'CREATE TABLE' command is not allowed within a multi-statement transaction in the 'INODE1' database.
  • Explanation: If you are using the mqsimigratecomponents command to migrate an integration node that uses a Sybase database, you must modify the database to enable the Data Definition Language (DDL) that the command uses.
  • Solution: Take the following steps:
    1. Log on to ISQL using a system administrator account.
    2. Run the following series of commands: 
      1> use master
2> go
1> sp_dboption "INODE1","ddl in tran",TRUE
2> go
Database option 'ddl in tran' turned ON for database 'INODE1'.
Run the CHECKPOINT command in the database that was changed.
(return status = 0)
1> use INODE1
2> go
1> checkpoint
2> go
      where INODE1 is the name of the Sybase broker database.

The File > Import menu provides only the option to import a compressed file inside an existing project

Procedure

  • Scenario: You have a compressed file that contains message set projects and message flow projects. When you click File > Import, you have only the option to import the compressed file inside an existing project, but you want to re-create the message set projects and message flow projects.
  • Solution: When you export and import files, do not export or import the root directory, which is created for you because of the project file. When you export your message flow and message set projects:
    1. Click Create only selected directories.
    2. Clear the project root folder.
    3. Select the files and subdirectories as required.
      The project root folder is selected, but is displayed as gray.
    Then, when you import the compressed file:
    1. Clear the root (/) folder.
    2. Select the files and subfolders as required.
      The project root folder is selected, but is displayed as gray.