This chapter provides an overview of the Oracle Application Integration Architecture (Oracle AIA) pre-built integrations installation procedure.
Oracle AIA is an Oracle Communications Solutions Integrations framework that provides pre-built integrations using standard integration patterns, business processes, orchestration logic, and common objects and services to connect Oracle applications.
Oracle Communications Solutions Integrations is a set of integration frameworks, technologies, and tools that lets you design and build integrations that connect Oracle applications to support end-to-end business processes for communications service providers across operations support systems and business support systems.
Oracle AIA installation consists of the following tasks:
Planning your installation, reviewing system requirements, and installing required prerequisite software. See "Oracle AIA System Requirements".
Performing pre-installation tasks. See "Oracle AIA Pre-Installation Tasks".
Installing Oracle AIA:
Downloading the Oracle AIA media pack.
Running the Installer. See "Installing Oracle AIA".
The Installer copies the installation files for all Oracle AIA pre-built integrations to the chosen installation directory.
Running the Configuration Wizard and running deployment scripts. See "Configuring and Deploying Pre-Built Integrations".
You choose which pre-built integration options to configure and deploy.
The Configuration Wizard updates the Oracle AIA properties file with your system details. The deployment scripts deploy the pre-built integrations and their configuration details to the integration server.
Performing post-installation tasks. See "Oracle AIA Post-Installation Tasks".
Verifying the installation. See "Verifying Oracle AIA Installation".
The Installer copies the files for all of the pre-built integrations and installs all of the infrastructure components required to support these options, including standard data objects and service definitions.
After copying the files using the Installer, you configure any of the following pre-built integration options for Oracle Communications using the Configuration Wizard:
Order to Cash options for:
Oracle Communications Billing and Revenue Management (BRM)
Oracle Communications Order and Service Management (OSM)
Oracle Siebel CRM
Agent-Assisted Billing Care
You can configure a single option at a time or multiple options at the same time.
After configuring a pre-built integration, you deploy it to the integration server using a deployment script. The Installer provides deployment scripts for the pre-built integration options.
When you configure pre-built integrations using the Configuration Wizard, you can only provide information about one instance of each application. After completing configuration with the Configuration Wizard, you can manually configure pre-built integrations to connect to multiple application instances. You must customize the deployment commands to configure the specific pre-built integrations to connect to multiple application instances.
For an example of configuring Oracle AIA to connect to multiple instances of an application, see the discussion of configuring multiple BRM instances for communications integrations in Oracle Application Integration Architecture Order to Cash Integration Pack Implementation Guide.
You deploy pre-built integrations by running scripts that use deployment plans. Each pre-built integration comes with a main deployment plan, an optional supplementary deployment plan, and an optional conditional policy file.
You can deploy two or more functionally interoperable pre-built integrations on the same Oracle Service Oriented Architecture (SOA) instance. This co-deployment allows the integration services to work together to fulfill end-to-end business processes. The Order to Cash pre-built integration can be co-deployed.
For more information about functional interoperability, including which pre-built integrations are functionally interoperable, see Oracle AIA Functional Interoperability Configuration Guide.
To install multiple options that are not functionally interoperable, you must install each option on a separate SOA instance. If you install unsupported combinations on a single SOA instance, you are responsible for making custom changes to accommodate any resulting functional impact on common components, such as routing rules.
Oracle AIA composites are protected by authentication through Oracle Web Services Manager security policies. When you deploy pre-built integrations, the default policies are automatically applied as follows:
Global security policies are automatically attached to all composites matching the Oracle 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 Oracle AIA naming conventions.
For more information on how global and local security policies are attached during deployment, see the discussion of working with security in Oracle Fusion Middleware Developer's Guide for Oracle SOA Core Extension.
Oracle recommends the following:
Harden the services with message protection in your production environment. Before modifying the default security policies, you must understand Oracle Web Services Management security policy configuration and the global and local deployment strategies. Changes to the default policies without proper understanding could impact the integration's expected behavior.
Do not completely disable default security policies.
Validate that the default security policies are correctly deployed before running your production system.
For more information about security policies, see Oracle Fusion Middleware Securing Web Services and Managing Policies with Oracle Web Services Manager.
To undeploy a pre-built integration, you must undeploy all options included in it by using the undeployment plan. The undeployment plan and the AIAInstallProperties.xml file are passed as parameters to the Oracle AIA Install Driver for un-deployment.
See "Uninstalling Oracle AIA" for more information about undeploying and uninstalling pre-built integrations.
You can deploy pre-built integrations directly to an existing SOA cluster.
You deploy pre-built integrations to nodes that were configured when setting up the SOA cluster. The nodes may be spread across different physical servers for higher availability, or the nodes may be on the same physical server for greater throughput.
For more information about deployment topology and setting up SOA clusters, see Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite. For more information about preparing a SOA cluster for pre-built integrations, see "Cluster Pre-Installation Tasks".
Because the deployment is targeted to the entire cluster, you run the deployment scripts only once for the entire cluster. The scripts deploy the pre-built integrations to all nodes of the cluster at the same time.
The placeholders in Table 1-1 are used in this guide.
Table 1-1 Placeholders Used in This Guide
| Placeholder | Directory Description |
|---|---|
|
Install_home |
The directory in which the Oracle AIA software is installed. This is typically the Oracle base directory for AIA Communications and it should be outside the Home directory of Oracle Service Oriented Architecture (SOA). This directory includes the comms_home directory, which the commsenv script sets as the COMMS_HOME environment variable. |
|
MW_home |
The directory in which Oracle Fusion Middleware components are installed. This directory contains the base directory for Oracle WebLogic Server, among other files and directories. |
|
JDev_home |
The directory in which Oracle JDeveloper is installed. |
|
domain_home |
The directory that contains the configuration for the domain onto which Oracle AIA is deployed. The default is MW_home/user_projects/domains/domain_name (where domain_name is the name of the Oracle AIA domain), but it is frequently set to some other directory at installation. |