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

Transcription

1 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. IMPORTANT: Before proceeding, ensure that you applied the fix pack using the IBM Installation Manager. Once you apply the InfoSphere MDM version 10 Fix Pack 3, two directories, /backup and /updates, are created under <MDM_HOME>. The /updates directory contains all the details regarding the fix pack such as templates and files needed for this fix pack. The /backup directory contains a directory with fix pack number; for example if you apply Fix Pack 03, then you will find the both the directory /03000 and a properties file named MDM_FixpackDetails.properties. The following components are changed for InfoSphere MDM Standard and Advanced Edition version 10 Fix Pack 3: OSGi changes (Bundles, CBA and EBA changes) Native Engine Changes and redeploying the native.ear Native WebService EAR Changes and redeploying the MDM-web-services-virtual-<MDM-App-Name>.ear Static Changes Broker Changes Inspector User Interface Changes Web Reports User Interface Changes EnterpriseViewer User Interface Changes Database changes OSGI changes ( Bundles, CBA and EBA changes These are the bundles names that must be updated for the InfoSphere MDM Standard and Advanced Edition version 10 Fix Pack 3: com.ibm.mdm.server.product com.ibm.mdm.server.dwlcommonservices com.ibm.mdm.server.dwlcommonservices.ejb com.ibm.mdm.mds.engine com.ibm.mdm.mds.history.logic com.ibm.mdm.mds.messages com.ibm.mdm.server.hybrid.api com.ibm.mdm.server.hybrid com.ibm.mdm.server.hybrid.handler com.ibm.mdm.server.extrules.hybrid com.ibm.mdm.server.party com.ibm.mdm.server.domains.referencemodels com.ibm.mdm.mds.event.manager com.ibm.mdm.mds.queue.manager com.ibm.mdm.mds.queue.logic com.ibm.mdm.mds.queue.work.manager com.ibm.mdm.server.extrules.common com.ibm.mdm.server.extrules.default com.ibm.mdm.mds.relationship.logic com.ibm.mdm.server.pme.integration com.ibm.mdm.server.domains.resources.schema

2 com.ibm.mdm.mds.relationship.service com.ibm.mdm.mds.job.manager com.ibm.mdm.mds.composite.handler com.ibm.mdm.mds.metadata com.ibm.mdm.server.ots com.ibm.mdm.server.coreutilities com.ibm.mdm.server.dwlbizservices com.ibm.mdm.server.adminservices com.ibm.mdm.server.crossdomainservices com.ibm.mdm.server.asi com.ibm.mdm.server.transformation com.ibm.mdm.server.thirdpartyadapters com.ibm.mdm.mds.pme.core com.ibm.mdm.mds.pme.api com.ibm.mdm.server.linguistics com.ibm.mdm.server.resources.schema Additionally, there are three CBA files that must be be updated: com.ibm.mdm.mds.jni.app com.ibm.mdm.mds.api.app com.ibm.mdm.thirdparty.cba You can locate these bundles and CBA files under <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/bundles. All bundles are appended with fix pack version. I. Stage one: Add bundles to WebSphere Application Server Internal bundle repository Log in to the WebSphere Application Server Administrative Console. Navigate to Environment OSGI bundle repositories Internal bundle repository, then click New. Click Browse to select a bundle, for example com.ibm.mdm.mds.composite.handler, then click OK.

3 Repeat steps 2 and 3 for all bundles and CBA files. II. Stage Two: Once bundles and CBA files are added to Internal bundle repository, update latest bundles in Assets. Navigate to Applications Application Types Assets. Select the asset named com.ibm.mdm.hub.server.app-<mdm-app-name>.eba. Click Update bundle versions in this application link to display all of the bundles for this EBA, as well as the version numbers that are currently used for each bundle.

4 By default, bundles will have only one version, 10.FP00IF000_ , which comes with base version of InfoSphere MDM. You will see two version numbers for the bundles that you added in stage I; for example, take com.ibm.mdm.mds.composite.handler, you can see two version for this bundle. You must select the latest fix pack version. The version number for InfoSphere MDM Standard and Advanced Edition version 10 Fix Pack 3 is 10.FP03IF000_2015XXXX-xxxx Update version numbers for all bundles and CBA files that you added in stage I. You can find CBA files at the end. After updating all bundles and CBA files with the latest version of the fix pack, click Preview. Verify that you can see the difference between the Deployed Version and the New Version for all bundles and CBA files. Verify, under New Version, that you can see 10.FP03IF000_2015XXXX-xxxx for all the bundles and CBA files added in stage I. 10. Once you have confirmed this, click Create, and then click Save.

5 III. Stage three: update deployment: Navigate to Applications Application Types Business-level applications. Select MDM-operational-server-EBA-<MDM-App-Name>. Select com.ibm.mdm.hub.server.app.<mdm-app-name>_000eba. Click Update to latest deployment.

6 Verify that you can see the preview of all bundles and CBA files with the new version number, then click OK. 6. Click Next on this page and on the next page without doing any modifications. 7. Click Finish, then click Save.

7 8. Click OK, then click Save.

8 Native engine changes and redeploying the native.ear IMPORTANT: Before applying the fix pack for the native engine, 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 main stages in updating native.ear file: I. Modify the file changes which are there for this fix pack based on the operating system. II. Redeploy the native.ear file. I. Stage one: Modify the files based on operating system Locate the new files for native engine are located at <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/engine/com.ibm.mdm.buil d.engine/installer. You can find 5 ZIP files each for different operating system: com.ibm.mdm.mds-aix6zip com.ibm.mdm.mds-linux6zip com.ibm.mdm.mds-sunos6zip com.ibm.mdm.mds-win64_amd6zip com.ibm.mdm.mds-win3zip com.ibm.mdm.mds-zlinux6zip Extract the ZIP file that corresponds to your operating system where the InfoSphere MDM application is installed. a. If your operating system is AIX, the files you must back up and replace can be found in the following location: <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/engine/com.ibm.m dm.build.engine/installer. You must replace these files in the locations <MDM_HOME>/aix and <MDM_HOME>/mds, which you can find by extracting the com.ibm.mdm.mds-aix6zip file: bin/openssl lib/libmad.so sql/maddbx.dbp bin/mpxconv lib/sdk/madappsvcs.ear lib/sdk/ibminitiatews.war lib/sdk/madapi.jar lib/sdk/madapi-nodeps.jar lib/madapi.jar lib/com.ibm.mdm.mds.common.jar b. If your operating system is Linux, the files you must back up and replace can be found in the following location: <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/engine/com.ibm.m dm.build.engine/installer. You must replace these files in the locations <MDM_HOME>/linux and <MDM_HOME>/mds, which you can find by extracting the com.ibm.mdm.mds-linux6zip file: bin/openssl lib/libmad.so sql/maddbx.dbp bin/mpxconv lib/sdk/madappsvcs.ear lib/sdk/ibminitiatews.war lib/sdk/madapi.jar lib/sdk/madapi-nodeps.jar lib/madapi.jar lib/com.ibm.mdm.mds.common.jar

9 c. If your operating system is Solaris, the files you must back up and replace can be found in the following location: <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/engine/com.ibm.m dm.build.engine/installer. You must replace these files in the locations <MDM_HOME>/solaris and <MDM_HOME>/mds, which you can find by extracting the com.ibm.mdm.mds-sunos6zip file: bin/openssl lib/libmad.so sql/maddbx.dbp bin/mpxconv lib/sdk/madappsvcs.ear lib/sdk/ibminitiatews.war lib/sdk/madapi.jar lib/sdk/madapi-nodeps.jar lib/madapi.jar lib/com.ibm.mdm.mds.common.jar d. If your operating system Windows 64, the files you must back up and replace can be found in the following location: <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/engine/com.ibm.m dm.build.engine/installer. You must replace these files in the locations <MDM_HOME>/win64 and <MDM_HOME>/mds, which you can find by extracting the com.ibm.mdm.mds-win64_amd6zip file: bin/libeay3dll bin/mad.dll bin/openssl.exe bin/ssleay3dll sql/maddbx.dbp bin/mpxconv.exe lib/sdk/madappsvcs.ear lib/sdk/ibminitiatews.war lib/sdk/madapi.jar lib/sdk/madapi-nodeps.jar lib/madapi.jar lib/com.ibm.mdm.mds.common.jar e. If your operating system is Windows 32, the files you must back up and replace can be found in the following location: <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/engine/com.ibm.m dm.build.engine/installer. You must replace these files in the locations <MDM_HOME>/win32 and <MDM_HOME>/mds, which you can find by extracting the com.ibm.mdm.mds-win3zip file: bin/libeay3dll bin/mad.dll bin/openssl.exe bin/ssleay3dll sql/maddbx.dbp bin/mpxconv.exe lib/sdk/madappsvcs.ear lib/sdk/ibminitiatews.war lib/sdk/madapi.jar lib/sdk/madapi-nodeps.jar lib/madapi.jar lib/com.ibm.mdm.mds.common.jar

10 f. II. If your operating system is ZLinux, the files you must back up and replace can be found in the following location: <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/engine/com.ibm.m dm.build.engine/installer. You must replace these files in the <MDM_HOME>/zlinux and <MDM_HOME>/mds, which you can find by extracting the com.ibm.mdm.mds-zlinux6zip file: bin/openssl lib/libmad.so sql/maddbx.dbp bin/mpxconv lib/sdk/madappsvcs.ear lib/sdk/ibminitiatews.war lib/sdk/madapi.jar lib/sdk/madapi-nodeps.jar lib/madapi.jar lib/com.ibm.mdm.mds.common.jar Stage two: redeploy the native.ear A). First steps for redeploying the native.ear file Navigate to Applications All applications. Select the check box for MDM-native-<MDM-App-Name> and change the action from start to stop and click Submit Action to stop MDM-native-<MDM-App-Name>. Select the check box for MDM-native-<MDM-App-Name> and click Remove, then click OK and Save.

