The Deployment Framework for BizTalk is the most powerful and customizable, yet easy-to-use toolkit for deploying and configuring your BizTalk solutions.
MIT License
53
stars
24
forks
source link
ESB Toolkit: Create a custom Resolver that can pull values from SSO based on the SettingsFileGenerator.xml spreadsheet #115
The SettingsFileGenerator.xml Excel spreadsheet allows the developer to define multiple runtime environments, then define settings that have a value for each runtime environment or a default value that applies to all environments. This is the foundation for the binding file (or other XML files) templating process, where a master XML file is converted to an environment-specific XML file by merging in settings from the spreadsheet (using XmlPreprocess.exe).
During deployment, one XML file is exported from the spreadsheet for each runtime environment, containing all settings and values for that particular environment. The environment-specific settings XML file for the target environment is loaded into the SSO database during deployment, and the settings are available at runtime using the SSOSettingsFileReader .NET component.
This same capability should be available for use with the ESB Toolkit. By creating a custom Resolver component, when an itinerary that uses the custom Resolver is executed by BizTalk, the custom Resolver can connect to SSO and extract setting values at runtime (loaded into SSO from the Excel spreadsheet as described above). This is an alternative to the XPath resolver, Static resolver, etc. It lets the resolver configuration be based off of the same spreadsheet that is used to maintain binding file and other environment-specific and default settings.
The Resolver should offer the same properties as the XPath and Static resolvers, but the developer should set the property values to be the names of settings in SettingsFileGenerator.xml.
This work item was migrated from CodePlex
CodePlex work item ID: '6235'
Assigned to: 'tfabraham'
Vote count: '0'
The SettingsFileGenerator.xml Excel spreadsheet allows the developer to define multiple runtime environments, then define settings that have a value for each runtime environment or a default value that applies to all environments. This is the foundation for the binding file (or other XML files) templating process, where a master XML file is converted to an environment-specific XML file by merging in settings from the spreadsheet (using XmlPreprocess.exe). During deployment, one XML file is exported from the spreadsheet for each runtime environment, containing all settings and values for that particular environment. The environment-specific settings XML file for the target environment is loaded into the SSO database during deployment, and the settings are available at runtime using the SSOSettingsFileReader .NET component. This same capability should be available for use with the ESB Toolkit. By creating a custom Resolver component, when an itinerary that uses the custom Resolver is executed by BizTalk, the custom Resolver can connect to SSO and extract setting values at runtime (loaded into SSO from the Excel spreadsheet as described above). This is an alternative to the XPath resolver, Static resolver, etc. It lets the resolver configuration be based off of the same spreadsheet that is used to maintain binding file and other environment-specific and default settings. The Resolver should offer the same properties as the XPath and Static resolvers, but the developer should set the property values to be the names of settings in SettingsFileGenerator.xml.
This work item was migrated from CodePlex
CodePlex work item ID: '6235' Assigned to: 'tfabraham' Vote count: '0'