Installing the IBM InfoSphere MDM version 11.4 Fix Pack 2 Manually

Size: px

Start display at page:

Download "Installing the IBM InfoSphere MDM version 11.4 Fix Pack 2 Manually"

Muriel Atkinson
5 years ago
Views:

1 Installing the IBM InfoSphere MDM version 11.4 Fix Pack 2 Manually Use this document if you are applying the fix pack manually instead of running the madconfig target Apply_Fixpack. IMPORTANT: Before proceeding make sure you applied fix pack through Installation manager. Once you apply the fix pack on InfoSphere MDM version 11.4, two directories (backup and updates) are created in the <MDM_HOME> directory. 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 there will be a directory and a property file named MDM_FixpackDetails.properties. The following components are changed for InfosSphere MDM version 11.4 Fix Pack 2 1. OSGI related changes to Bundles, CBA, and EBA changes 2. Native Engine Changes redeploying the native.ear file 3. Native WebService EAR Changes redeploying the MDM-web-services-virtual-<MDM-App-Name>.ear 4. Static Changes 5. Broker Changes 6. Inspector User Interface Changes 7. WebReports User Interface Changes 8. Database Changes OSGi related changes to Bundles, CBA, and EBA files: These are the bundle names that have been updated for InfoSphere MDM version 11.4 Fix Pack 2 com.ibm.mdm.server.dwlcommonservices com.ibm.mdm.server.dwlcommonservices.ejb com.ibm.mdm.server.extrules.default com.ibm.mdm.mds.job.manager com.ibm.mdm.server.asi com.ibm.mdm.server.linguistics com.ibm.mdm.server.ws.restful com.ibm.mdm.server.party com.ibm.mdm.server.thirdpartyadapters You can find these bundles and CBAs under in the folder <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/bundles All bundles are appended with the fix pack version. I. Add bundles to WebSphere Application Server Internal bundle repository: 1. Log in to the WebSphere Application Server Administrative Console. 2. Navigate to Environment OSGI bundle repositories Internal bundle repository.

Once the bundles and CBAs are added to the internal bundle repository, you must update the

2 3. Select a bundle; for example "com.ibm.mdm.mds.composite.handler". Repeat step I for all bundles and CBAs. II. Once the bundles and CBAs are added to the internal bundle repository, you must update the latest bundles in Assets by taking the following steps: 1. Navigate to Applications Application Types Assets. 2. Select the Asset named "com.ibm.mdm.hub.server.app-<mdm-app-name>.eba.

3. Click on "Update bundle versions in this application" link on the

View the displayed bundles for this EBA and the version numbers that

By default, bundles will have only one version "11.4.

3 3. Click on "Update bundle versions in this application" link on the right side. 4. View the displayed bundles for this EBA and the version numbers that are currently used for each bundles: 5. View the version. By default, bundles will have only one version "11.4.FP00IF000_ ", which comes with base version of InfoSphere MDM. If you already applied fixpack 1, then this version will be different.

6. You can see 2 version numbers for the bundles which were added in step I. 7. For example, take "com.ibm.mdm.mds.composite.handler", for which you can see 2 versions for this bundle.

4 6. You can see 2 version numbers for the bundles which were added in step I. 7. For example, take "com.ibm.mdm.mds.composite.handler", for which you can see 2 versions for this bundle. If you have applied fixpack 1, then there will be 3 versions for this bundle. 8. You must select latest fix pack version for the bundles. The version number for Fix Pack 2 is "11.4.FP02IF000_201503xx-xxxx" 9. Update the version numbers for all bundles and CBAs that you selected in step I. You can find CBAs at the end. 10. Click the "Preview" button after updating all bundles and CBAs with the latest version of fix pack. 11. Confirm that you can see the differences between the "Deployed Version" and the "New version" for all bundles and CBAs. Make sure under "New Version" you can see "11.4.FP03IF000_201503xx-xxxx" for all the bundles and CBA's which were added in Step I. 12. Once confirmed, go to down and click the "Create" button. 13. Click "Save".

5 III. 1. Navigate to Applications Application Types Business-level applications. 2. Select "MDM-operational-server-EBA-<MDM-App-Name>". 3. Select "com.ibm.mdm.hub.server.app.<mdm-app-name>_0001.eba

