13 Deploying Customer MDM Routing Rules

This chapter discusses how to deploy Oracle Customer Master Data Management: Routing Rules (Customer MDM: Routing Rules).

This chapter includes the following sections:

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

• Section 13.2, "Deploying Customer MDM: Routing Rules"

• Section 13.3, "Verifying Deployment"

• Section 13.4, "Undeploying Customer MDM: Routing Rules"

13.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 Section 13.2, "Deploying Customer MDM: Routing Rules". Routing Rules wire the integration services, depending on the integrations deployed.

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

13.2 Deploying Customer MDM: Routing Rules

To deploy the routing rules 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 13-1 Deployment Commands for Customer MDM: Routing Rules

   Platform	Deployment Command
   Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit)	sh $AIA_HOME/pips/MDMCustomer/DeploymentPlans/deployMDMCustomerEBS.sh
   Microsoft Windows (32-bit)	%AIA_HOME%\pips\MDMCustomer\DeploymentPlans\deployMDMCustomerEBS.bat

   
   

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

Oracle AIA ships artifacts in AIA Lifecycle Workbench which can be used in your integrations. These artifacts are created using FMW technologies such as BPEL and Mediator and are natively supported by AIA Foundation Pack tools such as Project Lifecycle Workbench, Harvester, Deployment Generator, AIA Deployment Driver (ADD). These are called native artifacts and they include SOA artifact types such as composites, DataSources, DVM, xRef, and so on. These artifacts can be modified or new natively supported artifacts can be added using the AIA Lifecyle Workbench and a BOM.xml file can be generated.

AIA integration development teams, most often, also require deployment of artifact types that are beyond what is supported by the Project Lifecycle Workbench and AIA Harvester. For instance, integration may require artifacts such as, Java applications, Shell Scripts, ANT based build scripts which constitute part of integration landscape in addition to the artifacts that are delivered by AIA. AIA also supports deployment of these supplementary artifacts. However, you must modify and add new non native artifacts outside AIA Lifecycle Workbench.

For more information on deploying artifacts, see the Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".

13.3 Verifying Deployment

To verify the Customer MDM: Routing Rules 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 Customer MDM: Routing 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.

   3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

   • CustomerPartyEBSV2

   • CustomerPartyResponseEBSV2

   • CustomerPartyOrchestrationEBSV2

   • CustomerPartyOrchestrationResponseEBSV2

   • ProcessCustomerPartyEBS

13.4 Undeploying Customer MDM: Routing Rules

To undeploy the routing rules 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 13-2 Undeployment Command for Customer MDM: Routing Rules

   Platform	Undeployment Command
   Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit)	sh $AIA_HOME/pips/MDMCustomer/DeploymentPlans/undeployMDMCustomerEBS.sh
   Microsoft Windows (32-bit)	%AIA_HOME%\pips\MDMCustomer\DeploymentPlans\undeployMDMCustomerEBS.bat

   
   

3. Restart the SOA server.

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