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:

• Section 24.1, "Configuring Oracle Data Integrator (Optional)"

• Section 24.2, "Deployment Configuration Wizard"

• Section 24.3, "Configuring and Deploying the Order to Cash: Siebel CRM - EBS"

• Section 24.4, "Performing Postdeployment Configurations"

• Section 24.5, "Verifying Deployment"

• Section 24.6, "Undeploying the Order to Cash: Siebel CRM - EBS PIP"

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 IDs	Work 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

Field	Description
Admin Host Name	Specifies where the admin server resides. This can be a remote server or the same system where the AIA Pre-Built Integrations Installer is launched. Example: server1.company.com. The Admin Host Name is _________________________________
Admin Port	This is the port number on which the Weblogic Admin server is started. To find this value contact the WebLogic administrator. Example: 7001. The Admin Port is _____________________________________
Domain Name	This is WebLogic server domain corresponding to the Admin Server. Example: domain1 The Domain Name is _______________________________
Admin User	This value is the WebLogic admin user name. To find this value contact your WebLogic administrator. The Admin User is __________________________________
Admin Password	This value is the WebLogic admin password. To find this value contact your WebLogic administrator. The password is _____________________________________
Managed Server	After you enter the Admin Host Name, Admin Port and Admin User, this field populates with managed servers for the domain. Select the managed server from the list. If you are deploying the 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

Field	Description
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

Field	Description
E-Business Suite Database Host	Specifies the system name. To find this value, contact the database administrator. Example: server1.oracle.com. E-Business Suite Database Host is ________________________
E-Business Suite Database Port	To find this value, contact the database administrator. Example: 1521. E-Business Suite Database Port is _______________________
E-Business Suite Database Username	To find this value, contact the database administrator. Example: APPS. 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

Field	Description
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)

Field	Description
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

Field	Description
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

Field	Description
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

Field	Description
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

Field	Description
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

Field	Description
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

Field	Description
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

   Platform	Deployment 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

      Composite	Service 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

      Composite	Service 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

      Composite	Reference	Client 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

      Composite	Reference	Client 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

      Composite	Reference	Client 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 environment.

2. Run the command for your platform.

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

   Platform	Undeployment 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

   Platform	Undeployment 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"