Go to primary content
Oracle® Application Integration Architecture Agile Product Lifecycle Management for Oracle E-Business Suite: Design to Release Install Guide
Release 3.6
E88835-06
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

3 Installing and Deploying AgileToEbiz PIP 3.6

This chapter discusses how to install and deploy AgileToEbiz PIP 3.6.

3.1 Installing AgileToEbiz PIP 3.6

To install AgileToEbiz PIP 3.6:

  1. Copy the AgileToEbizPIP3.6 package files from the Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite Package(V971125-01.zip) to your machine.

  2. Navigate to the Agile2EbizPIP3.6 directory.

  3. Run the following installation file for your platform:

    • Linux: .\setup_lin.bin

    • Windows: setup_win.exe

      The Agile PLM PIP Installer launches the Welcome screen.

  4. Click Next.

  5. Enter the Name and Path

    • AIA Name: AgileToEbizPIP

    • AIA Home Path: which should be the SCE Services Location you typed in post install (eg: /apps/agile/product/AgileToEbizPIP3.6)


      Note:

      If the AIA Home Path is not correct, the installation will not proceed.

  6. Click Next.

  7. Complete the remaining screens as described in the following sections:

    • "SOA Admin Server Details Screen"

    • "SOA Server Details Screen"

    • "SOA Server Cluster Details"

    • "EBS Server Connect Details Screen"

    • "EBS Server Details Screen"

    • "EBS Database Details Screen"

    • "Agile PLM Server Connect Details Screen"

    • "Agile PLM Server Details Screen"

    • "PIP Database Connect Details Screen fields"

    • "PIP Schema Details Screen fields"

    • "PIP Item Initial Load Data Location Details Screen"

  8. If the information displayed on the Pre-Installation Summary page is correct, click Install.

3.2 Agile PLM PIP Installer Screens

The following sections describe the fields on the Agile PLM PIP installer screens.

3.2.1 SOA Admin Server Details Screen

Use this screen to enter details about your SOA Admin Server. This screen contains the fields listed in Table 3-1.

Table 3-1 SOA Admin Server Details Screen Fields

Field Description

Admin Hostname

The value is the hostname of the WebLogic admin server. To find this value contact your WebLogic administrator.

The Admin Hostname is____________________________

Admin Port

This value is the port number of the WebLogic admin server. To find this value contact your WebLogic administrator.

The Admin Port 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 ___________________________________


3.2.2 SOA Server Details Screen

Use this screen to enter information about your managed or cluster SOA server. This screen contains the fields listed in Table 3-2.

Table 3-2 SOA Server Details Screen Fields (Standalone)

Field Description

SOA Domain Name

This is a WebLogic server domain corresponding to the Admin Server. Example: domain1

The SOA Domain Name is _____________________________

SOA Installation Directory

This value is the path where the SOA Domain is located.

Managed Server Name

This value is the name of the Managed Server for the domain.

Managed Server Port

This value is the port number of the managed server.


Table 3-3 SOA Sever Details Screen Fields (Cluster)

Field Description

SOA Domain Name

This is WebLogic server domain corresponding to the Admin Server. Example: domain1

The SOA Domain Name is _______________________________

SOA Installation Directory

This value is the path where the SOA Domain is located.

Cluster Name.

This value is the name of the cluster.

Cluster Proxy Hostname

This value is the hostname of the proxy server managing the cluster.

Proxy Port

This value is the proxy port of the cluster


3.2.3 SOA Server Cluster Details

This screen only appears if you are installing in a cluster environment. The field and description are as follows:

If installing in a cluster environment:

Path to SOA Cluster Shared Directory-Enter the path to the location of the SOA Cluster Shared Directory.

3.2.4 EBS Server Connect Details Screen

Use this screen to enter details related to connect to your Oracle E-Business Suite server instance. The screen contains the fields listed in Table 3-4.

Table 3-4 EBS Server Connect Details Screen Fields

Field Description

EBS Hostname

Specifies the hostname of the Oracle E-Business Suite application. Example:

example1.corp.oracle.com.

E-Business Suite hostname is __________________________

EBS 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 ________________________________

EBS User Name

To find this value, contact your administrator.

E-Business Suite User Name is __________________________

EBS Password

To find this value, contact your administrator.

E-Business Suite Password is ____________________________


3.2.5 EBS Server Details Screen

Use this screen to enter details related to your Oracle E-Business Suite server instance. The screen contains the fields listed in Table 3-5.

Table 3-5 EBS Server Details Screen Fields

Field Description

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 __________________

EBS Version

This is a drop down list of Oracle E-Business Suite Application versions. If you choose the version with PIM, then you need do more configuration after the installation has been completed.

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


3.2.6 EBS Database Details Screen

Use this screen to enter details related to your Oracle E-Business Suite database instance. The screen contains the fields listed in Table 3-6.

