Introducing Project Lifecycle Workbench Seed Data

5 Working with Project Lifecycle Workbench Seed Data 5-1 5 Working with Project Lifecycle Workbench Seed Data This chapter includes the following sections: ■ Section 5.1, Introducing Project Lifecycle Workbench Seed Data ■ Section 5.2, How to Set Up an Environment to Export or Import Seed Data for the First Time ■ Section 5.3, How to Export Seed Data ■ Section 5.4, How to Import Seed Data

5.1 Introducing Project Lifecycle Workbench Seed Data

In Project Lifecycle Workbench, seed data can be categorized into two areas: ■ Bill of material BOM data Bill of material seed data contains information about the SOA composites in a Project Lifecycle Workbench project. You can produce a BOM.xml file from the Project Lifecycle Workbench user interface UI based on seed data residing in the Project Lifecycle Workbench backend. For more information about generating BOMs, see Section 4.2, How to Generate a Bill of Material for an AIA Lifecycle Project. ■ Functional decomposition data Functional decomposition is a task performed by functional experts or solution architects that involves an overall analysis of an process integrations business logic. The Project Lifecycle Workbench can be used to facilitate this task. Functional decomposition data includes a set of requirements and intentions that have been defined in Project Lifecycle Workbench to articulate the business logic of a given process integration. This seed data is composed of projects, business tasks, and service solution components. For example, a Project Lifecycle Workbench service solution component is a product of functional decomposition that represents an intent to fulfill a chunk of business logic in the form of a service. At the time of its creation in Project Lifecycle Workbench, the service solution component may or may not correspond to an existing executable service. You can use the seed data created by your organizations work in Project Lifecycle Workbench to capture and migrate data from one Project Lifecycle Workbench to another. 5-2 Developers Guide for Oracle Application Integration Architecture Foundation Pack Oracle delivers BOM and functional decomposition seed data with its Process Integration Pack PIP products. You can clone this Oracle-delivered data and modify the projects, adding custom logic and artifacts. Cloning the delivered seed data ensures that subsequent AIA upgrades and patches do not tamper with your customized data. Once you have cloned the data, you can perform the following types of updates to the data: ■ Modify an existing composite and its associated annotations. ■ Add a composite to the cloned BOM, assuming that the composite has been developed based on the AIA programming models and annotation standards. ■ Remove a composite from the cloned BOM. With this seed data, you can go through your development cycle, modifying PIP project definitions and composites, generate BOMs, and from the BOMs, generate deployment plans. For more information about generating deployment plans, see Chapter 6, Generating Deployment Plans and Deploying Artifacts. Oracle-delivered seed data can be imported into a Project Lifecycle Workbench instance as a part of the overall PIP installation process, or the data can be imported using a standalone post-installation script, depending on the needs of your implementation. To determine the phase in which you should import your seed data, consider that deployment plans are only meaningful when the underlying executables, such as composite source code, are available for installation, deployment, and execution. For this reason, determine the phase in which to import seed data by determining when the executable source code will be ready for deployment on the target file system. For more information about how to load Project Lifecycle Workbench seed data post-installation, see Section 5.4, How to Import Seed Data Figure 5–1 provides a sample usage flow for the import and export of Project Lifecycle Workbench seed data. Working with Project Lifecycle Workbench Seed Data 5-3 Figure 5–1 Sample Usage Flow for Import and Export of Project Lifecycle Workbench Seed Data Project Lifecycle Workbench does not capture non-native artifacts. Deployment of Oracle-delivered non-native artifacts can be manually specified using SupplementaryDP.xml. Deployment of custom non-native artifacts can be manually specified using CustomSupplementaryDP.xml. For more information about how to deploy non-native artifacts using SupplementaryDP.xml and CustomSupplementaryDP.xml, see Section 6.2.2, Extending Non-Native Artifacts. The Project Lifecycle Workbench seed data schema is provided in Example 5–1 . Example 5–1 Project Lifecycle Workbench Seed Data Schema ?xml version=1.0 encoding=windows-1252? -- edited with XMLSpy v2006 rel. 3 sp2 http:www.altova.com by Siebel Systems Siebel Systems -- xsd:schema xmlns:xsd=http:www.w3.org2001XMLSchema xmlns=http:xml.oracle.com AIAPLWBOMV1 targetNamespace=http:xml.oracle.comAIAPLWBOMV1 elementFormDefault=qualified xsd:element name=PLW xsd:complexType xsd:sequence xsd:element name=Process xsd:annotation xsd:documentationProject LifeCycle WorkBench Seed Data 5-4 Developers Guide for Oracle Application Integration Architecture Foundation Pack Schemaxsd:documentation xsd:annotation xsd:complexType xsd:sequence xsd:element name=ProcessDetail type=ProcessType xsd:element name=ProcessUuid type=xsd:string xsd:element name=ParentProcessUuid type=xsd:string xsd:element name=Task minOccurs=0 maxOccurs=unbounded xsd:complexType xsd:sequence xsd:element name=TaskDetail type=TaskType xsd:element name=Scope type=xsd:string xsd:element name=SvccompId type=xsd:string minOccurs=0 maxOccurs=unbounded xsd:sequence xsd:complexType xsd:element xsd:element name=ProcessBom minOccurs=0 xsd:complexType xsd:sequence xsd:element name=ProcessBomDetail type=ProcessType xsd:element name=BomStatus type=xsd:string xsd:element name=TaskBom minOccurs=0 maxOccurs=unbounded xsd:complexType xsd:sequence xsd:element name=TaskBomDetail type=TaskType xsd:element name=TaskBomSource type=xsd:string xsd:element name=SvccompBomId type=xsd:string minOccurs=0 maxOccurs=unbounded xsd:sequence xsd:complexType xsd:element xsd:sequence xsd:complexType xsd:element xsd:element name=SvccompBom minOccurs=0 maxOccurs=unbounded xsd:complexType xsd:sequence xsd:element name=SvccompBomDetail type=SvccompType xsd:element name=SvccompBomId type=xsd:string xsd:element name=CompositeId type=xsd:string xsd:sequence xsd:complexType xsd:element xsd:sequence xsd:complexType xsd:element xsd:element name=Svccomp minOccurs=0 maxOccurs=unbounded xsd:complexType xsd:sequence xsd:element name=SvccompDetail type=SvccompType xsd:element name=ReusedServiceObjectType type=xsd:string minOccurs=0 xsd:element name=ReusedServiceObjectID type=xsd:string minOccurs=0 xsd:sequence xsd:complexType xsd:element xsd:element name=Composite minOccurs=0 maxOccurs=unbounded xsd:complexType Working with Project Lifecycle Workbench Seed Data 5-5 xsd:sequence xsd:element name=CompositeDetail xsd:complexType xsd:complexContent xsd:extension base=CompositeType xsd:complexContent xsd:complexType xsd:element xsd:element name=CompositeXML type=xsd:hexBinary minOccurs=0 xsd:element name=CompositeRevID type=xsd:hexBinary minOccurs=0 xsd:element name=CompositeServiceElem minOccurs=0 maxOccurs=unbounded xsd:complexType xsd:sequence xsd:element name=ServiceElementID type=xsd:string xsd:element name=CompositeServiceType type=xsd:string xsd:element name=CompositeServiceName type=xsd:string xsd:element name=ServiceElementXML type=xsd:hexBinary xsd:element name=Audit type=CommonAuditType xsd:element name=DeployAttributeValue type=DeployAttributeValueType minOccurs=0 maxOccurs=unbounded xsd:sequence xsd:complexType xsd:element xsd:element name=DeployAttributeValue type=DeployAttributeValueType minOccurs=0 maxOccurs=unbounded xsd:sequence xsd:complexType xsd:element xsd:element name=ServiceElement minOccurs=0 maxOccurs=unbounded xsd:complexType xsd:sequence xsd:element name=ServiceElementDetail type=ServiceElementType xsd:sequence xsd:complexType xsd:element xsd:sequence xsd:attribute name=processCode xsd:attribute name=version xsd:attribute name=createDate xsd:attribute name=uuid xsd:complexType xsd:element xsd:complexType name=CommonAuditType xsd:sequence xsd:element name=CreatedBy type=xsd:string xsd:element name=CreationDate type=xsd:string xsd:element name=LastUpdatedBy xsd:element name=LastUpdateDate xsd:element name=ObjectVersionNumber xsd:sequence xsd:complexType xsd:complexType name=ProcessType xsd:sequence xsd:element name=ProcessName type=xsd:string xsd:element name=ProcessDesc type=xsd:hexBinary xsd:element name=ProcessAssumption type=xsd:hexBinary xsd:element name=ProcessSource type=xsd:string xsd:element name=ProcessIndustry type=xsd:string 5-6 Developers Guide for Oracle Application Integration Architecture Foundation Pack xsd:element name=ProcessCode type=xsd:string xsd:element name=ProcessType type=xsd:string xsd:element name=Status type=xsd:string xsd:element name=Version type=xsd:string xsd:element name=Audit type=CommonAuditType xsd:sequence xsd:complexType xsd:complexType name=TaskType xsd:sequence xsd:element name=TaskID type=xsd:string xsd:element name=TaskName type=xsd:string xsd:element name=TaskDesc type=xsd:hexBinary xsd:element name=TaskUuid type=xsd:string xsd:element name=Audit type=CommonAuditType xsd:sequence xsd:complexType xsd:complexType name=SvccompType xsd:sequence xsd:element name=SvccompID type=xsd:string xsd:element name=SvccompType type=xsd:string xsd:element name=SvccompName type=xsd:string xsd:element name=SvccompDesc type=xsd:hexBinary xsd:element name=SvccompAssumption type=xsd:hexBinary xsd:element name=ProductPillar type=xsd:string xsd:element name=ProductFamily type=xsd:string xsd:element name=ProductCode type=xsd:string xsd:element name=SvccompGUID type=xsd:string xsd:element name=Audit type=CommonAuditType xsd:sequence xsd:complexType xsd:complexType name=CompositeType xsd:sequence xsd:element name=CompositeID type=xsd:string xsd:element name=CompositeName type=xsd:string xsd:element name=Source type=xsd:string xsd:element name=Audit type=CommonAuditType xsd:sequence xsd:complexType xsd:complexType name=ServiceElementType xsd:sequence xsd:element name=ServiceElementID type=xsd:string xsd:element name=ServiceElementType type=xsd:string xsd:element name=ServiceName type=xsd:string xsd:element name=OperationName type=xsd:string xsd:element name=Namespace type=xsd:string xsd:element name=ProductPillar type=xsd:string xsd:element name=ProductFamily type=xsd:string xsd:element name=ProductCode type=xsd:string xsd:element name=Audit type=CommonAuditType xsd:sequence xsd:complexType xsd:complexType name=DeployAttributeValueType xsd:sequence xsd:element name=GroupNumber type=xsd:string xsd:element name=DeployAttributeValue type=xsd:string xsd:element name=DeployAttributeCode type=xsd:string xsd:element name=Audit type=CommonAuditType xsd:sequence xsd:complexType xsd:schema 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