3 Pre-built Integration Deployment

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 AIA Install Driver (AID) for deployment.

In addition, AIAInstallProperties.xml is passed as a parameter to the AID for deployment.

You use the configuration wizard to configure AIAInstallProperties.xml with the pre-built integrations server details. The AID does not perform any checks to validate that AIAInstallProperties.xml has been configured with the corresponding pre-built integrations server details.

The 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 Service Oriented Architecture (SOA) instance, refer to My Oracle Support note 881206.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 impact on common PIP or DI components, such as common routing rules.

3.2 Pre-built Integration Undeployment

PIPs are undeployed using undeployment plans. The undeployment plan and the configured AIAInstallProperties.xml file are passed as parameters to the AID for undeployment.