How to Configure the XPath Expression for a Custom XML Document

Step 6: Add identifiers

6. Select Open with or Save to Disk.

8.1 Using the Custom Document Protocol

8.1.1 How to Configure the XPath Expression for a Custom XML Document

The XPath expression identifies a Custom XML document. You configure the XPath expression when you specify the document type parameters.

The options when configuring an XPath expression are as follows: Option 1: Specify the XPath and the Matching Value

XPath Name1 The XML XPath name for retrieving the value from the payload

XPath Expression1 The XML XPath expression for retrieving the value from the payload (see Note below table)

XPath Name2 The XML XPath name for retrieving the value from the payload

XPath Expression2 The XML XPath expression for retrieving the value from the payload (see Note below table)

XPath Name3 The XML XPath name for retrieving the value from the payload

XPath Expression3 The XML XPath expression for retrieving the value from the payload (see Note below table)

Correlation Tab -

Correlation From XPath Name

The name of the correlation property for initiating the correlation. Correlation From XPath

Expression

The XML XPath for retrieving the value from the payload to initiate the correlation. (see Note below table)

Correlation To XPath Name

The name of the correlation property for the correlation. Correlation To XPath

Expression

The XML XPath for retrieving the value from the payload for the correlation. (see Note below table)

Flat Tab -

Identification Start Position

Used in combination with the end position to retrieve a value from the payload between the start and end positions

Identification End Position Used in combination with the start position to retrieve a value from the payload between the start and end positions

Identification Value A value between the start and end positions

Apps Tab -

Document The name of the internal application document. Action A sub-classification within the document. XSLTFile The name of the XSLT file.

Note: When using EDI documents which have default namespace, the usage of

//*[local-name()='...']

can be used, but the more common usage

//Segment-TH/Field-101-A1/text()

cannot be used.

Table 8–2 (Cont.) Document Definition Parameters for a Custom Document

Using the Custom Document Protocol

■ Option 2: Check for the Existence of a Node ■ Option 3: Check the Value of an Attribute

8.1.1.1 Option 1: Specify the XPath and the Matching Value

Assume that the transaction ID is 12345. Set the parameters as follows:

Oracle B2B compares the value of Identification Expression in the payload to the value specified in Identification Value. If the values match, then the document is identified successfully and the corresponding document type and document protocol version are used to identify the agreement. Example 8–1 shows an excerpt of the XML payload for this option.

Example 8–1 Specify the XPath and the Matching Value

<?xml version="1.0" encoding="UTF-8" ?>

<ns:Case xsi:schemaLocation="http://www.example4.org" ns1:caseCategoryID="1"> <ns1:OfficialProvisionNumber>String</ns1:OfficialProvisionNumber>

</ns:Case> </Body> </Message>

8.1.1.2 Option 2: Check for the Existence of a Node

Assume that you are checking for the existence of a node called registerCommand. Set the parameters as follows:

When the Identification Value field is left blank, Oracle B2B checks for the node identified in Identification Expression. If a node in the payload matches, then the document is identified successfully. Example 8–2 shows an excerpt of the XML payload for this option.

Example 8–2 Check for the Existence of a Node

<uccnet:envelope xmins:eanucc="http://www.ean-ucc.org/schemas/1.3/eanucc"

Field Value

Identification Value 12345

Identification Expression //*[local-name() = 'TransactionID']/text()

Field Value

Identification Value Leave blank.

Identification Expression /*[local-name()='envelope']/body/transaction/command/*[loc al-name()='registerCommand']

Using the Custom Document Protocol xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:uccnet="http://www.uccnet.org/schemas/2.2/uccnet" communicationVersion="2.2" xsi:schemaLocation="http://www.uccnet.org/schemas/2.2/uccnet http://www.testregistry.net/xmlschema/uccnet/2.2/Envelope.xsd"> <messageHeader> <messageIdentifier> <value>791:1_EB3CDC749A1F2BABE03014906CC4605A</value> </messageIdentifier> <userId>oraclesupXSD</userId> <representingParty> <gin>0060974050142</gin> </representingParty> </messageHeader> <body> <transaction> <entityIdentification> <uniqueCreatorIdentification>856</uniqueCreatorIdentification> <globalLocationNumber> <gin>0060974050142</gin> </globalLocationNumber> </entityIdentification> <command> <uccnet:registerCommand> <registerCommandHeader type="ADD" /> </uccnet:registerCommand> </command> </transaction> </body> </uccnet:envelope>

8.1.1.3 Option 3: Check the Value of an Attribute

Assume that the value of the country attribute is US. Set the parameters as follows:

Oracle B2B compares the value of the country attribute to the value set for

Identification Value. If the values match, then the document is identified successfully. Example 8–3 shows an excerpt of the XML payload for this option.

Example 8–3 Check the Value of an Attribute

<?xml version="1.0" encoding="windows-1252" ?>

<name>B2B Buyer</name>

<street>100 Oracle Parkway</street> <city>Redwood City</city> <state>CA</state> <zip>94065</zip> </MyAddress> Field Value Identification Value US

Using the EDI EDIFACT Document Protocol

In document Oracle Fusion Middleware (Page 154-157)