14 Deploying Customer MDM: Match Fetch Enterprise Composite Application

This chapter discusses how to configure and deploy Oracle Customer Data Management: Match Fetch Enterprise Composite Application (Customer MDM: Match Fetch Enterprise Composite Application).

This chapter includes the following sections:

• Section 14.1, "Overall Configuration and Deployment of MDM Customer Integrations"

• Section 14.2, "Deploying Customer MDM: Match Fetch Enterprise Composite Application"

• Section 14.3, "Verifying Deployment"

• Section 14.4, "Undeploying Customer MDM: Match Fetch Enterprise Composite Application"

14.1 Overall Configuration and Deployment of MDM Customer Integrations

The overall MDM Customer integration consists of four component integrations: MDM Customer Base Pack (UCM) and three other options: MDM Customer Siebel, MDM Customer E-Business Suite and MDM Customer BRM. The overall MDM Customer integration can be configured and deployed by selecting any integration or integration combination. The configuration and deployment process consists of the following steps:

1. Configure and deploy the MDM Customer component integrations. For detailed instructions on the MDM Customer integrations, see your specific integration chapters in Part I, "Configuring and Deploying Pre-Built Integrations" of this guide.

2. Deploy the MDM Customer Routing Rules following the instructions discussed in Chapter 13, "Deploying Customer MDM Routing Rules". Routing Rules wire the integration services, depending on the integrations deployed.

3. Deploy the MDM Customer Match Fetch Enterprise Composite Application following the instructions in Section 14.2, "Deploying Customer MDM: Match Fetch Enterprise Composite Application". This UI application enables match and fetch of customers from the hub.

14.2 Deploying Customer MDM: Match Fetch Enterprise Composite Application

Note:

The Match Fetch Enterprise Composite Application available for previous versions of AIA is different from the one available for AIA 11.1. You must install and configure the latest Match Fetch Enterprise Composite Application available for this release.

To deploy the ADF-based UI to Fusion Middleware server:

1. Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.

2. Run the command for your platform.

   Table 14-1 Deployment Command for Customer MDM: Match Fetch Enterprise Composite Application

   Platform	Deployment Command
   Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit)	sh $AIA_HOME/services/core/UCM/UtilityServices/CustomerHub/DeploymentPlans/deployCustomerHUBMatchAndFetchApp.sh
   Microsoft Windows (32-bit)	%AIA_HOME%\services\core\UCM\UtilityServices\CustomerHub\DeploymentPlans\deployCustomerHUBMatchAndFetchApp.bat

   
   

3. Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/CustomerHUBMatchAndFetchAppDP_Deployments_YYYY-MM-DD_HH-MI-SS.log to verify successful deployment.

14.3 Verifying Deployment

To verify the Customer MDM: Match Fetch Enterprise Composite Application deployment:

1. Open the log files from the following location and look for warnings and error messages:

   • For Linux x86, Solaris SPARC (64-bit), HP-UX 11i (64 bit) and IBM AIX Based Systems (64-bit): Review the install log located at <AIA_HOME>/aia_ instances/<instance name>/logs to verify whether the integration is successfully installed.

   • For Microsoft Windows (32-bit): Review the install log located at <AIA_ HOME>\aia_instances\<instance name>\logs to verify whether the integration is successfully installed.

2. Confirm that the Proxy services were installed.

   1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).

   2. Log in with the server admin user name. For access details, contact the system administrator.

   • MatchAccountEBSProxyService

   • MatchContactEBSProxyService

   • FetchAccountEBSProxyService

   • FetchContactEBSProxyService

3. Confirm the installed application is accessible using the following URL -

   1. For Account Match-Fetch: http://<server name>:<port number>/CustomerHub-matchfetch-context-root/faces/Organization.jspx

   2. For Contact Match-Fetch: http://<server name>:<port number>/CustomerHub-matchfetch-context-root/faces/Person.jspx

14.4 Undeploying Customer MDM: Match Fetch Enterprise Composite Application

To undeploy the Match Fetch application from Fusion Middleware Server:

1. Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.

2. Run the command for your platform.

   Table 14-2 Undeployment Command for Customer MDM: Match Fetch Enterprise Composite Application

   Platform	Undeployment Command
   Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit)	sh $AIA_HOME/services/core/UCM/UtilityServices/CustomerHub/DeploymentPlans/undeployCustomerHUBMatchAndFetchApp.sh
   Microsoft Windows (32-bit)	%AIA_HOME%\services\core\UCM\UtilityServices\CustomerHub\DeploymentPlans\undeployCustomerHUBMatchAndFetchApp.bat

   
   

3. Restart the SOA server.

4. Uninstall the integration following the instructions in the Chapter 37, "Uninstalling Oracle AIA"