Migrating Business Process Design Projects

You can reuse projects, processes, and endpoints from Integration Orchestrator 4.0.3 or Unwired Server 1.0. Before beginning this process, be sure you have successfully completed the Unwired Orchestrator 4.3 installation.

To migrate business process design projects:

  1. Export your project from the existing directory.

  2. Export the endpoints from Directory Services using Endpoint Manager.

  3. Import the endpoints into Directory Services using Endpoint Manager.

Notes:
After endpoints are imported into Unwired Orchestrator 4.3, they cannot be exported and used in a pre-4.3 installation of Integration Orchestrator.  
If your project references user-defined XSLT functions, see Migrating User-Defined XSLT Extension Functions.

  1. Create a new runtime instance.
    To learn how to migrate user-defined XSLT extension functions referenced by your project, click here.

  2. Regenerate the package for the project.

  3. Import the project as a resource into your workspace.

  4. Deliver the package.

  5. Review the properties and edit as necessary.

  6. Deploy the business process.

  7. Copy the existing state.db into the new runtime directory and overwrite the state.db that was included with the 4.3 installation.

Note: For a successful migration of state.db, you must have disk space of at least 1.5 times the size of your pre-4.3 state.db file.  

  1. From the command line in your 4.3 runtime directory, which you created in step 4 above, run psmigrate.
    Windows example: Sybase\IO-43_svr\instances\NewInstance\runtime>..\..\..\bin\psmigrate
    A verification message appears when the file migration is successful.

Note: The state.db file migrates within itself. You will not see a new file after psmigrate successfully completes.

Note: If the NNSYMessageLog.nml contains the following error, ignore this message. No further action is required.

[Sybase][ODBC Driver][Adaptive Server Anywhere]Table or view not found: Table 'NNE_VER' not found.

WARNING: Processing no longer supports the scenario of a single event distributed to multiple business processes in the same package. (This is sometimes called a multiple route or spray condition.)  If you are migrating from a pre-4.3 version of Integration Orchestrator and have existing business processes that use this scenario, call Technical Support for assistance.