If you face problems when you migrate from the SA data model in IDD to the BE data model in IDD, use the following information to troubleshoot the issue.
The IDD configuration is invalid
When you generate a business entity schema, sometimes Hierarchy Manager entity base objects do not convert the relationships of Hierarchy Manager-enabled business entities correctly.
To resolve the issue, in the IDD Configuration Manager, edit a subject area with a Hierarchy Manager entity base object. A numeric subtype value indicates an invalid IDD configuration. In the
HM Entity Type
field, select another entity type and then reselect the original entity type until the value in the
Subtype Value
field changes to a nonnumeric value.
Smart search doesn't work
Verify that you completed the following steps:
In the Hub Console, you configured smart search and ZooKeeper. You configured only one Process Server as a ZooKeeper server.
You set
cmx.ss.enabled=true
in both the
cmxserver.properties
file and the
cmxcleanse.properties
file.
If you use IBM WebSphere, you set
pingSolrOnStartup=true
in the
cmxcleanse.properties
file.
In the E360 application, you marked fields as searchable in the business entity models.
You published the schema with the searchable fields.
From the MDM Hub Console, you ran the search index batch job on all the business entities.
A review task opens a business entity in a legacy view, but I turned off the legacy views
The task was migrated from the legacy IDD application. When you open the entity from the task, it opens in the view in which it was edited. When all the legacy tasks are closed, the legacy views are no longer used.