6 4. Click "Update to latest deployment..."

7 5. Verify that you can see the preview of all bundles and CBAs with the new fixpack 2 version number, then click "OK". 6. Click the "Next" button on the following two pages without performing any modifications.

8 7. Click "Finish", then click Save". 8. Click "OK", then click Save".

10 Native Engine Changes Redeploying the native.ear file IMPORTANT: Before applying the fix pack for the native engine, you must create backups of the following folders, which will be overwritten by the fix pack: - MDM_INSTALL_HOME/mds/conf - WAS_PROFILE_HOME/InstalledApps/CELL_NAME/MDM-native-APP_NAME.ear/native.war/conf There are two steps to updating the native.ear file: I. Modify the file changes for this fix pack based on the operating system. II. Redeploy the native.ear file. I. There are a number of files that must be modified based on operating system. New files for native engine are located at <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/engine/com.ibm.mdm.build.engine/installer You can find five ZIP files each for a different operating system: com.ibm.mdm.mds-aix64.zip com.ibm.mdm.mds-linux64.zip com.ibm.mdm.mds-sunos64.zip com.ibm.mdm.mds-win64_amd64.zip com.ibm.mdm.mds-zlinux64.zip Extract the ZIP file that corresponds to the operating where InfoSphere MDM is installed. This depend on which Operating system you running this on. For example, if you are running it from Linux enviroment then do the following : back up the contents of the <MDM_HOME>/linux and <MDM_HOME>/mds directories, extract the contents of com.ibm.mdm.mdslinux64.zip, and replace the following files in the <MDM_HOME>/linux and <MDM_HOME>/mds directories. lib/libmad.so conf/mdsbroadcast.xsd NOTE : the same changes applies to other OS, change the <linux> on above example to the first argument and the extracting content refers to 2nd argument below, <YOUR OS> = 1st arguement, 2nd arguement AIX = aix, com.ibm.mdm.mds-aix64.zip Solaris = solaris, com.ibm.mdm.mds-sunos64.zip Windows64 = win64,com.ibm.mdm.mds-win64_amd64.zip

"Submit Action". This will stop "MDM-native-<MDM-App-Name>". 3.

11 II. Reinstall the native.ear file A). 1. Navigate to Applications All applications. 2. Select the checkbox for "MDM-native-<MDM-App-Name>", change the action from "start" to "stop", then click "Submit Action". This will stop "MDM-native-<MDM-App-Name>". 3. Select the checkbox for "MDM-native-<MDM-App-Name>" and click "Remove", which will remove this application from WebSphere Application Server. Click "OK" and then click "Save".

Open a command terminal, then run cd <MDM_HOME>/<YOUR_Operating_System_FOLDER> 4. Make sure ANT is in the path. 5. Verify that native.war and native.

12 B). 1. Navigate to <MDM_HOME>/<YOUR_Operating_System_FOLDER>. In the case of Linux, the value in <YOUR_Operating_System_FOLDER> linux under <MDM_HOME>. In the case of AIX, the value in <YOUR_Operating_System_FOLDER> will be aix under <MDM_HOME>. 2. Locate the build.xml file. 3. Open a command terminal, then run cd <MDM_HOME>/<YOUR_Operating_System_FOLDER> 4. Make sure ANT is in the path. 5. Verify that native.war and native.ear files exist under <MDM_HOME>/InstallableApps, and rename them if they exist. 6. Run "ant -buildfile build.xml". This will invoke target name "all", which is a default target name in this XML file. 7. Verify that a new native.ear file has been created under <MDM_HOME>/InstallableApps. 8. Open the WebSphere Application Server Administrative Console. 9. Navigate to Applications All applications, click "Add" to deploy the new native.ear file, then click Next. 10. Provide the path to the location of the native.ear file that you want to deploy (for example, <MDM_HOME>/InstallableApps/native.ear), then click "Next". 11. Select the default installation options and click "Next". 12. Replace the default "Application name" to MDM-native-<MDM-App-Name>, then click "Next".

13. Specify where you want to deploy native.

select the corresponding check-box, then click the "Apply" next to

Click "Next" with the default values selected. 15.

