Using the Physical to Virtual MDM Publisher sample with no MDM customization

If you do not have any customization (additions or extensions) in your source Physical MDM instance, follow these steps:

1. Prepare the use the Physical to Virtual MDM Publisher sample:
   1. Run the MDM Workbench and create a new workspace.
   2. Import the following projects into the newly created workspace:

      com.ibm.mdm.ae2se 
      com.ibm.mdm.ae2se.cba
      com.ibm.mdm.ae2se.resources
      com.ibm.mdm.ae2se.transformation

   3. Open the com.ibm.mdm.ae2se\src\ae2se.properties file and change the serviceEndPoint.url= to match the ESOA target in your target environment, then change the synchronization.requesterName= value to match the MDM user name in your source environment, then save the file.
   4. Include MDM in the workspace and resolve any potential compile issues by referencing the MDM component.
   5. You may see some errors on the com.ibm.mdm.ae2se.transformation/BundleContent/META-INF/MANIFEST.MF file on the imported packages that begin with either com.ibm.xltxe or com.ibm.xml. In this case, make the resolution of these packages optional. For example:

      com.ibm.xltxe.rnm1.xtq.common.utils;resolution:=optional,

   6. Build all projects in the MDM Workbench.
2. Deploy the Enterprise Service madclient.war to the target InfoSphere® MDM Standard Edition and deploy the com.ibm.mdm.ae2se.cba to the source Advanced Edition instance.
   • Target virtual style InfoSphere MDM instance:
     1. Run the MDM Workbench and create a second new workspace.
     2. Create an MDM Configuration project based on the Party template.
     3. Generate Enterprise Services for that project by selecting the newly created project, right-click the project, then click Master Data Management > Generate Enterprise Services.
     4. ESOA deployment steps to configure and deploy the madclient.war into your designated InfoSphere MDM operational server environment.
     5. Restart the target virtual style MDM instance.
   • Source InfoSphere MDM Advanced Edition:
     1. Run the following SQL scripts to insert the required metadata for this sample:

        com.ibm.mdm.ae2se.resources\sql\setup-CapturePartyChanges.sql
        com.ibm.mdm.ae2se.resources\sql\setup-SynchronizePartyChanges.sql

        Note: Note: to roll back the changes made by the preceding SQL scripts, run the following SQL scripts:

        com.ibm.mdm.ae2se.resources\sql\rollback-CapturePartyChanges.sql
        com.ibm.mdm.ae2se.resources\sql\rollback-SynchronizePartyChanges.sql

     2. Right-click on com.ibm.mdm.ae2se.cba and export it as an OSGi Composite Bundle (CBA).
     3. Deploy the CBA to your source physical style MDM instance.
     4. Restart the source physical style MDM instances.