Table 3-6 EBS Database Details Screen Fields

Field Description

EBS Database Hostname

Specifies the hostname. To find this value, contact the database administrator. Example: server1.oracle.com.

E-Business Suite Database Host is _________________________

EBS Database Port

To find this value, contact the database administrator. Example: 1521. E-Business Suite Database Port is _____________________

EBS Database SID (System ID)

To find this value, contact the database administrator. Example: orcl. E-Business Suite Database SID is ______________________

EBS Database Username

To find this value, contact the database administrator. Example: apps. E-Business Suite Database Username is ________________

EBS Database Password

To find this value, contact the database administrator. E-Business Suite Database Password is _______________________________

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


3.2.7 Agile PLM Server Connect Details Screen

Table 3-7 Agile PLM Server Connect Details Screen

Field Description

Agile PLM Hostname

Specifies the hostname. Example: example1.corp.oracle.com. Agile PLM Host is _______________________

Agile PLM Port

This is the http or https port if you are using Agile PLM with Web Service Security enabled. 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 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 User Name

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_________________________


3.2.8 Agile PLM Server Details

Use this screen to enter details related to your Agile PLM instance. The screen contains the fields listed in Table 3-7.

Table 3-8 Agile PLM Server Details Screen Fields

Field Description

Agile PLM Version

Select the Agile PLM version from the dropdown list.

Web Services Security Enabled

If you are using Agile PLM 9.3.6, Agile PLM 9.3.5, or Agile PLM 9.3.4 and have enabled Web Services Security, then select the checkbox.


3.2.9 PIP Database Connect Details Screen for PIP Schema

Table 3-9 PIP Database Connect Details Screen Fields

Field Description

PIP Schema Database Hostname

Specifies the database hostname. To find this value, contact the database administrator. Example: server1.oracle.com.

PIP Schema Database Host is ____________________________

PIP Schema Database Port

To find this value, contact the database administrator. Example: 1521. PIP Schema Database Port is _______________________

PIP Schema Database SID (System ID)

To find this value, contact the database administrator. Example: orcl. PIP Schema Database SID is ________________________

Sys User Name

Enter the name of the SYS database user. Default value is sys.

Sys User Password

Enter the password for the SYS database user. To find this value, contact the database administrator.


3.2.10 PIP Schema Details Screen

Use this screen to enter details related to your new schema to be created for the pre-built integration queue tables. The screen contains the fields listed in Table 3-10.

Table 3-10 PIP Schema Details Screen Fields

Field Description

PIP Schema Name

Enter the name of the new schema to be created for the PIP queue tables. Default Value is plmpip.

Create a password for the schema.

Create a password for the schema.

Confirm PIP Schema password

Confirm the new password that you created.


3.2.11 PIP Item Initial Load Data Location Details Screen

Use this screen to enter details related to the Oracle EBS to Agile PLM Initial Load instance. The screen contains the fields listed in Table 3-11.

Table 3-11 PIP Item Initial Load Data Locations

Field Description

Location to store XML files with item data from EBS

This is the location where AIA stores the XML files that contain Initial Load Item data from Oracle E-Business Suite.

Location to read Item XML files to load 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 where AIA stores the XML files that contain Initial Load Item data from Oracle E-Business Suite.

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.



Note:

In a clustering PIP D2R environment, put the folders in $SHARED_LOCATION.

3.3 Complete Installation

Use these instructions to complete the installation.

  1. Review the configuration information on the Pre-Installation Summary screen.


    Note:

    If you want to make changes to the configuration, click the Back button to go to the screen you want to edit. You can create a response file based on the input provided in the Installer and use it in future when you want to deploy the integration.

    Start the Installer with the -r option to create a response file. On Linux: ./setup_lin.bin -r <response file path and name>. On Windows: setup_win.exe -r <response file path and name>.

    You can install using the steps described in the Section, "Install using the Response File" below.


  2. Click Install to start the installation.

    The system displays progress of the configuration in the Installation Progress screen.

    The system displays any warnings or errors as necessary. You can review the configuration log for additional details.

  3. When the configuration process completes without errors, the Installer displays the Install Complete screen.

  4. Click Done to close the Installer.

To install using the response file:

  1. Navigate to $DOMAIN_LOCATION/soa/aia/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.

  2. Navigate to PIP 3.6 Installer folder and run the command ./setup_lin.bin -f <Response File Location and Name> for Linux based systems and setup_ win.exe -f <Response File Location and Name> for Microsoft Windows.

3.3.1 Prerequisites for Deploying AgileToEbiz PIP

Prerequisite for E-Business Suite version 12.2.2 or later