13 13. Specify where you want to deploy native.ear by selecting the server or cluster based on your requirements, select the corresponding check-box, then click the "Apply" next to the server details, and then click "Next". 14. Click "Next" with the default values selected. 15. Finally, click "Finish" and then click "Save". 16. Verify that your MDM-native-<MDM-App-Name> is deployed under Applications All applications.

15 C). 1. Open a command terminal and run cd <MDM_HOME>/<YOUR_Operating_System_FOLDER>. 2. Copy build-install-config.xml from this location and paste it to <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDMnative-<MDM-App-Name>.ear/native.war. For <WAS_PROFILE_HOME> go forward to step 6. This value is same as USER_INSTALL_ROOT. 3. Open a command terminal and run cd <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-AppName>.ear/native.war.

16 4. Create a property file named install.properties under <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native<MDM-App-Name>.ear/native.war. IMPORTANT: take note of this information you will need it again when you reach part III, step 1 of the Native WebService EAR Changes topic (on page 23). 5. Add below key value pairs in this file. mds.was.profile.home=<user_install_root> mds.ear.install.dir=<app_install_root>/<cell_name>/mdm-native-<mdm-appname>.ear/native.war mds.root.dir=<app_install_root>/<cell_name>/mdm-native-<mdm-app-name>.ear/native.war mds.db.type=<user.db.type> mds.db.host=<user.db.host> mds.db.port=<user.db.port> mds.db.name=<user.db.name> mds.db.dsn=<user.db.name>_<user.instance.identifier> mds.db.user=<user.db.user> mds.db.password=enter DB PASSWORD, this is not available in any property files. You must enter it manually. mds.instance.id=<user.instance.identifier> mds.code.lang.list=<user.code.lang.list.mds> mds.db.auth.native=<user.db.auth.native> mds.db.schema=<user.db.schema> mds.db.service.name=( Leave this with empty value, If Oracle RAC is used then enter RAC service name here.) user.db.ssl.enabled=false user.db.ssl.file.path=none user.db.ssl.password=none mds.db.password.ecd=null dbpwdencrypted=null 6. Enter a value for mds.db.schema if your database type is either DB2 or DB2 for z/os, otherwise leave it empty. If your database type is DB2 or DB2 for z/os, the key/value will be: mds.db.schema=<user.db.schema> ( get user.db.schema from <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties ) If your database type is Oracle or SQLServer, the key/value will be: mds.db.schema= Keys will be common and values will change according to where the InfoSphere MDM instance is installed. You can find values of USER_INSTALL_ROOT and APP_INSTALL_ROOT in the WebSphere Application Server Administrative Console as follows: Open <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. From this file you can get the values of user.db.type, user.db.host, user.db.port etc...

$For example it'll be something like the following: APP_INSTALL_ROOT = ${USER_INSTALL_ROOT}/installedApps USER_INSTALL_ROOT = /opt/ibm/websphere/appserver/profiles/appsrv01 You can find two values for$

17 Replace the place holders in install.properties with the values that exist in <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. Open the WebSphere Application Server Administrative Console and Navigate to Environment WebSphere variables, get the values for APP_INSTALL_ROOT and USER_INSTALL_ROOT. For example it'll be something like the following: APP_INSTALL_ROOT = ${USER_INSTALL_ROOT}/installedApps USER_INSTALL_ROOT = /opt/ibm/websphere/appserver/profiles/appsrv01 You can find two values for USER_INSTALL_ROOT, if it's WebSphere Application Server ND: USER_INSTALL_ROOT = /opt/ibm/websphere/appserver/profiles/appsrv01 USER_INSTALL_ROOT = /opt/ibm/websphere/appserver/profiles/dmgr01 Use the first USER_INSTALL_ROOT to update the value in install.properties. NOTE: you will use the second USER_INSTALL_ROOT in step 9. Now replace the value of USER_INSTALL_ROOT in APP_INSTALL_ROOT. The new values are: APP_INSTALL_ROOT = /opt/ibm/websphere/appserver/profiles/appsrv01/installedapps USER_INSTALL_ROOT = /opt/ibm/websphere/appserver/profiles/appsrv01

