3 Pre-built Integration Deployment

This section discusses the deployment of the pre-built integration included in this release.

The deployment of a pre-built integration 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 using the Configuration Wizard. AID does not perform any checks to validate the AIAInstallProperties.xml has been configured with the corresponding pre-built integrations Server details.

The pre-built integration 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.

3.1 Pre-built Integration Codeployment

Codeployment is also available among PIPs or Direct Integrations (DIs) when neither is part of a pre-built integration group. Before you install multiple PIPs or DIs on a single SOA instance, refer to My Oracle Support note 1567671.1 to review the integration PIP Codeployment Matrix 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.

3.2 Pre-built Integration Undeployment

The undeployment of the PIP is done through the undeployment plan. The undeployment plan and the configured AIAInstallProperties.xml are passed as parameters to AID for undeployment.

The generated deployment plan generates an undeployment plan with the install deployment plan.