Completing configuration for Business Process Choreographer

1. If you used the LDAP people directory provider, perform the actions described in Configuring the LDAP people directory provider.
   Note: If you used the BPMConfig command to migrate, the LDAP configuration was migrated from source to target.
2. If you used the Virtual Member Manager people directory provider, perform the actions described in Configuring the Virtual Member Manager people directory provider.

In a network deployment environment, the transformation files must be available on the deployment manager and on the managed nodes (if they are on different computers). Make sure that they all use the same version of the transformation files.

To find the transformation files that you are using in the source environment, check the value of the transformation file path that is specified in the people directory configuration. If the transformation file path is install_root/ProcessChoreographer/Staff directory, you are using the default files. Otherwise, you are using custom transformation files that you must manually copy to the target environment and reconfigure in the people directory configuration.

For the VMM file registry:

1. Add the substitutionStartDate and substitutionEndDate properties to the definition of the PersonAccount entity type in the wimxmlextension.xml file. In a network deployment environment, edit the file on the deployment manager.

   The file is in profile_root/config/cells/cellName/wim/model.

   Extend the file to include the new properties:

   <wim:propertySchema nsURI="http://www.ibm.com/websphere/wim" 
        dataType="STRING" multiValued="false" propertyName="substitutionStartDate">
       <wim:applicableEntityTypeNames>PersonAccount</wim:applicableEntityTypeNames>
   </wim:propertySchema>
   
   <wim:propertySchema nsURI="http://www.ibm.com/websphere/wim" 
        dataType="STRING" multiValued="false" propertyName="substitutionEndDate">
        <wim:applicableEntityTypeNames>PersonAccount</wim:applicableEntityTypeNames>
   </wim:propertySchema>

2. The changes become effective after the deployment manager is restarted.

For the VMM property extension registry:

1. Check that the substitution properties isAbsent and substitutes are defined for the property extension repository. If they were not defined before migration, no substitution information was stored in the VMM property extension repository, and this migration step is not required.

   Change to the directory install_root/bin and enter the following commands in either local mode or connected mode. In a network deployment environment, enter the commands on the deployment manager.

   wsadmin -username admin -password adminPassWord
   $AdminTask listIdMgrPropertyExtensions

2. Add the new properties substitutionStartDate and substitutionEndDate to the property extension repository configuration by entering the following commands:

   $AdminTask addIdMgrPropertyToEntityTypes 
      {-name substitutionStartDate 
       -dataType String 
       -isMultiValued false 
       -entityTypeNames PersonAccount 
       -repositoryIds LA}
   
   $AdminTask addIdMgrPropertyToEntityTypes 
      {-name substitutionEndDate 
       -dataType String 
       -isMultiValued false 
       -entityTypeNames PersonAccount 
       -repositoryIds LA}

3. The changes become effective after the deployment manager is restarted.
4. Verify that the new properties were added to the property extension repository configuration by entering the following command:

   $AdminTask
   listIdMgrPropertyExtensions

• HTM_PredefinedTasks_Vnnn_cluster_name.ear
• HTM_PredefinedTaskMsg_Vnnn_cluster_name.ear

nnn

is the version number when the application was last updated, for example 700. If the newest version of these applications looks older than the current release, it just means that it did not change since that version. The important thing is whether there are multiple versions of these applications.

cluster_name

is the name of the cluster.

• bpe137650.jar
• icu4j_3_4_1.jar
• task137650.jar