Introduction Oracle Fusion Middleware Online Documentation Library

6 Generating Deployment Plans and Deploying Artifacts 6-1 6 Generating Deployment Plans and Deploying Artifacts This chapter discusses the approach to create Deployment Plans for SOA artifacts extended using AIA Extension mechanism. AIA Deployment Plan Generator utility helps generate Deployment Plans for extended artifacts and AIA Installation Driver AID helps deploy them. The chapter also outlines the approach to deploy non-native SOA artifacts. The Process Integration Packs PIPs or direct integrations delivered by Oracle AIA use the features outlined in this chapter to deploy both native SOA artifacts and non-native artifacts. This chapter includes the following sections: ■ Section 6.1, Introduction ■ Chapter 6.2, Extending Deployment Plans ■ Chapter 6.3, Generating Deployment Plans ■ Section 6.4, Generating Conditional Deployment Plans ■ Chapter 6.5, Deploying Artifacts ■ Chapter 6.6, Undeploying Services

6.1 Introduction

AIA Project Lifecycle Workbench contains the integration specific details of the PIP or direct integrations, like the business tasks involved and the service components involved in each business task. Project Lifecycle Workbench supports only Oracle SOA artifacts which are created using FMW technologies such as BPEL or Mediator. These are called native artifacts and they are supported by AIA Foundation Pack tools such as Project Lifecycle Workbench, Harvester, Deployment Generator, and AID. When a composite is harvested, the annotation details of the composite are stored in the lifecycle database. The Bill of Material BOM of a PIP can be exported as BOM.xml using the Generate BOM feature in AIA Lifecycle Workbench. The existing artifacts can be modified and new natively supported artifacts can be added using AIA Lifecycle Workbench and a BOM.xml file can be generated. The BOM.xml file consists of a list of artifacts that constitute a project and their ensuing annotations. Deployment Plan Generator reads the annotations and other information in BOM.xml file as input and generates deployment plan for the selected services. The deployment plan is used to perform the required configurations and deploy the services to the Fusion Middleware server using AID. 6-2 Developers Guide for Oracle Application Integration Architecture Foundation Pack Figure 6–1 illustrates the flow for extending and deploying native artifacts. Figure 6–1 Extending and Deploying Native Artifacts You may need to deploy artifact types that are not supported by the Project Lifecycle Workbench and AIA Harvester. For instance, your integration may require the use of Java Web Services or interaction with third party services. In such cases, the deployment of those artifacts is supported by invoking custom scripts such as Shell scripts or ANT scripts from the Deployment plan. AID supports deployment of these supplementary artifacts. However, you must modify and add new non-native artifacts outside AIA Lifecycle Workbench. Figure 6–2 illustrates the flow for extending and deploying non-native artifacts. Generating Deployment Plans and Deploying Artifacts 6-3 Figure 6–2 Extending and Deploying Non-native Artifacts The following files are used in the deployment plan generation and deployment of AIA artifacts: ■ PIP_NameDP.xml: This deployment plan file orchestrates the deployment of natively supported services and the configuration required for those services. Oracle AIA delivered PIPs usually have their deployment plans under AIA_ HOMEPIPSpip nameDeploymentPlans. Oracle AIA Foundation Pack customers are also advised to save their Deployment plans under the corresponding folder in the AIA_HOMEPIPS folder. ■ PIP_NameSupplementaryDP.xml: Supplementary Deployment Plan contains configuration required for deployment of non native services. A PIP installation may or may not constitute the deployment of non-native artifacts. If it does, then the corresponding PIP supplies a Supplementary deployment plan at AIA_ HOMEPIPSpip nameDeploymentPlans. ■ PIP_NameHS.xml: HS is a Harvester Settings file that harvests the deployed services to OER for a PIP project from the SOA run time. When a PIP is installed, the file can be located in AIA_HOMEPIPSpip nameHarvesterSettings folder. 6-4 Developers Guide for Oracle Application Integration Architecture Foundation Pack For more information about the Harvester settings file, see Chapter 3, Harvesting Oracle AIA Content You can also generate deployment plans for ODI and include them in your deployment plans. For information on generating a deployment plan for ODI refer to Chapter 7, Generating a Deployment Plan for ODI

6.2 Extending Deployment Plans