This appendix provides XML structures of exportable Composite Application Validation System (CAVS) definitions and instances.
This appendix includes the following sections:
The structure of the Definitions.xml file created by the CAVS definition export feature is shown in Example A-1.
This export feature should be used to migrate definitions between instances running on the same version of Oracle Application Integration Architecture (AIA) Foundation Pack.
Use this structure as a reference if you receive a validation error when importing definitions.
Edit this structure to create new definitions for importing to an Foundation Pack instance.
For more information about the definition export and import feature, see Chapter 12, "Exporting and Importing CAVS Definitions and Instances."
<DefinitionsList>
<!-- The section below is for one test/simulator definition. This includes all definition details
as well as XPATH conditions set by the user.
For each definition the section below will be repeated -->
<DefinitionsViewRORow>
<DefinitionId>[Definition ID that was set in the previous environment. During import, the
target system will generate a new ID for this field]</DefinitionId>
<Type>[Test|Simulator]</Type>
<Description>[String. Description of the test or simulator]</Description>
<State>[Locked|Unlocked]</State>
<ServiceType>[Synchronous|Notify|Asynchronous two way]</ServiceType>
<UrlEndpoint>[URL]</UrlEndpoint>
<SoapAction>[String. Valid soap action from the wsdl of the above URL]</SoapAction>
<SoapTransportType>[HTTP]</SoapTransportType>
<MessageRequest>[SOAP Message. Request message along with CAVS SOAP
envelopes]</MessageRequest>
<MessageResponse>[SOAP Message. Response message along with CAVS SOAP
envelopes]</MessageResponse>
<Delay>[Integer greater than -1. Only in the case of ServiceType Asynchronous two way]</Delay>
<ServiceName>[String]</ServiceName>
<ServiceVersion>[String]</ServiceVersion>
<ProcessName>[String]</ProcessName>
<PipName>[String]</PipName>
<AuditedOn>[YYYY-MM-DD HH:MM:SS.M]</AuditedOn>
<AuditedBy>[oc4jadmin]</AuditedBy>
<!-- Namespace details from the request/response message. There can be more than one occurrence
of the section below -->
<NsXpathsForDefinitionsRO>
<DefinitionNsXpathsViewRORow>
<DefinitionId>[Definition ID mentioned above]</DefinitionId>
<NamespaceAlias>[String. namespace alias]</NamespaceAlias>
<Namespace>[valid namespace URL]</Namespace>
</DefinitionNsXpathsViewRORow>
</NsXpathsForDefinitionsRO>
<!-- XPATH variables and values. There can be more than one occurrence of the section below
-->
<XpathsForDefinitionsRO>
<DefinitionXpathsViewRORow>
<DefinitionId>[Definition ID mentioned above]</DefinitionId>
<XpathSeqId>[Non negative Integer]</XpathSeqId>
<Xpath>[XPATH expression]</Xpath>
<IsNodeText>[0|1.Applicable only for Simulator Definitions]</IsNodeText>
<IsNodeKey>[0|1. Applicable only for Simulator Definitions]</IsNodeKey>
<Condition>[OK|EQ|NE|LT|GE|LE|Not Null]</Condition>
<IsSystemGenerated>[0|1]</IsSystemGenerated>
</DefinitionXpathsViewRORow>
</XpathsForDefinitionsRO>
</DefinitionsViewRORow>
<!-- The section below is for one group test definition. This includes all definition details as
well as references to Test definitions that are mentioned above.
For each such group definition the section below will be repeated -->
<GroupDefinitions>
<!-- There can be more than one occurrences of the section below -->
<GroupDefinitionsViewRORow>
<GroupDefinitionId>[Group Definition ID that was set in the previous environment. During import
the target system will generate a new ID for this field]
</GroupDefinitionId>
<Description>[String]</Description>
<ProcessName>[String]</ProcessName>
<PipName>[String]</PipName>
<GDDefinitionsViewRO>
<!-- There can be more than one occurrences of the section below -->
<GDDefinitionsViewRORow>
<GroupDefinitionId>[Group Definition ID set above]</GroupDefinitionId>
<SeqId>[Non negative Integer]</SeqId>
<DefinitionId>[One of the Definition ID set in the DefinitionsViewRORow
section]</DefinitionId>
<DefinitionSeqId>[Non negative Integer]</DefinitionSeqId>
<ServiceType>[Synchronous|Notify|Asynchronous two way]</ServiceType>
<SoapTransportType>[HTTP]</SoapTransportType>
</GDDefinitionsViewRORow>
</GDDefinitionsViewRO>
</GroupDefinitionsViewRORow>
</GroupDefinitions>
</DefinitionsList>
The structure of the Instance.xml file created by the CAVS instance export feature is shown in Example A-2.
This export feature can be used to export a test or group instance in XML format that can be used with XML reporting tools to generate reports of test executions.
For more information about the instance export feature, see Chapter 12, "Exporting and Importing CAVS Definitions and Instances."
<InstancesList><?xml version = '1.0' encoding = 'UTF-8'?>
<InstancesViewRORow>
<!-- There would be more occurrences of this if more instances are exported--!>
<InstanceId>[Instance ID that was assigned by the environment in which the instance was
run]</InstanceId>
<Type>[Test|Simulator|Group</Type>
<Status>[Status of the instances being exported] </Status>
<StartedOn>[Date and time at which the instance started]</StartedOn>
<EndedOn>[Date and time at which the instance ended]</EndedOn>
<IsStaled>[0|1]</IsStaled>
<DefinitionId>[Definition ID of the definition that generated the instance]</DefinitionId>
<Description>[Description of the definition ID that generated the instance]</Description>
<ServiceType>Synchronous|Asynchronous two-way|Asynchronous (notify)</ServiceType>
<SoapAction>[String. Valid SOAP action for the WSDL defined for the definition
ID]</SoapAction>
<SoapTransportType>HTTP</SoapTransportType>
<MessageRequest>actual request message</MessageRequest>
<MessageResponse>actual response message</MessageResponse>
<DefinitionsViewRO>
<DefinitionsViewRORow>
<DefinitionId>[Definition ID mentioned above]</DefinitionId>
<Type>[Type mentioned above] </Type>
<Description>[Description mentioned above]</Description>
<State>[Locked|Unlocked]</State>
<ServiceType>[Service Type mentioned above] </ServiceType>
<SoapAction>[SOAP Action mentioned above] </SoapAction>
<SoapTransportType>HTTP</SoapTransportType>
<MessageRequest>[Request message defined in the corresponding Test or Simulator
definition]</MessageRequest>
<MessageResponse>[Response message defined in the corresponding Test or Simulator
definition]</MessageResponse>
<AuditedOn>[YYYY-MM-DD HH:MM:SS.M]</AuditedOn>
<AuditedBy>[oc4jadmin]</AuditedBy>
</DefinitionsViewRORow>
</DefinitionsViewRO>
<InstanceXpathsViewRO>
<InstanceXpathsViewRORow>
<InstanceId>[Instance ID assigned to the instance}</InstanceId>
<XpathSeqId>[Non-negative integer] </XpathSeqId>
<Status>[Status of the instance] </Status>
<Xpath>/soap:Envelope</Xpath>
<IsNodeKey>[0|1. Applicable only for Simulator Definitions]</IsNodeKey>
<Condition>[OK|EQ|NE|LT|GE|LE|Not Null]</Condition>
</InstanceXpathsViewRORow>
</InstanceXpathsViewRO>
<InstanceNsXpathsViewRO>
<InstanceNsXpathsViewRORow>
<InstanceId>[Instance ID assigned to the instance] </InstanceId>
<NamespaceAlias>[String]</NamespaceAlias>
<Namespace>[Valid namespace URL]</Namespace>
</InstanceNsXpathsViewRORow>
</InstanceNsXpathsViewRO>
</InstancesViewRORow></InstancesList>