| Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.4 Part Number E37608-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.4 Part Number E37608-03 |
|
|
PDF · Mobi · ePub |
This chapter discusses how to configure and deploy the Oracle Product Master Data Management Integration Option for Oracle Communications for Design Studio (Product MDM: Design Studio).
This chapter includes the following sections:
You must make sure to install the Oracle Product Master Data Management Integration Base Pack prior to installing the Product MDM Integration Option for Design Studio Pre-built Integration pack. Also, the Product MDM: Design Studio integration option needs the Communications Order to Cash PIP for the requester that gets invoked from Design Studio. For more information , see Chapter 8, "Configuring and Deploying the Comms Order to Cash: SBL CRM and OSM Pre-Built Integration".
The Product MDM Base Pack can also be installed along with the Product MDM Integration Option for Design Studio Pre-built Integration pack.
To configure Product MDM: Design Studio:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure installation environment.
Navigate to <AIA_HOME>/bin and run the command ./aiaconfig.sh for Linux based systems and aiaconfig.bat for Microsoft Windows.
This launches the AIA Deployment Configuration Wizard (DCW).
Click Next.
Select Oracle Product Master Data Management Integration Base Pack under Product Master Data Management Pre-Built Integration.
Note:
The Product MDM Base Pack must be installed prior to installing the Product MDM: Design Studio pre-built integration pack or installed along with this installation.
Select Oracle Product Master Data Management Integration Option for Design Studio under Product Master Data Management Pre-Built Integration.
Click Next.
Enter information related to your integration server in the Integration Server Details screen.
Click Next.
Note:
If you have selected the MDM Product Base Pack install option along with this installation, then see Chapter 9, "Configuring and Deploying Customer MDM Base Pack"
Click Configure to accept this configuration and begin the installation.
The system displays progress of configuration in the Configuration Progress screen.
The system displays any warnings or errors as necessary. You can review the configuration log for additional details. The configuration log location is displayed in Configuration Progress screen.
When the configuration process finishes without errors, click Next.
When the AIA DCW displays the Configuration Complete screen, click Finish to close the DCW.
To configure using the response file:
Open the response file.
When you create a response file through OUI, passwords get stored as <SECURE>.
Replace the password fields with actual passwords in the response file.
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.
Navigate to <AIA_HOME>/bin and run the command./aiaconfig.sh <Response File Location and Name> for Linux based systems and aiaconfig.bat <Response File Location and Name> for Microsoft Windows.
To deploy the integration 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.
Note:
In Windows 2008, 2008 R2 and Vista, run the command prompt as an administrator (elevated mode). If the command prompt is invoked in normal mode, the integrations are not displayed.
Table 20-1 Deployment Commands for Product MDM: Siebel CRM
| Platform | Deployment Command |
|---|---|
|
Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit) |
sh $AIA_HOME/pips/MDMProductDS/DeploymentPlans/deployDS.sh |
|
Microsoft Windows (32-bit) |
%AIA_HOME%\pips\MDMProductDS\DeploymentPlans\deployDS.bat |
Review the log file in the location specified in the command 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 Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".
To retrieve product data from the Product Master, users can either select Siebel or Product Hub as their edge application. By default, this integration provides an out-of-the-box (OOTB) integration to Siebel.
The process to query ICCs (or product classes in Siebel CRM) depends on the AIAConfigurationProperties.xml file settings set by the users. For example, to retrieve ICCs from Product Hub, users must modify the settings in the AIAConfigurationProperties.xml file to set the Routing.EdgeApplications property of composite, QueryProductClassAndAttributesSCECommsReqABCSImpl to System ID of OPH (in the AIAConfigurationProperties.xml file, change <Property name="Routing.EdgeApplications">SEBL_01</Property> to <Property name="Routing.EdgeApplications">PIM_01</Property>) and update it to the MDS repository.
You have to setup and configure e-mail notifications in OPH. For more information about how to setup e-mail notifications, see knowledge base article, MOS Doc ID 1491286.1, "Design Studio integration with Product Hub" in My Oracle Support.
In an OOTB configuration, the Product MDM: Design Studio deployment assumes that the OPH web services are installed in the same machine as the AIA application server. However, if you have not selected this configuration, then post deployment, the AIA configuration properties must be updated with the URL for the OPH web services. The Oracle Metadata Services (MDS) database must be updated.
To verify Product MDM: Design Studio deployment:
Confirm that the Product MDM: Design Studio services were installed:
QueryClassificationListPIMCommsProvABCSImpl
QuerySpecificationValueSetListPIMCommsProvABCSImpl
To undeploy the integration 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 20-2 Undeployment Command for Product MDM: Siebel CRM
| Platform | Undeployment Command |
|---|---|
|
Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit) |
sh $AIA_HOME/pips/MDMProductDS/DeploymentPlans/undeployDS.sh |
|
Microsoft Windows (32-bit) |
%AIA_HOME%\pips\MDMProductDS\DeploymentPlans\undeployDS.bat |
Restart the SOA server.
Uninstall the integration following the instructions in Chapter 37, "Uninstalling Oracle AIA".
|
 Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
