Batching Operations Oracle Fusion Middleware Online Documentation Library

19-12 Oracle Fusion Middleware Users Guide for Oracle B2B

19.10 Verifying Agreement Availability

The b2bcheckcpaid utility enables you to verify the availability of an agreement for a given CPAID and trading partner. Based on the result, you can import the agreement with the option overwrite it. Example 19–21 ant -f ant-b2b-util.xml b2bcheckcpaid -Dargs=soa_file.zip

19.11 Creating Oracle B2B Metadata Based on selfservice.xsd

The following utility creates the selfservice.xsd file, which is used to understand or create selfservice XML based on the XSD structure. ant -f ant-b2b-util.xml b2bselfservicexsd The following utility creates Oracle B2B metadata from the XML file that is created based on selfservice.xsd. ant -f ant-b2b-util.xml b2bselfservice See Appendix E, Self Service Utility Protocols, Identifications, Security Specifications, and Parameters for information about selfservice protocols, identifications, and security specifications. Table 19–12 lists the options for these utilities. Example 19–22 Converts b2bselfservicexsd-Generated XML to an Oracle B2B Metadata ZIP file stored in tmpsoa.zip ant -f ant-b2b-util.xml b2bselfservice -Dinput=tmpselfservice1.xml Example 19–23 Converts b2bselfservicexsd-Generated XML to an Oracle B2B Metadata ZIP file stored in tmpas11b2b.zip ant -f ant-b2b-util.xml b2bselfservice -Dinput=tmpselfservice1.xml -Doutput=tmpas11b2b.zip

19.11.1 Using Selfservice to Batch Create Document Protocols, Trading Partners, and Agreements

When using a multiple file approach, you must make sure that the names of the selfservice XML files are in following order, otherwise, an error claiming that the referenced object does not exist might be thrown.

1. Document Protocols selfservice XML files.

Table 19–11 Options for b2bcheckcpaid utility Option Description Domain Required args Oracle B2B metadata file file name Yes Table 19–12 Options for b2bselfservice utility Option Description Domain Required input XML file absolute location - Yes output Location for Oracle B2B metadata stored as a ZIP file - No B2B Command-Line Tools 19-13 2. Trading Partner selfservice XML files HOST must be first in this list. 3. Trading Partner Agreement selfservice XML files. For example: 1. doc_selfservice.xml to hold Document Protocols. 2. tp_selfservice.xml to hold Trading Partner details. 3. tpa_selfservice.xml to hold Agreements details. Example 19–24 Converts Several b2bselfservicexsd-Generated XML Files Within a Folder to an Oracle B2B Metadata ZIP file stored in tmpas11b2b.zip ant -f ant-b2b-util.xml b2bselfservice -Dinput=folder -Doutput=tmpas11b2b.zip

19.11.2 Using Self Service Samples

Self service utility b2bselfservice XML samples are bundled along with its schemas and ECS files, which are together with the B2B metadata of B2B Samples configuration. Self service samples are found in samplesselfservice folder. Samples are not available for all of the document and exchange protocol combinations. However, by replacing the document protocol details and exchange protocol details in the existing samples, you can create new XML files. X12 Samples The X12 samples are located in: samples selfservicex12b2b-201-X12_4010_850_Filex12_ss.xml The schemas are located in: samples selfservicex12b2b-201-X12_4010_850_Fileschemas Use the following command: ant -f ant-b2b-util.xml b2bselfservice -Dinput=samplesselfservicex12b2b-201-X12_4010_850_Filex12_ss.xml Custom Samples The Custom samples are located in: samples selfservicecustomb2b-101-Custom_1.0_orders_generic_filecustom_ss.xml The schemas are located in; samples selfservicecustomb2b-101-Custom_1.0_orders_generic_fileschemas Use the following command: ant -f ant-b2b-util.xml b2bselfservice -Dinput=samplesselfservice custom\b2b-101-Custom_1.0_orders_generic_filecustom_ss.xml Note: Self service XML files can also be created using the XSD, which is useful for the advanced user who wants to start from scratch.