| Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.3 Part Number E28316-03 |
|
|
PDF · Mobi · ePub |
| 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 the Oracle Product Master Data Management Integration Option for Oracle Communications Billing and Revenue Management (Product MDM: Comms BRM).
This chapter includes the following sections:
Section 18.2, "Overall Configuration and Deployment of MDM Product Integrations"
Section 18.3, "Configuring and Deploying Product MDM: Comms BRM"
The DCW screens prompt you to enter the data required for successful configuration of the Product MDM: Comms BRM. Enter the details of the Product MDM: Comms BRM screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.
All artifacts associated with the integration infrastructure components deploy to the integration server. This screen contains the following fields:
Table 18-1 Integration Server Details Screen Fields
| Field | Description |
|---|---|
|
Admin Host Name |
This is where the admin server resides. This can be a remote server or the same computer where the AIA Pre-Built Integrations Installer is launched. Example: The Admin Host Name is _________________________________ |
|
Admin Port |
This is the port number on which Weblogic Admin server is started. To find this value contact WebLogic administrator. Example: The Admin Port is _____________________________________ |
|
Domain Name |
This is WebLogic server domain corresponding to the Admin Server. Example: The Domain Name is _____________________________________ |
|
Admin User |
This value is the WebLogic admin user name. To find this value contact your WebLogic administrator. The Admin User is __________________________________ |
|
Admin Password |
This value is the WebLogic admin password. To find this value contact your WebLogic administrator. The Admin Password is _____________________________________ |
|
Managed Server |
After you enter the Admin Host name, Admin Port, Domain Name, Admin user name and Admin Password, this field gets populated with managed servers for the domain. Select the manager server from the list. If you are deploying the integration to a SOA cluster, you should select the cluster name in this field. The Managed Server is _______________________________ |
|
Managed Port |
This field gets updated automatically after you select the managed server. If you have configured a SOA Cluster the SOA Cluster port appears in the list. |
Use this screen to enter details related to your Oracle Communications BRM instance. The screen contains the following fields:
Table 18-2 Oracle Communications BRM Details Screen
| Field | Description |
|---|---|
|
Primary CM Host Name |
This is the host name of the primary Connection Manager (CM) of the BRM server. For example: Primary CM Host Name is ______________________________ |
|
Primary CM Port Number |
This is the port number of primary Connection Manager (CM) of the BRM server. For example: Primary CM Port Number is ______________________________ |
|
Database Host |
This is the database host name of the Oracle AQ for which the BRM DM_AQ is configured. For example: Database Host is _______________________ |
|
Database Port |
This is the database port number of the Oracle AQ. For example: Database Port is _________________________ |
|
Oracle AQ Database SID |
This is the database instance of the Oracle AQ. For example: Oracle AQ Database SID is _______________________________ |
|
Oracle AQ Username |
This is the database user name of the Oracle AQ. For example, PIN7820. To find this value, contact your Oracle AQ administrator. Oracle AQ Username is _________________________ Note: This value must be in uppercase (PIN7820) for the OOTB PLM flow to work. |
|
Oracle AQ Password |
This is the database password of the Oracle AQ. To find this value, contact your Oracle AQ administrator. Oracle AQ Password is ___________________________ |
|
AQ Queue Name |
This is the queue name configured for the BRM DM_AQ. For example: AQ Queue Name is _________________________________ |
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. Section 18.3 discusses configuring and deploying the Product MDM: Comms BRM. For detailed instructions on the other 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 Chapter 19, "Deploying Product MDM: Routing Rules". Routing Rules wire the integration services, depending on the integrations deployed.
This section discusses the integration configuration and deployment process. There are two steps:
Configure your integration using the DCW.
Deploy the integration to the Fusion Middleware server.
The screens that appear prompt you to enter the data that is required for successful configuration of the Product MDM: Comms BRM option. Keep the completed worksheets of the Product MDM: Comms BRM option screens ready before you launch the DCW.
To configure the Product MDM: Comms BRM:
Note:
If you are harvesting content to Oracle Enterprise Repository (OER), perform the first three steps. Else start from step 4.
Navigate to /slot/emsxxxx/oracle/Middleware/user_projects/domains/soa_domain/bin/ and open setDomainEnv.sh for Linux based systems and setDomainEnv.bat for Microsoft Windows.
Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".
Restart the 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 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 DCW.
Click Next.
Select Oracle Product Master Data Management Integration Option for BRM under Product Master Data Management Pre-Build Integration
Click Next.
To specify integration server details:
Enter information related to your integration server in the Integration Server Details screen.
Click Next.
To specify Oracle Communications BRM details:
Enter Oracle Communications BRM information in the Oracle Communications BRM screen.
Click Next.
Review the configuration information on the Configuration Summary screen.
Note:
If you want to make changes to the configuration, use the navigation pane on the left and select the screen you want to edit.
You can create a response file based on the input provided in the DCW and use it in future when you want to deploy the integration. You can configure using the steps described in Section 18.3.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.
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 18-3 Deployment Commands for the Product MDM: Comms BRM
| Platform | Deployment Command |
|---|---|
|
Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit) |
sh $AIA_HOME/pips/MDMProductBRM/DeploymentPlans/deployMDMProductBRM.sh |
|
Microsoft Windows (32-bit) |
%AIA_HOME%\pips\MDMProductBRM\DeploymentPlans\deployMDMProductBRM.bat |
Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/MDMProductBRMDP_Deployments_YYYY-MM-DD_HH-MI-SS.log to verify successful deployment of the integration.
Oracle AIA ships a few artifacts in AIA Lifecycle Workbench which can be used in your integrations. These native artifacts created using FMW technologies such as BPEL, Mediator are natively supported by AIA Foundation Pack tools such as Project Lifecycle Workbench, Harvester, Deployment Generator and AID. These artifacts include SOA artifact types such as composites, DataSources, DVM, xRef, and so on. These can be modified or new natively supported artifacts can be added using AIA Lifecycle Workbench and a BOM.xml file can be generated.
Integrations, most often, also require deployment of artifact types that are beyond what is supported by the Project Lifecycle Workbench and AIA Harvester. For instance, you may want to deploy 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 verify the Product MDM: Comms BRM 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: Comms BRM 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:
SyncItemListBRMProvABCSImpl
SyncPriceListListBRMProvABCSImpl
For more information about the DVMs to be verified, see the Oracle Application Integration Architecture Product Master Data Management Integration Pack Implementation Guide
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 18-4 Undeployment Command for the Product MDM: Comms BRM
| Platform | Undeployment Command |
|---|---|
|
Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit) |
sh $AIA_HOME/pips/MDMProductBRM/DeploymentPlans/undeployMDMProductBRM.sh |
|
Microsoft Windows (32-bit) |
%AIA_HOME%\pips\MDMProductBRM\DeploymentPlans\undeployMDMProductBRM.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 |
|
