| 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 Oracle Product Master Data Management Integration Option for Oracle E-Business Suite (Product MDM: EBS).
This chapter includes the following sections:
The DCW screens prompt you to enter the data required for successful configuration of Product MDM: EBS. Enter the details of Product MDM: EBS 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 17-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 E-Business Suite server instance. The screen contains the following fields:
Table 17-2 Oracle E-Business Suite Server Details Screen Fields
| Field | Description |
|---|---|
|
E-Business Suite Version |
This is the version of the E-Business Suite Application. Valid values for the Oracle Product Hub integration is 11.5.10.2, 12.1.1, 12.1.2 or 12.1.3. Other versions are not supported in the 3.1 release. |
|
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 __________________ |
Use this screen to enter details related to your Oracle E-Business Suite database instance. The screen contains the following fields:
Table 17-3 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. |
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 17.3 discusses configuring and deploying the Product MDM: EBS. For detailed instructions on the other MDM Product integrations, see your specific integration chapters in Part I, "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 Product MDM: EBS. Keep the completed worksheets of Product MDM: EBS screens ready before you launch the DCW.
Note:
If you are harvesting content to OER, perform the first three steps. Else start from step 4.
To configure Product MDM: EBS:
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 Oracle E-Business Suite 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 E-Business Suite Server details:
Enter information about your Oracle 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 Oracle E-Business Suite Database in the E-Business Suite Database Details 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 17.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 17-4 Deployment Commands for Product MDM: EBS
| Platform | Deployment Command |
|---|---|
|
Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit) |
sh $AIA_HOME/pips/MDMProductEbiz/DeploymentPlans/deployEbiz.sh |
|
Microsoft Windows (32-bit) |
%AIA_HOME%\pips\MDMProductEbiz\DeploymentPlans\deployEbiz.bat |
Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/MDMProductEbiz_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, 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 verify the Product MDM: EBS 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: EBS 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:
QueryResponsibilityEbizAdapter
SyncBillOfMaterialsListEbizAdapter
SyncBillOfMaterialsListEbizProvABCSImpl
SyncItemListEbizAdapter
SyncItemListEbizProvABCSImpl
TransformAppContextEbizService
For more information about the DVMs to be verified, see the Oracle Application Integration Architecture Product Master Data Management Integration Pack Implementation Guide.
All SOA composites are protected by Global Policies provided by Foundation Pack as defined in the Security section of the Developer Guide. Additionally individual services for this integration have locally attached security policies.
To validate locally attached security policies:
Log in to Oracle Enterprise Manager Fusion Middleware Control.
Navigate to WebLogic Domain, soa_domain, Web Services, Policies.
Verify Service Policy attachment.
Find the service policy in the list of policies.
Click the number in Attachment Count column.
This opens Usage Analysis screen.
Change the Subject Type list box to SOA Service.
Validate that all the composites are listed with local attachment to this service policy.
Verify Client Policy attachment
Navigate back to Policies screen and find the client policy
Click the number in Attachment Count column.
This opens Usage Analysis screen.
Change the Subject Type list box to SOA Reference.
Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.
Table 17-5 Saml Opt On Client Policy Attachments for Product MDM EBS
| Composite | Reference | Client Policy |
|---|---|---|
|
TransformAppContextEbizService |
QueryRespEbizAdapter |
oracle/aia_wss10_saml_token_client_policy_OPT_ON |
|
TransformAppContextEbizService |
AIAAsyncErrorHandlingBPELProcess |
oracle/aia_wss10_saml_token_client_policy_OPT_ON |
For integration implementation, see 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 17-6 Undeployment Command for Product MDM: EBS
| Platform | Undeployment Command |
|---|---|
|
Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit) |
sh $AIA_HOME/pips/MDMProductEbiz/DeploymentPlans/undeployEbiz.sh |
|
Microsoft Windows (32-bit) |
%AIA_HOME%\pips\MDMProductEbiz\DeploymentPlans\undeployEbiz.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 |
|
