Is it possible to import procedures with a predefined version into TIBCO iProcess Engine using "Load From..." in the Procedure Management of the TIBCO iProcess Workspace (Windows)?
Article ID: KB0088195
Updated On:
| Products | Versions |
|---|---|
| TIBCO iProcess Engine (Oracle) | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
For example, a Test environment will work on a procedure a number of times, releasing it regularly to a Testing environment. This would mean the procedure versions are increased accordingly, since they are in sync with updates.
At some point the latest tested version would be exported from the Testing environment to the Production environment.
In the Production environment the latest released version of the procedure is quite different from the one being imported. For example, a production released procedure could be at version 2.6 and the latest release from the Test environment could be 3.4.
When the export of version 3.4 from the Test environment is imported into the Production environment, for version control reasons, it would be preferable for the procedure version to remain as 3.4, not the version defined by the Production system.
Environment:
==========
o All supported versions of TIBCO iProcess Engine.
Symptoms:
=========
n.a.
Cause:
======
n.a.
Resolution:
=========
It is not possible to guarantee that the same procedure version number is used when exporting a procedure from one system and importing to another when using the "Load From..." facility in Procedure Management of the TIBCO iProcess Workspace (Windows). This is inevitable as the system on which the procedure is imported may already have its own instance of that version number. Version numbers may not be reused nor may version numbers lower than the current version number be used.
The “swutil IMPORT” command provides the “-n” option. This will attempt to import the procedure definition using the same version number as was used on the exporting system. However, if that version number is not available on the importing system then a new version number will be automatically allocated.
To attempt to retain the procedure version, use the TIBCO iProcess Engine "swutil" utility as follows:
1). Use the "swutil EXPORT" command to save the procedure from the TIBCO iProcess Engine into a file, proc_name.xfr, where proc_name is the name of the procedure. This should be performed on the Test environment using the example described above.
2). Transfer the proc_name.xfr to the Production environment.
3). Use the "swutil IMPORT" command to load the procedure into the Production TIBCO iProcess Engine.
Full details of options available when using the "swutil" utility are available in the TIBCO iProcess™ swutil and swbatch Reference Guide.
Description:
============
For example, a Test environment will work on a procedure a number of times, releasing it regularly to a Testing environment. This would mean the procedure versions are increased accordingly, since they are in sync with updates.
At some point the latest tested version would be exported from the Testing environment to the Production environment.
In the Production environment the latest released version of the procedure is quite different from the one being imported. For example, a production released procedure could be at version 2.6 and the latest release from the Test environment could be 3.4.
When the export of version 3.4 from the Test environment is imported into the Production environment, for version control reasons, it would be preferable for the procedure version to remain as 3.4, not the version defined by the Production system.
Environment:
==========
o All supported versions of TIBCO iProcess Engine.
Symptoms:
=========
n.a.
Cause:
======
n.a.
Resolution:
=========
It is not possible to guarantee that the same procedure version number is used when exporting a procedure from one system and importing to another when using the "Load From..." facility in Procedure Management of the TIBCO iProcess Workspace (Windows). This is inevitable as the system on which the procedure is imported may already have its own instance of that version number. Version numbers may not be reused nor may version numbers lower than the current version number be used.
The “swutil IMPORT” command provides the “-n” option. This will attempt to import the procedure definition using the same version number as was used on the exporting system. However, if that version number is not available on the importing system then a new version number will be automatically allocated.
To attempt to retain the procedure version, use the TIBCO iProcess Engine "swutil" utility as follows:
1). Use the "swutil EXPORT" command to save the procedure from the TIBCO iProcess Engine into a file, proc_name.xfr, where proc_name is the name of the procedure. This should be performed on the Test environment using the example described above.
2). Transfer the proc_name.xfr to the Production environment.
3). Use the "swutil IMPORT" command to load the procedure into the Production TIBCO iProcess Engine.
Full details of options available when using the "swutil" utility are available in the TIBCO iProcess™ swutil and swbatch Reference Guide.
Issue/Introduction
Is it possible to import procedures with a predefined version into TIBCO iProcess Engine using "Load From..." in the Procedure Management of the TIBCO iProcess Workspace (Windows)?
Feedback
Yes
No
Powered by
