Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.3 Part Number E28316-03 |
|
|
PDF · Mobi · ePub |
This chapter discusses how to configure and deploy Oracle Product Master Data Management: Routing Rules (Product MDM: Routing Rules).
This chapter includes the following sections:
The overall MDM Product integration consists of four component integrations: MDM Product Base Pack (OPH) and three other options: MDM Product Siebel, MDM Product E-Business Suite and MDM Product 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:
Configure and deploy the MDM Product component integrations. For detailed instructions on the MDM Product integrations, see your specific integration chapters in Part II, "Configuring and Deploying Pre-Built Integrations" of this guide.
Deploy the MDM Product Routing Rules following the instructions discussed in Section 19.2, "Deploying Product MDM: Routing Rules". Routing Rules wire the integration services, depending on the integrations deployed.
To deploy the routing rules to Fusion Middleware server:
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.
Run the command for your platform.
Table 19-1 Deployment Commands for Product 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/MDMProduct/DeploymentPlans/deployEBS.sh |
Microsoft Windows (32-bit) |
%AIA_HOME%\pips\MDMProduct\DeploymentPlans\deployEBS.bat |
Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/MDMProductDP_Deployments_YYYY-MM-DD_HH-MI-SS.log to verify successful deployment of the integration.
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, and 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 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 about deploying artifacts, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts."
To verify the Product MDM: Routing Rules deployment:
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.
Confirm that the Product MDM: Routing services were installed.
Navigate to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).
Log in with the server admin user name.
For access details, contact the system administrator.
Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:
SpecificationValueSetEBS
SpecificationValueSetResponseEBS
ClassificationSchemeEBS
ClassificationSchemeResponseEBS
ItemEBSV2
ItemResponseEBSV2
PriceListResponseEBSV2
CommunicationsPriceListEBSV2
CommunicationsPriceListResponseEBSV2
PriceListEBSV2
CommunicationsItemCompositionEBSV1
CommunicationsItemCompositionResponseEBSV1
BillOfMaterialsEBS
BillOfMaterialsResponseEBS
Comms2CorePriceListBridgeService
Core2CommsPriceListBridgeService
To undeploy the routing rules from Fusion Middleware Server:
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.
Run the command for your platform.
Table 19-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/MDMProduct/DeploymentPlans/undeployEBS.sh |
Microsoft Windows (32-bit) |
%AIA_HOME%\pips\MDMProduct\DeploymentPlans\undeployEBS.bat |
Restart the SOA server.
Uninstall the integration following the instructions in the Chapter 37, "Uninstalling Oracle AIA".