Upgrading InfoSphere MDM Reference Data Management

Upgrading InfoSphere MDM Reference Data Management version 11.3 Fix Pack 1 Manually
This document helps you in applying the InfoSphere MDM Reference Data Management version 11.3 fix pack 1 manually instead of
running the madconfig target Apply_Fixpack.
IMPORTANT: Before proceeding with any of the following manual steps, make sure you applied fix pack through Installation manager.
Once you have applied this fix pack on InfoSphere MDM Reference Data Management version 11.3, two directories, backup and
updates, are created under <RDM_HOME>.
The updates directory contains all the details regarding the fix pack, like template for this and files needed for this fix pack.
The backup directory contains a directory with fix pack number; for example, if you apply fix pack 02 then there will be a directory
/02000 and a properties file named MDM_FixpackDetails.properties.
The following are components are changed for InfoSphere MDM Reference Data Management version11.3 Fix Pack 1:
•
OSGI changes ( Bundles , CBA and EBA changes )
•
Static Changes
•
RDM Client User Interface Changes
•
Database Changes
OSGi changes (Bundles, CBA and EBA changes)
These are the bundles names that you must update for InfoSphere MDM Reference Data Management version 11.3 Fix Pack 1:
•
com.ibm.mdm.server.dwlcommonservices
•
RDM
You can find these bundles under <RDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.rdm.fix/bundles. All
bundles are appended with fix pack version.
I. Add bundles to the WebSphere Application Server internal bundle repository:
1.
Log into the WebSphere Application Server Administrative Console.
2.
Navigate to Environment
3.
Select a bundle and add it to the Internal bundle repository.
4.
Repeat these steps for all bundles, or proceed to stage II.
OSGi bundle repositories
Internal bundle repository.
II. Once all bundles and CBAs are added to the internal bundle repository, you must update the latest bundles in Assets.
1.
Navigate to Applications
Application Types
Assets.
2.
Select the asset named com.ibm.mdm.cdh.app-<MDM-App-Name>.eba.
3.
Click the Update bundle versions in this application link.
4.
Verify that you see all the bundles for this EBA and the version numbers which are used currently for each bundles. By default
bundles will have only one version (11.3.0.FP00IF000_20140523-0446) that comes with base version of MDM
Reference Data Management. You should see the two version numbers for the bundles that you added in stage I.
5.
Select latest fix pack version for the bundles. The version number for Fix pack 1 is 11.3.0.FP00IF001_201411140829.
6.
Update the version numbers for all bundles you updated in stage I.
7.
Click Preview after updating all bundles with latest version of fix pack.
8.
Verify that you can see the difference between Deployed Version and New version for all bundles and CBAs.
9.
Verify under New Version that you see 11.3.0.FP00IF001_20141114-0829 for all the bundles which we added in
stage I.
10. Once you have confirmed the version numbers, click Create.
III.
1.
Navigate to Applications
Application Types
Business-level applications.
2.
Select CDH-operational-server-EBA-<MDM-App-Name>.
3.
Select com.ibm.mdm.cdh.app.<MDM-App-Name>_0001.eba.
4.
Click Update to latest deployment.
5.
Verify that you can see a preview of all bundles with new version number, then click OK.
6.
Click Next on this page and the next without doing any modifications.
7.
Click Finish and then Save.
8.
Finally, click OK and then Save.
User Interface Changes
RDM Client User Interface Changes
IMPORTANT: The following procedure will redeploy the RDMClient UI, so it is strongly recommended that you make a backup of the
existing Inspector UI EAR, which you can locate in <RDM_HOME>/InstallableApps/ear/RDMClientEAR.ear.
New files for User Interfaces are located at
<RDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.rdm.fix/userinterface/
com.ibm.mdm.build.rdm_ui/installer. Locate the RDMClientEAR.ear.zip file in that location and extract that ZIP file
in that location only.
I.
1.
Log in to the WebSphere Application Server Administrative Console.
2.
Navigate to Applications
1.
Select the check box for RDMClientEAR-<MDM-App-Name> or RDMClientEAR and change the action from start to
All applications.
stop, the click Submit Action. This will stop the RDMClientEAR-<MDM-App-Name> or the RDMClientEAR application.
3.
Select the check box for RDMClientEAR-<MDM-App-Name> or RDMClientEAR, click Remove to remove this
application from WebSphere Application Server, then click OK and Save.
4.
Verify that RDMClientEAR-<MDM-App-Name> or RDMClientEAR is removed from WebSphere Application Server
Administrative Console.
1.
Create a temporary directory /opt/TempRDM under this folder, then extract
<MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.rdm.fix/userinterface/com.ibm.mdm.bu
II).
ild.rdm_ui /installer/RDMClientEAR.ear to the temporary directory you created.
2.
Create a temporary directory under the /opt/TempRDM folder named /RDMClientEAR.
3.
Extract the RDMClientEAR.ear to the /opt/TempRDM/RDMClientEAR folder.
4.
Delete the RDMClientEAR.ear from the /opt/TempRDM folder.
5.
Create directories /RDM_JAX-WS_Client and /RestAPI under the /opt/TempRDM/RDMClientEAR directory.
6.
Extract RDM_JAX-WS_Client.jar to the /opt/TempRDM/RDMClientEAR/RDM_JAX-WS_Client directory, then
extract RestAPI.war to the/opt/TempRDM/RDMClientEAR/RestAPI directory.
7.
Delete the files RDM_JAX-WS_Client.jar and RestAPI.war from the /opt/TempRDM/RDMClientEAR directory.
8.
Navigate to the /opt/TempRDM/RDMClientEAR/RDM_JAX-WS_Client/META-INF/wsdl directory, and verify
that you can find the WSDL and XSD files inside it.
9.
Open each file and replace HOSTNAME with user.deploy.host and PORT with user.deploy.port. You can get
user.deploy.host and user.deploy.port from MDM_Fixpack.properties, which you can find from
<RDM_HOME>/backup/<FIXPACK_NUMBER>/properties.
10. Apply step 9 for all WSDL and XSD files under the /opt/TempRDM/RDMClientEAR/RDM_JAX-WS_Client/METAINF/wsdl directory.
11. Navigate to the /opt/TempRDM/RDMClientEAR/RestAPI/WEB-INF/classes directory and locate the
client.properties file inside it.
12. Replace HOSTNAME with user.deploy.host and PORT with user.deploy.port. You can get
user.deploy.host and user.deploy.port from MDM_Fixpack.properties, which you can find from
<RDM_HOME>/backup/<FIXPACK_NUMBER>/properties.
13. Navigate to /opt/TempRDM/RDMClientEAR/META-INF/RDMWSBinding/PolicyTypes/WSSecurity and open
bindings.xml.
14. Replace {xor}MjsyPjsyNjE= with MDM password. This is not a WebSphere Application Server profile password, and
cannot be available in any properties file, so you must enter this value manually.
15. Replace userid=”mdmadmin” with userid=”user.L2.was.admin.user”. You can get user.deploy.host
and user.deploy.port from MDM_Fixpack.properties, which you can find from
<RDM_HOME>/backup/<FIXPACK_NUMBER>/properties.
16. Open a command terminal and go to /opt/TempRDM/RDMClientEAR/RDM_JAX-WS_Client and run the following :
jar -cvf RDM_JAX-WS_Client.jar *
17. Copy /opt/TempRDM/RDMClientEAR/RDM_JAX-WS_Client/RDM_JAX-WS_Client.jar to
/opt/TempRDM/RDMClientEAR.
18. Open a command terminal, navigate to /opt/TempRDM/RDMClientEAR/RestAPI, and run the following command:
jar -cvf RestAPI.war *
19. Copy /opt/TempRDM/RDMClientEAR/RestAPI/RestAPI.war to /opt/TempRDM/RDMClientEAR, then
delete the following folders:
/opt/TempRDM/RDMClientEAR/RestAPI
/opt/TempRDM/RDMClientEAR/RDM_JAX-WS_Client
20. Open a command terminal and navigate to /opt/TempRDM/RDMClientEAR, then run the following command:
jar -cvf RDMClientEAR.ear *
21. Ensure that RDMClientEAR.ear is created under /opt/TempRDM/RDMClientEAR.
22. Open the WebSphere Application Server Administrative Console, then navigate to Applications
All applications.
23. Click Add to deploy the new RDMClientEAR.ear file, then click Next.
24. When asked to provide the location of the RDMClientEAR.ear to deploy, supply the path
/opt/TempRDM/RDMClientEAR/RDMClientEAR.ear and click Next.
25. Select the default installation options and click Next.
26. Change Application name to RDMClientEAR-<MDM-App-Name> , then click Next.
27. Select the check box corresponding to the server or server cluster where you want to deploy the RDMClientEAR-<MDMApp-Name>, select the server or cluster based on your requirements, click Apply, then click Next.
28. Click Next with the default values selected.
29. To finish deploying RDMClientEAR.ear, click Finish, then click Save.
30. Verify your RDMClientEAR-<MDM-App-Name> is deployed under Applications
Static Changes
IMPORTANT: Before modifying the files, make a backup of the existing files.
All applications.
The new files for static changes are located at 2 places
•
<RDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.rdm.fix/staticcontent/com.ibm.mdm.bu
ild.rdm_ui/installer
•
<RDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.rdm.fix/staticcontent/com.ibm.mdm.bu
ild.clientapps/installer
1.
In
<RDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.rdm.fix/staticcontent/com.ibm.mdm.bu
ild.rdm_ui/installer locate the file RDMBE-V11.3.zip and then extract it to the same location.
2.
Locate the BatchExportClient.jar, navigate to <RDM_HOME>/BatchExport and replace this file.
1.
In
<RDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.rdm.fix/staticcontent/com.ibm.mdm.bu
ild.clientapps/installer locate the com.ibm.mdm.batch.framework.zip file and extract it to the same
location.
2.
A /BatchProcessor directory is created where you can find the lib/com.ibm.mdm.batch.framework.jar.
3.
Navigate to <RDM_HOME>/BatchProcessor/lib and replace the file com.ibm.mdm.batch.framework.jar.
Database changes: New files for database changes are located at
<RDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.rdm.fix/database/com.ibm.mdm.build.database
/installer. Extract com.ibm.mdm.db.core.zip at this location only.
There are database updates for DB2 and Oracle:
•
For DB2 you can find the scripts under
<RDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.rdm.fix/database/com.ibm.mdm.build.d
atabase/installer/CoreData/Fixpack/DB2/Standard/ddl , where you will find the SQL script,
Upgradedb_fp1.sql. Open and replace the <SCHEMA> name inside the SQL files.
•
For ORACLE you can find the scripts under
<RDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.rdm.fix/database/com.ibm.mdm.build.d
atabase/installer/CoreData/Fixpack/Oracle/Standard/ddl, where you will find the SQL script
Upgradedb_fp1.sql.
Open a terminal and connect to database. Execute respective SQL files.
Download PDF
Similar pages