21 Configuring and Deploying Design to Release: Agile - EBS

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 21.1, "Deployment Configuration Wizard"
Section 21.2, "Performing Predeployment Configurations"
Section 21.3, "Configuring and Deploying Design to Release: Agile - EBS Pre-Built Integration"
Section 21.4, "Performing Postdeployment Configurations"
Section 21.5, "Verifying Deployment"
Section 21.6, "Undeploying the Design to Release: Agile - EBS Pre-Built Integration"

21.1 Deployment Configuration Wizard

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.

21.1.1 Integration Server Details Screen

All artifacts associated with the integration infrastructure components deploy to the integration server. This screen contains the following fields:

Table 21-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: `server1.company.com.` 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: `7001`. The Admin Port is _____________________________________
Domain Name	This is WebLogic server domain corresponding to the Admin Server. Example: `domain1` 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.

21.1.2 Agile PLM Details Screen

Use this screen to enter details related to your Agile PLM instance. The screen contains the following fields:

Table 21-2 Agile PLM Details Screen fields

Field	Description
Agile PLM Host	Specifies the system name. Example: `example1.corp.oracle.com`. 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: `80`. Agile PLM Port is ________________________________
Agile PLM Virtual Path	This value is the same virtual path entered during the Agile PLM installation. Example: `Agile`. Agile PLM Virtual Path is _________________________
Agile PLM Integration Username	This is the Agile PLM admin access user name. Example: `admin`. 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. Note: This drop down list may contain older versions of Agile PLM which are not supported by the PIP. To ensure that you have selected the right version of Agile PLM, see Chapter 2, "Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release."

21.1.3 Oracle E-Business Suite Server Details Screen

Use this screen to enter details related to your Oracle E-Business Suite server instance. The screen contains the following fields:

Table 21-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: `example1.corp.oracle.com`. 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: `8024`. 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: `SID.server2.xyz.com.` To find this value, contact your administrator. 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. Note: This drop down list may contain older versions of Oracle E-Business Suite which are not supported by the PIP. To ensure that you have selected the right version of Oracle E-Business Suite A, see Chapter 2, "Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release."
E-Business Suite Protocol for web services	This is a drop down list with options http or https for the protocols used to invoke webservices on E-Business Suite. To find this value, contact your administrator.

21.1.4 Oracle E-Business Suite Database Details Screen

Use this screen to enter details related to your Oracle E-Business Suite database instance.The screen contains the following fields:

Table 21-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: `server1.oracle.com`. E-Business Suite Database Host is ___________________
E-Business Suite Database Port	To find this value, contact the database administrator. Example: `1521`. E-Business Suite Database Port is ___________________
E-Business Suite Database Username	To find this value, contact the database administrator. Example: `apps`. 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: `orcl`. E-Business Suite Database SID is _________________________
Database Schema	To find this value, contact the database administrator. Example: `apps`. Database Schema is ______________________________ All the database credentials are used for creating the connection pool URL (universal resource locator) and data source URLs.

21.1.5 Design to Release: Agile - EBS Configurations Screen

Use this screen to enter details related to your new schema to be created for the PIP queue tables and Oracle EBS to Agile PLM Initial Load instance. The screen contains the following fields:

Note:

The PIP schema details listed in Table 21-5 applies only for fresh install of AIA 11.5. These details will not be considered for other releases and upgrade to AIA 11.5.

Table 21-5 PIP Schema Details

Field	Description
PIP Schema Name	Enter the name of the new schema to be created for the PIP queue tables. Default Value is plmpip.
PIP Schema password	Create a password for the schema.
Reconfirm PIP Schema password	Confirm the new password that you created.

Table 21-6 Item Initial Load Data Locations

Field	Description
Location to store XML files containing item data from E-Business Suite	This is the location where AIA stores the XML files that contain Initial Load Item data from Oracle E-Business Suite.
Location to pick up Item Data XML files for loading into Agile PLM	This is the location from where AIA picks up the Initial Load Item data XML files for loading into Agile PLM. This location option enables you to review and improve the data before loading into Agile.
Location to store the failed Item Data XML files	This is the location of the Item Data XML files that failed to load into Agile.
Location to store the successful Item Data XML files	This is the location of the Item Data XML files that were successfully loaded into Agile.

21.2 Performing Predeployment Configurations

Configure https enabled Ebiz (Optional)

