biztalkdeployment Work Item Rss Feed

Commented Feature: Feature: Add Knowledge of Inter-Application Dependency Stack [6130]

fkuiper — Fri, 17 May 2013 11:03:32 GMT

1) If application B relies on A, B has to be undeployed to redeploy A (for example B uses schemas contained in A). It would really be cool if this "stack" could be defined in BTDF. So if I'm fixing something in project A, B has to be undeployed, A has to be redeployed, then B has to be redployed. This would be a feature only for the development environment.

2) For the QA/production environment MSI install, a super-deploy of multiple MSI's in the proper order would also be very nice. Most applications that I've worked with are 5 to 25 inter-related applications with dependencies. BTDF still is very helpful. At one client, we had a spreadsheet of about 25 BT applications to deploy, and the proper order. There was still a large chance the the admins would mess up the deploy if they were not careful.
Comments: ** Comment from web user: fkuiper **

Hi Sander,

I unfortunately can't share the entire script here (there is to much business information in it), but I can share some highlights :)

What I've done is I've written a MSBuild target file containing 4 targets:
- Install feature
- Deploy feature
- Uninstall feature
- Undeploy feature

(a feature in this context is one BTDF-msi by the way)

The install feature target looks something like this:
```
<Target Name="InstallFeature">
<Message Text="Installing '$(FeatureName)'..." />

<Exec Command="msiexec /i "$(FeatureName)-1.0.0.msi" /passive" WorkingDirectory="..\Packages" />
<CreateItem Include="..\Packages\$(FeatureName)-1.0.0.msi">
<Output ItemName="MsiToCopy" TaskParameter="Include" />
</CreateItem>
<Copy SourceFiles="@(MsiToCopy)" DestinationFiles="@(MsiToCopy->'c:\Program Files (x86)\$(FeatureName) for BizTalk\%(FileName)%(Extension)')" />
</Target>
```

And the Deploy feature something like this:

```
<Target Name="DeployFeature">

<Exec
Command=".\Framework\DeployTools\EnvironmentSettingsExporter.exe EnvironmentSettings\SettingsFileGenerator.xml EnvironmentSettings"
WorkingDirectory="c:\Program Files (x86)\$(FeatureName) for BizTalk\1.0\Deployment\"
Condition="Exists('c:\Program Files (x86)\$(FeatureName) for BizTalk\1.0\Deployment\EnvironmentSettings\SettingsFileGenerator.xml')"
/>
<MsBuild
Projects="c:\Program Files (x86)\$(FeatureName) for BizTalk\1.0\Deployment\$(FeatureName).Deployment.btdfproj"
Properties="DeployBizTalkMgmtDB=$(BT_DEPLOY_MGMT_DB);Configuration=Server;SkipUndeploy=true;ENV_SETTINGS=c:\Program Files (x86)\$(FeatureName) for BizTalk\1.0\Deployment\$(ENV_SETTINGS_MASK)"
/>
</Target>
```

Uninstall and undeploy are very simular in setup.

Ofcourse these target in itself will not do anything. There are more scripts. One is the 'main'-project file which will import all 'features' and contain the main targets 'Deploy' and 'Undeploy'

```
<Import Project="Deployment.Targets" />

<Target Name="Deploy">
<CallTarget Targets="@(BizTalkApplication->'%(Identity)_Add')" />
</Target>

<Target Name="Undeploy">
<CallTarget Targets="@(BizTalkApplication->'%(Identity)_Remove')" />
</Target>
```

Last but not least there are the "feature config's" and that's where most of the magic happens:

```
<ItemGroup>
<BizTalkApplication Include="ApplicationA"/>
</ItemGroup>

<Target Name="ApplicationA_Remove" DependsOnTargets="">
<MsBuild
Projects="$(MSBuildProjectFile)"
Targets="UndeployFeature"
Properties="FeatureName=ApplicationA"
/>
<MsBuild
Projects="$(MSBuildProjectFile)"
Targets="UninstallFeature"
Properties="FeatureName=ApplicationA"
/>
</Target>
```

The config for feature B contains exactly the same as the above, but ofcourse you have to replace ApplicationA with ApplicationB. When you start the main msbuild file and call target "Deploy" all the features are installed and deployed and removed in sequence. Now for the magic to happen you can use the "DependsOn" attribute for the "ApplicationA_Add" target like this:

```
<Target Name="ApplicationA_Add" DependsOnTargets="ApplicationB_Add">
...
</Target>
```

Ofcourse you have to add the same dependancy to feature B when removing it, like this:

```
<Target Name="ApplicationB_Remove" DependsOnTargets="ApplicationA_Remove">
...
</Target>
```

