How to Set Up an Environment to Export or Import Seed Data for the First Time How to Export Seed Data

Working with Project Lifecycle Workbench Seed Data 5-7

5.2 How to Set Up an Environment to Export or Import Seed Data for the First Time

Objective Perform set up tasks to enable the export and import of Project Lifecycle Workbench seed data. Perform this procedure for each separate environment, whether it is being exported from or imported to. Perform this procedure only once for each environment, prior to the first time the environment will be accessed for export and import. Prerequisites and Recommendations None Actor ■ Integration developers ■ System administrators To set up a Linux environment to export or import seed data for the first time: 1. Start a server session. 2. Navigate to aiaenv.sh located in AIA_INSTANCEbinaiaenv.sh. 3. At the command prompt, execute source aiaenv.sh. To set up a Windows environment to export or import seed data for the first time: 1. Access a command prompt. 2. Access the drive on which AIAHome is installed. 3. Navigate to aiaenv.bat located in AIA_HOME\aia_instances\AB\bin. 4. At the command prompt, run aiaenv.bat.

5.3 How to Export Seed Data

Objective Export 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 . Actors ■ System administrators ■ Integration developers To export Project Lifecycle Workbench seed data: 1. Access a command window on the server from which you want to export seed data. 2. Navigate to the AIA_HOMEInfrastructureLifeCyclePLWImExport folder. 5-8 Developers Guide for Oracle Application Integration Architecture Foundation Pack 3. Run PLWExport to perform the seed data export. Output files are saved to the PLWImExport folder. One output XML file is generated per project. PLWExport provides a set of export commands, as discussed in Table 5–1 . Following are sets of sample commands for performing exports using a variety of export criteria. Export BOM and functional decomposition data by project code and version to a named output file: ■ For Linux: PLWExport.sh -p Project Code -v version -s all -o output file name ■ For Windows: PLWExport.bat -p Project Code -v version -s all -o output file name Table 5–1 PLWExport Commands Command Description -p project code You must provide -p or -u in the PLWExport command. -v version For optional use with -p. If a version is not specified and there are multiple projects with the same project code, but different versions, the projects are displayed. If a version is not specified and there is only one project that matches the project code criteria, the seed data for the project is exported. -u UUID value You must provide -u or -p in the PLWExport command. A UUID value is assigned to a Project Lifecycle Workbench project as the Project Unique ID value upon saving the project for the first time. The ID displays on the Add Project page and Update Project page and is stored in the AIA_OER_PROCESSES table. For more information about the project unique ID value as it displays in the Project Lifecycle Workbench UI, see Section 2.3, Working with Project Lifecycle Workbench Projects. -s scope Use as follows: ■ -s all Exports BOM and functional decomposition data. ■ -s fd Export functional decomposition data only. If not specified, PLWExport will use -s all. To export BOM data, you must also export functional decomposition data, -s all. You cannot export only BOM data. -o output file name If not specified, PLWExport will use a file name of project code_UUID.xml. Caution: If a project is exported with no -o command, and then is exported again with no -o command, the export file generated by the first export will be overwritten by the export file generated by the subsequent export. 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