Obtain the Ebiz environment certificate from the following path: $ORACLE_HOME/appsutil/wallet
Import this Ebiz certificate to the WebLogic server. To import this Ebiz certificate, follow these steps:
1. Add the keytool to classpath as export CLASSPATH=/slot/ems3486/oracle/Middleware/jrockit-jdk1.6.0_37-R28.2.5-4.1.0/bin:$CLASSPATH
2. Copy the Ebiz certificate to FMW server.
3. Import the certificate to WebLogic keystore as
  
  keytool -import -noprompt -trustcacerts -alias rws3221070 -file /slot/ems3486/oracle/EBSCertificate/ca.cer -keystore /slot/ems3486/oracle/Middleware/jrockit-jdk1.6.0_37-R28.2.5-4.1.0/jre/lib/security/cacerts -storepass changeit
  
  For example, keytool -import -noprompt -trustcacerts -alias <name> -file <path of fmw where you copied ebiz certificate> -keystore $MW_HOME/jrockit-jdk1.6.0_37-R28.2.5-4.1.0/jre/lib/security/cacerts -storepass <wls store password>
4. Verify this by listing the certificates in keystore as keytool -list -keystore /slot/ems3486/oracle/Middleware/jrockit-jdk1.6.0_37-R28.2.5-4.1.0/jre/lib/security/cacerts

Modify transaction values

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:
1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.
2. Expand SOA folder, right click soa_infra.
3. Select SOA Administration, BPEL Properties.
4. Click link More BPEL Configuration Properties.
5. Change the value of SyncMaxWaitTime from 45 to 120.
6. Click Apply.

21.3 Configuring and Deploying Design to Release: Agile - EBS Pre-Built Integration

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.

21.3.1 Configuring the Design to Release: Agile - EBS Pre-Built Integration

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, replace the following line:

WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false"

with the following changes

WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

Note:

The values specified are baseline values. You can modify the values to improve performance. Your server class machines must have 8GB RAM or more of available space for the above memory settings to be valid.
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 Design to Release: Agile - EBS under Product Lifecycle Management Pre-Built Integrations.
Click Next.

21.3.1.1 Specify Integration Server Details

To specify integration server details:

Enter information related to your integration server in the Integration Server Details screen.
Click Next.

21.3.1.2 Specify Oracle E-Business Suite Server Details

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.

21.3.1.3 Specify Oracle E-Business Suite Database Details

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.

21.3.1.4 Specify Agile PLM Application Details

To specify Agile PLM details:

Enter information about your Agile PLM installation in the Agile PLM Details screen.
Click Next.

21.3.1.5 Specify Design to Release: Agile - EBS Configurations Screen

To specify Design to Release: Agile - EBS Configurations Screen Details

Enter information about your PIP Schema Details from Design to Release: Agile - EBS Configurations installation in the Design to Release: Agile - EBS Configurationsscreen.
Enter information about your Item Initial Load Data Locations from Design to Release: Agile - EBS Configurations installation in the Design to Release: Agile - EBS Configurations screen.
Click Next.

21.3.1.6 Complete Configuration

To complete configuration:

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 21.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.

21.3.2 Configuring using the Response File

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.

21.3.3 Prerequisite for E-Business Suite version 12.2.0 or later

To install Design to Release: Agile - EBS Pre-Built Integration PIP 11.3 with E-Business Suite version 12.2.0 or later, you must perform the following steps before installing the PIP:

Navigate to $AIA_INSTANCE/config/AIAInstallProperties.xml
Add the following property for the endpoint URI under properties/participatingapplications/ebiz
- generateitemnumberservicewsdlurl - WSDL URL for the Generate Item Number service on the EBS ISG server. For example, http://rws3220107.example.com:16043/soa-infra/services/default/XZ1ST222_BSO_inv_ebi_item_GenerateItemNumberService/GenerateItemNumberService_Service?wsdl
- generateitemnumberserviceendpointuri Endpoint URI of the Genenerate Item Number service on the the EBS ISG server. For example, http://rws3220107.example.com:16043/soa-infra/services/default/XZ1ST222_BSO_inv_ebi_item_GenerateItemNumberService/GenerateItemNumberService_Service

21.3.4 Deploying the Design to Release: Agile - EBS Pre-Built Integration

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.

Table 21-7 Deployment Command for the Design to Release: Agile - EBS Pre-Built Integration

Platform	Deployment Command
Linux Solaris SPARC HP-UX IBM AIX Based Systems	sh $AIA_HOME/pips/AgileToEbiz/DeploymentPlans/AgileToEbizDP.sh
Microsoft Windows	%AIA_HOME%\pips\AgileToEbiz\DeploymentPlans\AgileToEbizDP.bat

Platform

Deployment Command

Linux

Solaris SPARC

HP-UX

IBM AIX Based Systems

sh $AIA_HOME/pips/AgileToEbiz/DeploymentPlans/AgileToEbizDP.sh

Microsoft Windows

%AIA_HOME%\pips\AgileToEbiz\DeploymentPlans\AgileToEbizDP.bat

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 Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".

21.4 Performing Postdeployment Configurations

This sections describes the postdeployment tasks you must perform after configuring the Design to Release: Agile - EBS Pre-Built Integration. This section includes the following topics:

Section 21.4.1, "Cluster Installation"
Section 21.4.2, "Enabling Security"
Section 21.4.3, "Configuring Initial Load"
Section 21.4.4, "Enabling the NPR & SYNC Flows"

21.4.1 Cluster Installation

To install the Design to Release: Agile - EBS PIP in a cluster, follow these steps:

Open the <WebTier_HOME>/instances/<instances_name>/config/OHS/ohs1/mod_wl_ohs.conf file.

Add the following code:

Example 21-1 Queue

<Location /queue> 
 SetHandler weblogic-handler 
 WebLogicCluster <<PrimaryHost>>:<PrimaryHost 
 Port>>,<<SecondaryHost>>:<SecondaryHost Port>> 
 WLLogFile /tmp/web_log.log 
 </Location>

Example 21-2 EBIBOMConfigurator

<Location /EBIBOMConfigurator/ebibomconfigreturnservlet > 
 SetHandler weblogic-handler 
 WebLogicCluster 
 <<PrimaryHost>>:<PrimaryHostPort>>,<<SecondaryHost>>:<SecondaryHost Port>> 
 WLLogFile /tmp/web_log.log 
 </Location>

21.4.2 Enabling Security

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 EBS Integration: SOA SERVER USER system profile to Weblogic 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.

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.

21.4.3 Configuring Initial Load

To configure the Agile Initial Load for the Design to Release: Agile - EBS Pre-Built Integration, perform the following steps:

Note:

These steps are required to use the Initial Load for the Design to Release: Agile - EBS Pre-Built Integration.

Apply patch 8313714:R12.EGO.C for EBS R12.1.1 or EBS R12.1.2
Login to the EBS database
Locate and open the EGO_EBI_ITEM_LOAD package

Perform the following changes:

In the GENERATE_EVENTS procedure, replace the following query:

INSERT INTO EGO_EBI_ITEM_LOAD_LOG (INVENTORY_ITEM_ID,ORGANIZATION_ID, EVENT_ID)
SELECT INVENTORY_ITEM_ID, ORGANIZATION_ID, NULL
FROM MTL_SYSTEM_ITEMS_B
WHERE ORGANIZATION_ID = p_organization_id
AND bom_item_type in (1, 2, 4)
AND customer_order_flag = 'Y'
AND customer_order_enabled_flag = 'Y';

With the following query:

INSERT INTO EGO_EBI_ITEM_LOAD_LOG (INVENTORY_ITEM_ID,ORGANIZATION_ID, EVENT_ID)
SELECT INVENTORY_ITEM_ID, ORGANIZATION_ID, NULL
FROM MTL_SYSTEM_ITEMS_B
WHERE ORGANIZATION_ID = p_organization_id;

In the REGENERATE_FAILED_EVENT procedure, replace the following query:

DELETE FROM  EGO_EBI_ITEM_LOAD_LOG
WHERE ORGANIZATION_ID = p_organization_id AND
EVENT_ID = p_event_id AND
INVENTORY_ITEM_ID NOT IN(
SELECT INVENTORY_ITEM_ID
FROM MTL_SYSTEM_ITEMS_B
WHERE ORGANIZATION_ID = p_organization_id
AND bom_item_type in (1, 2, 4)
AND customer_order_flag = 'Y'
AND customer_order_enabled_flag = 'Y');

With the following query:

DELETE FROM  EGO_EBI_ITEM_LOAD_LOG
WHERE ORGANIZATION_ID = p_organization_id AND
EVENT_ID = p_event_id AND
INVENTORY_ITEM_ID NOT IN(
SELECT INVENTORY_ITEM_ID
FROM MTL_SYSTEM_ITEMS_B
WHERE ORGANIZATION_ID = p_organization_id);

Recompile the EGO_EBI_ITEM_LOAD package

21.4.4 Enabling the NPR & SYNC Flows

To enable the NPR & SYNC flows in the Design to Release: Agile - EBS Pre-Built Integration, you must update the config.properties file located in NPRpx.jar:

Note:

Before performing any changes, back up the NPRpx.jar file.

In the Agile server, navigate to <AgileHome>/integration/sdk/extensions.
Unzip NPRpx.jar.
Open config.properties file.
Update Host and Port values for the following variables:
1. WS_LOCATION_CRETEITEMFLOW=http://<<FMWHost>>:<<ManagedPort>>/soa-infra/services/default/SyncItemListAgileReqABCS/client
2. WS_LOCATION_SYNCITEMFLOW=http://<<FMWHost>>:<<ManagedPort>>/soa-infra/services/default/SyncItemListAgileReqABCS/client
Check that the value for NPR_PX_TIMEOUT is 90000000. This is the recommended value.
Update the SOA_LOGIN_USERNAME and SOA_LOGIN_PASSWORD values with your username and password.

