QIK Integration Pack Migration

If you created an Integration Pack using the Opalis QIK Wizard, you will need to convert it to be compatible with Orchestrator before it can be imported and used by Orchestrator.

Prior to converting an IP, the following steps must be completed:

  • If the activities in your IP were created using the QIK CLI Wizard and you have not already converted them to be compatible with Orchestrator, you must follow the steps outlined in QIK CLI Activity Migration before continuing. If you do not have a separate copy of the assembly containing the activities, you will need to install the IP to an Opalis 6.3 server first and then locate the assembly in the following directory: “C:\Program Files (x86)\Common Files\Opalis Software\Opalis Integration Server\Extensions\Support\Quick Integration Kit 3”.
  • If the activities in your IP were custom-developed using C# or Java using the Opalis and you have not already converted them to be compatible with Orchestrator, you must follow the steps outlined in Migrating QIK API Custom Activities before continuing. 
  • If your IP contains dependent or other included files, those file must be available to repackage into the new IP. If you do not have a separate copy of these files, you will need to install the IP to an Opalis 6.3 server first and then locate the files in the following directory: “C:\Program Files (x86)\Common Files\Opalis Software\Opalis Integration Server\Extensions\Support\Bin”.
  • If your IP contains a custom resource file used for activity and category icons, that file must be available for the new IP. If you do not have a separate copy of this file, you will need to install the IP to an Opalis 6.3 server first and then locate the file in the following directory: “C:\Program Files (x86)\Common Files\Opalis Software\Opalis Integration Server\Extensions”.
  • If your IP used the standard icons provided by QIK for the category or activity icons and you wish to continue using those icons instead of using the new icons provided in Orchestrator, you will need to obtain the Opalis.QIK.Wizard.Images.dll file and use it as you would a custom resource file. If you do not have a separate copy of this file, you will need to install the IP to an Opalis 6.3 server first and then locate the file in the following directory: “C:\Program Files (x86)\Common Files\Opalis Software\Opalis Integration Server\Extensions”.
  • Note: For the easiest conversion process, you should place all of these files in the locations they were in when the IP was originally packaged before starting the IP Wizard. The IP Wizard references these files by their original paths. Selecting a new path is possible for all files, but selecting a new path for assemblies containing the activities will result in some of the details of the activity to be reset, requiring you to re-enter the information. By using the original paths for the files, the existing information is simply re-used without having to re-enter it.

To convert an Opalis-compatible Integration Pack:

  1. Start the Integration Pack Wizard
  2. Click Import Integration Pack.
  3. Select the existing OIP file and click Open.
  4. You will see a warning message indicating the IP is not compatible with Orchestrator. Click OK.
  5. Modify the product details as necessary to reflect any changes. Note that the version number of the IP is automatically incremented and the “Upgrade” checkbox is checked. Click Next.
  6. On the Activities page, go through each activity and ensure that the information is completed correctly. If the assembly for the activity has not been migrated or is not in the same location as it was when the IP was created, the Class field will be empty. To prevent having to retype any information, you should replace the assembly before starting the wizard.
  7. When you are done editing activities, click Next.
  8. Ensure dependent files are still in the same location as shown, or remove them and add new dependent files. Click Next.
  9. Enter a path and filename for the new IP file. Do not use the same name as the previous IP so that you can ensure that you retain a copy of the previous IP. Click Next to build the IP.

You now have an IP that is compatible with Orchestrator and can be registered and deployed using Orchestrator Deployment Manager.

 

Last edited Sep 21, 2011 at 3:49 PM by rhearn, version 3

Comments

No comments yet.