Input for Deployment Plan Generator Executing Deployment Plan Generator

Generating Deployment Plans and Deploying Artifacts 6-5 artifacts in the PIP_NameCustomSupplementaryDP.xml using the deployment command and also undeploy the artifacts manually.

6.3 Generating Deployment Plans

This section discusses the input required for Deployment Plan Generator, the process for generating the deployment plan, and the output generated

6.3.1 Input for Deployment Plan Generator

Deployment Plan Generator takes the following four command line inputs. ■ BOM.xml: The BOM file is exported from the Project Lifecycle Workbench UI for the projects that are selected. BOM.xml contains the annotations to the services that are specified by users. These annotations are read by the Deployment Plan Generator to generate the deployment plan for the selected services. This deployment plan is used to configure the required configuration and deploy the services to the FMW server. ■ ODIBOM.xml: This ODIBOM file is to be generated manually. It should contain the list of artifacts to be imported to ODI along with the list of tokens to be replaced and encrypted. These annotations, in addition to some other information, are read by Deployment Plan Generator to generate the deployment plan for ODI. ■ File path for the Deployment Plan to be generated: The naming convention for the deployment plan is projectCodeDP.xml. The Deployment Plan Generator gives a warning message if the given input argument for deployment plan does not follow the naming standards. ■ File path of the HarvesterSettings.xml to be generated: The naming convention for the HarvesterSettings is projectCodeHS.xml. The Deployment Plan Generator gives a warning message if the given input argument for Harvester Settings does not follow the naming standards. Set the path for the file to AIA_ HOMEpipsprojectCodeHarvesterSettings as the deployment plan refers to this file during execution.

6.3.2 Executing Deployment Plan Generator

To execute Deployment Plan Generator: 1. Set environment variables by running the commands specific to your platforms: ■ For UnixLinux based systems, run source AIA_HOMEaia_ instancesinstance_namebinaiaenv.sh ■ For Microsoft Windows, run AIA_HOMEaia_instancesinstance_ namebinaiaenv.bat 2. Run the following command for executing the Deployment Plan Generator. This can be executed from any location. ant –f {AIA_HOME}InfrastructureInstallAIDAIADeploymentPlanGenerator.xml –Dinput=full file path of lifecycle BOM.xml -DDeploymentPlan=output file path of the generated deploymentplan. For example {AIA_ HOME}PIPSpipNameDeploymentPlanspipNameDP.xml -DHarvesterSettings=output file path of the generated HarvesterSettings file. Note: You cannot modify and add new non-native artifacts in the same AIA-shipped PIP_NameSupplemenatryDP.xml. 6-6 Developers Guide for Oracle Application Integration Architecture Foundation Pack For example {AIA_HOME}PIPSpipNameHarvesterSettingspipNameHS.xml [-DODIinput=ODI BOM file name along with absolute path of the file]

6.3.3 Output by Deployment Plan Generator