Table of Contents

Search

  1. Preface
  2. Introduction to Informatica MDM - Customer 360
  3. Before You Install
  4. Installing MDM - Customer 360
  5. After You Install
  6. Business Processes for Customer Management
  7. Customizing Customer 360
  8. Upgrading Customer 360
  9. Troubleshooting

Extracting the Customer 360 Application Archive File

Extracting the Customer 360 Application Archive File

You receive the Customer 360 application as an archive file. Create the following directory structure and extract the contents of the
Customer 360
archive file into it:
<MDM Installation Directory>/app/tcr
The extracted content contains the following files and folders:
File or Folder Name
Description
batchgroup
Contains the JAR file for the silent installation process.
bin/
Contains installation, upgrade, and database schema validation utilities.
bpm/
Contains the ActiveVOS default business process in a deployable format. The folder contains the following sub-folders:
  • pre_c360_10.2_hf2/
    . Directory that contains the default business processes for the data model based on the Party Role table.
  • source/
    . Contains the source files for business processes.
  • InfaCustomer360Workflow.bpr
    . Contains the default business process for the data model based on the Party table.
config/
Contains configuration properties files.
data/
Contains the scripts for inserting lookup or reference data.
datamodelmigration/
Contains the scripts and the change lists required to migrate from the data model based on the Party Role table to the data model based on the Party table.
docs/
Contains the data dictionary. The folder contains the following files and sub-folders:
  • C360_104_DataDictionary_en.pdf
    . Data dictionary for the data model based on the Party table.
  • pre_c360_10.2_hf2
    . Directory that contains the data dictionary for the data model based on the Party Role table.
extensions
Contains the files for Customer 360 extensions.
hub/
Contains the subdirectories that contain the database schema and the configuration files to deploy. Following are the list of the subdirectories:
  • change-xml/
    . Contains the MDM Hub metadata including components, such as landing tables, lookup tables, staging tables, base objects, and match and merge rules, cleanse functions, component instances, business entities, and business entity services.
  • cocs-config-xml/
    . Contains configuration files for the business entities and business entity services.
  • delta_change_xml/
    . Contains the newly added MDM Hub metadata.
  • entity360config-xml/
    . Contains copies of the Entity 360 component instance definitions that ship with
    Multidomain MDM
    .
lib/
Directory for the external libraries. Copy the JDBC driver files for your database to the
lib
directory.
localizationScript
Contains the scripts for localizing labels and error messages.
lookuplocalization/
Contains the localized lookup data.
notices/
Contains the legal copyright file.
reporting/
Contains
datamart
folder which contains the data mart service and the chart configurations. The
pre_c360_10.2_hf2/
directory in the
datamart
folder contains the data mart service for the data model based on the Party Role table.
resources/
Contains the resource
bundle.properties
files for each of the supported locales.
upgrade/
Contains the supporting files for the upgrade utility.
user_exit/
Contains the MDM Hub user exit archive.
was
Contains the Provisioning tool user interface for a WebSphere environment.
bundleLocalization.jar
JAR file for localization.
MDMAppsServices.war
File that contains
Customer 360
services.
mdmappsview-ear.ear
uiwebapp-ear.ear
Files that contain
Customer 360
user interface JBoss.
productversion.jar
JAR file for the product version.
provisioning-ear.ear
File that contains the Provisioning tool user interface.
store-credentials.jar

0 COMMENTS

We’d like to hear from you!