Deploying an MDM Virtual project with sample data using MDM Workbench

Body

Creating a new Virtual Configuration Project

1. Open MDM Workbench.
2. Click File > New > Other > Master Data Management > Configuration Project.
3. Click Next.
4. Enter a name for the new Configuration Project. For this blog post I have named mine "Party".
5. Click Next.
6. Select a template to use for the project. For this blog post I selected the Virtual > Party template.
7. Click Finish. Workbench will create a new project using the name you supplied. It can be viewed in Package Explorer.

Creating a connection to the Operational Server

1. Switch to the MDM Configuration perspective in Workbench.
2. Click the Servers tab at the bottom pane of Workbench, right click on the white space in the Servers window and select New >Server.
3. Select Websphere Application Server 8.5 as the server type.
4. Enter the server's hostname/IP address in Server's host name.
5. Enter an identifable name for the server in Server name.
6. Make sure the Server runtime environment is set to Websphere Application Server v8.5.
7. Click Next.
8. If the Operational Server is on the same machine as Workbench, ensure the correct profile name is selected and click Automatically determine connection settings.
9. If the Operational Server is a remote machine, click Manually provide connection settings.
   1. You need to supply the correct port numbers for the Operational Server.
      1. IPC is the IPC_CONNECTOR_ADDRESS.
      2. RMI is the BOOTSTRAP_ADDRESS.
      3. SOAP is the SOAP_CONNECTOR_ADDRESS.
10. If security is enabled on the Operational Server, tick Security is enabled on this server.
    1. Enter the username and password to connect to the Operational Server.
11. Enter the Application server name for the Operational Server.
12. Click Finish.    

Deploy the new Configuration Project:

1. At the top of Workbench, click Master Data Management > Deploy Configuration Project.
2. Select the "Party" project you have just created.
3. Select the Server you have just defined the connection for.
4. Leave the check boxes unchanged.
5. Click Finish and wait for the wizard to deploy the project to the Operational Server.

Processing and loading the sample data:

1. Inside the Configuration Project there is a DemoData_config folder. This needs to be copied into the work directory on the Operational Server. This will be located under <WAS_install>/profiles/<AppSvr01 or Node01>/installedApps/<Cell name>/MDM-native*.ear/native.war/work/<Workbench Configuration Project Name>/work
2. In the DemoData_config folder there will be two types of files; *-mpxdata-input.cfg and *.unl. Make a note of all the file names. The "Party" project I created has four files - org-mpxdata-input.cfg, orgdata.unl, per-mpx-data-input.cfg, persondata.unl.
3. In Workbench, click Master Data Management > New Job Set.
4. Select the "Party" project
5. Leave Job Set Template as None
6. Select the correct Server
7. Click Next
8. Click the add button (green plus sign), and select Bulk Tools > Derive Data and Create UNLs (mpxdata)
9. Click OK.
10. Under the Input tab, enter DemoData_Config/orgdata.unl in the Input File field. If your Configuration project does not have orgdata.unl, enter a valid *.unl file from the DemoData_config folder. This field will look in the Operational Server's work directory (which is why we copied the folder into the work directory on the Operational Server)
11. Leave the rest of the tab unchanged.
12. Click the Input Config tab.
13. Click the Import From File button. This will open a File Browser window folder structure at the "Party" project root. Open the DemoData_Config folder and select the org-mpxdata-input.cfg file.
14. Click the Options tab
15. Select MEMCOMPUTE under Mode. Leave everything else unchanged.
16. Click Finish. This should start the job running. Select the Jobs tab in Workbench and wait for the job to finish. Once the job finishes, right click on the job and select Run Jobset Again. This will load the Job Configuration window again.
17. Click the Options tab and select MEMPUT. Make sure that at the bottom of the window, Mem mode is complete, and Put type is insert_update.
18. Click Finish. Select the Jobs tab in Workbench and wait for the job to finish.
19. Repeat steps 3-18 for the remaining *.unl with corresponding *-mpxdata-input.cfg files.

Comparing member records:

1. Once you have finished running the mpxdata jobs,  click Master Data Management > New Job Set.
2. Click the add button, and select Bulk Tools > Compare Members in Bulk (mpxcomp).
3. Under entity type, I selected mdmper - this will differ if you did not choose the Party template.
4. Click the Options tab, at the bottom of the window select Match, link, and search for the Comparison mode.
5. Click Finish. Select the Jobs tab in Workbench and wait for the job to finish.
6. Repeat steps 1-5 for the remaining entity types - I only had mdmorg left to do.

Enabling entity linkage:

1. Once you have finished running the mpxcomp jobs,  click Master Data Management > New Job Set.
2. Click the add button, and select Bulk Tools > Link Entities (mpxlink).
3. Under entity type, I selected mdmper - this will differ if you did not choose the Party template.
4. On the Inputs and Outputs tab check the Generate BXM output option. Leave the rest of the tab unchanged.
5. Click Finish. Select the Jobs tab in Workbench and wait for the job to finish.
6. Repeat steps 1-5 for the remaining entity types - I only had mdmorg left to do.

Conclusion

After completing these steps, you will have deployed a new Configuration Project to your Operational Server, and you will have populated the server with the sample data from the project template. To confirm this, perform a search against your Operational Server and you should have entities returned.