How to Compress your Workspace FOR IBM MDM

How to Compress your Workspace

This document will guide you through the process of converting a workspace into a binary workspace.

Step 1. Clean build the entire workspace.

Remove configured MDM.EAR from the Server.

Step 2. Export the MDM project as “Shared EAR”

               Right click on MDM  à export à  Share EAR

Save the MDM.ear to a temporary location.

This step packages all the projects into compressed binary modules (.Jar files) and adds them as

dependencies to MDM.EAR

Step 3. Create a new Workspace

               Follow all the required steps to set up the new Workspace

 for e.g  Deselect all validations under  Windows à General Preferences.

You need no t create a new server Profile. You can use any of configured existing server Profile 

Step 4. Import the MDM.ear exported earlier into the new Workspace

After this step you will see a single MDM project in the workspace.

              

Step 5. Extract the required Projects into Source format

Right click on MDM  à Shared EAR à Extract Binary Modules to Projects

Select only those projects  you want to work on.

DWLCommonServices  and  DWLCommonServicesEJB should always be selected.

Only the selected projects will be converted back to source format and listed in workspace.

All the other projects will be in compressed binary format (.Jar). You can follow this step anytime as and when you need to work on a particular project.

You can also package a source project to binary project when you are done working on it.

Step 6. Add Other Projects to the Workspace

Add CustomerResources and XMLTester projects to the workspace. These projects are not associated with MDM EAR Project and so needs to be added separately.

Step 7.  Add CustomerResources to classpath

If you are using existing server profile then you need to update server.xml to change classpath entries.

Go to D:\Program Files\IBM\SDP70\runtimes\base_v61\profiles\XXXX\config\cells\PC154104Node01Cell\nodes\PC154104Node01\servers\server1\server.xml

Where XXXX – Server Profile Name

      <classpath><<Path of new Workspace>>/CustomerResources/properties</classpath>

      <classpath><<Path of new Workspace>>/ConfigurationClient/src</classpath>

      <classpath><<Path of new Workspace>>/CustomerResources/xsd</classpath>

      <classpath><<Path of new Workspace>>/CustomerResources/dtd</classpath>

              

Step 8. Clean build the entire workspace once again and fix build errors.

After this step, You may get build errors like “Unable to resolve XXXXX”. Most of these errors occur because Projects were added to Java build path and now these projects are no longer available in Source format. Instead they are available in binary format. Adding required J2EE module dependencies to the corresponding Project will solve these build errors.

Step 9. Add and Publish MDM project to server.

               Start the Server.

Publish the Server.

Add the MDM EAR project to Server.

Publish the server.

Check the differences in build time and deploy time with the original workspace. You will be amazed. J