Troubleshooting failed installation verification tests

Often, an IVT failure can be fixed, especially if the issue is located in the application layer. The first step is to determine exactly what the problem is. Navigate to the application log files at <MDM_INSTALL_HOME>/logs/database and look for .err files under various folders. If there are any database problems, they should be found in that location.

Troubleshooting IVT failures using the WebSphere Application Server logs

Some WebSphere® Application Server logs that indicate problems that may not be obvious in the InfoSphere® MDM logs. This is true in the cases of the following examples, which each can cause IVT failures.

SIB tables missing or created with an older instance

If your installation has missing SIB tables or SIB tables that were created with an older instance, then the WebSphere Application Server logs will have errors such as the following example and will also have BlueprintContainer errors:

[2/7/14 15:51:54:023 PST] 00000058 DWLExceptionU E   javax.jms.JMSException: CWSIA0241E: An exception was received during the call to the method JmsManagedConnectionFactoryImpl.createConnection: com.ibm.websphere.sib.exception.SIResourceException: CWSIT0008E: A successful connection was made to the bootstrap server at localhost:7276:BootstrapBasicMessaging but the server returned an error condition: CWSIT0088E: There are currently no messaging engines in bus MDM.SIB.server1 running. Additional failure information: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=MDM.SIB.server1, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundBasicMessaging, proximity=Bus..at com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:195)

Resolution

1. Stop the server or cluster.
2. Delete the SIB tables from the MDM database. There should be nine tables starting with SIB*.
3. Restart the server or cluster.
4. Run IVT again.

These steps will recreate the SIB tables with new entries and refresh the instance.

Authorization failure for mdmadmin or MDM user

If there is an authorization failure, then the WebSphere Application Server logs will have errors such as the following example:

[4/29/14 20:07:39:710 CDT] 00000140 SecurityColla A   SECJ0053E: Authorization failed for tmwdchou01.tmw.com:389/mdmadmin while invoking (Bean)com.ibm.mdm.hub.server-E001..11.0.0..com.ibm.mdm.server.dwlcommonservices.ejb..11.0.0.FP00IF000_20131005-0518.war#com.ibm.mdm.server.dwlcommonservices.ejb..11.0.0.FP00IF000_20131005-0518.war#DWLServiceController processRequest:java.util.HashMap,java.io.Serializable:1  is not granted any of the required roles: ServiceConsumer ServiceProvider
[4/29/14 20:07:39:714 CDT] 00000140 AxisEngine    E org.apache.axis2.engine.AxisEngine receive An error was detected during JAXWS processing
org.apache.axis2.AxisFault: An error was detected during JAXWS processing
at org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:208)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:208)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)

Resolution

1. Log on to the WebSphere Application Server Integrated Solutions Console (admin console).
2. Navigate to Business-level applications > MDM-operational-server-EBA-E001 > com.ibm.mdm.hub.server.app-E001_0001.eba > Security role to user or group mapping.
3. Click Map Special Subjects > All Authenticated in Application's Realm to the ServiceConsumer.
4. Click Map users..., then select mdmadmin from LDAP server and map it to ServiceProvider.
5. Navigate to Business-level applications > MDM-operational-server-EBA-E001 > com.ibm.mdm.hub.server.app-E001_0001.eba > RunAs roles for users.
6. Add the mdmadmin user to both the ServiceProvider and ServiceConsumer.

The MDM engine instance cannot be found (BlueprintContainer error)

If the MDM engine instance cannot be found, then the WebSphere Application Server logs will have errors such as the following example:

[12/9/14 15:51:38:439 IST] 00000078 BlueprintCont E org.apache.aries.blueprint.container.BlueprintContainerImpl$1 run Unable to start blueprint container for bundle com.ibm.mdm.server.extrules.default due to unresolved dependencies [(objectClass=com.ibm.mdm.server.config.api.ConfigManager)]
java.util.concurrent.TimeoutException
at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:328)
at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:450)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:109)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:217)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929)
at java.lang.Thread.run(Thread.java:796)

This happens when the EBA name in WebSphere Application Server and the Configuration Manager tables are different. This situation can occur when you reinstall InfoSphere MDM, reusing the same database multiple times without cleaning it between installations.

Check the Configuration Manager table APPSOFTWARE and verify the EBA name. The EBA name value should match the EBA name in WebSphere Application Server.

Resolution

1. Open DB2 or another applicable database command line and connect to the MDM database.
2. Modify the APPSOFTWARE table as follows:

   Update APPSOFTWARE set name=”com.ibm.mdm.hub.server-E010” where APPLICATION_ID=1004;

3. Commit the change to the database.
4. Restart the WebSphere Application Server instance.
5. Rerun IVT.

The Standard Edition native component is not available in WebSphere Application Server

The InfoSphere MDM Standard Edition native component is installed on WebSphere Application Server as MDM-native-<instance>.ear. This file is extracted into the WAS_HOME folder as follows when the server starts: <WAS_HOME>/profiles/<PROFILE_NAME>/installedApps/<CELL_NAME>/MDM-native-E0010.ear

This native component is used by the Standard Edition engine for virtual MDM. The native component must have the correct configuration to enable the Standard Edition engine to work correctly. A copy of the component is also kept at <MDM_INSTALL_HOME>/mds and the configuration of both of these instances must be synchronized.

In some cases, an error may cause the MDM-native-E0010.ear to not be extracted into WAS_HOME, meaning that the folder is not created. This will cause the following error to occur:

Caused by: com.dwl.base.exception.DWLBaseException: com.dwl.base.exception.DWLBaseException: com.dwl.base.exception.DWLBaseException: Could not locate business object: VirtualMDMBObj     at com.dwl.base.xml.DWLDocumentHandlerHelper.createObject(DWLDocumentHandlerHelper.java:1358)     at com.dwl.base.xml.DWLDocumentHandlerHelper.populateTopObject(DWLDocumentHandlerHelper.java:1221)     at com.dwl.base.xml.DWLDocumentHandlerHelper.endElement(DWLDocumentHandlerHelper.java:891)     at com.dwl.tcrm.coreParty.xmlHandler.TCRMDocumentHandler.endElement(TCRMDocumentHandler.java:160)     at com.ibm.xml.xci.sax.serializer.SAXCursor.writeClosingTag(SAXCursor.java:225)     ... 71 more

Resolution

1. Restart the server.
2. Ensure that the following folder exists and contains the virtual MDM native component: <WAS_HOME>/profiles/<PROFILE_NAME>/installedApps/<CELL_NAME>/MDM-native-E0010.ear
3. If the correct content is present in this folder, rerun IVT. The error should go away. If not, skip to step 7.
4. If the correct content is not present, then navigate to <MDM_INSTALL_HOME>/mds/scripts and run the following command:

   madconfig install_native_engine_ear -propertyfile ../../properties/install_native_engine_ear.properties

5. Restart the server.
6. Rerun IVT.
7. If the issue persists, then check whether the installation configuration includes Microsoft SQL Server and LDAP. If so, then contact your database administrator (DBA) to run the following SQL scripts.
   Note: These scripts are only required if you are using SQL Server. Turn on snapshot isolation for SQL Server. This only needs to be done once.

   ALTER DATABASE <database name> SET ALLOW_SNAPSHOT_ISOLATION ON
   ALTER DATABASE <database name> SET SINGLE_USER WITH ROLLBACK IMMEDIATE
   ALTER DATABASE <database name> SET READ_COMMITTED_SNAPSHOT ON
   ALTER DATABASE <database name> SET MULTI_USER \

   After the scripts have been run, then restart the application server.
8. If the issue is still not fixed, then uninstall and reinstall InfoSphere MDM.