11 B). Second steps for redeploying the native.ear file Navigate to <MDM_HOME>/<YOUR_Operating_System_FOLDER>. a. In the case of Linux, the value in <YOUR_Operating_System_FOLDER> will be Linux under <MDM_HOME>. b. In the case of AIX, the value in <YOUR_Operating_System_FOLDER> value will be AIX under <MDM_HOME>. You can find the build.xml file by opening a command terminal and running the following command: cd <MDM_HOME>/<YOUR_Operating_System_FOLDER> Make sure that ant is in the path. Verify that the native.war and native.ear files exist under <MDM_HOME>/InstallableApps and rename them if they exist. Run the command ant -buildfile build.xml to invoke target name all that is the default target name in this XML file. A new native.ear file is created under <MDM_HOME>/InstallableApps. Open the WebSphere Application Server Administrative Console and navigate to Applications All applications. Click Add to deploy the new native.ear file.

12 Click Next. When asked to give location of native.ear that you want to deploy, provide the path <MDM_HOME>/InstallableApps/native.ear and click Next. When asked installation options, select the defaults and click Next. Change the Application name by from native to MDM-native-<MDM-App-Name>, then click Next. Specify the location where you want to deploy native.ear by selecting the server or cluster based on your requirements. Locate and select the check box to map the modules to the server, then click Next. Select the check box and click Apply next to server details, then click Next. Click Next with the default values selected. To finish deploying the native.ear, click Finish, then click Save. Verify your MDM-native-<MDM-App-Name> is deployed under Applications All applications.