18 7. Open a command terminal and go to <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>, then run chmod u+x MDM-native<MDM-App-Name>.ear. 8. Go to <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-App-Name>.ear/native.war/scripts and run chmod 755 madconfig.sh. 9. Open madconfig.env, and replace this with the USER_INSTALL_ROOT value you got in step Make sure ANT is in the path. 11. Go to <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-App-Name>.ear/native.war and check if build-install-config.xml file exists in this location, otherwise copy it from the <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-App-Name>.ear/native.war/scripts folder. 12. Run ant -buildfile build-install-config.xml to invoke target name "install", which is a default target name in this xml file. 13. Ensure that the *.cfg and odbc.ini files have been created under <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDMnative-<MDM-App-Name>.ear/native.war/conf. Native WebService EAR Changes redeploying MDM-web-services-virtual-<MDM-App-Name>.ear IMPORTANT: Before starting this, make a backup of <MDM_HOME>/mds/lib/sdk/ibminitiatews.ear. There is a change in the Native WebService EAR file, so you must uninstall the existing MDM-web-services-virtual-<MDM-AppName>.ear file and then redeploy it using the following steps. : I. Stop and remove the MDM-web-services-virtual-<MDM-App-Name> application. II. Install the MDM-web-services-virtual-<MDM-App-Name>.ear. III. Create an install.properties file for the MDM-web-services-virtual-<MDM-App-Name>.ear. I. Stop and remove the MDM-web-services-virtual-<MDM-App-Name> application. 1. Log in to the WebSphere Application Server Administrative Console. 2. Navigate to Applications All applications. 3. Select the check-box for "MDM-web-services-virtual-<MDM-App-Name>" and change the action from "start" to "stop", then click "Submit Action". This will stop "MDM-web-services-virtual-<MDM-App-Name>". 4. Select the check-box for "MDM-web-services-virtual-<MDM-App-Name>" and press "Remove", which will remove this application from WebSphere Application Server. Click "OK" and "Save". 5. Ensure that "MDM-web-services-virtual-<MDM-App-Name>" is removed from WebSphere Application Server Administrative Console.

II. Install the MDM-web-services-virtual-<MDM-App-Name>.ear. 1. Copy <MDM_HOME>/mds/lib/sdk/ibminitiatews.war to a directory, for example /opt/mdm_temp, and move ibminitiatews.war to this directory.

Run "jar -cvf ibminitiatews.ear ibminitiatews.war. 4. Run "jar -uvf ibminitiatews.ear META-INF/application.xml". 5. Make sure ibminitiatews.ear is created in the /opt/mdm_temp folder. 6.

20 II. Install the MDM-web-services-virtual-<MDM-App-Name>.ear. 1. Copy <MDM_HOME>/mds/lib/sdk/ibminitiatews.war to a directory, for example /opt/mdm_temp, and move ibminitiatews.war to this directory. Create META-INF folder in the new /opt/mdm_temp folder, then copy <MDM_HOME>/mds/lib/sdk/application.xml to the /opt/mdm_temp/meta-inf folder. 2. Open a command terminal and run "cd /opt/mdm_temp". 3. Run "jar -cvf ibminitiatews.ear ibminitiatews.war. 4. Run "jar -uvf ibminitiatews.ear META-INF/application.xml". 5. Make sure ibminitiatews.ear is created in the /opt/mdm_temp folder. 6. Open WebSphere Application Server Administrative Console. 7. Navigate to Applications All applications. 8. Click the "Add" button to deploy the new native.ear file, then click Next. 9. Provide the path to the location of the native.ear file that you want to deploy (for example, /opt/mdm_temp/ibminitiatews.ear), then click "Next". 10. Select the default installation options and click "Next". 11. Change the default "Application name" from "ibminitiatews" to MDM-web-services-virtual-<MDM-App-Name>, then click "Next".

details, then press "Next". 13. Press "Next" with the default values selected. 14.

21 12. Select where you want to deploy MDM-web-services-virtual-<MDM-App-Name>, select the check box associated with the server or cluster based on your requirements, click the "Apply" button next to server details, then press "Next". 13. Press "Next" with the default values selected. 14. Finally, click "Finish" and then Save. 15. Verify your MDM-web-services-virtual-<MDM-App-Name> is deployed under Applications All applications.

