Sometimes, even we do everything right like have enabled hybrid model but still do not see event manger to work properly means even data get inserted into Virtual MDM Model but event manger does not create golden record into Physical MDM. We also see mpi_entoque_xxx table populated with data but do not get picked by Event Manager.
There might be multiple reason for it. Below is written few check points
1. Make sure that Messaging Engine is started
2. See log files minutely while starting the server because sometimes it gets started successfully but still some errors get captured in SystemOut.log file.
For Example:
I have got this error:
There might be multiple reason for it. Below is written few check points
1. Make sure that Messaging Engine is started
2. See log files minutely while starting the server because sometimes it gets started successfully but still some errors get captured in SystemOut.log file.
For Example:
I have got this error:
java.lang.RuntimeException: Application could not be initialized. Application Name and Version could not be resolved.
Solution:
This error typically indicates that the InfoSphere MDM EBA application symbolic name does not match the entries in the APPSOFTWARE configuration table.
Confirm that the APPSOFTWARE entry matches the EBA symbolic name by executing the following SQL statement:
select * from APPSOFTWARE;
In the WebSphere Application Sever Administrative Console, navigate to Applications > Application Types > Assets. Under Assets, click on theMDM operational server EBA > com.ibm.mdm.hub.server.app-E001.eba asset. On the following page, click Export the deployment manifest from this application.
Now open the deployment.mf file and search for Application-SymbolicName and Version. Next to it will be the value that needs to correspond to the entry in the APPSOFTWARE table.
No comments:
Post a Comment