PK Yc|Boa,mimetypeapplication/epub+zipPKYc|BiTunesMetadata.plist} artistName Oracle Corporation book-info cover-image-hash 347337155 cover-image-path OEBPS/dcommon/oracle-logo.jpg package-file-hash 54378502 publisher-unique-id E23118-04 unique-id 985220722 genre Oracle Documentation itemName Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations, Release 11.1 releaseDate 2013-03-28T00:55:51Z year 2013 PK PKYc|BMETA-INF/container.xml PKYuPKYc|BOEBPS/agileplmopm.htm Configuring and Deploying the Design to Release: Agile PLM for Process - OPM PIP

23 Configuring and Deploying the Design to Release: Agile PLM for Process - OPM PIP

This chapter discusses how to configure and deploy the Oracle Design to Release Integration Pack for Agile Product Lifecycle Management for Process and Oracle Process Manufacturing (Design to Release: Agile PLM for Process - OPM PIP).

This chapter includes the following sections:

23.1 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of the Design to Release: Agile PLM for Process - OPM PIP. Enter the details of the Design to Release: Agile PLM for Process - OPM PIP screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.

23.1.1 PIP Server Details Screen

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

Table 23-1 PIP Server Details Screen Fields

FieldDescription

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


23.1.2 Agile PLM for Process Application Details

Use this screen to enter details related to your Agile PLM for Process instance.

The screen contains the following fields:

Table 23-2 Agile PLM for Process Application Details Screen Fields

FieldDescription

Agile PLM for Process Host

Specifies the system name. Example: example1.corp.example.com.

Agile PLM for Process Host name is _____________________________

Agile PLM for Process Port

This is the http port. This value depends on the web server port and operating system of your Agile PLM for Process instance. To find this value, contact your Agile PLM for Process administrator. Example: 80.

Agile PLM for Process Port is _________________________________

Agile PLM for ProcessVirtual Path

This value is the same virtual path entered during the Agile PLM for Process installation. Example: Integration/ProdikaContracts/CSS.

Agile PLM for ProcessVirtual Path is ______________________________


23.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 23-3 Oracle E-Business Suite Server Details Screen fields

FieldDescription

E-Business Suite Host Name

Specifies the fully qualified system name of the Oracle E-Business Suite application. Example: example1.corp.example.com.

E-Business Suite fully qualified 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 PIP.

E-Business Suite Version

This is a drop down list of Oracle E-Business Suite Application versions.


23.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 23-4 Oracle E-Business Suite Database Details Screen Fields

FieldDescription

E-Business Suite Database Host

Specifies the system name. To find this value, contact the database administrator. Example: server1.example.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.


23.2 Configuring and Deploying Design to Release: Agile PLM for Process - OPM PIP

This section discusses the PIP configuration and deployment process. There are two steps:

  1. Configure your PIP using the deployment DCW.

  2. Deploy the PIP to the Fusion Middleware server.

23.2.1 Configuring the Design to Release: Agile PLM for Process - OPM PIP

The screens that appear in the DCW prompt you to enter the data that is required for successful configuration of the Design to Release: Agile PLM for Process - OPM PIP. Keep the completed worksheets the Design to Release: Agile PLM for Process - OPM PIP 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 PLM for Process - OPM PIP:

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

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

  3. Restart the server.

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

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

  6. Click Next.

  7. Select theDesign to Release: Agile PLM for Process - OPM PIP

  8. Click Next.

23.2.1.1 Specify PIP Server Details

To specify PIP Server details:

  1. Enter information related to your PIP server in the PIP Server Details screen.

  2. Click Next.

23.2.1.2 Specify Agile PLM for Process Application Details

To specify Agile PLM for Process application details:

  1. Enter information about your Agile PLM for Process installation in the Agile PLM for Process Application Details screen.

  2. Click Next.

23.2.1.3 Specify Oracle E-Business Suite Server Details

To specify Oracle E-Business Suite Server details:

  1. Enter information about your Oracle E-Business Suite Server installation in the E-Business Suite Server Details screen.

  2. Click Next.

23.2.1.4 Oracle E-Business Suite Database Details Screen

To specify Oracle E-Business Suite Database details:

  1. Enter information about your Oracle E-Business Suite Database installation in the E-Business Suite Database Details screen.

  2. Click Next.

23.2.1.5 Complete Configuration

To complete configuration:

  1. 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 PIP. You can configure using the steps described in Section 23.2.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.


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

  3. When the configuration process completes without errors, the AIA DCW displays the Configuration Complete screen.

  4. Click Finish to close the DCW.

23.2.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

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

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

23.2.3 Deploying the Design to Release: Agile PLM for Process - OPM PIP

To deploy the PIP to Fusion Middleware server:

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

  2. 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 undeployment command too.


    Table 23-5 Deployment Commands for the Design to Release: Agile PLM for Process - OPM PIP

    PlatformDeployment Command

    Linux

    Solaris SPARC

    HP-UX

    IBM AIX Based Systems

    ant -f /<AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml 
    -DDeploymentPlan=/<AIA_HOME>/pips/PLM4PEbizOPM/DeploymentPlans/PLM4PEbizOPMDP.xml -DPropertiesFile=/<AIA_HOME>/aia_instances/<AIA_Instance_name>/config/AIAInstallProperties.xml 
    -DSupplementaryDeploymentPlan=/<AIA_HOME>/pips/PLM4PEbizOPM/DeploymentPlans/PLM4PEbizOPMSupplementaryDP.xml 
    -l /<AIA_HOME>/pips/PLM4PEbizOPM/DeploymentPlans/PLM4PEbizOPM.log
    

    Microsoft Windows

    ant -f \<AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml 
    -DDeploymentPlan=\<AIA_HOME>\pips\PLM4PEbizOPM\DeploymentPlans\PLM4PEbizOPMDP.xml 
    -DPropertiesFile=\<AIA_HOME>\aia_instances\<AIA_Instance_name>\config\AIAInstallProperties.xml 
    -DSupplementaryDeploymentPlan=\<AIA_HOME>\pips\PLM4PEbizOPM\DeploymentPlans\PLM4PEbizOPMSupplementaryDP.xml 
    -l \<AIA_HOME>\pips\PLM4PEbizOPM\DeploymentPlans\PLM4PEbizOPM.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 PIPs are not displayed.


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

23.3 Performing Postdeployment Configurations

Agile PLM for Process applies HTTP basic authentication to handle AIA syndication result messages by an Agile PLM for Process host account. You must add the Agile PLM for Process credential to Fusion Middleware for the HTTP basic authentication connection.

To configure credential:

  1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

  2. Navigate to WebLogic Domain, soa_domain, Securities, Credentials.

  3. Check whether the Map with name oracle.wsm.security exists in Credentials.

    If it does not exist, create a Map with name oracle.wsm.security.

  4. Create a key in oracle.wsm.security map with name PLM4P_CSSServices_BasicHttpBinding_ICSSServices. Select the type as password and enter the Agile PLM for Process host user name and password.

  5. Click OK.

23.4 Verifying Deployment

To verify the Design to Release: Agile PLM for Process - OPM PIP deployment:

  1. 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 PIP is successfully installed.

    • For Microsoft Windows: Review the install log located at <AIA_HOME>\aia_instances\<instance name>\logs to verify that the PIP is successfully installed.

  2. Confirm that the Design to Release: Agile PLM for Process - OPM PIP services were installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

    • ItemEBSV2

    • ItemResponseEBSV2

    • ProductionRecipeEBS

    • ProductionRecipeResponseEBS

    • QueryResponsibilityEbizAdapter

    • SyncItemListEbizAdapter

    • SyncItemListEbizProvABCSImpl

    • SyncProductionRecipeListEbizProvABCSImpl

    • SyncRecipeListEbizAdapter

    • SyncSpecPLM4PAdapter

    • SyncSpecPLM4PReqABCSImpl

    • TransformAppContextEbizService

23.4.1 Validating Security Policies

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 PIP have locally attached security policies.

To validate locally attached security policies:

  1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

  2. Navigate to WebLogic Domain, soa_domain, Web Services, Policies.

  3. Verify Service Policy attachment.

    1. Find the service policy in the list of policies.

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Service.

    4. Validate that all the composites are listed with local attachment to this service policy.

  4. Verify Client Policy attachment

    1. Navigate back to Policies screen and find the client policy

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Reference.

    4. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.

      Table 23-6 Service Policy Attachments for Design to Release: Agile PLM for Process – EBS OPM PIP

      CompositeService Policy

      SyncSpecPLM4PAdapter

      oracle/wss_http_token_service_policy


      Table 23-7 HTTP Token Client Policy Attachments for Design to Release: Agile PLM for Process – EBS OPM PIP

      CompositeReferenceClient Policy

      SyncSpecPLM4PAdapter

      PLM4PSyncResponse

      oracle/wss_http_token_client_policy

      SyncItemListEbizProvABCSImpl

      ItemResponseErrorEBS

      oracle/wss_username_token_client_policy

      SyncProductionRecipeListEbizProvABCSImpl

      ProductionRecipeResponseErrorEBS

      oracle/wss_username_token_client_policy


For more information about security validation, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Working with Security."

For PIP implementation, see Oracle Design to Release Integration Pack for Agile Product Lifecycle Management for Process and Oracle Process Manufacturing Implementation Guide.

23.5 Undeploying the Design to Release: Agile PLM for Process - OPM PIP

To undeploy the PIP from Fusion Middleware Server:

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

  2. Run the command for your platform.

    Table 23-8 Undeployment Command for the Design to Release: Agile PLM for Process - OPM PIP

    PlatformUndeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems.

    HP-UX

    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/PLM4PEbizOPM/DeploymentPlans/PLM4PEbizOPMUndeployDP.xml 
    -l <AIA_HOME>/pips/PLM4PEbizOPM/DeploymentPlans/PLM4PEbizOPMUndeployDP.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\PLM4PEbizOPM\DeploymentPlans\PLM4PEbizOPMUndeployDP.xml 
    -l <AIA_HOME>\pips\PLM4PEbizOPM\DeploymentPlans\PLM4PEbizOPMUndeployDP.log
    

  3. Restart the SOA server.

  4. Uninstall the PIP following the instructions in Chapter 37, "Uninstalling Oracle AIA".

PK)j`PKYc|BOEBPS/partpage_i.htm% Configuring and Deploying Pre-Built Integrations

Part I

Configuring and Deploying Pre-Built Integrations

This part describes how to configure and deploy the pre-built integrations that are delivered in this release on Foundation Pack.

This part contains the following chapters:

PKVPKYc|BOEBPS/custmdmmatchfetcheca.htm+~ Deploying Customer MDM: Match Fetch Enterprise Composite Application

14 Deploying Customer MDM: Match Fetch Enterprise Composite Application

This chapter discusses how to configure and deploy Oracle Customer Data Management: Match Fetch Enterprise Composite Application (Customer MDM: Match Fetch Enterprise Composite Application).

This chapter includes the following sections:

14.1 Overall Configuration and Deployment of MDM Customer Integrations

The overall MDM Customer integration consists of four component integrations: MDM Customer Base Pack (UCM) and three other options: MDM Customer Siebel, MDM Customer E-Business Suite and MDM Customer 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:

  1. Configure and deploy the MDM Customer component integrations. For detailed instructions on the MDM Customer integrations, see your specific integration chapters in Part I, "Configuring and Deploying Pre-Built Integrations" of this guide.

  2. Deploy the MDM Customer Routing Rules following the instructions discussed in Chapter 13, "Deploying Customer MDM Routing Rules". Routing Rules wire the integration services, depending on the integrations deployed.

  3. Deploy the MDM Customer Match Fetch Enterprise Composite Application following the instructions in Section 14.2, "Deploying Customer MDM: Match Fetch Enterprise Composite Application". This UI application enables match and fetch of customers from the hub.

14.2 Deploying Customer MDM: Match Fetch Enterprise Composite Application


Note:

The Match Fetch Enterprise Composite Application available for previous versions of AIA is different from the one available for AIA 11.1. You must install and configure the latest Match Fetch Enterprise Composite Application available for this release.


To deploy the ADF-based UI to Fusion Middleware server:

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

  2. Run the command for your platform.

    Table 14-1 Deployment Command for Customer MDM: Match Fetch Enterprise Composite Application

    PlatformDeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    sh $AIA_HOME/services/core/UCM/UtilityServices/CustomerHub/DeploymentPlans/deployCustomerHUBMatchAndFetchApp.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME%\services\core\UCM\UtilityServices\CustomerHub\DeploymentPlans\deployCustomerHUBMatchAndFetchApp.bat
    

  3. Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/CustomerHUBMatchAndFetchAppDP_Deployments_YYYY-MM-DD_HH-MI-SS.log to verify successful deployment.

14.3 Verifying Deployment

To verify the Customer MDM: Match Fetch Enterprise Composite Application deployment:

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

  2. Confirm that the Proxy services were installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    • MatchAccountEBSProxyService

    • MatchContactEBSProxyService

    • FetchAccountEBSProxyService

    • FetchContactEBSProxyService

  3. Confirm the installed application is accessible using the following URL -

    1. For Account Match-Fetch: http://<server name>:<port number>/CustomerHub-matchfetch-context-root/faces/Organization.jspx

    2. For Contact Match-Fetch: http://<server name>:<port number>/CustomerHub-matchfetch-context-root/faces/Person.jspx

14.4 Undeploying Customer MDM: Match Fetch Enterprise Composite Application

To undeploy the Match Fetch application from Fusion Middleware Server:

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

  2. Run the command for your platform.

    Table 14-2 Undeployment Command for Customer MDM: Match Fetch Enterprise Composite Application

    PlatformUndeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    sh $AIA_HOME/services/core/UCM/UtilityServices/CustomerHub/DeploymentPlans/undeployCustomerHUBMatchAndFetchApp.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME%\services\core\UCM\UtilityServices\CustomerHub\DeploymentPlans\undeployCustomerHUBMatchAndFetchApp.bat
    

  3. Restart the SOA server.

  4. Uninstall the integration following the instructions in the Chapter 37, "Uninstalling Oracle AIA"

PKB11++PKYc|B$OEBPS/designtoreleaseagileebspim.htm Configuring and Deploying Design to Release: Agile - EBS

20 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:

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

20.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 20-1 Integration Server Details Screen Fields

FieldDescription

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.


20.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 20-2 Agile PLM Details Screen fields

FieldDescription

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.


20.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 20-3 Oracle E-Business Suite Server Details Screen fields

FieldDescription

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.


20.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 20-4 Oracle E-Business Suite Database Details Screen fields

FieldDescription

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.


20.2 Performing Predeployment Configurations

You must modify transaction properties to complete the integration deployment. To modify transaction values:

  1. Log in to WebLogic Server Console. Navigate to Services, JTA. Change the value of property JTA Transaction Timeout from 30 to 3600.

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

20.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:

  1. Configure your integration using the DCW.

  2. Deploy the integration to the Fusion Middleware server.

20.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:

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

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

  3. Restart the server.

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

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

  6. Click Next.

  7. Select the Design to Release: Agile - EBS / PIM PIP

  8. Click Next.

20.3.1.1 Specify Integration Server Details

To specify integration server details:

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

  2. Click Next.

20.3.1.2 Specify Agile PLM Application Details

To specify Agile PLM details:

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

  2. Click Next.

20.3.1.3 Specify Oracle E-Business Suite Server Details

To specify Oracle E-Business Suite Server details:

  1. Enter information about your Oracle E-Business Suite Server installation in the E-Business Suite Server Details screen.

  2. Click Next.

20.3.1.4 Specify Oracle E-Business Suite Database Details

To specify Oracle E-Business Suite Database details:

  1. Enter information about your Oracle E-Business Suite Database installation in the E-Business Suite Database Details screen.

  2. Click Next.

20.3.1.5 Complete Configuration

To complete configuration:

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


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

  3. When the configuration process completes without errors, the AIA DCW displays the Configuration Complete screen.

  4. Click Finish to close the DCW.

20.3.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

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

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

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

To deploy the integration to Fusion Middleware server:

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

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

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


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

20.4 Performing Postdeployment Configurations

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:

  1. Set the value for Profile Option:

    1. Profile Option Short Name as INV_EBI_SOASERVER_USER.

    2. Profile Option Display Name as EBS Integration: SOA SERVER USER.

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

  3. Copy the file to your local directory.

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

20.5 Verifying Deployment

To verify the Design to Release: Agile - EBS Pre-Built Integration deployment:

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

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

  3. Confirm that the Design to Release: Agile - EBS / PIM Pre-Built Integration processes were installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. 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 Services12.1.x with PIM + 9.3x with VM12.1.x with PIM + 9.3x12.1.x with PIM + 922x12.1.x + 93x with VM12.1.x + 93x12.1.x + 922x11.5.10 + 93x11.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 Processes12.1.x with PIM + 9.3x with VM12.1.x with PIM + 9.3x12.1.x with PIM + 922x12.1.x + 93x with VM12.1.x + 93x12.1.x + 922x11.5.10 + 93x11.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.


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

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

    Table 20-8 Application Registry Values for Agile

    FieldValue

    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

FieldValue

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)


20.5.1 Validating Security Policies

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.

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

To undeploy the integration from Fusion Middleware Server:

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

  2. Run the command for your platform.

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

    PlatformUn-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
    

  3. Restart the SOA server.

  4. Uninstall the integration following the instructions in Chapter 37, "Uninstalling Oracle AIA".

PKu5f5PKYc|BOEBPS/cover.htmO Cover

Oracle Corporation

PK[pTOPKYc|BOEBPS/commsordertobill.htm Configuring and Deploying the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

7 Configuring and Deploying the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

This chapter discusses how to configure and deploy the Oracle Communications Order to Cash Integration Pack for Siebel Customer Relationship Management and Oracle Communications Billing and Revenue Management (Comms Order to Cash: SBL CRM and BRM Pre-Built Integration).

This option assumes integration with a Central Order Management system, other than Oracle OSM. On deployment, this option deploys Test Orchestration Process (TOP) to take order fulfillment requests from Siebel and hand them off to Oracle BRM. However, this process is for simple sanity testing of the order flow between Siebel CRM and Oracle BRM. You must replace this process with your Order Management system following the steps detailed in Section 7.7, "Replacing Test Order Orchestration with your Order Management System".

This chapter includes the following sections:

7.1 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration. Enter the details of the Comms Order to Cash: SBL CRM and BRM 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.

7.1.1 Integration Server Details Screen

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

Table 7-1 Integration Server Details Screen Fields

FieldDescription

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: server1.company.com.

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


7.1.2 Siebel CRM Server Details Screen

Use this screen to enter details related to your Siebel CRM server instance. The screen contains the following fields:

Table 7-2 Siebel CRM Server Details Screen Fields

FieldDescription

Siebel Host name

This is a computer name of the Siebel host. For example: example1.corp.siebel.com. To find the value, contact your administrator.

Siebel Host name is _____________________________

Siebel HTTP Port

This value is the Siebel application port. For example: 80. To find the value, contact your administrator.

Siebel HTTP Port is ________________________________

InternetProtocol

This value is the Siebel host internet protocol. For example, http://. To find the value, contact your administrator.

InternetProtocol is _______________________

Note: Our internal environments are always on http://. The default value is https// and must be changed for Siebel web services and Session Pool Manager services to work.

Siebel Enterprise Server Name

This value is the Siebel enterprise server name. For example, siebel. To find the value, contact your administrator.

Siebel Enterprise Server Name is _________________________

Note: This value must be in lowercase (siebel) for the Update Account flow to work.

Siebel EAI Application User

The Siebel application user is used for making EAI web service calls. For example: sadmin. To find the value, contact your administrator.

Siebel EAI Application User is ___________________________

Siebel EAI Application Password

This is the password for the EAI user. For example: sadmin. To find the value, contact your administrator.

Siebel EAI Application Password is ________________________

Siebel Version

Version of application, for example Siebel 8.1.1 SIA.

Siebel Version is __________________________

Siebel Language

This is the language used by the Siebel application. For example, enu. To find the value, contact your administrator.

Siebel Language is ________________________


7.1.3 Siebel CRM Database Details Screen

Use this screen to enter details related to your Siebel CRM database instance. The screen contains the following fields:

Table 7-3 Siebel CRM Database Details Screen Fields

FieldDescription

Siebel Database Host

This value is typically the computer name. For example: server1.example.com. To find the value, contact your database administrator.

Siebel Database Host is _________________________________

Siebel Database Port

This is the Siebel database port. For example: 1521. To find the value, contact your database administrator.

Siebel Database Port is _________________________________

Siebel Database SID

This is the Siebel database system ID. For example: qa7a. To find the value, contact your database administrator.

Siebel Database SID is ________________________________

Siebel Database Username

Specifies a database user that has access to loading the EIM tables Siebel. To find this value, contact the database administrator. Example: ora12345

Siebel Database Username is ______________________

Siebel Database Password

This is the Siebel Database Password. For example: ora07103. To find the value, contact your database administrator.

Siebel Database Password is _____________________


7.1.4 Oracle Communications BRM Screen

Use this screen to enter details related to your Oracle Communications BRM instance. The screen contains the following fields:

Table 7-4 Oracle Communications BRM Details Screen

FieldDescription

Primary CM Host Name

This is the host name of the primary Connection Manager (CM) of the BRM server. For example: example1.portal.com To find this value, contact your Oracle AQ system administrator.

Primary CM Host Name is ______________________________

Primary CM Port Number

This is the port number of primary Connection Manager (CM) of the BRM server. For example: 12600. To find this value contact your Oracle AQ database administrator System Administrator

Primary CM Port Number is ______________________________

Database Host

This is the database host name of the Oracle AQ for which the BRM DM_AQ is configured. For example: example2.portal.com. To find this value, contact your Oracle AQ database administrator

Database Host is _______________________

Database Port

This is the database port number of the Oracle AQ. For example: 1521. To find this value, contact your Oracle AQ database administrator.

Database Port is _________________________

Oracle AQ Database SID

This is the database instance of the Oracle AQ. For example: orcl. To find this value, contact your Oracle AQ database administrator.

Oracle AQ Database SID is _______________________________

Oracle AQ Username

This is the database user name of the Oracle AQ. For example, PIN7820. To find this value, contact your Oracle AQ database administrator.

Oracle AQ Username is _________________________

Note: This value must be in uppercase (PIN7820) for the OOTB PLM flow to work.

Oracle AQ Password

This is the database password of the Oracle AQ. To find this value, contact your Oracle AQ database administrator.

Oracle AQ Password is ___________________________

AQ Queue Name

This is the queue name configured for the BRM DM_AQ. For example: AqportalUser. To find this value, contact your Oracle AQ database administrator.

AQ Queue Name is _________________________________


7.1.5 Session Pool Manager Details Screen

The Session Pool Manager (SPM) details are optional and required only when your Siebel server is outside of the firewall. If all your servers are within the network, leave these fields blank.

In the java.net application programming interface (API) used by SPM, proxies are supported through two system properties: http.proxyHost and http.proxyPort. They must be set to the proxy server and port respectively. This value is only set when ProxySettings_Enabled is set to TRUE.

Table 7-5 Session Pool Manager Details Screen Fields

FieldDescription

Proxy host url

This determines the server to be set in the system properties for http.proxyHost property.

Proxy host url is ___________________________

Proxy port

This determines the port to be set in the system properties for the http.proxyPort property.

Proxy port is ______________________________



Caution:

These fields are optional so leave the values blank. These values are required only if the Siebel server is outside of the firewall.


7.2 Performing Predeployment Configurations

This section discusses predeployment configurations for the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration.

7.2.1 Configuring the Timeout Values

This section describes how to modify the JTA Transaction Value and the SyncMaxWaitTime values.

To modify JTA Transaction Value:

  1. Log in to the WebLogic Server console.

  2. Navigate to Services, JTA.

  3. Change the value of the property Timeout Seconds to 3600.

  4. Click Save and activate the changes.

To modify SyncMaxWaitTime values:

  1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

  2. Expand the SOA folder and right-click soa-infra.

  3. Select SOA Administration, BPEL Properties.

  4. Click the More BPEL Configuration Properties link.

  5. Change the value of SyncMaxWaitTime to 120.

  6. Click Apply.

7.3 Configuring and Deploying the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

This section discusses the integration configuration and deployment process. There are two steps:

  1. Configure your integration using the DCW.

  2. Deploy the integration to the Fusion Middleware server.

7.3.1 Configuring the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

The screens that appear prompt you to enter the data that is required for successful configuration of the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration. Keep the completed worksheets of the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration screens ready before you launch the DCW.

To configure the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration:


Note:

If you are harvesting content to Oracle Enterprise Repository (OER), perform the first three steps. Else start from step 4.


  1. Navigate to ../Middleware/user_projects/domains/<domain_name>/bin and open setDomainEnv.sh for Linux based systems and setDomainEnv.bat for Microsoft Windows.

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

  3. Restart the server.

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

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

  6. Click Next.

  7. Expand Communications Pre-built Integrations and select Comms Order to Cash: Siebel CRM and BRM.

  8. Click Next.

7.3.1.1 Specify Integration Server Details

To specify integration server details:

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

  2. Click Next.

7.3.1.2 Specify Siebel CRM Server Details

To specify Siebel CRM server details:

  1. Enter information about your Siebel CRM application in the Application Details - Siebel CRM screen.

  2. Click Next.

7.3.1.3 Specify Siebel CRM Database Details

To specify Siebel CRM database details:

  1. Enter information about your Siebel CRM database in the Siebel CRM Database Details screen.

  2. Click Next.

7.3.1.4 Specify Oracle Communications BRM Details

To specify Oracle Communications BRM details:

  1. Enter Oracle Communications BRM information in the Oracle Communications BRM screen.

  2. Click Next.

7.3.1.5 Complete Configuration

To complete configuration:

  1. 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 7.3.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.


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

  3. When configuration process finishes without errors, the AIA DCW displays the Configuration Complete screen.

  4. Click Finish to close the DCW.

7.3.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

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

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

7.3.3 Deploying the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

To deploy the integration to Fusion Middleware server:

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

  2. 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 7-6 Deployment Commands for the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

    PlatformDeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    $AIA_HOME/pips/Communications/O2B/DeploymentPlans/deployO2B.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME%\pips\Communications\O2B\DeploymentPlans\deployO2B.bat
    

  3. Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/O2BDP_Deployments_YYYY-MM-DD_HH-MI-SS.log to verify successful deployment of the integration.

Oracle AIA ships a few artifacts in AIA Lifecycle Workbench which can be used in your integrations. These native artifacts created using FMW technologies such as BPEL, Mediator are natively supported by AIA Foundation Pack tools such as Project Lifecycle Workbench, Harvester, Deployment Generator, and AIA Installer Driver (AID). These artifacts include SOA artifact types such as composites, DataSources, DVM, xRef, and so on. These can be modified or new natively supported artifacts can be added using AIA Lifecycle Workbench and a BOM.xml file can be generated.

Integrations, most often, also require deployment of artifact types that are beyond what is supported by the Project Lifecycle Workbench and AIA Harvester. For instance, you may want to deploy artifacts such as Java applications, Shell Scripts, ANT based build scripts which constitute part of integration landscape in addition to the artifacts that are delivered by AIA. AIA also supports deployment of these supplementary artifacts. However, you must modify and add new non native artifacts outside AIA Lifecycle Workbench.

For more information on deploying artifacts, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".

7.4 Performing Postdeployment Configurations

This section discusses post deployment configuration for Comms Order to Cash: SBL CRM and BRM Pre-Built Integration. This section includes:

7.4.1 Suppressing Auto-Retry and Preventing Multiple Error Notifications and Trouble Tickets

To suppress auto-retry and prevent multiple error notifications and trouble tickets:

  1. Set the GlobalTxMaxRetry property for outbound adapters:

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

    2. Expand the SOA folder, right-click soa_infra.

    3. Select SOA Administration, Common Properties.

    4. Click More SOA Infra Advanced Configuration Properties.

    5. Search for the GlobalTxMaxRetry property and set the value as 0 (zero).

  2. Set the GlobalInboundJcaRetryCount property for inbound adapters:

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

    2. Expand the SOA folder, right-click soa_infra.

    3. Select Administration, System Mbean Browser.

    4. Search for oracle.as.soainfra.config, expand <Server>, expand AdapterConfig.

    5. Select Adapter.

    6. Search for the GlobalInboundJcaRetryCount property and set the value as 0 (zero).

  3. Change Audit Level from Development to Production for soa infrastructure:

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

    2. Expand the SOA folder, right-click soa_infra.

    3. Select SOA Administration, Common Properties.

    4. Choose Production from the Audit Level list.

    5. Click Apply.

  4. Stop and Start the SOA and Admin Server so that your changes can take effect.

7.4.2 Supporting Message Priority

As part of supporting message priority, follow the below steps to configure the queues (AIA_CRTBO_OUT_JMSQ, AIA_CRTCUST_OUT_JMS) so that the message is prioritized based on JMSPriority.

  1. Creating Destination Sort Key based on JMSPriority:

    1. Log in to http://<host name>:<port number>/console.

    2. Navigate to Services, Messaging, JMS Modules.

    3. Click AIAJMSModule.

    4. Click New and select Destination Sort Key option.

    5. Give a name AIA_SALESORDERJMSPRIORITY_KEY, click OK. The key is created.

    6. Click AIA_SALESORDERJMSPRIORITY_KEY link and choose JMSPriority from the Sort Key drop down list.

    7. Select Key Type as Int.

    8. Select Direction as Descending.

    9. Click Save.

  2. Attaching Destination Sort Key to JMS Queues:

    1. Click AIAJMSModule.

    2. Click AIA_CRTBO_OUT_JMSQ.

    3. In The Destination Keys section, newly created Key is displayed. Select and choose the key.

    4. Click Save.

  3. Repeat steps 2a to 2d for queue AIA_CRTCUST_OUT_JMSQ.

7.4.3 Updating Internal ID for the BRM Instance BRM_01

To update the internal ID for the BRM instance BRM_01 in the AIA Application Registry in the AIA application perform the following steps:

  1. Find the BRM instance ID that is specified in BRM Payload Configuration file:

    1. Go to the file system where your BRM portal is installed.

    2. Navigate to folder ../portal/7.4/sys/eai_js.

    3. Find the payload configuration file payloadconfig_crm_sync.xml.

    4. Open the file. The instance Id is specified as shown in Example 7-1.

    Example 7-1 Instance ID Specified in the BRM Payload Configuration File

    <ProductInfoChange Source="EVENT" Tag="ProductInfoChange"
                                StartEvent="/event/notification/price/products/modify">
              <Attribute Tag="InstanceId" Value="Portal"/>
              <Attribute Tag="xmlns" Value="http://www.portal.com/schemas/CRMSync"/>
              <Attribute Tag="xmlns:xsi" Value="http://www.w3.org/2001/XMLSchema-instance"/>
              <Attribute Tag="xsi:schemaLocation" Value="http://www.portal.com/schemas/CRMSync/ProductInfoChange.xsd"/>
              <Field PinFld="PIN_FLD_ACCOUNT_OBJ" Tag="AccountObj"/>
              <SubElement Name="ProductInfo" OnEvent="/event/notification/price/products/modify" />
    </ProductInfoChange>
    

    If it is Portal, this value appears as brmproductabo:InstanceId in the Product Event message from BRM. See Example 7-2.

    Example 7-2 BRM Instance ID Specified in the Message Payload

    <SyncProductReqMsg>
    <part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    name="SyncProduct">
    <brmproductabo:ProductInfoChange
    xmlns:brmproductabo="http://www.portal.com/schemas/CRMSync"
    brmproductabo:InstanceId="Portal">
    
  2. Update the Internal ID column to the Instance ID from BRM to the value above. For example: Portal.

  3. In AIA Application, go to AIA Application Registry, Setup, System and find the entry for System Code "BRM_01".

  4. Change that value to the InstanceId from the BRM Payload Configuration file. For example: Portal.

7.4.4 Setting up the AIA FMW Server


Note:

This step is required if cluster is the deployment topology.


Perform the following steps to enable tunneling:

  1. Configure http proxy host

    1. Modify mod_wl_ohs.conf

      For example, scratch/nmankodi/Oracle/Middleware/Oracle_WT1/instances/instance1/config/OHS/ohs1/mod_wl_ohs.conf

    2. Add the following location:

      <Location / bea_wls_internal >

      SetHandler weblogic-handler

      WebLogicCluster adc1140309.example.com:8001,adc2101063.example.com:8011

      WLLogFile /tmp/web_log.log

      </Location>

    3. Restart using ./opmnctl stopall, ./opmnctl startall

  2. Configure WebLogic Server

    1. Log in to WebLogic Server console.

    2. Click Admin and each manager server.

    3. Click Protocols, HTTP, Enable Tunneling.

    4. Save the configuration.

    5. Restart Admin and managed servers.

7.5 Verifying Deployment

To verify the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration deployment:

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

  2. Confirm that the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration components were successfully installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control: (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

    • AIACOMOrderFalloutNotificationJMSConsumer

    • AIAOrderFalloutJMSBridgeService

    • BillingResponseConsumer

    • Comms2CoreCustomerPartybridge

    • CommsProcessBillingAccountListEBF

    • CommsProcessFulfillmentOrderBillingAccountListEBF

    • CommunicationsBillingEBSV1

    • CommunicationsBillingResponseEBSV1

    • CommunicationsClassificationEBSV1

    • CommunicationsCustomerPartyEBSV2

    • CommunicationsCustomerPartyEBSV2Requencer

    • CommunicationsCustomerPartyResponseEBSV2

    • CommunicationsInstalledProductEBSV2

    • CommunicationsItemCompositionEBSV1

    • CommunicationsItemCompositionResponseEBSV1

    • CommunicationsPriceListEBSV2

    • CommunicationsPriceListResponseEBSV2

    • CommunicationsSalesOrderEBSV2

    • CommunicationsSpecificationEBSV1

    • CommunicationsSpecificationValueSetEBSV1

    • CommunicationsTroubleTicketEBSV1

    • CommunicationsTroubleTicketResponseEBSV1

    • Core2CommsCustomerPartyBridge

    • CreateTroubleTicketAIACommsReqImpl

    • CreateTroubleTicketSiebelCommsProvABCSImpl

    • CustomerPartyEBSV2

    • CustomerResponseConsumer

    • OrderOrchestrationConsumer

    • ProcessFOBillingAccountListRespOSMCFSCommsJMSProducer

    • ProcessFufillmentOrderBillingAccountListOSMCFSCommsJMSConsumer

    • ProcessFulfillmentOrderBillingBRMCommsAddSubProcess

    • ProcessFulfillmentOrderBillingBRMCommsDeleteSubProcess

    • ProcessFulfillmentOrderBillingBRMCommsMoveAddSubProcess

    • ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl

    • ProcessFulfillmentOrderBillingBRMCommsSuspendResumeSubProcess

    • ProcessFulfillmentOrderBillingBRMCommsUpdateSubProcess

    • ProcessFulfillmentOrderBillingOSMCFSCommsJMSConsumer

    • ProcessFulfillmentOrderBillingResponseOSMCFSCommsJMSProducer

    • ProcessInstalledProductSpecialRatingSetListBRMCommsProvABCSImpl

    • ProcessInstalledProductSpecialRatingSetListSiebelCommsJMSConsumer

    • ProcessInstalledProductSpecialRatingSetListSiebelCommsReqABCSImpl

    • ProcessSalesOrderFulfillmentOSMCFSCommsJMSProducer

    • ProcessSalesOrderFulfillmentSiebelCommsJMSConsumer

    • ProcessSalesOrderFulfillmentSiebelCommsReqABCSImpl

    • ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl

    • QueryClassificationListSiebelCommsProvABCSImpl

    • QueryCustomerPartyListSiebelProvABCSImplV2

    • QuerySpecificationListSiebelCommsProvABCSImpl

    • QuerySpecificationValueSetListSiebelCommsProvABCSImpl

    • SyncAccountSiebelAggregatorAdapter

    • SyncAccountSiebelReqABCSImpl

    • SyncAcctSiebelAggrEventConsumer

    • SyncAddressSiebelAggregatorAdapter

    • SyncBPSiebelAggregatorAdapter

    • SyncContactSiebelAggregatorAdapter

    • SyncCustomerPartyListBRM_01CommsJMSConsumer

    • SyncCustomerPartyListBRMCommsJMSProducer

    • SyncCustomerPartyListBRMCommsProvABCSImpl

    • SyncCustomerSiebelEventAggregator

    • SyncDiscountBRMCommsReqABCSImpl

    • SyncDiscountInfoChangeBRMAQ

    • SyncItemCompositionListSiebelCommsProvABCSImpl

    • SyncProductBRMCommsReqABCSImpl

    • SyncProductInfoChangeBRMAQ

    • TestOrderOrchestrationEBF

    • TransformAppContextSiebelService

    • UpdateSalesOrderOSMCFSCommsJMSConsumer

    • UpdateSalesOrderSiebelCommsProvABCSImpl

    • UpdateTroubleTicketSiebelCommsProvABCSImpl

7.5.1 Validating Security Policies

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:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control

  2. Expand WebLogic Domain.

  3. Select soa_domain.

  4. Right-click soa_domain.

  5. Select Web Services, Policies.

  6. Verify Service Policy attachment.

    1. Find no_authentication_service_policy in the list of policies.

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Service.

    4. Validate that all the composites are listed with local attachment to this service policy.

  7. Verify Client Policy attachment

    1. Navigate back to Web Services Policies screen.

    2. Navigate to Applies To LOV, select Service Clients and hit enter. Find no_authentication_client_policy.

    3. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    4. Change the Subject Type list box to SOA Reference.

    5. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.

      Table 7-7 No Authentication Service Policy Attachments for Comms Order to Cash: SBL and BRM

      CompositeService Policy

      SyncCustomerSiebelEventAggregator

      oracle/no_authentication_service_policy


      Table 7-8 No Authentication Client Policy Attachments for Comms Order to Cash: SBL and BRM

      CompositeService Policy

      SyncAccountSiebelReqABCSImpl

      oracle/no_authentication_client_policy

      QuerySpecificationListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      QuerySpecificationValueSetListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      UpdateTroubleTicketSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      SyncItemCompositionListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      UpdateSalesOrderSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      CreateTroubleTicketSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      QueryCustomerPartyListSiebelProvABCSImplV2

      oracle/no_authentication_client_policy

      QueryClassificationListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy


For integration implementation, see Oracle Application Integration Architecture Oracle Communication Order to Cash Integration Pack Implementation Guide for Siebel CRM, Oracle Order and Service Management, and Oracle Billing and Revenue Management.

Also see Oracle Application Integration Architecture Siebel CRM Integration Pack for Oracle Communications Billing and Revenue Management: Agent Assisted Billing Care Implementation Guide.

7.6 Undeploying the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

To undeploy the integration from Fusion Middleware Server:

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

  2. Run the command for your platform.

    Table 7-9 Undeployment Command for the Comms Order to Cash: SBL CRM and BRM Pre-Built Integration

    PlatformUndeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    $AIA_HOME/pips/Communications/O2B/DeploymentPlans/undeployO2B.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME%\pips\Communications\O2B\DeploymentPlans\undeployO2B.bat
    

  3. Restart the SOA server.

  4. Uninstall the integration following the instructions in the Chapter 37, "Uninstalling Oracle AIA"

7.7 Replacing Test Order Orchestration with your Order Management System

After doing a simple flow test of order flow using TOP process, complete the following steps to replace TOP with your own Order Management System.

This step is mandatory before going into production. TOP is not a production quality code and not a supported product feature. So it must be replaced with your Order Management system after simple sanity testing of order flow between Siebel CRM and Oracle BRM.

  1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control: (http://<server name>:<port number>/em/) using admin access and undeploy the following composites:

    • BillingResponseConsumer

    • CustomerResponseConsumer

    • OrderOrchestrationConsumer

    • TestOrderOrchestrationEBF

  2. Configure your Order Management system to interact to AIA through the JMS queues listed in Table 7-10. You can find these queues in Weblogic by following these steps:

    1. Go to Oracle Weblogic Server Administration Console, Domain Structure.

    2. Select your soa domain.

    3. Go to Services, Messaging, JMS Modules, AIAJMSModule.

    4. Find these queues by matching the JNDI names of the queue type JMS resources.

Table 7-10 JMS Queues for AIA Interactions with Order Management System

JMS QueuesDescription

jms/aia/AIA_CRTFO_IN_JMSQ

Inbound queue to your Order Management system for picking up incoming Sales Order from Siebel. The order message is of type ProcessSalesOrderFulfillmentEBM, wrapped into the SOAP envelope in the following way.

<tns:Envelope xmlns:tns="http://schemas.xmlsoap.org/soap/envelope/"><tns:Body><crtfo:CreateOrder xmlns:crtfo="http://xmlns.example.com/communications/ordermanagement"><sord:ProcessSalesOrderFulfillmentEBM xmlns:sord="http://xmlns.example.com/EnterpriseObjects/Core/Custom/EBO/SalesOrder/V2">...</sord:ProcessSalesOrderFulfillmentEBM> </crtfo:CreateOrder></tns:Body></tns:Envelope>

jms/aia/AIA_CRTCUST_OUT_JMSQ

Outbound q)ueue from your Order Management system for creating customer in Oracle BRM. The message must confirm to ProcessFulfillmentOrderBillingAccountListEBM schema. Order Management must wait for response before doing further communication with Oracle BRM for the current order.

jms/aia/AIA_UPDCUST_IN_JMSQ

This is a response queue of jms/aia/AIA_CRTCUST_OUT_JMSQ. It contains success response message from AIA in ProcessFulfillmentOrderBillingAccountListResponseEBM schema.

jms/aia/AIA_CRTBO_OUT_JMSQ

Outbound queue from your Order Management system for creating billing order in Oracle BRM. The message must confirm to ProcessFulfillmentOrderBillingEBM schema. Order Management must wait for response before doing further communication with Oracle BRM for the current order message.

jms/aia/AIA_UPDBO_IN_JMSQ

This is a response queue of jms/aia/AIA_CRTBO_OUT_JMSQ. It contains success response message from AIA in ProcessFulfillmentOrderBillingResponseEBM schema.

jms/aia/AIA_UPDSO_OUT_JMSQ

Outbound queue from your Order Management system for updating Order information in Siebel CRM. The message must confirm to UpdateSalesOrderEBM schema. This is an asynchronous flow, so no response is sent back to Order Management.


PKWMPKYc|BOEBPS/o2csiebelcrmebs.htm Configuring and Deploying the Order to Cash for Siebel CRM - EBS PIP

24 Configuring and Deploying the Order to Cash for Siebel CRM - EBS PIP

This chapter discusses how to configure and deploy the Siebel CRM Integration Pack for Oracle Order Management: Order to Cash (Order to Cash: Siebel CRM - EBS PIP).

This chapter includes the following sections:

24.1 Configuring Oracle Data Integrator (Optional)

To run AIA Pre-Built Integrations Installer you must have Oracle Data Integrator (ODI) access with Supervisor privileges.

ODI is used by the O2C PIP for the initial load flows. You can skip this section if you do not plan to run the initial load flows. If you intend to run the ODI based initial loads, review the details in this section and perform tasks accordingly.

For installation purposes, the ODI software must reside at the same server where Foundation Pack is installed. Once the PIP installation is complete, the ODI software can be installed onto another server (if desired) connecting to the master and work repositories used during the PIP installation.

24.1.1 Creating Oracle Data Integrator Repositories

You can use an existing master repository if it exists on an Oracle database and its ID is not 0. If the ID is 0, AIA advises you to create a another master repository.

You can use an existing work repository if it exists on an Oracle database and its ID is not 778. If the ID is 778, AIA advises you to create a another repository and not to use 778 as the Work Repository ID.

Table 24-1 details a list of ids you must avoid when creating master and work repositories.

Table 24-1 Prohibited IDs

Master Repository Prohibited IDsWork Repository Prohibited IDs

666

667

611

711

999

516

515

126


When you run the DCW, it inserts or updates the ODI artifacts into these repositories.

AIA recommends that you make a backup copy of master and work repositories before you start the installation process.

For information about creating Oracle Data Integrator Master and Work repositories, see the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator, "Administering the Oracle Data Integrator Repositories."

24.1.2 Performing Postinstallation Configurations for ODI

Perform the following steps to apply the required patches to your ODI 11.1.1.5.0.

To install prerequisite installer patch #10288265:

  1. Access My Oracle Support [https://support.oracle.com]

  2. Navigate to the Patches & Updates tab

  3. In the Patch Name or Number field, write 10288265

  4. Select your platform

  5. Click Search

  6. Download and install patch #10288265

To install patch #12837214:

  1. Access My Oracle Support [https://support.oracle.com]

  2. Navigate to the Patches & Updates tab

  3. In the Patch Name or Number field, write 12837214

  4. Select your platform

  5. Click Search

  6. Download and install patch #12837214

After applying the patches, launch the ODI Installer:

  1. Go to Topology.

  2. Go to Physical Architecture.

  3. Find the XML technologies and expand it.

    You should see data sources for all DVM's used in your ODI flows.

  4. Select each DVM data source.

  5. Go to the JDBC tab.

  6. Append this to the end of the URL "&back_compat_specific_keywords=true"

  7. Test the data source to make sure the connection is successful.

  8. Save your changes.

For a screenshot of this screen in ODI Installer, see Appendix B, "Oracle Data Integrator Screen".

24.2 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of the Order to Cash: Siebel CRM - EBS PIP. Enter the details of the Order to Cash: Siebel CRM - EBS PIP screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.

24.2.1 PIP Server Details Screen

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

Table 24-2 PIP Server Details Screen Fields

FieldDescription

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


24.2.2 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 24-3 Oracle E-Business Suite Server Details Screen Fields

FieldDescription

E-Business Suite Host Name

Specifies the fully qualified 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: server2.xyz.com. To find this value, contact your administrator.

Workflow Business Event System Name is _________________

E-Business Suite Version

This is the version of the E-Business Suite Application.


24.2.3 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 24-4 Oracle E-Business Suite Database Details Screen Fields

FieldDescription

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.

Note: Ensure that the database user name is entered with the correct case. Else the ODI based initial loads may result in errors.

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: server1.

Database Schema is __________________________________

Note: All the database credentials are used for creating the connection pool URL (universal resource locator) and data source URLs.


24.2.4 Oracle Transportation Management (OTM) Server Details Screen (Optional)

Use this screen to enter details related to your OTM server instance. If the Shipping Charges flow of the Order to Cash: Siebel CRM - EBS PIP to Cash PIP is not being used, these details are optional. The screen contains the following fields:

OTM System Name and OTM System Version fields are optional.

Table 24-5 Oracle Transportation Management (OTM) Server Details Screen Fields

FieldDescription

OTM Host Name

Specifies the fully qualified system name of the OTM application. Example: example1.corp.oracle.com

OTM Host Name is ___________________________________

OTM HTTP Port

This value is the OTM port. To find this value, contact your administrator. Example: 8024

OTM HTTP Port is ______________________________________

OTM User Name

To find this value, contact your administrator.

OTM User Name is ____________________________________

OTM Password

To find this value, contact your administrator.

OTM Password is _____________________________________

OTM System Name

To find this value contact your administrator.

OTM System Name is _________________________________

OTM System Version

To find this value contact your administrator.

OTM System Version is _________________________________


24.2.5 Oracle Transportation Management (OTM) Database Details Screen (Optional)

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

Table 24-6 Oracle Transportation Management (OTM) Database Details Screen Fields (Optional)

FieldDescription

OTM Database Host

Specifies the fully qualified system name of the OTM database. Example: example1.corp.oracle.com

OTM Host Name is ___________________________________

OTM Database Port

This value is the OTM database port. To find this value, contact your database administrator. Example: 8024

OTM HTTP Port is ______________________________________

OTM Database User Name

To find this value, contact your database administrator.

OTM User Name is ____________________________________

OTM Database Password

To find this value, contact your database administrator.

OTM Password is _____________________________________

OTM Database SID

This value is OTM Database System ID. To find this value contact your database administrator.

OTM Database SID is _____________________________


24.2.6 Siebel CRM Server Details Screen

Use this screen to enter details related to your Siebel CRM server instance. The screen contains the following fields:

Table 24-7 Siebel CRM Server Details Screen Fields

FieldDescription

Siebel Host name

Specifies the fully qualified system name of the Siebel CRM application. Example: example1.corp.oracle.com.

Siebel Host name is ____________________________

Siebel HTTP Port

This is the value of the Siebel CRM application port. To find this value, contact your administrator. Example: 8024.

Note: Enter 80 as the port number, if the default port is used.

Siebel HTTP Port is _____________________________.

Siebel EAI Application User

This value is the Siebel integration user used to make EAI web service calls. To find this value, contact your administrator.

Siebel EAI Application User is __________________________

Siebel EAI Application Password

To find this value, contact the database administrator.

Siebel EAI Application Password is ________________________

Siebel Enterprise Server Name

To find this value, contact the database administrator.

Siebel Enterprise Server Name is _________________________

Siebel Version

This is the version of the Siebel CRM application. Valid value for Order to Cash: Siebel CRM - EBS PIP is 8.0.0.8 and 8.1.1.3. Other versions are not supported for this release.


24.2.7 Siebel CRM Database Details Screen

Use this screen to enter details related to your Siebel CRM database instance. The screen contains the following fields:

Table 24-8 Siebel CRM Database Details Screen Fields

FieldDescription

Siebel Database Host

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

Siebel Database Host is _________________________________

Siebel Database Port

To find this value, contact the database administrator. Example: 1521

Siebel Database Port is _________________________________

Siebel Database Username

Specifies a database user that has access to loading the EIM tables Siebel. To find this value, contact the database administrator. Example: ORA12345

Note: Ensure that the database user name is entered with the correct case. Else the ODI based initial loads may result in errors.

Siebel Database Username is ____________________________

Siebel Database Password

To find this value, contact your administrator.

Siebel Database Password is _____________________________

Siebel Database SID

To find this value, contact the database administrator. Example: orcl

Siebel Database SID is _________________________________


24.2.8 Oracle Data Integrator Access Details Screens (Optional)

Oracle Data Integration Access Information is captured in three screens. Use these screens to enter details to access the Oracle Data Integrator (ODI). The screens contain the following fields:

The ODI screens are optional and they help you capture the ODI details and are only required you intend to run the ODI based Initial Data Loads for the PIP. See Oracle Application Integration Architecture Siebel CRM Integration Pack for Oracle Order Management: Order to Cashfor details on how to deploy and execute these Initial Loads.

Table 24-9 Oracle Data Integrator Access Details Screen Fields

FieldDescription

Path to Oracle Data Integrator

This value is the fully qualified path to the ODI HOME, including the agent folder in the oracledi directory. The default is the environment variable ODI_HOME. Linux example: /slot/ems1203/oracle/ODI11113/oracledi/agent.

Path to ODI is ____________________________

Note: The existence of the ODI software is validated by checking whether odiparams.sh (or .bat) exists in the ODI_HOME/agent/bin directory.

ODI User

Enter the user name to access ODI. Example: SUPERVISOR.

ODI user is ______________________________

ODI Password

Enter the password to access ODI. Example: SUNOPSIS.

ODI password is ___________________________

Path for exported DVMs

Enter the path to the directory to export domain value mappings (DVMs). Example: $AIA_HOME/abc

One of the steps for setting up the PIP is to export some DVMs to a location. The Installer must have this location to configure ODI artifacts during the install. It is recommended to choose this location in the same server where ODI software runs.

Path for Exported DVMs is _______________________


24.2.9 Oracle Data Integrator Master Repository Details Screen (Optional)

Use this screen to enter details to access the ODI master repository. The screen contains the following fields:

Table 24-10 Oracle Data Integrator Master Repository Details Screen Fields

FieldDescription

Database Host Name

To find this value, contact your database administrator. Example: server1.oracle.com

ODI Master Repository Database Host Name is _________________

Database Port Number

To find this value, contact your database administrator. Example: 1606

ODI Master Repository Database Port Number is_________________

Database Username

To find this value, contact your database administrator. Example: snpm

ODI Master Repository Database Username is _________________

Database Password

To find this value, contact your database administrator. Example: snpm

ODI Master Repository Database Password is _________________

Database SID

To find this value, contact your database administrator. Example: orcl

ODI Master Repository Database SID is _________________


24.2.10 Oracle Data Integrator Work Repository Details for Order to Cash Screen (Optional)

The install process imports the Order to Cash: Siebel CRM - EBS PIP ODI artifacts into an ODI work repository. You can provide an existing ODI work repository or provide an empty one. It is recommended to use an empty repository.

For a step-by-step instructions on how to configure Oracle Data Integrator (ODI) and then perform initial data loads for customer data, product data, price list data, and assets data, see Oracle® Application Integration Architecture Siebel CRM Integration Pack for Oracle Order Management: Order to Cash Implementation Guide, chapter "Running Initial Data Loads".

Use this screen to enter details related to the ODI work repository. The screen contains the following fields:

Table 24-11 Oracle Data Integrator Work Repository Details for Order to Cash: Siebel CRM - EBS PIP Screen Fields

FieldDescription

ODI Work Repository Name

Enter the name you gave to the ODI work repository for Order to Cash: Siebel CRM - EBS PIP artifacts. Example: OrderToCash

ODI Work Repository Name is: _________________________

ODI Work Repository ID

Enter the ID number that you used for the ODI work repository. It should be between 1 and 899. Example: 42

Do not use 900. Also do not use the ID used for other work repositories.

ODI Work Repository ID is: ______________


24.2.11 Session Pool Manager Screen (Optional)

This PIP uses the Session Pool Manager utility to interact with Siebel web services. If the AIA server must invoke Siebel web services through a proxy server, fill in the values in this screen. If no proxy server is involved, these values can be left blank.

Use this screen to enter details related to your Session Pool Manager.

The screen contains the following fields:

Table 24-12 Session Pool Manager Screen Fields

FieldDescription

Proxy Host URL

Specify the proxy host location. Example: www-proxy.your.company.com

Proxy Host URL is _________________________________

Proxy Port

Specify the proxy port. Example: 80

Proxy Port is _________________________________


For information about Session Pool Manager, see Oracle Application Integration Architecture Process Integration Pack Utilities Guide, "Session Pool Manager".

24.3 Configuring and Deploying the Order to Cash: Siebel CRM - EBS

This section discusses the PIP configuration and deployment process. There are two steps:

  1. Configure your PIP using the deployment DCW.

  2. Deploy the PIP to the Fusion Middleware server.

24.3.1 Configuring the Order to Cash: Siebel CRM - EBS PIP

The screens that appear prompt you to enter the data that is required for successful configuration of the Order to Cash: Siebel CRM - EBS PIP. Keep the completed worksheets of the Order to Cash: Siebel CRM - EBS PIP screens ready before you launch the DCW.

By default OTM is not defined as a participating application for the Order to Cash: Siebel CRM - EBS PIP in the DCW. If you intend to use the Shipping Charges flow of the Order to Cash: Siebel CRM - EBS PIP, define OTM as participating application.

Define OTM as a participating application for DCW (Optional)

To define OTM as participating application:

  1. Open <AIA_HOME>/pips/PIPManifest.xml.

  2. Find the PIP OrderToCash, and in the participating application section for this PIP, uncomment the entry for OTM.


Note:

If you are harvesting content to OER, perform the first three steps. Else start from step 4.


To configure the Order to Cash: Siebel CRM - EBS PIP:

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

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

  3. Restart the server.

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

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

  6. Click Next.

  7. Select the Order to Cash: Siebel CRM - EBS PIP.

  8. If you intend to configure the ODI details for Order to Cash Initial Loads, also select the Order to Cash: Siebel CRM - EBS Initial Loads PIP.

  9. Click Next.

24.3.1.1 Specify PIP Server Details

To specify PIP Server details:

  1. Enter information related to your PIP server in the PIP Server Details screen.

  2. Click Next.

24.3.1.2 Specify Oracle E-Business Suite Server Details

To specify Oracle E-Business Suite server details:

  1. Enter your Oracle E-Business Suite Server information in the E-Business Suite Server Details screen.

  2. Click Next.

24.3.1.3 Specify Oracle E-Business Suite Database Details

To specify Oracle E-Business Suite database details:

  1. Enter your Oracle E-Business Suite Database connection information in the E-Business Suite Database Details screen.

  2. Click Next.

24.3.1.4 Specify Oracle Transportation Management Server Details (Optional)


Note:

The OTN screens appear only if you have uncommented OTN as participating application in PIPManifest.xml.


To specify details of the Oracle Transportation Management (OTM) Server:

  1. Enter your OTM Server information in the Oracle Transportation Management (OTM) Server Details screen.

  2. Click Next.

24.3.1.5 Oracle Transportation Management (OTM) Database Details Screen (Optional)

To specify details of the Oracle Transportation Management (OTM) Database:

  1. Enter your OTM Server information in the Oracle Transportation Management (OTM) Database Details screen.

  2. Click Next.

24.3.1.6 Specify Siebel CRM Server Details

To specify Siebel CRM server details:

  1. Enter your Siebel CRM connection information in the Application Details - Siebel CRM screen

  2. Click Next.

24.3.1.7 Specify Siebel CRM Database Details

To specify Siebel CRM database details:

  1. Enter your Siebel CRM Database connection information in the Siebel CRM Database Details screen.

  2. Click Next.

24.3.1.8 Specify Oracle Data Integrator Access Details (Optional)


Note:

The ODI screens appear if you have selected the Order to Cash: Siebel CRM - EBS Initial Loads PIP.


To specify Oracle Data Integrator access details:

  1. Enter information about your ODI access installation in the Oracle Data Integrator Access Information screens.

    ODI access information is captured in three screens. Enter the following information in the screens.

  2. Specify the ODI Home.

  3. Click Next.

  4. Enter ODI User and ODI Password.

  5. Click Next.

  6. Specify the Path for exported DVMs.

  7. Click Next.

24.3.1.9 Specify Oracle Data Integrator Master Repository Details (Optional)

To specify Oracle Data Integrator master repository details:

  1. Enter information about your ODI master repository installation in the Oracle Data Integrator Master Repository screen.

  2. Click Next.

24.3.1.10 Specify Oracle Data Integrator Work Repository Details for Order to Cash (Optional)

To specify Oracle Data Integrator Work Repository Details for Order to Cash:

  1. Enter information about your ODI work repository installation in the Oracle Data Integrator Work Repository Details for Order to Cash screen.

  2. Click Next.

24.3.1.11 Specify Session Pool Manager Details

To specify Session Pool Manager details:

  1. Enter information related to your Session Pool Manager installation in the Session Pool Manager Details screen.

  2. Click Next.

24.3.1.12 Complete Configuration

To complete configuration:

  1. 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 PIP. You can configure using the steps described in Section 24.3.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.


  2. Click Configure to accept the configuration.

    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.

  3. When configuration process finishes without errors, the AIA DCW displays the Configuration Complete screen.

  4. Click Finish to close the DCW.

24.3.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

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

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

24.3.3 Deploying the Order to Cash: Siebel CRM - EBS

To deploy the PIP to Fusion Middleware server, run the command specific to your platform:

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

  2. 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 undeployment command too.


    Table 24-13 Deployment Commands for the Order to Cash: Siebel CRM - EBS PIP

    PlatformDeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems

    HP-UX

    ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml  
    -DDeploymentPlan=<AIA_HOME>/pips/OrderToCash/DeploymentPlans/OrderToCashDP.xml  
    -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml  
    -DSupplementaryDeploymentPlan=<AIA_HOME>/pips/OrderToCash/DeploymentPlans/OrderToCashSupplementaryDP.xml  
    -DDeploymentPolicyFile=<AIA_HOME>/pips/OrderToCash/DeploymentPlans/OrderToCashConditionalPolicy.xml  
    -l <AIA_HOME>/pips/OrderToCash/DeploymentPlans/OrderToCash.log
    

    Microsoft Windows

    ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml  
    -DDeploymentPlan=<AIA_HOME>\pips\OrderToCash\DeploymentPlans\OrderToCashDP.xml  
    -DPropertiesFile=<AIA_HOME>\aia_instances\<aia_instance>\config\AIAInstallProperties.xml  
    -DSupplementaryDeploymentPlan=<AIA_HOME>\pips\OrderToCash\DeploymentPlans\OrderToCashSupplementaryDP.xml  
    -DDeploymentPolicyFile=<AIA_HOME>\pips\OrderToCash\DeploymentPlans\OrderToCashConditionalPolicy.xml  
    -l <AIA_HOME>\pips\OrderToCash\DeploymentPlans\OrderToCashDP.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 PIPs are not displayed.


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

24.4 Performing Postdeployment Configurations

Perform the following tasks as part of postdeployment configurations for the Order to Cash: Siebel CRM - EBS PIP.

24.4.1 Setting up Order to Cash PIP

As part of this PIP implementation, review and perform a few application and PIP related configurations as described in Oracle Application Integration Architecture Siebel CRM Integration Pack for Oracle Order Management: Order to Cash "Implementing the Order to Cash: Siebel CRM – EBS Process Integration Pack".

24.4.2 Configuring Session Pool Manager

This PIP uses the Session Pool Manager utility. Configure Session Pool Manager after you install the PIP. For information on how to configure Session Pool Manager for your integration environment and needs, see the Oracle Application Integration Architecture Process Integration Pack Utilities Guide, "Session Pool Manager".

24.5 Verifying Deployment

To verify the Order to Cash: Siebel CRM - EBS PIP deployment:

  1. 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 PIP 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 PIP is successfully installed.

  2. Confirm that the Order to Cash: Siebel CRM - EBS PIP services were installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

    • AIASessionPoolManager

    • BulkLoadProductEbizReqABCSImpl

    • CalculateShippingChargeSalesOrderSiebelReqABCSImpl

    • CheckATPSalesOrderSiebelReqABCSImpl

    • ConfiguratorCopyConfigEbizAdapter

    • ConfiguratorUserLangSiebelAdapter

    • CreateAssetSiebelProvABCSImpl

    • CreateItemEbizEventConsumer

    • CreateItemInstanceEbizEventConsumer

    • CreateItemInstanceEbizReqABCSImpl

    • CreateProductEbizReqABCSImpl

    • CreateSalesOrderEbizProvABCSImpl

    • CreditCheckSalesOrderSiebelReqABCSImpl

    • CustomerPartyEBSV2

    • CustomerPartyOrchestrationEBSV2

    • CustomerPartyOrchestrationResponseEBSV2

    • CustomerPartyResponseEBSV2

    • ExplodeItemCompositionEbizAdapter

    • FetchATPScheduleSequenceEbizAdapter

    • GetItemValidationOrganizationEbizAdapter

    • GetItemValidationOrganizationOUEbizAdapter

    • GetOperatingUnitIVOrgEbizAdapter

    • GetSalesOrderEbizAdapter

    • GetSalesOrderLineShippingDetailsEbizAdapter

    • InstalledProductEBSV2

    • InterfaceCustomerToFulfillmentEBF

    • InterfaceSalesOrderToCustomerEBFV2

    • InterfaceSalesOrderToFulfillmentEBF

    • InterfaceSyncProductStructureEBF

    • ItemCompositionEBS

    • ItemCompositionOrchestrationEBS

    • ItemCompositionResponseEBS

    • ItemEBSV2

    • MergeAccountEbizEventConsumer

    • MergeAccountEbizReqABCSImpl

    • MergePartyEbizEventConsumer

    • MergePartyEbizReqABCSImpl

    • PaymentAuthorizationSalesOrderSiebelReqABCSImpl

    • ProcessCreditChargeAuthorizationEbizAdapter

    • ProcessCreditChargeAuthorizationEbizProvABCSImpl

    • ProcessCreditEligibilityEbizAdapter

    • ProcessCreditEligibilityEbizProvABCSImpl

    • ProcessQuoteSiebelJMSConsumer (applicable only for Siebel 8.0.x)

    • ProcessQuoteSiebelJMSProducer (applicable only for Siebel 8.0.x)

    • ProcessQuoteSiebelReqABCSImpl

    • ProcessQuoteSoapMsgSiebelJMSConsumer (applicable only for Siebel 8.1.x)

    • ProcessSalesOrderATPCheckEbizAdapter

    • ProcessSalesOrderATPCheckEbizProvABCSImpl

    • ProcessSalesOrderEbizAdapter

    • ProcessSalesOrderShippingChargeLogisticsProvABCSImpl

    • ProcessSalesOrderSiebelJMSConsumerV2 (applicable only for Siebel 8.0.x)

    • ProcessSalesOrderSiebelJMSProducerV2 (applicable only for Siebel 8.0.x)

    • ProcessSalesOrderSiebelReqABCSImplV2

    • ProcessSalesOrderSoapMsgSiebelJMSConsumer (applicable only for Siebel 8.1.x)

    • QueryCustomerPartyEbizAdapter

    • QueryCustomerPartyListEbizCreateAdapter

    • QueryCustomerPartyListEbizUpdateAdapter

    • QueryCustomerPartyListSiebelProvABCSImplV2

    • QueryItemCompositionEbizAdapter

    • QueryItemCompositionListEbizProvABCSImpl

    • QueryItemInstanceEbizAdapter (applicable only for E-Business Suite 11.x)

    • QueryItemInstanceEbizR12VersionAdapter (applicable only for E-Business Suite 12.x)

    • QueryMergeAccountEbizAdapter

    • QueryMergeOrgCustEbizAdapter

    • QueryPartyMergeEbizAdapter

    • QueryRelatedOrgCustEbizAdapter

    • QueryResponsibilityEbizAdapter

    • QuerySimpleItemAdapter

    • QuerySimpleItemBulkLoadAdapter

    • QuerySimpleItemUpdateAdapter

    • QueryStructureItemCompositionEbizAdapter

    • ReceivedPaymentEBS

    • RequestProductStructureSiebelJMSConsumer

    • RequestProductStructureSiebelJMSProducer

    • RequestProductStructureSiebelReqABCSImpl

    • SalesOrderEBSV2

    • SalesOrderOrchestrationEBSV2

    • SalesOrderOrchestrationResponseEBSV2

    • SalesOrderResponseEBSV2

    • SyncAccountSiebelAggregatorAdapter

    • SyncAccountSiebelReqABCSImpl

    • SyncAcctSiebelAggrEventConsumer

    • SyncAddressSiebelAggregatorAdapter

    • SyncBPSiebelAggregatorAdapter

    • SyncContactSiebelAggregatorAdapter

    • SyncContactSiebelReqABCSImpl

    • SyncContSiebelAggrEventConsumer

    • SyncCustomerPartyListEbizAdapter

    • SyncCustomerPartyListEbizEventConsumer

    • SyncCustomerPartyListEbizProvABCSImpl

    • SyncCustomerPartyListEbizReqABCSImpl

    • SyncCustomerPartyListPersonEbizAdapter

    • SyncCustomerPartyListSiebelProvABCSImpl

    • SyncCustomerSiebelEventAggregator

    • SyncItemCompositionListSiebelProvABCSImpl

    • SyncProductSiebelProvABCSImpl

    • SyncSalesOrderEbizProvABCSImpl

    • TransformAppContextEbizService

    • TransformAppContextLogisticsService

    • TransformAppContextSiebelService

    • UpdateAssetSiebelProvABCSImpl

    • UpdateItemEbizEventConsumer

    • UpdateItemInstanceEbizEventConsumer

    • UpdateItemInstanceEbizReqABCSImpl

    • UpdateProductEbizReqABCSImpl

    • UpdateSalesOrderEbizEventConsumer

    • UpdateSalesOrderEbizReqABCSImpl

    • UpdateSalesOrderSiebelProvABCSImpl

  3. Verify whether Session Pool Manager is successfully installed and ensure that the Siebel server is active.

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).

    2. Expand Farm_soa_domain, SOA, soa-infra (soa_server1), Default and click AIASessionPoolManager on the left panel.

    3. Click Test.

    4. Enter Operation = Start.

    5. Under the collapsible section titled Security, select WSS Username Token and enter the WLS admin user name and password.

    6. Enter Input Argumemt Host Id = SEBL_01.

    7. Click Test Web Service.

      You should see a successful initialization response message. For more information and troubleshooting steps, see Oracle Application Integration Architecture Process Integration Pack Utilities Guide, "Session Pool Manager".

24.5.1 Validating Security Policies

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 PIP have locally attached security policies.

To validate locally attached security policies:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

  2. Navigate to WebLogic Domain, soa_domain, Web Services, Policies.

  3. Verify Service Policy attachment.

    1. Select Security from the Category list and Service Clients from the Applies To list, and click Search/Arrow.

    2. Find the service policy in the list of policies.

    3. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    4. Change the Subject Type list box to SOA Service.

    5. Validate that all the composites are listed with local attachment to this service policy.

  4. Verify Client Policy attachment

    1. Navigate back to Policies screen.

    2. Select Security from the Category list and Service Endpoints from the Applies To list, and click Search/Arrow to refresh the list of policies.

    3. Find the client policy in the list of policies

    4. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    5. Change the Subject Type list box to SOA Reference.

    6. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.

      Table 24-14 Service Policy Attachments for Order to Cash: Siebel CRM - EBS PIP

      CompositeService Policy

      AIASessionPoolManager

      oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON

      TransformAppContextSiebelService

      oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON

      TransformAppContextEbizService

      oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON

      TransformAppContextLogisticsService

      oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON


      Table 24-15 No Authentication Service Policy Attachments for Order to Cash: Siebel CRM - EBS PIP

      CompositeService Policy

      RequestProductStructureSiebelJMSProducer

      oracle/no_authentication_service_policy

      ConfiguratorUserLangSiebelAdapter

      oracle/no_authentication_service_policy

      PaymentAuthorizationSalesOrderSiebelReqABCSImpl

      oracle/no_authentication_service_policy

      CreditCheckSalesOrderSiebelReqABCSImpl

      oracle/no_authentication_service_policy

      CalculateShippingChargeSalesOrderSiebelReqABCSImpl

      oracle/no_authentication_service_policy

      ProcessSalesOrderSiebelJMSProducerV2 (only applicable for Siebel 8.0.x)

      oracle/no_authentication_service_policy

      ProcessQuoteSiebelJMSProducer (only applicable for Siebel 8.0.x)

      oracle/no_authentication_service_policy

      SyncCustomerSiebelEventAggregator

      oracle/no_authentication_service_policy

      CheckATPSalesOrderSiebelReqABCSImpl

      oracle/no_authentication_service_policy


      Table 24-16 Saml Opt On Client Policy Order to Cash: Siebel CRM - EBS PIP

      CompositeReferenceClient Policy

      SyncCustomerSiebelEventAggregator

      SyncContactSiebelAggregatorAdapter

      oracle/aia_wss10_saml_token_client_policy_OPT_ON

      SyncCustomerSiebelEventAggregator

      SyncAddressSiebelAggregatorAdapter

      oracle/aia_wss10_saml_token_client_policy_OPT_ON

      SyncCustomerSiebelEventAggregator

      AIAAsyncErrorHandlingBPELProcess

      oracle/aia_wss10_saml_token_client_policy_OPT_ON

      SyncCustomerSiebelEventAggregator

      SyncBPSiebelAggregatorAdapter

      oracle/aia_wss10_saml_token_client_policy_OPT_ON

      SyncCustomerSiebelEventAggregator

      SyncAccountSiebelAggregatorAdapter

      oracle/aia_wss10_saml_token_client_policy_OPT_ON

      TransformAppContextSiebelService

      AIAAsyncErrorHandlingBPELProcess

      oracle/aia_wss10_saml_token_client_policy_OPT_ON

      TransformAppContextLogisticsService

      AIAAsyncErrorHandlingBPELProcess

      oracle/aia_wss10_saml_token_client_policy_OPT_ON

      TransformAppContextEbizService

      AIAAsyncErrorHandlingBPELProcess

      oracle/aia_wss10_saml_token_client_policy_OPT_ON

      TransformAppContextEbizService

      QueryRespEbizAdapter

      oracle/aia_wss10_saml_token_client_policy_OPT_ON


      Table 24-17 No Authentication Client Policy for Order to Cash: Siebel CRM - EBS PIP

      CompositeReferenceClient Policy

      SyncCustomerPartyListSiebelProvABCSImpl

      SWI_spcContact_spcService

      oracle/no_authentication_client_policy

      SyncCustomerPartyListSiebelProvABCSImpl

      SyncCustomerPartyListSiebelService

      oracle/no_authentication_client_policy

      SyncCustomerPartyListSiebelProvABCSImpl

      MergeCustomerPartyListSiebelService

      oracle/no_authentication_client_policy

      SyncAccountSiebelReqABCSImpl

      SWICustomerParty

      oracle/no_authentication_client_policy

      SyncContactSiebelReqABCSImpl

      SWIContactIO

      oracle/no_authentication_client_policy

      UpdateAssetSiebelProvABCSImpl

      SWIAssetManagementIO

      oracle/no_authentication_client_policy

      CreateAssetSiebelProvABCSImpl

      SWIAssetManagementIO

      oracle/no_authentication_client_policy

      ProcessSalesOrderSiebelReqABCSImplV2

      SBLOrderUpsertService

      oracle/no_authentication_client_policy

      ProcessSalesOrderSiebelReqABCSImplV2

      SWIOrderUpsertService

      oracle/no_authentication_client_policy

      QueryCustomerPartyListSiebelProvABCSImplV2

      SWI_spcCustomer_spcParty_spcService

      oracle/no_authentication_client_policy

      UpdateSalesOrderSiebelProvABCSImpl

      SBLOrderUpsertService

      oracle/no_authentication_client_policy

      UpdateSalesOrderSiebelProvABCSImpl

      SWIOrderUpsertService

      oracle/no_authentication_client_policy

      UpdateSalesOrderSiebelProvABCSImpl

      SWIQuoteUpsertService

      oracle/no_authentication_client_policy

      ProcessQuoteSiebelReqABCSImpl

      SWIQuoteUpsert

      oracle/no_authentication_client_policy

      SyncProductSiebelProvABCSImpl

      SWIPromotionIntegration

      oracle/no_authentication_client_policy

      SyncProductSiebelProvABCSImpl

      SWIProductIntegration

      oracle/no_authentication_client_policy

      SyncItemCompositionListSiebelProvABCSImpl

      SWIProductIntegration

      oracle/no_authentication_client_policy

      ProcessSalesOrderShippingChargeLogisticsProvABCSImpl

      IntXmlService

      oracle/no_authentication_client_policy


      Table 24-18 Wss User Name Token Client Policy Attachments for Order to Cash: Siebel CRM - EBS PIP

      CompositeReferenceClient Policy

      InterfaceCustomerToFulfillmentEBF

      CustomerPartyOrchestrationErrorResponseEBSV2

      oracle/wss_username_token_client_policy(AIABasicCredentials)

      InterfaceSalesOrderToCustomerEBFV2

      SalesOrderOrchestrationErrorResponseEBSV2

      oracle/wss_username_token_client_policy(AIABasicCredentials)

      InterfaceSalesOrderToFulfillmentEBF

      SalesOrderErrorEBSV2

      oracle/wss_username_token_client_policy(AIABasicCredentials)

      InterfaceSalesOrderToFulfillmentEBF

      SalesOrderOrchestrationErrorResponseEBSV2

      oracle/wss_username_token_client_policy(AIABasicCredentials)

      CreateSalesOrderEbizProvABCSImpl

      SalesOrderErrorResponseEBSV2

      oracle/wss_username_token_client_policy(AIABasicCredentials)

      SyncSalesOrderEbizProvABCSImpl

      SalesOrderErrorResponseEBSV2

      oracle/wss_username_token_client_policy(AIABasicCredentials)

      SyncCustomerPartyListEbizProvABCSImpl

      CustomerPartyErrorResponseEBSV2

      oracle/wss_username_token_client_policy(AIABasicCredentials)


For PIP implementation, see Oracle Application Integration Architecture Siebel CRM Integration Pack for Oracle Order Management: Order to Cash.

24.6 Undeploying the Order to Cash: Siebel CRM - EBS PIP

To undeploy the PIP from Fusion Middleware Server:

  1. 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 envi0ronment.

  2. Run the command for your platform.

    Table 24-19 Undeployment Command for the Order to Cash: Siebel CRM - EBS PIP

    PlatformUndeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems

    HP-UX

    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/OrderToCash/DeploymentPlans/OrderToCashUndeployDP.xml  
    -l <AIA_HOME>/pips/OrderToCash/DeploymentPlans/OrderToCashUndeployDP.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\OrderToCash\DeploymentPlans\OrderToCashUndeployDP.xml  
    -l <AIA_HOME>\pips\OrderToCash\DeploymentPlans\OrderToCashUndeployDP.log
    

  3. Session Pool Manager does not get undeployed when you undeploy the PIP as it belongs to common components. To undeploy Session Pool Manager, run the command specific to your platform.


    Note:

    Undeploy Session Pool Manager only if no other PIP is using it.


    Table 24-20 Undeployment Command for Session Pool Manager

    PlatformUndeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems.

    HP-UX

    ant Uninstall -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml 
    -DPropertiesFile=<AIA_HOME>/aia_instances/<AIA_Instance_name>/config/AIAInstallProperties.xml  
    -DDeploymentPlan=<AIA_HOME>/utilities/SessionPoolManager/V1/DeploymentPlans/SessionPoolManagerUndeployDP.xml
    

    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>\utilities\SessionPoolManager\V1\DeploymentPlans\SessionPoolManagerUndeployDP.xml
    

  4. Restart the SOA server.

  5. Uninstall the PIP following the instructions in Chapter 37, "Uninstalling Oracle AIA"

PKD0PKYc|BOEBPS/title.htm Oracle Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations, Release 11.1

Oracle® Application Integration Architecture

Installation and Upgrade Guide for Pre-Built Integrations

Release 11.1

E23118-04

March 2013

Documentation for administrators that describes the installation, configuration and deployment process for the integrations released in Oracle Application Integration Architecture (AIA) Pre-Built Integrations 11.1, including Communications Pre-Built Integrations, Master Data Management (MDM) Pre-Built Integrations, Agile Product Lifecycle Management (PLM) Pre-Built Integrations as well as 3.1.1 Process Integration Packs (PIP) and Direct Integrations (DI). This guide provides an overview of the installation process for the AIA media pack, the software requirements for each integration as well as detailed steps to complete the install process successfully. Each integration has a specific configuration and deployment chapter for easy reference. The upgrade and uninstall chapters are located in the final chapters of this guide.


Oracle Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations, Release 11.1

E23118-04

Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Oracle Corporation

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

PKq#PKYc|BOEBPS/finopscontoraretps.htm Configuring and Deploying the Financials Ops Control: Oracle Retail - PSFT PIP

27 Configuring and Deploying the Financials Ops Control: Oracle Retail - PSFT PIP

This chapter discusses how to configure and deploy the Oracle Financial Operations Control Integration Pack for Oracle Retail Merchandise Operations Management and PeopleSoft Enterprise Financials (Financials Ops Control: Oracle Retail - PSFT PIP).

This chapter includes the following sections:

27.1 Configuring Oracle Data Integrator

To run AIA Pre-Built Integrations Installer you must have ODI access with Supervisor privileges.

For install purposes, the ODI software must reside at the same server where Foundation Pack is installed. Once the PIP installation is complete, the ODI Software can be installed into another server (if desired) connecting to the master and work repositories provided during the PIP installation.

If you decide to have ODI software running on a different server than Foundation Pack, after installing the PIP, you should copy the <aia_home>/config/AIAConfigurationProperties.xml file into that server, then modify the JDBC URL information for the AIA Configuration Properties DS Data Server in ODI to point to the new location of the AIAConfigurationProperties.xml

AIA Configuration Properties DS is located in the Physical Architecture tab in ODI topology. The JDBC URL is located under the JDBC tab.

For example, after installing you copied the file into Z:/Oracle/PIP/. Consider the following JDBC URL:

jdbc:snps:xml?f=D:/Oracle/FPAIAHOME/config/AIAConfigurationProperties.xml&s=AIACONFIGSCHEMA

Then update the path to the location of the file in the server where ODI software is running:

jdbc:snps:xml?f=Z:/Oracle/PIP/AIAConfigurationProperties.xml&s=AIACONFIGSCHEMA

For more information, see Notes on the Recommended Topology section for additional configurations for running ODI in a different server.

The ODI batch pieces of the Retail to PSFT PIP are designed to process extremely large transaction volumes. You must adjust and tune all databases accordingly particularly the rollback capability of the Retail (source) database. For this you must size the UNDO tablespace. For information on how to size the UNDO tablespace, see the OTN article at: http://www.oracle.com/technology/oramag/oracle/05-jul/o45tuning.html

27.1.1 Creating Oracle Data Integrator Repositories

You can use an existing master repository if it exists on an Oracle database. You need not create a new master repository.

You can use an existing work repository if it exists on an Oracle database and its ID is not 900. If its ID is 900, AIA advises you to create another repository and do not use 900 as Work Repository ID

when you run the DCW, it inserts/updates the PIP artifacts into these repositories.

AIA recommends that you take a backup of master and work repositories before you start the install process.

For information about creating Oracle Data Integrator Master and Work repositories, see the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator, "Administering the Oracle Data Integrator Repositories."

27.1.2 Performing Postinstallation Configurations for ODI

Perform the following steps to apply the required patches to your ODI 11.1.1.5.0.

To install prerequisite installer patch #10288265:

  1. Access My Oracle Support [https://support.oracle.com]

  2. Navigate to the Patches & Updates tab

  3. In the Patch Name or Number field, write 10288265

  4. Select your platform

  5. Click Search

  6. Download and install patch #10288265

To install patch #12837214:

  1. Access My Oracle Support [https://support.oracle.com]

  2. Navigate to the Patches & Updates tab

  3. In the Patch Name or Number field, write 12837214

  4. Select your platform

  5. Click Search

  6. Download and install patch #12837214

After applying the patches, launch the ODI Installer:

  1. Go to Topology.

  2. Go to Physical Architecture.

  3. Find the XML technologies and expand it.

    You should see data sources for all DVM's used in your ODI flows.

  4. Select each DVM data source.

  5. Go to the JDBC tab.

  6. Append this to the end of the URL "&back_compat_specific_keywords=true"

  7. Test the data source to make sure the connection is successful.

  8. Save your changes.

For a screenshot of this screen in ODI Installer, see Appendix B, "Oracle Data Integrator Screen".

27.2 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of the Financials Ops Control: Oracle Retail - PSFT PIP. Enter the details of the Financials Ops Control: Oracle Retail - PSFT PIP screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.


Note:

Oracle Schema Names are in uppercase. Enter the schema names in uppercase in the DCW screens.


27.2.1 PIP Server Details Screen

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

Table 27-1 PIP Server Details Screen Fields

FieldDescription

Admin Host Name

Specifies 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 PIP 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.


27.2.2 PeopleSoft FSCM Web Services Details Screen

Use this screen to enter details related to your PeopleSoft FSCM Web Services instance. These details are also used by the DrillBackForward service to:

  • Construct the URL for PSFT

  • Communicate with PSFT web service deployed at this location

The screen contains the following fields:

Table 27-2 PeopleSoft FSCM Web Services Details Screen Fields

FieldDescription

Host Name

This value is the host name for the web service provided by PeopleSoft. To find this value, contact PeopleSoft system administrator. Example: rtas245.peoplesoft.com

PeopleSoft FSCM Web Services Host Name is _________________________________

Port Number

This value is the port for the web service provided by PeopleSoft. To find this value, contact the PeopleSoft system administrator. Example: 7501

PeopleSoft FSCM Web Services Port Number is _______________________________

Default Local Node

This value is the default local node for the specific instance of PeopleSoft. This value is unique to the instance of PeopleSoft and enables the PeopleSoft Gateway to identify the application server to which it should route the web service request. Example: E900B20

PeopleSoft FSCM Web Services Default Local Node is _______________________________


27.2.3 PeopleSoft FSCM Application URL Details Screen

Use this screen to enter details related to PeopleSoft FSCM Application URL. These details are used by the DrillBackForward service to construct PSFT application URL.

The screen contains the following fields:

Table 27-3 PeopleSoft FSCM Application URL Details Screen Fields

FieldDescription

Servlet

This value is the name of the PeopleSoft FSCM Application Servlet. To find this value, contact the PeopleSoft system administrator. Example: psp

PeopleSoft FSCM Application Servlet name is _____________________________________

Site

This value is the Site name of the PeopleSoft FSCM application. To find this value, contact the PeopleSoft system administrator. Example: e900b20nt

PeopleSoft FSCM Application Site name is _________________________________________

Portal,Node,Content

This value is the Portal, Node, Content for the PeopleSoft FSCM Application. To find this value, contact the PeopleSoft system administrator. Enter this information in this format: <portal>/<node>/<content>Example: EMPLOYEE/ERP/c

The Portal, Node, Content for the PeopleSoft FSCM Application is ______________________


27.2.4 PeopleSoft FSCM Database Connection Details Screen

Use this screen to enter details related to your PeopleSoft FSCM database connection instance.

The screen contains the following fields:

Table 27-4 PeopleSoft FSCM Database Connection Details Screen Fields

FieldDescription

Database Type

This value is the database type being used by the PeopleSoft Financials system. To find this value, contact the database administrator. Example: Oracle

PeopleSoft Financials system Database Type is ____________________________.

Database Host Name

This value is the PeopleSoft database host name. To find this value, contact the database administrator. Example: psftserver.mycompany.com

PeopleSoft Financials system Database Host Name is ____________________________.

Database Port Number

This value is the PeopleSoft database host name. To find this value, contact the database administrator. Example: 1588

PeopleSoft Financials system Database Port Number is ____________________________.

SID (System ID)

To find this value, contact the database administrator. Example: psftfscm

PeopleSoft Financials system SID is ____________________________.

Database Username

To find this value, contact the database administrator. Example: psft

PeopleSoft Financials system Database Username is ____________________________.

Database Password

To find this value, contact the database administrator. Example: welcome

PeopleSoft Financials system Database Password is ____________________________.

Database Schema

Usually, this value equals the Database user name. However, if the database user name uses synonymous schema to access the actual tables, provide the schema name that owns the tables.

This value is the PeopleSoft database schema. To find this value, contact the database administrator. Example: psft

PeopleSoft Financials system Database Schema is ____________________________.


27.2.5 Oracle Retail Service Layer Connection Details Screen

Use this screen to enter details related to your Oracle Retail Service Layer connection database instance. These details are also used by the DrillBackForward service to communicate with Retail service.

The screen contains the following fields:

Table 27-5 Oracle Retail Service Layer Connection Details Screen Fields

FieldDescription

Host Name

This value is the host name for the web services provided by Retail. To find this value, contact the Retail system administrator. Example: mspdev68.

Host Name is ___________________________

Port Number

This value is the port for the web services provided by Retail. To find this value, contact the Retail system administrator. Example: 7781.

Port Number is __________________________


27.2.6 Oracle Retail Integration Bus Connection Details Screen

Use this screen to enter details related to your Oracle Retail Integration Bus connection database instance.

The screen contains the following fields:

Table 27-6 Oracle Retail Integration Bus Connection Details Screen Fields

FieldDescription

Database Host Name

This value is the database host name for the Retail Integration Bus (RIB) database connection. To find this value, contact the Retail database administrator. Example: mspdev73.

Oracle Retail Integration Bus Database Host Name is ______________________________.

Database Port Number

This value is the database port number for the RIB database connection. To find this value, contact the Retail database administrator. Example: 1521

Oracle Retail Integration Bus Database Port Number is ______________________________.

Database SID

This value is the database system ID for the RIB database connection. To find this value, contact the Retail database administrator. Example: dvolr022

Oracle Retail Integration Bus Database SID is ______________________________.

Database Username

This value is the database user name for the RIB database connection. To find this value, contact the Retail database administrator. Example: ribaq

Oracle Retail Integration Bus Database Username is ______________________________.

Database Password

This value is the database password for the RIB database connection. To find this value, contact the Retail database administrator. Example: retek

Oracle Retail Integration Bus Database Host Name is ______________________________.


27.2.7 Oracle Retail Database Connection Details Screen

Use this screen to enter details related to your Oracle Retail database connection instance.

The screen contains the following fields:

Table 27-7 Oracle Retail Database Connection Details Screen Fields

FieldDescription

Database Host Name

To find this value, contact the database administrator. Example retekserver.oracle.com

Oracle Retail Database Host Name is______________________

Database Port Number

To find this value, contact the database administrator. Example: 1521

Oracle Retail Database is Port Number ____________________

Database SID

To find this value, contact the database administrator. Example retek

Oracle Retail Database SID is ________________________

Database Username

To find this value, contact the database administrator. Example: retek

Oracle Retail Database Username is ______________________

Database Password

To find this value, contact the database administrator. Example: welcome

Oracle Retail Database Password is ___________________

Database Schema

Usually, this value equals the Database user name. However, if the database user name uses synonymous schema to access the actual tables, provide the schema name that owns the tables.

To find this value, contact the database administrator. Example: retek

Oracle Retail Database Schema is ___________________


27.2.8 Oracle Data Integrator Access Details Screen

Use this screen to enter details to access Oracle Data Integrator. The screen contains the following fields:

Table 27-8 Oracle Data Integrator Access Details Screen Fields

FieldDescription

Path to Oracle Data Integrator

Provide the path to the ODI HOME up to the agent folder (included).

To find this value, contact your administrator. Example: /slot/ems3344/oracle/ODI11113/oracledi/agent (for Linux)

Oracle Data Integrator Path is _________________________________________

ODI User

To find this value, contact your administrator. Example: SUPERVISOR.

Oracle Data Integrator User is _________________________________________

ODI Password

To find this value, contact your administrator. Example: SUNOPSIS

Oracle Data Integrator Password is ______________

Path for exported DVMs

Enter the path to directory to export Domain Value Mappings (DVM). Example: $AIA_HOME/PIPS/Core/DIS/RetailToPSFTFin/DVM

One of the steps for setting up the PIP is to export some DVMs to a location. The Installer must have this location to configure ODI artifacts during the install. It is recommended to choose this location in the same server where ODI software runs.

Path for Exported DVM is _______________________


27.2.9 Oracle Data Integrator Master Repository Details Screen

You must set up an ODI Master Repository before installing the Financials Ops Control: Oracle Retail - PSFT PIP. This master repository must be created in an Oracle database. The install process appends PIP artifacts into this master repository.

Use this screen to enter details to access the Oracle Data Integrator Master Repository.

The screen contains the following fields:

Table 27-9 Oracle Data Integrator Master Repository Details Screen Fields

FieldDescription

Database Host Name

To find this value, contact your database administrator. Example: server1.oracle.com

Oracle Database Integrator Master Repository Database Host Name is _________________

Database Port Number

To find this value, contact your database administrator. Example: 1521

Oracle Database Integrator Master Repository Database Port Number is_________________

Database SID

To find this value, contact your database administrator. Example: orcl

Oracle Database Integrator Master Repository Database SID is _________________

Database Username

To find this value, contact your database administrator. Example: snpm

Oracle Database Integrator Master Repository Database Username is _________________

Database Password

To find this value, contact your database administrator. Example: snpm

Oracle Database Integrator Master Repository Database Password is _________________


27.2.10 Oracle Data Integrator Work Repository for Retail to PeopleSoft Financials PIP Details Screen

The install process imports the Retail to PeopleSoft Financials ODI artifacts into an ODI Work repository. You can provide an existing ODI Work Repository or provide an empty one. It is recommended to use an empty repository.

Use this screen to enter details related to the ODI Work Repository.

The screen contains the following fields:

Table 27-10 Oracle Data Integrator Work Repository for Retail to PeopleSoft Financials PIP Details Screen Fields

FieldDescription

ODI Work Repository Name

Enter the name you gave to the ODI Work Repository for PIP Artifacts. Example: RETAILPSFT

ODI Work Repository Name is: _________________________

ODI Work Repository ID

Enter the ID number that you used for the ODI Work Repository. It should be between 1 and 899. Example: 42

Do not use 900. Also do not use the ID used for other work repositories.

ODI Work Repository ID is: ______________


27.3 Configuring and Deploying the Financials Ops Control: Oracle Retail - PSFT PIP

This section discusses the PIP configuration and deployment process. There are two steps:

  1. Configure your PIP using the deployment DCW.

  2. Deploy the PIP to the Fusion Middleware server.

27.3.1 Configuring the Financials Ops Control: Oracle Retail - PSFT PIP

The screens that appear prompt you to enter the data that is required for successful configuration of the Financials Ops Control: Oracle Retail - PSFT PIP. Keep the completed worksheets of the Financials Ops Control: Oracle Retail - PSFT PIP screens ready before you launch the DCW.


Note:

If you are harvesting content to OER, perform the first three steps. If not, start from step 4.


To configure the Financials Ops Control: Oracle Retail - PSFT PIP:

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

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

  3. Restart the server.

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

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

  6. Click Next.

  7. Select the Financials Ops Control: Oracle Retail - PSFT PIP

  8. Click Next.

27.3.1.1 Specify PIP Server Details

To specify PIP Server details:

  1. Enter information related to your PIP server in the PIP Server Details screen.

  2. Click Next.

27.3.1.2 Specify PeopleSoft FSCM Web Services Details

To specify PeopleSoft FSCM Web Services details:

  1. Enter information about your PeopleSoft FSCM Web Services installation in the PeopleSoft FSCM Web Services Information screen.

  2. Click Next.

27.3.1.3 Specify PeopleSoft FSCM Application URL Details

To specify PeopleSoft FSCM Application URL details:

  1. Enter information about your PeopleSoft FSCM Web Application URL in the PeopleSoft FSCM Application URL screen.

  2. Click Next.

27.3.1.4 Specify PeopleSoft FSCM Database Connection Details

To specify PeopleSoft FSCM Database Connection details:

  1. Enter information about your PeopleSoft FSCM Database Connection installation in the PeopleSoft FSCM Database Connection Information screen.

  2. Click Next.

27.3.1.5 Specify Oracle Retail Service Layer Connection Details

To specify Oracle Retail Service Layer Connection details:

  1. Enter information about your Oracle Retail Service Layer Connection installation in the Oracle Retail Service Layer Connection Information screen.

  2. Click Next.

27.3.1.6 Specify Oracle Retail Integration Bus Connection Details

To specify Oracle Retail Integration Bus Connection details:

  1. Enter information about your Oracle Retail Integration Bus Connection installation in the Oracle Retail Integration Bus Connection Information screen.

  2. Click Next.

27.3.1.7 Specify Oracle Retail Database Connection Details

To specify Oracle Retail Database Connection details:

  1. Enter information about your Oracle Retail Database Connection installation in the Oracle Retail Database Connection Information screen.

  2. Click Next.

27.3.1.8 Specify Oracle Data Integrator Access Details

To specify Oracle Data Integrator Access details:

  1. Enter information about your Oracle Data Integrator Access installation in the Oracle Data Integrator Access Information screens.

    Oracle Data Integration Access Information is captured in three screens. Enter the following information in the screens.

  2. Specify ODI Home.

  3. Click Next.

  4. Enter ODI User and ODI Password.

  5. Click Next.

  6. Specify the Path for exported DVMs.

  7. Click Next.

27.3.1.9 Specify Oracle Data Integrator Master Repository Details

To specify Oracle Data Integrator Master Repository details:

  1. Enter information about your Oracle Data Integrator Master Repository installation in the Oracle Data Integrator Master Repository screen.

  2. Click Next.

27.3.1.10 Specify Oracle Data Integrator Work Repository Details

To specify Oracle Data Integrator Work Repository details:

  1. Enter information about your Oracle Data Integrator Work Repository installation in the Oracle Data Integrator Work Repository for Retails to PeopleSoft Financials screen.

  2. Click Next.

27.3.1.11 Complete Configuration

To complete configuration:

  1. 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 PIP. You can configure using the steps described in Section 27.3.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.


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

  3. When the configuration process completes without errors, the AIA DCW displays the Configuration Complete screen.

  4. Click Finish to close the DCW.

27.3.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

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

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

27.3.3 Deploying the Financials Ops Control: Oracle Retail - PSFT PIP

To deploy the PIP to Fusion Middleware server:

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

  2. 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 undeployment command too.


    Table 27-11 Deployment Commands for the Financials Ops Control: Oracle Retail - PSFT PIP

    PlatformDeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems.

    HP-UX

    ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml 
    -DDeploymentPlan=<AIA_HOME>/pips/OracleRetailToPeopleSoftFinancials/DeploymentPlans/OracleRetailToPeopleSoftFinancialsDP.xml 
    -DPropertiesFile=<AIA_HOME>/aia_instances/<AIA_Instance>/config/AIAInstallProperties.xml 
    -DDeploymentPolicyFile=<AIA_HOME>/pips/OracleRetailToPeopleSoftFinancials/DeploymentPlans/OracleRetailToPeopleSoftFinancialsConditionalPolicy.xml 
    -DSupplementaryDeploymentPlan=<AIA_HOME>/pips/OracleRetailToPeopleSoftFinancials/DeploymentPlans/OracleRetailToPeopleSoftFinancialsSupplementaryDP.xml 
    -l <AIA_HOME>/pips/OracleRetailToPeopleSoftFinancials/DeploymentPlans/OracleRetailToPeopleSoftFinancialsDP.log
    

    Microsoft Windows

    ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml 
    -DDeploymentPlan=<AIA_HOME>\pips\OracleRetailToPeopleSoftFinancials\DeploymentPlans\OracleRetailToPeopleSoftFinancialsDP.xml 
    -DPropertiesFile=<AIA_HOME>\aia_instances\<AIA_Instance>\config\AIAInstallProperties.xml 
    -DDeploymentPolicyFile=<AIA_HOME>\pips\OracleRetailToPeopleSoftFinancials\DeploymentPlans\OracleRetailToPeopleSoftFinancialsConditionalPolicy.xml 
    -DSupplementaryDeploymentPlan=<AIA_HOME>\pips\OracleRetailToPeopleSoftFinancials\DeploymentPlans\OracleRetailToPeopleSoftFinancialsSupplementaryDP.xml 
    -l <AIA_HOME>\pips\OracleRetailToPeopleSoftFinancials\DeploymentPlans\OracleRetailToPeopleSoftFinancialsDP.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 PIPs are not displayed.


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

27.4 Performing Postdeployment Configurations

This section discusses the following postdeployment configurations for the Financials Ops Control: Oracle Retail - PSFT PIP:

27.4.1 Configuring Retail to PeopleSoft Accounting Entries Integration

The Retail to PeopleSoft_AccountingEntry ODI Integration can be configured to send emails to an individual when a successful transaction occurs.

To send emails to individuals on successful transaction:

  1. Edit the AIAConfigurationProperties.xml file located in AIA_HOME/config.

  2. Set the polling interval.

    <Property name="PollingInterval">300000</Property>

    The ODI process has a polling interval, which is the time period (in milliseconds) the process waits before polling tables for new data. This polling interval can be changed as required.

  3. Modify the property name:

    Example 27-1 Property Name Modification

    <Property name="FromMailAddress">admin@company.com</Property>
    <Property name="ToMailAddress">admin@compnay.com</Property>
    <Property name="MailServerName">mail.company.com</Property> 
    
  4. Enter the email ID of the recipient in the ToMailAddress section to specify the person to receive the email messages.

  5. Enter the email ID of the sender in the FromMailAddress section.

    This value is required by the email process to send the email. Oracle AIA recommends that FromMailAddress and ToMailAddress to prevent the recipient from receiving two emails for the same successful process.

  6. Enter the name of the mail server in the MailServerName section to specify the mail server.

After you modify the AIAConfigurationProperties.xml file, update the MDS with the information.

To update SOA-MDS, apps/AIAMetaData:

  1. Browse to the folder at $AIA_HOME/aia_instances/$INSTANCE_NAME/bin.

  2. Execute source aiaenv.sh and source the file aiaenv.sh.

  3. Browse to the folder at $AIA_HOME/aia_instances/$INSTANCE_NAME/config and open UpdateMetaDataDP.xml.

  4. Update the file UpdateMetaDataDP.xml. To add resource groups to the MDS insert the include tags.

    • To upload all the files under "AIAMetaData", add <include name ="AIAMetadata/**"/>

    • To upload the files copied to AIAComponents/ApplicationObjectLibrary/SEBL/schemas folder, add <include name ="AIAComponents/ApplicationObjectLibrary/SEBL/schemas/**"/>


    Note:

    In the include tag, the folder path must be relative to the folder AIAMetaData.


  5. Browse to AIA_HOME/Infrastructure/Install/scripts.

  6. Execute ant -f UpdateMetaData.xml to update MDS.

27.4.2 Configuring Retail to PeopleSoft Invoice/Voucher Integration

The Retail to PeopleSoft Invoice ODI Integration can be configured to send emails to an individual when a successful transaction occurs.

To send emails to individuals on successful transaction:

  1. Edit the AIAConfigurationProperties.xml file located in AIA_HOME/config.

  2. Set the polling interval.

    <Property name="PollingInterval">300000</Property>

    The ODI process has a polling interval, which is the time period (in milliseconds) the process waits before polling tables for new data. This polling interval can be changed as required.

  3. Modify the property name:

    Example 27-2 Property Name Modification

    <Property name="FromMailAddress">admin@company.com</Property>
    <Property name="ToMailAddress">admin@company.com</Property>
    <Property name="MailServerName">mail.company.com</Property> 
    
  4. Enter the email ID of the recipient in the ToMailAddress section to specify the person to receive the email messages.

  5. Enter the email ID of the sender in the FromMailAddress section.

    This value is required by the email process to send the email. Oracle AIA recommends that FromMailAddress and ToMailAddress to prevent the recipient from receiving two emails for the same successful process.\

  6. Enter the name of the mail server in the MailServerName section to specify the mail server.

27.4.3 Configuring Web Services for Financials Ops Control: Oracle Retail - PSFT PIP (Optional)

In addition to the above modules, you can perform postdeployment configuration for the following services:

  • CreatePaymentTermPeopleSoftReqABCSImpl

  • CreatePaymentTermRetailProvProvABCSImpl

  • CreateSupplierPartyListPeopleSoftReqABCSImpl

  • CreateSupplierPartyRetailProvProvABCSImpl

  • DrillBackForward

  • ProcessGLAccountValidationPeopleSoftProvABCSImpl

  • ProcessGLAccountValidationRetailReqABCSImpl

  • SyncCurrencyExchangeListPeopleSoftReqABCSImpl

  • SyncCurrencyExchangeListRetailProvProvABCSImpl

  • SyncPaymentTermListPeopleSoftReqABCSImpl

  • SyncSupplierPartyListPeopleSoftReqABCSImpl

  • SyncSupplierPartyListRetailProvProvABCSImpl

  • UpdatePaymentTermPeopleSoftReqABCSImpl

  • UpdatePaymentTermRetailProvProvABCSImpl

  • UpdateSupplierPartyListPeopleSoftReqABCSImpl

  • UpdateSupplierPartyRetailProvProvABCSImpl

For more information on how to configure these services, see the Oracle Application Integration Architecture Oracle Financial Operations Control Integration Pack Implementation Guide for Oracle Retail Merchandise Operations Management and PeopleSoft Enterprise Financials.

27.4.4 Creating Sequence Rights to PeopleSoft Database User (Required)

The ODI processes create a database sequence in PeopleSoft database. Ensure that the database user for the PeopleSoft database has appropriate rights to create sequences.

27.4.5 Verifying the Database Connection (Optional)

To verify the database connection:

  1. Open ODI Topology Manager.

  2. Expand Oracle in Physical Architecture tab.

  3. Select AIA SCHEMA DS.

  4. Right click and select Edit to open AIA SCHEMA DS.

  5. Click Test.

    This opens Test Connection window.

  6. Click Test.

    If successful connection message does not appear, verify the connection information in the Definitions and JDBC tabs.

  7. Repeat steps 1 to 6 for the following data sources:

    • ORACLE RETAIL DS

    • PEOPLESOFT DS


Note:

If PeopleSoft is under IBM DB2, the data source is under IBM DB2 UDB technology.


27.4.6 Setting Up and Exporting Domain Value Mappings (Required)

You must set up and export Domain Value Maps (DVM) to complete the install process.

To set up and export DVMs:

  1. Set up all DVMs for the PIP.

  2. Export the following DVMs:

    • BUSINESS_UNIT

    • CURRENCY_CODE

    • CHARTOFACCOUNTS_GLELEMENT

  3. During installation, AIA Pre-Built Integrations Installer prompts you to specify a folder in your local file system to store the exported DVMs files. Export the following DVMs to that folder:

    • BUSINESS_UNIT

    • CURRENCY_CODE DVMs

  4. And export the CHARTOFACCOUNTS_GLELEMENT DVM to the <AIA_HOME>/services/core/BulkDataProcess/OracleRetailToPeopleSoft/Financials/CreateRetailViewSQL folder. When exporting this dvm, change the name to CHARTOFACCOUNTS_GLELEMENT.xml, instead of CHARTOFACCOUNTS_GLELEMENT.dvm.

For more information on how to set up DVMs, Oracle Application Integration Architecture Oracle Financial Operations Control Integration Pack Implementation Guide for Oracle Retail Merchandise Operations Management and PeopleSoft Enterprise Financials, "Describing Domain Value Maps", Implementing Oracle Retail to PeopleSoft Financials Process Integration Pack.

27.4.7 Setting Up ORGANIZATION_ID XREF (Required)

For information about how to set up the ORGANIZATION_ID XREF, see Oracle Application Integration Architecture Oracle Financial Operations Control Integration Pack Implementation Guide for Oracle Retail Merchandise Operations Management and PeopleSoft Enterprise Financials, "Implementing Oracle Retail Merchandising Integration Pack for PeopleSoft Enterprise Financials," Setting Up Cross-References for Oracle Retail IDs and PeopleSoft Entities.

27.5 Verifying Deployment

To verify the Financials Ops Control: Oracle Retail - PSFT PIP deployment:

  1. 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 PIP is successfully installed.

    • For Microsoft Windows: Review the install log located at <AIA_HOME>\logs\Install\PIPS\<PIPName>Install-${current.time}.log to verify that the PIP is successfully installed.

  2. Verify that you can see the following Financials Ops Control: Oracle Retail - PSFT PIP services were installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control: (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

    • ChartOfAccountsEBS

    • CreatePaymentTermPeopleSoftReqABCSImpl

    • CreatePaymentTermRetailProvABCSImpl

    • CreateSupplierPartyPeopleSoftReqABCSImpl

    • CreateSupplierPartyRetailProvABCSImpl

    • CurrencyExchangeEBS

    • CurrencyExchangePeopleSoftJMSConsumer

    • PaymentTermEBS

    • PaymentTermPeopleSoftJMSConsumer

    • ProcessGLAccountValidationPeopleSoftProvABCSImpl

    • ProcessGLAccountValidationRetailReqABCSImpl

    • SupplierPartyEBS

    • SupplierPartyPeopleSoftJMSConsumer

    • SyncCurrencyExchangeListPeopleSoftReqABCSImpl

    • SyncCurrencyExchangeListRetailProvJMSProducer

    • SyncPaymentTermListPeopleSoftReqABCSImpl

    • SyncPaymentTermListRetailProvABCSImpl

    • SyncSupplierPartyListPeopleSoftReqABCSImpl

    • SyncSupplierPartyListRetailProvABCSImpl

    • UpdatePaymentTermPeopleSoftReqABCSImpl

    • UpdatePaymentTermRetailProvABCSImpl

    • UpdateSupplierPartyPeopleSoftReqABCSImpl

    • UpdateSupplierPartyRetailProvABCSImpl

  3. Confirm that the Financials Ops Control: Oracle Retail - PSFT PIP queues (JMS) are installed.

    1. To verify the JMS Queues, connect to the WLS Console http:<host>:<port>/console.

    2. Navigate to Services, Messaging, JMS Modules, AIAJMSModule.

    3. Drill down and verify that the following queues exist:

      AIA_PeopleSoftCurrencyExchangeJMSQueue.

      AIA_PeopleSoftPaymentTermsJMSQueue.

      AIA_PeopleSoftSupplierPartyJMSQueue.

  4. Confirm that the DrillBackForward web service is installed:

    1. Navigate to the Application Server Console: http://<server name>:<port number>/em.

    2. Select the Application Server Control option.

    3. Log in with the server administrator user name. To find this information, contact the system administrator.

    4. Navigate to Farm_SOA_Domain, Application Deployments.

    5. Verify that in the Web Services tab, the GetDrillBackForwardURL web service is available with port name DrillBackForwardURLService.

  5. Confirm that necessary configuration properties exist.

    1. Navigate to the AIA home location. For example, http://<host_name>:<port>/AIA/faces/home.jspx

    2. Navigate to Setup, Configuration and check for the following configuration properties:

      CreatePaymentTermPeopleSoftReqABCSImpl

      CreatePaymentTermRetailProvABCSImpl

      CreateSupplierPartyPeopleSoftReqABCSImpl

      CreateSupplierPartyRetailProvABCSImpl

      ProcessGLAccountValidationPeopleSoftProvABCSImpl

      ProcessGLAccountValidationRetailReqABCSImpl

      SyncCurrencyExchangeListPeopleSoftReqABCSImpl

      SyncCurrencyExchangeListRetailProvABCSImpl

      SyncPaymentTermListPeopleSoftReqABCSImpl

      SyncPaymentTermListRetailProvABCSImpl

      SyncSupplierPartyListPeopleSoftReqABCSImpl

      SyncSupplierPartyListRetailProvABCSImpl

      UpdatePaymentTermPeopleSoftReqABCSImpl

      UpdatePaymentTermRetailProvABCSImpl

      UpdateSupplierPartyPeopleSoftReqABCSImpl

      UpdateSupplierPartyRetailProvABCSImpl

  6. Verify Integration Scenarios.

    1. Navigate to the AIA home location. For example, http://<host_name>:<port>/AIA/faces/home.jspx

    2. Find Project Lifecycle Workbench and click Go.

    3. On the AIA Project Lifecycle Workbench page, click Search.

    4. Click the link in the Bill Of Material column to view the following artifacts included in this PIP.

    • Create PaymentTerm PeopleSoft Requestor

    • Create PaymentTerm Retail Provider

    • Create SupplierParty PeopleSoft Requestor

    • Create SupplierParty Retail Provider

    • Process GL Account Validation PeopleSoft Provider

    • Process GL Account Validation Retail Requestor

    • ProcessGLAccountValidationRetailReqABCSImpl

    • Sync CurrencyExchangeList PeopleSoft Requestor

    • Sync CurrencyExchangeList Retail Provider

    • Sync PaymentTerm PeopleSoft Requestor

    • Sync PaymentTerm Retail Provider

    • Sync SupplierParty PeopleSoft Requestor

    • Sync SupplierParty Retail Provider

    • Update PaymentTerm PeopleSoft Requestor

    • Update PaymentTerm Retail Provider

    • Update SupplierParty PeopleSoft Requestor

    • Update SupplierParty Retail Provider

  7. Verify that 32 ABCSs have been published.

    1. Navigate to the AIA home location. For example, http://<host_name>:<port>/AIA/faces/home.jspx

    2. Navigate to Service Repository, type %ABCS% in the Service Name field and click Search.

    • CreatePaymentTermPeopleSoftReqABCSImpl

    • CreatePaymentTermPeopleSoftReqABCSImplExt

    • CreatePaymentTermRetailProvABCSImpl

    • CreatePaymentTermRetailProvABCSImplExt

    • CreateSupplierPartyPeopleSoftReqABCSImpl

    • CreateSupplierPartyPeopleSoftReqABCSImplExt

    • CreateSupplierPartyRetailProvABCSImpl

    • CreateSupplierPartyRetailProvABCSImplExt

    • ProcessGLAccountValidationPeopleSoftProvABCSImpl

    • ProcessGLAccountValidationPeopleSoftProvABCSImplExt

    • ProcessGLAccountValidationRetailReqABCSImpl

    • ProcessGLAccountValidationRetailReqABCSImplExt

    • SyncCurrencyExchangeListPeopleSoftReqABCSImpl

    • SyncCurrencyExchangeListPeopleSoftReqABCSImplExt

    • SyncCurrencyExchangeListRetailProvABCSImpl

    • SyncCurrencyExchangeListRetailProvABCSImplExt

    • SyncPaymentTermListPeopleSoftReqABCSImpl

    • SyncPaymentTermListPeopleSoftReqABCSImplExt

    • SyncPaymentTermListRetailProvABCSImpl

    • SyncPaymentTermListRetailProvABCSImplExt

    • SyncSupplierPartyListPeopleSoftReqABCSImpl

    • SyncSupplierPartyListPeopleSoftReqABCSImplExt

    • SyncSupplierPartyListRetailProvABCSImpl

    • SyncSupplierPartyListRetailProvABCSImplExt

    • UpdatePaymentTermPeopleSoftReqABCSImpl

    • UpdatePaymentTermPeopleSoftReqABCSImplExt

    • UpdatePaymentTermRetailProvABCSImpl

    • UpdatePaymentTermRetailProvABCSImplExt

    • UpdateSupplierPartyPeopleSoftReqABCSImpl

    • UpdateSupplierPartyPeopleSoftReqABCSImplExt

    • UpdateSupplierPartyRetailProvABCSImpl

    • UpdateSupplierPartyRetailProvABCSImplExt

27.5.1 Validating Security Policies

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 PIP have locally attached security policies.

To validate locally attached security policies:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

  2. Navigate to WebLogic Domain, soa_domain, Web Services, Policies.

  3. Verify Service Policy attachment.

    1. Find the service policy in the list of policies.

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Service.

    4. Validate that all the composites are listed with local attachment to this service policy.

  4. Verify Client Policy attachment

    1. Navigate back to Policies screen and find the client policy

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Reference.

    4. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.

      Table 27-12 Service Policy Attachments for Financials Ops Control: Oracle Retail - PSFT PIP

      CompositeService Policy

      ProcessGLAccountValidationRetailReqABCSImpl

      oracle/no_authentication_service_policy


      Table 27-13 No Authentication Client Policy Attachments for Financials Ops Control: Oracle Retail - PSFT PIP

      CompositeReferenceClient Policy

      ProcessGLAccountValidationPeopleSoftProvABCSImpl

      GL_CHARTFIELD

      oracle/no_authentication_client_policy

      CreatePaymentTermRetailProvABCSImpl

      PayTermService

      oracle/no_authentication_client_policy

      UpdatePaymentTermRetailProvABCSImpl

      PayTermService

      oracle/no_authentication_client_policy

      SyncPaymentTermListRetailProvABCSImpl

      PayTermService

      oracle/no_authentication_client_policy

      CreateSupplierPartyRetailProvABCSImpl

      SupplierService

      oracle/no_authentication_client_policy

      UpdateSupplierPartyRetailProvABCSImpl

      SupplierService

      oracle/no_authentication_client_policy

      SyncSupplierPartyListRetailProvABCSImpl

      SupplierService

      oracle/no_authentication_client_policy


For more information about security validation, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Working with Security."

27.5.2 ODI Topology

  1. Verify the following connections are accurate in the Physical Architecture tab.

    1. Launch ODI Topology Manager and navigate to Physical Architecture tab.

    2. Expand XML node and double click AIA Configuration PropertiesDS.

    3. Click JDBC tab and check for the connection <AIAHome>/aia_instances/<AIAInstance Name>/AIAMetaData/config/AIAConfigurationProperties.xml

    4. Similarly find the following data servers based on the technology and artifact name. The first row in the table is used as an example.

      Table 27-14 Data Servers

      Artifact importedConnectionTechnology

      CONN_AIAConfigurationPropertiesDS.xml

      <AIAHome>/aia_instances/<AIAInstance Name>/AIAMetaData/config/AIAConfigurationProperties.xml

      XML

      CONN_AIASCHEMADS.xml

      AIA database connection

      Oracle

      CONN_BusinessUnitGLDS.xml

      Path to exported DVM BUSINESS_UNIT.xml

      XML

      CONN_CurrencyCodeDS.xml

      Path to exported DVM CURRENCY_CODE.xml

      XML

      CONN_ExchangeRateTypeDS.xml

      Path to exported DVM CURRENCYEXCHANGE_CONVERSIONTYPECODE.xml

      XML

      CONN_ORACLERETAILDS.xml

      Oracle Retail database connection

      Oracle

      CONN_PEOPLESOFTDS.xml **

      PeopleSoft database connection

      Oracle

      CONN_PSFT_DB2_DS **

      PeopleSoft database connection

      IBM DB2 UDB



      Note:

      If your data server connects to an Oracle database, the Schema and User name must be capitalized.


  2. Verify the context in the Contexts tab.

    If PeopleSoft system is under an Oracle database, the name of the artifact imported is RETL_TO_PSFT.xml. If the PeopleSoft system is under an IBM DB2 database, then the context imported is CONT_RETL_TO_PSFT_DB2.xml.

    1. Launch ODI Topology Manager and navigate to Contexts tab.

    2. Double click RETL_TO_PSFT and navigate to Schema tab.

      Table 27-15 describes the imported artifacts:

      Table 27-15 Imported Artifacts

      Artifact importedDescription

      CONT_RETL_TO_PSFT.xml Or

      CONT_RETL_TO_PSFT_DB2.xml

      Holds the correlation between logical schemas and physical ones.

      Verify the following schemas associations are set up. You may see more schemas than the ones here. The PIP processes ignore these additional schemas.

      AIAConfigSchema

      BusinessUnitGL

      Currency

      ESB_XREF

      Exchange Rate

      PSFT_DB2_LogicalSchema

      PeopleSoft

      Retail



      Note:

      If PeopleSoft system is connected to an Oracle database, associate the Logical schema PeopleSoft with Physical schema. If it is under IBM DB2, then associate PSFT_DB2_Logial Schema to a Physical schema.


  3. Verify the following Logical Data Servers are imported in the Logical Architecture tab.

    1. Launch ODI Topology Manager and navigate to Logical Architecture tab.

    2. Expand XML node and double click AIA Config Schema.

    3. Click Definition tab check whether the RETL_TO_PSFT context has AIA Configuration properties DS physical schema associated.

    4. Similarly find the following logical data servers based on the technology and artifact name. The first row in Table 27-16 is used as an example.

      Table 27-16 Logical Data Servers

      Artifact importedDescriptionTechnology

      LSC_AIAConfigSchema.xml

      <AIA_HOME>/config/ AIAConfigurationProperties.xml

      XML

      LSC_BusinessUnitGL.xml

      Exported DVM BUSINESS_UNIT.xml

      XML

      LSC_Currency.xml

      Exported DVM CURRENCY_CODE.xml

      XML

      LSC_ESB_XREF.xml

      AIA database connection

      Oracle

      LSC_ExchangeRate.xml

      Exported DVM CURRENCYEXCHANGE_CONVERSIONTYPECODE.xml

      XML

      LSC_Retail.xml

      Oracle Retail database

      Oracle

      LSC_Peoplesoft.xml

      PeopleSoft database for Oracle database

      Oracle

      LSC_PSFT_DB2_LogicalSchema.xml

      PeopleSoft database for IBM DB2 database

      IBM DB2 UDB


27.5.3 ODI Designer

  1. Launch ODI Designer and verify the following models are imported in the Models tab.

    • Oracle Retail To PeopleSoft

    • RMS To PeopleSoft Accounting Entry

    • ReIM To PSFT Invoice

    • ReIM To PeopleSoft Accounting Entry

  2. Launch ODI Designer and verify the following projects are imported in the Projects tab.

    • RMS To PSFT Acct Entry Project

    • ReIM To PSFT Acct Entry Project

    • ReIM To PeopleSoft Invoice Project

  3. Verify the path to the AIAConfigurationProperties.xml is correctly set up for RMS to PSFT AcctEntry project.

    1. Expand RMS to PSFT AcctEntry and Procedures.

    2. Double-click the Load AIA Configuration Properties XML procedure.

    3. Double-click the command LoadAIAConfigXML in the Details tab.

    4. Under Definition tab, click Command on Source sub tab.

    5. Verify the path to AIAConfigurationProperties.xml is accurate.

  4. Using the same procedure verify the path for the following Exported DVMs:

    • Load Business Unit GL DVM XML

    • Load Currency Code DVM XML

    1. Verify the path to the AIAConfigurationProperties.xml is correctly set up for ReIM To PSFT Acct Entry project.

    2. Verify the path to the Exported DVMs:

      Load Business Unit GL DVM XML

      Load Currency Code DVM XML

    3. Verify the path to the AIAConfigurationProperties.xml is correctly set up for ReIM To PeopleSoft Invoice project

    4. Verify the path to the Exported DVMs:

      Load Business Unit GL DVM XML

      Load Currency Code DVM XML

  5. Verify the WSDL URL for ErrorNotification step name is accurate for AIAAsyncErrorHandlingBPELProcess in the Load RMS To PSFT Acct Entry Package:

    1. Launch ODI Designer.

    2. Go to Projects tab.

    3. Double click Load RMS To PSFT Acct Entry Package.

    4. Select the Diagram tab.

    5. Click the Error Notification icon.

    6. In the Properties frame under General tab verify the WSDL URL user and password are accurate

    7. Verify the WSDL URL for ErrorNotification step name is accurate for AIAAsyncErrorHandlingBPELProcess in the Load ReIM to PSFT AcctEntry PKG

    8. Verify the WSDL URL for OdiInvokeWebService 5-step name is accurate for AIAAsyncErrorHandlingBPELProcess in the Load RETL Invoices To PSFT Pkg.

27.5.4 Error Messages During Financials Ops Control: Oracle Retail - PSFT PIP Deployment

When deploying the Financials Ops Control: Oracle Retail - PSFT PIP, you might encounter the following errors:

  • Failed to execute: Create user xxxxx identified by yyyyy

  • Unique Constraint Violation

27.5.4.1 Failed to execute: Create user xxxxx identified by yyyyy

AIA Pre-Built Integrations Installer displays this error message in the log file if the install script attempts to create a database user name for an existing database user name. You can ignore this message and continue with the install process.

The AIA Pre-Built Integrations Installer displays the following message when it finds an identical database user name:

Example 27-3 Identical Database User Name Message

ODIInstall_CreateDBSchemaWorkRep:
[echo] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[echo] Creating ODI Work Repository DB User: xxxxx
[sql] Executing commands
[sql] Failed to execute: create user xxxxx identified by yyyyy
[sql] java.sql.SQLException: ORA-01920: user name 'xxxxx' conflicts with another user or role name
[sql] 1 of 2 SQL statements executed successfully
[echo] Done creating DB User for ODI Work Repository: xxxxx
[echo] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Note:

xxxxx refers to the database user name provided for ODI Work Repository and yyyyy is the password.


27.5.4.2 Unique Constraint Violation

AIA Pre-Built Integrations Installer displays this error message in the log file if the ODI data source xxxxx exists in the ODI master repository. The ODI data source is defined in Topology in the Physical Architecture tab. This error occurs when the Financials Ops Control: Oracle Retail - PSFT PIP is reinstalled.

The AIA Pre-Built Integrations Installer displays the following message when it finds an identical ODI data source:

Example 27-4 Identical ODI Data Source Message

[echo] - Importing CONN_xxxxx.xml
[exec] OracleDI: Starting Command : OdiImportObject -FILE_NAME=<AIA_HOME>/PIPS/Core/DIS/RetailToPSFTFin/ODI Master Repository/CONN_xxxxx.xml -IMPORT_MODE=SYNONYM_INSERT_UPDATE ...
[exec] java.sql.SQLException: ORA-00001: unique constraint (SNPM.PK_MTXT) violated

This error does not stop the install process. The process imports the remaining ODI PIP artifacts into the ODI; however, it is important to verify the accuracy of the connections for these ODI data sources. To resolve this issue, verify that the connections and associated logical schemas in the ODI topology are accurate.

For PIP implementation, see Oracle Application Integration Architecture Oracle Financial Operations Control Integration Pack Implementation Guide for Oracle Retail Merchandise Operations Management and PeopleSoft Enterprise Financials.

27.6 Undeploying the Financials Ops Control: Oracle Retail - PeopleSoft PIP

To undeploy the PIP from Fusion Middleware Server:

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

  2. Run the command for your platform.

    Table 27-17 Undeployment Command for the Financials Ops Control: Oracle Retail - PeopleSoft PIP

    PlatformUndeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems.

    HP-UX

    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/OracleRetailToPeopleSoftFinancials/DeploymentPlans/OracleRetailToPeopleSoftFinancialsUndeployDP.xml 
    -l <AIA_HOME>/pips/OracleRetailToPeopleSoftFinancials/DeploymentPlans/OracleRetailToPeopleSoftFinancialsUndeployDP.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\OracleRetailToPeopleSoftFinancials\DeploymentPlans\OracleRetailToPeopleSoftFinancialsUndeployDP.xml 
    -l <AIA_HOME>\pips\OracleRetailToPeopleSoftFinancials\DeploymentPlans\OracleRetailToPeopleSoftFinancialsUndeployDP.log
    

  3. Restart the SOA server.

  4. Uninstall the PIP following the instructions in Chapter 37, "Uninstalling Oracle AIA".

PK^eQPKYc|BOEBPS/partpage_v.htm Appendix

Part V

Appendix

This part includes screenshots for the AIA Pre-Built Integrations Installer and Oracle Data Integrator.

This part includes the following appendixes:

PK@PKYc|BOEBPS/partpage_ii.htm+ Configuring and Deploying AIA RV 3.1.1 PIPs and DIs

Part II

Configuring and Deploying AIA RV 3.1.1 PIPs and DIs

This part provides a general introduction to the Oracle AIA RV 3.1.1 PIPs and DIs. It also provides the steps involved in the configuration and deployment of the PIPs and DIs.

This part contains the following chapters:

PKʼnJ 0 + PKYc|B OEBPS/loe.htmA List of Examples

List of Examples

PKvF A PKYc|BOEBPS/lspdrivermgmt.htm Configuring and Deploying the LSP Driver Mgmt: OTM - EBS PIP

30 Configuring and Deploying the LSP Driver Mgmt: OTM - EBS PIP

This chapter discusses how to configure and deploy the Oracle Driver Management Integration Pack for Oracle Transportation Management and Oracle E-Business Suite (LSP Driver Mgmt: OTM - EBS PIP).

This chapter includes the following sections:

30.1 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of the LSP Driver Mgmt: OTM - EBS PIP. Enter the details of the LSP Driver Mgmt: OTM - EBS PIP screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.

30.1.1 PIP Server Details Screen

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

Table 30-1 PIP Server Details Screen Fields

FieldDescription

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


30.1.2 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 30-2 Oracle E-Business Suite Server Details Screen Fields

FieldDescription

E-Business Suite Host Name

Specifies the fully qualified system name of the Oracle E-Business Suite application. Example: example1.corp.example.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: server2.xyz.com. To find this value, contact your administrator.

Workflow Business Event System Name is __________________

E-Business suite version

This is the version of the E-Business Suite Application. Valid value is 12.1.2. Other versions are not supported in the 11.1 release.


30.1.3 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 30-3 Oracle E-Business Suite Database Details Screen Fields

FieldDescription

E-Business Suite Database Host

Specifies the system name. To find this value, contact the database administrator. Example: server1.example.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: server1.

Database Schema is __________________________________

Note: All the database credentials are used for creating the connection pool URL and data source URLs.


30.1.4 Oracle OTM Server Details Screen

Use this screen to enter details related to your OTM server instance.

The screen contains the following fields:

Table 30-4 Oracle OTM Server Details Screen Fields

FieldDescription

OTM Host name

Specifies the system name of the OTM application. For example: example1.corp.example.com. To find the value, contact your administrator.

OTM Host name is _________________________________

OTM Http Port

This value is the OTM Web Service port. For example: 8024. To find the value, contact your administrator.

OTM Port is _________________________________

OTM User Name

This is the user name for OTM application. To find the value, contact your administrator.

OTM Username is _________________________________

OTM Password

This is the password for OTM application. For example: welcome. To find the value, contact your administrator.

OTM Password is ________________________________

OTM System Name

This is the system name for the OTM application. To find the value, contact your administrator. For example: http://<server name.example.com>:<port_no>

OTM System Name is __________________

OTM System Version

This is the version of the OTM Application like 5.5,6.0.

OTM System Version is ________________


30.1.5 Oracle OTM Database Details Screen

Use this screen to enter details related to your OTM database instance.

The screen contains the following fields:

Table 30-5 Oracle OTM Database Details Screen Fields

FieldDescription

OTM Database Host

Specifies the system name. For example: example1.corp.example.com. To find the value, contact your database administrator.

OTM Database Host is ______________________________

OTM Database Port

This is the Database port for OTM application. For example: 8024. To find the value, contact your database administrator.

OTM Database Port is ______________________________

OTM Database Username

This is the Database user name for OTM application. For example: apps. To find the value, contact your database administrator.

OTM Database Username is _______________________

OTM Database Password

This is the password for Database Password user. For example: apps. To find the value, contact your database administrator.

OTM Database Password is _________________________

OTM Database System ID (SID)

This is the Database SID for OTM application. For example: orcl. To find the value, contact your database administrator.

OTM Database SID is _________________________________


30.2 Configuring and Deploying the LSP Driver Mgmt: OTM - EBS PIP

This section discusses the PIP configuration and deployment process. There are two steps:

  1. Configure your PIP using the deployment DCW.

  2. Deploy the PIP to the Fusion Middleware server.

30.2.1 Configuring the LSP Driver Mgmt: OTM - EBS PIP

The screens that appear prompt you to enter the data that is required for successful configuration of the LSP Driver Mgmt: OTM - EBS PIP. Keep the completed worksheets of the LSP Driver Mgmt: OTM - EBS PIP 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 LSP Driver Mgmt: OTM - EBS PIP:

  1. Navigate to <MiddleWare_HOME>/user_projects/domains/<soa_domain_name>/bin/ and open setDomainEnv.sh for Linux based systems and setDomainEnv.bat for Microsoft Windows.

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

  3. Restart the server.

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

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

  6. Click Next.

  7. Select the LSP Driver Mgmt: OTM - EBS PIP

  8. Click Next.

30.2.1.1 Specify PIP Server Details

To specify PIP Server details:

  1. Enter information related to your PIP server in the PIP Server Details screen.

  2. Click Next.

30.2.1.2 Specify Oracle E-Business Suite Server Details

To specify Oracle E-Business Suite Server details:

  1. Enter information about your E-Business Suite Server in the E-Business Suite Server Details screen.

  2. Click Next.

30.2.1.3 Specify Oracle E-Business Suite Database Details

To specify Oracle E-Business Suite Database details:

  1. Enter information about your E-Business Suite Database in the E-Business Suite Database Details screen.

  2. Click Next.

30.2.1.4 Specify Oracle OTM Server Details

To specify Oracle OTM Server details:

  1. Enter server information about Oracle OTM in the Oracle OTM Server Details screen.

  2. Click Next.

30.2.1.5 Specify Oracle OTM Database Details

To specify Oracle OTM Database details:

  1. Enter information about your Oracle OTM Database in the Oracle OTM Database Details screen.

  2. Click Next.

30.2.1.6 Complete Configuration

To complete configuration:

  1. 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 PIP. You can configure using the steps described in Section 30.2.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.


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

  3. When the configuration process completes without errors, the AIA DCW displays the Configuration Complete screen.

  4. Click Finish to close the DCW.

30.2.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

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

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

30.2.3 Deploying the LSP Driver Mgmt: OTM - EBS PIP

To deploy the PIP to Fusion Middleware server:

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

  2. 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 undeployment command too.


    Table 30-6 Deployment Commands for the LSP Driver Mgmt: OTM - EBS PIP

    PlatformDeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems.

    HP-UX

    ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml 
    -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml 
    -DDeploymentPlan=<AIA_HOME>/pips/FleetDriverManagement/DeploymentPlans/FleetDriverManagementDP.xml 
    -DSupplementaryDeploymentPlan=<AIA_HOME>/pips/FleetDriverManagement/DeploymentPlans/FleetDriverManagementSupplementaryDP.xml 
    -DDeploymentPolicyFile=<AIA_HOME>/pips/FleetDriverManagement/DeploymentPlans/FleetDriverManagementConditionalPolicy.xml 
    -l <AIA_HOME>/pips/FleetDriverManagement/DeploymentPlans/FleetDriverManagement.log
    

    Microsoft Windows

    ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml 
    -DPropertiesFile=<AIA_HOME>\aia_instances\<aia_instance>\config\AIAInstallProperties.xml 
    -DDeploymentPlan=<AIA_HOME>\pips\FleetDriverManagement\DeploymentPlans\FleetDriverManagementDP.xml
    -DSupplementaryDeploymentPlan=<AIA_HOME>\pips\FleetDriverManagement\DeploymentPlans\FleetDriverManagementSupplementaryDP.xml 
    -DDeploymentPolicyFile=<AIA_HOME>\pips\FleetDriverManagement\DeploymentPlans\FleetDriverManagementConditionalPolicy.xml 
    -l <AIA_HOME>\pips\FleetDriverManagement\DeploymentPlans\FleetDriverManagement.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 PIPs are not displayed.


  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 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 PIP development teams, most often, also requirSce 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".

30.3 Performing Postdeployment Configurations

This section discusses post deployment configurations for LSP Driver Mgmt: OTM - EBS PIP. The section includes:

30.3.1 Configuring Time Zone Property

To configure time zone property:

  1. Open <AIA_INSTANCE>/AIAMetaData/config/AIAConfigurationProperties.xml

  2. Navigate to property EBIZ_01.SERVER_TIMEZONE under the module 'Ebiz'

  3. Set it to appropriate value, for example PST or IST.

    Possible values:

    • PST, IST and so on. (OR)

    • -07:00, +05:30 and so on.

  4. Update MetaData.

  5. Reload from the AIA page (http://< server name >: < port number >/AIA).

30.3.2 Migrating from AIA 2.x to AIA 11.1

If you are migrating from an earlier version to 11.1, then ensure the following:

The last number value for the sequence DR_CAL_EVENT_ID created in "<AIA_INSTANCE>_AIA" database user in the 11.1 version should be set to the same value as in the 10g version. In 10g, this sequence is available in the "aia" database user. This can be done using the following commands:

  1. Execute select dr_cal_event_id.nextval from Dual in the 10g database.

  2. Execute alter sequence dr_cal_event_id increment by <nextval from 10g> in the 11g database

30.3.3 Creating New Csf-Key and Configuring Flows to Use Csf-Key

You can edit existing csf-key or create new csf-key and configure flows to use the modified/new csf-key.

To edit existing csf-key or create new csf-key:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control (http://<server_host>:<server_port>/em).

  2. Right click WebLogic Domain and navigate to <your_domain>, Security, and select Credentials.

  3. Expand oracle.wsm.security and click OTM_DOMAIN.

  4. Edit existing csf-key credentials or create new csf-key with new credentials.

To configure flows to use new csf-key:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control (http://<server_host>:<server_port>/em).

  2. Click the process name which is invoking OTM Webservice based on the flow.

  3. Click the corresponding Reference under Services and References section. (use the security exceptions table in the Section 30.4.1, "Validating Security Policies" section to find the References)

  4. Click the Policies and select oracle/wss_http_token_client_policy.

  5. Update the csf-key value under Security Configuration Details tab and save the changes.

30.4 Verifying Deployment

To verify the LSP Driver Mgmt: OTM - EBS PIP deployment:

  1. 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 PIP is successfully installed.

    • For Microsoft Windows: Review the install log located at <AIA_HOME>\aia_instances\<instance name>\logs to verify that the PIP is successfully installed.

  2. Confirm that JMS Queues are created:

    1. Log in to the WLS Console: http:// name>:<port number>/console/

    2. Log in with the server admin user name. For access details, contact the system administrator

    3. Navigate to Services, Messaging, JMS Modules, AIAJMSModule and verify that the following queue names exist.

    • AIA_EbizTrainingCalendarJMSQueue

    • AIA_EbizAbsenceCalendarJMSQueue

    • AIA_EbizWorkerJMSQueue

    • AIA_EbizLocationJMSQueue

  3. Confirm that the LSP Driver Mgmt: OTM - EBS PIP services were installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

    • CalculateDriverIncentiveCompensationListEbizAdapter

    • CalculateDriverIncentiveCompensationListEbizProvABCSImpl

    • CalculateDriverIncentiveCompensationListLogisticsAQConsumer

    • CalculateDriverIncentiveCompensationListLogisticsReqABCSImpl

    • CreateAbsenceAttendanceEbizAdapter

    • CreateDelegateBookingEbizAdapter

    • CreateLocationListEbizAdapter

    • DeleteAbsenceAttendanceEbizAdapter

    • DeleteDelegateBookingEbizAdapter

    • LocationEBS

    • LocationResponseEBS

    • PayableInvoiceEBS

    • PayableInvoiceResponseEBS

    • ResourceCalendarEntryEBS

    • ResourceCalendarEntryResponseEBS

    • SyncAbsenceCalendarListEbizJMSConsumer

    • SyncAbsenceCalendarListEbizJMSProducer

    • SyncAbsenceCalendarListEbizReqABCSImpl

    • SyncAbsenceCalendarListInitialLoadDBAdapter

    • SyncAbsenceCalendarListProcess

    • SyncLocationListEbizGetABM

    • SyncLocationListEbizJMSConsumer

    • SyncLocationListEbizJMSProducer

    • SyncLocationListEbizReqABCSImpl

    • SyncLocationListInitialLoadDBAdapter

    • SyncLocationListLogisticsProvABCSImpl

    • SyncResourceCalendarEntryListLogisticsProvABCSImpl

    • SyncTrainingCalendarListEbizJMSConsumer

    • SyncTrainingCalendarListEbizJMSProducer

    • SyncTrainingCalendarListEbizReqABCSImpl

    • SyncTrainingCalendarListInitialLoadDBAdapter

    • SyncTrainingCalendarListProcess

    • SyncWorkerListBPELAggregator

    • SyncWorkerListEbizAggrEventConsumer

    • SyncWorkerListEbizEventAggregator

    • SyncWorkerListEbizGroupEventAdapter

    • SyncWorkerListEbizInitialLoad

    • SyncWorkerListEbizJMSConsumer

    • SyncWorkerListEbizJMSProducer

    • SyncWorkerListEbizReqABCSImpl

    • SyncWorkerListLogisticsProvABCSImpl

    • UpdateAbsenceAttendanceEbizAdapter

    • UpdateClassScheduleEbizAdapter

    • UpdateDelegateBookingEbizAdapter

    • UpdateLocationEbizAdapter

    • UpdateLocationListEbizAdapter

    • UpdateTrainingCenterandLocationEbizAdapter

    • WorkerEBS

    • WorkerResponseEBS

  4. LSP Financial Mgmt: OTM - EBS PIP and LSP Driver Mgmt: OTM - EBS PIP use same PayableInvoiceEBS and PayableInvoiceResponseEBS.

    When you install Fleet PIPs, if LSP Driver Mgmt: OTM - EBS PIP is installed after LSP Financial Mgmt: OTM - EBS PIP, routing rules pertaining to WorkInvoice flow of LSP Driver Mgmt: OTM - EBS PIP do not appear in Oracle Enterprise Manager Fusion Middleware Control for PayableInvoiceEBS and PayableInvoiceResponseEBS. In this case, routing rules pertaining to CalculateDriverIncentiveCompensationListEbizProvABCSImpl of WorkInvoice flow of LSP Driver Mgmt: OTM - EBS PIP have to be added manually to PayableInvoiceEBS and routing rules pertaining to CalculateDriverIncentiveCompensationListLogisticsReqABCSImpl of WorkInvoice flow of LSP Driver Mgmt: OTM - EBS PIP have to be added manually to PayableInvoiceResponseEBS and deployed on server.

    For more information on manual deployment of routing rules, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Creating Routing Rules".

30.4.1 Validating Security Policies

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 PIP have locally attached security policies.

To validate locally attached security policies:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

  2. Navigate to WebLogic Domain, soa_domain, Web Services, Policies.

  3. Verify Service Policy attachment.

    1. Find the service policy in the list of policies.

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Service.

    4. Validate that all the composites are listed with local attachment to this service policy.

  4. Verify Client Policy attachment

    1. Navigate back to Policies screen and find the client policy

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Reference.

    4. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.


      Note:

      The default csf-key for all the flows is OTM_DOMAIN. This is created in server automatically as a part of PIP installation.


      Table 30-7 Service Policy Attachments for LSP Driver Mgmt: OTM - EBS PIP

      CompositeServiceService Policy

      SyncLocationListLogisticsProvABCSImpl

      TransmissionReport

      oracle/wss_http_token_service_policy

      SyncResourceCalendarEntryListLogisticsProvABCSImpl

      TransmissionReport

      oracle/wss_http_token_service_policy

      SyncWorkerListLogisticsProvABCSImpl

      TransmissionReport

      oracle/wss_http_token_service_policy


      Table 30-8 Wss Http Token Client Policy Attachments for LSP Driver Mgmt: OTM - EBS PIP

      CompositeReferenceClient Policy

      CalculateDriverIncentiveCompensationListLogisticsReqABCSImpl

      LogisticsWebService

      oracle/wss_http_token_client_policy

      SyncLocationListLogisticsProvABCSImpl

      LogisticsWebService

      oracle/wss_http_token_client_policy

      SyncResourceCalendarEntryListLogisticsProvABCSImpl

      LogisticsWebService

      oracle/wss_http_token_client_policy

      SyncWorkerListLogisticsProvABCSImpl

      LogisticsWebService

      oracle/wss_http_token_client_policy


For more information about security validation, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Working with Security."

For PIP implementation, see Oracle Application Integration Architecture Oracle Driver Management Integration Pack for Oracle Transportation Management and Oracle E-Business Suite Implementation Guide.

30.5 Undeploying the LSP Driver Mgmt: OTM - EBS PIP

To undeploy the PIP from Fusion Middleware Server:

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

  2. Run the command for your platform.

    Table 30-9 Undeployment Command for the LSP Driver Mgmt: OTM - EBS PIP

    PlatformUndeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems.

    HP-UX

    ant Uninstall -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml 
    -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml 
    -DDeploymentPlan=<AIA_HOME>/pips/FleetDriverManagement/DeploymentPlans/FleetDriverManagementUndeployDP.xml 
    -l <AIA_HOME>/pips/FleetDriverManagement/DeploymentPlans/FleetDriverManagementUndeployDP.log
    

    Microsoft Windows

    ant Uninstall -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml 
    -DPropertiesFile=<AIA_HOME>\aia_instances\<aia_instance>\config\AIAInstallProperties.xml 
    -DDeploymentPlan=<AIA_HOME>\pips\FleetDriverManagement\DeploymentPlans\FleetDriverManagementUndeployDP.xml 
    -l <AIA_HOME>\pips\FleetDriverManagement\DeploymentPlans\FleetDriverManagementUndeployDP.log
    

  3. Restart the SOA server.

  4. Uninstall the PIP following the instructions in Chapter 37, "Uninstalling Oracle AIA".

PKmPKYc|BOEBPS/serialtrackopsmebs.htm Configuring and Deploying the Serialization and Tracking: OPSM - EBS integration

34 Configuring and Deploying the Serialization and Tracking: OPSM - EBS integration

This chapter discusses how to configure and deploy Oracle Serialization and Tracking Integration Pack for Oracle Pedigree and Serialization Manager and Oracle E-Business Suite (Serialization and Tracking: OPSM - EBS).

This chapter includes the following sections:

34.1 Configuring Oracle Data Integrator

To run AIA Pre-Built Integrations Installer you must have ODI access with Supervisor privileges.

For install purposes, the ODI software must reside on the same server where Foundation Pack is installed. After the Serialization and Tracking: OPSM - EBS installation is complete, the ODI software can be installed on another server (if desired) connecting to the master and work repositories used during the Serialization and Tracking: OPSM - EBS installation.

34.1.1 Creating Oracle Data Integrator Repositories

You can use an existing master repository if it exists on an Oracle database and its ID is not 200. If its ID is 200, AIA advises that you create a new master repository.

You can use an existing work repository if it exists on an Oracle database and its ID is not 900. If its ID is 900, AIA advises that you create a new master repository.

When you run the DCW, it inserts or updates the integration artifacts into these repositories.

AIA recommends that you take a backup of the master and work repositories before you start the install process.

For information about creating Oracle Data Integrator Master and Work repositories, see the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator, "Administering the Oracle Data Integrator Repositories."

34.1.2 Performing Postinstallation Configurations for ODI

Perform the following steps to apply the required patches to your ODI 11.1.1.5.0.

To install prerequisite installer patch #10288265:

  1. Access My Oracle Support [https://support.oracle.com]

  2. Navigate to the Patches & Updates tab

  3. In the Patch Name or Number field, write 10288265

  4. Select your platform

  5. Click Search

  6. Download and install patch #10288265

To install patch #12837214:

  1. Access My Oracle Support [https://support.oracle.com]

  2. Navigate to the Patches & Updates tab

  3. In the Patch Name or Number field, write 12837214

  4. Select your platform

  5. Click Search

  6. Download and install patch #12837214

After applying the patches, launch the ODI Installer:

  1. Go to Topology.

  2. Go to Physical Architecture.

  3. Find the XML technologies and expand it.

    You should see data sources for all DVM's used in your ODI flows.

  4. Select each DVM data source.

  5. Go to the JDBC tab.

  6. Append this to the end of the URL "&back_compat_specific_keywords=true"

  7. Test the data source to make sure the connection is successful.

  8. Save your changes.

For a screenshot of this screen in ODI Installer, see Appendix B, "Oracle Data Integrator Screen".

34.2 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of Serialization and Tracking: OPSM - EBS. Enter the details of Serialization and Tracking: OPSM - EBS screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.

34.2.1 PIP Server Details Screen

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

Table 34-1 PIP Server Details Screen Fields

FieldDescription

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


34.2.2 Oracle Pedigree and Serialization Manager Database Details

Use this screen to enter details related to your Oracle Pedigree and Serialization Manager database instance. The screen contains the following fields:

Table 34-2 Oracle Pedigree and Serialization Manager Database Details Screen Fields

FieldDescription

OPSM Database Host

Specifies the fully qualified system name of the OPSM database. Example: example1.corp.oracle.com

OPSM Database Host is ______________________

OPSM Database Port

To find this value, contact the database administrator. Example: 8024

OPSM Database Port is _________________

OPSM Database Username

To find this value contact the database administrator. Example: sys.

OPSM Database Username is ______________________

OPSM Database Password

To find this value, contact the database administrator.

OPSM Database Password is ______________________

OPSM Database SID (System ID)

To find this value, contact the database administrator. Example: SID.

OPSM Database SID is ______________________

OPSM Database Schema

To find this value, contact the database administrator. The database schema name should be in upper case. Example: PAS.

OPSM Database Schema is _________________________


34.2.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 34-3 Oracle E-Business Suite Server Details Screen Fields

FieldDescription

E-Business Suite Host Name

Specifies the fully qualified 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 the administrator. Example: 8024.

E-Business Suite Port is ___________________________

E-Business Suite User Name

To find this value, contact the administrator.

E-Business Suite User Name is _____________________

E-Business Suite Password

To find this value, contact the administrator.

E-Business Suite Password is ______________________

Workflow Business Event System Name

This is the Workflow Business Event System Name of the E-Business Suite Server. For example: server2.xyz.com. To find this value, contact your administrator.

Workflow Business Event System Name is ___________________________

E-Business suite version

This is the version of the E-Business Suite application.


34.2.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 34-4 Oracle E-Business Suite Database Details Screen Fields

FieldDescription

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 ____________________

E-Business Suite Database Schema

To find this value, contact the database administrator. The database schema name should be in upper case. Example: APPS.

E-Business Suite Database Schema is _______________________________

Note: All the database credentials are used for creating the connection pool URL and data source URLs.


34.2.5 Oracle Data Integrator Access Information Details Screen

Use this screen to enter details for accessing Oracle Data Integrator. This screen contains the following fields:

Table 34-5 Oracle Data Integrator Access Information Details Screen Fields

FieldDescription

ODI_HOME

Provide the path to the ODI_HOME up to the oracledi folder (included).

To find this value, contact your administrator. Example: /slot/emsxxx/abc/ODI11113/oracledi/agent for Linux and c:\ODI11113\oracledi\agent for Windows.

ODI_Home is ___________________________

ODI User

To find this value, contact your administrator. Example: SUPERVISOR.

ODI User is ____________________________________

ODI Password

To find this value, contact your administrator. Example: SUNOPSIS

ODI Password is _________________________________

Path for exported DVMs

Enter the path to the directory where you want to export domain value mappings (DVMs). Example: <AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1/DVM_XMLS

One of the steps for setting up the integration is to export some DVMs to a location. The Installer must have this location to configure ODI artifacts during the install. It is recommended that you select a location in the same server where the ODI software runs.

Path for exported DVMs is _______________________


34.2.6 Oracle Data Integrator Master Repository Details Screen

You must set up an ODI Master Repository before installing the Serialization and Tracking: OPSM - EBS. This master repository must be created in an Oracle database.

The install process appends integration artifacts into this master repository.

Use this screen to enter details to access the Oracle Data Integrator master repository. If the master repository is configured, field values in the screen populate automatically.

The screen contains the following fields:

Table 34-6 Oracle Data Integrator Master Repository Details Screen Fields

FieldDescription

Database Host Name

To find this value, contact your database administrator. Example: server1.oracle.com

Database Host Name is _______________________________

Database Port Number

To find this value, contact your database administrator. Example: 1521

Database Port Number is ________________________________

Database Username

To find this value, contact your database administrator. Example: snpm

Database Username is _______________________________

Database Password

To find this value, contact your database administrator. Example: snpm

Database Password is _________________________________

Database SID (System ID)

To find this value, contact your database administrator. Example: oracle

Database SID is __________________________________


34.2.7 Oracle Data Integrator Work Repository for Serialization and Tracking: OPSM - EBS Details Screen

You must set up an ODI Work Repository before installing the Serialization and Tracking: OPSM - EBS. The install process imports the Serialization and Tracking: OPSM - EBS ODI artifacts into an ODI work repository. You can provide an existing ODI work repository or provide an empty one that has been created specifically for the PIP. It is recommended that you use an empty repository.

Use this screen to enter details related to the ODI work repository. If the master repository is configured, field values in the screen populate automatically.

The screen contains the following fields:

Table 34-7 Oracle Data Integrator Work Repository for Serialization and Tracking: OPSM - EBS Details Screen Fields

FieldDescription

ODI Work Repository Name

Enter the name you gave to the ODI work repository for PIP Artifacts. Example: OPSMEBS

ODI Work Repository Name is ___________________________

ODI Work Repository ID

Enter the ID number that you used for the ODI work repository. It should be between 1 and 899. Example: 200

Do not use 900. Also do not use the ID used for other work repositories.

ODI Work Repository ID is ______________________________

ODI Work Repository Database Host

To find this value, contact your database administrator. Example: localhost

ODI Work Repository Database Host is_______________________________

ODI Work Repository Database Port

To find this value, contact your database administrator. Example: 1521

ODI Work Repository Database Port is________________________________

ODI Work Repository Database SID

To find this value, contact your database administrator. Example: XE

ODI Work Repository Database SID is__________________________________

ODI Work Repository Database Username

To find this value, contact your database administrator. Example: master. This field is also known as the Work Repository Schema Name.

ODI Work Repository Database Username is_______________________________

ODI Work Repository Database Password

To find this value, contact your database administrator.

ODI Work Repository Database Password is_________________________________

ODI Work Repository Database Schema

To find this value, contact your database administrator. The database schema name should be in upper case. Example: OPSMEBSWORKREP.

ODI Work Repository Database Schema is __________________________________


34.3 Configuring and Deploying the Serialization and Tracking: OPSM - EBS

This section discusses the integration configuration and deployment process. There are two steps:

  1. Configure your integration using the deployment DCW.

  2. Deploy the integration to the Fusion Middleware server.

34.3.1 Configuring Serialization and Tracking: OPSM - EBS

The screens that appear prompt you to enter the data that is required for successful configuration of Serialization and Tracking: OPSM - EBS. Keep the completed worksheets of Serialization and Tracking: OPSM - 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 Serialization and Tracking: OPSM - EBS:

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

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

  3. Restart the server.

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

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

  6. Click Next.

  7. Select Serialization and Tracking: OPSM - EBS.

  8. Click Next.

34.3.1.1 Specify PIP Server Details

To specify PIP Server details:

  1. Enter information related to your PIP server in the PIP Server Details screen.

  2. Click Next.

34.3.1.2 Specify Oracle Pedigree and Serialization Manager Database Details

To specify Oracle Pedigree and Serialization Manager Database details:

  1. Enter information about your Oracle Pedigree and Serialization Manager Database instance in the Oracle Pedigree and Serialization Manager Database Details screen.

  2. Click Next.

34.3.1.3 Specify Oracle E-Business Suite Server Details

To specify Oracle E-Business Suite Server details:

  1. Enter information about your Oracle E-Business Suite Server in the E-Business Suite Server Details screen.

  2. Click Next.

34.3.1.4 Specify Oracle E-Business Suite Database Details

To specify Oracle E-Business Suite Database details:

  1. Enter information about your Oracle E-Business Suite Database in the E-Business Suite Database Details screen.

  2. Click Next.

34.3.1.5 Specify Oracle Data Integrator Access Details

To specify Oracle Data Integrator Access details:

  1. Enter information about your Oracle Data Integrator Access installation in the Oracle Data Integrator Access Information screens.

    Oracle Data Integration Access Information is captured in three screens. Enter the following information in the screens.

  2. Specify ODI Home.

  3. Click Next.

  4. Enter ODI User and ODI Password.

  5. Click Next.

34.3.1.6 Specify Oracle Data Integrator Master Repository Details

To specify Oracle Data Integrator Master Repository details:

  1. Enter information about your Oracle Data Integrator Master Repository installation in the Oracle Data Integrator Master Repository screen.

  2. Click Next.

34.3.1.7 Specify Oracle Data Integrator Work Repository for Serialization and Tracking: OPSM - EBS Details

To specify Oracle Data Integrator Work Repository for Serialization and Tracking: OPSM - EBS details:

  1. Enter information about your Oracle Data Integrator Work Repository for Serialization and Tracking: OPSM - EBS installation in the Oracle Data Integrator Work Repository for Serialization and Tracking: OPSM - EBS screen.

  2. Click Next.

34.3.1.8 Complete Configuration

To complete configuration:

  1. 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 PIP. You can configure using the steps described in Section 34.3.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.


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

  3. When the configuration process completes without errors, the AIA DCW displays the Configuration Complete screen.

  4. Click Finish to close the DCW.

34.3.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

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

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

34.3.3 Deploying Serialization and Tracking: OPSM - EBS

To deploy the integration to Fusion Middleware server:

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

  2. 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 undeployment command too.


    Table 34-8 Deployment Commands for the Serialization and Tracking: OPSM - EBS

    PlatformDeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems.

    HP-UX

    ant -f  <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml 
    -DDeploymentPlan=<AIA_HOME>/pips/OPSMtoEbiz/DeploymentPlans/OPSMtoEbizDP.xml 
    -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml  
    -l <AIA_HOME>/pips/OPSMtoEbiz/DeploymentPlans/OPSMtoEbiz.log
    

    Microsoft Windows

    ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml 
    -DDeploymentPlan=<AIA_HOME>\pips\OPSMtoEbiz\DeploymentPlans\OPSMtoEbizDP.xml 
    -DPropertiesFile=<AIA_HOME>\aia_instances\<aia_instance>\config\AIAInstallProperties.xml  
    -l <AIA_HOME>\pips\OPSMtoEbiz\DeploymentPlans\OPSMtoEbizDP.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 PIPs are not displayed.


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

34.4 Performing Postdeployment Configurations

This section discusses postdeployment configurations for the Serialization and Tracking: OPSM - EBS integration. The section includes:

34.4.1 Configuring Environment Variables

Configure the following environment variables:

Table 34-9 Environment Variables to be Configured for the Serialization and Tracking: OPSM - EBS

Environment VariableDescription

ODI_BIN_DIR

The location of the ODI program. Recommended: <ODIHOME>/oracledi/agent/bin


34.4.2 Launching the Serialization and Tracking: OPSM - EBS Agent

The Serialization and Tracking: OPSM - EBS agent should be up and running before you execute any scenario from ODI or OPSM.

To start the Serialization and Tracking: OPSM - EBS agent, navigate to <AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1/Agent_Files directory and run the start_odi_agent.bat file (or start_odi_agent.sh in Linux) command.

The agent is launched as a listener.


Note:

Ensure that the executable permission is enabled on all the shell scripts.


34.4.3 Stopping the Serialization and Tracking: OPSM - EBS Agent

When you are not using integration, you can stop the Serialization and Tracking: OPSM - EBS agent.

To stop the Serialization and Tracking: OPSM - EBS agent, navigate to <AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1/Agent_Files directory and run the stop_odi_agent.bat file (or stop_odi_agent.sh in Linux).

34.4.4 Configuring ODI Variables

A number of variables must be configured in ODI to support the Serialization and Tracking: OPSM - EBS. Many variables are configured when you install the integration. Configure the following variables using the ODI Designer. After the variables are defined in the ODI Designer, run the Regenerate All Scenarios package to reconfigure the main integration packages.

Table 34-10 ODI Variables to be Configured for the Serialization and Tracking: OPSM - EBS

ODI VariableDescription

PVV_FROM_EMAIL_ADDRESS

Email address for notification result queries.

PVV_TO_EMAIL_ADDRESS

Email addresses of individuals to be notified of integration results. Separate multiple email addresses with a comma.

PVV_PIP_HOME

Home directory of the PIP. Default value is <AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1

PVV_MAIL_SERVER

Mail server to which email is to be forwarded for notification.


All the ODI scenarios must be regenerated if any variable value is changed. To regenerate the ODI scenarios:

  1. Open ODI Operator.

  2. Expand the Scenarios tab.

  3. Right click the scenario you want to regenerate.

  4. Click Regenerate option.

  5. Click OK twice.

34.4.5 Configuring Web Services for Serialization and Tracking: OPSM - EBS (Optional)

Configure the following services:

  • CreateShipmentReceiptListEbizJMSProducer

  • CreateShipmentReceiptListEbizJMSConsumer

  • CreateShipmentReceiptListEbizReqABCSImpl

  • ShipmentReceiptEBS

  • CreateShipmentReceiptListPASProvABCSImpl

  • CreateShipmentReceiptListPASJMSProducer

  • CreateAdvanceShipmentNoticeListEbizJMSProducer

  • CreateAdvanceShipmentNoticeListEbizJMSConsumer

  • CreateAdvanceShipmentNoticeListEbizReqABCSImpl

  • AdvanceShipmentNoticeEBS

  • CreateAdvanceShipmentNoticeListPASProvABCSImpl

  • CreateAdvanceShipmentNoticeListPASJMSProducer

  • SyncItemLotListEbizJMSProducer

  • SyncItemLotListEbizJMSConsumer

  • SyncItemLotListEbizReqABCSImpl

  • ItemLotEBS

  • SyncItemLotListPASProvABCSImpl

  • SyncItemLotListPASJMSProducer

To configure the above Web Services, see Oracle Serialization and Tracking Integration Pack for Oracle Pedigree and Serialization Manager and Oracle E-Business Suite Implementation Guide.

34.4.6 Verifying the Database Connection (Optional)

To verify the database connection:

  1. Open ODI Topology Manager.

  2. Navigate to Technologies, Oracle in the Physical Architecture tab and expand the Oracle node.

  3. Select PASDS.

  4. Right click and select Open.

  5. Click Test Connection.

    The Test Connection window appears.

  6. Click Test.

    If successful connection message does not appear, verify the connection information in the Definitions and JDBC tabs.

  7. Repeat steps 1 - 6 for the following data sources:

    • OracleEbizDS

    • WorkRepDS

34.4.7 Configuring the Remote OPSM JMS Queue in Serialization and Tracking: OPSM - EBS (Required)

To configure the Remote OPSM JMS Queue in Serialization and Tracking: OPSM - EBS:

  1. Navigate to Administration Console (http://<server name>:<port number>/console).

  2. Log in with the server admin user name. For access details, contact the system administrator.

  3. Navigate to Domain Structure, soa_domain, Deployments.

  4. Click AIA_JmsAdapter_Config in the Deployments table.

  5. Select Configuration Tab.

  6. Select Outbound Connection Pools tab.

  7. Click eis/wlsjms/AIAPASCF instance in the Outbound Connection Pool Configuration Table.

  8. Update the following properties and leave the rest of the properties with their default values:

    Table 34-11 Properties to be Updated for Configuring the Remote OPSM JMS Queue

    Property NameProperty TypeProperty Value

    ConnectionFactoryLocation

    Java.lang.String

    oracle/apps/jms/pas/OPSMCF

    FactoryProperties

    Java.lang.String

    java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://<OPSM server host >:<SOA port number>


  9. Click Save.

  10. Navigate back to soa_domain, Deployments.

  11. Select AIA_JmsAdapter_Config and click Update.

  12. Select the option Update this application in place with new deployments plan changes…….

  13. Click Finish.

34.4.8 Configuring Cross Domain Security in Serialization and Tracking: OPSM – EBS (Required)

Cross Domain Security establishes trust between two WebLogic Server domain pairs by using a credential mapper to configure communication between these WebLogic Server domains.

To configure Cross Domain Security between the OPSM Weblogic Server domain and the PIP WebLogic Server domain:

  1. Enable Cross Domain Security.

    1. Open Administration Console: http://<server name>:<port number>/console.

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Navigate to Domain Structure, soa_domain.

    4. Open the Security: General tab in the console.

    5. Check Cross Domain Security Enabled.

    6. Click Save.

      Repeat steps a to f for the OPSM WebLogic Server domain.

  2. Configure a Cross Domain User.

    Cross-domain security in WebLogic Server uses a global security role named CrossDomainConnector with resource type remote and a group named CrossDomainConnectors, which is assigned the CrossDomainConnector role. Invocation requests from remote domains are expected to be from users with the CrossDomainConnector role. By default, the CrossDomainConnectors has no users as members. You must create one or more users and add them to the group CrossDomainConnectors. Typically, such a user is a virtual system user and preferably should have no privileges other than those granted by the CrossDomainConnector security role.

    1. Open Administration Console: http://<server name>:<port number>/console.

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Navigate to Domain Structure, soa_domain, Security Realms.

    4. Click the name of your security realm (default is myrealm).

    5. Open the Users and Groups tab in the console.

    6. Click New to create a user.

    7. Enter the Name, Description, and Password for the new user and click OK.

    8. On the Users and Groups: Users tab, click the name of the user you just created.

    9. Open the Groups tab.

    10. Find the CrossDomainConnectors group in the list of available parent groups on the left and click the shuttle button to move that group into the chosen group list on the right.

    11. Click Save.

      Repeat these steps for the OPSM WebLogic Server domain to create a cross domain user in that domain.

  3. Configure a Credential Mapping for Cross Domain Security.

    In each WebLogic Server domain, you must specify a credential to be used by each user on each remote domain to be trusted. Do this by configuring credential mappings for each domain in the connection.

    1. Open Administration Console: http://<server name>:<port number>/console.

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Navigate to Domain Structure, soa_domain, Security Realms.

    4. Click the name of your security realm (default is myrealm).

    5. Open the Credential Mappings: Default tab and click New.

    6. On the Creating the Remote Resource for the Security Credential Mapping:

      Select Use cros}s-domain protocol.

      In the Remote Domain field, enter the name of the remote domain that must interact with the local domain.

      Leave blank the Protocol, Remote Host, Remote Port, Path, and Method parameters.

      Click Next.

    7. On the Create a New Security Credential Mapping Entry page, enter the following:

      Local User: cross-domain

      Remote User: User configured in the Remote Domain that is authorized to interact with the Local Domain.

      Password: The password for the Remote User.

    8. Click Finish.

      Repeat the steps for the OPSM WebLogic Server domain to create a credential mapping for cross domain security on that domain.

34.4.9 Maintaining Serialization and Tracking: OPSM - EBS

Serialization and Tracking: OPSM - EBS integration files are maintained in the <AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1 (PIP_HOME) directory. This directory contains DVM xml files, Agent files, and error log files used by the ODI flows.

  • DVM xmls: Serialization and Tracking: OPSM - EBS integration is delivered with the location and work order status DVM xml files with their defaults mapping values. DVM files are maintained in the DVM_XMLS directory, which is available under the PIP_HOME directory. You can add additional mapping values by editing these xml files. The table below is an example of the Location DVM xml.

    Table 34-12 Serialization and Tracking: OPSM - EBS Location DVM XML

    EBIZ_01COMMONPAS_01

    M1

    M1 org

    M1

    M2

    M2 org

    M2

    P1

    P1 org

    P4


  • Agent files: Agent files are maintained in the Agent_Files directory, which is available under the PIP_HOME directory. To execute an ODI flow you must start an agent from this location.

  • Error logs: Error log files are used by the ODI flows. These logs are maintained in the ODI_Error_Records directory, which is available under PIP_HOME directory.

34.4.10 Adding File permissions

Add read,write and execute permissions for group, owner and others to all the files that are available under following folders:

  • <AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1/Agent_Files

  • <AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1/DVM_XMLS

  • <AIA_HOME>/services/core/BulkDataProcess/OPSMtoEbiz/Product/ODI/Oracle/V1/ODI_Error_Records

34.5 Verifying Deployment

To verify Serialization and Tracking: OPSM - EBS deployment:

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

  2. Confirm that the Serialization and Tracking: OPSM - EBS components were successfully installed.

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

    • AdvanceShipmentNoticeEBS

    • CreateAdvanceShipmentNoticeListEbizJMSConsumer

    • CreateAdvanceShipmentNoticeListEbizJMSProducer

    • CreateAdvanceShipmentNoticeListEbizReqABCSImpl

    • CreateAdvanceShipmentNoticeListPASJMSProducer

    • CreateAdvanceShipmentNoticeListPASProvABCSImpl

    • CreateShipmentReceiptListEbizJMSConsumer

    • CreateShipmentReceiptListEbizJMSProducer

    • CreateShipmentReceiptListEbizReqABCSImpl

    • CreateShipmentReceiptListPASJMSProducer

    • CreateShipmentReceiptListPASProvABCSImpl

    • ItemLotEBS

    • ShipmentReceiptEBS

    • SyncItemLotListEbizJMSConsumer

    • SyncItemLotListEbizJMSProducer

    • SyncItemLotListEbizReqABCSImpl

    • SyncItemLotListPASJMSProducer

    • SyncItemLotListPASProvABCSImpl

  3. Confirm that the Serialization and Tracking: OPSM - EBS queues (JMS) are installed.

    1. Log in to the Administration Console (http://<server name>:<port number>/console).

      Log in with the server admin user name. For access details, contact the system administrator.

    2. Navigate to soa_domain, Services, Messaging, JMS Modules, AIAJDBCJMSModule.

    3. Verify that the following queues exist in the summary of Resource table.

    • AIA_EbizItemLotJMSQueue: This queue is used between the SyncItemLotListEbizJMSProducer and SyncItemLotListEbizJMSConsumer.

    • AIA_EbizAdvanceShipmentNoticeJMSQueue: This queue is used between the CreateAdvanceShipmentNoticeListEbizJMSProducer and CreateAdvanceShipmentNoticeListEbizJMSConsumer.

    • AIA_EbizShipmentReceiptJMSQueue: This queue is used between the CreateShipmentReceiptListEbizJMSProducer and CreateShipmentReceiptListEbizJMSConsumer.

    • AIAEbizCF: This connection factory is used to connect AIA_EbizItemLotJMSQueue, AIA_EbizAdvanceShipmentNoticeJMSQueue, and AIA_EbizShipmentReceiptJMSQueue.

    • AIAPASCF: This connection factory is used to connect the JMS Queues that are available in the OPSM application which are OPSMLotSynchQueue and OPSMCreateTransactionQueue.

  4. Confirm that the necessary configuration properties exist.

    1. Log in to AIA home. For example, http://<host_name>:<port>/AIA/faces/aiaHomeLogin.jspx.

    2. Navigate to Setup, AIAConfiguration and check that the following configuration properties are listed:

    • CreateShipmentReceiptListEbizReqABCSImpl

    • CreateShipmentReceiptListPASProvABCSImpl

    • CreateAdvanceShipmentNoticeListEbizReqABCSImpl

    • CreateAdvanceShipmentNoticeListPASProvABCSImpl

    • SyncItemLotListEbizReqABCSImpl

    • SyncItemLotListPASProvABCSImpl

  5. Verify Integration Scenarios.

    1. Log in to AIA home. For example, http://<host_name>:<port>/AIA/faces/home.jspx.

    2. Find Project Lifecycle Workbench and click Go.

    3. On the AIA Project Lifecycle Workbench page, select industry as core and click Search.

    4. Click the link in the Bill Of Material column to view the following artifacts included in this integration.

    • AdvanceShipmentNoticeEBS

    • CreateAdvanceShipmentNoticeListEbizJMSConsumer

    • CreateAdvanceShipmentNoticeListEbizJMSProducer

    • CreateAdvanceShipmentNoticeListEbizReqABCSImpl

    • CreateAdvanceShipmentNoticeListPASJMSProducer

    • CreateAdvanceShipmentNoticeListPASProvABCSImpl

    • CreateShipmentReceiptListEbizJMSConsumer

    • CreateShipmentReceiptListEbizJMSProducer

    • CreateShipmentReceiptListEbizReqABCSImpl

    • CreateShipmentReceiptListPASJMSProducer

    • CreateShipmentReceiptListPASProvABCSImpl

    • ItemLotEBS

    • ShipmentReceiptEBS

    • SyncItemLotListEbizJMSConsumer

    • SyncItemLotListEbizJMSProducer

    • SyncItemLotListEbizReqABCSImpl

    • SyncItemLotListPASJMSProducer

    • SyncItemLotListPASProvABCSImpl

  6. Verify the following connections are accurate in the Physical Architecture tab.

    1. Launch ODI Topology Manager and navigate to Physical Architecture tab.

    2. Expand XML node under Technologies and double click LocationDS.

    3. Click JDBC tab and check for the connection <PVV_PIP_HOME>/DVM_XMLS/ LOCATION.xml.

    4. Similarly, find the following data servers based on the technology name.

      Table 34-13 Verifying Data Servers for the Serialization and Tracking: OPSM - EBS

      Data ServersTechnology

      LocationDS

      XML

      WorkOrderStatusDS

      XML

      OracleEbizDS

      Oracle

      PASDS

      Oracle

      WorkRepDS

      Oracle


  7. Verify the context in the Contexts tab.

    1. Launch ODI Topology Manager and navigate to Contexts tab.

    2. Double click EBIZ_01 and navigate to Schemas tab.

      Table 34-14 Verifying Context in the Serialization and Tracking: OPSM - EBS

      ContextDescription

      EBIZ_01

      Holds the correlation between logical schemas and physical ones.

      Verify the following schema association is set up. You may see more schemas than the one that is here. The integration processes ignore these additional schemas.

      Location

      OracleEbiz

      PAS

      WorkOrderStatus

      WorkRep


  8. Verify the following Logical Data Servers are imported in the Logical Architecture tab.

    1. Launch ODI Topology Manager and navigate to Logical Architecture tab.

    2. Expand XML node and double click Location logical schema.

    3. Select Definition tab and verify that the EBIZ_01 context has the LocationDS physical schema associated with it.

    4. Similarly, find the following logical data servers based on the technology.

      Table 34-15 Verifying Logical Data Servers for the Serialization and Tracking: OPSM - EBS

      Logical SchemaTechnology

      Location

      XML

      WorkOrderStatus

      XML

      OracleEbiz

      Oracle

      PAS

      Oracle

      WorkRep

      Oracle


  9. Launch the ODI Designer and verify that the OracleEbiz To PAS Model folder is imported in the Models tab. Expand the OracleEbiz To PAS Model folder and verify that the following models are present:

    • Location DVM Model

    • OracleEbiz Model

    • PAS Model

    • Work Order Status Model

  10. Launch the ODI Designer and verify that the OracleEbiz To PAS Project project is imported in the Project tab. Expand the OracleEbiz To PAS Project project and verify that the following project folders are present:

    • OracleEbiz To PAS Bulk Lot Folder

    • OracleEbiz To PAS Product Serialization Folder

    • OracleEbiz To PAS Product Synchronization Folder

    1. Expand the OracleEbiz to PAS Product Synchronization folder.

    2. Double-click the Load Location DVM XML procedure.

    3. Double-click the command Load Location DVM in the Details tab.

    4. Under Definition tab, click Command on Source sub tab.

    5. Verify that the path to LOCATION.xml is accurate.

    6. Using the same procedure verify the path for the Load Work Order Status DVM XML.

  11. Verify that the WSDL URL for the InvokeAIASyncErrorHandling step name is accurate for the AIAAsyncErrorHandlingBPELProcess in the Load OracleEbiz DiscreteMfg Bulk Lot Data to PAS package.

    1. Launch ODI Designer.

    2. Navigate to Projects tab.

    3. Expand the OracleEbiz To PAS Bulk Lot Folder.

    4. Double click Load OracleEbiz DiscreteMfg Bulk Lot Data to PAS Pkg.

    5. Select the Diagram tab.

    6. Click the InvokeAIAAsyncErrorHandling icon.

    7. In the Properties frame under the General tab verify that the WSDL URL user and password are accurate.

  12. Verify that the error log location for the Error Notification Step is accurate in the Load OracleEbizDiscreteMfg Bulk Lot Data to PAS Package.

    1. Click Email Notification step in Load OracleEbiz DiscreteMfg Bulk Lot Data To PAS package.

    2. In the properties frame under the General tab verify that the attachment url is accurate.

  13. Verify the OPSM database connection in the Load Error Records step.

    1. Double click the Load Error Log step in the Load OracleEbiz DiscreteMfg Bulk Lot to PAS Pkg.

    2. In the properties frame under the General tab verify that the JDBC URL is pointing to OPSM database.

  14. Repeat steps 10 - 13 for all the packages under the following folders.

    • OracleEbiz To PAS Bulk Lot Folder

    • OracleEbiz To PAS Product Serialization Folder

34.5.1 Validating Security Policies

All SOA composites are protected by the Global Policies provided by Foundation Pack as defined in the Security section of the Foundation Pack Developer's Guide. Additionally, individual services for this integration have locally attached security policies.

To validate locally attached security policies:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

  2. Navigate to Weblogic domain, soa_domain. In the window to the right, select the WebLogic Domain, then navigate to Web Services, Policies.

  3. Verify Service Policy attachment.

    1. Find the service policy in the list of policies.

    2. Click the number in Attachment Count column.

      The Usage Analysis screen appears.

    3. Change the Subject Type list box to SOA Service.

    4. Validate that all the composites are listed with local attachment to this service policy.

  4. Verify Client Policy attachment.

    1. Navigate back to the Policies screen and find the client policy.

    2. Click the number in Attachment Count column.

      The Usage Analysis screen appears.

    3. Change the Subject Type list box to SOA Reference.

    4. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.

      Table 34-16 No Authentication Service Policy Attachments for Serialization and Tracking: OPSM - EBS

      CompositeService Policy

      CreateAdvanceShipmentNoticeListEbizJMSProducer

      oracle/no_authentication_service_policy

      CreateShipmentReceiptListEbizJMSProducer

      oracle/no_authentication_service_policy

      SyncItemLotListEbizJMSProducer

      oracle/no_authentication_service_policy


      Table 34-17 Saml or User Name or Http Opt On Client Policy Attachments for Serialization and Tracking: OPSM - EBS

      CompositeReferenceClient Policy

      CreateAdvanceShipmentNoticeListEbizReqABCSImpl

      AIAAsyncErrorHandlingBPELProcess

      oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON

      CreateAdvanceShipmentNoticeListEbizProvABCSImpl

      AIAAsyncErrorHandlingBPELProcess

      oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON

      CreateShipmentReceiptListEbizReqABCSImpl

      AIAAsyncErrorHandlingBPELProcess

      oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON

      CreateShipmentReceiptListEbizProvABCSImpl

      AIAAsyncErrorHandlingBPELProcess

      oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON

      SyncItemLotListEbizReqABCSImpl

      AIAAsyncErrorHandlingBPELProcess

      oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON

      SyncItemLotListPASProvABCSImpl

      AIAAsyncErrorHandlingBPELProcess

      oracle/aia_wss_saml_or_username_or_http_token_service_policy_OPT_ON


For more information about security validation, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Working with Security."

For implementation, see Oracle Serialization and Tracking Integration Pack for Oracle Pedigree and Serialization Manager and Oracle E-Business Suite Implementation Guide.

34.6 Undeploying Serialization and Tracking: OPSM - EBS

To undeploy the Serialization and Tracking: OPSM - EBS from Fusion Middleware Server:

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

  2. Run the undeployment command for your platform.

    Table 34-18 Undeployment Command for Serialization and Tracking: OPSM - EBS

    PlatformUndeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems.

    HP-UX

    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/OPSMtoEbiz/DeploymentPlans/OPSMtoEbizUndeployDP.xml 
    -l <AIA_HOME>/pips/OPSMtoEbiz/DeploymentPlans/OPSMtoEbizUndeployDP.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\OPSMtoEbiz\DeploymentPlans\OPSMtoEbizUndeployDP.xml 
    -l <AIA_HOME>\pips\OPSMtoEbiz\DeploymentPlans\OPSMtoEbizUndeployDP.log
    

  3. Restart the SOA server.

  4. Uninstall the integration following the instructions in Chapter 37, "Uninstalling Oracle AIA".

PKB Oracle Data Integrator Screen

B Oracle Data Integrator Screen

This appendix includes screenshots of the Oracle Data Integrator (ODI) Installer that you see when configuring the ODI for the Financials Ops Control: Oracle Retail - PSFT PIP. For more information, see Chapter 27, "Configuring and Deploying the Financials Ops Control: Oracle Retail - PSFT PIP".

Figure B-1 Oracle Data Integrator Topology Screen

Description of Figure B-1 follows
Description of "Figure B-1 Oracle Data Integrator Topology Screen"

Figure B-2 JDBC Tab of the ODI Installer Screen

Description of Figure B-2 follows
Description of "Figure B-2 JDBC Tab of the ODI Installer Screen"

PKL PKYc|BOEBPS/upgradechapter.htm Upgrading Pre-Built Integrations

36 Upgrading Pre-Built Integrations

This chapter provides an overview of the Application Integration Architecture (AIA) upgrade process for the Pre-Built Integrations included in this release.

This chapter includes the following sections:


Note:

If you have AIA 2.4 or 2.5 installed, you cannot migrate or upgrade to AIA 11.1. You must install AIA 11.1 following the steps included in Chapter 3, "Installing Pre-Built Integrations"

To migrate customizations made to OOTB 2.4 or 2.5 artifacts, see the Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack

To migrate the 2.4 or 2.5 xref data to AIA 11.1, you must use the SOA xref utility. For more information, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

If you have modified or created custom services, custom DVMs and Xrefs, you must migrate these to AIA 11.1. For more information on migrating custom services, custom DVMs and Xrefs from AIA 2.4 or 2.5 to AIA 11.1, see the Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.


36.1 Understanding AIA Upgrade

The AIA upgrade process consists of three phases:

  1. Upgrade newer AIA Release: the file-system (under $AIA_HOME) is updated with the latest content.

  2. Merge customizations and extensions: if you have customized services, you must merge the customizations.

  3. Redeploy previously deployed PIPs or DIs: update the server to the latest content by redeploying new PIPs or DIs from the new release.

After these three tasks are completed, you can configure and deploy new PIPs or DIs from the new release.

36.1.1 Upgrading the AIA Release

You must run the AIA Pre-Built Integrations Installer and point to the existing $AIA_HOME where the previous AIA version is installed. The AIA Pre-Built Integrations Installer:

  1. Warns you when there is a previous release of AIA Pre-Built Integrations installed in $AIA_HOME.

  2. Updates the PIP and DI content in $AIA_HOME with the latest version, after you back up AIA_HOME.

36.1.2 Merging Customizations and Extensions

This applies if you have customized or extended the OOTB services or the PIPs or DIs. You must review the changes in this release and restore your customization and extensions after upgrading.

36.1.3 Redeploying previously deployed PIPs and DIs

After upgrading the release and merging your customizations and extensions, the previously deployed PIPs and DIs may be redeployed. FOR OOTB PIPs or DIs that require redeployment, see Section 36.2, "Upgrading Pre-Built Integrations" and Section 36.3, "Upgrading AIA R.V. 3.1.1 PIPs and DIs". The required upgrade scripts are included by the PIPs or DIs in this release.

For custom PIPs or DIs, you must identify the artifacts that require redeployment by rerunning the deployment plan of the specific PIP or DI or by redeploying the specific artifacts using a custom deployment plan.

36.2 Upgrading Pre-Built Integrations

This section lists the tasks that you must perform to upgrade pre-built integrations.

36.2.1 AIA Upgrade Requirements

AIA Pre-Built Integrations Installer upgrades your RV 3.1 version PIPs and DIs to RV 3.1.1.


Note:

Before upgrading Pre-Built Integrations 11.1 or AIA RV 3.1.1 PIPs or DIs, you must upgrade Foundation Pack to version 11.1.1.5.0, RUP patch 12636915 or later. For more information and instructions, see Oracle Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack If you are using an AIA Foundation Pack release that is earlier than 11.1.1.4.0, first upgrade to release 11.1.1.4.0 using the respective upgrade guides and then upgrade to 11.1.1.5.0.


To upgrade from Foundation Pack 11.1.1.4.0 to 11.1.1.5.0 you must manually run the upgrade scripts found in the Oracle Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack. To upgrade individual PIPs or DIs, you must manually run the upgrade scripts after you upgrade Foundation Pack.

AIA Pre-Built Integrations Installer does not republish AIA content to the service registry when you upgrade from Foundation Pack 11.1.1.4.0 to 11.1.1.5.0. To upgrade the registry with AIA 11.1.1.5.0 content, you must manually republish.

AIA Foundation Pack 11.1.1.5.0 contains bug fixes in Core Infrastructure areas (CAVS, BSR, and so on). When you upgrade from 11.1.1.4.0 to 11.1.1.5.0, these applications get redeployed. However, the upgrade does not have any impact because your data is preserved and all fixes are backward compatible.


Note:

The upgrade of individual components is not supported in this release.


36.2.1.1 Software and Hardware Requirements

The system requirements for the upgrade (CPU/memory/disk space) are the same as those discussed under Hardware Requirements.

For more details on the software requirements for your specific PIPs or DIs, see Chapter 2, "Software Requirements".

36.2.2 Performing Preupgrade Tasks for Pre-Built Integrations

Before running the AIA Pre-Built Integrations Installer, you must:

  1. Navigate a command prompt to the <AIA_HOME> parent directory: For example: "cd $AIA_HOME/..." (Go to the <AIA_HOME> directory and move up one directory higher).

  2. Change the file permissions for the <AIA_HOME> directory and all subdirectories recursively to Read/Write/Execute for User/Group/Other owners. For example: chmod -R 777 <AIA_HOME>.


Note:

These steps must be performed to upgrade every PIP or DI in Section 36.3, "Upgrading AIA R.V. 3.1.1 PIPs and DIs".


Back up extended solution artifacts

Following the AIA extensibility model, as documented in the extensibility sections of the Oracle Application Integration Architecture - Foundation Pack: Concepts and Technologies Guide and the Oracle Application Integration Architecture - Foundation Pack: Integration Developer's Guide, you created or updated one or more of the following artifacts:

  • Custom EBOs:

    These are AIA schema extensions performed on EBOs. Though the AIA Foundation Pack Installer automatically preserves these schema extensions, it is advisable to back up the custom directory. For example, all custom xsd files for core EBOs are accessed as http://hostname:port/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/

    If you are using the oracle application server, you can access this folder from SOA_HOME/Apache/Apache/htdocs/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/

  • Custom XSLTs:

    These are the extensions performed on the AIA Transformation style sheet. Foundation Pack does not contain any Extensible Stylesheet Language Transformations (XSLTs) for its components and utilities. Because the process content is delivered only in PIPs or DIs, you must manually back up the XSLTs if you have developed any for the custom integrations, and reapply them as a postupgrade step.

  • Custom EBS WSDL:

    If you have customized any EBS WSDL that is delivered or shipped with AIA Foundation Pack, you must back it up and restore it manually as a postupgrade step

36.2.3 Performing Upgrade Process for Pre-Built Integrations

Launching the AIA Pre-Built Integrations Installer

  • To launch AIA Pre-Built Integrations Installer:

  1. Navigate to aiapip/Disk1.

  2. Follow the launch instructions for your platform.

    Table 36-1 Launch Instructions for AIA Pre-Built Integrations Installer

    PlatformTo launch the AIA Pre-Built Integrations Installer

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit)

    HP-UX 11i (64 bit)

    At the command line prompt, enter:

    ./runInstaller -invPtrLoc <AIA_HOME>/oraInst.loc -jreLoc <location of the jre specific to your operating system. This directory should have /bin/java>
    

    Microsoft Windows (32-bit)

    Double-click setup.exe


  3. Click Next.

36.2.4 Choosing the Existing Home Directory

  • To choose the home directory where the existing version of Pre-Built Integrations is installed:

  1. Specify the home directory of your existing AIA implementation.


    Note:

    Provide the directory where Foundation Pack 11.1.1.4.0 was installed. The path should be available in the list. When you select the current home directory, AIA Pre-Built Integrations Installer disables the rest of the options in the screen and displays the information related to AIA (product name and version number) that is in the directory.


  2. Click Next.

36.2.5 Running the Directory Selection and Upgrade Process

  • To run the directory selection and upgrade process:

  1. On the Summary screen, review the summary of upgrade information.

    The summary screen provides information about the existing AIA Pre-Built Integrations installation.

  2. Click Install. This upgrades the Pre-Built Integrations version.

    PIP- and DI-related files get copied to the specified location. You must manually execute the PIP or DI upgrade scripts to complete the upgrade.

36.2.6 Performing Postupgrade Tasks for Pre-Built Integrations

You must perform the following key tasks after you successfully upgrade to pre-built integrations 11.1:

  • Merge extensions.

Any xsl extensions and wsdl customizations maintained in AIA HOME / SOA HOME must be merged with the preupgrade back up changes after comparison.

  • Restore customizations.

Any custom code developed and maintained in AIA HOME / SOA HOME must be restored.

  • Deploy any custom processes that were developed.

    If you plan to use any of the enhanced or new features in pre-built integrations 11.1, including the EBO changes, you must update these custom processes before re-deployment.

  • Upgrading ABCS Service Generator input.xml

    The input.xml files created in previous versions of the pre-built integrations do not directly work with 11.1.1.5.0 version of ABCS Service Generator. You must move GenerateReferenceWSDLFileIndicator element from GenerateOutputFiles section to each TargetService where you must reference the WSDL. This flag must be added to each of the targetservice sections.

    Log in to the AIA Console to verify that the following components are working:

  • OER (optional):

Ensure that the services and objects can be searched for and viewed. If you had any integration scenarios published, check whether they are accessed as well.

  • CAVS:

Check that the existing Test and Simulator definitions defined can still be viewed and are functional.

  • Error Handling and Setup:

Verify that the existing setup data (Setup Tab Page) is unchanged and two new columns (ERROR_TYPE, ERROR_EXT_HANDLER) are added to the Error Notifications table.

Perform additional post upgrade tasks as described in Section 36.4, "Performing Postupgrade Tasks for AIA".

The PIPs or DIs that are not listed in this section do not require updates because the contents have not changed.

36.3 Upgrading AIA R.V. 3.1.1 PIPs and DIs

This section discusses the upgrade process for AIA R.V 3.1 PIPs and DIs. The PIPs and DIs included in this section are upgraded from version 3.1 to 3.1.1.

36.3.1 Upgrading the Design to Release: Agile - EBS / PIM Integration

Upgrade Foundation Pack first and then upgrade the Design to Release: Agile - EBS / PIM integration following the tasks discussed below.

36.3.1.1 Performing Preupgrade Tasks for the Design to Release: Agile - EBS / PIM Integration

To upgrade the Design to Release: Agile - EBS / PIM integration from version 3.1 to 3.1.1, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.5.0 from your existing version before you can upgrade Design to Release: Agile - EBS / PIM PIP.

36.3.1.2 Running Upgrade Scripts for Design to Release: Agile - EBS / PIM Integration

To upgrade the integration on the Fusion Middleware server, run the command specific to your platform:

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

  2. Navigate to <AIA_HOME>pips/AgileToEbiz/upgrade/11.1 and run the command for your platform.

    Table 36-2 Deployment Commands for the Design to Release: Agile - EBS / PIM Integration

    PlatformDeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems

    HP-UX

    ./AgileToEbizUpgradeDP31_TO_111.sh

    Microsoft Windows

    AgileToEbizUpgradeDP31_TO_111.bat


  3. Review the log file in the location specified in the command to verify successful deployment.

36.3.1.3 Performing Postupgrade Tasks for Design to Release: Agile - EBS / PIM Integration

Verify the AIAConfigurationProperties.xml settings listed. If they do not exist, you must add them.

  1. Navigate to folder $AIA_HOME/aia_instances/<INSTANCE_NAME>/AIAMetaData/config.

  2. Take a backup of the file AIAConfigurationProperties.xml.

  3. Open the file AIAConfigurationProperties.xml.

  4. Search for <ServiceConfigurationserviceName="{http://xmlns.example.com/ABCSImpl/Ebiz/Core/CreateEngineeringChangeOrderListEbizProvABCSImpl/V1}CreateEngineeringChangeOrderListEbizProvABCSImpl">

  5. Add

    <!-- T to allow Unimplemented bom updates,F not to allow Unimplemented bom updates -->

    <Property name="UNIMPLEMENTED_BOM_UPDATES_ALLOWED">F</Property>

    <!-- T to allow item lcp skip,F not to allow item lcp skip -->

    <Property name="ALLOW_LIFECYCLE_PHASE_SKIP">F</Property>

  6. Search for <ServiceConfigurationserviceName="{http://xmlns.example.com/ABCSImpl/Ebiz/Core/ValidateEngineeringChangeOrderListEbizProvABCSImpl/V1}ValidateEngineeringChangeOrderListEbizProvABCSImpl">

  7. Add

    <!-- T to allow Unimplemented bom updates,F not to allow Unimplemented bom updates -->

    <Property name="UNIMPLEMENTED_BOM_UPDATES_ALLOWED">F</Property>

    <!-- T to allow item lcp skip,F not to allow item lcp skip -->

    <Property name="ALLOW_LIFECYCLE_PHASE_SKIP">F</Property>

  8. Save the changes.

  9. Reload the AIAConfig file from http://host:port/AIA.

  10. If the EBS version is 12.1.x, verify that patch 10172716:R12.INV.B is applied on the EBS database.

    If the EBS version is 11.5.10, verify that patch 12374991 is applied on the EBS database.

  11. Enable security in the 3 concurrent programs of the Design to Release: Agile - EBS integration.

    1. Set the value for the Profile Option Short Name as INV_EBI_SOASERVER_USER.

    2. Set the value for the Profile Option Display Name as EBS Integration: SOA SERVER USER.

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

    4. Copy the file to your local directory.

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

  12. Perform additional post upgrade tasks as described in Section 36.4, "Performing Postupgrade Tasks for AIA".

36.3.2 Upgrading the Design to Release: Agile PLM for Process - OPM PIP

Upgrade Foundation Pack first and then upgrade the Design to Release: Agile PLM for Process - OPM PIP following the tasks discussed below.


Note:

Existing patches for the Design to Release: Agile PLM for Process - OPM 3.1.1 PIP are still applicable in the 11.1 release and are not included as part of the upgrade process. After upgrading you must reapply any patches installed for the RV 3.1.


36.3.2.1 Performing Preupgrade Tasks for the Design to Release: Agile PLM for Process - OPM PIP

To upgrade the Design to Release: Agile PLM for Process - OPM PIP from version 3.1 to 3.1.1, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.5.0 from your existing version before you can upgrade Design to Release: Agile PLM for Process - OPM PIP.

36.3.2.2 Running Upgrade Scripts for the Design to Release: Agile PLM for Process - OPM PIP

To upgrade the PIP on the Fusion Middleware server, run the command specific to your platform:

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

  2. 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 -. The same is true when running the undeployment command.


    Table 36-3 Deployment Commands for the Design to Release: Agile PLM for Process - OPM PIP

    PlatformDeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems

    HP-UX

    ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>/pips/PLM4PEbizOPM/upgrade/11.1/PLM4PEbizOPMUpgrade31_To_111DP.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml -l <AIA_HOME>/pips/PLM4PEbizOPM/upgrade/11.1/PLM4PEbizOPMUpgrade31_To_111.log

    Microsoft Windows

    ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>\pips\PLM4PEbizOPM\upgrade\11.1\PLM4PEbizOPMUpgrade31_To_111DP.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<aia_instance>\config\AIAInstallProperties.xml -l <AIA_HOME>\pips\PLM4PEbizOPM\upgrade\11.1\PLM4PEbizOPMUpgrade31_To_111.log


  3. Review the log file in the location specified in the command to verify successful deployment.

36.3.2.3 Performing Postupgrade Tasks for the Design to Release: Agile PLM for Process - OPM PIP

36.3.3 Upgrading the Design to Release: Agile - JDE Integration

Upgrade Foundation Pack first and then upgrade the Design to Release: Agile JDE integration following the tasks discussed below.

36.3.3.1 Performing Preupgrade Tasks for the Design to Release: Agile - JDE Integration

To upgrade the Design to Release: Agile - JDE integration from version 3.1 to 3.1.1, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.5.0 from your existing version before you can upgrade Design to Release: Agile - JDE integration.

36.3.3.2 Running Upgrade Scripts for the Design to Release: Agile - JDE Integration

To upgrade the integration on the Fusion Middleware server, run the command specific to your platform:

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

  2. Run the command for your platform.

    Table 36-4 Deployment Commands for the Design to Release: Agile - JDE Integration

    PlatformDeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems

    HP-UX

    ./AgileToJDEE1UpgradeDP31_TO_111.sh

    Microsoft Windows

    AgileToJDEE1UpgradeDP31_TO_111.bat


  3. Review the log file in the location specified in the command to verify successful deployment.

36.3.3.3 Performing Postupgrade Tasks for the Design to Release: Agile - JDE Integration

36.3.4 Upgrading the Lead to Order: CRM OD - EBS PIP

Upgrade Foundation Pack first and then upgrade the Lead to Order: CRM OD -EBS PIP following the tasks discussed below.


Note:

Existing patches for the Lead to Order: CRM OD -EBS 3.1.1 PIP are still applicable in the 11.1 release and are not included as part of the upgrade process. After upgrading you must reapply any patches installed for the RV 3.1.


36.3.4.1 Performing Preupgrade Tasks for the Lead to Order: CRM OD - EBS PIP

To upgrade Lead to Order: CRM OD - EBS PIP from version 3.1 to 3.1.1, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.5.0 from your existing version before you can upgrade Lead to Order: CRM OD - EBS PIP.

36.3.4.2 Running Upgrade Scripts for the Lead to Order: CRM OD - EBS PIP

To upgrade the PIP on the Fusion Middleware server, run the command specific to your platform:

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

  2. Navigate to <AIA_HOME>pips/CRMODtoEbizLeadToOrder/upgrade/11.1 and run the command for your platform.

    Table 36-5 Deployment Commands for the Lead to Order: CRM OD - EBS PIP

    PlatformDeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems

    HP-UX

    ./CRMODtoEbizLeadToOrderUpgradeDP31_TO_111.sh

    Microsoft Windows

    CRMODtoEbizLeadToOrderUpgradeDP31_TO_111.bat


  3. Review the log file in the location specified in the command to verify successful deployment.

36.3.4.3 Performing Postupgrade Tasks for Lead to Order: CRM OD - EBS PIP

Perform additional post upgrade tasks as described in Section 36.4, "Performing Postupgrade Tasks for AIA".

36.3.5 Upgrading the Order to Cash: Siebel CRM - EBS PIP

Upgrade Foundation Pack first and then upgrade the Order to Cash: Siebel CRM - EBS PIP following the tasks discussed below.


Note:

Existing patches for the Order to Cash: Siebel CRM - EBS 3.1.1 PIP are still applicable in the 11.1 release and are not included as part of the upgrade process. After upgrading you must reapply any patches installed for the RV 3.1.


36.3.5.1 Performing Preupgrade Tasks for the Order to Cash: Siebel CRM - EBS PIP

To upgrade the Order to Cash: Siebel CRM - EBS PIP from version 3.1 to 3.1.1, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.5.0 from your existing version before you can upgrade Order to Cash: Siebel CRM - EBS PIP.

36.3.5.2 Running Upgrade Scripts for the Order to Cash: Siebel CRM - EBS PIP

To upgrade the PIP on the Fusion Middleware server, run the command specific to your platform:

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

  2. 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 undeployment command too.


    Table 36-6 Deployment Commands for the Order to Cash: Siebel CRM - EBS PIP

    PlatformDeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems

    HP-UX

    ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>/pips/OrderToCash/upgrade/11.1/OrderToCashUpgrade31_To_111DP.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml -l <AIA_HOME>/pips/OrderToCash/upgrade/11.1/OrderToCashUpgrade31_To_111.log

    Microsoft Windows

    ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>\pips\OrderToCash\upgrade\11.1\OrderToCashUpgrade31_To_111DP.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<aia_instance>\config\AIAInstallProperties.xml -l <AIA_HOME>\pips\OrderToCash\upgrade\11.1\OrderToCashUpgrade31_To_111.log


  3. Review the log file in the location specified in the command to verify successful deployment.

36.3.5.3 Performing Postupgrade Tasks for the Order To Cash: Siebel CRM - EBS PIP

Perform additional post upgrade tasks as described in Section 36.4, "Performing Postupgrade Tasks for AIA".

36.3.6 Upgrading the LSP Order Mgmt: OTM - EBS - Siebel CRM PIP

Upgrade Foundation Pack first and then upgrade the LSP Order Mgmt: OTM - EBS - Siebel CRM PIP following the tasks discussed below.


Note:

Existing patches for the LSP Order Mgmt: OTM - EBS - Siebel CRM 3.1.1 PIP are still applicable in the 11.1 release and are not included as part of the upgrade process. After upgrading you must reapply any patches installed for the RV 3.1.


36.3.6.1 Performing Preupgrade Tasks for the LSP Order Mgmt: OTM - EBS - Siebel CRM PIP

To upgrade the LSP Order Mgmt: OTM - EBS - Siebel CRM PIP from version 3.1 to version 3.1.1, you must manually execute the upgrade scripts. You must upgrade Foundation Pack to 11.1.1.5.0 from your existing version before you can upgrade the Order to Cash: Siebel CRM - EBS PIP.

36.3.6.2 Running Upgrade Scripts for the LSP Order Mgmt: OTM - EBS - Siebel CRM PIP

To upgrade the LSP Order Mgmt: OTM - EBS - Siebel CRM PIP on the Fusion Middleware server, run the command specific to your platform:

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

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


    Table 36-7 Deployment Commands for the LSP Order Mgmt: OTM - EBS - Siebel CRM PIP

    PlatformDeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems

    HP-UX

    ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>/pips/FleetOrderManagement/upgrade/11.1/FleetOrderManagementUpgrade31_To_111DP.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml -l <AIA_HOME>/pips/FleetOrderManagement/upgrade/11.1/FleetOrderManagementUpgrade31_To_111DP.log

    Microsoft Windows

    ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>/pips/FleetOrderManagement/upgrade/11.1/FleetOrderManagementUpgrade31_To_111DP.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml -l <AIA_HOME>/pips/FleetOrderManagement/upgrade/11.1/FleetOrderManagementUpgrade31_To_111DP.log


  3. Review the log file in the location specified in the command to verify successful deployment.

36.3.6.3 Performing Postupgrade Tasks for the LSP Order Mgmt: OTM - EBS - Siebel CRM PIP

Perform additional postupgrade tasks as described in Section 36.4, "Performing Postupgrade Tasks for AIA".

36.4 Performing Postupgrade Tasks for AIA

Evaluate the upgrade log file for any exceptions or warnings:

  • For pre-built integrations, the upgrade DP log is created on the name of the integration. For example, if you are upgrading the CRMOD to Ebiz Lead to Order PIP, the name of the log file is AIA_HOME/pips/CRMODtoEbizLeadToOrder/upgrade/11.1/CRMODtoEbizLeadToOrderUpgradeDP31_TO_111.log.

The following warning message describes the EOL content:

runCustomExtTracer:

[java] java.io.UTFDataFormatException: Invalid byte 1 of 1-byte UTF-8 sequence.

  • For objects that were identified to have been extended, the AIA Pre-Built Integrations Installer logs the list of EBOs that it found extended by you. These are reported in the following way:

[java] /slot/ems1846/oracle/FP_Upgrade_9June_1/patchset/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/InstalledProduct/V2/CustomInstalledProductEBO.xsd

[java] :[Element: <xsd:sequence [Namespace: http://www.w3.org/2001/XMLSchema]/>]element updated

  • Every major task performed by the AIA Pre-Built Integrations Installer is audited in the file. Here are some sample audit comments:

undeployAIAUI:

[echo] - Undeploying the Ear AIAApplication.ear

[java] 08/08/09 16:12:33 Notification ==>Application UnDeployer for AIAApplication STARTS.

DeployAIAUI:

[echo] - Deploying the Ear AIAApplication.ear

[oracle:deploy] Deploying application AIAApplication.

[oracle:deploy] Application deployer for AIAApplication COMPLETES.

[echo] - Deployment of AIAApplication.ear completed

From the backups that you performed, compare the following files and manually merge the configuration settings, as required:

You should consider restoring files from the backups of the <aia_instance>/AIAMetaData/config folder.

For more information about how to perform implementation-related configurations, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.

PK>PKYc|BOEBPS/partpage_iii.htm/ Upgrading Pre-Built Integrations

Part III

Upgrading Pre-Built Integrations

This part provides a general introduction to and the steps involved in upgrading Pre-Built Integrations.

This part contains the following chapter:

PK*?PKYc|BOEBPS/commsrevacct.htm Configuring and Deploying the Comms Revenue Accounting: BRM - EBS Pre-Built Integration

5 Configuring and Deploying the Comms Revenue Accounting: BRM - EBS Pre-Built Integration

This chapter discusses how to configure and deploy the Oracle Communications Billing and Revenue Management Integration Pack for Oracle EBusiness Suite: Revenue Accounting (Comms Revenue Accounting: BRM - EBS Pre-Built Integration).

This chapter includes the following sections:

5.1 Creating Oracle Data Integrator Repositories

Prerequisite/Assumption: The Master Repository and the Work Repository are created in ODI

You need not create a master repository. You can use an existing master repository if it exists on an Oracle database and the ID is between 126 and 999. If you are creating a new master repository, ensure that the repository ID is between 126 and 999.

You can use an existing work repository if it exists on an Oracle database and its ID is between 126 and 999. If its ID is not in that range, AIA advises you to create a repository with an ID between 126 and 999.

Table 5-1 details a list of ids you must avoid when creating master and work repositories.

Table 5-1 Prohibited IDs

Master Repository IDsWork Repository IDs

219

129

999

239

-

543


When you run the DCW, it inserts or updates the integration artifacts into these repositories.

AIA recommends that you take a backup of master and work repositories before you start the install process.

For information about creating Oracle Data Integrator Master and Work repositories, see the Oracle Data Integrator Installation Guide, "Creating Repositories."

5.2 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of the Comms Revenue Accounting: BRM - EBS Pre-Built Integration. Enter the details of the Comms Revenue Accounting: BRM - EBS Pre-Built Integration screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.

5.2.1 Integration Server Details Screen

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

Table 5-2 Integration Server Details Screen Fields

FieldDescription

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: server1.company.com.

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


5.2.2 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 5-3 Oracle E-Business Suite Server Details Screen Fields

FieldDescription

E-Business Suite Host Name

This value is the fully qualified computer 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: server2.xyz.com. To find this value, contact your administrator.

Workflow Business Event System Name is __________________

E-Business Suite Version

Examples: 11.5.10 or 12.1.1.

E-Business Suite version is __________________________


5.2.3 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 5-4 Oracle E-Business Suite Database Details Screen Fields

FieldDescription

E-Business Suite Database Host

This value is typically the computer 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: server1.

Database Schema is __________________________________

Note: All the database credentials are used for creating the connection pool URL and data source URLs.


5.2.4 Oracle Communications BRM Screen

Use this screen to enter details related to your Oracle Communications BRM instance. The screen contains the following fields:

Table 5-5 Oracle Communications BRM Screen Fields

FieldDescription

Primary CM Host Name

This is the host name of the primary Connection Manager (CM) of the BRM server. For example: example1.portal.com To find this value, contact your Oracle AQ system administrator.

Primary CM Host Name is ______________________________

Primary CM Port Number

This is the port number of primary Connection Manager (CM) of the BRM server. For example: 12600. To find this value contact your Oracle AQ system administrator

Primary CM Port Number is ______________________________

Database Host

This is the database host name of the Oracle AQ for which the BRM DM_AQ is configured. For example: example2.portal.com. To find this value, contact your Oracle AQ database administrator

Database Host is _______________________

Database Port

This is the database port number of the Oracle AQ. For example: 1521. To find this value, contact your Oracle AQ database administrator.

Database Port is _________________________

Oracle AQ Database SID

This is the database instance of the Oracle AQ. For example: orcl. To find this value, contact your Oracle AQ database administrator.

Oracle AQ Database SID is ________________

Oracle AQ Username

This is the database user name of the Oracle AQ. For example: PIN7820. To find this value, contact your Oracle AQ administrator.

Oracle AQ Username is ________________

Note: This value must be in uppercase (PIN7820) for the OOTB PLM flow to work.

Oracle AQ Password

This is the database password of the Oracle AQ. To find this value, contact your Oracle AQ administrator.

Oracle AQ Password is ___________________________

AQ Queue Name

This is the queue name configured for the BRM DM_AQ. For example: AqportalUser. To find this value, contact your Oracle AQ database administrator.

AQ Queue Name is _________________________________


5.2.5 Oracle Data Integrator Access Information Details Screens

Prerequisite/Assumption: Master Repository and the Work Repository are created in ODI,

Use these screens to enter details to access Oracle Data Integrator.

These screens contain the following fields:

Table 5-6 Oracle Data Integrator Access Information Details Screens Fields

FieldDescription

Path to Oracle Data Integrator

Provide the path to the ODI_HOME up to the oracledi/agent folder (included).

To find this value, contact your administrator. Example: /slot/ems8141/oracle/ODI11113/oracledi/agent for Linux and C\odi\oracledi\agent for Windows.

Path to Oracle Data Integrator is ___________________________

Path for exported DVMs

Enter the path of the directory to export Domain Value Mappings (DVM). DVM folder gets created along with Foundation Pack installation. If you have installed Foundation Pack use $AIA_HOME/AIAMetaData/dvm.

If you are installing the integration along with Foundation Pack for the first time, create a temporary folder for the DVMs. DVMs are exported to this location.

If you want to change the path to reflect the above location, open AIAInstallProperties.xml file from $AIA_INSTANCE/config post installation, search for odi.dvm.path and replace the temporary folder path with the above location.

Path for exported DVMs is ______________________________

ODI Username

To find this value, contact your administrator. Example: SUPERVISOR.

ODI Username is ____________________________________

ODI User Password

To find this value, contact your administrator. Example: SUNOPSIS

ODI User Password is _________________________________


5.2.6 Oracle Data Integrator Master Repository Details Screen

You must set up an ODI Master Repository before installing the Comms Revenue Accounting: BRM - EBS Pre-Built Integration. This master repository must be created in an Oracle database.


Note:

If you are using either a new master repository or an existing master repository, you must ensure that the identifier for that repository is between 126 and 999.


The install process appends integration artifacts into this master repository.

Use this screen to enter details to access the Oracle Data Integrator Master Repository. If the Master repository is configured, field values in the screen are populated automatically.

The screen contains the following fields:

Table 5-7 Oracle Data Integrator Master Repository Details Screen Fields

FieldDescription

Database Host

To find this value, contact your database administrator. Example: server1.oracle.com

Database Host is_______________________________

Database Port

To find this value, contact your database administrator. Example: 1521

Database Port is________________________________

Database SID

To find this value, contact your database administrator. Example: oracle

Database SID is__________________________________

Database Username

To find this value, contact your database administrator. Example: snpm

Database Username is_______________________________

Database Password

To find this value, contact your database administrator. Example: snpm

Database Password is_________________________________


5.2.7 Oracle Data Integrator Work Repository Details for Revenue Accounting Screen

The install process imports the Comms Revenue Accounting: BRM - EBS Pre-Built Integration ODI artifacts into an ODI Work repository. You can provide an existing ODI Work Repository or provide an empty one. It is recommended that you use an empty repository.


Note:

If you are creating either an existing work repository or a new work repository, you must ensure that the repository is created with an ID is between 126 and 999.


Use this screen to enter details related to the ODI Work Repository. If the Master repository is configured, field values in the screen are populated automatically.

The screen contains the following fields:

Table 5-8 Oracle Data Integrator Work Repository Details for Revenue Accounting Screen Fields

FieldDescription

ODI Work Repository Name

Enter the name you gave to the ODI Work Repository for integration Artifacts. Example: WORKREP

ODI Work Repository Name is ___________________________

ODI Work Repository ID

Enter the ID number that you used for the ODI Work Repository.

ODI Work Repository ID is ______________________________


5.3 Configuring and Deploying the Comms Revenue Accounting: BRM - EBS Pre-Built Integration

This section discusses the integration configuration and deployment process. There are two steps:

  1. Configure your integration using the DCW.

  2. Deploy the integration to the Fusion Middleware server.

5.3.1 Configuring the Comms Revenue Accounting: BRM - EBS Pre-Built Integration

The screens that appear prompt you to enter the data that is required for successful configuration of the Comms Revenue Accounting: BRM - EBS Pre-Built Integration. Keep the completed worksheets of the Comms Revenue Accounting: BRM - EBS Pre-Built Integration screens ready before you launch the DCW.

To configure the Comms Revenue Accounting: BRM - EBS Pre-Built Integration:


Note:

If you are harvesting content to Oracle Enterprise Repository (OER), perform the first three steps. Else start from step 4.


  1. Navigate to /slot/emsxxxx/oracle/Middleware/user_projects/domains/soa_domain/bin/ anHd open setDomainEnv.sh for Linux based systems and setDomainEnv.bat for Microsoft Windows.

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

  3. Restart the server.

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

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

  6. Click Next.

  7. Expand Communications Pre-built Integrations and select Comms Revenue Accounting: BRM - EBS.

  8. Click Next.

5.3.1.1 Specify Integration Server Details

To specify integration server details:

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

  2. Click Next.

5.3.1.2 Specify Oracle E-Business Suite Server Details

To specify Oracle E-Business Suite Server details:

  1. Enter information about your E-Business Suite Server in the E-Business Suite Server Details screen.

  2. Click Next.

5.3.1.3 Specify Oracle E-Business Suite Database Details

To specify Oracle E-Business Suite Database details:

  1. Enter information about your E-Business Suite Database in the E-Business Suite Database Details screen.

  2. Click Next.

5.3.1.4 Specify Oracle Communications BRM Details

To specify Oracle Communications BRM details:

  1. Enter Oracle Communications BRM information in the Oracle Communications BRM screen.

  2. Click Next.

5.3.1.5 Specify Oracle Data Integrator Access Details

To specify Oracle Data Integrator Access details:

  1. Enter information about your Oracle Data Integrator Access installation in the Oracle Data Integrator Access Information screens.

    Oracle Data Integration Access Information is captured in three screens. Enter the following information in the screens.

  2. Specify path to Oracle Data Integrator.

  3. Click Next.

  4. Specify the path for exported DVMs.

  5. Click Next.

  6. Enter ODI User name and ODI User Password.

  7. Click Next.

5.3.1.6 Specify Oracle Data Integrator Master Repository Details

To specify Oracle Data Integrator Master Repository details:

  1. Enter information about your Oracle Data Integrator Master Repository installation in the Oracle Data Integrator Master Repository screen.

  2. Click Next.

5.3.1.7 Specify Oracle Data Integrator Work Repository Details

To specify Oracle Data Integrator Work Repository details:

  1. Enter information about your Oracle Data Integrator Work Repository installation in the Oracle Data Integrator Work Repository Details for Revenue Accounting screen.

  2. Click Next.

5.3.1.8 Complete Configuration

To complete configuration:

  1. Review the configuration information on the Configuration Summary screen.


    Note:

    If you want to make changes to the configuration, use the navigation pane on the left and select the screen you want to edit.

    You can create a response file based on the input provided in the DCW and use it in future when you want to deploy the integration. You can configure using the steps described in Section 5.3.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.


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

  3. When configuration process finishes without errors, the AIA DCW displays the Configuration Complete screen.

  4. Click Finish to close the DCW.

5.3.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

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

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

5.3.3 Deploying the Comms Revenue Accounting: BRM - EBS Pre-Built Integration

To deploy the integration to Fusion Middleware server:

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

  2. Run the command for your platform.


    Note:

    In Windows 2008, 2008 R2 and Vista, run the command prompt as an administrator (elevated mode). If the command prompt is invoked in normal mode, the integrations are not displayed.


    Table 5-9 Deployment Commands for the Comms Revenue Accounting Pre-Built Integration

    PlatformDeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    $AIA_HOME/pips/Communications/RA/DeploymentPlans/deployRA.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME\pips\Communications\RA\DeploymentPlans\deployRA.bat
    

  3. Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/RADP_Deployments_YYYY-MM-DD_HH-MI-SS.log to verify successful deployment of the integration.

Oracle AIA ships a few artifacts in AIA Lifecycle Workbench which can be used in your integrations. These native artifacts created using FMW technologies such as BPEL, Mediator are natively supported by AIA Foundation Pack tools such as Project Lifecycle Workbench, Harvester, Deployment Generator, and AIA Installer Driver (AID). These artifacts include SOA artifact types such as composites, DataSources, DVM, xRef, and so on. These can be modified or new natively supported artifacts can be added using AIA Lifecycle Workbench and a BOM.xml file can be generated.

Integrations, most often, also require deployment of artifact types that are beyond what is supported by the Project Lifecycle Workbench and AIA Harvester. For instance, you may want to deploy artifacts such as Java applications, Shell Scripts, ANT based build scripts which constitute part of integration landscape in addition to the artifacts that are delivered by AIA. AIA also supports deployment of these supplementary artifacts. However, you must modify and add new non native artifacts outside AIA Lifecycle Workbench.

For more information on deploying artifacts, see the Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".

5.4 Verifying Deployment

To verify the Comms Revenue Accounting: BRM - EBS Pre-Built Integration deployment:

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

  2. Navigate to <AIAHome>/DISHome and verify whether the following folders have been created:

    • RevenueManagementHome

    • RevenueManagementHome/input

    • RevenueManagementHome/input/schema

    • RevenueManagementHome/success

    • RevenueManagementHome/failure

  3. Verify whether CurrencyCodeMapping.xml is present in the DVM path. This is the same path that is mentioned during installation. You can find this path in deploy.properties file under the property 'odi.dvm.path.

  4. Check <AIAHome>/DISHome/RevenueManagementHome/input/schema and find brm_gl_data.xsd.

  5. Open <AIA_Instance>/logs/RADP_Deployments_YYYY-MM-DD_HH-MI-SS.log. The log contains several statements starting with "[exec] OracleDI: Starting Command: OdiImportObject -FILE_NAME=". None of these statements should be followed by error messages except the error messages mentioned in Section 5.4.1, "Error Messages During Comms Revenue Accounting: BRM - EBS Pre-Built Integration Deployment".

5.4.1 Error Messages During Comms Revenue Accounting: BRM - EBS Pre-Built Integration Deployment

When deploying the Comms Revenue Accounting: BRM - EBS Pre-Built Integration, you can encounter the following errors:

  • Failed to execute: Create user xxxxx identified by yyyyy

  • Unique Constraint Violation

5.4.1.1 Failed to execute: Create user xxxxx identified by yyyyy

AIA Pre-Built Integrations Installer displays this error message in the log file if the install script attempts to create a database user name for an existing database user name. You can ignore this message and continue with the install process.

The AIA Pre-Built Integrations Installer displays the following message when it finds an identical database user name:

Example 5-1 Identical Database User Name Message

ODIInstall_CreateDBSchemaWorkRep:
[echo] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[echo] Creating ODI Work Repository DB User: xxxxx
[sql] Executing commands
[sql] Failed to execute: create user xxxxx identified by yyyyy
[sql] java.sql.SQLException: ORA-01920: user name 'xxxxx' conflicts with another user or role name
[sql] 1 of 2 SQL statements executed successfully
[echo] Done creating DB User for ODI Work Repository: xxxxx
[echo] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Note:

xxxxx refers to the database user name provided for ODI Work Repository and yyyyy is the password.


5.4.1.2 Unique Constraint Violation

AIA Pre-Built Integrations Installer displays this error message in the log file if the ODI data source xxxxx exists in the ODI master repository. The ODI data source is defined in Topology in the Physical Architecture tab. This error occurs when the Comms Revenue Accounting: BRM - EBS Pre-Built Integration is reinstalled.

The AIA Pre-Built Integrations Installer displays the following message when it finds an identical ODI data source:

Example 5-2 Identical ODI Data Source Message

[echo] - Importing CONN_xxxxx.xml
[exec] OracleDI: Starting Command: OdiImportObject -FILE_NAME=<AIA_HOME>/PIPS/Industry/Communications/DIS/Revenue/src/master/CONN_xxxxx.xml -IMPORT_MODE=SYNONYM_INSERT_UPDATE ...
[exec] java.sql.SQLException: ORA-00001: unique constraint (SNPM.PK_MTXT) violated

This error does not stop the install process. The process imports the remaining ODI integration artifacts into the ODI; however, it is important to verify the accuracy of the connections for these ODI data sources. To resolve this issue, verify that the connections and associated logical schemas in the ODI topology are accurate.

5.5 Undeploying the Comms Revenue Accounting: BRM - EBS Pre-Built Integration

This feature is not available for the Comms Revenue Accounting: BRM - EBS Pre-Built Integration.

PKEg<PKYc|BOEBPS/mdmprodcommsbrm.htmk Configuring and Deploying Product MDM: Comms BRM

18 Configuring and Deploying Product MDM: Comms BRM

This chapter discusses how to configure and deploy the Oracle Product Master Data Management Integration Option for Oracle Communications Billing and Revenue Management (Product MDM: Comms BRM).

This chapter includes the following sections:

18.1 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of the Product MDM: Comms BRM. Enter the details of the Product MDM: Comms BRM screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.

18.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 18-1 Integration Server Details Screen Fields

FieldDescription

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: server1.company.com.

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


18.1.2 Oracle Communications BRM Screen

Use this screen to enter details related to your Oracle Communications BRM instance. The screen contains the following fields:

Table 18-2 Oracle Communications BRM Details Screen

FieldDescription

Primary CM Host Name

This is the host name of the primary Connection Manager (CM) of the BRM server. For example: example1.portal.com To find this value, contact your Oracle AQ system administrator.

Primary CM Host Name is ______________________________

Primary CM Port Number

This is the port number of primary Connection Manager (CM) of the BRM server. For example: 12600. To find this value contact your Oracle AQ database administrator System Administrator

Primary CM Port Number is ______________________________

Database Host

This is the database host name of the Oracle AQ for which the BRM DM_AQ is configured. For example: example2.portal.com. To find this value, contact your Oracle AQ database administrator

Database Host is _______________________

Database Port

This is the database port number of the Oracle AQ. For example: 1521. To find this value, contact your Oracle AQ database administrator.

Database Port is _________________________

Oracle AQ Database SID

This is the database instance of the Oracle AQ. For example: orcl. To find this value, contact your Oracle AQ database administrator.

Oracle AQ Database SID is _______________________________

Oracle AQ Username

This is the database user name of the Oracle AQ. For example, PIN7820. To find this value, contact your Oracle AQ administrator.

Oracle AQ Username is _________________________

Note: This value must be in uppercase (PIN7820) for the OOTB PLM flow to work.

Oracle AQ Password

This is the database password of the Oracle AQ. To find this value, contact your Oracle AQ administrator.

Oracle AQ Password is ___________________________

AQ Queue Name

This is the queue name configured for the BRM DM_AQ. For example: AqportalUser. To find this value, contact your Oracle AQ database administrator.

AQ Queue Name is _________________________________


18.2 Overall Configuration and Deployment of MDM Product Integrations

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:

  1. Configure and deploy the MDM Product component integrations. Section 18.3 discusses configuring and deploying the Product MDM: Comms BRM. 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.

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

18.3 Configuring and Deploying Product MDM: Comms BRM

This section discusses the integration configuration and deployment process. There are two steps:

  1. Configure your integration using the DCW.

  2. Deploy the integration to the Fusion Middleware server.

18.3.1 Configuring Product MDM: Comms BRM

The screens that appear prompt you to enter the data that is required for successful configuration of the Product MDM: Comms BRM option. Keep the completed worksheets of the Product MDM: Comms BRM option screens ready before you launch the DCW.

To configure the Product MDM: Comms BRM:


Note:

If you are harvesting content to Oracle Enterprise Repository (OER), perform the first three steps. Else start from step 4.


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

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

  3. Restart the server.

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

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

  6. Click Next.

  7. Select Oracle Product Master Data Management Integration Option for BRM under Product Master Data Management Pre-Build Integration

  8. Click Next.

18.3.1.1 Specify Integration Server Details

To specify integration server details:

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

  2. Click Next.

18.3.1.2 Specify Oracle Communications BRM Details

To specify Oracle Communications BRM details:

  1. Enter Oracle Communications BRM information in the Oracle Communications BRM screen.

  2. Click Next.

18.3.1.3 Complete Configuration

To complete configuration:

  1. 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 18.3.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.


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

  3. When the configuration process finishes without errors, click Next.

  4. When the AIA DCW displays the Configuration Complete screen, click Finish to close the DCW.

18.3.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

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

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

18.3.3 Deploying the Product MDM: Comms BRM

To deploy the integration to Fusion Middleware server:

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

  2. 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 18-3 Deployment Commands for the Product MDM: Comms BRM

    PlatformDeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    sh $AIA_HOME/pips/MDMProductBRM/DeploymentPlans/deployMDMProductBRM.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME%\pips\MDMProductBRM\DeploymentPlans\deployMDMProductBRM.bat
    

  3. Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/MDMProductBRMDP_Deployments_YYYY-MM-DD_HH-MI-SS.log to verify successful deployment of the integration.

Oracle AIA ships a few artifacts in AIA Lifecycle Workbench which can be used in your integrations. These native artifacts created using FMW technologies such as BPEL, Mediator are natively supported by AIA Foundation Pack tools such as Project Lifecycle Workbench, Harvester, Deployment Generator and AID. These artifacts include SOA artifact types such as composites, DataSources, DVM, xRef, and so on. These can be modified or new natively supported artifacts can be added using AIA Lifecycle Workbench and a BOM.xml file can be generated.

Integrations, most often, also require deployment of artifact types that are beyond what is supported by the Project Lifecycle Workbench and AIA Harvester. For instance, you may want to deploy artifacts such as Java applications, Shell Scripts, ANT based build scripts which constitute part of integration landscape in addition to the artifacts that are delivered by AIA. AIA also supports deployment of these supplementary artifacts. However, you must modify and add new non native artifacts outside AIA Lifecycle Workbench.

For more information on deploying artifacts, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".

18.4 Verifying Deployment

To verify the Product MDM: Comms BRM deployment:

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

  2. Confirm that the Product MDM: Comms BRM services were installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control: (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

    • SyncItemListBRMProvABCSImpl

    • SyncPriceListListBRMProvABCSImpl

For more information about the DVMs to be verified, see the Oracle Application Integration Architecture Product Master Data Management Integration Pack Implementation Guide.

18.5 Undeploying the Product MDM: Comms BRM

To undeploy the integration from Fusion Middleware Server:

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

  2. Run the command for your platform.

    Table 18-4 Undeployment Command for the Product MDM: Comms BRM

    PlatformUndeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    sh $AIA_HOME/pips/MDMProductBRM/DeploymentPlans/undeployMDMProductBRM.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME%\pips\MDMProductBRM\DeploymentPlans\undeployMDMProductBRM.bat
    

  3. Restart the SOA server.

  4. Uninstall the integration following the instructions in Chapter 37, "Uninstalling Oracle AIA".

PKITkkPKYc|BOEBPS/aiainstallprocess.htm^M Understanding the Installation Process

1 Understanding the Installation Process

This guide provides an overview of the Oracle Application Integration Architecture (AIA) Pre-Built Integrations installation process.

This chapter includes the following sections:


Note:

For information about how to migrate 2.5 pre-built integrations to the 11.1 version, see Oracle Fusion Middleware Migration Guide for Oracle Application Integration Architecture.


1.1 Pre-Built Integrations Installation

Pre-Built Integrations installation consists of three stages:

  • Installation

  • Configuration

  • Deployment

Figure 1-1 Flow of the Pre-Built Integrations Installation

Description of Figure 1-1 follows
Description of "Figure 1-1 Flow of the Pre-Built Integrations Installation"

AIA Pre-Built Integrations Installer is built on Oracle Universal Installer (OUI) and enables you to install products included in Oracle AIA. AIA Pre-Built Integrations Installer is platform independent.

Pre-built integrations include multiple integration types:

  • Direct Integrations

  • Process Integration Packs

  • Partial Process Integration Packs

The Pre-Built Integrations 11.1 release delivers Direct Integrations (DI) and Process Integration Packs (PIP).

AIA Pre-Built Integrations Installer contains all the pre-built integrations as individual components, but does not install them individually. The AIA Pre-Built Integrations Installer lays down the pre-built integrations files inside AIA_HOME and installs all the components in the media pack.

You can also use AIA Pre-Built Integrations Installer to uninstall Oracle AIA.

For information about system requirements and supported platforms for Oracle Application Integration Architecture Foundation Pack, search for System Requirements and Supported Platforms for Oracle Application Integration Architecture Foundation Pack on http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html and download the xls file.

For information about system requirements and supported platforms for Oracle Application Integration Architecture 11.x, search for System Requirements and Supported Platforms for Oracle Application Integration Architecture 11.x on http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html and download the xls file.

The Deployment Configuration Wizard (DCW) defines the configurations needed for each pre-built integrations and guides you through the configuration. When you launch the DCW, you select the individual pre-built integrations to configure and enter the information required for the configuration. DCW prevents you from selecting mutually exclusive integrations.

For details about the DCW, see Section 1.3, "Pre-Built Integrations Configuration".

For details about the configuration information required for your pre-built integrations, see the applicable pre-built integrations chapters in Part I, "Configuring and Deploying Pre-Built Integrations" and Part II, "Configuring and Deploying AIA RV 3.1.1 PIPs and DIs"of this guide.

When your pre-built integrations are configured, you run the pre-built integrations deployment command and specify the deployment plan.

For more details about Deployment, see Section 1.4, "Pre-Built Integrations Deployment"

For more details about the deployment information required for your pre-built integrations, see the applicable pre-built integrations chapters in Part I, "Configuring and Deploying Pre-Built Integrations" and Part II, "Configuring and Deploying AIA RV 3.1.1 PIPs and DIs"of this guide.

1.2 Cluster Installation

AIA Pre-Built Integrations Installer enables you to deploy the pre-built integration content directly to an existing AIA Foundation Pack cluster. You must successfully set up the AIA Foundation Pack cluster before attempting to deploy pre-built integrations on the cluster.

For more information on how to set up your Foundation Pack cluster see, Oracle Fusion Middleware Installation and Upgrade Guide for Oracle Application Integration Architecture Foundation Pack.

AIA PIPs and DIs (and AIA Foundation Pack) deploy to cluster nodes that are configured during the underlying SOA cluster setup. Depending on how the SOA cluster is set up, the AIA PIPs and DIs deploy in different ways. The most common deployment options are:

  • Cluster nodes can be spread across different physical servers. This option is the most common for production deployments as it provides high-availability and is the Oracle recommended topology per the Enterprise Deployment Guide.

  • Cluster nodes can be present in the same physical server. This option provides increased throughput for the same hardware.

For more information on how to set up your SOA cluster, see Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite.

During the installation process, PIPs and DIs deploy to all nodes of the cluster in one flow. Repeating the steps provided in the guide on all nodes of the cluster is not required.When providing the SOA server details on the AIA Foundation Pack Installer, the cluster name automatically appears in the list of available managed servers.The Foundation Pack installation creates and configures a unique AIA Instance which identifies the cluster as a whole.The PIP or DI is configured and deployed to this unique created AIA Instance. The complete configuration and deployment is directly targeted to the cluster as a whole.

AIA products deploy to all nodes of the SOA cluster. Additional nodes can be added to an existing SOA cluster.

Before you proceed to install and configure AIA PIPs or DIs to the cluster, check the successful setup of your SOA cluster and AIA Foundation Pack cluster setup by accessing appropriate URLs, such as Oracle Enterprise Manager, weblogic console and AIA Home page from all the nodes participating in the cluster. Additional tests like sample deployments can also be done to ensure that the cluster setup is indeed working well.

1.3 Pre-Built Integrations Configuration

Oracle AIA DCW helps you configure the PIPs and DIs that are delivered in the pre-built integrations release. The screens that appear when you run the DCW are based on whether you choose to configure single or multiple pre-built integrations. This sections includes an overview of the configuration options available.

When you configure a pre-built integrations, DCW prompts for pre-built integrations specific information. For more information about the configuration information required for your pre-built integrations, see the applicable pre-built integrations chapters in Part I, "Configuring and Deploying Pre-Built Integrations" and Part II, "Configuring and Deploying AIA RV 3.1.1 PIPs and DIs".

When you configure multiple pre-built integrations, the following occurs:


Note:

The configuration screen sequence described in the specific pre-built integrations configuration and deployment chapters is based on the assumption that you are configuring a pre-built integrations for the first time, and that you are configuring one pre-built integrations at a time.


  • When multiple pre-built integrations are selected for configuration at the same time, and these pre-built integrations have one or more common participating applications, DCW queries for common details only one time.

    For example, if integration1 and integration2 both connect to Oracle E-Business Suite, then the information for this participating application is collected one time.

  • When configuring pre-built integrations over an existing configuration which has one or more integrations, and the new integration selected for configuration share one or more participating applications with existing pre-built integrations, then the common application information that is captured is shown to you. You can choose to change the captured information or keep it the same.

    For example, when the first run of the DCW configures integration1 and the second run tries to configure integration2, and integration2 shares a participating application with integration1 such as Oracle E-Business Suite, then DCW shows the captured details and asks you to overwrite or not. If you choose not to overwrite then the details previously provided are retained.

1.3.1 Routing Rules Configuration in Enterprise Business Services

Every pre-built integrations has its own set of routing rules. These routing rules get delivered when you install Oracle AIA. However, the routing rules implementation can differ depending upon the various installation scenarios.

When you deploy a single pre-built integrations, the Enterprise Business Services (EBS) for that integration are deployed with all default routing rules delivered by Oracle AIA.

When you deploy multiple pre-built integrations (Comms pre-built integration and Core PIP) at the same time, the EBS that are used by multiple pre-built integrations do not get deployed. You must manually configure the routing rules to suit the functional scenario for the combination of the pre-built integrations. However, the routing rules that were delivered through only one of pre-built integrations get deployed.

For more information about using and extending routing rules, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite, " Creating Mediator Routing Rules".


Note:

Customers who are installing the Comms Agent Assisted Billing Care Pre-Built Integration and the Communications Order to Cash Pre-Built Integration do not have to perform this task.

Customers who are installing MDM Customer base along with one or more options pre-built integrations, do not have to perform this task when only MDM customer pre-built integrations are being deployed.

Customers who are installing MDM Product base along with one or more options pre-built integrations, do not have to perform this task when only MDM product pre-built integrations are being deployed.


The routing rules for the same EBS delivered through other integrations are available in AIA_HOME/pips/<PIP Name>/EBS. The install log provides information about the EBS for which you need configure routing rules. The install log reads, "<EBS Name> already deployed. The routing rules for PIP <PIP Name> have not been added. AIA_HOME/pips/<PIP Name>/EBS contains Oracle Delivered EBS with routing rules for this PIP".

For more information about how to use these delivered routing rules to design and implement your own Oracle AIA routing rules and the associated Oracle AIA configuration properties, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.


Note:

For EBS that are not shared between the pre-built integrations, all the default routing rules delivered with the pre-built integrations are deployed.


1.3.2 Installation, Configuration and Deployment Topologies

There are several installation and deployment topologies possible using AIA Pre-Built Integrations Installer. Choose the installation that best suits your needs. For more details, see the whitepaper AIA Installation and Deployment -Strategies, Topologies and Flexibilities on http://www.oracle.com/index.html.

Only one instance of each participating application can participate in any given direct or process integration when configured through the DCW. After installing using AIA Pre-Built Integrations Installer, you can configure pre-built integrations to connect to multiple instances. You must customize the deployment commands to configure the specific pre-built integrations to connect to multiple instances. DCW does not support this configuration.

1.4 Pre-Built Integrations Deployment

This section discusses the deployment of the pre-built integrations included in this release.

The deployment of a pre-built integrations is done through the deployment plan. The deployment plan and the configured AIAInstallProperties.xml are passed as parameters to the AIA Install Driver (AID) for deployment.

You must configure the AIAInstallProperties.xml with the corresponding pre-built integrations Server details. AID does not perform any checks to validate the AIAInstallProperties.xml has been configured with the corresponding pre-built integrations Server details.

Each pre-built integrations ships a main deployment plan, a supplementary deployment plan (optional) and a conditional policy file (optional). These files are passed as parameters to the AID with the configured AIAInstallProperties.xml. AID retrieves the required property values from the install properties file and deploys the pre-built integrations.

1.4.1 Pre-Built Integrations Codeployment

PIPs or DIs that do not belong to the same pre-built integrations group can be codeployed. For example, the Order to Cash: Siebel CRM - EBS and Customer Master Data Management Pre-Built Integrations. Before you install multiple PIPs or DIs on a single SOA instance, see the Oracle Application Integration Architecture Pre-Built Integrations 11.1: Functional Interoperability Configuration Guide and check whether your PIP or DI combination is supported on a single instance.

To install multiple PIPs that do not support codeployment, you must install each PIP or DI on a separate SOA instance. Installing unsupported PIP or DI combinations on a single SOA instance may require custom changes to accommodate any resulting functional impact or common PIP or DI components, such as common routing rules.

1.4.2 Pre-Built Integrations Security Policies

AIA Pre-Built Integration composites are protected by Oracle Web Services Manager (WSM) security policies by default. In this release, the minimum protection provided by AIA services is authentication. The default policies are automatically applied when the integration is deployed, using either of the following strategies:

  1. Global security policies are automatically attached to all composites matching the AIA naming conventions.

  2. Local security policies are automatically attached to composites whose security requirements differ from the global policy or whose name does not match the AIA naming conventions.

For more information on how Global and Local security policies are attached during deployment, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack"Working with Security".

1.4.2.1 Default Security Policies

AIA recommends hardening the services with message protection in the production environment. Before attempting to modify the default security policies, you must understand the Oracle WSM policy configuration and the global and local deployment strategies completely. Changes to the default policies without proper understanding could impact the integration's expected behavior.

AIA does not recommend disabling default policies completely.

For more information see Oracle Fusion Middleware Security and Administrator's Guide for Web Services.

1.4.2.2 Security Policy Validation

Validating that the default security policies are correctly deployed before running the integration is recommended.

For more information on how to validate the security policies for your integrations, see the latest applicable implementation guide.

1.4.3 Pre-Built Integrations Un-Deployment

To un-deploy a pre-built integrations, you must un-deploy the PIPs or DIs included in it. The un-deployment of a PIP or DI is done through the un-deployment plan. The un-deployment plan and the configured AIAInstallProperties.xml are passed as parameters to AID for un-deployment.

For more details about the un-deployment information required for your integrations, see the applicable PIP or DI chapters in Part I, "Configuring and Deploying Pre-Built Integrations" and Part II, "Configuring and Deploying AIA RV 3.1.1 PIPs and DIs" of this guide.

1.5 AIA Master Notes

AIA master notes provide you with a one-stop reference point for all the documentation available for your pre-built integrations. AIA master notes are stored on My Oracle Support (MOS) [https://support.oracle.com]. To find a specific master note, search in MOS using the note ID.

Note 1318600.1 is the main master note for the AIA 11.1 release and includes links to pre-built integration specific master notes. The specific master notes for each pre-built integration include links to:

  • Installation pre-requisites

  • Certification matrix

  • Software downloads and required patches

  • Release notes

  • Implementation guide

  • Known issues and workarounds

Before starting the installation process, review the master note for your specific pre-built integration.

PK=^^PKYc|BOEBPS/preface.htm9 Preface

Preface

Welcome to Oracle Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.1.

What's New in this Guide

Common Oracle AIA Pre-Built Integration Guides

Oracle Application Integration Architecture Pre-Built Integrations 11.1 includes the following guides shared by all products delivered with this release:

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Additional Resources

The following resources are also available:

PK>i>9PKYc|BOEBPS/mdmprodsiebel.htm Configuring and Deploying Product MDM: Siebel CRM

16 Configuring and Deploying Product MDM: Siebel CRM

This chapter discusses how to configure and deploy Oracle Product Master Data Management Integration Option for Siebel CRM (Product MDM: Siebel CRM).

This chapter includes the following sections:

16.1 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of Product MDM: Siebel CRM. Enter the details of Product MDM: Siebel CRM screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.

16.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 16-1 Integration Server Details Screen Fields

FieldDescription

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: server1.company.com.

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


16.1.2 Siebel CRM Server Details Screen

Use this screen to enter details related to your Siebel CRM server instance. The screen contains the following fields:

Table 16-2 Siebel CRM Server Details Screen Fields

FieldDescription

Siebel HTTP Host name

This is a computer name of the Siebel host. For example: sdcp1953i054.corp.siebel.com. To find the value, contact your administrator.

Siebel HTTP Host name is _____________________________

Siebel HTTP Port

This value is the Siebel application port. For example: 80. To find the value, contact your administrator.

Siebel HTTP Port is ________________________________

Siebel Internet Protocol

Specifies the Siebel host internet protocol. For example: http://.

Siebel host internet protocol is _____________________________

Siebel EAI Application User

The Siebel application user is used for making EAI web service calls. For example: sadmin. To find the value, contact your administrator.

Siebel EAI Application User is ___________________________

Siebel EAI Application Password

This is the password for the EAI user. For example: sadmin. To find the value, contact your administrator.

Siebel EAI Application Password is ________________________

Siebel Enterprise Server Name

This is the Siebel server name. For example: siebel. To find the value, contact your administrator.

Siebel Enterprise Server Name is __________________________

Siebel Version

This is the version of the Siebel CRM application.

Siebel Language

This is the language used by the Siebel application. For example, enu.

Siebel Language is ________________________


16.1.3 Siebel CRM Database Details Screen

Use this screen to enter details related to your Siebel CRM database instance. The screen contains the following fields:

Table 16-3 Siebel CRM Database Details Screen Fields

FieldDescription

Siebel Database Host

This value is typically the computer name. For example: server1.oracle.com. To find the value, contact your database administrator.

Siebel Database Host is _________________________________

Siebel Database Port

This is the Siebel database port. For example: 1521. To find the value, contact your database administrator.

Siebel Database Port is _________________________________

Siebel Database Username

Specifies a database user that has access to loading the EIM tables Siebel. To find this value, contact the database administrator. Example: ora12345

Siebel Database Username is ______________________

Siebel Database Password

This is the Siebel Database Password. For example: ora07103. To find the value, contact your database administrator.

Siebel Database Password is _____________________

Siebel Database SID

This is the Siebel database system ID. For example: qa7a. To find the value, contact your database administrator.

Siebel Database SID is ________________________________


16.2 Session Pool Manager Details Screen

The Session Pool Manager (SPM) details are optional and required only when your Siebel server is outside of the firewall. If all your servers are within the network, leave these fields blank.

In the java.net application programming interface (API) used by SPM, proxies are supported through two system properties: http.proxyHost and http.proxyPort. They must be set to the proxy server and port respectively. This value is only set when ProxySettings_Enabled is set to TRUE.

Table 16-4 Session Pool Manager Details Screen Fields

FieldDescription

Proxy host url

This determines the server to be set in the system properties for http.proxyHost property.

Proxy host url is ___________________________

Proxy port

This determines the port to be set in the system properties for the http.proxyPort property.

Proxy port is ______________________________



Caution:

These fields are optional so leave the values blank. These values are required only if the Siebel server is outside of the firewall.


16.3 Overall Configuration and Deployment of MDM Product Integrations

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:

  1. Configure and deploy the MDM Product component integrations. Section 16.4 discusses configuring and deploying the Product MDM: Siebel CRM. 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.

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

16.4 Configuring and Deploying Product MDM: Siebel CRM

This section discusses the integration configuration and deployment process. There are two steps:

  1. Configure your integration using the DCW.

  2. Deploy the integration to the Fusion Middleware server.

16.4.1 Configure Product MDM: Siebel CRM

The screens that appear prompt you to enter the data that is required for successful configuration of Product MDM: Siebel CRM. Keep the completed worksheets of Product MDM: Siebel CRM 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: Siebel CRM:

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

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true"

  3. Restart the server

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

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

  6. Click Next

  7. Select Oracle Product Master Data Management Integration Option for Siebel CRM under Product Master Data Management Pre-Build Integration

  8. Click Next

16.4.1.1 Specify Integration Server Details

To specify integration server details:

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

  2. Click Next.

16.4.1.2 Specify Siebel CRM Server Details

To specify Siebel CRM Server details:

  1. Enter information about your Siebel CRM application in the Application Details - Siebel CRM screen.

  2. Click Next.

16.4.1.3 Specify Siebel CRM Database Details

To specify Siebel CRM Database details:

  1. Enter information about your Siebel CRM database in the Siebel CRM Database Details screen.

  2. Click Next.

16.4.1.4 Specify Session Pool Manager Details

To specify Session Pool Manager details:

  1. Enter information related to your Session Pool Manager installation in the Session Pool Manager Details screen.

  2. Click Next.

16.4.1.5 Complete Configuration

To complete configuration:

  1. 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 16.4.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.


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

  3. When the configuration process finishes without errors, click Next.

  4. When the AIA DCW displays the Configuration Complete screen, click Finish to close the DCW.

16.4.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

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

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

16.4.3 Deploying Product MDM: Siebel CRM

To deploy the integration to Fusion Middleware server:

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

  2. 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 16-5 Deployment Commands for Product MDM: Siebel CRM

    PlatformDeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    sh $AIA_HOME/pips/MDMProductSiebel/DeploymentPlans/deploySiebel.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME%\pips\MDMProductSiebel\DeploymentPlans\deploySiebel.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 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".

16.5 Postdeployment Configuration

This section includes the postdeployment configurations required for the Product MDM: Siebel CRM.

16.5.1 Configuring Session Pool Manager

This integration uses the Session Pool Manager utility. Configure Session Pool Manager after you install the integration. For information on how to configure Session Pool Manager for your integration environment and needs, see the Oracle Application Integration Architecture Process Integration Pack Utilities Guide, "Session Pool Manager".

16.5.2 Updating Product.Source.PIP Property Value

To update the Product.Source.PIP property value:

  1. Edit the AIAConfigurationProperties.xml file located in <AIA_INSTANCE>/AIAMetaData/config.

  2. Locate the Product.Source.PIP property and change the value as follows:

    From: <Property name="Product.Source.PIP">O2C</Property>

    To: <Property name="Product.Source.PIP">MDM</Property>

16.6 Verifying Deployment

To verify the Product MDM: Siebel CRM deployment:

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

  2. Confirm that the Product MDM: Siebel CRM services were installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control: (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

    • ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl

    • SyncBillOfMaterialsListSiebelProvABCSImp0'l

    • SyncClassificationSchemeListSiebelProvABCSImpl

    • SyncItemCompositionListSiebelCommsProvABCSImpl

    • SyncProductSiebelProvABCSImpl

    • SyncSpecificationValueSetListSiebelProvABCSImpl

    For more information about the DVMs to be verified, see the Oracle Application Integration Architecture Product Master Data Management Integration Pack Implementation Guide.

  3. Verify whether Session Pool Manager is successfully installed and ensure that the Siebel server is active.

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control: (http://<server name>:<port number>/em/).

    2. Expand Farm_soa_domain, SOA, soa-infra (soa_server1), Default and click AIASessionPoolManager on the left panel.

    3. Click Test.

    4. Enter Operation = Start.

    5. Under the collapsible section titled Security, select WSS Username Token and enter the WLS admin user name and password.

    6. Enter Input Argumemt Host Id = SEBL_01.

    7. Click Test Web Service.

    You should see a successful initialization response message. For more information and troubleshooting steps, see Oracle Application Integration Architecture Process Integration Pack Utilities Guide, "Session Pool Manager".

16.6.1 Validating Security Policies

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:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control

  2. Navigate to WebLogic Domain, soa_domain, Web Services, Policies.

  3. Verify Service Policy attachment.

    1. Find the service policy in the list of policies.

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Service.

    4. Validate that all the composites are listed with local attachment to this service policy.

  4. Verify Client Policy attachment

    1. Navigate back to Policies screen and find the client policy

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Reference.

    4. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.

      Table 16-6 Service Policy Attachments for Product MDM Siebel CRM

      CompositeService Policy

      ReloadProcess

      oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON

      AIAB2BInterface

      oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON

      AIAErrorTaskAdministrationProcess

      oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON

      AIASessionPoolManager

      oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON


      Table 16-7 No Authentication Service Policy Attachments for Product MDM Siebel CRM

      CompositeService Policy

      SyncClassificationSchemeListSiebelProvABCSImpl

      oracle/no_authentication_client_policy

      SyncSpecificationValueSetListSiebelProvABCSImpl

      oracle/no_authentication_client_policy

      SyncBillOfMaterialsListSiebelProvABCSImpl

      oracle/no_authentication_client_policy

      SyncItemCompositionListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      SyncProductSiebelProvABCSImpl

      oracle/no_authentication_client_policy


      Table 16-8 Saml Opt On Client Policy Attachments for Product MDM Siebel CRM

      CompositeReferenceClient Policy

      AIAB2BInterface

      X12ProcessSalesOrderReqB2BCSImplService

      oracle/aia_wss10_saml_token_client_policy_OPT_ON

      AIAReadJMSNotificationProcess

      AIAErrorTaskAdministrationProcess

      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.

16.7 Undeploying Product MDM: Siebel CRM

To undeploy the integration from Fusion Middleware Server:

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

  2. Run the command for your platform.

    Table 16-9 Undeployment Command for Product MDM: Siebel CRM

    PlatformUndeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    sh $AIA_HOME/pips/MDMProductSiebel/DeploymentPlans/undeploySiebel.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME%\pips\MDMProductSiebel\DeploymentPlans\undeploySiebel.bat
    

  3. Restart the SOA server.

  4. Uninstall the integration following the instructions in Chapter 37, "Uninstalling Oracle AIA".

PKC?ذPKYc|BOEBPS/primaverap6ebs.htm Configuring and Deploying the Project Portfolio Management: Primavera P6 - EBS PIP

32 Configuring and Deploying the Project Portfolio Management: Primavera P6 - EBS PIP

This chapter discusses how to configure and deploy the Oracle Project Portfolio Management Integration Pack for Primavera P6 and Oracle E-Business Suite (Project Portfolio Management: Primavera P6 - EBS PIP).

This chapter includes the following sections:

32.1 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of the Project Portfolio Management: Primavera P6-EBS Projects PIP. Enter the details of the Project Portfolio Management: Primavera P6-EBS Projects PIP screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.

32.1.1 PIP Server Details Screen

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

Table 32-1 PIP Server Details Screen Fields

FieldDescription

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


32.1.2 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 32-2 Oracle E-Business Suite Server Details Screen Fields

FieldDescription

E-Business Suite Host Name

Specifies the fully qualified 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 ____________________________

E-Business suite version

This is the version of the E-Business Suite Application.


32.1.3 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 32-3 Oracle E-Business Suite Database Details Screen Fields

FieldDescription

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 User Name

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: server1.

Database Schema is __________________________________

Note: All the database credentials are used for creating the connection pool URL and data source URLs.


32.1.4 Primavera P6 Server Details Screen

Table 32-4 Primavera P6 Server Details Screen Fields

FieldDescription

P6 Webservice host url

This value is url of P6 Webservice host. Example: http://p6webservice.com

P6 Webservice host url is ____________________________

P6 Webservice port

This value is the P6 Webservice port. To find this value, contact your administrator. For example: 1521

P6 Webservice port is ______________________

Username

To find this value, contact your administrator.

Username is _____________________

Password

To find this value, contact your administrator.

Password is ___________________

Currency Code

This value is the currency code in which the P6 server is currently operating. To find this value, contact your administrator.

Currency Code is ______________________


32.2 Configuring and Deploying the Project Portfolio Management: Primavera P6-EBS Projects PIP

This section discusses the PIP configuration and deployment process. There are two steps:

  1. Configure your PIP using the deployment DCW.

  2. Deploy the PIP to the Fusion Middleware server.

32.2.1 Configuring the Project Portfolio Management: Primavera P6-EBS Projects PIP

The screens that appear prompt you to enter the data that is required for successful configuration of the Project Portfolio Management: Primavera P6-EBS Projects PIP. Keep the completed worksheets of the Project Portfolio Management: Primavera P6-EBS Projects PIP 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 Project Portfolio Management: Primavera P6-EBS Projects PIP:

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

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

  3. Restart the server.

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

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

  6. Click Next.

  7. Select the Project Portfolio Management: Primavera P6-EBS Projects PIP

  8. Click Next.

32.2.1.1 Specify PIP Server Details

To specify PIP Server details:

  1. Enter information related to your PIP server in the PIP Server Details screen.

  2. Click Next.

32.2.1.2 Specify Oracle E-Business Suite Server Details

To specify Oracle E-Business Suite Server details:

  1. Enter information about your Oracle E-Business Suite Server installation in the E-Business Suite Server Details screen.

  2. Click Next.

32.2.1.3 Specify Oracle E-Business Suite Database Details

To specify Oracle E-Business Suite Database details:

  1. Enter information about your Oracle E-Business Suite Database installation in the E-Business Suite Database Details screen.

  2. Click Next.

32.2.1.4 Specify the Primavera P6 Server Details

To specify Primavera P6 server details:

  1. Enter information about your Primavera P6 installation in the Primavera P6 Server Details screen.

  2. Click Next.

32.2.1.5 Complete Configuration

To complete configuration:

  1. 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 PIP. You can configure using the steps described in Section 32.2.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.


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

  3. When the configuration process completes without errors, the AIA DCW displays the Configuration Complete screen.

  4. Click Finish to close the DCW.

32.2.2 Configuring using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

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

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

32.2.3 Deploying the Project Portfolio Management: Primavera P6-EBS Projects PIP

To deploy the PIP to Fusion Middleware server:

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

  2. 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 undeployment command too.


    Table 32-5 Deployment Commands for the Project Portfolio Management: Primavera P6-EBS Projects PIP

    PlatformDeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems.

    HP-UX

    ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml 
    -DDeploymentPlan=<AIA_HOME>/pips/EbizToP6EPPM/DeploymentPlans/EbizToP6EPPMDP.xml 
    -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml 
    -DDeploymentPolicyFile=<AIA_HOME>/pips/EbizToP6EPPM/DeploymentPlans/EbizToP6EPPMConditionalPolicy.xml 
    -l <AIA_HOME>/pips/EbizToP6EPPM/DeploymentPlans/P6ToEbizEPPM.log
    

    Microsoft Windows

    ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml 
    -DDeploymentPlan=<AIA_HOME>\pips\EbizToP6EPPM\DeploymentPlans\EbizToP6EPPMDP.xml 
    -DPropertiesFile=<AIA_HOME>\aia_instances\<aia_instance>\config\AIAInstallProperties.xml 
    -DDeploymentPolicyFile=<AIA_HOME>\pips\EbizToP6EPPM\DeploymentPlans\EbizToP6EPPMConditionalPolicy.xml 
    -l <AIA_HOME>\pips\EbizToP6EPPM\DeploymentPlans\EbizToP6EPPM.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 PIPs are not displayed.


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

32.3 Verifying Deployment

To verify the Project Portfolio Management: Primavera P6-EBS Projects PIP deployment:

  1. 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 PIP is successfully installed.

    • For Microsoft Windows: Review the install log located at <AIA_HOME>\aia_instances\<instance name>\logs to verify that the PIP is successfully installed.

  2. Confirm that the Project Portfolio Management: Primavera P6-EBS Projects PIP components were successfully installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

    • GetOperatingUnitEbizAdapter

    • SyncProjectFinancialPlanListEbizAdapter

    • SyncProjectFinancialPlanListEbizProvABCSImpl

    • SyncProjectFinancialPlanListEbizReqABCSImpl

    • SyncProjectFinancialPlanListP6PPMProvABCSImpl

    • SyncProjectFinancialPlanListP6PPMReqABCSImpl

    • SyncProjectListEbizAdapter

    • SyncProjectListEbizProvABCSImpl

    • SyncProjectListEbizReqABCSImpl

    • SyncProjectListP6PPMProvABCSImpl

    • SyncProjectListP6PPMProvABCSImpl

    • SyncProjectResourceRateScheduleListEbizJMSConsumer

    • SyncProjectResourceRateScheduleListEbizJMSProducer

    • SyncProjectResourceRateScheduleListEbizReqABCSImpl

    • SyncProjectResourceRateScheduleListP6PPMProvABCSImpl

    • SyncProjectResourceSetListEbizJMSConsumer

    • SyncProjectResourceSetListEbizJMSProducer

    • SyncProjectResourceSetListEbizReqABCSImpl

    • SyncProjectResourceSetListP6PPMProvABCSImpl

32.3.1 Validating Security Policies

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 PIP have locally attached security policies.

To validate locally attached security policies:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

  2. Navigate to WebLogic Domain, soa_domain, Web Services, Policies.

  3. Verify Service Policy attachment.

    1. Find the service policy in the list of policies.

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Service.

    4. Validate that all the composites are listed with local attachment to this service policy.

  4. Verify Client Policy attachment

    1. Navigate back to Policies screen and find the client policy

    2. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Reference.

    4. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.

      Table 32-6 Service Policy Attachments for Project Portfolio Management: Primavera P6-EBS Projects PIP

      CompositeService Policy

      ProjectTemplateUtility

      oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON

      ProjectSplitter

      oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON


      Table 32-7 No Authentication Service Policy Attachments for Project Portfolio Management: Primavera P6-EBS Projects PIP

      CompositeService Policy

      SyncProjectResourceSetListEbizJMSProducer

      oracle/no_authentication_service_policy

      SyncProjectResourceRateScheduleListEbizJMSProducer

      oracle/no_authentication_service_policy

      SyncProjectListEbizJMSProducer

      oracle/no_authentication_service_policy

      SyncProjectFinancialPlanListEbizJMSProducer

      oracle/no_authentication_service_policy


      Table 32-8 Saml Opt On Client Policy Attachments for Project Portfolio Management: Primavera P6-EBS Projects PIP

      CompositeReferenceClient Policy

      ProjectTemplateUtility

      client

      oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON

      ProjectSplitter

      client

      oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON


      Table 32-9 No Authentication Client Policy Attachments for Project Portfolio Management: Primavera P6-EBS Projects PIP

      CompositeReferenceClient Policy

      SyncProjectListP6EPPMProvABCSImpl

      SyncService

      oracle/no_authentication_client_policy

      SyncProjectListP6EPPMProvABCSImpl

      EPSService

      oracle/no_authentication_client_policy

      SyncProjectListP6EPPMReqABCSImpl

      SyncService

      oracle/no_authentication_client_policy

      SyncProjectListP6EPPMReqABCSImpl

      UDFTypeService

      oracle/no_authentication_client_policy

      SyncProjLabExpendItemListP6EPPMReqABCSImpl

      TimesheetService

      oracle/no_authentication_client_policy

      SyncProjLabExpendItemListP6EPPMReqABCSImpl

      ActivityService

      oracle/no_authentication_client_policy

      SyncProjectResourceSetListP6EPPMProvABCSImpl

      ExpenseCategoryService

      oracle/no_authentication_client_policy

      SyncProjectResourceSetListP6EPPMProvABCSImpl

      UnitOfMeasureService

      oracle/no_authentication_client_policy

      SyncProjectResourceSetListP6EPPMProvABCSImpl

      WBSCategoryService

      oracle/no_authentication_client_policy

      SyncProjectResourceSetListP6EPPMProvABCSImpl

      RoleService

      oracle/no_authentication_client_policy

      SyncProjectResourceSetListP6EPPMProvABCSImpl

      ResourceRateService

      oracle/no_authentication_client_policy

      SyncProjectResourceSetListP6EPPMProvABCSImpl

      ResourceService

      oracle/no_authentication_client_policy

      SyncProjectResourceRateScheduleListP6EPPMProvABCSImpl

      ResourceRateService

      oracle/no_authentication_client_policy

      SyncProjectResourceRateScheduleListP6EPPMProvABCSImpl

      RoleRateService

      oracle/no_authentication_client_policy

      SyncResourceAvailabilityCalendarListP6EPPMProvABCSImpl

      CalendarService

      oracle/no_authentication_client_policy

      ProjectTemplateUtility

      UDFValueService

      oracle/no_authentication_client_policy

      ProjectTemplateUtility

      SyncService

      oracle/no_authentication_client_policy

      ProjectTemplateUtility

      ProjectCodeAssignmentService

      oracle/no_authentication_client_policy

      ProjectTemplateUtility

      ProjectCodeTypeService

      oracle/no_authentication_client_policy

      ProjectTemplateUtility

      UDFTypeService

      oracle/no_authentication_client_policy

      ProjectTemplateUtility

      ProjectCodeService

      oracle/no_authentication_client_policy


For more information about security validation, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Working with Security."

For PIP implementation, see Oracle Project Portfolio Management Integration Pack for Primavera P6 and Oracle E-Business Suite Implementation Guide.

32.4 Undeploying the Project Portfolio Management: Primavera P6 - EBS PIP

To undeploy the PIP from Fusion Middleware Server:

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

  2. Run the command for your platform.

    Table 32-10 Undeployment Command for the Project Portfolio Management: Primavera P6 - EBS PIP

    PlatformUndeployment Command

    Linux

    Solaris SPARC

    IBM AIX Based Systems.

    HP-UX

    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/EbizToP6EPPM/DeploymentPlans/EbizToP6EPPMUndeployDP.xml 
    -l <AIA_HOME>/pips/EbizToP6EPPM/DeploymentPlans/EbizToP6EPPMUndeployDP.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\EbizToP6EPPM\DeploymentPlans\EbizToP6EPPMUndeployDP.xml 
    -l <AIA_HOME>\pips\EbizToP6EPPM\DeploymentPlans\EbizToP6EPPMUndeployDP.log
    

  3. Restart the SOA server.

  4. Uninstall the PIP following the instructions in Chapter 37, "Uninstalling Oracle AIA".

PK_T}sPKYc|BOEBPS/commsordertocashcrm.htm Configuring and Deploying the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration

6 Configuring and Deploying the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration

This chapter discusses how to configure and deploy the Oracle Communications Order to Cash Integration Pack for Siebel Customer Relationship Management, Oracle Communications Order and Service Management, and Oracle Communications Billing and Revenue Management (Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration).

This chapter includes the following sections:

6.1 Deployment Configuration Wizard

The DCW screens prompt you to enter the data required for successful configuration of the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration. Enter the details of the Comms Order to Cash: SBL CRM, OSM, and BRM 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.

6.1.1 Integration Server Details Screen

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

Table 6-1 Integration Server Details Screen Fields

FieldDescription

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: server1.company.com.

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


6.1.2 Siebel CRM Server Details Screen

Use this screen to enter details related to your Siebel CRM server instance. The screen contains the following fields:

Table 6-2 Siebel CRM Server Details Screen Fields

FieldDescription

Siebel Host name

This is a computer name of the Siebel host. For example: example1.corp.siebel.com. To find the value, contact your administrator.

Siebel Host name is _____________________________

Siebel HTTP Port

This value is the Siebel application port. For example: 80. To find the value, contact your administrator.

Siebel HTTP Port is ________________________________

InternetProtocol

This value is the Siebel host internet protocol. For example, http://. To find the value, contact your administrator.

InternetProtocol is _______________________

Note: Our internal environments are always on http://. The default value is https// and must be changed for Siebel web services and Session Pool Manager services to work.

Siebel Enterprise Server Name

This value is the Siebel enterprise server name. For example, siebel. To find the value, contact your administrator.

Siebel Enterprise Server Name is _________________________

Note: This value must be in lowercase (siebel) for the Update Account flow to work.

Siebel EAI Application User

The Siebel application user is used for making EAI web service calls. For example: sadmin. To find the value, contact your administrator.

Siebel EAI Application User is ___________________________

Siebel EAI Application Password

This is the password for the EAI user. For example: sadmin. To find the value, contact your administrator.

Siebel EAI Application Password is ________________________

Siebel Version

Version of application, for example Siebel 8.1.1 SIA.

Siebel Version is __________________________

Siebel Language

This is the language used by the Siebel application. For example, enu. To find the value, contact your administrator.

Siebel Language is _______________________


6.1.3 Siebel CRM Database Details Screen

Use this screen to enter details related to your Siebel CRM database instance. The screen contains the following fields:

Table 6-3 Siebel CRM Database Details Screen Fields

FieldDescription

Siebel Database Host

This value is typically the computer name. To find the value, contact your database administrator.

Siebel Database Host is _________________________________

Siebel Database Port

This is the Siebel database port. For example: 1521. To find the value, contact your database administrator.

Siebel Database Port is _________________________________

Siebel Database SID

This is the Siebel database system ID. For example: qa7a. To find the value, contact your database administrator.

Siebel Database SID is ________________________________

Siebel Database Username

Specifies a database user that has access to loading the EIM tables Siebel. To find this value, contact the database administrator. Example: ora12345

Siebel Database Username is ______________________

Siebel Database Password

This is the Siebel Database Password. For example: ora07103. To find the value, contact your database administrator.

Siebel Database Password is _____________________


6.1.4 Oracle Communications BRM Screen

Use this screen to enter details related to your Oracle Communications BRM instance. The screen contains the following fields:

Table 6-4 Oracle Communications BRM Details Screen Fields

FieldDescription

Primary CM Host Name

This is the host name of the primary Connection Manager (CM) of the BRM server. For example: example1.portal.com To find this value, contact your Oracle AQ system administrator.

Primary CM Host Name is ______________________________

Primary CM Port Number

This is the port number of primary Connection Manager (CM) of the BRM server. For example: 12600. To find this value contact your Oracle AQ database administrator System Administrator

Primary CM Port Number is ______________________________

Database Host

This is the database host name of the Oracle AQ for which the BRM DM_AQ is configured. For example: example2.portal.com. To find this value, contact your Oracle AQ database administrator

Database Host is _______________________

Database Port

This is the database port number of the Oracle AQ. For example: 1521. To find this value, contact your Oracle AQ database administrator.

Database Port is _________________________

Oracle AQ Database SID

This is the database instance of the Oracle AQ. For example: orcl. To find this value, contact your Oracle AQ database administrator.

Oracle AQ Database SID is _______________________________

Oracle AQ Username

This is the database user name of the Oracle AQ. For example, PIN7820. To find this value, contact your Oracle AQ database administrator.

Oracle AQ Username is _________________________

Note: This value must be in uppercase (PIN7820) for the OOTB PLM flow to work.

Oracle AQ Password

This is the database password of the Oracle AQ. To find this value, contact your Oracle AQ database administrator.

Oracle AQ Password is ___________________________

AQ Queue Name

This is the queue name configured for the BRM DM_AQ. For example: AqportalUser. To find this value, contact your Oracle AQ database administrator.

AQ Queue Name is _________________________________


6.1.5 Oracle OSM Server Details Screen

Use this screen to enter details related to your Oracle OSM server instance. The screen contains the following fields:

Table 6-5 Oracle OSM Server Details Screen Fields

FieldDescription

OSM CFS Admin Username

This is the OSM admin user name used to connect to the OSM server. For example, osm. To find this value, contact your Oracle OSM administrator.

OSM CFS Admin Username is _______________________________

OSM CFS Admin Password

This is the OSM admin password used to connect to the OSM server. For example, osmadmin. To find this value, contact your Oracle OSM administrator.

OSM CFS Admin Password is _________________________

OSM Provisioning Admin Username

This is the admin user used to connect to the OSM Provisioning server. For example, osm. To find this value, contact your OSM administrator.

OSM Provisioning Admin Username is ___________________________

OSM Provisioning Admin Password

This is the admin password used to connect to the OSM Provisioning server. For example, osmadmin. To find this value, contact your OSm administrator.

OSM Provisioning Admin Password is ___________________________

OSM CFS WL JMS Queue Access Host

This is the Weblogic host name for accessing inbound JMS queues for OSM CFS. To find this value, contact your administrator.

OSM CFS WL JMS Queue Access Host is ______________________________

OSM CFS WL JMS Queue Access Port

This is the Weblogic port number for accessing inbound JMS queues for OSM CFS. For example, 7080. To find this value, contact your administrator.

OSM CFS WL JMS Queue Access Port is ______________________________

OSM CFS WL JMS Queue Access Username

This is the Weblogic user name for accessing inbound JMS queues for OSM CFS. For example, weblogic. To find this value, contact your administrator.

OSM CFS WL JMS Queue Access Username is _______________________

OSM CFS WL JMS Queue Access Password

This is the Weblogic password for accessing inbound JMS queues for OSM CFS. For example, weblogic1. To find this value, contact your administrator.

OSM CFS WL JMS Queue Access Password is _______________________

OSM Provisioning WL JMS Queue Access Host

This is the Weblogic host used for accessing inbound JMS queues for OSM Provisioning. To find this value, contact your Oracle OSM administrator.

OSM Provisioning WL JMS Queue Access Host is ___________________________

OSM Provisioning WL JMS Queue Access Port

This is the Weblogic port number used for accessing inbound JMS queues for OSM Provisioning. For example, 7080. To find this value, contact your Oracle OSM administrator.

OSM Provisioning WL JMS Queue Access Port is ___________________________

OSM Provisioning WL JMS Queue Access Username

This is the Weblogic user name for accessing inbound JMS queues for OSM Provisioning. For example, weblogic. To find this value, contact your Oracle OSM administrator.

OSM Provisioning WL JMS Queue Access Username is ___________________________

OSM Provisioning WL JMS Queue Access Password

This is the Weblogic password for accessing inbound JMS queues for OSM Provisioning. For example, weblogic1. To find this value, contact your Oracle OSM administrator.

OSM Provisioning WL JMS Queue Access Password is ___________________________


6.1.6 Session Pool Manager Details Screen

The Session Pool Manager (SPM) details are optional and required only when your Siebel server is outside of the firewall. If all your servers are within the network, leave these fields blank.

In the java.net application programming interface (API) used by SPM, proxies are supported through two system properties: http.proxyHost and http.proxyPort. They must be set to the proxy server and port respectively. This value is only set when ProxySettings_Enabled is set to TRUE.

Table 6-6 Session Pool Manager Details Screen Fields

FieldDescription

Proxy host url

This determines the server to be set in the system properties for http.proxyHost property.

Proxy host url is ___________________________

Proxy port

This determines the port to be set in the system properties for the http.proxyPort property.

Proxy port is ______________________________



Note:

These fields are optional so leave the values blank. These values are required only if the Siebel server is outside of the firewall.


6.2 Performing Predeployment Configurations

This section discusses predeployment configurations for the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration.

6.2.1 Configuring the Timeout Values

This section describes how to modify the JTA Transaction Value and the SyncMaxWaitTime values.

To modify JTA Transaction Value:

  1. Log in to the WebLogic Server console.

  2. Navigate to Services JTA.

  3. Change the value of the property Timeout Seconds to 3600.

  4. Click Save and activate the changes.

To modify SyncMaxWaitTime values:

  1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

  2. Expand the SOA folder and right-click soa-infra.

  3. Select SOA Administration, BPEL Properties.

  4. Click the More BPEL Configuration Properties link.

  5. Change the value of syncMaxWaitTime to 120.

  6. Click Apply.

6.3 Configuring and Deploying the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration

This section discusses the integration configuration and deployment process. There are two steps:

  1. Configure your integration using the DCW.

  2. Deploy the integration to the Fusion Middleware server.

6.3.1 Configuring the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration

The screens that appear prompt you to enter the data that is required for successful configuration of the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration. Keep the completed worksheets of the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration screens ready before you launch the DCW.

To configure the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration:


Note:

If you are harvesting content to Oracle Enterprise Repository (OER), perform the first three steps. Else start from step 4.


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

  2. Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".

  3. Restart the server.

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

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

  6. Click Next.

  7. Expand Communications Pre-built Integrations and select Comms Order to Cash: SBL CRM, OSM, and BRM.

  8. Click Next.

6.3.1.1 Specify Integration Server Details

To specify Integration Server details:

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

  2. Click Next.

6.3.1.2 Specify Siebel CRM Server Details

To specify Siebel CRM server details:

  1. Enter information about your Siebel CRM application in the Application Details - Siebel CRM screen.

  2. Click Next.

6.3.1.3 Specify Siebel CRM Database Details

To specify Siebel CRM database details:

  1. Enter information about your Siebel CRM database in the Siebel CRM Database Details screen.

  2. Click Next.

6.3.1.4 Specify Oracle Communications BRM Details

To specify Oracle Communications BRM details:

  1. Enter Oracle Communications BRM information in the Oracle Communications BRM screen.

  2. Click Next.

6.3.1.5 Specify Oracle OSM Server Details

To specify Oracle OSM server details:

  1. Enter Oracle OSM server information in the Oracle OSM Server Details screen.

  2. Click Next.

6.3.1.6 Complete Configuration

To complete configuration:

  1. 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 6.3.2, "Configuring Using the Response File". Click Save Response File and save the response file with the name and location of your choice.


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

  3. When configuration process finishes without errors, the AIA DCW displays the Configuration Complete screen.

  4. Click Finish to close the DCW.

6.3.2 Configuring Using the Response File

To configure using the response file:

  1. Open the response file.

    When you create a response file through OUI, passwords get stored as <SECURE>.

  2. Replace the password fields with actual passwords in the response file.

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

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

6.3.3 Deploying the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration

To deploy the integration to Fusion Middleware server:

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

  2. 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 6-7 Deployment Commands for the Comms Order to Cash for Siebel CRM, OSM and BRM

    PlatformDeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    $AIA_HOME/pips/Communications/O2C/DeploymentPlans/deployO2C.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME%\pips\Communications\O2C\DeploymentPlans\deployO2C.bat
    

  3. Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/O2CDP_Deployments_YYYY-MM-DD_HH-MI-SS.log to verify successful deployment of the integration.

Oracle AIA ships a few artifacts in AIA Lifecycle Workbench which can be used in your integrations. These native artifacts created using FMW technologies such as BPEL, Mediator are natively supported by AIA Foundation Pack tools such as Project Lifecycle Workbench, Harvester, Deployment Generator, and AIA Installer Driver (AID). These artifacts include SOA artifact types such as composites, DataSources, DVM, xRef, and so on. These can be modified or new natively supported artifacts can be added using AIA Lifecycle Workbench and a BOM.xml file can be generated.

Integrations, most often, also require deployment of artifact types that are beyond what is supported by the Project Lifecycle Workbench and AIA Harvester. For instance, you may want to deploy artifacts such as Java applications, Shell Scripts, ANT based build scripts which constitute part of integration landscape in addition to the artifacts that are delivered by AIA. AIA also supports deployment of these supplementary artifacts. However, you must modify and add new non native artifacts outside AIA Lifecycle Workbench.

For more information on deploying artifacts, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Generating Deployment Plans and Deploying Artifacts".

6.4 Performing Postdeployment Configurations

This section discusses post deployment configuration for Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration. This section includes:

6.4.1 Adding Singleton property to ProcessFulfillmentOrderBillingAccountListOSMCFSCommsJMSConsumer Service

  1. Log in to the Oracle Enterprise Manager console of the Oracle AIA cluster.

  2. Navigate to the SOA composite: ProcessFulfillmentOrderBillingAccountListOSMCFSCommsJMSConsumer

    • In the left-side navigation tree, expand SOA > soa-infra (soa_server1) in the navigator.

    • Expand the partition: default.

  3. Select the SOA Composite : ProcessFulfillmentOrderBillingAccountListOSMCFSCommsJMSConsumer

  4. From the SOA Composite menu, select Services/Reference Properties.

  5. Select Consume_PFOBAL service. Click Properties tab. Click Add to add a new property.

  6. Click Search and select Singleton from the Property Names pop-up window. In the Value column, enter true.

  7. Click Apply.

6.4.2 Suppressing Auto-Retry and Preventing Multiple Error Notifications and Trouble Tickets

To suppress auto-retry and prevent multiple error notifications and trouble tickets:

  1. Set the GlobalTxMaxRetry property for outbound adapters:

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

    2. Expand the SOA folder, right-click soa_infra.

    3. Select SOA Administration, Common Properties.

    4. Click More SOA Infra Advanced Configuration Properties.

    5. Search for the GlobalTxMaxRetry property and set the value as 0 (zero).

  2. Set the GlobalInboundJcaRetryCount property for inbound adapters:

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

    2. Expand the SOA folder, right-click soa_infra.

    3. Select Administration, System Mbean Browser.

    4. Expand oracle.as.soainfra.config, <Server>, AdapterConfig.

    5. Select Adapter.

    6. Search for the GlobalInboundJcaRetryCount property and set the value as 0 (zero).

  3. Change Audit Level from Development to Production for soa infrastructure:

    1. Log in to the Oracle Enterprise Manager Fusion Middleware Control.

    2. Expand the SOA folder, right-click soa_infra.

    3. Select SOA Administration, Common Properties.

    4. Choose Production from the Audit Level list.

    5. Click Apply.

  4. Stop and Start the SOA and Admin Server so that your changes can take effect.

6.4.3 Supporting Message Priority

As part of supporting message priority, follow the below steps to configure the queues (AIA_CRTBO_OUT_JMSQ, AIA_CRTCUST_OUT_JMS, AIA_CRTFO_OUT_JMSQ, AIA_FOPROV_OUT_JMSQ) so that the message is prioritized based on JMSPriority.

  1. Creating Destination Sort Key based on JMSPriority

    1. Log in to <httphost>:<httpport>/console.

    2. Navigate to Services, Messaging, JMS Modules.

    3. Click AIAJMSModule.

    4. Click New and select Destination Sort Key option.

    5. Click Next.

    6. Give a name AIA_SALESORDERJMSPRIORITY_KEY, click OK. The key is created.

    7. Click AIA_SALESORDERJMSPRIORITY_KEY link and choose JMSPriority from the Sort Key list.

    8. Select Key Type as Int.

    9. Select Direction as Descending.

    10. Click Save.

  2. Attaching Destination Sort Key to JMS Queues

    1. Click AIAJMSModule.

    2. Click AIA_CRTBO_OUT_JMSQ.

    3. In Destination Keys section, newly created Key is displayed. Select and choose the key.

    4. Click Save.

  3. Repeat steps 2a to 2d for the following queues:

    • AIA_CRTCUST_OUT_JMSQ

    • AIA_CRTFO_OUT_JMSQ

    • AIA_FOPROV_OUT_JMSQ

6.4.4 Updating Internal ID for the BRM Instance BRM_01

To update the internal ID for the BRM instance BRM_01 in the AIA Application Registry in the AIA application perform the following steps:

  1. Find the BRM instance ID that is specified in BRM Payload Configuration file:

    1. Go to the file system where your BRM portal is installed.

    2. Navigate to folder ../portal/7.4/sys/eai_js.

    3. Find the payload configuration file payloadconfig_crm_sync.xml.

    4. Open the file. The instance Id is specified as shown in Example 6-1.

    Example 6-1 Instance ID Specified in the BRM Payload Configuration File

    <ProductInfoChange Source="EVENT" Tag="ProductInfoChange"
                                StartEvent="/event/notification/price/products/modify">
              <Attribute Tag="InstanceId" Value="Portal"/>
              <Attribute Tag="xmlns" Value="http://www.portal.com/schemas/CRMSync"/>
              <Attribute Tag="xmlns:xsi" Value="http://www.w3.org/2001/XMLSchema-instance"/>
              <Attribute Tag="xsi:schemaLocation" Value="http://www.portal.com/schemas/CRMSync/ProductInfoChange.xsd"/>
              <Field PinFld="PIN_FLD_ACCOUNT_OBJ" Tag="AccountObj"/>
              <SubElement Name="ProductInfo" OnEvent="/event/notification/price/products/modify" />
    </ProductInfoChange>
    

    If it is Portal, this value appears as brmproductabo:InstanceId in the Product Event message from BRM. See Example 6-2.

    Example 6-2 BRM Instance ID Specified in the Message Payload

    <SyncProductReqMsg>
    <part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    name="SyncProduct">
    <brmproductabo:ProductInfoChange
    xmlns:brmproductabo="http://www.portal.com/schemas/CRMSync"
    brmproductabo:InstanceId="Portal">
    
  2. Update the Internal ID column to the Instance ID from BRM to the value above. For example: Portal.

  3. In AIA Application, go to AIA Application Registry, Setup, System and find the entry for System Code "BRM_01".

  4. Change that value to the InstanceId from the BRM Payload Configuration file. For example: Portal.

6.4.5 Adding Security Policy to the QueryProductClassAndAttributesSCECommsReqABCSImpl Service

Add the following security policy to have the Product Class SCE flow working from the OSM Design Studio.


Note:

This step is only required if you are using OSM 7.0.2 version.


To add the security policy:

  1. Log in to the Oracle Enterprise Manager Fusion Middleware Control (http://<host>:<port>/em).

  2. Select the service QueryProductClassAndAttributesSCECommsReqABCSImpl.

  3. Scroll down to the Services and References section and select the QueryProductClassAndAttributesSCECommsReqABCSImpl link.

  4. Go to the Policies tab.

  5. Go to the Directly Attached Policies section and click Attach/Detach.

  6. Select oracle/no_authentication_service_policy and click Attach.

  7. Click OK.

  8. Verify that oracle/no_authentication_service_policy is attached.

6.4.6 Setting up the AIA FMW Server


Note:

This step is required if cluster is the deployment topology.


Perform the following steps to enable tunneling:

  1. Configure http proxy host

    1. Modify mod_wl_ohs.conf

      For example, scratch/nmankodi/Oracle/Middleware/Oracle_WT1/instances/instance1/config/OHS/ohs1/mod_wl_ohs.conf

    2. Add the following location:

      <Location / bea_wls_internal >

      SetHandler weblogic-handler

      WebLogicCluster adc1140309.com:8001,adc2101063.com:8011

      WLLogFile /tmp/web_log.log

      </Location>

    3. Restart using ./opmnctl stopall, ./opmnctl startall

  2. Configure WebLogic Server

    1. Log in to the WebLogic Server Console.

    2. Click Admin and each manager server.

    3. Click Protocols, HTTP, Enable Tunneling.

    4. Save the configuration.

    5. Restart Admin and managed servers.

  3. Configure SAF Remote Context if OSM is clustered

    1. Navigate to console <host>:<port>/console.

    2. Navigate to Home, JMS Modules, AIAJMSModule, OSM (SAF Remote Context).

    3. Select Lock and Edit: update the URL to include all the OSM clustered nodes.

      For example, t3://coqalv0045.example.com:7070,coqalv0046.example.com:8070.

    4. Save and Release the configuration.

  4. Configure SOM SAF Remote Context if OSM Provisioning system is clustered

    1. Navigate to console <host>:<port>/console.

    2. Navigate to Home, JMS Modules, AIAJMSModule, SOM (SAF Remote Context).

    3. Select Lock and Edit: update the URL to include all the OSM clustered nodes.

      For example, t3://coqalv0045.example.com:7070,coqalv0046.example.com:8070.

    4. Save and Release the configuration.

6.5 Verifying Deployment

To verify the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration Deployment:

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

  2. Confirm that the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration components are successfully installed.

    1. Navigate to the Oracle Enterprise Manager Fusion Middleware Control: (http://<server name>:<port number>/em/).

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Expand Farm_soa_domain, SOA, soa-infra, Default and look for the following items:

    • AIACOMOrderFalloutNotificationJMSConsumer

    • AIAOrderFalloutJMSBridgeService

    • Comms2CoreCustomerPartybridge

    • CommsProcessBillingAccountListEBF

    • CommsProcessFulfillmentOrderBillingAccountListEBF

    • CommunicationsBillingEBSV1

    • CommunicationsBillingResponseEBSV1

    • CommunicationsClassificationEBSV1

    • CommunicationsCustomerPartyEBSV2

    • CommunicationsCustomerPartyEBSV2Resequencer

    • CommunicationsCustomerPartyResponseEBSV2

    • CommunicationsFulfillmentOrderEBSV1

    • CommunicationsInstalledProductEBSV2

    • CommunicationsItemCompositionEBSV1

    • CommunicationsItemCompositionResponseEBSV1

    • CommunicationsPriceListEBSV2

    • CommunicationsPriceListResponseEBSV2

    • CommunicationsProvisioningOrderEBSV1

    • CommunicationsSalesOrderEBSV2

    • CommunicationsSpecificationValueSetEBSV1

    • CommunicationsTroubleTicketEBSV1

    • CommunicationsTroubleTicketResponseEBSV1

    • Core2CommsCustomerPartyBridge

    • CreateFaultNotificationLFCommsJMSConsumer

    • CreateOrderFalloutNotificationOSMCFSCommsJMSConsumer

    • CreateOrderFalloutNotificationOSMCFSCommsJMSProducer

    • CreateOrderFalloutNotificationOSMCFSCommsProvImpl

    • CreateTroubleTicketAIACommsReqImpl

    • CreateTroubleTicketOSMCFSCommsJMSConsumer

    • CreateTroubleTicketRespOSMCFSCommsJMSProducer

    • CreateTroubleTicketSiebelCommsProvABCSImpl

    • CustomerPartyEBSV2

    • ProcessFOBillingAccountListRespOSMCFSCommsJMSProducer

    • ProcessFulfillmentOrderBillingAccountListOSMCFSCommsJMSConsumer

    • ProcessFulfillmentOrderBillingBRMCommsAddSubProcess

    • ProcessFulfillmentOrderBillingBRMCommsDeleteSubProcess

    • ProcessFulfillmentOrderBillingBRMCommsMoveAddSubProcess

    • ProcessFulfillmentOrderBillingBRMCommsProvABCSImpl

    • ProcessFulfillmentOrderBillingBRMCommsSuspendResumeSubProcess

    • ProcessFulfillmentOrderBillingBRMCommsUpdateSubProcess

    • ProcessFulfillmentOrderBillingOSMCFSCommsJMSConsumer

    • ProcessFulfillmentOrderBillingResponseOSMCFSCommsJMSProducer

    • ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer

    • ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer

    • ProcessInstalledProductSpecialRatingSetListBRMCommsProvABCSImpl

    • ProcessInstalledProductSpecialRatingSetListSiebelCommsJMSConsumer

    • ProcessInstalledProductSpecialRatingSetListSiebelCommsReqABCSImpl

    • ProcessProvisioningOrderOSMCFSCommsJMSConsumer

    • ProcessProvisioningOrderOSMPROVCommsJMSProducer

    • ProcessSalesOrderFulfillmentOSMCFSCommsJMSProducer

    • ProcessSalesOrderFulfillmentSiebelCommsJMSConsumer

    • ProcessSalesOrderFulfillmentSiebelCommsReqABCSImpl

    • ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl

    • QueryClassificationListSiebelCommsProvABCSImpl

    • QueryCustomerPartyListSiebelProvABCSImplV2

    • QueryProductClassAndAttributesSCECommsReqABCSImpl

    • QuerySpecificationListSiebelCommsProvABCSImpl

    • QuerySpecificationValueSetListSiebelCommsProvABCSImpl

    • SyncAccountSiebelAggregatorAdapter

    • SyncAccountSiebelReqABCSImpl

    • SyncAcctSiebelAggrEventConsumer

    • SyncAddressSiebelAggregatorAdapter

    • SyncBPSiebelAggregatorAdapter

    • SyncContactSiebelAggregatorAdapter

    • SyncCustomerPartyListBRM_01CommsJMSConsumer

    • SyncCustomerPartyListBRMCommsJMSProducer

    • SyncCustomerPartyListBRMCommsProvABCSImpl

    • SyncCustomerSiebelEventAggregator

    • SyncDiscountBRMCommsReqABCSImpl

    • SyncDiscountInfoChangeBRMAQ

    • SyncItemCompositionListSiebelCommsProvABCSImpl

    • SyncProductBRMCommsReqABCSImpl

    • SyncProductInfoChangeBRMAQ

    • TransformAppContextSiebelService

    • UpdateSalesOrderOSMCFSCommsJMSConsumer

    • UpdateSalesOrderSiebelCommsProvABCSImpl

    • UpdateTroubleTicketOSMCFSCommsJMSConsumer

    • UpdateTroubleTicketSiebelCommsProvABCSImpl

6.5.1 Validating Security Policies

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:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control

  2. Expand WebLogic Domain.

  3. Select soa_domain.

  4. Right-click soa_domain.

  5. Select Web Services, Policies.

  6. Verify Service Policy attachment.

    1. Find no_authentication_service_policy in the list of policies.

    2. Click the number in Attachment Co^#unt column.

      This opens Usage Analysis screen.

    3. Change the Subject Type list box to SOA Service.

    4. Validate that all the composites are listed with local attachment to this service policy.

  7. Verify Client Policy attachment

    1. Navigate back to Web Services Policies screen.

    2. Navigate to Applies To LOV, select Service Clients and hit enter. Find no_authentication_client_policy.

    3. Click the number in Attachment Count column.

      This opens Usage Analysis screen.

    4. Change the Subject Type list box to SOA Reference.

    5. Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.

      Table 6-8 No Authentication Service Policy Attachments for Comms Order to Cash: SBL CRM, BRM, and OSM

      CompositeService Policy

      SyncCustomerSiebelEventAggregator

      oracle/no_authentication_service_policy


      Table 6-9 No Authentication Client Policy Attachments for Comms Order to Cash: SBL CRM, BRM, and OSM

      CompositeClient Policy

      SyncAccountSiebelReqABCSImpl

      oracle/no_authentication_client_policy

      QuerySpecificationListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      QuerySpecificationValueSetListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      UpdateTroubleTicketSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      SyncItemCompositionListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      UpdateSalesOrderSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      CreateTroubleTicketSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy

      QueryCustomerPartyListSiebelProvABCSImplV2

      oracle/no_authentication_client_policy

      QueryClassificationListSiebelCommsProvABCSImpl

      oracle/no_authentication_client_policy


For integration implementation, see Oracle Application Integration Architecture Oracle Communication Order to Cash Integration Pack Implementation Guide for Siebel CRM, Oracle Order and Service Management, and Oracle Billing and Revenue Management.

Also see Oracle Application Integration Architecture Siebel CRM Integration Pack for Oracle Communications Billing and Revenue Management: Agent Assisted Billing Care Implementation Guide.

6.6 Undeploying the Comms Order to Cash: SBL CRM, OSM, and BRM Pre-Built Integration

To undeploy the integration from Fusion Middleware Server:

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

  2. Run the command for your platform.

    Table 6-10 Undeployment Command for the Comms Order to Cash: SBL CRM, OSM, and BRM

    PlatformUndeployment Command

    Linux x86

    Solaris SPARC (64-bit)

    IBM AIX Based Systems (64-bit).

    HP-UX 11i (64 bit)

    $AIA_HOME/pips/Communications/O2C/DeploymentPlans/undeployO2C.sh
    

    Microsoft Windows (32-bit)

    %AIA_HOME%\pips\Communications\O2C\DeploymentPlans\undeployO2C.bat
    

  3. Restart the SOA server.

  4. Uninstall the integration following the instructions in the Chapter 37, "Uninstalling Oracle AIA"

PK3m#^#PKYc|BOEBPS/img/installerg.pngPNG  IHDRSD, pHYs+ IDATx_hW^p p d\`$ `,D& c3Nf 306)&D30A`6D1i?ڐ6P :nUu_,ٱ!8UG{Ϲ-kZQg_Fh4g1u.-0󹷧G?5Fh4;;lsL(8vz#Nh4槎܀%;R7/ח"I˿><`SFh4&ק,`u(R_5h4FلʹKչקk5icjFh4$ټH۩ ,WkrFh46(Z۩[nBl2ߜW4[qw9?eW¥M ToɅw/b Xq&U{V5i]lԣ}_v=[:{mNly;rh3_ l_x TYd,QwL 5X.U"L(br;7ѳ_ `[ gpF`3Q1cyM] dߟb}!K3ĽzԐgJ=+ˉ#Goүy;ω?~x] X~ҷl7Lp-\:3G#07CyVׅrm:wu!_ jk-|=/]2wo]gDK|5}zP[7pw?۹\ֶϮ728oVO0J0wNw?!C~+ ={O>AŸFu W/`[>R/uRo=tN7簸\ֶON vlP2̼3ug4<*ūn58"|?M/;q/tW\ MMƑm%Ǐ8spi4}d=?-ГS_|~ͣ"%,]_¶ȴe-VL\Qx QtuA}91mޅ,~Q8KK3#ۚ:|ϩjky_&{x8uF_oZcck?-c6_ɖƟʗNl[6{;`\vS %ۂp(9.j g΋XMfrD;2ͨ"5#p/qàho%oƟ\\lL<DZi6 ,5ĶgZ-ky(~?,- ȯfߣ>Uލh P_~@g`EJaJ,۷r4Ah3r%q/*.rƅ^Foc4^h YVE3C׬|SZ*8 z~kaalgx; aχA >ߞްGubxLS+Ծ#ݛ7Lg_=e۫' [6X/NǞ-^Q>S|ݟ<~e@8RX1^.\Ͻ~evҾvOU_adԣFh]x񱣌3O^/xzVS/3~%~Ϸ;Z}3?wtVC Xq%wKUڙW&!g20hx,N, ia/&q=P/{^Z:8qwE2-u&n퇶ytK(>uN٭grhCg;=b4~<Ʌ3§^t6aA8~g Z1o/U럦`p>?)<oKq@澑MK`ֶ\_^kۋjvtbu;9߆^)v$Q>yI-}VUk^{l 0 :ښ|&OxG˜pڻ1 1Amc -B7H>Y,κ][k };ʍB6ݷ6cT^,# ` q`,=+VMggyL=-`i:iu}7#u C5qjnBcu;7vn";Du뼶_cblŶ1l DG%qߚ81ꯇ'~VL%t:ΗOi{Dg8_.s#ʹpQsan.1g_~۴ޚ74s/@#Ռ RIHx{[F~n^18lJW,鶑.oYP} M9A0}fş tZ-ζ1T-^n9 reYPc4d:;e욬h-Q)/]o oYWwޑ^/אsm|rتGh-A.v]Vgu]DC_IBn|2xGM+\[^9n%ڂ{\۩ Q׌]~-Mc읯T^LrxlXA~۟eW!BqY ro{R5 -ҡA֒{\ۯ(lVt~B~kUr@yWg4p9Ws'&;ͨE#.n3x_W B,\@pwOLn^.+Su˯cu5Fh9A} `׃FGx>~Wh4 ]M}~CEFh4? @`?qǢh4FylhOh4YA[~Fh4 h4FyVPn`yiFh4͏rK-?Gh4FHXbi2Y~FӣF p޺h4F}~E 9^KJ2\#]NXB%"$ywmu0c&,t'3˰oD#'j ℡Ɩ0@ zY.Jψ(] 0I( RJ5)gZ:wNyΰFd-ɆE,B a0H6$7@EDd`fnpQ ]ՅlHIȡ=d~x뗏7=lk24ͳ R@pj`)2C RL]B% +c("LGySdPj# LyG8AR0 H:{?`d*!29RvF$7$ i^DZBUU_󣻑*Y"eZ\bB%"Marclzs=EC}[{^Fh4gh4 (ITW4Vfѽc CFln&T/ @#T`T]5̝5$Q4)!(a6 H@PjE^'׬0s: nA jD#glr#2cq8ÎۚCr%[ ڍႌL5@R A !/j4XɻMiq?ɭe|Hh4PU1 . P{c)TǂPjlKoX*Ifj-a3 -Nk/oD 4Ȋ hT{l_ 2 * !Fgȉ6",YmSc%Q~Σ._E"*?WP^w+,s;X'ؐ `*QčldzOb Q5ګh4F}~YfkO0RvE@!E*J! "c~ "RY6s쁘Y23ƶb 3wF, i(aSE>`=n 4 LqR ;A !p0.FWlARʯy-SPRCr( q"KvQC04ǖᴚIى4ͳUH2 sm̞pEnK@߻ʪC Z.{Karad``_DR:{|䜀<8 Yc n̬qqVou"X ݓ22cG$r,8|zEhOrk;87ҿM@HycZh4FyV>?Fr2*d.Ȋ!O ;D@Ɏnc#׫* X&'D,0R)9J, @YXr#1nDʃ `eZgfQ asl;l=.[ʓA QxL,(KڗM@7fdǧHx2rזu=KGkF؎W.gvv4*VtgSTͼ'F~Ď~m2?֢͝E7ׂVfB nɨ\fFE9 L+jDPŢ(r]T\B('ԉD0T,[JvR6J VjI:jupJua2ɒP$x޽jFh4ͳi4g)>mkuJ+҈ ᳔$DhM^$,Z/G Bb{IQ,q/,lDyg =TM DKR=p}{2 fr&թ!%K#MM 6_, ±FH;$M|g[f)׿wЬKW+߬uى4ͳT%rn(d=I@kF!A9,'1 ^lM<:d#Rf\:L,+_h(_$۔ԙ"F$ 8t (̒DELjos8d5_ $\=G{rǧHx}[f Frmku!Q{[CjZh4FyV>?FQ7_/Y`#vZgjo;P&?_AMq!&Ôڋ$qÌXC\TW>THC d b\Ve8JP#"Pp=T d{ Rk* |iPiB5wӑY)SZ+Lx^+`VŦ7 \ƭ-?Fy?{WY{(ɶbB0&sJ^J ,RfҔ?(q0){d,`fc4K*UXJ6egiQ|/Vmp'Cw8_+0ęi 4MG8@K2lR6>?F,EHxF{(]K<mD(0aQI< K-"u0ƈ*{R6tN# X1wF$7,x h&u>ot7ߪud`\lDj>JaEdGۻC}[F ,ʷ+ynjooksXfXڻmi4g-*pmQL ,pFa(llN=LԥTneV !*iYds{2s{3Ya:n(N@Jj;)9 OC6d3ř^nn_-S˶mse0DIn&p?q5h߮W._of,y'z߿Tv|[߁:Wh4F8>?FQ0 JBJ)Td0FSN~l/3R_c e?}'!Ga)Hg$6a89ϯDrJ@dD`& IDATicKHB–xNAdYJ4Rͬ FEQv_F4R{T촵$EԹHY{(ry\@VɸK_,UTY&"j—_}YRUā4:oh4'UB!l0LιAvxB>BLQ`3:D @pJMթ2ߓ1Ǫڛ=RO|npawƖlF$2IH6djꁔ״_3M@tRFwڭZ.8r4i8a(@MJƎfry*Gch<\|ŗwAk΋d#pzֽ}:Wh4FX>?F,Pkz&jJ9ۈ핽Orl&/#5zԫ4E^2+{~@A +ܣLMӡ?06@9׵ѧVF^MW֡f%8ӭ/cn"s-߯fCkl!lۛRRZ5"eUV_pk7\88 ceآϘxnK4`N'X#r <c)<-mLi]=M9 t ZT$a,!L3+|Om _f1ly&dʴS7zǍ8LV<7_TfVҭlHĈ83䔟/)`t[unY'O-,AJ ـڅ+ϟ^šVQfSCxk)q .ޜP196WS., !Bːz+KPB]lD8V! )o.d+p_M Viˣe2zrlmsIȭ:!DhRb=c{|` K_-Aw]]k¥uwQ[!Ki4Fh~ q;= FQؚ SnRe 邓njN[lM9b$V:؍-e ]U'Xɠp#TDzɆ%:| lGEcc㯌WF+?_?neeVsZmDX!ݙYL.38Pu5Fh4?-t>?F2 uS$c$lp_$@ 6Tu*V eLDfx׮/ޏ-˱m?a9O@^WY6iYd{ frY:4[-l!:2jDIwͬ 0a "9o돯H5fܪ-wƵe@!eꥻ`8R7 /2̽5\Pct ^t-Cήg']s Pq+a7}^ ueUEm%HPX; ֣+zz`KD5Ϲփ lwcgiOh0f^ReaD`;3Q3۫r;FFSNj (nm @vn/ 蘳nLD])"R˦ Fj5OVvRWd|#LXm=H%|PeO7a!ÀU[/Y4N!RH4u[( ܋)&}bi?WK| oO{3!/nZ@3M1sj}LqgD3VVdF-s{DdP) O-j5?yABeMr]7F ԮS{Fh4)D4ͳ̖)B.4}l:Un?`c{àb&gĎ͍$o fI8a$DSmn oF'L,84(uȉ4ujEILg^ uG?EIQ`K8egwEC)>oOȏJq!J 8x ٗ8RY4"sy\~( ^>9j;%bF=R:gL4jSp'N ATsfzn;б%,drzD&_6$ ~ԿP~,7/XbI6dѿ^Fy(%ԪC.$VH+Hbn3O'lvj d0(6,jde ۦ;qbM2/ 4&n$AH_p#| + =}B ;5Un}_o$ NY\8p?? Wˇ<3֍cqjCޚ߼_Hd8n6ޙgD K}߳$V5c4زyL$1UpMgR: )I~}6‰qp?ͽ@0ۺGbH`FdP^-r3)*b]c{UDrp'P1~b| 7okŜ/Zh4Fli4 r#Ȣ:',I2o=:܋!0cq)7F"2͉YtK['޶2rC=8BJsȠ8M\kQ#Rΐd;,\ eܭVWzdD3R\\*B/tXtCWx82yvvnogL0*0'XJdA QJ9 `ű+7Vן.z~|#jm?͇sFh`~2>ѫ8ar5gW)=!ɳ5.3)%\zYBH >)=(=04-fp"DI ,#'2DKV>OFf4PnnJ)*٘ ߶z}qR׿c,?qRr&ݺ\wpCFQz5"!R"+Ntc** a;{^Zvqz:rY4w{ٽK} BLTBpwl\ʫ7/@߱eZqlܭ/#}'ZS#Ϣk[#X)D"[m⎀f^A(&\Dt}n4kI2^SnJ@4pAyX_1vnܐ¶U#:;]+6A?,12LNb&Ԟٞl\ZH^c@ɯy@ϕA(e NX "QIݍ~v=M3!*B}ۧC6Tlˡ9C,Ź'JTq՞?7R>LIC۽ܐ&ߜDQR/^>b}j=*Զvq갭kdNɱJQBKXVV_IE ?~R٦fٗ5.Uzm꺧[]ߵ9:~|+L+3lU.qh4f8vkS%%Z9޻ ؑFǗvg:,]s?k(`>9konw.T`0.l>\-fSMW\K )e+_WT{{q؜dzFP,&4U/`-1iii|*Nys5]dV$=#Ϗخ kunr)y0 L2D$X0X]H%4L(plco}.\u,VO'YCh@<9@%OI&( Rgӣg:YOs, kRV_WyP=WLU[Kz(aTkdL~$ۊ adz*VG Ta0eRz`RJ)eHF8a1&&ߏی4O,K7 Eͽ\obaQ+{^;H)QGyW.{u+$ 2`A&Y&Y&Ld%5$DzXB"~D((∃Z7*Q\j)8Î3Xkaa.nq-mmͿsL|; ([c+֧֓\챬O!iW{;L;NF&;$ML2m:;hSwfU>3S0}i׮'}L&ډFr\ }tj|e2:<l:s__k~M܅m86~`YKh4M1)ýުTVRoή|r=g\=%uk@#g.[Hg*mu0fKZ`YKC2Rm7wW{9f@.55#'\i&;~6qE{܏I#4a^l\Bxa1rCE$GXeJm! 5 aW#إ'Ev=,,)]Y{^ ^n( )7 %Fj+0u&6cm6)i@MunogkP _ijSL=Lc3yU_۷Gׯ|wuvGa8pՙJ_WѴ_kJI%M |(/ߥg̗k 9g31`L_4ր̌Kǐ&eo1P_d g 6n2Tv~2|v쿞+λhW'.e(lT6<_ݨy8 @0I;|,`<rtT؎:Jvù(]g_䆜p;y_WVٖ%<GM\p7!QjI}8[NͲ/Ok~zv9}Jο_@_Q!3̜wpDi4 :YoV.] #k5~||2_MJ)"w峿<C˯Tۛ@SUZ+vvb{?_|z?.Lo,XN)pH#H3u?=w!T'_ͶW(G7Vj6Z"}h4&ňc#v_~K}7f|+Uճ+WRՓ۔)>yJ/_x0SyGbfmSV_\\ki4[e Q !!D/Wel vmCIfqiqwAo3("Ώgn?}ycf*qKtvT2) Q#Are3*,&!ِyX쫖K&_"2!2$NJjrCF2<5sk8N!rK2ner oWNX;Ԯ܇s|7^,R3X"$ǨDSoM/?YVɺwP>]83X+\9V_OiNݗգa~<}~Mf|U7eK/ڶ `UUWoO0Msy|ĸlH1d~ڣG+?[4 Sof.Nww.}kߚ'NCO(8ʩߜ7B_䛓<mD> <ɹʉXtv 0{3drok/U>:_o1GM2h[-ٴ]wi](Y¶zj wù |ݙ&V.~}/ͶBnVKyhDvבp˕(i*7˜9bfa6L` #Ӊ5_623auc* ^Dؚ{T0G5U) IDATwK U a)Y孈dY dk≨$8Aqad[F'`&)SO(ZaqjfD2n[ $2F?<6:_qKXVqo#,q%<JTܭ t `uoԂ_5rb뺫WϽy=XZ^~`EaەcjrR9~x|cky\鳵5{ȶ,03˻r?& ?> aSb կ^HϤv׶ { `yU2^Wϼz+㋟-Oz}%mʱ ``YcG+^y Ý9,8r0KIzvv|39BGmO'w*|۶*ٿgJR}vFuݫ֒zdv<%#Rx܏̃~cU7h4?ϯdA^^.X[Y#]yz[Anu<6@!zVki4[a˱$o joo0S 9+`p$# %J, dB DU7KTTdc[݁- S N`%\U]D ibL6/ vYӄPJQ!2 "uH4~ %,$j ȃcړel8*>וf[8p+#8`Ew#fV!(`|̩"Z3y ^JZI+imo}{fWk_k;{~VyK$yʿgyE)>P@EoKv߹[N !iwȉB D׹"KS{U{;5s*9r1b%$LK%`\ n!g=D:OXBeeGW?D}6ɣ}&EuL ( نsج' %{ެ,0e^tmKe^Qo;a AK4 yF d#T*yQ,@QSm#HNwHʿMyt196gԩz!ز`f6~| _j?(./f-!~;o^F8KV[)<_F Sr0ԵvGXyR7R~95$,Q{6^*-m6pG5XI2@4^{?{Yqi$ٻҫ?f ޭuճ'[Ru W^`,I+ޯJsO߯#Ņ O8^Ծ'qR^0=;y߷J*25?P*(soz?~<>V^Y]H0nTU 刳qyX`]=V*G]_7njHǮ »뭯-Pb2]E_!+lHvŅɶ)5haotSAiy~U@q@km-0@B8)sNBƏB´,p(aQ3j =@Xk՞Xm!R]>]6.T.~\ ͒:/g'ޝ ZXccMl: ,˫o\OXr27;Wz]WYoLG?A4ճUز=[2!kghXX?>=++;[A9P)G+-aI mj}3!sy yɑyy<9ss1F3rI[VSZ toQRJ?#x2R Y\o1DrQLpyA FdJ r&Ꮈ"/gZZ7=bGٜ [RHH5qZ(p]jY5w='gO6>}{3AsV@L\9 At4Pb s^r{@RRy{n,@+W@AUL6Glm#un6m{o{=~WdS`Kw_gO}-~ dv 5X} {eu%{ʯe^o ]Q͛u'{ ʟ:7 y SWΌX孬֑~<a?}쭼U ۛ~.mj?՝Z?ݺ-Zasy}Xf"S.A禜V{ۋ 'ma4"k<6{e{F`:{[#ler';v,!D^3+Űi%uRde]#H)+ʥK~R̹sq7|g5ٵ >.p슽p΋R*)H!U+! 9"[-͚?ؚV /3VWEm"`RZ뷼u<h/aqw_>Y0;/8<P$44~M7>ݧ*cV6jf_/BW?j [:{k fr\+AnXm}"ٷ7YvPnppFdv6s;DJ="aS(j٦]+ءkv.҂wCK(2/ 9X@Kq3ANf }fQE:8Y/F37u\Z"eiϛR yi/ďb? EqXRq_ݓz(ʃ]F1"'K@DtҼ(9+gKB[Kt!\HK7O?QmTިȼGl(n٪3p=^_u=HԖy!R 9%o֧"yxYFTu=ϫ߬j'c9']v SQ?^oCGls84/9HfhiĻZ-6vyd}ڷ7䎿6L-Xn6!f$+9iDDDDc]KϺDDpBTrw}}MV` XH @T#K䔎cKZ93w{.ia7>;uT KI+-鉕l!‹'ByD P:YcYkK"{bxQ?mуSRqxQ P(}WIY [M +]S[r?*M<0+B5U܌;ꤋ>Z+@h~`{Iϔqcy1&33R=_k9oٷD#Ed pW׿ݮt"i 1Z0kk@+w9uRG04~ۛrO*&U?鎺ɚ&wjԿN1#a2s-wY{=T{(%cHEJ: Yrq0 V!ұ뎶 fC&tob݊$&d%lp9"b]5Yۜ|@0M-PJuт4ME1|Obپnb4,Ȃiм&Y׿kt?zݲ"r?K-W~yE,~-5oUYm':m QP67K @C)g,ZkZpUSٟ\*O_/X? f;HE+oUg/2_x>v[婟LO/?OԌUS^-6vTP[, 㯕̘Hﮧk*gƃ D~%"""=p^""Zkia /`{f9#}zZ$-+bhVnrk˲mV;ޜq),iqMrI 0HJt:薎Tdv$/A4 a*CchsE-hhVfun3ZQ8^0"N0 o۶ ~N2&_@?Ph&~vƭwլh )F͊z `勺k?%;p~w:]X? &\zTVwp+Hzdn{Z^)e'o{mEon'"lyBB{.$"8]iaOe{uO][[IwWOym7瓨+i(p~2};-m?'?^,uw'okjDž`Le{[Nۿo<9+}IZjoIjomB kkf$StJν{8+7W:j/9?"fhaJ۫k>;[ə0"ٱi:2T#bDIIklD|"K?hRnbDMe"vQ dl£dtvJX4ȶR  "),)oB dRt.'T&"G{MSJ+-@P2/Mh!;ml%3 aup?c|YOy>yYzٝD^:e;;m'SN8cvy{UY+_w]yR+Mj/`+{nVTS9'cVVWFun鴫b@k}*9DZDtQayD[4w72-3e37;s{ߙl7)(u+]ߣJ=<]nۺcE}NB(E7u l>݌6u-JZȆ(2k! O.Yy΄|AJ۵)8F:)}-uKp^{~QS<­aPȋ7*N,wn WJ '}@t|.j*-Gdlu|l|LRdiUM#"B# m]ZaOtqcݓnh6zw@2>o.`V9Q̬3Hɾ:7"T4lrdYZJ gTZtAғj!lw{,l3+ՙlPZ BX≢)w}d9L@Z'+ul0WH’I2Gfy2Nش@ӥ:~'500wTMKm+Ȫْb_5n !Ǜ=+fΗEGHl{Bc>4^ެT SBf bDB]Edy hfdhc*9KHiJ,:a h]($ N8ٴp[Ep^tuiTʒMXHVҢu`̕yY8VHnH@5/@!o5%QtV2HG6i,յe^jM{:'.:(c-4 ;pKrB;5"ҹGd\f^%W]ߏD@K䬜ļmRfT <% yr9sUPA#HJQd^vUSt`f1W %#.diQ8gL73^-akΏs{S- [ b^.yfڇXWdAH&raGDlKtLkOڋ@FB^ȉ$uN'AgZ0%7o+TCA R#fjtF uB0\< tSvf!h3`.)مC;E'xw= ڇ5uVySNGȡ&2 [d~SybW嬜 LguKF45j镒DNdAOy0qmZV_uM_)2( ЭtV49!{~p?0'8;b[Tfd{ĖR70Z SSq3=_,G!K{d5bvj/Ѱ`Ώ=V|B&Y[7;,| ! + B@ i K3vof–T -i0k jmo-C~^޸PM V!]0Z:U '> IDATby4ItL5;#8?{F9uNLRA#0?0$U2W'{JYiRұDYX1[-Ħ= V!ұL0 ^ rOg΋[V fkk\5KT8^io&[:_8/mv6k^t.ضmn9"ZwDZ{U{%r`A"LBaBdnul!,4ĖPIm*tMH>eJ-,a6@ YL# 1  Mc$^SmDuJQ"5ZAaĬM# >_jCFF@)y(eEX4]uSqQ t^p̉ +ɏ"YZ)vkP(dg)`4g&#v2ʥ+B)S,%DtK˖g\7F\*O| @tY"Z2nAΉ=b>oj:!f< 9uoX%"""0gJcM!,ti޸6,!Γ{I׬؄ht&[9,g#--[M# p;m/82{%Yc9g^#ft骶rD*b*7c_{Hˉ\wXhieV`n(՘e^ u9fZ*ajaXՊ~ٚBuR}5/qdV;\귐[Э@& m* Rdm{#ضl߷9 mqO]3K&{mavT2M#?"flZDȩVvwWkL5`)>SN - J?ҒrEf 3#Dh핦ڛN\r۾bC qHEZ,ڋkรn%td̟ zMHm-jf젉zBL5w6-ENzvnAuݜND6 7g/e>gfx y_,4a\h -dfZj*9"͂/&7Fo}5s0Z;V*fw>oxT{|V{s~DDGGt3H}n"g=Xk԰tRJ4i$[2[Os6N&|}neL3tpK8nj?qFe9"ka(*e#BmUMe;`l/g M?mZV+6fB2 ʶ9KV.9$kՄNk"/#Ŝ3bӷΛԮYN%SC0|펺"/m%]ԌTC: ˸6e&Gdy<^j!Ĺa{c}늏=aGDk4Z ff'ev*-WXBHŎ,&Y!TeALYfb9V{ۑM{Υ[B /(@\ pFSte5Qq=_7uGmSgjK !U3vLhצHf+C(Ht beNw}@IMWh[:8$4bjhdt61] e}3mӻ/:"/!fDMWjЖq+%s @SYW 9/Yc(/\Tno}\ V{s~D4WQ iAU{ mjyM=UYyt^RJZ*˫mڨ7[G/K qa.̴drƮL:0F篯V.K)\:6٤.[PE!_0,HG@t7R2/ #b9ОJԝGly\IZ*yť!D*ٹ,,"W(sN'#TYC3"Z@KJl-(S!:߮߂jnPbLIF@50sxO8Ϳ[Z#?"fHQږ6!u]Q-@.q>4hd6n̚HA`#)%ZUٷ$R# X"hhL,ygzcօɷ}?ȥ% ӐY&ڂy9 ]`٬Wnrm܊Mױu], Q L һ@ _l,r-m8SN+n߻ w/":B ~+plMF,>fDX5ODDGEOEh!+d 7mG7i1kXҴ,X7RK5 hiN:[Br.u@0m6&x}Feq @܆YXXkvtJisEe焽gFx8N0~FHk,=>6nHE۾, Bʼt:þ4n @R}vNttBҫ%yO pl'_J,Q Qdt`D@%]Rs̋~F־E]=;x;";󉈈ǏWVה S+^lz|cz[ʹI/kN {FDDDDO5Ǚ(rOZ oDDDDz1`=N/ghm]ADDD4< F~DDDDÂѰ`GDDD4, -Rhg :˿@DDo~~/9. C%R !ֺŢyju[Z+_H o{43՞&ڬ_W[}_ʭҿiRm_Py ӗ> nlz7KNͥ_"M_pjod^[KN/aMlz_ڲ+vg;niѻ;)Vt''>|9tDDDDwgu ߬F(,FXY))| =;]4i;h#NSmKDDDDGsW~yjd|#VV*Zzw1m{>uhvZz}krlU5̬͙~ߙש'C""""8ܷhX0#"""#?"""aȏhX0#"""O*b~DDDDIE~PDDDDt0 F~DDDDÂѰ`GDDD4, F~DDDDân!lwξ6ny"""": ͅBH)ZkJbQTiv;3߸NMk{sg~˗?̗#wrwh~F~a5 70T.ӟ.?XǙqQO193XJ?#?#pO:Z"/;~o_j-K" q=@yrꪕX.yT<3fܭ [su7˭b<˹ zs|n{اVv<ҵi:]4xBͽDDDD{kw{RW (*g%ϼ1F%n,Q~s{bHgbf#d# ۽TV.cvsݾ0=-TV_/\yPRNDP2)fQ %,[kKy⑱9'˂(u ~:YWʟ{=8]^ vfOiomCgzwth~F~]xc7_<.@: ЃW7~|]"U5nu_tZ[eŨaI"""~⎺AoU#T#߬A,鸥50Ax7ڏJP:$ޛ?_9IKgؙڧ˽$ӵrڜMI"""MRTTn]qݿ8/Ir"e=g'ٹ]>t?@[x(^yKDDDt3sG 7 oփ pGUcMڟtر-vc]o]xt3[ko\ {ҭHjvdl9ozvyrBƏrimq3ۣT;ZhsNzsNo[[( GI`nKDDDD[=jq+^l-ɻpZ:IO;-˗~~iz|czs?_"""ꦟ%Q}%Ry7ҶGsXVg.`V{9^vGnyKmR'ϯ1<đ=K.x^.[϶ OtyBvV/}Xo=Ry ӗ>(^9 gb|fxyyzZ˄;APYWPXP~;ziȱ&WEW;-y&x[+ [@)jZ-f˱3)~DDD~RTTn]qݿ8/Ir"~%S禒oə ??r˥YLlضSh=;]NfxR94BTfa}a=\k =~DDD?~<>V^Y]S0}0<3f'X.K%nU#DDDD]5^H)ث H?\je~v3U~s{bLvj̴ҵxo1Zhn,Q CQAPr'/;~6R}pv`g^V?[Qr}@GgWX"ll-쪆gKIINq&a飫KwwxZZZz5F򺗖nwGW/tu3L&bzmz __;DA?z ם!"""J3g7wcYOųBZ^p||_ߒKsc_i]/Xy'Tf۝!"""jgu ߬F(,FXYWP$ޛ?_rc]o],vwcqm'n>rgI)*g*k֮߸l[9Sr+禒}ə ??r˥YLlضSh=;]Nfc8Nmʱw+]>g*et"a#DDDD=jq+^l-ɻpZ:y])/vB˿|痞f_?^7go~8Yr8kJԳv.~N0#""'߳2C/r}ěy^""""L//с| \ 7q~=#""":3 ɾ0o8}_A j s~DDDDI IDAT /!07s3G> Ax9!vd^Povߗj+=.a| D;;R AHKtb@Ax9Gʁ;ouhs>"""dKChRDG|9zŹDDDDªQ} zʘ"""!e_csF=PeD)` ֧SnAX{ܫNBDDDD۶Чȝ?ʼB?J/^ K ϕ=w6{}_Z8ds[^P{*z+'^?ԱF5BTNz^vWzzr&?wv ~Ԣ4DDDT:TcmD7\Dt!@ZGj❒X,a3a&ߚƿX_l[6GNj҃i=ܹoondᣬRٹ|$_{9]vE\Γ;ѷOVu(aaaU,B*9 (`_9?STW>_e$V^$6gwxm9үnjgGx S֚QVҷ-"赵7o:M7X.*OQy|\AßU8_L]|9DDD4l7 ߄D k1=s.c:#~4:RY$LkW/S}xݙJѵoح/?̦t~q. Yp+ݥYMs9) D~2/ʆVM#VMlh0Ύ9j{7&+: a2^K察 i(VDDD4De_頥##_`J~WBUk7TI?8EN#G}(cg%JDDDC?_D_:)#ﮎ?FètR\_' 9D;]9ZHΕO{Qˑ~&i\`|.];x ]TZ 6z:l) ?~<>V^Y]SwUVguۚ' >^Y[0>JqNtŜ2i};7:5.?R?pW/Ҟ-XƖ9`ï}pWν|+?+h:b x ~"ڿ8WAo -_㛪z^W^Ywȏi>Im1&xѸG*#a>L 4xc#f~S ~8s4 hɾ8AA U埈A`ygaRw4G 1}8oanD9?"""a1HQ(ѷ |>Iz@ BbhN r[b~9?"""aqXc~oƧXN?(%:Ax?;Ǭf AB-#8Ax9FZbTpNA0/ aΏhX8/r'!;2h\ }$H1GDDD4,9Zbenŀx9^@ ̣q)]=]9hѸh$xkn #"""Q!8 A:Jh\| EDO?A>Ahdh-AG ƜѰDO |<IVpA A,>dx+qLl@qHGs~D4zz(|96cΏhX0#"""#?"""aȏhX0#"""#?"""aȏ(usc9oǦ汷6v~n:Y#;eKv/8߾ܶ>O{+z;{. }3i tDO #?"_>??'Ku?"8SI?[2?K WU6=r^O^g;vrzVl]9MXrtܴgrv}`G X?W_B$6L>wMen/ɽ3UlmSoy?of':~o._ɥډ=A/4egT޼+{s{_Qh\W ņ XB԰ `ZaYyq 0L 10$ L^(ƕ`=h C À ,>T*JRV_|–J{ιfgGj~q.p&mBKw=sۋťm74R:q^ry'9>ߋLWn{ty8:!=yvwjH[I=8wŽR{`Td~RZX|j$ݳK]V?L_9;;tL2 z~dлw E}ؗQ-s6~`y_Q kma1B.zvuX׃yi?6c$$q뷯tPOSԣ_9!X76\;VώyߣʫG,ۻzw魏)ì戚жPeQ)q;W;BGrbya6k?MY/ wL'O^I_>5R+gggή^нwx/]}m~e zܾrvvf/ofg8}|L=sTŕu70zt _x̳Cv;"жjϳtjQ7&]ǝc#אQJW~{BefggW[y{[+әQ|W˩?Uޛ)8!{7ήcU1R(a8z!S +Ga#D( X0GYthlKPȤRU, 6q_K`0$PXFuEMKF,B t8-P@J&!QlИ0aYHٖ@)"ePE&X{CuBj~'ұS5 ESSBj~P*e*X <¹1DP 5?J\C?4[\n?̤;v61DP 5?Jr9;\@)P.ME 5?RT^#/B y .5?RQe jӡ0ED!s!j~P81;"T 4"E6!TA]j~'xG5cHDE #4f_D.2?88[E Ccc-R-8̏T"$+AN/!Ⱦ-B3خ.Z lU0L5IG&~78d#"leq!"PW̏LG"D("DIp]d~0}.tj1#<"e"IGl~-U舐jhE!H2C'}[)V'Q<5HAPJ"4EB2i3L\PQk6ǠВ)Q$DMQ]jNJDTyd(2?cIS{AFT0ȉA%Ź;&CGYnC0"FIDAT71BP @)d~BP @)d~BP @) \uə!Fo`\P @)_fN/|oa&j}IGq /-~(~~}t^wG{>WR?<~jM;;?~L)IBRuc>wcix2YJ)OGAf;m>ܸ;j~lU0>{aNJ2?)KQ#,\k.<xa+D֛m՞ϟϯNTl O~Ɉ):n9*I ='4xԔ^4iēQvSk5oHcѡv?d߁:Fso!sЈ?o{1y\jm Oݚm|XXmn<}[)63B̉Gyn>'75|xqpo!4Pͅ!U/}guW;QNi5:xiyڽ}ܹܹ/n>:|҅6mWR^1(=Rjx_z3*>槟,;yvonCCh8ơlK/OVh.}yW^a>7?ko. wAQ>hv/걹R_ܡ٘qZ37ҥŹ_ylt$rj5Z ^5Yf77v8L{oͽzbW/,4-.n6Z H{{1{1xp7;'wOx׿aqy\kCh=ȑ6b3;;;/rǏ3>OR<_cw~q4;{/`TkK˓:aOuo>=~RzB7Q~)=lϯpTίw=?͍ vC:> @yz5aC'+:3{}ґ`G>YL#N.h"8c~ؽ|=ҫ{{#5riHtWo [!&swLN)?^ߴgSJ{?㗋V)[B.-OtnN)-L,$NcŹ//M:Sh}>\ZBj7w Gu=v(ϯNTޔ78ua,|oa&j}m={纙T?P~ρ{{f~v 7<2?RJ!(2?RIΫ_![17<j Q׿z|Gmn(ΧѤC(?{TppԆ,qp0B/19dL2*g~L29dlb{c&NZI+;QaƁ7006|75SJ)]oo]7wh_{i}w{d_n;흽%|Gi}t'ԾU[0MWi!/7/9rkz|mOh;ƍ嶺/7&yo{? 5&ހ nD͵=hviܘi4ffwz0={dff/qe13Ӹbwvon7n.qc13ӘY#uz^_u~nܘ9۵_˺K[k̜mF:^ZMݙδ_y3)I~ݘ9<͵{\7iR6iun"uYo}YRJ+G)>Mg)}՘yj|jz/;oqƣ)5җѯ)-FiYq6l~w.ϧgõtlc&Z\m>y:/G-`;l" Pqwat7w{QJ)[_+g%RBjaZRJ?Gh`7|8S/u#jɁSVKou.k$,}-Hg;y+^?4Ho߽{{aX2?`|=7ՓSte恵1s3H_ޖN.}fΞ`g{^"Ծ3x4V?L?^8>84s+?zhXbz/?bv}>9}.Ѹqr©U9vf;m>ܸ;j~.#wd{fM=y#^t?L̨'.>qO693{NozzTSz>~zF9]w\O)ϛiSJch)oh暷M7ZӾiN}Qe7Δk;Sos5HYn?tL{?o>iSgL:v u< 'V~w{0g`7;(=P @)n>t1@v3^lΤc`?du]+IENDB`PK6/گЯPKYc|BOEBPS/img/installera.pngPNG  IHDRSa pHYs+ IDATxhV΢##p@"H -fGnBP.L1 3v?ugt[g`C\&揀]H DdAt @q$]_uIs^=#]>sv,][70 &?ZFh4g1̺AD3 Fh4DŽ;l{{L;8<6ђȽh4F|5;`IcV$lTqⓛ[*h4F|\sf‹s_ _W#cki}pY~?ҖFh4&WgN^^JΎ9Ӹn.8h_Vh4F_߫_7-܁[5Q%C~L䅆,sjP?`~9\^V6}}f^u=[ G7;ROvagl ED yK~7SontT#0_3^hzNYu&қl=~guub5:?IrՑUǣ ^" '0 RoA A#/ '=xVynQۿٸ ɷj1@ϮrrLW<lGatyw{xX^5Q|4x#=LoN˕ .ގc^M^ǮO@Vob?f^uq+ ? Gksh/Fӓ-wS_yT FGjm®s]X Xd,Qwke R+k+D֩HDwo9_ `[ g+!g*!bҪFp. qSZ?Ul(N84~3A#(Y({OI+]({5UakP] 6y?d ˫|3hzNk飮+"xZX=/6ݓ/;~+wGsD]/Md٫ħ𫙛K2wY4x#vG㟻on;/WF_*{ _XD"^יZ<սQ_zonb9 V.s[L%+NvaKa1.'o:^i4e)W^A{{o@J7*lxmҕ:yZtK$\cXJ {ًs%!Å++/9ae_; νj7j5Rʥ+nUݕpa3Wo..^-8q+6n6QlAm(@%y/[7L3aK{b=ڴMcڲkWp wJ0.|lLrBġSjd79,OWNOvlH27O{oz U~ ' VDҵiU'39CNI@+wW\sNWLƑ&[&s q =?uOapH=W!cꗰm1Ϻy?6NtK3q͜:.:M\^^Bu~a.v;gj8{O}hO¥!2fˡܸ$Xk%,ͮT `b =1Q<2QF"|wa yu)V=W[Vh(UbI 1iYzlEb:M?x[~8' 7Gk/UG SAUu&X i#v6ZJNAf?pK yhpFCJ^nmo񮰤+{t_,FhF#[#<4b` yrqQs½u0׈50SE,s j®~uUq0 iOwE]z%B8=o˫KĮpM5MM)SEt(PMm0H->wz8c.\\tNTo2u-wKԺVC]տ\?g۝| 0E|xMV&lx&sIfzbkm@b{fVckvP*z 㠞zVաuUދ^716EoսϲQߏn Xٔӭe/M碮*/{uߞFo#,yV E3,HZj8 '{qalgy; a6χA K׃#oO׎s o#zxTKGk4M 'l{z& MA?]hou!`hSGۻ@OJ5T;thm[zwk{ `V+b~f'T$"M nUݿ}$%]B2dAZY .X.] iM=37U =G^r"W,58#'AFbtݗ& ݨ8Y(epݗ7E :]6# 霮!n<۱U3 S \4{@gu (ﻘ"M/jo"IIGuPqlh49ܘ^; nƼ{tE۩ q׊]z- c콯T^LvplXA¿BҐ[N`,g wf537@|k=v:E[~:?F!_,\8 rQ$U_h\o{RB,Ln2UmFfSS~zDY1|Z{C5ګh4F}~yfkO&02qQ|D@!E**! ".b~ "2Y6w쁘Y23Tv p, i(aKE{p- N 4 \q"RE]f?R ;a !` .GWlARʯyK-QPQCrq"+vYCO0,ǖᴚxohO,(h& DJ[hf+7LMʖZB$dM((ZiJâXǮS2\6!y4yqks,:HSje[ѷ}[{ <FsEwN[~=h=ZR_t=o"2hWh4yA4a ۶UFEኣ,B,% /wS)C^DZD{. bDyJ$p *"N"3m|oXDUvN9_=NyLL29qj`ٔTBs&(P[@؎P=GOW|x[fASuZõpj}Zw-?F<5UEI\:$JYfOĒ$W>Qr5ijCK%viRFKEy?"Y7ׯ-ˊǪ3*Y2* 6e8H)9ArFdfB"35o2DJj:iY^@{zgHx}[fMVFrm{u nqg[#jZh4Fy^>?FQ Η۫h4FyhFyy$qP})Im;YC6(@+ fG Lx= cfVY1Ke,+ ւ(T9vb,DIcDDDY?4kLI QBѬ\uza3bs.HDDBiyAf]}[Zr]֯\p(YdzVɋW6`iyI%/j.ԭv @m۱oo>:ꉉOl4mo>! 5njle2T #`L95Gh48[TRFT 9j+\gLP\~FBAȬ/A$2V0@ Ux;Nk|ݡ(v)`aAPoG;j$Ia@f  -eXij/P9ʑ[}ھjqok6|2;eq q%nnxodY~|<^Exof}<~muQQO~q n4"Wf]9#2$jGj^?0U <6:6xm`ዅC^\i\RfFT߈Ʋםi2~w]h4FBh4 ,1 R;2A"6I9!wH7s^dSrSHfN2eQ:LȬole9{! hp̳Ir$KG,3ӡjbKёq3.v+mem 3ؿ "o믯gH5fѿO" Bɐ2 A>>őqv@J D> ai\_qRA1x}|Б.9wB>TҎUs܇[ZoNVWU6= "A#5NNAlo/__ֲ-"uQ y4#N[~FAu7Jc(%&aZ?ؾ*lfiҐ9kDT C""l +\ {lFVk`e!NY(B(UZΑKN $Mҳ$eTo ޛ->֢p- Cb !݁|{n8l#)׍Q!n1"p?wf*&Y t_-MaoP! ; Åy |yVCsiA8<=. B=:_Zf83~vkkE2g}^PpͪXjGjTNˬ~d:/SBIFZhF!=Z5hjTh4F">ߜ:uqˉL|4is\9g|:&gQ1cںg9~D%7lYB g[TnaSWnXp'KU./}q ○)uj4#E._,<22F㦻#!@ld&#M;"-G٣:!Q3àe1 lB $QH81l( $Z0w@!J~81!jda[( g|Ty/@;}v6Zϒ( >gZG`q,&_r/LV7I${) 9xg~l'E$kxoO@@z)\YxgGjYeHaŬ ]MlƱƒ, i-v̲l!)AY::c{IWͤl4)UP-c: &<:A4mshWh4F h4Pf0('UHC7ϼé~ ɃĄ HRHՕO RkNͲ[X8>3RBF%ibZÌ\ub7ɋ#adRwVl~L'ua$I[ٮT!PeSnfw+}0Gkx!KӨn12W`,1J'>]cMqg[2jɹi|8 J.p`x28q`C:wnX2 (ݔ$Fnx cRJ8x,!<@\06:Yrsx<9Plt7f$e A2e)K0EmU{bU0-kJyTK]a7=ГCl^wSڷطzB-Z,%]Tfw0եgI;vر㕹LWSR3;vO#Fh4#Cu60 |>_9iX h46ؚ s̹Ӗ|., Vh$qȅׁLem38eZ4aA HRiU '"3Z(e);*RJJ6f C,7\_qL Z~ 8n,X+IK=ܔq+bXLJ$ؑJC頇og݅hUe[Uʄ`K@r?)$MRBjyALʸ u `)%љWlZOsz~@>wJbnjc{8uVc{5V2sXGRn!%l 2q'r^F#XN@u_˯%Δ~:rܣuW?SP캥=y~j4F<~ro uoOy~hM:PuUo9fU>+;;@dw;^Co >i?b?5`^ 2 V{ $ j[jo0uЀGQ|KILSH 6Q얖Ň7W3Hޓ HfJŅ^<_ݖ 07cLw ebu EƖ&0aw ^ȇ*KQb=?bz=Q.RT!{':dR aP{|~nD@fmT}pV̜}>|a4N**?NE|`Y>zgOFtG2IKfJdBR$)#sUb>1g(+L$3RJ)PX5)H00Af${]ҤUgo-jx zGz^7[qBJߋ$.c{ߛ~z#UCykR/~tZj4'ƚ]$x/7e2(2\ ,b1_-`?$E"2;id!3X;Mbdk.-4tf"b}UEpZx^`DBPokA+dvETeQVj%H 8T)f;KZRʬ70 X$,;mQݴX`Ǎ¿}6eI !x}_< FUksy`ƍK{Ǐyԯ}i1#ãvV?{07sj|/'ۆ_G^Q7qߜ DEpOŲNAv:yB.\P/Ns}̜0$Q;&ߜfy¥0v[GǗ/ՔRMBp7X)5g;: Z.uYv۷oo eJZwVh"ۉ]bQm"#7:N{su?}Nȉū|[#h4Fyrdltd󂏗<@خd)Po,vc "^~=9 ߝjOo|T^? MhBS{Uf+l:݄H2+K܌MLҤzvyp~$79o8`GkGj-_\y,Ʃ_N~:?֛oEyX"d>?8ywHLj cTwZ՗s͝uh>ꗧ\n My;8Of}Y9Eǟ͡NqL̼7svTzj}i}6M)lj/p]{p 0ʁ̽[^3=yjڙw!Đm>cќ:vp=Miq IDATe.Z jr}ۧ}.z\];<`WSõ 6ǹꡪڎgRjhq6n4!۲k,ɩ.s8S??INOUf'3丶Ǐ{lͩZ<9gKѲjO*j>[="]l~ٓoo_?Mh4F|~'pl탇?[sy7~#4سAlڬFyrl/ aC7Wu;eB` 8p]p@ &Yd5r}%X ̊.*py*2ı. φsR.GªKMibL6/KӔwHJQ!2cUHT4A%,$j(c:傚l$*>Jklw-mZŕpy\*0AIj{13+w6xMyjN??qr\mS\|svx }mѱזwKK>U(DvSN(}߿Xk;<]q3;T8y ;0PۓVҶ>ߔdYf[:QJ/|q!c+om#`|`I۶$i\\ }P/ӿ;=,ǥ]w},sč֣p=,Ҟ 쩽FTUqf[i_o,`ekt8sleڶDEe@DIzdV,KߜݖDE iBe49`pr5}f_ AJT)]DT!n`U%ya[n@KF˼{Ǖoe 2t )!%bp1Dp 2~ y0c݉aفY)#ko ix+o6"[!xPT`A..Կ%EKU}soGs|Wa1߬wOWgxbP(^:;xb7B]}!4eS)?  ɲ88/ڛQJOL< eK98\YuOͻY1F8D?1nD(y*+ Q<~`dNIͅ+]۪sQ czNOf_?ܾkG^y>, sxtcdf$ګ6]C(p<Ǖ<DžZu8mweZURDE x%˱L˲h|B~g~9f6KgfU `p]e9=zuc;RK.?:nlu+w1)ռ^P:zQA #Gia,yqҙ?ɺ{s3 ŏ/vt51Ζ& d(U=~]9&KgNJsgv-y ?/wUӧKo͹PuI]" t}ʭX:[ֹ%|$/ }Μ{bsc OXp1"]y')~]:\!|l+%qg[]G{3Fcrb|F-xA5m^ @R㰩e]ȺT5GR]}}Ϯޮ4q=|>?~|sGaޖQ݀QDT9xLKŔo~_ u]x. YMC~$@J-(0 ''バ@`J~T.ltf~O?Jp{<<@@JL BfhWb[x i=zDhqfqc;2yW@ӡpQC^cĐZRGvh]fn~tWTs9?dsO-̾5+WWd]8semO9#TOoW!Sg8ZBHDQbuy˪.uԚ{knoH7 97-b/_OL~g߮ ;tdl]e][aΞ`Xz+>Ea#Fu  yCS L 7-yছrmd|%K<.T^m]Ilv[w"CνM,TŻ I04.DMB9g1[ʻzPs +M!L0N`R%;Gr~# Uk0n 5Uŏn"קo߹Ɨ~, `xNiwvfEST>y7V2y|rio*?}'vAp%YN(NLXqKTO!ɥ?,y_Wd*J?[V]w ㅉt[0ooTŦ[ |SQ/̛_UiR>w=OM:@(׃CLj*D{ס˴KP/e!SAc G QrXƠ::^ c*7N2GxTKi̾0.@Hڏ2AcJӃGif B OrxC l0`h?\2$,4\ѼRR=Ubss!$J"Ņw} `K[P|s1TQbθ5?)^*TF%y9NCs,+@魒*mW**9\ |% ϯ^_]| i i1֩sh hidq)eK!nc+[oot4:bMRefuS-B T$*96  C+\V ⩰0c(,T%#ިA@T'\>Zh Jeì]ƌv#c3HT0Ps4ѢRG1~Pe2,;6lL!C?ǎ!qᡀA2 73de(նo+0 ۻvB~DMp/}*BEPdsтu،>^)e2 \ 7" ^eF1}GJ[O+(ꒁGr n=sٴ7K/YT35_|sU[,s.~xr|(w%GO*7i8}{cɢrmĎ?Wʹ[QMx}wyد, g2ATW0@7C<ç#: dj̭Y@}i@eZQ6]`B֛}x;F2 "$jҺW=y$o5їu Bֺ!} m[ٽ<u12( d}EQ+u}us=;\nT׹H!;8UDfPT~h|XʩO+S _jn󿙟{knR|@% !H3oSK|/E]X-՟w0>w4Yjn^&ܮVչU*4cL?<]0 @2*P :%~uWUD+th&1U  ͊iKgJQǿQOh0+^^|Yy Ѽ^"ܯ0-sڰ>/<*8ƴR],,/b;6gVY/B,X5@|S˪ơ3cGh9]G( b,h&wD{6[8?jO?ؕf=IŖb,& 4 *uƷ^ @,IA< Ad@}V߈"qX %t߇&H4ULcяuX$*3I ؁B o<*3BqoqkHgƽC7(:* 䦽qnF 1U^6c\oon5Ȧi^ضӇmZ/Y'Wztd|ɺqyVShH"?jv>q捙y\|>?|̛3 pUlsa &NL;[HXV&Dg-ܞF)iv@c'7BlT7I>3ofߜ`z&AA} A]< ƄQq~^iZHVbr=WBc-tnWÂ(ƈB.1ƄCu?t[1kto g˨-JC$Gea>`cLu-AojU榞9穯Nk BA8)[>P:ʉ e/̟!*`96jqx@VCwfQ3꾃l!.. (GɉIg,:$hTU)KAA|~A8~$&+#ōDZ^yՄjacN5ˀp}佫|np#Pn-W,YC*ri(]cno"QzD,7$7@20 x(Х10\a6YrQdU?OUS8&`,ẮsPeh^ӹ 5SU3=JUPKg6)%ђiGZPHc9ϵ{ gu 7ǫ`|##m7}H^%-TX&1}6RJ)_E΢RJEKa#2e5ƹx,:1H@Qqm6J7q`hi;DʢJ*{ DA+IKnH骞<z!q @ԅse9SUHT"JK?*aRI\縔RYǽ:snY9j` +TWX1M/C}e8l"H0uyƲZV?Q!:'%D#5K| ! ȏ䓻z>(:\iOXPOfez!s^6[np=~oN4lB^  >~d4n}{տp`RM!|Dq[29E] %OZ14ICs1x#%S~tPh\Rl`}Ti~uƩ|>@YU3T՛KNM dYUʣD#^]Cs d0~ttWDuYq{DQr܇.ӘC6`/NB*j­QJmQRy*Y=:P09[Q>@pPd(YjYu]X/ ?/GD;Q@7>oƝwn'\gwo" 0⣱T2]3Qth/B[.W1DK _zȲ eV"k\SA: y uBlfHU 9-q m ׋]Y객*E,̛Yd5׾g[#_Л2 tD'4Xud(A渎:wFLբ:\ղSfqА5L±Xe{ʮ!C*bYHRy.y(a\i'I#jzs;WM4sz:;Ҟ]UUdc0)Fu`0jXoEx0x#]k􆢽AAA` VΪ0u/c5ZiYƘ>_QI |v65W.\W^ZR\ /~g{BEMtM1PMF^-׾g xdɄە2:#8?6qݚeY2^*0Nݚ?Le]uU)P9>f%j"J\ԅ $wUa(5}`zˀi*ȸ47T@UZmٲ݇u0}z|J0q;J{øISDA}-&QYZ7MYgLe(uC7 SP#1Yn5r:>R,~^1!l hYȀ墤]Ƙ:Ƅv(`iMSIl tc\e3L)T Hlʖg`>"ơfQWmLy3Rpgn IDATU9]X31DG_ԅ_!n竱qkxJKu. 8!SMl9w֣r`,*m-nC$ydTB1bDl\BDOƘg4PCS.?bg^:~^6;4u#j~[EM~ QqyvQmAAG~f-:  <A 9c|zҦc/Ly dJGa_US yCDop2IGUO#dazR s}4Ƭ1[,*JUc93njCE32QJW#\ 8Fb.˲R@P3q˲MyYqr2T,AֿY?JCRq /BXG,=EUè;\C$^10ThC$$ӥ/<_;1&&&ڼ}}4ِ o5fTfwӱ%{m?|`FPP&wY~AgvV1eEiBJf VM!LY$$C|NK"L?\|$_V\E{[Fn_os|޹%4}K)k}ս8dZ-Fָ ntO=j-)US麮Rh4DoKM8pE5YG˪[ #`9 MlJe0p."V뾬K!<.W_QFWs|6=˪u*NU}n?oxa|AAGD|$M}๽ OB{0.+iC䓡0G Vd&mҺi\2U455f67{KuȦiMGBn|<_QG䪌#1cP}rE]rT!f?mKX۪ RpUQ8I6@f/d?D|PI֢ǎYGY-J&5#qQj빞ac,MZ/jBX "DsE]p4 Kz ,?  B6Sh REbö=,Q|qkʹ, bSUA\s$6-ftP}!t^x>G/d݇yTJ42bL j<)!ɹX7C7tywkN(9'EBp;jtвL@sǨI]R嘞ӕ|s͂DmMD(x#:@ eVӛn*w$x\w1Al&F*"qqiq4k:Ū3˱ V|~ToH{ )<PzB@Mrf 9f>miCPENlk.Q Lh_iBAh8Ӄ4qn*Ձj"d>pDZ\֭ qQY?Q6nuU99)<#'nøD h̭ye~_ }wf0T]\߀8D64Ӑc*˲,XVuŦµA(/U5Xm9ɩAⶺd] eӴWgRQ/4Kol6]944v5r@-j^)ew]8eK]XeJ*1Bsͤ4fdY/ZI<9f򷒢AAA`9jF?-J Hբ_sy*8hRl~SmhQ/|#o9@Jn@.)}'?m;بm~帲I*Kl  #_;QZɋ뺮$5s{C~a4]fcTT 1uD|>F)#X;RJ>p}Йes*Gl B!DmpB&yF}vu;*qv}3AO2," \W1m-7D{#Z l^Ѹs@֣P q8(1 %Su dԣC30A1 mOt܇A7*Au&ҹ Uܘ@JU;:Rxt5z$y4ݚ]})eRYzrbMlj?3]׃ P[sL}<(lm[-c8wuMLТewY&t ]R0ϱa?Ws.ff\v/AA F191~{CC[9f=}zkFAA WӧE%-s?O^3  ɣ͝Y7GSVW_%  bg SAAcp7P_  MӴsl\?n{҈xn)Qx*֪AAWr~.  A@O9AA? o/AA~,?  Y~AA]خ?u2/; AA iU#J5i߬_8=P@x\KO[ 1P ~e3NO K[s_=?QyzӘ~pxBq0+nLW3+/5fȨ$vİ~y 0Dpy{RSl %4H YbKXR{>mW iu2  y^lP-9!үI=)|ONoap7۳ w]x]~Ç8z}~qRyp +X.n{sq,AA5?.ſ3 vVKY&e]f5T|^"NXyɮ~2^8y؝z~2+ˍƌ˫71^X؍V17赻zo  睟16⡀ ?p 6{͍կ\Qe= e吻nTF6beP~bǦxX`uY  {-N^٣~qY1W@B}G u7{uoƛF'A)#AAdCȠ_EMN1qA] K)sǝ|c\Ԥ[}ܛqL|F!:gYGzuZlT׀5{@;MY  {~VW2<[Rl7 8o߬GʨU8 8bN9 '-/d2Y/LtW-&ŅNZx /^Y  wսKɿw3sgjf~S4g4ٽϦ2m2;^7!@A삼ybܵ+\EOM_{_m.|7o5FQ_*Z[FC=$ˍrqە]q(iJQrf/. Q#P|}~z@{󕻛׋rwuf%䫱㕅B&ɜ yY~e!3^Ld_ /pr_|Ų; |fo5icڷѦI-tzm6x([dhϦ2#rq/niפ}if[DAbW:<ۢz򙫳W+/Y+TO_jwKSקe{ˍ[Gr4֥苶*V~؅҉҅co;Zf}$l9ibٛ,Me23XQھNbF-t~6\]j(Q,޸`Y*峅o:La_jҲwNACcIߔDM|sŅϮqf][h.Gݾ+9{x&6m̞:qjWڴ1{j}Lە*і+''S_$?RӨ5KL|smnKV4gO \hRx6+Ծi:w\oQd?4ACĖ: CHYԀ[;WDa,mN<} q%.yjߛ~Qyιz`eɽ抶.^Zۮrgvmre]I)0vRX(h+uemu){=JhK*ҥ}el9Ug *z {]1dtrǼ-~zjҍ[g$\M.|' 1Lo;d]BB5 ߙ-my6cATgOEdySM|+b&\:r˼SoV2Lfj yhfNҞDi<{; 횤־{ܔ,LC#h4&'ooZ/s~۞>=Տ $ "oN7nT,.Nr8WT M&5 v4 yڵ6o,ΞHveBZu{Q~']kU؎t_/=-jY?S9mj? !1@BUbB=pbXtݦڌ5M6Λ/ eTI bV> ]08R5ԥpֈj TwJ0/g+ݏPZL-ouWÀnm*ҢUy* KojMɫA9W\E"m@{}?nP([.֎Ƥ/ EOtW+\v@y/wF`ڷe Դ̝>; jɐy$$˃i^ 2dC%fQZ9hڻR{T9[S P>J9lJhZT\8Qy{D TjU}HϜ6-j_TG7W*W],bNLwԹ>w5.usoi vK')pxă_;Jēb65 oLwƴKwc՘Ziovi߬}(9v9&hO h_= `;y81=Q/]Be|/i͑81=jwql~JK__A"Mm tܥFh4޷^F.Geh=?P3h.@@@> ȇAݡ$0js\_Zٸul1p1V(G5UAG!N?t D<(7Qf9{RzZ?}#vc@}١%!l L&).w]ײKϬm]*ds*Ѣ5L!Z~p53bA36._q W8AXn4O[ o  .>m~"->m xvy&,?W  KAAwzehZ$99  6DY2dB5!t5fr0Mq"pܙ3Y|ؽW6Wݽ*AAOa[RspnsW.4ﯫ)pgSo.o.!+A>Kh}._(G.amY`Jk ,dd2ɏ))3L\2Lfam/Y!AõNf5+ Y _S3V5_ͦ;s;s;E;y;V Zh"I 8׸3#WJ)o2W]kfNqZ%p*qJwf }|Th4=xN3}vjTgm!=Fq =A?AB+ @CZ~ϭtzKSקeSNAWi]o߾':{r}8o=8TlgS'q3IF c/W2W2N1~¯9b`_!FS߮V/};/li)Ov‰rZe>kw 2^؅=5嵯bԉSz1jڮ][]:iݹ2 b2̪.,h?V;8-N ANꪤ /Ε[xeq'Ӎ_&}LJBˤ-suT oتIߕc1[:cA<-1u*\}KV*<?z˯M-a~UN7S)y㖝)Wi0zۗ1dX.B2ބQ|9|0O|%آL]w{Br%6g8:?34="?pf)tfAE<ŏod2"_ܸ`d2s?fu*dV$v;Kh5 ȗ>R-f2̥#Wvڗ} nrܨ`F-A wX bd QK>2oӧ,?w9Wv$ƝC<ҿ][S0)r 2WӧE~9rJ:7h6 [>su[O[* Yᙰ'Gtcߚ}Pu[)A3ȐAA,dAA# /<.o^  ,˟-?&AAh/AA~,?  Y~AA  dAA# / !_x5!á'  v6\q'csƘR֥2\ж>H"m@{ݹ} ~ޜ9)AAaZZs*ӱW8Jq}໮[Kuۍtn߇~;CA3L0t<``>釧/_2.^{7vw>fD.vv7Crel߇^;CbQ.`OVޝ>Th4ZĮ-dF{4z7Uv׽13m2ȮV?{F.x! vi F,{l.,@dzMًn 36趧/f ti7>hrqp.6t.NT( gf2bał6{!T?*[?W}?~WGOν׍w\vl8^~F~tJDۥV[IMFGkWyյduo߬l6?;/G7s+-M1ЖpṊ<0.zT+յ9흔[a~/-u{۝&֭Z|%ñw7vtf,iR`G&C[jW4ǽt2Ρc-uoC?hKtNr&ly w+kھP\Y>ho_mq ~TlbASmo{m7v,p e.esO4ў׳ګǗRn[Uv,L;夻a79WqKuUq[]Ӥo^m`{u]j}n޿R|;joW<; {L{ՎgY_K]/^lѲNsS;)^lZ_K9x\vʵuj뺖mq^uhKKwR;U:޽,aFëwRP.vfõ+f_6156]vg]rDmđsдBRܘe[\Rw!uO3=~KNcK{u1BlVy-+~9W{Ꝕ{i!W#frFrt&a1ru2 8-^ҾM3wil_ZkWߍD޽YKNknlqku}ʵgv{5ne3""2*ĤKK/{^? ?:}톏p˵>eqL]}t<uiQ5O#6WgXH+ܚLL8n>&O/eYfggfݗepqL{iViu'ZY#o_.O7)'t<,%qe˧7F$;r~S 9c:?y0Zon=x(J-;i}<ӫCf*mLV5]jGt7̀l-?[W7#;;ٮ]w-[eNF?ml NοDBmZ]]H|0+ \F!x㶿?6wK8ۡbΙHʃ>3ǓFzc-ٝ[;7[VQThSBR|~8:TvE9?^bor3^bgi꼯Ao'֝2F]\plc2-qZ#lXB!-c[۾6ͥVZ{,-r/RҨnTVlKC}zN=g+r5uMdZ]6)??CZ?|Q/[t$zB>EI9ܭ-EbH,IMwcUk#uQR W4KZe:3trQcI{))~=%Ro%uK'_MI 52S뚤#KEF]:#a"Hd{6 \ݹ2jfYfec- Sn1-jױe0:{o2knOzquiSKS4jyl3'EDrak:SۦIrd [c?5`_kƒsBԶewDLȱ/O'HdN]h\Tu}o{ͼFy9aF>Unm7'Y}&ͧ,~=6?~W)d,Wۛ ~Pn@/p|yw76 y^U0IXneW~zpJ ӱ/M'fs'Կ:x*t qWq7[͗~Aa7~j3w^ukJY"?oư4ZUDžu>JibqE~\T:xK2@LG*fTQ0$ۂ1" c*j/pQ*$3*4D:pP@[]"o ^i}oQk.4X7V^ "%RJzPe 4=jҥbөscґB땲zpe6ݝ?lv0rZ?;l]}7yPrvӸt&~­&LgZ/T.wRVmHgwDD{s)n>sn]1{յ^~p94.=ܽPe\ dp{ܥb_HS4Yߤ9*SDrwfN͕j{ze@޶teyXؓ2{)~TK۶&_)j뇲f?{_?l x ]H|sޒ0?$ow;B n~3Z.@ydݛlq4 1C L#9TcRu;`_mK~,-\k]Vv'PaEjy?"ɨo!s _eEvU/E0;Q}ٸ{R_%vyvVF"HJ.?Y6oT,NwcUSm w^E02O']kӖ̕t$zαvNu~îlcz.{M>C:l9ruK=693_*4>O{n 쵥.$պ{DŎ,urxMDsgK_1(=/g>7??ya_ksd,TyrLQZUεArdX 9ܤљύJsXQBcƶZ٪ԲTԬ|~F~XsFe1J/o-%iF+~v[/ f,Q[1緳rag@jUE=m[VFF}:*9nѣs\HN(MDDV~1Ͼx`E lb*{S/ᆳ&ލ'LMFG=Llyoly巅2IM\ yvoe+{e_'c*-\kON$z{9G.)JΞon;nY`& g:^xVq vҟ'(O~|Vtj(R菏j/&~eW0L6s\WD~J89CڗOsL$5u +"+J$(ZL~ˮMEn;륥vʛJn[,iU2.MJuuSԺ^JNҟȦ^_'֚B"_޹وJ ο)^`_Ykז_e"K?z1{+i>0~s'ntdߵL/z'OVIKW IDATwv-sF [4={^ӵɫͅ@ӄE'w'%S껱Ȼ״"2'+ ~ܳHuYof9zgwDD{sﳩV峙iΘή%wh0rVMk7MDߤdG@ӄ8>YklzUHތV]18<~iet/o֟xfc~3N'Nٮ5R0zp̈c2+8[Ʌ :}]S]+>]ɕL+u7UBL+xکH527f ʎ׍j*S391%ȊJ(֧EOEkR_M_+wqV3WvґX$RsȊfjʞ1i7.d&N.7PH,rQ3"gH{ZNDE"oV6Uz ۟w @O—P3UCN:BPPr~aA<FCV+C:&a`PeBPPM/NzY `bT (S 5P }HW )"tRT%+әB8-/9 `$TT*/*2EXGxȁBO1!)*$T8:#GyO9hEA JCT*ғi9?L8)* *0 E~4;/Aʜ)-"ͿmصTZtJ$r2.-947J^j݈-mb5W=ݹpzyXn=qԡyyl5jAM?XMM\--xP/z9!=]ȊfsO0ͧG֒Xp/2j/=qhǽOU>3m ]~^|WE}jT2ѹ]~_9VkCg?v\vb8<_RdχAxj>m7KK{QA H$hkk_k^F9ɥ5첣ȊvDU&7NQ`cwƚ^YaKo"$hi%Ij~lDYaaϨJbplut21qNKKXKyϼpd% c tSjk7ܢsY ݥ;k?Xn=okmX_8쫟&Gַ4DZC̥.c!b=컎+s4W3X$K-vX]""ڍl􃚾%vlK/Ȧ95|K[HAAk;T?ڛ|"t]5huM}{V~^\zA6:6Z׋YfR5rnU=#rfj|3Y˴h5]隤,uTWk_i}a3xU;7{\'%FlHM$"+ڡH+<3?5-I&RFw$~ƈRj f\H|x*QYk=-Y;KcnyGr~Pޑ,u[x!F >ZorK"S۩ g;6l;O2iɷ$sI:;3vjsz:L5inSV;XMS͏ySlXl&ՓR|Pӷ'S4t>2M5oҮa~ۮ8m,v L#n3~,\H|`y^X_?OX˥;(oƥLB+ g_Ou>0RTTn,5*eL$']jҹn(nvt˶#5LoIzTEFKص'_U_&h׋CD"Ȼך.gRnrKGbTVq¶iϋŏ"2#U_vyrٽIjklpwI]6>hXh7Nъ;j޵[;ӱX(ME.溕fo@K},eڋr/!yw]ٴ1"t掜O +"?oj z5-t cA& +iy`_9vPS.wVuX~rȥ;m#olJDz?aeLԪwRrZ4.ƒ7*)9l7V2kH#;?6N*h4pʺI.{iJaᄅu7P.섽c4F9#{g⯖uUvNk:tf׮>k4kke4eڋr+3uzu֘!N~plcawqsm]m,t韓mD~_LyKE]7uݱδ;έiwG†(^z^t&{k͸oO񳫿l&^&ߋ+,kKS"ɟƝʒeקvk߮ni׵!Z+ڱ5ewښW6?nfhw܅{ݙB{Ts /_ Z_n.}#ܽ=6{i{g }},?wOo;ڭE~"MHrDlŽM\EFbpU ۻE"HJeM<|sJuvEF y*Ț,-5nkAIV3֎{ù>ֺ,s1mM^}llZij7.escDrW4>'"mO kǍ'ˍ+ߧkH,Jl E?iߝn\t罿##H^8}㟦P'~dޅl?ͥb"Ԋv(_I5>>k^/\nDC6vVk"g$Ϸw.Dm]79Ywss3gyt3@GH 6D&[)HU!."#ȓDkKj>u"O;[zbqf^0#03Qg~E$ӉI~Qsb\2% yq<:*4Np-f 2fX*["9?h|Jd7'z]oxw\xzz#2?\=ay I2NSzLWu7:.<&î|‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚`{%2khï:Jp\oQ] ~+KW{yٯc@!g]^\A-5B`7)-]ܹWO X)ێu|PG꫞QN9?`0\v1n+-Y3pm7n/,-sK4-mwmta)͡""{g:eG|U|:sQ\7)-U2\m:1u#. ׺{9<\+l1 m}; !S)?fne-I( yP+MYyj~lWn|rB~OD~(;2d[YM?(fԴqLLJsO+/l]Ǚ:]_RyRν,dKo&G\w^rfN_/ڇTY񏗳 m 0DB%ΣeywDR{|j`XiYNӫ[|̬o~BVgula( 3O'G(uWK>cs{b,2[K9/"O;[zbqKnͼFy9aF'_9`@gnϬnm_pSk7cmǾiaX[+d>쿱kSݭjj~Ѭ'ț"7 @|P+0~P[wyN?<ӽp r~sb:{C``^ r~!ox#nP-l`C ̊ ¤Rȼ9? KyE:Y8bb@XN^`ª LgK:)‚pa7mp"SB]p r~iW!g‚ ,‚ ,‚ ,‚ ,W"#cMDd}`jk/`~77z; 0E)՛֭Kz-l~Lc{T.ps (L5k#%0 JdybqK7Jv7#cmƆ򻥥l;b_^(22Q+ˮMo2geN5;cnkּв/Ֆ޶o^^B>jP0JbfUd!/wȓ~DӋ PGzέ=+V.?Xk,;b]ݘ[1r[?xo%.l9ZD1s~vSZ^̓z%kh_awNvղS[uKBRdbºr9=I|N33V/?ծ&"kƲr|dp;vL+`d)g;T٬^qHLQN-ié-I;d [ \b{Yǵ{o5 0DF-8ƃ+O-zGE {?ERFvW[ZăNjF &>}1wzS1r[R!p)c8ӺTՃ۲ES9ۅ[he־vԫݘqcw.>_x<@ه."?`Pӫ c~;Zf:hܸ$ך4xZjұ]E):\k^'gm߹sq,22gẕ\Ƨ.fduo_{_+Xd oTsmCsZ"O;[zbqOQͼFy9aF'_9`@gnϬnmœKmDn%co\]!afVXneWgzs{J?x{5u' >85u1~v}ؕ ‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ , ; &4"G`CPE`r_pB ,灰RWE`e`_ CRF5_u ρ:S‚0 o}BCT(2 Ee)2%TPaf*3B81GC0VB uNK *AL `g E"R$7HjdT*A*t ŗP0EU\%=v*A@xCx oU$YRDm> G1+T@Ôʀ*p eBPx|AdVTyD"Ǹ7M*7(3+@ ,=w{;Lj@lo0(r{:W9?] pI)R LNG\BL@p|#B|LC9?2o}~J‚ , (`SWEr~aA8}|x7w "TC ‚p'?7 G ҟG ,!U@ ǗB)H03U@e‚p҂ ]BJ4|AACr~aA8iwT!ߦBW&k S;EZH5?uE"]ףqjPgfzBSPjHDD9? ?=HP_N&ꠈ` "T/43G: }>CGGTh uA:9? v" IDAT}~*5͓E!VH"ƒBG7^ @THҙ>RM(HA ,!t~wHrţd UE£`f* Gh9? Q͟ R`(2*1-NW "?Vcxos饕neVbZ?i_/-}Y8UEbZR,#͊iJ2UsqkEkX<˫Cs:xi<_zJ8>֓=Z]msMsVKx柈挵z{c%u#꠨fqz;QtSЧgRUkͿ)w0wn|&^bfD1Ud|$[ZÕϾ,/y{:gV{yЬFRjV}Qz^DžNF.JVkU\t L}8?fƜ8,4gTcl2?@EO hڦgO9||6pZ}ond_ZT*RZϵ[3vinsOݜ̲։bBt,iF{G9HۃgW^oVkv~+ k$4Z>8ѹR^̜R5-$>^~_Jufޯx<ܮTDD^|jVuBǑ*{eDSwnn5bUk3s4ggN.Ron_zfIWYFֺҥ'KS;fKӜ ߜ{͕;SͪfaG!NQ9fneF.WZӬY+<[ҜGr>|:yhv\s;C>*m]:\J5Uv7gwbMb٘nM>R`u&ЗvdQmIȁ#Yժ䵅/ٝl֪z#?}οkM)ڋ[+JV5Z}b͒۫og/[Em$_5_2;7i?DbzLDz# o+/ED*fQ^ww.cX #\ka]DdA+ҽ`)O2~UW0z:%ӽ;\Ȳ|ԊkKoIKʶvx%{\Zg9֎"`E[S.m x3jE3XS[HQ kuf}VsgT$ui1dGT;j>U:5"WG40*cmBFjR셸&tX| "?/\׀&RJkg2}5$skZDbh܀X}$0=đWsbgZnڱV,䄪쫪k9Vzp~V{odGGb(Jo$w1#7mf8^vԬ?Hf}6 З2⌎Z50-Jʒ73(Zgtka &$ +v{ /}$wdмI+'SniYFrq#kHϓ s7)S.Xm[!i]Dk k]r}Fo'Xf_4GDzq{CyD;7ud DuSzqIZ)&FCh}7$NrwD~@ίԶ$mV+Xo~P&o1&O3WX<*%nh_=V[x23c>gzjwB:mcjwHPnz4fG7ḳB&%˦V&yw"O;[zbq|k3f0`!/kjlwk罔ϑPZi}⻛3xk<[L~k .9E<_ݜyw4?~eyc\GgoER+7&:r˿Y>rẇ7{mb_-NX5P^!7Sh}5Ğl(L' , bwsόcP>>@ |:Z F+$@ AC0TVppq|'<‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ ,‚ , s *>-E'*V**̴ LC+ЧFC _dL*|8=Ǘ !"D~%_#"MsxET4 ot9ƽ7swOT8k'+ASx}Nc{Ww!v\_(2+=}~$8}HЦH5N?/ Q"Qe*"g@Pp|)&# eBQ\$ ԤT$Tj NE>@38BEǗ(AqtL!N! ]"TTPH9:Tm N"g^UĎީ0%ST#!tAN #^_IT*3:|7H(xBWxB|0ѓJ!Cp .)2IHD~ܭp!\<*040 @X@X@X@X@Xř^V*|W8ze>̜@=p܎TN8nD~a'<(C1oM`ZHWIc-9;t+ՒϟHZ]~VgLӞ=j_~V>o1igW}x*35ه;˳9 ݙ{l{5?iE|d}cN 8 gɱɱzGO Y?Vٴ2eZu\UOx';y4y~}۳@c4cd ͙xl,Diel5osxll.O4 &{g򟢱,ЖdzS3_ػKu5qws XZV>FzlsշX OR5Ftie,VVḰ3wfkkĿHkW?t ⱱrͅgfն#Y=y33bT9<Ӵ|0&ϧRSzѽk9ͅϵ7s-{*y~_6:ĉ8Jcb +Q貾'E2b}F'Wko+d#{[9W?7lTy[LEBz]}5Mku)&"2_>I.a.gh&V>?azf\/?{QTjɱ7e+//"Gm"55^:J6^F|%Z/|DϵVkCcX+ct+ëdTMuY#\d#&UO?e}zd;yG+|?_kxRZ]?%19HF:%GMO%eLq2:$/W|tL?FϺշ"D~g6M^?9LXw6dX}8j,$:h/Sg'{HN ϖi~|yo'YpyHe~/^oMFG;w{o,R?jF}&N})65׾yY?lw=_ygcho=h(<Th|o\^s<|+7]dFE]ᄉS_m?\Nu9Yc"󏫓}NUp|_Y x25&"_zTw=4k'ɔg?wNO.?kEN|G~nbr6_3hJ\T_Z\6Cոv/ck$s.Qn,F2/*?TVkP"SΖZ7l9/b~wlyEqi\&?lTVx|WU p\gZ|jص[ H}bJ*9[9wUTS'ϟH5==g8.V^%]=ކuAL&zv' ɜcd_Y+az\sxq""̾Ja}V& u.l&8hg3X$sUDZQiɵVTE `Q{.(G ;-K 2Z?7FZ!R"O_ mXpEv|PDRO/A W_w?vEPN1I4Qx%Gow|~f*SOp8 a$鳽"RxceݟOK] @ݩ}:;cFlWS=7F6@a)AD~aAD~aAGsI22]7<^} nԽzn@oư4cu.""lG# љB}\ % zQt}\D!Uקe~4.g.@F$r|^{b3$4Ҽ{RX|AF Bc&A]?똻H42"lclsa}}K#FMDr5$Dk-|#i%;@ [Q}Ɗ4U}p̹.uOڷ4>L>mUNtg3~2޸^5#_uV ?f~k= 2?\|ݬy`3I E[IENDB`PKy}PKYc|BOEBPS/img/installerc.pngPNG  IHDRQe/" pHYs+ IDATxohWCNAn U lp"p?`,D& c3/f5YQ6cڼOl{Q9Z J`eh4FhPZw;..yFY{zFh4fp-)oϛxh4Fuϒmk3Fz"IlNq*h4Fr_0L8=L}-x疢+fX|Fh4[\yRrp35cjFh4!ٺHOR0 E@ydmRQWh4FFv[[I*&>&7yꬲŧ3W殆K- Tȅ7I}NH^87.'?,+krˊweS?]?'g ׳(M^꿑6S94oGMq Q #ޫ-sAd logXLq!RΐYFhR] >{FtJ%3韗cv.2?_G?ת8\ƚ/S$# pP7 ^/]ap+|?*G+^=ނ[վW3UUoJ~yj5&(eX_鸽gM48l5Q]wa?9-V+z蘨M^꿑SS;g#g;d뺣e*̼t:Vdg3oP׿/8Բ^^h^Z 94\wF{G4 O.J|oNp7k8Ziqͦbk4P9`nG݅jӈ7|eSȕDPDww8_ `[ gpf`3Q1cyM^f?TB8g!-S}zS_v?N3vJxAoe&o$czx3P}u6ɥMqV׉rm:su!_jk- :{5"_Td._^2wk`/µ]tZD_꿑ǻ#O5v7y;et/K(Y:9B~^rï|'t宬^_w0HǓZ{•$X>f˦;ם<…/|6] q(ޑF]p7ue5=@?]ZRf|3b ˗V<>^B* :^RO ,^]~[x9s̶_+xOL;>8 @J|sJts!n9l/]jEm⥥ޤߜS kw|A:fӃM&vj9#[߬DjP@D "f^r7L3oA׮{r=ڴMmkӹ7p w^:LA^biye2•8bç{&/=vN78]vP2O~0=I o|Zs[~ 'kNcrL˝y{S0⥥J v'zk:'(x #իoGq$cL楅~ۼnuϧ0CĝՀ13ضg~V 3Pao?.`'>$}2?YVoՙ#^\~smoOoN6,G,Y(Y׽6~~Qm(te9^ f..M>C=/aK/`Ì5&j:oWVId7,bx[==Xbi#W(kFl#1M 4l/>5G:]זxP#nDOvX[C*v9bo0mA*?*E/M\~f%PϹťE3xΜ>dOuO¥!1:,2 ` 3oyiv `ÞKDMv[20~ Lkp|3jUVws?Mz&?OQ6mOvroΉ"Cy|Zy{Xe>5I{UFH;}_.kՙc_OM}j76krS (_gDjel@ia–҅WZw#𨭧n1_,f ˨vf-]̧c84}b` }J~Qe*ed ͒"諟@-?M SIMMmrid[} %eRD\8(]*2T_^W!Cf ]+\F}dy{;AmZ4dC`)xsSqfy?kRs%@l{b"k{行j9뽪ݽnQo"Rw^9Y R!Ydj[(a l1 n:rWJg5囷QrzN9 9#P.ߪXY̛.o0 W-c囷Qy?uc\5כiw_y鐾c؋|2bn폶y뿯8Mz>)/?ǯnYn'=]Cb4~<Ɖk'_s7/l>s1p6j-~ʵ? X.0?s}ɣ#_Ut_3_֧8fp1_S5"*.m[IG˕Wn/ݞ|GF޾ ltٵk _7(O*^%k*ZhnxpFP.^\xgkO>u&/ݥ8 sȖ%|Yk/EڹcӼOGⷡWdž* fng0/#I5{U6űʶ]wsQI^Rr}6/#)l+~f[6 }MB7jk^:M)soj~tAgkՁ` En6bgݮqn)ZYȋ@5/3<oX(N?:-=e7&o.n^]f6_W8˼QG` *9d]$,a{(9n7wVK$=Wk^ȵ ]:-a LNSl&MQm7|<'቟LC枑uv-W7 [ L1pT>MH\B#H5)uymi[oג]ܑ^Ztq#<1+]fT3}W0`?n܈KR6}pXOI lHH qڒ8jZ}CFItc{LQ3a>I]}rfǹm[~0omiAF0  B#XE pw~F~nuW6*@vu[0P,(!& J[eAH m:fۘ79TK[x\[sDU*68P3}h_]gd0Fu%'my+J5^MQKmvݖw5M9Ov ZAZjf^]>?e}A$qWtQ_xR`V,\cZ4/=\[ ǧ{͈'FFh4_E%מC6匡 Fh4c vߘ|Fh4gѣGr#Ek4FѼ?Fh4)m>Fh4mi4FѼhOh4gʹW꛼h4FyFc\n+ͧox4Fh4җK[h4 k4`tOh4G4ˈrCuyH@F*'JIj^,-7 3FlBqZ 0\A0@D801p Njl `*\"Z8!DSa& %@J.٭y3lY ik!s:6˲H EY-$OBErCD^Wu!@%18G4r{ȵ-k֞څook/44 mz匔RY?pjZ)2 RSLBY$ +3("LGySdPj LaG8AR0 H:?$ҧ0T$7Bd r.:N1DHnH*1D0ݎc; l>)G#ՑU"Dj8a˴!!7BUJD$ 3(}6? Yn9W j4FѼh?FyK)HK'2IF ϧh^Nw$&깵;%0` 9-VQDd Y`@qkP3*tɠ<3/d 0bILC .ϷvZ uJeΣvj2(#1ΰBJ?bJy=[nℕDI)]y8hMkֶw;ټl4ɀJ~,JFf{\"[Z%7!r Þ0bdd8,$,zA(n'9' 8h*]w7bfVk88ns4gmk+$hd;@03?BkFh4/>ϧh^rw%-Q&sU yb!"hLdTV]Wgi^T_09Q> bI QfI`’Ap#bV^Cy00->3hY s`4agiqR NH`bAY?LPŶQ#u{[{ ^_îWTVnčȱ\jm44KN_Ur?]GD3oAuc3xoMQLLDHEm7W~Vf< .i\fF9 L+jDPŢ(r]T Ÿ('ȂQ҉D0T)[JnضP 6~&k+5!wδ|],p#\Z]X t=o$Ԣ' *]hmWh4G4`mZAE~4fBn,% +vKm C]Ds:1K",9s9[%%aHDS6E$"ɪ}j:'-Q2My T:Os2qj_ِTr&&WZ@؎P#ۋ]>K=a)׿gЬKת+߬u mi44%rn(b%I&v^ AM5,'1 y[lMm=9޻c#R\zZmYV RQ!HSP>-}DPtS. 10 C0K jy8|5Hry&ܳ#/>G26`/Zl.ζVW?Q;SڮFh4͋i4Ԣ0 9n/jY`#vZgpm(Fo&8aLEC8a \͂ExHMs!w(vՙ i  ]TtK3"50 C> @J b(upq%&Hs:Ҟ#QxaPiոO6=]xi mi44e0;+JҬýi d[| 9j.%`) irl`sm  8ҵt`D201p%iB{lV3@%aAYiƙF?J Đ89qf386MВp-֞3S^]Η=yWg^^YP] 餳ڮFh4͋i4"*@khEϡE}/PݬIčb T/I7^}ؐj N"R[Ii !e#0M'4! @8"n{p[<[TqCaRBfRh"PFz^@{LV1A@6xЈW4`?ϯ|6Yv Y.n4ɀA\j4&)QJ%qnƓ,k'#IT)2mQʹX2~~vvY v7ax/ t]l!R)rCR̸T/7dt?Ҩke۶9 q$ʓ0AH d8yx ]" IDAT=~e[/%4; +h_:nWh4Ft~>FӟZ0 "aR /yFrjQm!b^& @g;]$,:Qע1 bJݨ!Í@|gN83(<8+HPaWi^a23(HI!/lJ&PSEXJу(\}`{ݑC#Đ0a)cA(Ҁ\۶S8av>֞>˭ ָ5|V>@{ܮ/__^ @m7dw XsmN_cVA0 j4FѼh?Fy_-J[2 L4Dt3b(gV_YߩԬ 8`Qܐ]Vrt?`9NەK6ery<'m&ּ3HP#QrC]M!=zԓ4%]2+{^@A*ܣL-616@!gsk-c7z70оq׾zt5$+|D#uH}Dn|5\_;!2`˸ݔҗK(XU9Rcϭݬ]{8c`@o4KNNgW#n <c)seOWQ g7a13K"̊.?PK)@ A*Y#2w 1q#0` ͧ2|P+1"N 9Ce0J.w[ҷ-yU8%H!Pͺ^:xs"X*9hHpx-qiת0) \p{!|<± , וqu JTY G+0dyB6`t C5q6EI9`⭉7tݶvOD7NNd eVk)Cۭ}2'X`h#b(>mi4D<!D+DZ ('3T~ j%%`PPj&2+KmT 𑤗Xx`6[_(S-XsNY >MY2PDQbu -D8v[~zvDmmƁ?c#kvay1ɝ:>6ߝ:|4Wr >RSm[ĭ:y?:(Y=֢e' 7kxk dZ|J.uP?{NpoO <6:6xe`G.pCn/+RjOJmEQ]gf1eLhmWh4G4KN 5S$c$ChpZA9$@ 6Tc*V aLDfxn,>-˱maO@^WыY^hYd{ dYz3[Ml!1jD>u 0aտ "os$3iѻON2B B2A:pG`)qMrz~W}[^i}>fg@X(8] >2RVe[dָ]2UVL11~l3m&qzrc_O7 l٢z-bn7mi4T6jm( %a}?~*Kli4ţ`dҐ(9D E~""l +X lVs^e!zn<!ZvKnȤ88aTuKXtYi1 X%K@;-~Ɖ DjIn^n%B3J"xoAdH8O8%?,..`H`ו&‘1q}mv8 gح)ZKR*G*VP9ZRd]]߯k~8a!ʅneA#5Zh4FtE4;~N!~zs*Wq0(jDlb%Qs73#[Y> N* Qu[Ŷm{v7zp{ͷZכH&R`|@L:DIp:հ$B&3OFK6[$T(`%ղq buN3x,M:E]`a@8>k>}C.\I}=_*uK TY||](fQ#9sIFor)OpO ATysfܺ߮;ъ%,d{r&6$ ^?P~,7/.XrI6dѧ]FE|s%jݽ v%37I i6.Y]B343 0 X¶i=@!c̦ԋ Ms KH܈b#H̭_E|w80v;}jjQ-~$` 85U]F{0qk5͢|3i8F7/0i;46 IuS ׶4? %Y/p/{8ZI-+[DhZJGc`:^/'K8>UHtQcꨑ0F=npELʪJX׸]m ԢtBxs"~Z1v5Fh4=~>FӗƍA!8aQL 7lnIvH9⇱ 3F'lȪ+ߞzc$"S EWD4fFnH~GH ' 3g 3jDJr=r-ڔ.~@D*— ىkeCbe:[q\vJ%B#Z6dt?蝷Ymi 4FuA: [ɱ 5LvwkiN"~{<p^(i8[UǝZ{k`! {pSZYlMiKlmgnX׸`# TOKSTkecc;uAlF2ЗƌSh!5@&,eA#m9I]#( ic%vv'lTk 7m3:q5_)k!ooffԿB8a';-AQ̕RUXܽ.0 @8\9a[0 #]I?ݎo3-Z8V]uvo'wXؐ2^ ;:pxfb-lMi*mꙶ a45_Nkr$lJh4mرѣGVs5g@2qępӒL.ݎ, f#q?YvS5ROgZ EbYj=?XG%d c3{]w2"P è Yq`;ZQi{Waew#6Z}]EjWݻJS@5,yUz0l:⻴VwH_Iȳٖn4o v[a#ؼx A!hWwH#ܽfgHG}GY< &!{Ÿ lDrC ۆO̶4vRxs@qKs709aPkvfkqyk1#vb=gƿaY}8aAB6ZrD%nt?4!K̴D" (oJdP)-J %F ~jj S VkH AE0zhO2+Ig=? w;;%(ʲqw:qjF3-SrE%VGvsysZtGw>l+x-+R 3{]ORePz5ҫf7v~bY)wرj4FlѣG{ oovϝ߸Χjaםm5QxI6c[_z&08Q՟9붇Yy;@e6#`CSvioz6i׭P;ςGsӇ< L?Vb:VhyQ* 2a4WHPL~$[r ad*V\G Ta0e±zx`RJ)eHF8a1&&?ӌӄϛ,cK7 yE5[Ġ#WMWV%RF8<<\.{]wwaW!Hd"LLLVRSjI keD$3 QEQ#5oT|T8qgZ[ µt dwڷڷ5 rOrh ¿^ZMj=ŞovmjddfrM$3ߢ6i8vwk bUto`=VBev'mfmn1h$rI-SmSjKW:L~a lYj>h4Fqgyp*3sUWgǿVtɞ3Q۪Shv#a T\›o^<3lB2R9mΗwv9}f?%5"'ͬif{~6qsڜmd2$sYH*:|cp\Q Rn0&ݏ5_;12Pk[ޔ'i@Ing}kPϴCP~vs3zGa՟q^5,miFπes J*0IP6_h/ߎ2C0Ο=`b"I4ր̀Kǐ}&ei10^d {n93Tv>2w07O75ZM\ZYymDą guկԛÿdZ;Ƅ{X' S'w@\i<' {=oO΃hIoV.^έk5~l|2_LI)$Nɟ oqzx+5~v(#Rտ*x[kNxvsSo|[R}QL~\H{AٖFq5_îv3Ǽv[>FhR?nmzvLJs~E斮V זXݼ]} V?N_]L-NtTn\u/S̫9%h/ !!D/mW^ vmCkIfeiqwlA rGp_rSWHپ13%'_zv9Tq2)' Q#Are1*%!ِyUȫK&t^"2!2$ˊjrCF2<4sk8N!r Ѷ4 9{~ʷ+'UFV,__^89?O w~,R3X"s ƨDM`](Zl~X%a@V[|N `^w<4nphe g9u}Y='ͣN0_M|0sEvjZui6{ )lu#MT2λ{3}ys]!Đm>'ʋ9udjgNyrWgPu:z>?G ?g~d]8,;͕xF2s{vT峳sʎtC1jgŹw#lk]^%WUs{}G=vG>m2|} h4Md<|crBC%M]UF30G̬Yۆ S=L2adF&q&nՄh[sm@ȑ>r4QU6Ae*m IDAT A(d*JWk LI0lqa2-n'b A$Fpԏ@!0P>zt cc;/-GX²4x#a.ٞDTDyꅿ.]pl~lW ̇k~8uWoyrZV җ¶+GLbrR9~q|Qmc\5{ȶ,03rߧ ?6ON#ab__Ux% 9m#cU-fio/^ZT˫WKl?Z9 `§sƎTV߇۳.Y"q`tw i emr6C{|u[{RTCܺn]j䯿$O)t{f@h4 p(Zv;w 췿~fT?zt\K;GZ߭uϝǺ rlYk~Sz3>c3p. aSm7pw}˩F08!L@!!m|ƪ%Ku*py*ñ.\͆vc'.F. Q$[OiA( J$Jdf0Յ,hΧ_ړel8*וf[ت*#8`E#fV!(m~,nr9a 5' / 83>`Ia֝se]#sHFly'nFsj<#njU˽FyfTʄXS-nKVZNc!em(Qj@% 7wq\15v@81dE y5.d_D!y(1 J Z GR~E.B\ .B's` xaxaЀ/쮴VڒSfΞG99G,)~& Ҵ,@("C&%iƆJ["ﮟdA: !DAPCwu*J"4;Q^ ?LÌBżYwHB2qo_LVq>}0z܏t(m|[ߖX%4)0<f oObHTgYk8Ɋ]l{nylM[[z.-ܮc1~s1uRf.T+$ Mi0 3F>'=v% )-jV3O Lܱ%E| CdKnb_ge r|*XFa3~yRJ'/(a]#a˂ ~;l mܮ`9a$ kC) R4mYzj tS]"~(}?j(#u9RMwoկ;z\9L=@JR}{oT[{>hW/BZyl@1ߚsVv=^t|ߟx{/ƩAoJ!_d0ىJHoܯ&`xJ#gΞ{ؕ~VZ{TT&T`W@J1K73s=2'N fdq._|@p=t(l~FWYrA@Xp}69۷2ضTxi c Qu_;xc^K}ney/E{T`s6}j(j$Ҳ/Ȃx؀U9)C'Y+?F60$%:nM! rjAAwt mA62`ED,p4(piӠNԣlc[n?-UݠAd&&a ߎQ<'z@w|)slQL D*DGC:4ܔe * 0Py4}az-O 0y?z OtPdk_S Q>Y8SzW.F=;y{|Obк~bLEۢì9Uon1ce=vnWvoSdP˷b~_h]8m CHgA饎H$yGd{A;Ѻֲ}1F^f HG0 |%Gۅ=I)(#"Jg!- 4(]$8sA5tJp?0MSZ(Σn Q@~;J"^L@&RKj:@>S^Lap]Rw u;lmok?>t?8bj8?r}E{myǾ\c؎% 0w]Y-/YE[GEي<@ Al<]?Gz_i93of7]n;7K4#60H h29(/ztF ӰĈ֢QPp:A=PuPtc#e!+%QSBEYW$gR4ҍt~f$Mζu{¿_rR{xiq[@ ܯ~"(فZyR YY*lEj/ qwſ]tku_YU^ק|U>9\E?\s˞%a7"۶~;_^u҉׫V-Ag߮e1c1ƞq]%пnmnY8m+/z=Du;Q=} y_Ͳx %ԺyetOWa #qFW"aHJ:Su+=Qg kRWdfa|YQeGwzD-ྲH} X\tX?}9({ R%B Az!s[!W"N"{[6Rˤ5۸ekO_ud@兿,wE_3&w'N ^ޫިz]`텿.ZP:yy>ARωԠWF\WTCG,ZNM~?l>.PƗnVL;1-w4T.Se7S~i5ͱm}@~pzw֫7DKN2أ*5|cSl? $xHPiHD„$B/t*/KY z d}zPE7#^-5VL+@CK c 6TЍX+^0`qbPJGd>~v_p)E pK(ls!)C@q;?0u{Y`VKo*;ޤ^[0t}W[P~, uyaJr#˟U]´"Ot?-- B,=qRެN9P\0RL5 by՛UkIoDT5H@D("Zmc~Igw{ -"U,h@W$0;_߯KQAoѓZ?~|l@H!*1Vwף}eYp(tEtMD4בዔ) VLC+˰"*]X3 7m-Ak)x$c%lp/.!Kew|'[-у$PJ-q"VHv7ԘnI_)+y"D_i]iIK,\~)-I֝XWޖ]{UsY"k& b^;].~.|ru+e/QT ]F;{k"|૿~=}uJCg'FJ#{^oOT^>]0}K{ut?_ObꃩFJwRooc)Ҳ]ﷻg9Qs;Rj_^99:8c1ƶ|g\wI!d汽.pZvzaIlu>PzwZ榴y輦}qRl&TݶŶzt/ dT(HEmwZ/As3[H CEy%  r}Y˜Kod\,:?0}_m@SB(#$ IiQgmxWuDgWKQ:+J.U)N=7GsY҉RqT7{W83x^7SLY2-Xy;\&:|=Dz-MiMTɯ޾]@Qs펾9: ;^Zb8WFݼqDп(L< nx= !LIgVlqzkn7h91@`g9Et4qn.Ĺ]c1%c=i^i!R*-]nW:8oꝔ0 Hw%"}X.&oTHGHՕ@69(l(S9|QC٢4{J:3HA/O(R:})@rI7 +QB4G8R*)$ "%2.Ͱ+QH~ছ)EQJ 8}n[/]AD`䕑-V4?.ϭ`ݮ(ҋ룁 >?h;[m'b蛣#8[\:E^y"r%h?g_.KAʜe$~.)+zDc[:D4EzRiY8Wd;!u:YR)_y6 auL8dU;B5oj[/C!~?BE*PA@ܾ{{ 55[@ G (ғ#-efMhZKJCӵ$)8FZk>%4<< 9jw&wy[Q# _unJ΀Hw߈J b~Y9Sѿ )ZBTsBns1cl+<{u-"@*XH®rYbbQo!U~\YU3NOG/.>g롬@"}w‚Az,z]^' @Bu~n7"PV6pݺ|PBk),X07%!l~{FNzxGAwk0E o],q @DiEֵ z !-L0FPJe%D! ei:  !UCw2l #OU;hMD9ƅ jPl]y9~M'$-A{psn1vtNAO׹]~ @ 1/e)ҢD$4yTm\aR`@&YPK6ND6.i+oE.u4!/dIC& ђ&iz[Y!+!Y99j(n  PB@DQZ&,,H"R 8*+R|D3QB暙ο,HfzE KXϏGT?C06J)=oF#.4u+yb~C?(֞pWnx?h9g襡o}pB;avc1>c==[d~_HʮDD9(V# Һ#$m"!o&D6(L}X!z,uy;0H<~ 2J)l1D!cb1FWޏ5'qD˴mwgu,oУ8hl2{X XZ+PifQҐaiN\@@*4Mq UUWA=HQd]fsT"r e7@%J_M1bK[ǍY 4L @Dq>BkO4t??kpv+Vo-ZRnp{60crE]v X VA0E 2);ҐznABOlHW @%Zjvgu \UA. =Ntқ_8):&LA=xn@?ViMQyl&j^u!(!O~^JYO2 S|:ؔ\^* C”`<6K"ٔtfqi _+ RJ9IZOӰ0Fό/5x2UoK)70"ZTo., ƍثyo,FBYv_s1c1ƞq]wi_=@]n7?,|=g !,Æ) D*(h Wlkk ^׋!qG@$|7tC?buO[t8˰bYӠtV`5xJ$XdAy~~~S(P2. ^`aRJ_,AwP,UWZ)UCQL(Ѕha2ba:@YmB] Gq@L9/'m8 IDAT;ݵYG(PnpA/mv"l˶NK|1cUF`RIcmP*2eabQH !$0(]G?-d*&!HRmZ ILJ0@ hrÅG*bA !1ܮ6w&KeQ !կ+H`! RepҜn=TCER*kx 1GbQw)O0 tsҭKVJ|bYV_2 C 3nzo 3 TO!2ikd"鉕I}Ā* Z :}ZslҶdVghzUE-!ziVh]Hgq6vc1>c=v1 DC!2'P,0([ߴ9 ń$׀-& H4뽥K7Ou;'$'KZ ;wK%%,ֹK$e5Y}Z/R1űč'q0ӟH bҵEQ^WYc҄5-tՅ| wKab0VJϻ#U֋NҽO?A 8LBAI jIo@z-hJÛM#|O}ro;w`^}C SK8c=vif"%LhOv`ܥ^J[|'S d }J+ tJ# )QPЫ}ul]sZa零_o‹ŢקqHEDyQ]wKIZͶMpG߄tP"a7su ,K/aw> F\]@U^o'-/5,zEmp?FͣII8$$GT@5엺gۂ$(t.Gkse8׻mquܑᑡҐv-pn1cq>3AQ#"unWRYh@L$|)] D5(Q΀oU J7m͐P.1v6O ?/t8s0t|HKR 0 #dZVͽ}!lj(].,g&TI[A@H'=C2 ̓!b4}o$mZ5@Y