22 III. Create an install.properties file for the MDM-web-services-virtual-<MDM-App-Name>.ear 1. Verify that you created install.properties under <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDMnative-<MDM-App-Name>.ear/native.war following the instructions for making native engine changes II --> section C --> step 4 (on page 17). 2. Add some extra key/value parameters to the run target (install_ws_prop), as follow: mds.ws.api.installed.path=<app_install_root>/<cell_name>/mdm-web-services-virtual-<mdmapp-name>.ear/ibminitiatews.war mds.http.port=<user.was.application.http.port> mdm.admin.user=<user.l2.was.admin.user> mdm.admin.password=enter MDM PASSWORD note that this is not a WebSphere Application Server password, nor is it available in any property files; instead, you must enter this value manually. 3. Make sure ANT is in the path 4. Go to <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-App-Name>.ear/native.war, copy the build-install-config.xml and install.properties files from this location to <WAS_PROFILE_HOME>/temp, then navigate to <WAS_PROFILE_HOME>/temp and proceed to step Run "ant -buildfile build-install-config.xml install_ws_prop, which will invoke the target name "install_ws_prop". 6. Ensure that the ibminitiatews.properties file is created under <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-web-services-virtual-<MDM-AppName>.ear/ibminitiatews.war/WEB-INF/classes User Interface Changes Inspector User Interface Changes Important: the following process will redeploy Inspector User Interface, so you must create a backup of the existing Inspector User Interface EAR, which you can find at <MDM_HOME>/InstallableApps/ear/inspector.ear

23 The new files for User Interfaces are located at <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/userinterface/com.ibm.mdm.build.we bapps/installer. You can find inspector.zip file there. Extract that ZIP file in that location only. I. 1. Log in to the WebSphere Application Server Administrative Console. 2. Navigate to Applications All applications. 3. Select the check-box for "inspector-<mdm-app-name>" or "Inspector", change the action from "start" to "stop", then click "Submit Action". This will stop "inspector-<mdm-app-name>" or "Inspector" application. 4. Select the check-box for "inspector-<mdm-app-name>" or "Inspector" and click "Remove", which will remove this application from WebSphere Application Server. Click "OK", then click "Save". 5. Make sure "inspector-<mdm-app-name>" or "Inspector" is removed from the WebSphere Application Server Administrative Console. II. 1. Create a temporary directory "/opt/tempinspector" under this folder. 3. Extract <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/userinterface/com.ibm.mdm.build.we bapps/installer/inspector.ear to the "/opt/tempinspector" folder. 4. Create one more temporary directory named inspector under the "/opt/tempinspector". 5. Extract inspector.war to the "/opt/tempinspector/inspector" folder. 6. Create a directory named "classes" under the "/opt/tempinspector/inspector/web-inf" folder. 7. Create a property file named "inspector.properties" under the "/opt/tempinspector/inspector/webinf/classes" folder. 8. Add the following key/value pairs to "inspector.properties" file: HostName=<user.was.application.host> HostPort=<user.was.application.http.port> UserName=<user.L2.was.admin.user> Password=ENTER MDM PASSWORD note that this is not a WebSphere Application Server password, nor is it available in any property files; instead, you must enter this value manually. UseSSL=<user.use.ssl.inspector> InitContext="5" MaxContext="10" TimeOut="30" KeepAlive="false"