13

14 C). Third steps for redeploying the native.ear file Open a command terminal and run the command cd <MDM_HOME>/<YOUR_Operating_System_FOLDER> Copy build-install-config.xml from this location and paste it to <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-AppName>.ear/native.war. For <WAS_PROFILE_HOME> see step This value is same as USER_INSTALL_ROOT. Open a command terminal and run the command cd <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-AppName>.ear/native.war Create a properties file named install.properties under <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-AppName>.ear/native.war, then add the following 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>

15 mds.db.password=enter DB PASSWORD (which isn t available in any property files) 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= Supply the value for mds.db.schema if your database type is either DB2 or DB2ZOS, otherwise leave it as empty. For example if your database type is DB2 or DB2ZOS, then the key/value will be as follows: mds.db.schema=<user.db.schema> You can get the user.db.schema from <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. For example if your database is Oracle or SQLServer, the key/value will be as follows: mds.db.schema= Leave mds.db.service.name as empty, in case if you are using Oracle RAC then enter the value of Oracle RAC service name. Keys will be common and values will change according to MDM instance where it's installed. You can find values of USER_INSTALL_ROOT and APP_INSTALL_ROOT from the WebSphere Application Server Administrative Console as mentioned in step Open <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties where you can get the values of user.db.type, user.db.host, user.db.port, and so forth. Replace the place holders in install.properties with the values in <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. 7. Open the WebSphere Application Server Administrative Console and navigate to Environment WebSphere variables, and determine the values for APP_INSTALL_ROOT, USER_INSTALL_ROOT. For example it'll be something like APP_INSTALL_ROOT = ${USER_INSTALL_ROOT}/installedApps USER_INSTALL_ROOT = /opt/ibm/websphere/appserver/profiles/appsrv01 8. Locate the 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 value in install.properties. You can use the second USER_INSTALL_ROOT in step Now replace the value of USER_INSTALL_ROOT in APP_INSTALL_ROOT, new values are as follows: APP_INSTALL_ROOT = /opt/ibm/websphere/appserver/profiles/appsrv01/installedapps USER_INSTALL_ROOT = /opt/ibm/websphere/appserver/profiles/appsrv01

16 10. Open a command terminal, navigate to <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>, then run the following command: chmod u+x MDM-native-<MDM-App-Name>.ear 1 Navigate to <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-AppName>.ear/native.war/scripts and run the following command: run chmod 755 madconfig.sh 1 Open madconfig.env, where you can and replace this with USER_INSTALL_ROOT, which you can get from step number 7. 1 Ensure that ant is in the path. 1 Navigate to <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-AppName>.ear/native.war and verify that the build-install-config.xml file exists in this location. If it does not, copy it from the <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-AppName>.ear/native.war/scripts directory. 1 Run the command ant -buildfile build-install-config.xml to invoke the target name install, which is a default target name in this XML file. 16. Verify that the *.cfg and odbc.ini files are created under <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-AppName>.ear/native.war/conf. Native WebService EAR changes and redeploying the MDM-web-services-virtual-<MDM-App-Name>.ear IMPORTANT: Before starting this procedure, back up the existing <MDM_HOME>/mds/lib/sdk/ibminitiatews.ear. This fix pack contains changes to the Native WebService EAR, so you must uninstall the existing MDM-web-services-virtual<MDM-App-Name>.ear and then redeploy it in a two stage process:

17 I. II. I. Uninstall the MDM-web-services-virtual-<MDM-App-Name>.ear. Re-install the MDM-web-services-virtual-<MDM-App-Name>.ear. Stage one: Uninstall the MDM-web-services-virtual-<MDM-App-Name>.ear. Log into the WebSphere Application Server Administrative Console. Navigate to Applications All applications. Select the check box for MDM-web-services-virtual-<MDM-App-Name>, change the action from start to stop, then click Submit Action to stop MDM-web-services-virtual-<MDM-App-Name>. Select the check box for MDM-web-services-virtual-<MDM-App-Name>, click Remove, then click OK and then Save. Verify that MDM-web-services-virtual-<MDM-App-Name> has been removed from the WebSphere Application Server Administrative Console.

