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 Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release (Design to Release: Agile - EBS Pre-Built Integration).
This chapter includes the following sections:
Section 20.3, "Configuring and Deploying Design to Release: Agile - EBS Pre-Built Integration"
Section 20.6, "Undeploying the Design to Release: Agile - EBS Pre-Built Integration"
The DCW screens prompt you to enter the data required for successful configuration of the Design to Release: Agile - EBS Pre-Built Integration. Enter the details of the Design to Release: Agile - 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 deploy to the integration server. This screen contains the following fields:
Table 20-1 Integration Server Details Screen Fields
Field | Description |
---|---|
Admin Host Name |
Specifies where the admin server resides. This can be a remote server or the same system where the AIA Pre-Built Integrations Installer is launched. Example: The Admin Host Name is _________________________________ |
Admin Port |
This is the port number on which the Weblogic Admin server is started. To find this value contact the 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 password is _____________________________________ |
Managed Server |
After you enter the Admin Host Name, Admin Port and Admin User, this field populates with managed servers for the domain. Select the managed 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 is automatically updated 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 Agile PLM instance. The screen contains the following fields:
Table 20-2 Agile PLM Details Screen fields
Field | Description |
---|---|
Agile PLM Host |
Specifies the system name. Example: Agile PLM Host is ________________________________ |
Agile PLM Port |
This is the http port. This value depends on the web server port and operating system of your Agile PLM instance. To find this value, contact your Agile PLM administrator. Example: Agile PLM Port is ________________________________ |
Agile PLM Virtual Path |
This value is the same virtual path entered during the Agile PLM installation. Example: Agile PLM Virtual Path is _________________________ |
Agile PLM Integration Username |
This is the Agile PLM admin access user name. Example: Agile PLM Integration Username is ________________ |
Agile PLM Integration User Password |
To find this value, contact your Agile PLM administrator. Agile PLM Integration User Password is ____________ |
Agile Version |
This is a drop down list of Agile PLM Application Versions. |
Use this screen to enter details related to your Oracle E-Business Suite server instance. The screen contains the following fields:
Table 20-3 Oracle E-Business Suite Server Details Screen fields
Field | Description |
---|---|
E-Business Suite Host Name |
Specifies the system 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 _________________. This field is not used in Design to Release: Agile - EBS/PIM integration. |
E-Business Suite Version |
This is a drop down list of Oracle E-Business Suite Application versions. |
Use this screen to enter details related to your Oracle E-Business Suite database instance.The screen contains the following fields:
Table 20-4 Oracle E-Business Suite Database Details Screen fields
Field | Description |
---|---|
E-Business Suite Database Host |
Specifies the system 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 ______________________________ All the database credentials are used for creating the connection pool URL (universal resource locator) and data source URLs. |
You must modify transaction properties to complete the integration deployment. To modify transaction values:
Log in to WebLogic Server Console. Navigate to Services, JTA. Change the value of property JTA Transaction Timeout from 30 to 3600.
Change the SyncMaxWaitTime parameter as follows:
Log in to the Oracle Enterprise Manager Fusion Middleware Control.
Expand SOA folder, right click soa_infra.
Select SOA Administration, BPEL Properties.
Click link More BPEL Configuration Properties.
Change the value of SyncMaxWaitTime from 45 to 120.
Click Apply.
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 Design to Release: Agile - EBS Pre-Built Integration. Keep the completed worksheet of the Design to Release: Agile - EBS Pre-Built Integration 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 the Design to Release: Agile - EBS Pre-Built Integration:
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.
In the setDomainEnv.sh (or .bat) file, perform a search for USER_MEM_ARGS. Go to the second instance found and replace the following lines:
USER_MEM_ARGS="-Xms2048m -Xmx2048m -XX:PermSize=256 -XX:MaxPermSize=256 -XX:NewSize=1228 -XX:MaxNewSize=1228"
WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false"
with the following changes
USER_MEM_ARGS="-Xms2048m -Xmx2048m -XX:PermSize=256m -XX:MaxPermSize=512m -XX:NewSize=1228m -XX:MaxNewSize=1228m"
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 the 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 the Design to Release: Agile - EBS / PIM PIP
Click Next.
To specify integration server details:
Enter information related to your integration server in the Integration Server Details screen.
Click Next.
Enter information about your Agile PLM installation in the Agile PLM Details screen.
Click Next.
To specify Oracle E-Business Suite Server details:
Enter information about your Oracle E-Business Suite Server installation 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 installation 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 20.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 the configuration.
The system displays progress of the 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 completes 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:
When you copy and paste the command in the command line, ensure that there is space between .xml
and -
. Ensure that there is space between these two when you run un-deployment command too.
Table 20-5 Deployment Command for the Design to Release: Agile - EBS Pre-Built Integration
Platform | Deployment Command |
---|---|
Linux Solaris SPARC HP-UX IBM AIX Based Systems |
ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>/pips/AgileToEbiz/DeploymentPlans/AgileToEbizDP.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<instancename>/config/AIAInstallProperties.xml -DDeploymentPolicyFile=<AIA_HOME>/pips/AgileToEbiz/DeploymentPlans/AgileToEbizConditionalPolicy.xml -DSupplementaryDeploymentPlan=<AIA_HOME>/pips/AgileToEbiz/DeploymentPlans/AgileToEbizSupplementaryDP.xml -l <AIA_HOME>/pips/AgileToEbiz/DeploymentPlans/AgileToEbizDP.log |
Microsoft Windows |
ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>\pips\AgileToEbiz\DeploymentPlans\AgileToEbizDP.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<aia instance>\config\AIAInstallProperties.xml -DDeploymentPolicyFile=<AIA_HOME>\pips\AgileToEbiz\DeploymentPlans\AgileToEbizConditionalPolicy.xml -DSupplementaryDeploymentPlan=<AIA_HOME>\pips\AgileToEbiz\DeploymentPlans\AgileToEbizSupplementaryDP.xml -l <AIA_HOME>\pips\AgileToEbiz\DeploymentPlans\AgileToEbizDP.log |
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.
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 the Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".
After configuration of the EBS is complete, you must enable security in the three concurrent programs of the Design to Release: Agile - EBS Pre-Built Integration. To complete this task, perform the following steps:
Set the value for Profile Option:
Profile Option Short Name as INV_EBI_SOASERVER_USER.
Profile Option Display Name as EBS Integration: SOA SERVER USER.
Set the SOA Password using the SQL script: inveipwd.sql
.
The file is located in EBS APPLICATION_TOP in the following folder: APPL_TOP/inv/12.0.0/patch/115/sql/inveipwd.sql.
Copy the file to your local directory.
Run the file in the database.
You are prompted to enter the password for the SOA user to be encoded and stored. (This is used by Business Event to invoke RequestorABCS.) The password is stored in FND_VAULT under the module EBI and Vault Key INV_EBI_SOA_PASSWORD.
To verify the Design to Release: Agile - EBS Pre-Built Integration deployment:
Open the log files from the following location and look for warnings and error messages:
For Linux, Solaris SPARC, HP-UX and IBM AIX Based Systems: Review the install log located at <AIA_HOME>/aia_instances/<instance name>/logs to verify that the integration is successfully installed.
For Microsoft Windows: Review the install log located at <AIA_HOME>\aia_instances\<instance name>\logs to verify that the integration is successfully installed.
Confirm that the Design to Release: Agile - EBS / PIM Pre-Built Integration queue was installed.
Navigate to the PLM integration Queue Management console (http://<server name>:<port number>/queue).
Log in with the server admin user name. For access details, contact the system administrator.
Confirm that the Design to Release: Agile - EBS / PIM Pre-Built Integration processes 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:
Note:
Services marked as x are not available.
Table 20-6 Design to Release: Agile - EBS Pre-Built Integration ESB Services
Mediator Services | 12.1.x with PIM + 9.3x with VM | 12.1.x with PIM + 9.3x | 12.1.x with PIM + 922x | 12.1.x + 93x with VM | 12.1.x + 93x | 12.1.x + 922x | 11.5.10 + 93x | 11.5.10. + 922x |
---|---|---|---|---|---|---|---|---|
EBS |
||||||||
BillOfMaterialsConfigurationEBS |
x |
x |
x |
x |
x |
x |
||
EngineeringChangeOrderEBS |
||||||||
EngineeringChangeOrderResponseEBS |
||||||||
ItemBalanceEBS |
||||||||
ItemBalanceResponseEBS |
||||||||
ItemResponseEBSV2 |
x |
x |
||||||
Adapter Services |
||||||||
UpdateEngineeringChangeOrderStatusEbizEventConsumer |
||||||||
QueryEngineeringChangeOrderListEbizAdapter |
||||||||
QueryItemBalanceListEbizAdapter |
||||||||
QueryItemListEbizAdapter |
||||||||
QueryResponsibilityEbizAdapter |
x |
x |
||||||
SyncBillOfMaterialsConfigurationEbizJMSConsumer |
x |
x |
x |
x |
x |
x |
||
SyncBillOfMaterialsConfigurationEbizJMSProducer |
x |
x |
x |
x |
x |
x |
||
SyncItemListEbizAdapter |
x |
x |
||||||
ValidateEngineeringChangeOrderListEbizAdapter |
x |
x |
||||||
Agile > ECOQueue |
||||||||
ACSJMSConsumer |
Also check for the items in Table 20-7.
Note:
Processes marked as x are not available.
Table 20-7 Design to Release: Agile - EBS Pre-Built Integration processes
BPEL Processes | 12.1.x with PIM + 9.3x with VM | 12.1.x with PIM + 9.3x | 12.1.x with PIM + 922x | 12.1.x + 93x with VM | 12.1.x + 93x | 12.1.x + 922x | 11.5.10 + 93x | 11.5.10. + 922x |
---|---|---|---|---|---|---|---|---|
CreateEngineeringChangeOrderListEbizProvABCSImpl |
||||||||
CreateQueueService |
||||||||
GenerateItemNumberService |
x |
x |
x |
x |
x |
|||
GetConfiguratorURLEbizProvABCSImpl |
x |
x |
x |
x |
x |
x |
||
GetConfiguratorURLAgileReqABCSImpl |
x |
x |
x |
x |
x |
x |
||
ProcessEngineeringChangeOrderAgileReqABCSImpl |
||||||||
QueueProcessorServiceImpl |
||||||||
SyncBOMConfigurationAgileProvABCSImpl |
x |
x |
x |
x |
x |
x |
||
SyncBillOfMaterialsConfigurationListEbizReqABCSImpl |
x |
x |
x |
x |
x |
x |
||
SyncItemListAgileReqABCS |
x |
x |
||||||
SyncItemListAgileReqABCSImpl |
x |
x |
||||||
SyncItemListEbizProvABCSImpl |
x |
x |
||||||
UpdateEngineeringChangeOrderListAgileProvABCSImpl |
||||||||
UpdateEngineeringChangeOrderListEbizReqABCSImpl |
||||||||
UpdateItemBalanceListAgileProvABCSImpl |
||||||||
UpdateItemBalanceListEbizReqABCSImpl |
||||||||
UpdateItemListAgileProvABCSImpl |
||||||||
UpdateItemListEbizReqABCSImpl |
||||||||
ValidateEngineeringChangeOrderListAgileReqABCSImpl |
x |
x |
||||||
ValidateEngineeringChangeOrderListEbizProvABCSImpl |
x |
x |
Note:
IF EBS is down, the GenerateItemNumberService does not deploy. An error is generated for the deployment of this service.
Confirm that the AIA Foundation Manager components were successfully installed.
Navigate to the AIA Console URL: http://<server name>:<port number>/AIA
.
Log in with server admin user name.
Navigate to Setup, System to access the Application Registry page.
Check the rows for the following sets of values:
Table 20-8 Application Registry Values for Agile
Field | Value |
---|---|
Internal ID |
AGILE_01 |
System Code |
AGILE_01 |
System Description |
Agile PLM Instance 01 |
IP Address |
IP address of the Agile PLM system |
URL |
URL of the Agile PLM system |
System Type |
Agile |
Application Type |
PLM |
Version |
9226 (Out of the Box) This can be edited to appropriate version of Agile PLM. |
Table 20-9 Application Registry Values for EBS Agile
Field | Value |
---|---|
Internal ID |
Database SID (Example: M00MQ102) |
System Code |
EBIZ_01 |
System Description |
Oracle E-Business Suite Instance 01 |
IP Address |
IP address of the EBS system |
URL |
URL of the EBS system |
System Type |
Ebiz |
Application Type |
EBIZ_01 |
Version |
Oracle E-Business Suite Version (Example: 11.5.10, 12.1.x, 12.1.x with PIM) |
For information on validating security policies, see Oracle Application Integration Architecture Design to Release: Agile - EBS Implementation Guide, "Security Policies Validation".
For more information about security validation, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Working with Security."
For integration implementation, see Oracle Application Integration Architecture Design to Release: Agile - EBS 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 20-10 Un-deployment Command for the Design to Release: Agile - EBS Pre-Built Integration
Platform | Un-deployment Command |
---|---|
Linux Solaris SPARC HP-UX IBM AIX Based Systems |
ant Uninstall -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<AIA_Instance_name>/config/AIAInstallProperties.xml -DDeploymentPlan=<AIA_HOME>/pips/AgileToEbiz/DeploymentPlans/AgileToEbizDPUndeployDP.xml -DDeploymentPolicyFile=<AIA_HOME>/pips/AgileToEbiz/DeploymentPlans/AgileToEbizConditionalPolicyUndeploy.xml -DSupplementaryDeploymentPlan=<AIA_HOME>/pips/AgileToEbiz/DeploymentPlans/AgileToEbizSupplementaryUndeployDP.xml -l <AIA_HOME>/pips/AgileToEbiz/DeploymentPlans/AgileToEbizUndeployDP.log |
Microsoft Windows |
ant Uninstall -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<AIA_Instance_name>\config\AIAInstallProperties.xml -DDeploymentPlan=<AIA_HOME>\pips\AgileToEbiz\DeploymentPlans\AgileToEbizDPUndeployDP.xml -DDeploymentPolicyFile=<AIA_HOME>\pips\AgileToEbiz\DeploymentPlans\AgileToEbizConditionalPolicyUndeploy.xml -DSupplementaryDeploymentPlan=<AIA_HOME>\pips\AgileToEbiz\DeploymentPlans\AgileToEbizSupplementaryUndeployDP.xml -l <AIA_HOME>\pips\AgileToEbiz\DeploymentPlans\AgileToEbizUndeployDP.log |
Restart the SOA server.
Uninstall the integration following the instructions in Chapter 37, "Uninstalling Oracle AIA".