Understanding the ODI Deployment Plan

Generating a Deployment Plan for ODI 7-5 To generate a combined Deployment Plan for Project Lifecycle Workbench BOM and ODI BOM, execute the following command: ant –f AIA_ HOMEInfrastructureInstallAIDAIADeploymentPlanGenerator.xml -Dinput=BOM file name along with absolute path of the file -DODIinput=ODI BOM file name along with absolute path of the file -DDeploymentPlan=output path for the Deployment plan along with file name -DHarvesterSettings=output path for the runtime Harvester setting file along with file name

7.3.1 Understanding the ODI Deployment Plan

Once you generate a deployment plan for the sample ODIBOM.xml file discussed in Section 7.2, Generating the BOM for ODI the deployment plan shown in Example 7–4 is generated. Example 7–4 Sample Deployment Plan DeploymentPlan component=ODISample version=3.0 Configurations replace token=siebel.db.username value={siebel.db.username} dir={AIA_HOME}PIPSCoreDISRetailToPSFTFinmaster replace token=siebel.db.username value={siebel.db.username} dir={AIA_HOME}PIPSCoreDISRetailToPSFTFinwork replace token=brm.username value={brm.username} dir={AIA_ HOME}PIPSCoreDISRetailToPSFTFinmaster replace token=brm.username value={brm.username} dir={AIA_ HOME}PIPSCoreDISRetailToPSFTFinwork replace token=ebiz.db.username value={ebiz.db.username} dir{AIA_ HOME}PIPSCoreDISRetailToPSFTFinmaster replace token=ebiz.db.username value={ebiz.db.username} dir{AIA_ HOME}PIPSCoreDISRetailToPSFTFinwork UpdateOdiParams projectCode=ODISample OdiEncrypt property=siebel.db.password masterRepositoryLoc={AIAHome}PIPSCoreDISRetailToPSFTFinmaster workRepositoryLoc={AIAHome}PIPSCoreDISRetailToPSFTFinwork OdiEncrypt property=ebiz.db.password masterRepositoryLoc={AIAHome}PIPSCoreDISRetailToPSFTFinmaster workRepositoryLoc={AIAHome}PIPSCoreDISRetailToPSFTFinwork OdiEncrypt property=brm.password masterRepositoryLoc={AIAHome}PIPSCoreDISRetailToPSFTFinmaster workRepositoryLoc={AIAHome}PIPSCoreDISRetailToPSFTFinwork copy todir={odi.dvm.path} fileset dir={AIA_ HOME}PIPSIndustryCommunicationsDISCollectionssetupxmls include name=COLLECTION_ACTIONNAME.xml fileset copy Configurations Deployments OdiImportObject import_mode=SYNONYM_INSERT_UPDATE path id=masterFiles Note: While generating a combined Deployment Plan, ensure that the PIP_Name attribute in the root tags of both BOMs is the same. The Deployment Plan Generator generates a single deployment plan for both the Project Lifecycle Workbench BOM and ODI BOM. 7-6 Developers Guide for Oracle Application Integration Architecture Foundation Pack pathelement location={AIA_ HOME}PIPSCoreDISRetailToPSFTFinmasterCONT_Global.xml pathelement location={AIA_ HOME}PIPSCoreDISRetailToPSFTFinmasterCONT_RETL_TO_PSFT.xml pathelement location={AIA_ HOME}PIPSCoreDISRetailToPSFTFinmasterCONT_RETL_TO_PSFT_DB2.xml pathelement location={AIA_ HOME}PIPSCoreDISRetailToPSFTFinmasterCONN_PEOPLESOFTDS.xml pathelement location={AIA_ HOME}PIPSCoreDISRetailToPSFTFinmasterCONN_PSFT_DB2_DS.xml pathelement location={AIA_HOME}PIPSCoreDISRetailToPSFTFinmaster LSC_Peoplesoft.xml pathelement location={AIA_HOME}PIPSCoreDISRetailToPSFTFinmaster LSC_PSFT_DB2_LogicalSchema.xml pathelement location={AIA_HOME}PIPSCoreDISRetailToPSFTFinmaster LSC_Retail.xml path OdiImportObject OdiImportObject workrepname={pips.ODISample.odi.workrep.name} import_ mode=SYNONYM_INSERT_UPDATE path id=workFiles pathelement location={AIA_HOME}PIPSCoreDISRetailToPSFTFinwork MFOL_OracleRetailToPeopleSoft.xml pathelement location={AIA_HOME}PIPSCoreDISRetailToPSFTFinwork MFOL_ReIMToPeopleSoftAccountingEntry.xml pathelement location={AIA_HOME}PIPSCoreDISRetailToPSFTFinwork MFOL_ReIMToPSFTInvoice.xml pathelement location={AIA_HOME}PIPSCoreDISRetailToPSFTFinwork MFOL_RMSToPeopleSoftAccountingEntry.xml pathelement location={AIA_HOME}PIPSCoreDISRetailToPSFTFinwork CONN_PSFT_DB2_DS.xml pathelement location={AIA_HOME}PIPSCoreDISRetailToPSFTFinwork PROJ_ReIMToPeopleSoftInvoiceProject.xml pathelement location={AIA_HOME}PIPSCoreDISRetailToPSFTFinwork PROJ_ReIMToPSFTAcctEntryProject.xml pathelement location={AIA_HOME}PIPSCoreDISRetailToPSFTFinwork PROJ_RMSToPSFTAcctEntryProject.xml path OdiImportObject Deployments The macros in the generated deployment plan handle the following tasks.