To install Design to Release: AgileToEbiz PIP 3.6 with E-Business Suite version 12.2.2 or later, and you chose the E-Business Suite version with PIM, you must perform the following steps before deploying the AgileToEbiz PIP:

  1. Navigate to $DOMAIN_LOCATION/soa/aia/bin/AIAInstallProperties.xml

  2. 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://isghostname.us.oracle.com:8088/soa-infra/services/default/XZ1ST226_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://isghostname.us.oracle.com:8088/soa-infra/services/default/XZ1ST226_BSO_inv_ebi_item_GenerateItemNumberService/GenerateItemNumberService_Service

Surrounding text describes ch3one.jpg.

3.3.2 Updating MDS

To update MDS before deploying AgileToEbiz PIP:

Navigate to $DOMAIN_LOCATION/soa/aia/bin, run the following installation file for your platform:

  • Linux

    source aiaenv.sh

    ant -f $SOA_HOME/aiafp/Install/AID/AIAInstallDriver.xml -DPropertiesFile=$DOMAIN_LOCATION/soa/aia/bin/AIAInstallProperties.xml -DDeploymentPlan=$DOMAIN_LOCATION/soa/aia/MDSUtils/UpdateMetaDataFileDP.xml

  • Windows

    aiaenv.bat

    ant -f %SOA_HOME%\aiafp\Install\AID\AIAInstallDriver.xml -DPropertiesFile=%DOMAIN_LOCATION%\soa\aia\bin\AIAInstallProperties.xml -DDeploymentPlan=%DOMAIN_LOCATION%\soa\aia\MDSUtils\UpdateMetaDataFileDP.xml

    It will also ask for Admin user and password

3.3.3 Depolying the Design to Release: AgileToEbizPIP 3.6

To deploy AgileToEbiz PIP to SOA Server

  1. Navigate to $DOMAIN_LOCATION/soa/aia/bin and run the command source aiaenv.sh for Linux based systems or aiaenv.bat for Microsoft Windows to configure the environment.

  2. Run the command for your platform.

    Table 3-12 Deployment Command for the Design to Release: AgileToEbiz PIP

    Platform Deployment Command

    Linux x86-64

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

    Microsoft Windows x64 (64-bit)

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


  3. 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 SOA Core Extension 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".

3.4 Verifying Deployment

To verify AgileToEbiz PIP 3.6 deployment:

  1. Open the log files from the following location and look for warnings and error messages:

    • For Linux Based Systems: Review the install log located at $SERVICES_ LOCATION/pips/AgileToEbiz/DeploymentPlans/ to verify that the integration is successfully installed.

    • For Microsoft Windows: Review the install log located at %SERVICES_ LOCATION%\pips\AgileToEbiz\DeploymentPlans\ to verify that the integration is successfully installed.

  2. Confirm that the Design to Release: AgileToEbiz 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.

  3. Confirm that the Design to Release: AgileToEbiz 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.

    • Click Target Navigation, expend SOA folder, click soa-infra and look for the following items:


      Note:

      Services marked as x are not available.

      Table 3-13 Design to Release: AgileToEbiz PIP ESB Services

      MediatorServices EBS with PIM+ Agile with VM EBS withPIM + Agile EBS + Agilewith VM EBS + Agile

      EBS

      BillOfMateri alsConfigur ationEBS

      x

      x

      x

      x

      ItemEBSV2





      Engineering ChangeOrd erEBS





      EngineeringChangeOrderResponseEBS





      ItemBalanceEBS





      ItemBalance ResponseEBS





      ItemBalance ResponseEBS





      Adapter Services

      UpdateEngineeringChangeOrderStatusEbizEven tConsumer





      CreateEngineeringChangeOrderListEbizAdapter





      GetConfiguratorURLEbizAdapter





      ProcessEbizItemBatchLoadEventConsumer





      QueryEngineeringChangeOrderListEbizAdapter





      QueryItemBalanceListEbizAdapter





      QueryItemlistEbizAdapter





      QueryResponsibilityEbiz Adapter





      SyncBillOfMaterialsConfigurationEbizJMSCons umer


      x


      x

      SyncBillOfMaterialsConfigurationEbizJMSProducer


      x


      x

      SyncItemListEbizAdapter





      ValidateEngineeringChangeOrderListEbizAdapter





      ACSAXMLJ

      MSConsumer





      Utility Service

      CreateQueueControlService





      QueueProcessorService






      Also check for the items in Table 3-14.


      Note:

      Services marked as x are not available.

      Table 3-14 Design to Release: AgileToEbiz PIP processes

      BPEL Processes EBS with PIM + Agile with VM EBS with PIM + Agile EBS+ Agile with VM EBS+ Agile

      CreateEngineeringChangeOrderListEbizProvAB CSImpl





      CreateQueueService





      GenerateItemNumberService



      x

      x

      GetConfiguratorURLEbizProvABCSImpl


      x


      x

      GetConfiguratorURLAgileReqABCSI mpl


      x


      x

      ProcessItemListInitialLoadAgileABF





      ProcessItemListInitialLoadEbizABF





      ProcessEngineeringChangeOrderAgileReqABCS Impl





      QueueProcessorServiceImpl





      SyncBillOfMaterialsConfigurationAgileProvABCSImpl


      x


      x

      SyncBillOfMaterialsConfigurationListEbizReqABCSImpl


      x


      x

      SyncItemListAgileReqABCS





      SyncItemListAgileReqABCSImpl





      SyncItemListEbizProvABCSImpl





      UpdateEngineeringChangeOrderListAgileProvABCSImpl





      UpdateEngineeringChangeOrderListEbizReqABCSImpl





      UpdateItemBalanceListAgileProvABCSImpl





      UpdateItemBalanceListEbizReqAB CSImpl





      UpdateItemListAgileProvABCSImpl





      UpdateItemListEbizReqABCSImpl





      ValidateEngineeringChangeOrderListAgileReqABCSImpl





      ValidateEngineeringChangeOrderListEbizProvABCSImpl





      TransformAppContextEbizService





      UpdateEngineeringChangeOrderListEbizReqABCS





      UpdateItemBalanceListEbizReqABCS





      UpdateItemListEbizReqABCS







      Note:

      After deploying on Windows and restarting the SOA Server, two composites, ACSAXMLJMSConsumer and SyncBillofMaterialsConfigurationEbizJMSConsumer, cannot be started. For more information, refer to the Release Notes for Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release.


      Note:

      If EBS is down, the GenerateItemNumberService does not deploy. An error is generated for the deployment of this service.

  4. Confirm that the SOA Core Extension Manager components were successfully installed.

    • Navigate to the AIA Console URL: http://<server name>:<port number>/sce.

    • Log in with server admin user name.

    • Navigate to Setup, System to access the Application Registry page.

  5. Check the rows for the following sets of values:

    Table 3-15 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.6 (Based on your selected Agile PLM version)

    This can be edited to appropriate version of Agile PLM.


    Table 3-16 Application Registry Values for EBS

    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.2.x, 12.2.x with PIM)


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

