|Oracle® Application Integration Architecture Installation and Upgrade Guide for Pre-Built Integrations
Part Number E28316-03
|PDF · Mobi · ePub|
This guide provides an overview of the Oracle Application Integration Architecture (AIA) Pre-Built Integrations installation process that consists of installation, configuration and deployment.
This chapter includes the following sections:
For information about how to migrate 2.5 pre-built integrations to the 11.3 version, see Oracle Fusion Middleware Migration Guide for Oracle Application Integration Architecture Foundation Pack.
Pre-Built Integrations installation consists of three stages:
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:
Process Integration Packs
Partial Process Integration Packs
The Pre-Built Integrations 11.3 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 II, "Configuring and Deploying Pre-Built Integrations" and Part III, "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 II, "Configuring and Deploying Pre-Built Integrations" and Part III, "Configuring and Deploying AIA RV 3.1.1 PIPs and DIs"of this guide.
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.
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 II, "Configuring and Deploying Pre-Built Integrations" and Part III, "Configuring and Deploying AIA RV 3.1.1 PIPs and DIs".
When you configure multiple pre-built integrations, the following occurs:
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.
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".
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.
For EBS that are not shared between the pre-built integrations, all the default routing rules delivered with the pre-built integrations are deployed.
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
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.
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.
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 PIP 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.
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:
Global security policies are automatically attached to all composites matching the AIA naming conventions.
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".
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.
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 II, "Configuring and Deploying Pre-Built Integrations" and Part III, "Configuring and Deploying AIA RV 3.1.1 PIPs and DIs" of this guide.
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.3 release and includes links to pre-built integration specific master notes. The specific master notes for each pre-built integration include links to:
Software downloads and required patches
Known issues and workarounds
Before starting the installation process, review the master note for your specific pre-built integration.