Rather than use the the File Save or File Open menu options in Oracle Workflow Builder, you can also use the Workflow Definitions Loader to save or load process definitions from a database or flat file.
Use the Loader program when you upgrade your database to preserve your process definitions to a flat file. When the database upgrade is complete, use the Loader program again to upload the definitions back into your database. You can also use the Loader program to transfer process definitions to other databases. The Loader program lets you quickly download or upload one or more process definitions to database or flat file without having to run Oracle Workflow Builder.
The Workflow Definitions Loader program accepts several parameters. You control the behavior of the Loader program based on the values that you provide to these parameters:
|Mode||Specify "Download" to download a process definition from the database to a flat file.|
|Specify "Upgrade" to apply a seed data upgrade to a database from an input file. The Workflow Definitions Loader assumes the access level of the file's creator (seed data provider) and overwrites any objects protected at a level equal to or above the upgrade file's access level. The Loader program preserves any customizations made to customizable seed data in the database.|
|Specify "Upload" to load a process definition from a flat file into the database. The upload mode is useful to someone who is developing a workflow process. It allows the developer to save definitions to the database without concern that accidental customizations to existing objects might prevent the upload of some process definition elements. The Workflow Definitions Loader uses the access level defined by the input file to upload the process definitions from the file and therefore will overwrite objects in the database that are protected at a level equal to or higher than that file's access level.|
|Specify "Force" to force an upload of the process definitions from an input file to a database regardless of an object's protection level You should be certain that the process definition in the file is correct as it overwrites the entire process stored in the database. The Force mode is useful for fixing data integrity problems in a database with a known, reliable file backup and for loading .wft files from Oracle Workflow Release 1.0 or 1.0.1, which reflect an older data model.|
Note: When using the Force mode to load a .wft file from Oracle Workflow Release 1.0 or 1.0.1 into a database, you must also complete a manual step once the .wft file is loaded. You must associate the lookup types that you load with an item type. To do this, in the Navigator window of Oracle Workflow Builder, drag the lookup types from the independent Lookup Types branch to a Lookup Types branch associated with an item type.
|File||Specify the full path and name of the file that you want to download a process definition to, or upgrade or upload a process definition from.|
|Item Type||If you set Mode to "Download", use the List button to choose the item type for the process definition you want to download.|
To upgrade-- WFLOAD apps/pwd 0 Y UPGRADE file.wft
To upload-- WFLOAD apps/pwd 0 Y UPLOAD file.wft
To force-- WFLOAD apps/pwd 0 Y FORCE file.wft
To download-- WFLOAD apps/pwd 0 Y DOWNLOAD file.wft ITEMTYPE1 [ITEMTYPE2 ... ITEMTYPEN]
Replace apps/pwd with the username and password to the APPS schema, replace file.wft with the file specification of a workflow process definition file, and replace ITEMTYPE1, ITEMTYPE2, ... ITEMTYPEN with the one or more item type(s) you want to download. You can also download all item types simultaneously by replacing ITEMTYPE1 with '*' (make sure you enclose the asterisk in single quotes).
A file specification is specified as: