The other day I came accross an interesting new problem while working with BPM in the SmartCloud Orchestrator (SCO). It was in a multi-staging environment and my client was trying to export a change made in their test environment to import it in their production environment.
When you are trying to export your freshly developed code from a test system and import it on a production system you would usually create a snapshot on test, export it and import it on production. Pretty much straight forward, no magic.
Now if the Process Application or the Toolkit that you are trying to export/import has dependecies on the
SCOrchestrator_Scripting_Utilities_Toolkit (SCOSUTK) and SCOrchestrator_Support_IaaS_Toolkit (SCOIAAS) (both shipped with SCO) and these Toolkits are already present in production, you may receive a notification during the import stating that these Toolkits already exist and will not be imported.
If you confirm this with 'OK' you may receive the following error message indicating the import failed:
Now, what went wrong?
In the installation guide for SCO IF0004 and IF0005 some of the manual steps described can lead to this problem.
For the mentioned toolkits SCOrchestrator_Scripting_Utilities_Toolkit (SCOSUTK) and SCOrchestrator_Support_IaaS_Toolkit (SCOIAAS) you have to update the dependencies and you need to create a new snapshot.
By doing this on both systems (test and production) individually, the internal Snapshot ID will differ in both environments due to the algorithm that is used to create these IDs. Although the Snapshot-Name as well as the acronym are identically on both systems, the import process will not identify them being the same due to the different IDs. Which does make sense.
Hence, a correct approach in a multi-staging environment is to perform these actions (updating the dependencies and creating a new snapshot) on one system and then export/import these to the other systems. Do not perform these steps on the target environment as this will lead to the above error.
If you encounter this issue, and the above steps did not help, take two of these and call me in the morning.