Recovering from Human Workflow Service Engine Faults

Managing Human Workflow Service Components and Engines 21-11 To export mapped attribute mappings, use the following values in the migration.properties file: objectType = TASK_PAYLOAD_FLEX_FIELD_MAPPING migrateAttributeLabel = false 3. Export the data with the ant script. The following example shows how to invoke the command and specify the parameters: ant -f ant-t2p-worklist.xml -Dbea.home=scratchoracleMW_HOME -Dsoa.home=scratchoracleMW_HOMEAS11gR1SOA -Dmigration.properties.file=migration.properties -Dsoa.hostname=hostname -Dsoa.rmi.port=7001 -Dsoa.admin.user=weblogic -Drealm=jazn.com -Dmigration.file=tmpexport_all_userRules.xml -Dmap.file=tmpexport_all_userRules_mapper.xml See Section 21.6.3, ant Script Data Migration Syntax for instructions on specifying ant properties. 4. Ensure that the application is deployed to the production system. 5. Create the migration.properties file to import user metadata for the worklist application to the production environment. Note the following: – You can only import one type of data at a time. – When you import data for a particular user or group, you must import it in separate operations. – You must import attribute labels before you import mapped attribute mappings. To import attribute labels, use the following values in the migration.properties file: objectType = TASK_PAYLOAD_FLEX_FIELD_MAPPING migrateAttributeLabel = true To import mapped attribute mappings, use the following values in the migration.properties file: objectType = TASK_PAYLOAD_FLEX_FIELD_MAPPING migrateAttributeLabel = false Note: After specifying the Admin user name, enter the password when prompted. Note: Human workflow artifacts such as task mapped attribute mappings, rules, views, and approval groups are defined based on namespace. The Data Migrator migrates human workflow artifacts based on namespace. Therefore, it is not possible to migrate human workflow artifacts based on a partition. 21-12 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite 6. Import the data to the production environment from the file export_all_ userRules.xml, which you created with the map.file property in Step 3. The following example shows how to invoke the command and specify the properties: ant -f ant-t2p-worklist.xml -Dbea.home=scratchoracleMW_HOME -Dsoa.home=scratchoracleMW_HOMEAS11gR1SOA -Dmigration.properties.file=migration.properties -Dsoa.hostname=hostname -Dsoa.rmi.port=7001 -Dsoa.admin.user=weblogic -Dsoa.admin.password=password -Drealm=jazn.com -Dmigration.file=tmpexport_all_userRules.xml -Dmap.file=tmpexport_all_userRules_mapper.xml Note that if the data, such as rules and views, are attached to the user, then the user must be an available user in the production SOA server. 7. Deploy J2EE human task forms, as you would deploy any .ear file. 8. If necessary, update the workflow notification configuration with production mail server and inbound and outbound email accounts. See Section 19.1, Configuring Human Workflow Notification Properties.

21.6.2 migration.properties File Syntax

The migration.properties file specifies the input parameters for data migration. The template for this file is located in the following directory: The migration.properties file contains the following input parameters: operationType = {EXPORT | IMPORT} objectType = {VIEW | RULE | TASK_PAYLOAD_FLEX_FIELD_MAPPING} name = name of VIEW or TASK_PAYLOAD_FLEX_FIELD_MAPPING user = username of VIEW or RULE group = groupname for RULE grantPermission = {true | false} migrateAttributeLabel = {true | false} override = {true | false} skip = {true | false} migrateToActiveVersion = {true | false} Argument Definition operationType Specify to perform one of the following actions: ■ EXPORT: Data is migrated from a SOA server instance into an XML file. ■ IMPORT: Data is migrated from the XML file into the SOA server instance. objectType Specify the type of object to migrate: ■ VIEW: Migrates views. ■ RULE: Migrates vacation rules. ■ TASK_PAYLOAD_FLEX_FIELD_MAPPING: Migrates mapped attribute mappings.