Import and Export

Note: To migrate databases from BC 7.4.x to 7.5.0, use the Version Upgrade Tool. This tool automates the migration process, eliminating the need for manual export and import of CSX, BC initialization, and protocol activation. For more information, see the "Migrating Databases to BC 7.5.0" section in TIBCO BusinessConnect™ Release Notes.

TIBCO BusinessConnect allows you to export configuration data from one TIBCO BusinessConnect application and import it into another application of the same or higher version. The configuration data includes these sets of data:

  • Participants

  • Business agreements

  • Operations

  • System settings

  • Public process configuration except the advanced configuration

  • Private process configuration

  • Component settings

Note: Saved queries are not exported. See TIBCO BusinessConnect™ Trading Partner Administration, Saving a Query.

You can set a password before you export data. This is optional.

You can export an installation configuration to use it with a future installation, or to use the same configuration on another server. You can also import an installation configuration that was previously saved (exported). The installation configuration is saved in the format Domain_name.csx.

Note: Ensure that the activated TIBCO BusinessConnect protocols used for importing configuration files are the same as those used for exporting the configuration files.

To learn how certain installation components are merged in the .csx file, see Component Behavior During Import/Export.

For more information on migrating the installation configuration from the previous versions of TIBCO BusinessConnect, see Migration and Compatibility in TIBCO BusinessConnect™ Release Notes.

Importing the Saved Installation Configuration

If you are importing data from the previously saved installation configuration, follow these steps:

  1. Expand BusinessConnect > Manage > Configuration Repository.

  2. Click Import.

  3. In the Configuration Data Import dialog, click change and locate the previously exported configuration file BC-domain_name.csx.

  4. If the configuration .csx file was exported using a password, enter that password.

  5. A warning is displayed:

    Installation enters into maintenance mode while Import is in progress.

    Configuration data in the import file may merge or overwrite the current configuration.

  6. Click Import, and then click OK.

    Warning: Do not exit the screen while the data import is in progress. It is important to allow this process to be completed properly. If the data import is interrupted for any reason, the system may be left in an unpredictable state. In such a case, you have to recreate the installation and perform a new import.

    The Importing Data dialog is displayed showing you the data import log, with the message Data import has completed successfully. Your session will be automatically logged off at the end.

  7. Click Done to finish import.

    You are logged out of the system.

Exporting the Installation Configuration

If you are exporting the existing installation configuration to use it for the new installation, follow these steps:

  1. Expand BusinessConnect > Manage > Configuration Repository.

  2. Click Export.

  3. In the Configuration Data Export dialog, set a password to protect the configuration file (not mandatory).

  4. Click Export.
    The Export Configuration dialog is displayed showing you the data export log, with the message Export Completed Successfully at the end.

  5. Click Download.
    Navigate to the desired location and save the exported file BC-domain_name.csx.

  6. Click Done to conclude the export.

Component Behavior During Import/Export

When importing an installation configuration, components are imported in the following way:

Installation Component

• Server name and subject prefix are merged.
• Default host is set if there was no default host.
• TIBCO BusinessConnect properties are merged, or added if new.
• Plug-in properties are merged, or added if new.
• Credential alerts are merged.
• Outbound file pollers are merged.
• Proxy information is added only if the proxy name did not exist. If it exists with the same name, it is not merged.
• JDBC information entries are added only if the JDBC name did not exist. If it exists with the same name, it is not merged.
• For logging: logs with message flags are merged.
• Private process transport information is merged.
• Public and private smart routes are inserted at the top of their tables, as in the exporter's order.
• Domain, Partner Classification codes, supply Chain codes, and role catalog entries are added if they do not exist.

Interface Component (Operations)

• New uploaded files are created.
• Interfaces are created.
• Operations are added if they do not exist on the importing system, otherwise they are not merged.

Participant Profiles (Hosts, Trading Partners)

• Trading partners are created if they do not exist.
• Enabled protocols are added if they do not exist.
• Credentials are added if they do not exist with the same name; otherwise they are not merged.
• Domain types and domain IDs are added if they do not exist.
• Business locations and contacts are added if they do not exist; properties are always merged.
• Trading partners enabled protocols are added if they do not exist; default domain IDs and AS2 domain IDs are merged.
• PartnerClassification codes and supplyChain codes are added (if they do not exist) and merged.
• Scheduled transmission details are merged where available.
• Outbound transports are added if a transport with the same name does not exist, otherwise they are not merged.

Business Agreements

• If an agreement does not exist between the given participants, it is created.
• If protocol bindings do not exist for a given protocol, the binding is added.
• Document security properties, primary, backup, error transports are merged.
• Inbound transport properties are merged and enabled as per import configuration, for example, certificates, keys, passwords, URLs, and so on.