IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from previous versions > Migrating from Teamworks 6 > Migrating from Teamworks 6 to IBM BPM V8.0.1 > Migrating the runtime environments

Instance mapping file examples

The instance mapping file that you generate for each runtime environment must be complete as shown in the provided examples.

BPD entry example

The following example shows the beginning of an instance mapping file, along with a complete entry for a BPD. The <from> tag lists the name of the BPD in Teamworks 6 and the <to> tag lists the process application and snapshot to which to map this particular BPD in IBM BPM V8.0.1. In this example, the BPD named Billing Disputes is mapped to the Initial Import snapshot of the All1 process application. The BPD retains its original name (Billing Disputes) in IBM BPM V8.0.1.

If this mapping did not match your expectations, you could change the designated process application or snapshot by editing the contents of the <processApp> and <snapshot> tags to point to the correct construct in IBM BPM V8.0.1.

Remember a mapping must exist in the instance mapping file for each BPD that has in-flight instances and for each service that results in a task. (Services that produce tasks require an entry in the mapping file only if the teamworks.upgrade.migrateStandaloneTasks property in the upgrade.properties file is set to true.)

<?xml version="1.0" encoding="UTF-8"?>
<upgrade xmlns="http://lombardisoftware.com/schema/teamworks/upgrade/config.xsd">
  <runtime>
    <mappings>
      <bpd>
        <from>
          <name>Billing Disputes</name>
        </from>
        <to>
          <processApp>ALL1</processApp>
          <snapshot>Initial Import</snapshot>
        </to>
      </bpd>

Service entry example

The following example shows the end of an instance mapping file, along with a complete entry for a service. The <from> tag lists the name of the service in Teamworks 6 and the <to> tag lists the process application and snapshot to which to map this particular service in IBM BPM V8.0.1. In this example, the service named Research Dispute is mapped to the Snap3 snapshot of the PA2 process application. The service retains its original name (Research Dispute) in IBM BPM V8.0.1.

<service>
        <from>
          <name>Research Dispute</name>
        </from>
        <to>
          <processApp>PA2</processApp>
          <snapshot>Snap3</snapshot>
        </to>
      </service>
    </mappings>
  </runtime>
  <problems errorLimit="50" warnLimit="1000">
    <ignore>TWU-0000-1-3-5</ignore>
    <ignore>TWU-0000-1-3-6</ignore>  
  </problems>
</upgrade>

If this mapping did not match your expectations, you could change the designated process application or snapshot by editing the contents of the <processApp> and <snapshot> tags to point to the correct construct in IBM BPM V8.0.1.

Remember a mapping must exist in the instance mapping file for each BPD that has in-flight instances and for each service that results in a task. (Services that produce tasks require an entry in the mapping file only if the teamworks.upgrade.migrateStandaloneTasks property in the upgrade.properties file is set to true.)

Also, you can adjust the settings in the <problems> tag as follows:

Setting	Description
errorLimit="50"	Specify the number of recoverable errors to allow during migration. The default is 50. If the specified number is exceeded, the migration fails.
warnLimit="1000"	Specify the number of warnings to allow during migration. The default is 1000. If the specified number is exceeded, the migration fails.
<ignore>TWU-0000-1-3-5</ignore>	Use this setting to ignore specific recoverable errors, which enables the migration to proceed to the next error or to the end.

: Migrating the runtime environments