| Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.3 Part Number E28316-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations Release 11.3 Part Number E28316-03 |
|
|
PDF · Mobi · ePub |
This chapter discusses how to configure and deploy the Oracle Communications Order to Cash Integration Pack for Siebel Customer Relationship Management and Oracle Communications Order and Service Management (Comms Order to Cash: SBL CRM and OSM Pre-Built Integration).
This chapter includes the following sections:
The DCW screens prompt you to enter the data required for successful configuration of the Comms Order to Cash: SBL CRM and OSM Pre-Built Integration. Enter the details of the Comms Order to Cash: SBL CRM and OSM Pre-Built Integration screens below, take a printout and keep it ready when you run the DCW. This action enables faster and error free configuration.
All artifacts associated with the integration infrastructure components are deployed to the integration server. This screen contains the following fields:
Table 8-1 Integration Server Details Screen Fields
| Field | Description |
|---|---|
|
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: 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: The Admin Port is _____________________________________ |
|
Domain Name |
This is WebLogic server domain corresponding to the Admin Server. Example: The Domain Name is _____________________________________ |
|
Admin User |
This value is the WebLogic admin user name. To find this value contact your WebLogic administrator. The Admin User is __________________________________ |
|
Admin Password |
This value is the WebLogic admin password. To find this value contact your WebLogic administrator. The 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. |
Use this screen to enter details related to your Siebel CRM server instance. The screen contains the following fields:
Table 8-2 Siebel CRM Server Details Screen Fields
| Field | Description |
|---|---|
|
Siebel Host name |
This is a computer name of the Siebel host. For example: Siebel Host name is _____________________________ |
|
Siebel HTTP Port |
This value is the Siebel application port. For example: 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: Siebel EAI Application User is ___________________________ |
|
Siebel EAI Application Password |
This is the password for the EAI user. For example: Siebel EAI Application Password is ________________________ |
|
Siebel Version |
Version of application, for example Siebel 8.1.1 SIA. To find the value, contact your administrator. Kindly ensure that the value is only 10 character long. 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 ________________________ |
Use this screen to enter details related to your Siebel CRM database instance. The screen contains the following fields:
Table 8-3 Siebel CRM Database Details Screen Fields
| Field | Description |
|---|---|
|
Siebel Database Host |
This value is typically the computer name. For example: Siebel Database Host is _________________________________ |
|
Siebel Database Port |
This is the Siebel database port. For example: Siebel Database Port is _________________________________ |
|
Siebel Database SID |
This is the Siebel database system ID. For example: 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: Siebel Database Username is ______________________ |
|
Siebel Database Password |
This is the Siebel Database Password. For example: Siebel Database Password is _____________________ |
Use this screen to enter details related to your Oracle OSM server instance. The screen contains the following fields:
Table 8-4 Oracle OSM Server Details Screen
| Field | Description |
|---|---|
|
OSM CFS Admin Username |
This is the OSM admin user name used to connect to the OSM server. For example, OSM CFS Admin Username is _______________________________ |
|
OSM CFS Admin Password |
This is the OSM admin password used to connect to the OSM server. For example, 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 Provisioning Admin Username is ___________________________ |
|
OSM Provisioning Admin Password |
This is the admin password used to connect to the OSM Provisioning server. For example, 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. For example, 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, 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, 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, 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. For example, 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, 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, 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, OSM Provisioning WL JMS Queue Access Password is ___________________________ |
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.
The http.proxyHost and http.proxyPort properties are set during the configuration in the DCW. If you do not have a proxy server, leave these properties blank. This step is required before you can deploy the integration.
For more information, see Oracle Application Integration Architecture Process Integration Pack Utilities Guide.
Table 8-5 Session Pool Manager Details Screen Fields
| Field | Description |
|---|---|
|
Proxy host url |
This determines the server to be set in the system properties for Proxy host url is ___________________________ |
|
Proxy port |
This determines the port to be set in the system properties for the 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.
This section discusses the integration configuration and deployment process. There are two steps:
Configure your integration using the DCW.
Deploy the integration to the Fusion Middleware server.
The screens that appear prompt you to enter the data that is required for successful configuration of the Comms Order to Cash: SBL CRM and OSM Pre-Built Integration. Keep the completed worksheets of the Comms Order to Cash: SBL CRM and OSM Pre-Built Integration screens ready before you launch the DCW.
To configure the Comms Order to Cash: SBL CRM and OSM Pre-Built Integration:
Note:
If you are harvesting content to Oracle Enterprise Repository (OER), perform the first three steps. Else start from step 4.
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.
Replace WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=false" with WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true".
Restart the server.
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure installation environment.
Navigate to <AIA_HOME>/bin and run the command ./aiaconfig.sh for Linux based systems and aiaconfig.bat for Microsoft Windows.
This launches the AIA DCW.
Click Next.
Expand Communications Pre-built Integrations and select Comms Order to Cash: Siebel CRM and OSM.
Click Next.
To specify integration server details:
Enter information related to your integration server in the Integration Server Details screen.
Click Next.
To specify Siebel CRM server details:
Enter information about your Siebel CRM application in the Application Details - Siebel CRM screen.
Click Next.
To specify Siebel CRM database details:
Enter information about your Siebel CRM database in the Siebel CRM Database Details screen.
Click Next.
To specify Oracle OSM server details:
Enter Oracle OSM server information in the Oracle OSM Server Details screen.
Click Next.
Review the configuration information on the Configuration Summary screen.
Note:
If you want to make changes to the configuration, use the navigation pane on the left and select the screen you want to edit.
You can create a response file based on the input provided in the DCW and use it in future when you want to deploy the integration. You can configure using the steps described in Section 8.2.2, "Configuring using the Response File". Click Save Response File and save the response file with the name and location of your choice.
Click Configure to accept this configuration and begin the installation.
The system displays progress of configuration in the Configuration Progress screen.
The system displays any necessary warnings or errors. You can review the configuration log for additional details. The configuration log location is displayed in Configuration Progress screen.
When configuration process finishes without errors, the AIA DCW displays the Configuration Complete screen.
Click Finish to close the DCW.
To configure using the response file:
Open the response file.
When you create a response file through OUI, passwords get stored as <SECURE>.
Replace the password fields with actual passwords in the response file.
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Navigate to <AIA_HOME>/bin and run the command ./aiaconfig.sh <Response File Location and Name> for Linux based systems and aiaconfig.bat <Response File Location and Name> for Microsoft Windows.
Before deploying Comms Order to Cash: SBL CRM and OSM Pre-Built Integration, you must install the patch 16604969.
To deploy the integration to Fusion Middleware server:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Run the command for your platform.
Note:
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 8-6 Deployment Commands for the Comms Order to Cash: SBL CRM and OSM Pre-Built Integration
| Platform | Deployment Command |
|---|---|
|
Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit) |
$AIA_HOME/pips/Communications/O2A/DeploymentPlans/deployO2A.sh |
|
Microsoft Windows (32-bit) |
%AIA_HOME%\pips\Communications\O2A\DeploymentPlans\deployO2A.bat |
Review the log file in the location specified in the command or at the default location <AIA_Instance>/logs/O2ADP_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".
This section discusses post deployment configuration for Comms Order to Cash: SBL CRM and OSM Pre-Built Integration. This section includes:
This step is necessary to ensure that an transaction does not get auto tried using Database or SOA's inbuilt auto retry mechanism. Relying on Database or SOA's inbuild retry would cause undesirable effect on AIA flows and end to end transactionlity.
To suppress auto-retry and prevent multiple error notifications and trouble tickets:
Set the GlobalTxMaxRetry property for outbound adapters:
Log in to the Oracle Enterprise Manager Fusion Middleware Control.
Expand the SOA folder, right-click soa_infra.
Select SOA Administration, Common Properties.
Click More SOA Infra Advanced Configuration Properties.
Search for the GlobalTxMaxRetry property and set the value as 0 (zero).
Set the GlobalInboundJcaRetryCount property for inbound adapters:
Log in to the Oracle Enterprise Manager Fusion Middleware Control.
Expand the SOA folder, right-click soa_infra.
Select Administration, System Mbean Browser.
Search for oracle.as.soainfra.config, expand <Server>, expand AdapterConfig.
Select Adapter.
Search for the GlobalInboundJcaRetryCount property and set the value as 0 (zero).
Change Audit Level from Development to Production for soa infrastructure:
Log in to the Oracle Enterprise Manager Fusion Middleware Control.
Expand the SOA folder, right-click soa_infra.
Select SOA Administration, Common Properties.
Choose Production from the Audit Level list.
Click Apply.
Stop and Start the SOA and Admin Server so that your changes can take effect.
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.
Creating Destination Sort Key based on JMSPriority
Log in to <httphost>:<httpport>/console
Navigate to Services, Messaging, JMS Modules
Click AIAJMSModule
Click New and select Destination Sort Key option
Give a name AIA_SALESORDERJMSPRIORITY_KEY, click OK. The key is created
Click AIA_SALESORDERJMSPRIORITY_KEY link and choose JMSPriority from the Sort Key drop down list
Select Key Type as Int
Select Direction as Descending
Click Save
Attaching Destination Sort Key to JMS Queues
Click AIAJMSModule
Click AIA_CRTBO_OUT_JMSQ
In The Destination Keys section, newly created Key is displayed. Select and choose the key
Click Save
Repeat steps 2a to 2d for the following queues:
AIA_CRTCUST_OUT_JMSQ
AIA_CRTFO_OUT_JMSQ
AIA_FOPROV_OUT_JMSQ
Add the following security policy to have the Product Class SCE flow working from the OSM Design Studio.
Caution:
This step is only required if you are using OSM 7.0.2 version.
Log in to the Oracle Enterprise Manager Fusion Middleware Control (http://<host>:<port>/em).
Select the service QueryProductClassAndAttributesSCECommsReqABCSImpl.
Scroll down to the Services and References section and select the QueryProductClassAndAttributesSCECommsReqABCSImpl link.
Go to the Policies tab.
Go to the Directly Attached Policies section and click Attach/Detach.
Select oracle/no_authentication_service_policy and click Attach.
Click OK.
Verify that oracle/no_authentication_service_policy is attached.
Note:
This step is required if cluster is the deployment topology.
Perform the following steps to enable tunneling:
Configure http proxy host
Modify mod_wl_ohs.conf
For example, scratch/userid/Oracle/Middleware/Oracle_WT1/instances/instance1/config/OHS/ohs1/mod_wl_ohs.conf
Add the following location:
<Location / bea_wls_internal >
SetHandler weblogic-handler
<Node1Servername: Portno>,<Node2Servername: Portno>
WLLogFile /tmp/web_log.log
</Location>
Restart using ./opmnctl stopall, ./opmnctl startall
Configure WebLogic Server
Log in to WebLogic Server console.
Click Admin and each manager server.
Click Protocols, HTTP, Enable Tunneling.
Save the configuration.
Restart Admin and managed servers.
Configure OSM SAF Remote Context if OSM Fulfillment system is clustered
Navigate to console <host>:<port>/console.
Navigate to Home, JMS Modules, AIAJMSModule, OSM (SAF Remote Context).
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.
Save and Release the configuration.
Configure SOM SAF Remote Context if OSM Provisioning system is clustered
Navigate to console <host>:<port>/console.
Navigate to Home, JMS Modules, AIAJMSModule, SOM (SAF Remote Context).
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.
Save and Release the configuration.
After deploying Comms Order to Cash: SBL CRM and OSM Pre-Built Integration, you must deploy the following patches:
11843588
12755349
To verify the Comms Order to Cash: SBL CRM and OSM Pre-Built Integration deployment:
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.
Confirm that the Comms Order to Cash: SBL CRM and OSM Pre-Built Integration components were successfully deployed.
Navigate to the Oracle Enterprise Manager Fusion Middleware Control: (http://<server name>:<port number>/em/).
Log in with the server admin user name. For access details, contact the system administrator.
Expand Farm_soa_domain, SOA, soa-infra, Default and look for items listed below.
AIAOrderFalloutJMSBridgeService
CreateFaultNotificationLFCommsJMSConsumer
CreateOrderFalloutNotificationOSMCFSCommsJMSConsumer
CreateOrderFalloutNotificationOSMCFSCommsJMSProducer
CreateOrderFalloutNotificationOSMCFSCommsProvImpl
CreateTroubleTicketOSMCFSCommsJMSConsumer
CreateTroubleTicketRespOSMCFSCommsJMSProducer
CreateTroubleTicketSiebelCommsProvABCSImpl
CustomerPartyEBSV2
ProcessFOBillingAccountListRespOSMCFSCommsJMSProducer
ProcessFulfillmentOrderBillingAccountListOSMCFSCommsJMSConsumer
ProcessFulfillmentOrderBillingOSMCFSCommsJMSConsumer
ProcessFulfillmentOrderBillingResponseOSMCFSCommsJMSProducer
ProcessFulfillmentOrderUpdateOSMCFSCommsJMSProducer
ProcessFulfillmentOrderUpdateOSMPROVCommsJMSConsumer
ProcessProvisioningOrderOSMCFSCommsJMSConsumer
ProcessProvisioningOrderOSMPROVCommsJMSProducer
ProcessSalesOrderFulfillmentOSMCFSCommsJMSProducer
ProcessSalesOrderFulfillmentSiebelCommsJMSConsumer
ProcessSalesOrderFulfillmentSiebelCommsReqABCSImpl
ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl
QueryClassificationListSiebelCommsProvABCSImpl
QueryCustomerPartyListSiebelProcCommsABCSImplV2
QueryProductClassAndAttributesSCECommsReqABCSImpl
QuerySpecificationListSiebelCommsProvABCSImpl
QuerySpecificationValueSetListSiebelCommsProvABCSImpl
SyncAccountSiebelAggregatorAdapter
SyncAccountSiebelReqABCSImpl
SyncAcctSiebelAggrEventConsumer
SyncAddressSiebelAggregatorAdapter
SyncBPSiebelAggregatorAdapter
SyncContactSiebelAggregatorAdapter
SyncCustomerSiebelEventAggregator
SyncItemCompositionListSiebelCommsProvABCSImpl
TransformAppContextSiebelService
UpdateSalsOrderOSMCFSCommsJMSConsumer
UpdateSalesOrderSiebelCommsProvABCSImpl
UpdateTroubleTicketOSMCFSCommsJMSConsumer
UpdateTroubleTicketSiebelCommsProvABCSImpl
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:
Log in to Oracle Enterprise Manager Fusion Middleware Control.
Expand WebLogic Domain.
Select soa_domain.
Right-click soa_domain.
Select Web Services, Policies.
Verify Service Policy attachment.
Find no_authentication_service_policy in the list of policies.
Click the number in Attachment Count column.
This opens Usage Analysis screen.
Change the Subject Type list box to SOA Service (1).
Validate that all the composites are listed with local attachment to this service policy.
Verify Client Policy attachment
Navigate back to Web Services Policies screen.
Navigate to Applies To LOV, select Service Clients and hit enter. Find no_authentication_client_policy.
Click the number in Attachment Count column.
This opens Usage Analysis screen.
Change the Subject Type list box to SOA Reference.
Validate that all the composites are listed with local attachment to this client policy and attached to the correct references.
Table 8-7 No Authentication Service Policy Attachments for Comms Order to Cash: SBL and OSM
| Composite | Service Policy |
|---|---|
|
SyncCustomerSiebelEventAggregator |
oracle/no_authentication_service_policy |
Table 8-8 No Authentication Client Policy Attachments for Comms Order to Cash: SBL CRM and OSM
| Composite | Service 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 |
Note:
In the Oracle Enterprise Manager Fusion Middleware Control, the ProductOptimizedSyncPriceListListSiebelCommsProvABCSImpl composite is listed with port SWIPriceListItem and SWIProductImport.
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.
To undeploy the integration from Fusion Middleware Server:
Navigate to <AIA_Instance>/bin and run the command source aiaenv.sh for Linux based systems and aiaenv.bat for Microsoft Windows to configure the environment.
Run the command for your platform.
Table 8-9 Undeployment Command for the Comms Order to Cash: SBL CRM and OSM Pre-Built Integration
| Platform | Undeployment Command |
|---|---|
|
Linux x86 Solaris SPARC (64-bit) IBM AIX Based Systems (64-bit). HP-UX 11i (64 bit) |
$AIA_HOME/pips/Communications/O2A/DeploymentPlans/undeployO2A.sh |
|
Microsoft Windows (32-bit) |
%AIA_HOME%\pips\Communications\O2A\DeploymentPlans\undeployO2A.bat |
Restart the SOA server.
Uninstall the integration following the instructions in the Chapter 37, "Uninstalling Oracle AIA"
|
 Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
