In a previous blog, we discussed a number of new features that were added to the admin console with the release of BizTalk 2016. This new release has provided users with a number of helpful features, and among them is the ability to import and export parties separately from applications.
Importing a New Party
Previously, importing a party was only possible by importing a set of application bindings which contained global party information as well. Microsoft has made this easier for us by separating out this feature to make it more versatile.
Importing a new party (or set of parties) is as simple as navigating to the Parties tab in the admin console and taking a look at the right panel. There’s a new import button there, as you can see below.
Clicking the “Import…” button here opens up a dialog window which allows us to select the file which contains our new party’s information.
This window will accept any file that contains valid party bindings, such as the ones we’ll create next when testing out the Export functionality.
Exporting Existing Parties
Similarly to the importing feature, the ability to export parties was previously only available while exporting the application bindings, via an extra checkbox in the dialog. If a user wanted to use only the party information from these bindings, they’d have to search through the file and extract the party related nodes manually. BizTalk 2016 makes this much easier by allowing us to export one or more parties directly from the Parties tab.
As you might have noticed while we were going over importing above, there are a couple of buttons on the right panel which initiate exporting. There’s an “Export…” button right below the “Import…” button which exports the information of all of the existing parties, and there is also an “Export” option in the “Selected Item” section of the right panel, which will export only the parties which have been selected. The selected item scenario is also available by selecting the desired parties and using the right-click context menu, as shown below.
Whichever way we choose to use, clicking “Export” brings us to the following dialog box:
The export option is preselected since this feature is purely for exporting parties, so the only thing the user has to do here is select the desired location of the exported file. After doing this, we can go take a look at the exported file, and it will contain only party specific information related to the party or parties which we selected.
As mentioned above, this file can now be imported into another BizTalk application separate from application bindings. If the desired result is to keep the party information together with the rest of the bindings, however, the old options for exporting and importing all of the binding information are still available.