Export Trading Partner Data Using the Command Line

You can export a file from the command line.

To export a file from the command line:
  1. Change to the install_dir/tp_import directory.
  2. Run one of the following commands:
    ./export.sh -input [input filename] (UNIX)

    export.cmd -input [input filename] (Windows)

    Input filename is the name of the XML file you want to export. This is a mandatory parameter.

    All the available parameters are listed in the following table:

    Option Description
    -input [filename]
    Name of the file that contains the objects to be exported. Mandatory. The properties file describing which resources to be exported should have the following format:
    RESOURCE_TYPE[1]=ALL

    Or

    RESOURCE_TYPE[1]=ResourceNameA 
RESOURCE_TYPE[2]=ResourceNameB 
RESOURCE_TYPE[3]=ResourceNameC
Etc.

    The RESOURCE_TYPE is the name of the resource as defined by tp_import_export.properties. If a resource has a subtype, then the specific subtype name must be used. The following is an example properties file to export all EDI envelopes and maps from the system.

    DOCUMENT_ENVELOPES[1]=ALL MAPS[1]=ALL

    Available resource types include: BPDEFS, SCHEMAS, XSLTS, SERVICE_INSTANCES, USERS, GROUPS, PERMISSIONS, PGPPROFILES, SCHEDULES, SCI_CA_CERTS, SCI_TRUSTED_CERTS, SCI_PRIVATE_KEY_CERTS, MAPS, CD_NETMAPS, ProxyServers, PGP_PARTNERS, PGP_SPONSORS, BANDWIDTH_THROTTLING, COMMAND_LIMITING, LOCKOUT, DATA_LIMIT, ADAPTER_MAPPING, WMQFTE_USERMAPS, APP_CONFIGURATIONS, SCI_PACKAGES, SCI_ENTITIES, CONTRACTS, CODE_LISTS, XFORMS, WEB_JSP_FILES, WEB_JAVASCRIPT_FILES, WEB_HTML_FILES, WEB_XML_FILES, WEB_IMAGES, WEB_PROPERTY_FILES, WEB_STYLESHEETS, WEB_OTHER_FILES, WSDL, MBXVIRTUAL, MBXMETA, MBXROUTING, EBXMLBPSS, EBXMLBPSSEXT, EBXMLCPA, PSERVERS, REPORT_CONFIGS, SCI_SSH_REMOTE_PROFILES, SCI_SSH_HOST_USER_IDENTITY_KEYS, SCI_SSH_KNOWN_HOST_KEYS, SCI_SSH_AUTHORIZED_USER_KEYS, SECURITY_TOKENS, EXTENDED_RULE_LIBRARIES, POLICIES, PROXY_NETMAPS, SWIFT_NET_ROUTING_RULES, EB_Host, EB_Partner, EB_User, EB_File_Format, EB_Ord_Type, EB_Offer, Agreements, COMMUNITIES, DOCUMENT_ENVELOPES, CONTROL_NUMBERS, SWIFTNET_ROUTING_RULES, SWIFTNET_SVC_PROFILES, SWIFTNET_COPY_PROFILES, SWIFTNET_CLIENT_PROFILES, AS3Profiles, AS3Contracts, CustomJars, CustomServices, CustomUserExits, PropertyFiles

    Note:
    • To export the specific CustomJar record, in the input file, you must specify the name of the record in the following format:
      CustomJars[1]=vendorNameA~vendorVersionA
      CustomJars[2]=vendorNameB~vendorVersionB
    • To export the specific CustomUserExit record, in the input file, you must specify the name of the record in the following format:
      CustomUserExits[1]=vendorNameA~vendorVersionA
      CustomUserExits[2]=vendorNameB~vendorVersionB
    Note: Do not use SCHEDULES[1]=ALL to export all SCHEDULES. Export each schedule individually as shown below:
    SCHEDULES[1]=SCHEDULENameA 
SCHEDULES[2]=SCHEDULENameB
...
    -tag [tagname] Resource tag name to associate with the export file. This will be the default tag created when importing. Optional
    -output [filename] Name of the file that contains the exported data (use .xml as the file extension). Optional.
    -report [filename] Name of the file that contains a report if there were in errors during the export. Optional.
    -doCerts [filename] Name of the file used to export transport and certificates. Optional.
    -passphrase [passphrase] Password used to export transport and certificates. Optional.
    Note: This is the passphrase that was used during export.
    -allversions Used to export all versions from the system. Optional.