How to Import Seed Data

Working with Project Lifecycle Workbench Seed Data 5-9 Export functional decomposition data by project code and version to a named output file: ■ For Linux: PLWExport.sh -p Project Code -v version -s fd -o output file name For Windows: PLWExport.bat -p Project Code -v version -s fd -o output file name Export BOM and functional decomposition data by project code to a named output file: ■ For Linux: PLWExport.sh -p Project Code -s all -o output file name For Windows: PLWExport.bat -p Project Code -s all -o output file name Export functional decomposition data by project code to a named output file: ■ For Linux: PLWExport.sh -p Project Code -s fd -o output file name For Windows: PLWExport.bat -p Project Code -s fd -o output file name Export BOM and functional decomposition data by UUID to a named output file: ■ For Linux: PLWExport.sh -u UUID value -s all -o output file name For Windows: PLWExport.bat -u UUID value -s all -o output file name Export functional decomposition data by UUID to a named output file: ■ For Linux: PLWExport.sh -u UUID value -s fd -o output file name For Windows: PLWExport.bat -u UUID value -s fd -o output file name

5.4 How to Import Seed Data

Objective Import Project Lifecycle Workbench seed data. Prerequisites ■ Complete the steps covered in Section 5.2, How to Set Up an Environment to Export or Import Seed Data for the First Time. ■ Ensure that the seed data file to be imported exists. For information about how to export seed data, see Section 5.3, How to Export Seed Data. Actors ■ Integration developers ■ System administrators 5-10 Developers Guide for Oracle Application Integration Architecture Foundation Pack To import Project Lifecycle Workbench seed data: 1. Access a command window on the server into which you want to import seed data. 2. Navigate to the PLWImExport folder: AIA_ HOMEInfrastructureLifeCyclePLWImExport. 3. Run PLWImport to perform the seed data import. PLWImport provides a set of import commands, as discussed in Table 5–2 . You must provide -f or -d in the PLWImport command. If you do not specify -f or -d, PLWImport displays an error message. The -f and -d commands are mutually exclusive, meaning they cannot be used together.

4. All imported seed data includes associated UUIDs.

If a UUID associated with imported data already exists in the target Project Lifecycle Workbench instance, the PLWImport updates data associated with the existing UUID. Table 5–2 PLWImport Commands Command Description -f file name or file path Use to import a single file. If you provide a file name, PLWImport will look for the file name in the directory from which the PLWImport was invoked and will attempt to perform the import. For example, in Linux: .PLWImport.sh -f import1.xml If you provide a file path, PLWImport will look for the file name in that specified directory and will attempt to perform the import. You can provide a full file path that provides a path to the file from the root of the file system. For example, in Linux: .PLWImport.sh -f homeuserplwdataimport1.xml You can provide a relative file path that provides a path to the file relative to the directory from which PLWImport was invoked. For example, in Linux: .PLWImport.sh -f dataimport1.xml -d directory path Use to import multiple files stored in a directory. If you provide a directory path, PLWImport will look for the specified directory and attempt to perform imports using all files in the directory. You can provide a full directory path that provides a directory path from the root of the file system. For example, in Linux: .PLWImport.sh -d homeuserplwdatabatch You can provide a relative directory path that provides a directory path relative to the directory from which PLWImport was invoked. For example, in Linux: .PLWImport.sh -d databatch or .PLWImport.sh -d batch Working with Project Lifecycle Workbench Seed Data 5-11 If the UUID is unique in the target instance, PLWImport inserts a record for the new UUID. 5. The results of the import are stored in the plwimporter.log file located in the PLWImExport folder. 6. Once the PLWImport script has run successfully, verify that the imported data is accessible in Project Lifecycle Workbench. For more information about Project Lifecycle Workbench, see Section 2.3, Working with Project Lifecycle Workbench Projects. 5-12 Developers Guide for Oracle Application Integration Architecture Foundation Pack 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