Exporting Data Oracle Fusion Middleware Online Documentation Library

B2B Command-Line Tools 19-11 oracle.tip.b2b.ebms.TPCertificateAlias Optional Property For secure message transfer, this property is used to get the trading partner certificate details to the CPPCPA export. oracle.tip.b2b.ebms.BPSSExport Optional Property This Boolean property is used to generate the BPSS document.

19.9.1.1.3 Common Properties The common properties are as follows:

oracle.tip.b2b.ebms.LogDirectory Required Property This property is used to store the log files. oracle.tip.b2b.ebms.LogLevel Required Property This property is used to specify the mode of the logs, such as DEBUG, INFO, or ERROR. oracle.tip.b2b.ebms.LogType Required Property This property is used to specify whether the log file is stored as text or XML.

19.9.2 CPPCPA Import

The following utility converts an ebXML standard cpa.xml file to an Oracle B2B metadata file, which must then be imported into Oracle B2B. ant -f ant-b2b-util.xml b2bcpaimport Table 19–9 lists the options for this utility. Example 19–19 Converts CPA-Formatted XML to an Oracle B2B ZIP File ant -f ant-b2b-util.xml b2bcpaimport -Dpropfile=tmpcpp_cpa.properties

19.9.3 CPPCPA Export

The following utility converts an Oracle B2B metadata file data exported from Oracle B2B to an ebXML standard cpa.xml file a CPA-ready configuration. ant -f ant-b2b-util.xml b2bcpaexport Table 19–10 lists the options for this utility. Example 19–20 Converts an Oracle B2B ZIP File to a CPA-Formatted XML File ant -f ant-b2b-util.xml b2bcpaexport -Dpropfile=tmpcpp_cpa.properties Table 19–9 Options for b2bcpaimport utility Option Description Domain Required propfile Property file that stores configuration details for b2bcpaimport and b2bcpaexport - Yes Table 19–10 Options for b2bcpaimport utility Option Description Domain Required propfile Property file that stores configuration details for b2bcpaimport and b2bcpaexport - Yes 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