IBM MDM DSUI workspace optimization
1. Set
the workspace preferences
1. Import
Shared EAR
When you extract the CusttomDataStewardshipWeb
project, the java files gets moved to src folder so do the below setting in the
workspace before importing EAR.
The page code should not be
present in JavaSource folder.
We can use the Shared EAR capabilities for doing the build for DSUI as well. We
need to change few preferences, project faces and library settings for it to
work.
I have tried it with a new workspace, the code is working
as expected and a lot faster. PFA the document for your reference.
Most of the time we only need CustomDataStewardshipWeb
project only and others are not modified, so extract only this one.
The CommonUIServiceDataObjects project is real killer
and we should use 16GB configuration machine if we want to generate SDO
objects and build this project.
ADD
-XX:+UseParallelGC
In eclipse.ini file
Open RAD open preferences=>project=>default source folder(JavaSource)=>Change it as per u r folder name
1. Set
the workspace preferences
(through menu Windowsà
preferences)
Click “show heap status” Check box check it.
Enable all capabilities
Disable as validations
Building à
circular dependencies—Change this to “warning”
Remove “build automatically”
Right click on the server in the server view of bottom pane
and change the publishing settings to “Never Publish Automatically”
1. Import
Shared EAR
Go to Import and choose “Shared EAR file”
Import the EAR and click finish
You will get a single project
Right click on the project and select “Extract Binary
Modules to Projects”
We need CustomDataStewardshipWeb more often so select only
this module
There will be errors, do the below steps to remove those.
Go to properties of CustomDataStewardshipWeb project
The project facet for DataStewardshipWeb project would be
1.4 by default, change it to 6.0
Add all the jars from CustomerDataStewardship project into
the libraries of extracted web project and do the full build. You would get
below two errors
1.
Faces resources needs to be updated
No comments:
Post a Comment