| Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.1 Part Number E23118-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.1 Part Number E23118-04 |
|
|
PDF · Mobi · ePub |
This chapter discusses how to configure and deploy the Oracle Communications Billing and Revenue Management Integration Pack for Oracle EBusiness Suite: Revenue Accounting (Comms Revenue Accounting: BRM - EBS Pre-Built Integration).
This chapter includes the following sections:
Prerequisite/Assumption: The Master Repository and the Work Repository are created in ODI
You need not create a master repository. You can use an existing master repository if it exists on an Oracle database and the ID is between 126 and 999. If you are creating a new master repository, ensure that the repository ID is between 126 and 999.
You can use an existing work repository if it exists on an Oracle database and its ID is between 126 and 999. If its ID is not in that range, AIA advises you to create a repository with an ID between 126 and 999.
Table 5-1 details a list of ids you must avoid when creating master and work repositories.
When you run the DCW, it inserts or updates the integration artifacts into these repositories.
AIA recommends that you take a backup of master and work repositories before you start the install process.
For information about creating Oracle Data Integrator Master and Work repositories, see the Oracle Data Integrator Installation Guide, "Creating Repositories."
The DCW screens prompt you to enter the data required for successful configuration of the Comms Revenue Accounting: BRM - EBS Pre-Built Integration. Enter the details of the Comms Revenue Accounting: BRM - EBS Pre-Built Integration 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 are deployed to the integration server. This screen contains the following fields:
Table 5-2 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 E-Business Suite server instance. The screen contains the following fields:
Table 5-3 Oracle E-Business Suite Server Details Screen Fields
| Field | Description |
|---|---|
|
E-Business Suite Host Name |
This value is the fully qualified computer name of the Oracle E-Business Suite application. Example: E-Business Suite Host Name is ___________________________ |
|
E-Business Suite Port |
This value is the Oracle E-Business Suite application port. To find this value, contact your administrator. Example: E-Business Suite Port is _______________________________ |
|
E-Business Suite User Name |
To find this value, contact your administrator. E-Business Suite User Name is ___________________________ |
|
E-Business Suite Password |
To find this value, contact your administrator. E-Business Suite Password is ____________________________ |
|
Workflow Business Event System Name |
This is the Workflow Business Event System Name of E-Business Suite Server. For example: Workflow Business Event System Name is __________________ |
|
E-Business Suite Version |
Examples: 11.5.10 or 12.1.1. E-Business Suite version is __________________________ |
Use this screen to enter details related to your Oracle E-Business Suite database instance. The screen contains the following fields:
Table 5-4 Oracle E-Business Suite Database Details Screen Fields
| Field | Description |
|---|---|
|
E-Business Suite Database Host |
This value is typically the computer name. To find this value, contact the database administrator. Example: E-Business Suite Database Host is ________________________ |
|
E-Business Suite Database Port |
To find this value, contact the database administrator. Example: E-Business Suite Database Port is _____________________ |
|
E-Business Suite Database Username |
To find this value, contact the database administrator. Example: E-Business Suite Database Username is ___________________ |
|
E-Business Suite Database Password |
To find this value, contact the database administrator. E-Business Suite Database Password is ___________________ |
|
E-Business Suite Database SID (System ID) |
To find this value, contact the database administrator. Example: E-Business Suite Database SID is ________________________ |
|
Database Schema |
To find this value, contact the database administrator. Example: Database Schema is __________________________________ Note: All the database credentials are used for creating the connection pool URL and data source URLs. |
Use this screen to enter details related to your Oracle Communications BRM instance. The screen contains the following fields:
Table 5-5 Oracle Communications BRM Screen Fields
| 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 _________________________________ |
Prerequisite/Assumption: Master Repository and the Work Repository are created in ODI,
Use these screens to enter details to access Oracle Data Integrator.
These screens contain the following fields:
Table 5-6 Oracle Data Integrator Access Information Details Screens Fields
| Field | Description |
|---|---|
|
Path to Oracle Data Integrator |
Provide the path to the ODI_HOME up to the oracledi/agent folder (included). To find this value, contact your administrator. Example: Path to Oracle Data Integrator is ___________________________ |
|
Path for exported DVMs |
Enter the path of the directory to export Domain Value Mappings (DVM). DVM folder gets created along with Foundation Pack installation. If you have installed Foundation Pack use If you are installing the integration along with Foundation Pack for the first time, create a temporary folder for the DVMs. DVMs are exported to this location. If you want to change the path to reflect the above location, open Path for exported DVMs is ______________________________ |
|
ODI Username |
To find this value, contact your administrator. Example: ODI Username is ____________________________________ |
|
ODI User Password |
To find this value, contact your administrator. Example: ODI User Password is _________________________________ |
You must set up an ODI Master Repository before installing the Comms Revenue Accounting: BRM - EBS Pre-Built Integration. This master repository must be created in an Oracle database.
Note:
If you are using either a new master repository or an existing master repository, you must ensure that the identifier for that repository is between 126 and 999.
The install process appends integration artifacts into this master repository.
Use this screen to enter details to access the Oracle Data Integrator Master Repository. If the Master repository is configured, field values in the screen are populated automatically.
The screen contains the following fields:
Table 5-7 Oracle Data Integrator Master Repository Details Screen Fields
| Field | Description |
|---|---|
|
Database Host |
To find this value, contact your database administrator. Example: Database Host is_______________________________ |
|
Database Port |
To find this value, contact your database administrator. Example: Database Port is________________________________ |
|
Database SID |
To find this value, contact your database administrator. Example: Database SID is__________________________________ |
|
Database Username |
To find this value, contact your database administrator. Example: Database Username is_______________________________ |
|
Database Password |
To find this value, contact your database administrator. Example: Database Password is_________________________________ |
The install process imports the Comms Revenue Accounting: BRM - EBS Pre-Built Integration ODI artifacts into an ODI Work repository. You can provide an existing ODI Work Repository or provide an empty one. It is recommended that you use an empty repository.
Note:
If you are creating either an existing work repository or a new work repository, you must ensure that the repository is created with an ID is between 126 and 999.
Use this screen to enter details related to the ODI Work Repository. If the Master repository is configured, field values in the screen are populated automatically.
The screen contains the following fields:
Table 5-8 Oracle Data Integrator Work Repository Details for Revenue Accounting Screen Fields
| Field | Description |
|---|---|
|
ODI Work Repository Name |
Enter the name you gave to the ODI Work Repository for integration Artifacts. Example: ODI Work Repository Name is ___________________________ |
|
ODI Work Repository ID |
Enter the ID number that you used for the ODI Work Repository. ODI Work Repository ID is ______________________________ |
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 Comms Revenue Accounting: BRM - EBS Pre-Built Integration. Keep the completed worksheets of the Comms Revenue Accounting: BRM - EBS Pre-Built Integration screens ready before you launch the DCW.
To configure the Comms Revenue Accounting: BRM - EBS Pre-Built Integration:
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.
Expand Communications Pre-built Integrations and select Comms Revenue Accounting: BRM - EBS.
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 E-Business Suite Server details:
Enter information about your E-Business Suite Server in the E-Business Suite Server Details screen.
Click Next.
To specify Oracle E-Business Suite Database details:
Enter information about your E-Business Suite Database in the E-Business Suite Database Details screen.
Click Next.
To specify Oracle Communications BRM details:
Enter Oracle Communications BRM information in the Oracle Communications BRM screen.
Click Next.
To specify Oracle Data Integrator Access details:
Enter information about your Oracle Data Integrator Access installation in the Oracle Data Integrator Access Information screens.
Oracle Data Integration Access Information is captured in three screens. Enter the following information in the screens.
Specify path to Oracle Data Integrator.
Click Next.
Specify the path for exported DVMs.
Click Next.
Enter ODI User name and ODI User Password.
Click Next.
To specify Oracle Data Integrator Master Repository details:
Enter information about your Oracle Data Integrator Master Repository installation in the Oracle Data Integrator Master Repository screen.
Click Next.
To specify Oracle Data Integrator Work Repository details:
Enter information about your Oracle Data Integrator Work Repository installation in the Oracle Data Integrator Work Repository Details for Revenue Accounting 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 5.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 configuration process finishes without errors, 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 5-9 Deployment Commands for the Comms Revenue Accounting Pre-Built Integration
| Platform | Deployment Command |
|---|---|
|
Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit) |
$AIA_HOME/pips/Communications/RA/DeploymentPlans/deployRA.sh |
|
Microsoft Windows (32-bit) |
%AIA_HOME\pips\Communications\RA\DeploymentPlans\deployRA.bat |
Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/RADP_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 AIA Installer Driver (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 the Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".
To verify the Comms Revenue Accounting: BRM - EBS Pre-Built Integration 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.
Navigate to <AIAHome>/DISHome and verify whether the following folders have been created:
RevenueManagementHome
RevenueManagementHome/input
RevenueManagementHome/input/schema
RevenueManagementHome/success
RevenueManagementHome/failure
Verify whether CurrencyCodeMapping.xml is present in the DVM path. This is the same path that is mentioned during installation. You can find this path in deploy.properties file under the property 'odi.dvm.path.
Check <AIAHome>/DISHome/RevenueManagementHome/input/schema and find brm_gl_data.xsd.
Open <AIA_Instance>/logs/RADP_Deployments_YYYY-MM-DD_HH-MI-SS.log. The log contains several statements starting with "[exec] OracleDI: Starting Command: OdiImportObject -FILE_NAME=". None of these statements should be followed by error messages except the error messages mentioned in Section 5.4.1, "Error Messages During Comms Revenue Accounting: BRM - EBS Pre-Built Integration Deployment".
When deploying the Comms Revenue Accounting: BRM - EBS Pre-Built Integration, you can encounter the following errors:
Failed to execute: Create user xxxxx identified by yyyyy
Unique Constraint Violation
AIA Pre-Built Integrations Installer displays this error message in the log file if the install script attempts to create a database user name for an existing database user name. You can ignore this message and continue with the install process.
The AIA Pre-Built Integrations Installer displays the following message when it finds an identical database user name:
Example 5-1 Identical Database User Name Message
ODIInstall_CreateDBSchemaWorkRep: [echo] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [echo] Creating ODI Work Repository DB User: xxxxx [sql] Executing commands [sql] Failed to execute: create user xxxxx identified by yyyyy [sql] java.sql.SQLException: ORA-01920: user name 'xxxxx' conflicts with another user or role name [sql] 1 of 2 SQL statements executed successfully [echo] Done creating DB User for ODI Work Repository: xxxxx [echo] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Note:
xxxxx refers to the database user name provided for ODI Work Repository and yyyyy is the password.
AIA Pre-Built Integrations Installer displays this error message in the log file if the ODI data source xxxxx exists in the ODI master repository. The ODI data source is defined in Topology in the Physical Architecture tab. This error occurs when the Comms Revenue Accounting: BRM - EBS Pre-Built Integration is reinstalled.
The AIA Pre-Built Integrations Installer displays the following message when it finds an identical ODI data source:
Example 5-2 Identical ODI Data Source Message
[echo] - Importing CONN_xxxxx.xml [exec] OracleDI: Starting Command: OdiImportObject -FILE_NAME=<AIA_HOME>/PIPS/Industry/Communications/DIS/Revenue/src/master/CONN_xxxxx.xml -IMPORT_MODE=SYNONYM_INSERT_UPDATE ... [exec] java.sql.SQLException: ORA-00001: unique constraint (SNPM.PK_MTXT) violated
This error does not stop the install process. The process imports the remaining ODI integration artifacts into the ODI; however, it is important to verify the accuracy of the connections for these ODI data sources. To resolve this issue, verify that the connections and associated logical schemas in the ODI topology are accurate.
This feature is not available for the Comms Revenue Accounting: BRM - EBS Pre-Built Integration.
|
 Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
