Exported ZIP Files Containing Agreement Names in Multibyte Character Languages

8-2 Oracle Fusion Middleware Users Guide for Oracle B2B ■ Section 8.10, Using Document Routing IDs For related information, see the following: ■ Chapter 3, Creating Guideline Files ■ Chapter 4, Creating Document Definitions

8.1 Using the Custom Document Protocol

Oracle B2B supports custom document protocols to create documents needed for proprietary transactions. With XML messages, you have the advantage of schema enforcement XSDs. With non-XML messages, you can create trading partner agreements for specific message types. When creating a Custom document, you specify rules to identify the incoming document. For XML documents, specify an XPath expression and a value, which is the expected result of the expression. For non-XML documents such as a flat file, you can specify start and end positions or a document routing ID. Document Version Parameters No parameters need to be set when you create the document version for a Custom document. Document Type Parameters When you create a Custom document type, you can set ebXML messaging service ebMS parameters to identify the ebXML document. Figure 8–2 shows the document type parameters for a Custom document. Using Document Protocols 8-3 Figure 8–2 Document Type Parameters for a Custom Document The image shows a section of the New Document Type screen. The first area of the screen shows the following fields: Document Type Name and Description. The second area of the screen shows the ebMS tab with the following fields: Action name, Service name, Service type, FromRole, ToRole, Vaildate ebMS Header, and CPA File. Table 8–1 describes the document type parameters for a Custom document. Table 8–1 Document Type Parameters for a Custom Document Parameter Description ebMS Tab - Action name The action name for the ebXML header, which is also an identification criteria for inbound and outbound messages. ebMS documents require an action name to avoid run-time errors. Service name The service name for the ebXML header, which is also an identification criteria for inbound messages. ebMS documents require a service name to avoid run-time errors. Service type The service type for the ebXML header, which is also an identification criteria for inbound messages. ebMS documents require a service type to avoid run-time errors. From Role The trading partner that sends the message. A value provided here overrides the Identifiers values supplied on the Profile tab. To Role The trading partner that receives the message. A value provided here overrides the Identifiers values supplied on the Profile tab. Vaildate ebMS Header When selected, validates inbound ebMS header from role, to role. CPA File CPA file 8-4 Oracle Fusion Middleware Users Guide for Oracle B2B Document Definition Parameters When you create a Custom document definition, select the file type—XML or Flat—and set parameters in the tabbed areas. Figure 8–3 shows the document definition parameters for an XML-type Custom document. Figure 8–3 Document Definition Parameters for an XML-Type Custom Document The image shows the ebMS custom document screen. The first area of the screen shows the following fields: Document Definition Name, Description, Definition, and Root XSD Name. The first area also shows the Reset Parameter button. The second area of the screen shows the following tabs: XML, Routing, XPath, Correlation, and Apps. The XML tab is selected. The tab shows the following fields: Identification Expression XPath, Identification Value, and DTDXSD Namespace Conversion. At the top right of the screen is the Save button. Figure 8–4 shows the document definition parameters for a flat-file Custom document. Using Document Protocols 8-5 Figure 8–4 Document Definition Parameters for a Flat-FIle Custom Document The image shows the ebMS custom document screen. The first area of the screen shows the following fields: Document Definition Name, Description, Definition, and Root XSD Name. The first area also shows the Reset Parameter button. The second area of the screen shows the following tabs: Flat, Routing, XPath, Correlation, and Apps. The Flat tab is selected. The tab shows the following information: Identification Start Position, Identification End Position, and Identification Value. At the top right of the screen is the Save button. Table 8–2 describes the document definition parameters for a Custom document. Table 8–2 Document Definition Parameters for a Custom Document Parameter Description XML Tab Available if XML is selected from Identification Type Identification Expression XPath Locates a node in the XML payload Identification Value Provides the value to match in the node identified by the Identification Expression. If the values match, then the document is successfully identified. If the value is left blank, then Oracle B2B checks for the existence of the node and the document is successfully identified. DTDXSD NamespaceConversion Select from None, Both, Inbound, or Outbound. Routing Tab - Document Routing ID Sets the consumer name to the back-end application XPath Tab See Section 8.1.1, How to Configure the XPath Expression for a Custom XML Document, for more information