18 II. Stage two: Re-install the MDM-web-services-virtual-<MDM-App-Name>.ear Copy <MDM_HOME>/mds/lib/sdk/ibminitiatews.war to a directory, for example /opt/mdm_temp, and move ibminitiatews.war to this directory. Create a /META-INF directory in the new directory, for example /opt/mdm_temp/meta-inf. Copy <MDM_HOME>/mds/lib/sdk/application.xml to the new temporary directory (/opt/mdm_temp/metainf). Open a command terminal and run the following command: cd /opt/mdm_temp Run the command jar -cvf ibminitiatews.ear ibminitiatews.war. Run the command jar -uvf ibminitiatews.ear META-INF/application.xml. Ensure that ibminitiatews.ear is created under /opt/mdm_temp. Open WebSphere Application Server Administrative Console and navigate to Applications All applications. Click Add to deploy the new native.ear file, then click Next.

19 10. When asked to give location of native.ear which you want to deploy, provide the path /opt/mdm_temp/ibminitiatews.ear, then click Next. 1 When asked for installation options, select the defaults and click Next. 1 Change the default Application name to MDM-web-services-virtual-<MDM-App-Name>, then click Next. 1 Specify where you want to deploy MDM-web-services-virtual-<MDM-App-Name> and select the server or cluster based on your requirements. Select the corresponding check box, click Apply, then click Next. 17. Click Next with default values. 18. To finish deploying the native.ear, click Finish, then click Save. 19. Verify that MDM-web-services-virtual-<MDM-App-Name> is deployed under Applications All applications.

20 III. Optional additional steps You have already created install.properties under <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDMnative-<MDM-App-Name>.ear/native.war: see the native engine changes stage II section C step 4 on page 16. You can add some extra key/value parameters to run the target install_ws_prop. Here are the new keys: mds.ws.api.installed.path=<app_install_root>/<cell_name>/mdm-web-services-virtual<mdm-app-name>.ear/ibminitiatews.war mds.http.port=<user.was.application.http.port> mdm.admin.user=<user.lwas.admin.user> mdm.admin.password=enter MDM PASSWORD (This is not available in any property files, and is not a WebSphere Application Server password, so you must enter this value manually). Make sure ant is in the path. Navigate to <WAS_PROFILE_HOME>/installedApps/<CELL_NAME>/MDM-native-<MDM-AppName>.ear/native.war, then copy build-install-config.xml and install.properties from this location to <WAS_PROFILE_HOME>/temp. Navigate to <WAS_PROFILE_HOME>/temp and run the following ant target to invoke the target name install_ws_prop: ant -buildfile build-install-config.xml install_ws_prop Verify that 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: This procedure will redeploy Inspector UI, so before starting, it is strongly recommended that you make a backup of the existing Inspector UI EAR, which you can find at <MDM_HOME>/InstallableApps/ear/inspector.ear. New files for User Interfaces are located at <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/userinterface/com.ibm.mdm.buil d.webapps/installer. You can find inspector.zip inside it. Extract this ZIP file in that location only.

21 I. II Stage one: Log in to the WebSphere Application Server Administrative Console. Navigate to Applications All applications. Select the check box for inspector-<mdm-app-name> or Inspector and change the action from start to stop and click Submit Action to stop inspector-<mdm-app-name> or Inspector application.. Select the check box for inspector-<mdm-app-name> or Inspector and press Remove, then click OK, then click Save. Make sure inspector-<mdm-app-name> or Inspector is removed from WebSphere Application Server Administrative Console. Stage two: Create a temporary directory /opt/tempinspector under this folder. Extract <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/userinterface/com.ibm.m dm.build.webapps/installer/inspector.ear to /opt/tempinspector directory. Create one more temporary directory under "/opt/tempinspector" folder named "inspector". Extract inspector.war to "/opt/tempinspector/inspector" folder. Create a directory named "classes" under "/opt/tempinspector/inspector/web-inf" folder. Create a property file named "inspector.properties" under "/opt/tempinspector/inspector/web-inf/classes" folder. Add below key/value pairs to "inspector.properties" file. HostName=<user.was.application.host> HostPort=<user.was.application.http.port> UserName=<user.Lwas.admin.user> Password=ENTER MDM PASSWORD (which is not available in any property files, nor is it a WebSphere Application Server password, so you must to enter this value manually). UseSSL=false InitContext="5" MaxContext="10" TimeOut="30" KeepAlive="false" Open <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. From this file you can get the values of user.was.application.host, user.lwas.admin.user, user.use.ssl.inspector, and so forth. Replace the place holders in inspector.properties with the values which exists in <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. Locate the Encoding Password value in inspector.properties file. Open a command terminal and navigate to <WAS_HOME>/bin, where you can get <WAS_HOME> value from key user.lwas.home from <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. 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:./propfilepasswordencoder.sh /opt/tempinspector/inspector/webinf/classes/inspector.properties Password Open /opt/tempinspector/inspector/web-inf/classes/inspector.properties and verify the value for Password; it should be in encryption format. Copy /opt/tempinspector/inspector/web-inf/classes/inspector.properties file to <MDM_HOME>/InstallableApps/properties. Delete inspector.war and inspector.ear if they exist in the /opt/tempinspector directory. Open a command terminal, navigate to /opt/tempinspector/inspector, and then run the command jar cvf inspector.war. Copy inspector.war from /opt/tempinspector/inspector to /opt/tempinspector. Delete the /inspector directory under the /opt/tempinspector directory. In a command terminal, navigate to /opt/tempinspector and run the following commands in sequence:

