Importing and Transferring Considerations
You can use Orchestrator Studio to export and import the stateful orchestrations. If you import through Orchestrator Studio while there are active stateful instances, the system will move the old stateful version to F980081 so the existing instances can resume using the old version and set the current stateful version to one higher than the last for all the new instances. If there are no active stateful instances, the stateful version will not change during the import.
(Tools Release 9.2.8.4 and 9.2.9.1) The system manages the stateful orchestration versions when sharing, promoting, and importing them from P98220U or P98220W. The stateful orchestration version number is incremented by one when sharing, promoting, or importing, regardless of the existence of stateful instances because of UDO caching. The system may take some time to update the new version in all the UDO caches even if there are no instances when the orchestration is shared or promoted. Therefore, instances can still be started using the old version. The old version is saved in F980081 so the instances started with the old version can be completed with the old specifications.
If you are on Tools Release 9.2.8.3 or 9.2.9.0, it is recommended to use the Orchestrator Studio Export/Import to move stateful orchestrations. If you are using P98220U or P98220W to promote or share a stateful orchestration, ensure that all active stateful instances are completed before promoting or sharing.