With this setting ApplicationB will allway be installed and deployed BEFORE ApplicationA and ApplicationA will allways be remove BEFORE ApplicationB.

And that's how I've solved the dependancy tree problem for our 27 (or so) individual BTDF-msi's.

Hope this will be helpfull to you.

Kind Regards,
Ferdinand.

Created Unassigned: BounceSelectedBizTalkHosts - failes for clustered hosts [10120]

fkuiper — Fri, 17 May 2013 09:56:34 GMT

When restarting host instances for a clustered host the job will fail when restarting the inactive host instance. See log below:

"c:\Program Files (x86)\********* for BizTalk\1.0\Deployment\Framework\DeployTools\cscript64.exe" /nologo "c:\Program Files (x86)\******** for BizTalk\1.0\Deployment\Framework\DeployTools\BounceBizTalkHost.vbs" "MsDynamicsMSMQReceive"
Stopping and starting: MsDynamicsMSMQReceive on BIZ1
Stopping and starting: MsDynamicsMSMQReceive on BIZ1
Stopping and starting: MsDynamicsMSMQReceive on BIZ2
SWbemObjectEx 80C02831:
Retrying: 1
SWbemObjectEx 80C02831:
Retrying: 2
SWbemObjectEx 80C02831:
Retrying: 3
SWbemObjectEx 80C02831:
Retrying: 4

Commented Issue: BTS Admin - Modify resources after BTDF deploy - Dependency not found [10103]

fkuiper — Mon, 13 May 2013 16:54:16 GMT

Hi,

I'm posting this to verify that the behavior is by design;

Let's say Orchestration 'OrderBroker' is using component 'HelperLibrary'. The BTDF project deploys these artefacts based on 2 defined itemgroups:
- Orchestrations
- Components

After deployment, the Components will only be installed in the GAC. When you click on 'Modify Resource' in the BizTalk Administration Console, on the Orchestration 'OrderBroker', you will see a dependency missing error.

I know that at runtime, the GAC due to the .Net framework / probing and stuff, and that the Orchestration works fine, however i would like to ensure that i'm not missing anything.

Can this be confirmed?
Comments: ** Comment from web user: fkuiper **

Hi Thomas,