22 III. 6. jar -cvf inspector.ear inspector.war jar -uvf inspector.ear META-INF/application.xml jar -uvf inspector.ear META-INF/ibmconfig Ensure that inspector.ear is created under /opt/tempinspector. Delete inspector.ear from <MDM_HOME>/InstallableApps/ear, if it exists there. Copy /opt/tempinspector/inspector.ear to <MDM_HOME>/InstallableApps/ear. Delete the /TempInspector directory from the /opt directory. Stage three: Open WebSphere Application Server Administrative Console and navigate to Servers All servers. Under You can administer the following resources, in the Name column, locate click the user interface server; in the example screenshot, it is UIS Click the Ports link and get the values for WC_defaulthost and WC_defaulthost_secure. Navigate to Environment Virtual hosts. Click default_host, then click HostAliases and verify that the value that you got in step 3 exists here. If it is there, you don't need to do anything. If the port number does not exist, click New and provide the values.

23

24 IV. Stage four: 6. Open the WebSphere Application Server Administrative Console and navigate to Servers All servers. Select the User Interface server (in the example screen shot, this is UIS2). Under Container Settings, locate and expand Container Services. Click ORB service, then locate and click Custom properties. Search for the com.ibm.corba.requesttimeout property, and verify that the value is 720. If the value is 720, take no further action. If it is not, proceed to step 6. If the com.ibm.corba.requesttimeout property doesn't exist, add it with a value of 720, click OK and then click Save. IMPORTANT: If your Inspector User Interface is deployed to a single server, this will be enough. If your Inspector User Interface is deployed to a cluster, you must repeat these steps for each member of the cluster.

25 V. Stage five: Open the WebSphere Application Server Administrative Console and navigate to Applications All Applications. Click Add to deploy the new inspector.ear file, then click Next. Provide the path (<MDM_HOME>/InstallableApps/inspector.ear) to the location of the inspector.ear that you want to deploy, then click Next.

26 When asked for the installation options, select the defaults, and click Next. Change the default inspector in Application name to inspector-<mdm-app-name>, then click Next. Select where you want to deploy inspector-<mdm-app-name>, select the server or cluster based on your requirements, locate and select the check box associated with the server, click Apply, then click Next. Click Next with the default values selected. To complete deploying the inspector.ear, click Finish and then click Save. Verify that inspector-<mdm-app-name> is deployed under Applications All applications. Web Reports User Interface Changes IMPORTANT: This action will redeploy Web Reports UI; before starting this procedure, make a backup of the existing Web Reports UI EAR, which you can find at <MDM_HOME>/InstallableApps/ear/webreports.ear. New files for User Interfaces are located at <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/userinterface/com.ibm.mdm.buil d.webapps/installer. You can find webreports.zip in this location. Extract this ZIP file in that location only. I. Stage one: II. Log in to the WebSphere Application Server Administrative Console and navigate to Applications All applications. Select the check box for webreports-<mdm-app-name> or Webreports and change the action from start to stop and click Submit Action to stop webreports-<mdm-app-name> or Webreports application.. Select the check box for webreports-<mdm-app-name> or Webreports and click Remove, click OK and then click Save. Verify that webreports-<mdm-app-name> or Webreports is removed from WebSphere Application Server Administrative Console. Stage two: Create a temporary directory /opt/tempwebreports under this folder. Extract <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/userinterface/com.ibm.m dm.build.webapps/installer/webreports.ear to /opt/tempwebreports directory. Create one more temporary directories under /opt/tempwebreports folder named /webreports. Extract webreports.war to the /opt/tempwebreports/webreports directory. Create a directory named /classes under /opt/tempwebreports/webreports/web-inf folder. Create a properties file named webreports.properties under /opt/tempwebreports/webreports/webinf/classes directory. Add the following key/value pairs to the webreports.properties file: HostName=<user.was.application.host> HostPort=<user.was.application.http.port> UserName=<user.Lwas.admin.user> Password=ENTER MDM PASSWORD (this is not a WebSphere Application Server password; it is not available in any properties file; you must enter this value manually) MaxContext="15" TimeOut="60" jdbc.classname=this value will change based on database, which you will find in the immediately following section; use that value here. jdbc.servername=<user.db.host> jdbc.portnumber=<user.db.port>

