Configuration Manager updates

Once the application server components are deployed, the last step in engine deployment is to enter instance details in the Configuration Manager tables.

Note: This step must be done for the combined InfoSphere® MDM Standard and Advanced Edition engine, so cannot be ignored.

The Configuration Manager component for physical MDM consists of several tables:

APPDEPLOYMENT
This table should only have one row, which describes this deployment. Columns include Deployment_ID, Application_ID, Name, and last update information.
APPINSTANCE
This table should be empty unless there is a WebSphere® Application Server cluster being used. If a cluster is being used, then there will be one row per node in the cluster. Columns include Instance_ID, Deployment_ID, Name, and last update information.
APPSOFTWARE
This table should only contain one row. The Name column should be the specificed application instance value, such as E001. Columns include Application_ID, Name, and last update information.
Tip: If there are multiple instances or a mismatch between installed applications and instances, you can often resolve this by ensuring that the marked instance name matches the EBA deployed name. This situation can occur if multiple installation attempts are performed in the same database without fully uninstalling or cleaning up the database between installation attempts.
  1. Use sqldeveloper or its equivalent to create a row in the APPSOFTWARE table with the current instance name, if it does not already appear. Delete any other rows from this table.
    update APPSOFTWARE set NAME='com.ibm.mdm.hub.server-<instance name>', LAST_UPDATE_DT=CURRENT_TIMESTAMP where NAME='com.ibm.mdm.hub.server-<old_instance_name>';
delete from APPSOFTWARE where NAME='com.ibm.mdm.hub.server';
  2. Restart the server and log in.
  3. Review the system logs