Managing Human Task Service Component Policies

Managing Human Workflow Service Components and Engines 21-9 If outgoing notifications are sent to an incorrect address of a message recipient, they are displayed as errors in the Recipient column. You can correct the recipients address and resend the notification.

4. In the Recipient column, click the email address and correct the address.

5. Perform the following actions on incoming notifications. For more information about notifications, see Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

21.6 Moving Human Workflow Data from a Test to a Production Environment

You can migrate Human Workflow user metadata, such as views, mapped attribute previously known as flex field mappings, and vacation rules, from a test environment to a production environment using the Human Workflow User Config Data Migrator. The Data Migrator is available as an ant target that can be executed at the command line. You specify the input parameters for the migration of data in a properties file, migration.properties. For example, assume you have two SOA servers installed: ■ SOAServer_A Action Description Send Test Notification Test that outgoing messages are arriving at the correct destination. This ensures that the destination is reachable and messages are arriving. Selecting this option invokes a dialog for specifying the following destination details: ■ Destination address ■ Delivery channel for example, email ■ Message subject and content Resend Select specific outgoing notification messages in the table and click Resend to resend. Use this option if you believe that messages are not arriving at their correct destination. For example, you may have incorrectly configured a recipient address. After correcting the address, click Resend to test the delivery. Resend All Similar Notifications Resend all error notification messages having the same recipient address as the selected one. View Bad Addresses Click to display a list of bad or invalid addresses. The addresses are automatically removed from the bad address list after one hour. If you do not want to wait an hour, you can explicitly select and delete them. Delete icon Click to delete a selected message. Action Description Mark as Spam Mark the message senders address of the selected notification as spam. This action prevents incoming notifications from the same sender address from being delivered again. No Spam Mark incoming messages as not being spam. This action enables new messages from the senders address to be delivered again. Delete icon Click to delete a selected message. 21-10 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite A test server that includes human workflow user-configurable data user views, standard views, user rules, group rules, attribute labels, and task payload mapped attribute mappings. ■ SOAServer_B A production server to which you want to move the data on SOAServer_A. Since you have a significant amount of data on SOAServer_A, it can be time consuming to manually migrate all of the data to SOAServer_B. You can use the Data Migrator to move the data from the test server to the production server. You run the ant target at the command line of SOAServer_A to migrate data to SOAServer_B. Migration is always performed through an XML file. The Data Migrator supports the following operations: ■ Export operation: Stores all the human workflow user-configurable data from the source SOA server to the XML file. ■ Import operation: Creates all the human workflow user-configurable data in the target SOA server by reading from the XML file. The Data Migrator consists of the following files: ■ migration.properties: Contains all required input properties in terms of key-value pairs for migration operations. ■ build.xml: Contains the ant target runHwfMigrator that executes the Data Migrator.

21.6.1 Moving Human Workflow Data from Test to Production Environments

Perform the following steps to move data from a test to a production environment. To move human workflow data from test to production environments: 1. Ensure that the PATH environment variable contains the JAVA_HOME and ANT_ HOME environment variables and that they point to the locations within the Oracle SOA Suite installation. 2. Create a migration.properties file in any location to export user metadata for the worklist application for example, group rules, views, mapped attribute mappings, and vacation rules from the test environment. See Section 21.6.2.1, Migration Property File Examples for instructions on how to specify properties. Note the following: – You can export mapped attribute mappings. – You can export attribute labels. – You can only export one type of data at a time. – When you export data for a particular user or group, you must export each in separate operations. – You must export attribute labels before you export mapped attribute mappings. To export attribute labels, use the following values in the migration.properties file: objectType = TASK_PAYLOAD_FLEX_FIELD_MAPPING migrateAttributeLabel = true 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.