27 jdbc.databasename=<user.db.name> jdbc.user=<user.db.user> jdbc.password= ENTER Database PASSWORD (this is not a WebSphere Application Server password; it is not available in any properties file; you must enter this value manually) UseSSL=false If your database type is DB2 or DB2ZOS, add this key/value pair to the webreports.properties file: jdbc.alternateid=< user.db.schema> (needed if the database user and schema are different.) If your database type is ORACLE, add this key/value pair to the the webreports.properties file: jdbc.wireprotocolmode="2" jdbc.servicename= (used if Oracle service is configured; ignore this if the SID value exists) jdbc.sid=<user.db.name> If database type is DB2, then use jdbc.classname=com.ibm.mdm.jdbc.db2datasource If database type is DB2ZOS, then use jdbc.classname=com.ibm.mdm.jdbc.db2datasource If database type is ORACLE, then use jdbc.classname=com.ibm.mdm.jdbc.oracledatasource If database type is MSSQLU, then use jdbc.classname=com.ibm.mdm.jdbc.sqlserverdatasource 8. Open <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties, where you can locate the values of user.was.application.host, user.lwas.admin.user, user.use.ssl.webreports, and so forth. Replace the placeholders in webreports.properties with the values that exists in <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. 9. Verify the Encoding Password value in "webreports.properties" file by opening a command terminal and navigating to <WAS_HOME>/bin, where you can get <WAS_HOME> value from key user.lwas.home from <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. 10. Run the command PropFilePasswordEncoder.sh or PropFilePasswordEncoder.bat by passing arguments as /opt/tempwebreports/webreports/web-inf/classes/webreports.properties and Password. For example, /opt/ibm/websphere/appserver/bin, go to the following locations in a command terminal:./propfilepasswordencoder.sh /opt/tempwebreports/webreports/webinf/classes/webreports.properties Password./PropFilePasswordEncoder.sh /opt/tempwebreports/webreports/webinf/classes/webreports.properties jdbc.password 1 Open /opt/tempwebreports/webreports/web-inf/classes/webreports.properties and verify the values for Password and jdbc.password. It should be in encryption format. 1 Copy the /opt/tempwebreports/webreports/web-inf/classes/webreports.properties file to <MDM_HOME>/InstallableApps/properties. 16. Delete webreports.war and webreports.ear if they exist in /opt/tempwebreports. 17. Open a command terminal and go to /opt/tempwebreports/webreports and run the command jar cvf webreports.war. 18. Copy webreports.war from /opt/tempwebreports/webreports to /opt/tempwebreports. 19. Delete the /webreports directory under /opt/tempwebreports. 20. In a command terminal navigate /opt/tempwebreports and run the following commands in this order: jar -cvf webreports.ear webreports.war jar -uvf webreports.ear META-INF/application.xml jar -uvf webreports.ear META-INF/ibmconfig 2 Verify that webreports.ear is created under /opt/tempwebreports. 2 Delete webreports.ear from <MDM_HOME>/InstallableApps/ear, if it exists. 2 Copy /opt/tempwebreports/webreports.ear to <MDM_HOME>/InstallableApps/ear. 2 Delete the /TempWebreports directory from /opt. III. Stage three:

28 6. IV. Open the WebSphere Application Server Administrative Console and navigate to Servers All Servers. Select the appropriate User Interface server. Click the Ports link and get the values for WC_defaulthost and WC_defaulthost_secure. Navigate to Environment Virtual hosts. Click default_host and then select HostAliases. Verify that the values that you got in step 3 exist here. a. If the values are present, you don't need to do anything, and you can proceed to the stage IV. b. If the port number values do not appear, click New and provide the values. Stage four: Open the WebSphere Application Server Administrative Console and navigate to Servers All Servers. Select the appropriate User Interface server. Locate and expand Container Services. Select ORB service, then locate and select Custom properties. Search for the com.ibm.corba.requesttimeout" property. a. If the value is present and it is 720, proceed to stave V. b. If the com.ibm.corba.requesttimeout property is not present, add it with a value of 720, click OK, and then click Save. Note: if your Web Reports User Interface is deployed to a single server, no further action is required. However, if it is deployed on a cluster, you need to repeat these steps for each member of the cluster. V. Stage five: Open the WebSphere Application Server Administrative Console and navigate to Applications All Applications. Click Add to deploy the new webreports.ear file, then click Next. When asked to provide the location of the webreports.ear that you want to deploy, enter <MDM_HOME>/InstallableApps/webreports.ear, then click Next. 6. When asked for the installation options, select the defaults and click Next. In Application name, replace the default webreports with webreports-<mdm-app-name>, then click Next. Determine where you want to deploy webreports-<mdm-app-name>, select the appropriate server or server cluster based on your requirements, select the corresponding check box, and click Apply, then click Next. Click Next with the default values selected. To complete deploying the webreports.ear, click Finish, then click Save. Verify that your webreports-<mdm-app-name> is deployed under Applications All Applications. Enterprise Viewer User Interface Changes IMPORTANT: This will redeploy the Enterprise Viewer UI, so before you start this procedure, make a backup of the existing Enterprise Viewer UI EAR, which you can find at <MDM_HOME>/InstallableApps/ear/viewer.ear. New files for User Interfaces are located at <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/userinterface/com.ibm.mdm.buil d.webapps/installer. You can find viewer.zip inside it. Extract this zip file in that location only. I. Stage one: Log into the WebSphere Application Server Administrative Console and navigate to Applications All applications. Select the check box for enterpriseviewer-<mdm-app-name> or enterpriseviewer and change the action from start to stop and click Submit Action. This will stop the enterpriseviewer-<mdm-app-name> or enterpriseviewer application..