7.3.1.1 OdiImportObject

The OdiImportObject macrodef shown in Example 7–5 imports the contents of an export file into a repository. This macrodef internally invokes the OdiImportObject utility provided as a part of Oracle Data Integrator tools. Example 7–5 Sample Syntax of OdiImportObject OdiImportObject workrepname=work_rep_name import_mode=SYNONYM_INSERT_ UPDATE path id=workFiles pathelement location={AIAHome]PIPSCoreDISRetailToPSFTFinsrcworkMFOL_ OracleRetailToPeopleSoft.xml pathelement location={AIAHome]PIPSCoreDISRetailToPSFTFinsrcworkMFOL_ ReIMToPeopleSoftAccountingEntry.xml path OdiImportObject Generating a Deployment Plan for ODI 7-7 import_mode is optional. If you do not include import_mode, the value will be set to SYNONYM_INSERT_UPDATE. You should include all the names to be listed using the pathelement tags. For the master repository files, workrepname attribute should not be present.

7.3.1.2 OdiEncrypt

The OdiEncrypt macrodef encrypts the passwords and replaces the password tokens in the ODI artifacts with the encrypted values. When AIA Install Driver is launched it decrypts all of the values in AIAInstallProperties.xml and loads them into memory. Using OdiEncrypt macrodef, the values in memory will be encrypted and the files in master and work repository directories are updated with the new values. Syntax of OdiEncrypt: OdiEncrypt property=property name in AIAInstallProperties.xml masterRepositoryLoc= workRepositoryLoc=

7.3.1.3 UpdateOdiParams

UpdateOdiParams macrodef updates the odiparams.shbat script under ODI_ HOMEagentbin with the current ODI server details. It picks up the required properties from AIAInstallProperties.xml. The password fields will be encrypted using the ODI_HOMEagentbinencode.shbat script. The syntax of UpdateOdiParams will be as below: UpdateOdiParams projectCode=ODISample The replace tokens, UpdateOdiParams, ODIEncrypt and Dvm Copy tags are generated in the Configurations section. The ODIImportObject tags that are used for ODI artifacts import are generated in the Deployments section. Once the deployment plan is generated, deploy the services using commands specified in Section 6.5, Deploying Artifacts 7-8 Developers Guide for Oracle Application Integration Architecture Foundation Pack 8 Configuring and Using Oracle Enterprise Repository as the Oracle AIA SOA Repository 8-1 8 Configuring and Using Oracle Enterprise Repository as the Oracle AIA SOA Repository This chapter includes the following sections: ■ Section 8.1, Introduction to Using Oracle Enterprise Repository as the Oracle AIA SOA Repository