In the Informatica Data Director Configuration Manager, if you accidentally generate business entity schema for

Customer 360

, the Configuration Manager overwrites your business entity configuration. After you generate the business entity schema,

Customer 360

does not function as expected. For example, the task inbox and the Task Manager does not display any tasks even though you have valid tasks.

To resolve this issue, perform the following tasks:

In the Configuration workbench of the Hub Console, click
Repository Manager
.
The Repository Manager tool opens.
To select the source repository, perform the following tasks:
On the
Promote
tab, click
Visual
.
Click the
Select
button next to the
Source
list.
The
Open Repository
dialog box appears.
On the
File Repository
tab, browse to the following directory:
For Party table-based data model.
<MDM installation directory>/app/tcr/hub/change-xml
For Party Role table-based data model.
<MDM installation directory>/app/tcr/hub/change-xml/pre_c360_10.2_hf2
Select the
TCR_HUB.change.xml
file, and click
Open
.
The Repository Manager tool loads and validates the repository from the selected file.
Click
OK
.
The Repository Manager tool displays the source repository as a hierarchical tree.
To select the target repository, in the
Target
list, select the ORS of
Customer 360
.
In the hierarchy tree of the source repository, select
Business Entity/Business Entity Services Configurations
.
To promote the selected object, perform one of the following tasks:
Right-click the selected object, and select
Promote
.
Click the
Promote
icon.
Drag the selected object from the source repository to the target repository.
The
Promotion
dialog box appears.
Select
Replace the target objects with source objects
, and click
OK
.
The
Impact Analyser
dialog box appears.
Click
OK
.
Click the
Apply Changes
icon.
If you have extended your business entities, restore or reconfigure the extended objects.
On the
Validate
tab, select the ORS of
Customer 360
, and click
Validate
.
Reopen a browser, and log in to Customer 360.

In a WebSphere and IBM DB2 environment, when you import an IDD application in the Zip format, the import might fail.

To resolve the issue, use one of the following options:

Increase the size of BLOB_DATA column to 30 MB in the CMX_SYSTEM.C_REPOS_DS_CONFIG table with the following IBM DB2 command:
ALTER TABLE CMX_SYSTEM.C_REPOS_DS_CONFIG ALTER COLUMN BLOB_DATA SET DATA TYPE BLOB(31457280);
Import and deploy the
BDDConfig.xml
file.

In the

C_REPOS_CO_CS_CONFIG

repository table, if the

TASKS

configuration contains the

LookupSegmentValue

business entity for a trigger, the Provisioning tool does not respond.

To fix this issue, remove the

LookupSegmentValue

business entity from the

TASKS

configuration. However, after you remove the

LookupSegmentValue

business entity from the

TASKS

configuration, you cannot add a new tag to a business entity.