29 II. Select the check box for enterpriseviewer-<mdm-app-name> or enterpriseviewer and click Remove, then click OK, then click Save. Verify that enterpriseviewer-<mdm-app-name> or enterpriseviewer is removed from the WebSphere Application Server Administrative Console. Stage two: Create a temporary directory /opt/tempviewer under this folder. Extract <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/userinterface/com.ibm.m dm.build.webapps/installer/viewer.ear to the /opt/tempviewer directory. Create one more temporary directory under /opt/tempviewer folder named /viewer. Extract the viewer.war file to the /opt/tempviewer/viewer folder. Create a directory named /classes under /opt/tempviewer/viewer/web-inf folder. Create a property file named ContextManager.prop under /opt/tempviewer/viewer/web-inf/classes folder. Add below key and value pairs to ContextManager.prop file: HostGroupName="server1 serverhostname=<user.was.application.host> serverhostport=<user.was.application.http.port> serverusrname=<user.lwas.admin.user> serverusrpass= ENTER MDM PASSWORD (which is not a WebSphere Application Server password and is not available in any properties file; you must enter this value manually) serverinitcontext="1" servermaxcontext="10" servertimeout="30" serverusessl=false debug.dodebug="false Open <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties, where you can locate the values for user.was.application.host, user.lwas.admin.user, et cetera. Replace the place holders in inspector.properties with the values which exists in <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. Locate the Encoding Password value in the ContextManager.prop file. Open a command terminal and go to <WAS_HOME>/bin and locate the <WAS_HOME> value from key user.lwas.home from <MDM_HOME>/backup/<FIXPACK_NUMBER>/properties/MDM_Fixpack.properties. Run PropFilePasswordEncoder.sh or PropFilePasswordEncoder.bat by passing arguments as /opt/tempviewer/viewer/web-inf/classes/contextmanager.prop and serverusrpass. For example, you could navigate to /opt/ibm/websphere/appserver/bin in a command terminal and run./propfilepasswordencoder.sh /opt/tempviewer/viewer/webinf/classes/contextmanager.prop serverusrpass. Open /opt/tempviewer/viewer/web-inf/classes/contextmanager.prop and verify that the value for serverusrpass is in encryption format. Copy /opt/tempviewer/viewer/web-inf/classes/contextmanager.prop file to <MDM_HOME>/InstallableApps/properties. Delete viewer.war and viewer.ear if they exist under /opt/tempviewer. Open a command terminal and go to /opt/tempviewer/viewer, then run the command jar cvf viewer.war. Copy viewer.war from /opt/tempviewer/viewer to /opt/tempviewer. Delete the /viewer folder under /opt/tempviewer. In a command terminal, go to /opt/tempviewer and run the following commands: jar -cvf viewer.ear viewer.war jar -uvf viewer.ear META-INF/application.xml

30 III. Verify that viewer.ear is created under /opt/tempviewer. Delete viewer.ear from <MDM_HOME>/InstallableApps/ear, if it exists there. Copy /opt/tempviewer/viewer.ear to <MDM_HOME>/InstallableApps/ear. Delete the /TempViewer directory from /opt. Stage three: Open the WebSphere Application Server Administrative console. Navigate to Servers -> All servers. Select User Interface server, for example, UIS Click the Ports link and get the values for WC_defaulthost and WC_defaulthost_secure. Navigate to Environment -> Virtual hosts. 6. Select default_host and then select HostAliases. 7. Check the values which you got at step #4 exists in this. If it's there you don't need to do anything. If the port number doesn't exist, click New and give the values. IV. Stage four: V. Open the WebSphere Application Server Administrative Console and navigate to Servers All servers. Select the appropriate User Interface server. Open and expand Container Settings, select ORB service, then click Custom properties. Search for com.ibm.corba.requesttimeout property. a. If the com.ibm.corba.requesttimeout property is present, verify that the value is 720. b. If the com.ibm.corba.requesttimeout property is not present, add it with a value of 720, click OK, then click Save. If your Enterprise Viewer User Interface is deployed to a single server, you can proceed to stage V. If your Enterprise Viewer User Interface is deployed to a cluster, repeat all of the preceding steps for each server on the cluster, then proceed to stage V. Stage five: Open the WebSphere Application Server Administrative Console and navigate to Applications All applications. Click Add to deploy new viewer.ear file, then click Next. When asked to provide the location of the viewer.ear that you want to deploy, enter <MDM_HOME>/InstallableApps/viewer.ear and click Next. When asked for the installation options, select the defaults and click Next. Replace the default viewer in Application name with enterpriseviewer-<mdm-app-name>, then click Next. Determine where you want to deploy enterpriseviewer-<mdm-app-name>, select the server or cluster based on your requirements, select the corresponding check box and click Apply, then click Next. Click Next with the default values selected. To complete deploying the viewer.ear, click Finish, then click Save. Verify that enterpriseviewer-<mdm-app-name> is deployed under Applications All applications. Broker Changes IMPORTANT: Before applying the fix pack for Broker, back up the files that you will be modifying. Files to be modified are determined by operating system.

