Biztalk binding file editor

BizTalk Server follows certain rules when updating existing artifacts with matching artifacts in a binding file. In general, the following rules are applied:. Text boxes and check boxes that are exposed when configuring an artifact via the BizTalk Server user interface such as the BizTalk Server Administration console or BizTalk Explorer , must either be set to a specific value or be empty.

Values supplied for artifacts in a binding file will set the user interface value for the updated item accordingly. Drop-down boxes that are exposed when configuring an artifact via the BizTalk Server user interface must either be set to a specific value or be set to "None".

Datagrid views that are exposed when configuring an artifact via the BizTalk Server user interface are updated with lists from the corresponding item in the binding file. The list associated with a datagrid view is always overwritten by the list in the binding file unless the datagrid view list is tied to a port or a receive location.

In this case the list in the binding file is merged with the existing datagrid view list. Artifacts in the binding file are identified by a primary key value. The value associated with the primary key for an artifact can never be set to null in the user interface and so all artifacts in a binding file must have their primary key value set.

If the value associated with the primary key for an artifact in the binding file matches the value associated with the primary key for an existing configuration artifact then these artifacts are considered to be identical or matching.

If the binding file artifact and the existing artifact are identical then the existing artifact is updated with the binding file artifact as described in the table below. If an artifact in the binding file contains a unique primary key value then a new artifact is created in the BizTalk Server configuration when the binding file is imported.

The following table describes expected behavior if you are updating existing configuration artifacts with matching artifacts by importing a binding file. Binding file artifacts are typically configured to reference other artifacts, for example a receive port is typically configured to reference a receive location. The binding file also contains names of ports and receive locations. If the BizTalk application to which you are importing the binding file creates a port or a receive location that has the same name as an already existing port in the same BizTalk application, you will get an error.

You must manually edit the binding file to specify a unique name for the ports or receive locations. The binding file also contains information about the connection URI. If the binding file creates a receive location that has the same receive URI as an already existing receive location in the same BizTalk application, you will get an error. You must manually edit the binding file to specify a unique URI. By default, the port binding file for outbound operations always contains definitions for a two-way send port.

When you import this file in a BizTalk application, it creates a two-way send port. However, you may have an orchestration that has a one-way send port. So, when you configure such an orchestration and use the port created by importing the binding file, the port is not available in the list.

This happens because the logical port you created as part of the orchestration is a one-way port while the physical port created in the orchestration is a two-way port. In such cases, you can edit the binding file to make the following changes:. Import the binding file in BizTalk Server Administration console. After you import the new assembly version into the application, you can import the binding file into the application to apply the bindings.

For instructions on editing a binding file, see Customizing Binding Files. When you deploy an assembly into multiple BizTalk groups, you can transport the bindings for the assembly along with the assembly.

This avoids the need to separately configure the bindings for the assembly in each group. You can do this as follows:. Create a binding file for the assembly that you want to deploy by exporting the assembly's bindings. Add the assembly and its binding file to an application. If you are deploying the assembly separately from other artifacts, the application can contain only the assembly and the binding file.

Export an. Import the application. The bindings in the file are automatically applied to the assembly on import. A binding file is not automatically generated for a BizTalk assembly, application, or group, but you can generate a binding file by exporting bindings, as described in Exporting Bindings.

You can then import the binding file into an application or group, as described in How to Import Bindings into a BizTalk Application and How to Import Bindings into a BizTalk Group , which automatically applies its bindings.

Alternatively, you can add the binding file to an application so that its bindings are applied when the application is imported into another group, rather than being applied immediately, as described in How to Add a Binding File to an Application.

Using the last method, you can add multiple binding files to an application and optionally specify a target deployment environment for each one. When you import the application, you can then select which bindings to apply, based on the target deployment environment, as described in How to Import a BizTalk Application. Using the last method, you can also import separate binding files for the different assemblies in your application.

You can edit binding files after you generate them to change their binding information. Note When you use a binding file, you should verify that the artifacts have been bound to the correct host, and that the trust level is appropriate. Important If you leave this field blank, the bindings in this file will always be applied upon application import. In this article. Name of the BizTalk application to which to add the binding file. If the application name is not specified, the default BizTalk application is used.

If the name includes spaces, you must enclose it in double quotation marks ". Option to update an existing binding file. If not specified, and binding file already exists in the application that has the same file name as the file being added, the AddResource operation fails. Full path of the binding file, including the file name. If the path includes spaces, you must enclose it in double quotation marks ". A string that specifies the target deployment environment.

You can use any string, for example Production. The value is case sensitive. If the value includes spaces, you must enclose it in double quotation marks ".