1 | P a g e
How to Compress your Workspace ( IBM MDM workspace optimization )
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.
2 | P a g e
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 ( SharedEAR ) 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 J2ee Extract Binary Modules to Projects
Select only those projects you want to work on.
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.
3 | P a g e
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\s
ervers\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
publish/deploy time with the original workspace.
You will be amazed.
How to Compress your Workspace ( IBM MDM workspace optimization )
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.
2 | P a g e
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 ( SharedEAR ) 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 J2ee Extract Binary Modules to Projects
Select only those projects you want to work on.
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.
3 | P a g e
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\s
ervers\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
publish/deploy time with the original workspace.
You will be amazed.
Hi MONOJ KUMAR Das,
ReplyDeletethanks for posting this! I followed the steps and it worked until I tried to modify mdmxmi and generate code: mdmxmi file appears to be read-only, all the options to modify it are greyed-out.
Is this expected behavior? is there way to overcome this?
thanks in advance!
Sorry for very late reply.
ReplyDeleteWell yes, we too have observed this behavior. The best way to get over it is, if you have your code base on version control then checkout that particular project(on which you need to work) from version control rather then shared ear into your workspace. This will be alternative to step 5.
Once you do this you will be able to see that the ear deployed on server(Server view on RAD/RSA) {after clean, build, restart}[by expanding the ear]is referring to the project checked out from version control. Hope it helps.