Wednesday 18 October 2017

Uninstall a User Interface from IBM InfoSphere Master Data Management v11.5

To uninstall a User Interface that has been installed with MDM v11.5, please follow the below steps.
Note: Please do not use the Modify option from Installation Manager to remove a User Interface from MDM v11.5

Changes to MDM_Variables.properties
1. Go to MDM_INSTALL_HOME/properties and edit the file MDM_Variables.properties.
2. From the value of property user.L2.mdm.feature.list, remove the feature name corresponding to the user interface that you want to uninstall.  The features names corresponding to the MDM user interfaces are listed below:
Business Administration UI: com.ibm.im.mdm.ba.webapp.feature
Enterprise Viewer: com.ibm.im.mdm.ev.webapp.feature
Web Reports: com.ibm.im.mdm.wb.webapp.feature
Inspector: com.ibm.im.mdm.inspector.webapp.feature
3. Save the properties file.

Changes to MDM_isInstalled.properties

1. Go to MDM_INSTALL_HOME/properties and edit the file MDM_isInstalled.properties.
2. Ensure that the value of property IS_MODIFY is YES
IS_MODIFY=YES
3. Ensure that the property corresponding to the installation of user interface is set to YES.  The property names corresponding to the MDM user interfaces are listed below:
Business Administration UI: BA_UI_APPLIED
Enterprise Viewer: EV_UI_APPLIED
Web Reports: WEB_UI_APPLIED
Inspector: INS_UI_APPLIED
4. Save the properties file.

Changes to MDM_Rollback.properties

1. Go to MDM_INSTALL_HOME/properties and edit the file MDM_Rollback.properties.
2. Ensure that the property corresponding to the installation of user interface is set to YES.  The property names corresponding to the MDM user interfaces are listed below:
Business Administration UI: BA_STATUS
Enterprise Viewer: EV_STATUS
Web Reports: WEB_STATUS
Inspector: INS_STATUS
3. Save the properties file.

Target Execution
1. Go to MDM_INSTALL_HOME/MDS/scripts and run the Configure_MasterDataManagement madconfig script to apply the new configuration:
i) When the installation is on Windows, execute
madconfig Configure_MasterDataManagement
ii) On other operating systems, execute
./madconfig.sh Configure_MasterDataManagement


Installation of IBM InfoSphere MDM on Oracle Database 12c Release 2

We have noticed failure when MDM is configured using Oracle Database 12c Release 2 as the database with the below exception:
test_datasource:

Running ODBC SQL statement [select 1 from dual;]...
Executing <MDM_INSTALL_DIR>/mds/bin/madsql.exe
<MDM_INSTALL_DIR>/mds/scripts../bin/madsql.exe: STATE=HY000, CODE=28040, MSG=[InitiateSystems][ODBC Oracle Wire Protocol driver][Oracle]ORA-28040: No matching authentication protocol
Result: 1


To overcome this exception, perform the below steps on Oracle configuration:
1. Set the value of property SQLNET.ALLOWED_LOGON_VERSION_SERVER to a value below 12
in file sqlnet.ora.  The recommended value is 8
2. Restart the Oracle Service corresponding to the database
3. Change the password using the ALTER USER command
The above steps can also be found at SQLNET.ALLOWED_LOGON_VERSION_SERVER


Note: MDM uses ojdbc6.jar for JDBC communication with Oracle during installation, configuration and runtime, hence please ensure that ojdbc6.jar is available at <ORACLE_HOME>/jdbc/lib folder.

Installing MDM v11.6 and MDM v11.5 on WebSphere Application Server v8.5.5.12 using IM GUI

When an attempt is made to install MDM v11.6.0.2 or below on WebSphere Application Server v8.5.5.12 using the Installation Manager GUI, certain exceptions are noticed in the WAS Config Panel and in the Panels that correspond to the MDM User Interfaces.  To overcome this exception and continue installation using IM GUI, the below steps have to be performed:
1. When the installation is on WAS ND, go to System Administration -> Deployment Manager -> Java And Process Management -> Process definition -> Java Virtual Machine -> Custom Properties
When the installation is on WAS Base, go to Servers -> Server Types -> WebSphere Application Servers -> <SERVER> -> Java And Process Management -> Process definition -> Java Virtual Machine -> Custom Properties
2. Add property com.ibm.ws.management.connector.soap.disableSOAPAuthCheck with value as true
3. Restart the Deployment Manager

Setting value for JVM Custom property com.ibm.ws.management.connector.soap.disableSOAPAuthCheck

This property can be removed from the JVM Custom properties and the server can be restarted after the Installation Manager completes extraction of MDM.

The other alternatives to proceed with installation of MDM v11.6.0.2 and below on WAS v8.5.5.12 are:
1. Install using silent mode by providing the inputs through a response file
2. Install MDM on a lower fixpack of WAS and upgrade WAS after MDM installation and configuration.