3.5 Undeploying the Design to Release: AgileToEbiz PIP

To undeploy AgileToEbiz PIP form SOA Server:

  1. Navigate to $DOMAIN_LOCATION/soa/aia/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.

  2. Run the command for your platform.

    Table 3-17 Un-deployment Command for the Design to Release: Agile - EBS Pre-Built Integration

    Platform Un-deployment Command

    Linux

    ant Uninstall -f $SOA_HOME/aiafp/Install/AID/AIAInstallDriver.xml

    -DPropertiesFile=$DOMAIN_LOCATION/soa/aia/bin/AIAInstallProperties.xml

    -DDeploymentPlan=$SERVICES_ LOCATION/pips/AgileToEbiz/DeploymentPlans/AgileToEbizDPUndeployDP.xml

    -DDeploymentPolicyFile=$SERVICES_ LOCATION/pips/AgileToEbiz/DeploymentPlans/AgileToEbizConditionalPolicyUndepl oy.xml

    -DSupplementaryDeploymentPlan=$SERVICES_ LOCATION/pips/AgileToEbiz/DeploymentPlans/AgileToEbizSupplementaryUndeployDP

    .xml

    -l $SERVICES_

    LOCATION/pips/AgileToEbiz/DeploymentPlans/AgileToEbizUndeployDP.log

    Microsoft Windows

    ant Uninstall -f %SOA_HOME%\aiafp\Install\AID\AIAInstallDriver.xml

    -DPropertiesFile=%DOMAIN_LOCATION%\soa\aia\bin\AIAInstallProperties.xml

    -DDeploymentPlan=%SERVICES_ LOCATION%\pips\AgileToEbiz\DeploymentPlans\AgileToEbizDPUndeployDP.xml

    -DDeploymentPolicyFile=%SERVICES_ LOCATION%\pips\AgileToEbiz\DeploymentPlans\AgileToEbizConditionalPolicyUndep loy.xml

    -DSupplementaryDeploymentPlan=%SERVICES_ LOCATION%\pips\AgileToEbiz\DeploymentPlans\AgileToEbizSupplementaryUndeployD P.xml

    -l %SERVICES_

    LOCATION%\pips\AgileToEbiz\DeploymentPlans\AgileToEbizUndeployDP.log



    Note:

    The log file may show that undeploying has failed. Actually, all deployed composites and applications are removed successfully. To avoid the failure, see the Release Notes for Agile Product Lifecycle Management Integration Pack for Oracle E-Business Suite: Design to Release for more information on how to apply the workaround.

  3. Restart the SOA server.

  4. Uninstall the integration.