© Copyright International Business Machines
Corporation 2006, 2008. All rights reserved. US Government Users
Restricted Rights - Use, duplication or disclosure restricted by GSA
IBM InfoSphere Master Data Management Server Workbench V8.0.1.2 Readme
This Programming
Temporary Fix (PTF) for IBM InfoSphere Master Data Management (
This hotfix only
applies to the InfoSphere MDM Server Workbench. For the InfoSphere MDM server
hotfix, see IBM InfoSphere Master Data Management Server 8.0.1.x.
This update includes the
following fixes:
|
|
Incident/PMR |
Description |
|
1 |
PMR # 85259,999,706 |
Fixed code to make MDM workbench use existing code table instead of creating new one when created an MDM 'Type code' attribute in Addition in which use an existing code table. |
|
2 |
PMR # 21731,999,706 |
Fixed code to enable the function to add 'Type code' attribute in Extension. |
|
3 |
PMR # 85260,999,706 |
Fixed code to prevent from workbench generating invalid temporary project files which may cause code generation errors. |
|
4 |
PMR # 45395,082,000 |
Fixed code to generate the ObjectNavigator property declaration of extension Objects. |
|
5 |
PMR # 85262,999,706 |
Fixed some code table definition missing by providing the modified Reference Model file. Those file were usually packaged in the MDM.ear - they are not part of the MDM Workbench plug-ins. Therefore, client need to follow our attached instruction file and apply those file to their MDM EAR workspace environment. |
|
6 |
Defect # 4082 |
Fixed code to prevent from adding incorrect import statement to the generated xsd file for the extension when a data extension references a code table defined in another module. |
|
7 |
PMR # 56716,082,000 |
Fixed code to prevent from causing the stack overflow issue being caused by having a cyclic dependency between projects |
This PTF is backward compatible with InfoSphere
This PTF changes how Web Services are generated by InfoSphere MDM Server Workbench. As part of the Web Service generation process, a project called .MDMWebService is created in your workspace. This contains temporary files used during Web Service generation and will be automatically deleted when code generation completes. If code generation is terminated due to errors, this project may not be automatically deleted. You may delete it manually or ignore it - it should be deleted the next time code generation is run.
InfoSphere MDM Server
Workbench is installed as an extension to IBM Rational Application Developer
v7.0.0.3 or higher.
The following RAD features must be installed:
InfoSphere MDM Server
must be installed onto your BEA WebLogic application server following the
instructions in the InfoSphere MDM Server Installation Guide. Ensure the
InfoSphere MDM Server application is deployed on the server and is working correctly
before starting to develop extensions to the InfoSphere MDM Server application.
To prepare your development environment:
1.
Create a new Rational Application Developer workspace.
2.
Locate the MDM.ear that has been deployed on your application
server
3.
From the RAD menu, select File > Import - J2EE - EAR file to
import the MDM.ear into your development workspace.
4.
Set the target runtime to generic
BEA WebLogic Server v9.2.
5.
Create a new project named 'CustomerResources' in your workspace.
6.
Locate the properties.jar file in the InfoSphere MDM Server
application projects, and unzip the properties.jar file into the
CustomerResources project.
7.
Create a folder named 'schemas' in the CustomerResources project
8.
Locate the DWLSchemas.jar file in the InfoSphere MDM Server
application projects and unzip this into the CustomerResources/schemas folder.
You are now ready to develop additions and extensions to InfoSphere MDM Server
as described in the InfoSphere MDM Server Workbench User Guide.
The properties.jar and
DWLSchemas.jar files contain files that you must modify in order to deploy
additions and extensions. When you deploy the extended application
to your application server, you can either:
· Replace
the properties.jar file and the DWLSchemas.jar file that are contained within
the MDM.ear file with your modified versions.
· Add
the CustomerResources and CustomerResources and schemas folders to the
application server's classpath so that the modified files will be loaded
instead of the versions packaged into the MDM.ear.
To
deploy the extended application, from the RAD menu, select File > Export -
J2EE - EAR file to export the InfoSphere MDM Server application project as an
ear file that you can deploy onto your application server.
If there are compilation
errors in the generated WS and WSEJB projects that appear to be caused by
missing class files, part of the Web Service generation process has
failed. To resolve the problem, run the code generation again. If
that does not resolve the problem, try the following solutions:
The generated WSDL and
XSD files for additions are located in the generated WSEJB project under
ejbModule/META-INF/wsdl, and for data extensions can be found in the extended
module's WSEJB project under ejbModule/META-INF/wsdl. If there are errors,
which appear as red crosses, in any of these files then Web Service generation
will fail.
In data extensions errors
can be caused when a property is defined with the same name as a field in the
extended entity. Any problems with naming can be corrected by changing the
relevant name in the InfoSphere MDM Server module model, then re-generating.
The wsgen.xml file in the
build folder of the generated WS project is an Ant script that performs part of
the Web Service generation process. Run this script in isolation to
generate diagnostic information.
1.
Right-click on wsgen.xml and select Run As > Ant Build ....
2.
In the dialog, select the JRE tab.
3.
Ensure that Run in the same JRE as the workspace is selected.
4.
Click Run
IBM Software Support provides
assistance with product defects.
Before you
submit your problem to
Product support
can be obtained through the following methods.
|
On the Web |
Go to http://www.ibm.com/software/data/masterdata/customer/
|
|
By Telephone |
•
If you are in •
If you are outside of |
The following
terms are trademarks of International Business Machines Corporation in the
Other company,
product, or service names may be trademarks or service marks of others.