The password must be encrypted. To encrypt the password:
1. In the Agile Server, navigate to <AgileHome>/agileDomain/bin
2. Run the encryption script "./encryptpwd.sh <PasswordToBeEncrypted>"
Save your changes and rezip NPRpx.jar.
Restart the Agile Server.

21.5 Verifying Deployment

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.
1. Navigate to the PLM integration Queue Management console (http://<server name>:<port number>/queue).
2. 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 21-8 Design to Release: Agile - EBS Pre-Built Integration ESB Services

Mediator Services	12.1.x or 12.2.x with PIM + 9.3.x where x>=1 with VM	12.1.x or 12.2.x with PIM + 9.3.x where x>=1	12.1.x or 12.2.x + 9.3.x where x>=1 with VM	12.1.x or 12.2.x + 9.3.x where x>=1
EBS
BillOfMaterialsConfigurationEBS	x	x	x	x
ItemEBSV2
EngineeringChangeOrderEBS
EngineeringChangeOrderResponseEBS
ItemBalanceEBS
ItemBalanceResponseEBS
ItemResponseEBSV2
Adapter Services
UpdateEngineeringChangeOrderStatusEbizEventConsumer
CreateEngineeringChangeOrderListEbizAdapter
GetConfiguratorURLEbizAdapter
ProcessEbizItemBatchLoadEventConsumer
QueryEngineeringChangeOrderListEbizAdapter
QueryItemBalanceListEbizAdapter
QueryItemListEbizAdapter
QueryResponsibilityEbizAdapter
SyncBillOfMaterialsConfigurationEbizJMSConsumer		x		x
SyncBillOfMaterialsConfigurationEbizJMSProducer		x		x
SyncItemListEbizAdapter
ValidateEngineeringChangeOrderListEbizAdapter
ACSAXMLJMSConsumer
Utility Service
CreateQueueControlService
QueueProcessorService

Also check for the items in Table 21-9.

Note:

Processes marked as x are not available.

Table 21-9 Design to Release: Agile - EBS Pre-Built Integration processes

BPEL Processes	12.1.x or 12.2.x with PIM + 9.3.x where x>=1	12.1.x or 12.2.x + 9.3.x where x>=1 with VM	12.1.x or 12.2.x + 9.3.x where x>=1
CreateEngineeringChangeOrderListEbizProvABCSImpl
CreateQueueService
GenerateItemNumberService		x	x
GetConfiguratorURLEbizProvABCSImpl	x		x
GetConfiguratorURLAgileReqABCSImpl	x		x
ProcessItemListInitialLoadAgileABF
ProcessItemListInitialLoadEbizABF
ProcessEngineeringChangeOrderAgileReqABCSImpl
QueueProcessorServiceImpl
SyncBillOfMaterialsConfigurationAgileProvABCSImpl	x		x
SyncBillOfMaterialsConfigurationListEbizReqABCSImpl	x		x
SyncItemListAgileReqABCS
SyncItemListAgileReqABCSImpl
SyncItemListEbizProvABCSImpl
UpdateEngineeringChangeOrderListAgileProvABCSImpl
UpdateEngineeringChangeOrderListEbizReqABCSImpl
UpdateItemBalanceListAgileProvABCSImpl
UpdateItemBalanceListEbizReqABCSImpl
UpdateItemListAgileProvABCSImpl
UpdateItemListEbizReqABCSImpl
ValidateEngineeringChangeOrderListAgileReqABCSImpl
ValidateEngineeringChangeOrderListEbizProvABCSImpl
TransformAppContextEbizService
UpdateEngineeringChangeOrderListEbizReqABCS
UpdateItemBalanceListEbizReqABCS
UpdateItemListEbizReqABCS

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.
1. Navigate to the AIA Console URL: http://<server name>:<port number>/AIA.
2. Log in with server admin user name.
3. Navigate to Setup, System to access the Application Registry page.

Check the rows for the following sets of values:

Table 21-10 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	9.3.2 (Out of the Box) This can be edited to appropriate version of Agile PLM.

Table 21-11 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: 12.1.x, 12.1.x with PIM)

21.5.1 Validating Security Policies

For information on validating security policies for the Design to Release: Agile - EBS Pre-Built Integration, 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.

21.6 Undeploying the Design to Release: Agile - EBS Pre-Built Integration

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 21-12 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

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".