24 9. Open <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. From this file you can get the values of user.was.application.host, user.l2.was.admin.user, user.use.ssl.inspector, and so forth. Replace the place holders in inspector.properties with the values in <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. 10. Verify the Encoding Password value in "inspector.properties" file. 11. Open a command terminal and go to <WAS_HOME>/bin. You can locate the <WAS_HOME> value from key user.l1.was.home from <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. 12. Run PropFilePasswordEncoder.sh or PropFilePasswordEncoder.bat by passing arguments as /opt/tempinspector/inspector/web-inf/classes/inspector.properties and Password. For example, /opt/ibm/websphere/appserver/bin, go to this location in terminal and enter:./propfilepasswordencoder.sh /opt/tempinspector/inspector/webinf/classes/inspector.properties Password 13. Open /opt/tempinspector/inspector/web-inf/classes/inspector.properties and verify the value for Password. It should be in encryption format. 14. Copy /opt/tempinspector/inspector/web-inf/classes/inspector.properties file to <MDM_HOME>/InstallableApps/properties. 15. Delete inspector.war and inspector.ear if it exists under /opt/tempinspector. 16. Open a command terminal and go to /opt/tempinspector/inspector, then run "jar cvf inspector.war". 17. Copy inspector.war from /opt/tempinspector/inspector to /opt/tempinspector. 18. Delete the Inspector folder under /opt/tempinspector. 19. In the command terminal, go to /opt/tempinspector and run "jar -cvf inspector.ear inspector.war". 20. Run "jar -uvf inspector.ear META-INF/application.xml". 21. Run "jar -uvf inspector.ear META-INF/ibmconfig". 22. Make sure inspector.ear is created under /opt/tempinspector. 23. Delete inspector.ear from <MDM_HOME>/InstallableApps/ear if it exists in that folder. 24. Copy /opt/tempinspector/inspector.ear to <MDM_HOME>/InstallableApps/ear. 25. Delete TempInspector folder from /opt. III. 1. Open WebSphere Application Server Administrative Console. 2. Navigate to Servers All servers. 3. Select the Inspector User Interface server; for example, "UIS2". 4. Click the "Ports" link and get the values for "WC_defaulthost" and "WC_defaulthost_secure". 5. Navigate to Environment Virtual hosts. 6. Click "default_host" and then click "HostAliases". 7. Verify the values that you got in step number 4 exist here. If they do, you don't need to do anything.

25 8. If the port number doesn't exist, click "New" and provide the values manually.

IV). 1. Open the WebSphere Application Server Administration Console. 2. Navigate to Servers All servers. 3. Select User Interface server; for example, "UIS2". 4.

ibm.corba.requesttimeout" property. If it's there check the value. 7. If the value is 720, then you don't need to do anything. 8. If "com.ibm.corba.requesttimeout" property doesn't exist, add it with a value of 720, then click "OK" and "Save".

27 IV). 1. Open the WebSphere Application Server Administration Console. 2. Navigate to Servers All servers. 3. Select User Interface server; for example, "UIS2". 4. In right hand side under "Container Settings", locate "Container Services" and expand it. 5. Select "ORB service". Locate "Custom properties" in the right hand side and select it. 6. Search for "com.ibm.corba.requesttimeout" property. If it's there check the value. 7. If the value is 720, then you don't need to do anything. 8. If "com.ibm.corba.requesttimeout" property doesn't exist, add it with a value of 720, then click "OK" and "Save". If your Inspector User Interface is deployed to a single server, this will be enough. If your Inspector User Interface is deployed on a cluster, you must repeat steps 4 through 8 for each member of the cluster.

V). 1. Open WebSphere Application Server Administrative Console. 2. Navigate to Applications All applications. 3. Click "Add" to deploy the new inspector.ear file. 4. Select "Next" button.

When asked for installation options, select the defaults and click "Next". 7. In "Application name", change the default "inspector" to inspector-<mdm-app-name>, then click "Next". 8.

28 V). 1. Open WebSphere Application Server Administrative Console. 2. Navigate to Applications All applications. 3. Click "Add" to deploy the new inspector.ear file. 4. Select "Next" button. You are asked to give location of inspector.ear that you want to deploy. 5. Provide the path (<MDM_HOME>/InstallableApps/inspector.ear) and click "Next". 6. When asked for installation options, select the defaults and click "Next". 7. In "Application name", change the default "inspector" to inspector-<mdm-app-name>, then click "Next". 8. Select where you want to deploy inspector-<mdm-app-name>, select the server or cluster based on your requirements. Select the check box that corresponds to the server you want, click "Apply", and then click "Next" 9. Click "Next" with the default values selected. 10. To finish deploying inspector.ear, click "Finish", then click "Save".