31 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, and you can find four ZIP files, each for a different operating system: com.ibm.mdm.mds.brokers-aix6zip com.ibm.mdm.mds.brokers-linux6zip com.ibm.mdm.mds.brokers-sunos6zip com.ibm.mdm.mds.brokers-win64_amd6zip Extract the ZIP file that corresponds to your operating system where InfoSphere MDM is installed. If your operating system is AIX, the files you must back up and replace are located in <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/brokers/com.ibm.mdm.build.brok ers/installer. You must replace these files under <MDM_HOME>/MessageBrokerSuite. You can get these files by extracting com.ibm.mdm.mds.brokers-aix6zip: 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 your operating system is Linux, the files you must back up and replace are located in <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/brokers/com.ibm.mdm.build.brok ers/installer. You must replace these files under <MDM_HOME>/MessageBrokerSuite. You can get these files by extracting com.ibm.mdm.mds.brokers-linux6zip: 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 your operating system is Solari, the files you must back up and replace are located in <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/brokers/com.ibm.mdm.build.brok ers/installer. You must replace these files under <MDM_HOME>/MessageBrokerSuite. You can get these files by extracting com.ibm.mdm.mds.brokers-sunos6zip: bin/msgreader bin/msgsender bin/querybroker bin/openssl lib/libmicommon.so

32 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 your If your operating system is Windows 64, the files you must back up and replace are located in <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/brokers/com.ibm.mdm.build.brok ers/installer. You must replace these files under <MDM_HOME>/MessageBrokerSuite. You can get these files by extracting com.ibm.mdm.mds.brokers-win64_amd6zip. In the case of Windows 64, you must replace all of the files under bin, lib, and proxy/lib folders and a file build-utilsbrokers.xml under the scripts folder. Static Changes Before you begin, back up the existing files that you are are changing. The new files for static changes are located in two places: <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/staticcontent/com.ibm.mdm.build.cl ientapps/installer <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/staticcontent/com.ibm.mdm.build.ei /installer BatchProcessor changes: New files for static changes are located at <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/staticcontent/com.ibm.m dm.build.clientapps/installer. Extract the ZIP file com.ibm.mdm.batch.framework.jar in the same location, then locate the file /BatchProcessor/lib/com.ibm.mdm.batch.framework.jar. Before proceeding, create a backup of the existing <MDM_HOME>/BatchProcessor/lib/com.ibm.mdm.batch.framework.jar before replacing it with the new file. Copy <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/staticcontent/com.ibm.m dm.build.clientapps/installer/batchprocessor/lib/com.ibm.mdm.batch.framework.jar to <MDM_HOME>/BatchProcessor/lib. In <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/staticcontent/com.ibm.m dm.build.clientapps/installer, locate the files com.ibm.mdm.clientutils.hybridpostinstall.zip and com.ibm.mdm.clientutils.namesearchexclusion.zip. Extract the ZIP file com.ibm.mdm.clientutils.hybridpostinstall.zip in the same location. Locate the ReadMe.txt file which is under /HybridPostInstall/doc folder, then go to <MDM_HOME>/Hybrid/HybridPostInstall/doc and replace this file. Extract the ZIP file com.ibm.mdm.clientutils.namesearchexclusion.zip in the same location. In the commonnamesearchexclusion directory, locate and back up the files build_nonstandardized_searchexclrule_by_city.sql and build_ Standardized_searchExclRule_by_City.sql, then update these files.

33 10. Extract the ZIP file com.ibm.mdm.mds.ei-win3zip in the same location. You can find this zip file under <MDM_HOME/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/staticcontent/com.ibm.md m.build.ei/installer. 1 There are two files, libeay3dll and ssleay3dll in the /bin directory. Update these files under <MDM_HOME>/EnterpriseIntegrator/bin. Sample Changes IMPORTANT: Before modifying these files, back up your existing files. The new files for sample changes are located in two places: <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/samples/com.ibm.mdm.build.samples/ installer <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/samples/com.ibm.mdm.build.ui.legac y/installer 6. Under <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/samples/com.ibm.mdm.bui ld.samples/installer locate the files com.ibm.mdm.bil.assets.zip and com.ibm.mdm.bil.configqsrules.zip, then extract both in the same location. Copy the file from <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/samples/com.ibm.mdm.bui ld.samples/installer/bildistribution/mdmis_bil.zip to the <MDM_HOME>/Samples/BILDistribution folder. Copy the folder from <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/samples/com.ibm.mdm.bui ld.samples/installer/configqsrules to the <MDM_HOME>/Samples folder. Under <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/samples/com.ibm.mdm.bui ld.ui.legacy/installer, locate the following ZIP files: com.ibm.mdm.sample.ba.webapp.ear.zip com.ibm.mdm.sample.ds.webapp.ear.zip com.ibm.mdm.sample.pui.webapp.ear.zip Extract these ZIP files in same location. When you are finished, you will find three directories: /BAUI, /DSUI, and /PUI. Copy the directories /BAUI, /DSUI, and /PUI from <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/samples/com.ibm.mdm.bui ld.ui.legacy/installer to the <MDM_HOME>/Samples folder. 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. Extract com.ibm.mdm.db.domain.zip at this location only. Locate the update corresponding with your database. There are database updates for DB2, Oracle, and z/os: For DB2, you can find the scripts under <MDM_HOME>/updates/<FIXPACK_NUMBER>/com.ibm.mdm.advanced.fix/database/com.ibm.mdm

34 .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 all three SQL files: Upgrade.sql Upgradedb_fpsql Upgradedb_fpsql