Maybe this could be as simple as adding an extra property to the items in itemgroup "Components". If this property is set (let's call is AddAsResource) the assembly is added to the BizTalk application. If this property is not set (or present) this step is skipped and the assembly will only be added to the GAC.

Regards,
Ferdinand.

Commented Issue: BTS Admin - Modify resources after BTDF deploy - Dependency not found [10103]

tfabraham — Mon, 13 May 2013 06:10:40 GMT

By design. The Deployment Framework does not add .NET assemblies as resources in the application. One problem with adding assemblies as resources is that a particular assembly must be unique in the BizTalk group, so take our SSOSettingsFileReader.dll as an example. It may be used by nearly every BizTalk app, but it can be added as a resource to only one app... so what to do? I don't have a good answer and there is no functional requirement to add as a resource except to satisfy the dependency analysis tool in 2013. Open to suggestions...

Closed Feature: Feature: Disable the BizTalk App listing in Start Menu--> Program in a Server using BTDF 5.0 [10096]

tfabraham — Fri, 10 May 2013 21:18:46 GMT

Hello

We are using BTDF 5.0 version to deploy the BizTalk App.

After Deployment the BizTalk App(MSI) which is created using BTDF will be listing in Start Menu--> Programs
We need disable the Biztalk app listing the Start Menu--> Programs of the Server/ Machine
Please let us know how can we avoid this ?

Softwares Used
Windows 2008 R2
BTDF 5.0
VS 2010
BTS 2010

Regards
Srikanth.T.V

---------------------

Add CreateStartMenuShortcuts property, default to True
Comments: Resolved with changeset 72831: Add option to disable all Start menu shortcuts on server install (#10096)

Edited Feature: Feature: Disable the BizTalk App listing in Start Menu--> Program in a Server using BTDF 5.0 [10096]

tfabraham — Fri, 10 May 2013 20:30:26 GMT

Created Issue: BTS Admin - Modify resources after BTDF deploy - Dependency not found [10103]

sandernefs — Fri, 10 May 2013 09:58:45 GMT

Hi,

I'm posting this to verify that the behavior is by design;

Let's say Orchestration 'OrderBroker' is using component 'HelperLibrary'. The BTDF project deploys these arefacts based on 2 defined itemgroups:
- Orchestrations
- Components

After deployment, the Components will only be installed in the GAC. When you click on 'Modify Resource' in the BizTalk Administration Console, on the Orchestration 'OrderBroker', you will see a dependency missing error.

I know that at runtime, the GAC due to the .Net framework / probing and stuff, and that the Orchestration works fine, however i would like to ensure that i'm not missing anything.

Can this be confirmed?

Commented Feature: Feature: Add Knowledge of Inter-Application Dependency Stack [6130]

sandernefs — Fri, 10 May 2013 09:11:03 GMT

Hi Ferdinand,

I believe you mean that you use MSBuild to figure out the dependencies and that you only need some sort of 'config' file, which would make life a lot easier.

Are you willing to share this script here as well?

Regards,

Sander

Closed Feature: Feature: Add the UpdateSSO / UpdateBindings as a menu item [10095]

tfabraham — Fri, 10 May 2013 06:08:20 GMT

When making changes to the ExcelSheet / Bindings, you might not want to redeploy everything. Right now, updating the SSO settings / Bindings based on the new 'templates' requires some scripting.

It would be great if the actions available in VS.Net would be available after deployment. This would make it easier to update parts of an deployed application which would be overkill to undeploy fully.
Comments: Resolved with changeset 72823: Add Start menu shortcuts for Quick Deploy, Preprocess and Import Bindings, Terminate Service Instances; remember selected settings file from deploy for use in undeploy (#3858, 7635, 10095)

Closed Feature: Feature: On server deploy, persist settings file path at deploy time and reload at undeploy [7635]

tfabraham — Fri, 10 May 2013 06:08:19 GMT

Currently the settings file path chosen during a server deploy is not saved, so when the solution is undeployed, the original settings file path is unknown. In some situations it would be helpful to use the same settings file again during undeployment.

The deploy can save the value of $(SettingsFilePath) to the registry, and reload the value during undeploy.
Comments: Resolved with changeset 72823: Add Start menu shortcuts for Quick Deploy, Preprocess and Import Bindings, Terminate Service Instances; remember selected settings file from deploy for use in undeploy (#3858, 7635, 10095)

Closed Feature: Feature: Add start menu item on BizTalk App Install for Quick Deploy task [3858]

tfabraham — Fri, 10 May 2013 06:08:18 GMT

Would it be possible to add a Quick Deploy option to the start menu? This'd make patching assemblies a lot faster and easier.
Comments: Resolved with changeset 72823: Add Start menu shortcuts for Quick Deploy, Preprocess and Import Bindings, Terminate Service Instances; remember selected settings file from deploy for use in undeploy (#3858, 7635, 10095)

Commented Feature: Feature: Add the UpdateSSO / UpdateBindings as a menu item [10095]

tfabraham — Fri, 10 May 2013 06:01:41 GMT

Also adding Terminate Service Instances

Closed Issue: Issue: Update sample apps [10102]

tfabraham — Fri, 10 May 2013 05:58:09 GMT

* BasicMasterBindings: Add PropsFromEnvSettings
* Advanced: Move input folder to standard path for other samples
Comments: Resolved with changeset 72822: Minor updates to Advanced and BasicMasterBindings sample apps (#10102)

Edited Issue: Issue: Update sample apps [10102]

tfabraham — Fri, 10 May 2013 05:56:21 GMT

* BasicMasterBindings: Add PropsFromEnvSettings
* Advanced: Move input folder to standard path for other samples

Created Issue: Issue: Update sample apps [10102]

tfabraham — Fri, 10 May 2013 05:56:21 GMT

* BasicMasterBindings: Add PropsFromEnvSettings
* Advanced: Move input folder to standard path for other samples

Edited Feature: Feature: Add start menu item on BizTalk App Install for Quick Deploy task [3858]

tfabraham — Fri, 10 May 2013 05:52:06 GMT

Would it be possible to add a Quick Deploy option to the start menu? This'd make patching assemblies a lot faster and easier.

Edited Feature: Feature: On server deploy, persist settings file path at deploy time and reload at undeploy [7635]

tfabraham — Thu, 09 May 2013 23:35:55 GMT

Closed Feature: Feature: When server MSI is installed, create registry key to hold install path and version [7178]

tfabraham — Thu, 09 May 2013 21:29:41 GMT

When server MSI is installed, create registry key to hold install path and version
Comments: Resolved with changeset 72819: Update server deploy MSI to create InstallPath registry key; fix MSBuild ToolsVer property (#7178)

Edited Feature: Feature: When server MSI is installed, create registry key to hold install path and version [7178]

tfabraham — Thu, 09 May 2013 21:23:52 GMT

When server MSI is installed, create registry key to hold install path and version

Edited Issue: Add the UpdateSSO / UpdateBindings as a menu item [10095]

tfabraham — Thu, 09 May 2013 21:10:24 GMT