29 11. Verify your inspector-<mdm-app-name> is deployed under Applications All applications. Broker Changes Important: Before applying the fix pack for Broker, create a backup of the files that you will be are modifying. Your operating system determines which files will be modified. New files for native engine are located at <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/brokers/com.ibm.mdm.build.brokers/installer You can find four ZIP files, each for different operating system. com.ibm.mdm.mds.brokers-aix64.zip com.ibm.mdm.mds.brokers-linux64.zip com.ibm.mdm.mds.brokers-sunos64.zip com.ibm.mdm.mds.brokers-win64_amd64.zip Extract the ZIP file appropriate to the operating system where InfoSphere MDM is installed. If InfoSphere MDM is installed on a machine with the AIX operating system, back up the contents of <MDM_HOME>/MessageBrokerSuite directory, extract the com.ibm.mdm.mds.brokers-aix64.zip file, and replace the following files in the <MDM_HOME>/MessageBrokerSuite directory: bin/msgreader bin/msgsender bin/querybroker bin/openssl lib/libmicommon.so lib/libcrypto.so lib/libssl.so lib/libmicommon_routingbroker.so proxy/lib/libmicommon.so proxy/lib/libcrypto.so proxy/lib/libssl.so scripts/build-utils-brokers.xml If InfoSphere MDM is installed on a machine with the Linux operating system, back up the contents of <MDM_HOME>/MessageBrokerSuite directory, extract the com.ibm.mdm.mds.brokers-linux64.zip file, and replace the following files in the <MDM_HOME>/MessageBrokerSuite directory: bin/msgreader bin/msgsender bin/querybroker bin/openssl lib/libmicommon.so

30 lib/libcrypto.so lib/libssl.so lib/libmicommon_routingbroker.so proxy/lib/libmicommon.so proxy/lib/libcrypto.so proxy/lib/libssl.so scripts/build-utils-brokers.xml If InfoSphere MDM is installed on a machine with the Oracle operating system, back up the contents of <MDM_HOME>/MessageBrokerSuite directory, extract the com.ibm.mdm.mds.brokers-sunos64.zip file, and replace the following files in the <MDM_HOME>/MessageBrokerSuite directory: bin/msgreader bin/msgsender bin/querybroker bin/openssl lib/libmicommon.so lib/libcrypto.so lib/libssl.so lib/libmicommon_routingbroker.so proxy/lib/libmicommon.so proxy/lib/libcrypto.so proxy/lib/libssl.so scripts/build-utils-brokers.xml If InfoSphere MDM is installed on a machine with the Windows 64 operating system, back up the contents of <MDM_HOME>/MessageBrokerSuite directory, extract the com.ibm.mdm.mds.brokers-win64_amd64.zip file, and replace all of the files under bin, lib, proxy/lib folders and the file build-utils-brokers.xml under the scripts folder.. Static Changes 1. New files for static changes are located at <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/staticcontent/com.ibm.mdm.build.clientapps /installer 2. Extract the zip file com.ibm.mdm.batch.framework.jar in the same location. 3. There is a single file change named com.ibm.mdm.batch.framework.jar under BatchProcessor/lib. 4. First, create a backup of <MDM_HOME>/BatchProcessor/lib/com.ibm.mdm.batch.framework.jar before replacing the new file.

31 5. Copy <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/staticcontent/com.ibm.mdm.build.clientapps /installer/batchprocessor/lib/com.ibm.mdm.batch.framework.jar to <MDM_HOME>/BatchProcessor/lib Database changes The new files for database changes are located at <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/database/com.ibm.mdm.build.dat abase/installer. 1. Extract com.ibm.mdm.db.domain.zip at this location only. 2. Locate the update corresponding with your database. There are database updates for DB2, Oracle, and z/os: 3. For DB2, you can find the scripts under <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/database/com.ibm.mdm.build.database/installer/Fixpack/DB2/Standard/ddl. There you will find two SQL scripts. Open and replace <SCHEMA> name inside the SQL files. For DB2ZOS, you can find the scripts under <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/database/com.ibm.mdm.build.database/installer/Fixpack/DB2/ZOS/ddl. There you will find two SQL scripts. Open and replace <USER ACCOUNT> name inside the SQL files. For ORACLE, you can find the scripts under <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/database/com.ibm.mdm.build.database/installer/Fixpack/Oracle/Standard/ddl, where you can locate two SQL scripts. Open a terminal and connect to database. Execute Upgradedb_fp1.sql sql file.

Installing the InfoSphere MDM Standard and Advanced Edition version 11.0 Fix Pack 3 Manually

Installing the InfoSphere MDM Standard and Advanced Edition version 10 Fix Pack 3 Manually This document helps you in applying the fix pack manually instead of running the madconfig target Apply_Fixpack.