Prerequisites for Running the Command-line Tools

19-6 Oracle Fusion Middleware Users Guide for Oracle B2B

19.5 Exporting Data

The b2bexport utility exports metadata from the Oracle B2B repository. If no options are specified then the entire repository is exported. The following usage exports the entire repository without policy details to tmpexport.zip if no other options are specified. ant -f ant-b2b-util.xml b2bexport Table 19–4 lists the options for this utility. Example 19–5 Export entire repository with policy details to tmpexport.zip ant -f ant-b2b-util.xml b2bexport -Dexportfile=tmpexport.zip -Dpolicies=true localfile If the export file location exists on the server, then set this option to true to improve performance. The export file must be on the server on which B2B is running. true false default No Note: No security or permission checks are performed to prevent the logged-in user from exporting data. Table 19–4 Options for b2bexport utility Option Description Domain Required tpanames One or more agreement names to be exported. If one agreement is exported, then the ZIP file contains the folder soab2b. If multiple agreements are exported, then the ZIP file contains an individual ZIP file for each of the agreements. Agreement names must be separated by a comma No tpname The trading partner name to be exported Name of the trading partner No exportfile Location of the ZIP file where the exported data is stored tmpexport.zip default No active Exports agreements that have been deployed and are in active state. true false default No policies Set to true to export the entire repository with user and role details, which is needed for the policy store. A warning is displayed to remind you to export the policy store also. See Section 7.2, What Is Copied When You Import or Export from the ImportExport Tab, for more information. true false default No localfile Set to true for improved performance if the export file is on the same computer as Oracle B2B. true false default No Table 19–3 Cont. Options for b2bimport utility Option Description Domain Required B2B Command-Line Tools 19-7 Example 19–6 Export entire repository wo details to tmpexportinserver.zip on same server ant -f ant-b2b-util.xml b2bexport -Dexportfile=tmpexportinserver.zip -Dlocalfile=true Example 19–7 Exports the Trading Partner Acme to tmpAcme.zip ant -f ant-b2b-util.xml b2bexport -Dtpname=Acme -Dexportfile=tmpAcme.zip Example 19–8 Exports an Agreement from Design-Time with Listening Channel Details to tmpacmeGc.zip ant -f ant-b2b-util.xml b2bexport -Dtpanames=Acme_GC_Agreement1 -Dexportfile=tmpAcmeGc.zip Listening channels are deactivated while exporting and must be reactivated after you import data. Example 19–9 Exports Multiple Deployed and Active Agreements to tmpexport.zip ant -f ant-b2b-util.xml b2bexport -Dtpanames=Acme_GC_Agreement1, GC_Acme_Agreement1 -Dactive=true No listening channels are exported.

19.6 Batching Operations

The command line b2bbatch utility enables you to create batches, based on various criteria. This utility is a supplement to the available batch creationdeletion feature in the Oracle B2B Console for EDI documents. This is an ANT based command, and provides the flexibility to selectively set the criteria to create batches. To create multiple trading partners and document versions in a single step, you must use the Oracle B2B Console; to achieve it on command-line you must run the batch creation utility multiple times. For advanced functionality, such as disabling or updating a batch you must use the Oracle B2B Console. The usage is as follows: ant -f ant-b2b-util.xml b2bbatch -Dtp=tpName -Dbatchtime=batchTriggerTime -Dbatchname=batchName -Ddocument=documentProtocolName -Ddocrevision=docRevision -Ddoctype=docType -Disrepetitive=true|false Table 19–5 lists the options for this utility. Table 19–5 Options for b2bbatch utility Option Description Domain Required tp Trading Partner name. Specify the trading partner name. Yes 1 batchname Batch name. Specify a name for the batch. Yes batchtime Batch trigger time. The trigger time can be a cron String or the date in ddMMyyyy HH:mm AMPM format. See also Example 19–13 . Yes