Project Description
AutoDeployer Alpha .01
For ease in ESB installation.
Will be releasing soon:

This project is still in development.


Possible Commands:
///Command – doesRegistryEntryExist – to see if a registry entry exists (example:SOFTWARE/Microsoft/UDDI)
///Command – isInstalled – to see if they have the proper installations (example:SQL Server)
///Command – isServiceInstalled - to see if they have the proper service installed (example:IISADMIN)
///Command - Message
///Command - runCommandLine (EXE, COM, PS1, EXE, MSI, ZIP/UNZIP, Copy Move, Mappings can all be done here.)
///Command - runSQLCommand (Run Command From XML Config)
///Command - runSQLScript (SQL in file)
///Command - runIfServiceExists
///Command - runIfProgramInstalled
///Command - runIfRegistryExists
///Command - addXElement
///Command - replaceOrAddXElementIfMissing
///Command - replaceOrAddXAttributeIfMissing


Uses XML file like SO:
<?xml version="1.0" encoding="utf-8"?>
<AutoDeploy>
<!-- Mark Rowe 2010 autodeploy.codeplex.com-->
<DeploymentObject name="ESBToolKitRemote">
<!-- If you have SQL Scripts to Run This is the default (if the first VALUE is Empty in a runSqlCommand SQL command) -->
<!-- -->
<SQLConnectionString></SQLConnectionString>
<!-- RunAsUser an RunAsPassword are only filled if you need to do impersonation. -->
<RunAsUser></RunAsUser>
<RunAsPassword></RunAsPassword>
<!-- Load External Command when you are concerned about a call being in regular or x86 always use \Program Files\ and it will check if that EXE resides there.
Else it will try <x86> if it is not found in either. It will move to -->
<PrepareCommands>
<PreparedApp>
<Name>BM.EXE</Name>
<File>Program Files\Microsoft BizTalk Server 2009\Tracking\BM.exe</File>
<Description>To run the BAM management utility, you must be member of the dbowner SQL Server Database role in the BAM Primary Import, BAM Star Schema, and BAM Archive databases. You must also have dbowner permissions on the BAM Notification databases.</Description>
<OnError>Bam management utility could not be found. (and we checked all local drives possible)</OnError>
</PreparedApp>
<PreparedApp>
<Name>BTSTASK.EXE</Name>
<File>Program Files\Microsoft BizTalk Server 2009\BTSTASK.exe</File>
<Description>BTSTask</Description>
<OnError>Bam management utility could not be found. (and we checked all local drives possible)</OnError>
</PreparedApp>
<PreparedApp>
<Name>SCRIPTDIRECTORY</Name>
<File>c:\projects\autodeploy\scripts</File>
<Description>BTSTask</Description>
<OnError></OnError>
</PreparedApp>
</PrepareCommands>
<Commands>
<CommandSet priority="1">
<!-- PreReq means it runs before configuration:: true/false to control the process "Stop on Error" -->
<Part>PreReq::false</Part>
<Command>Message</Command>
<Description>Shameless self promotion</Description>
<Values>
<Value>Deployment Helper:Provided By Mark Rowe part of the Auto-Deployer @ autodeploy.codeplex.com</Value>
</Values>
</CommandSet>
<CommandSet priority="2">
<Part>PreReq::false</Part>
<Description>Promoting A nice Guide I used to Build this Deployment Take</Description>
<Command>Message</Command>
<Values>
<Value>This ESB installer was created using the instructions: http://www.biztalkgurus.com/blogs/biztalksyn/archive/2009/06/10/getting-up-and-running-with-biztalk-esb-toolkit-2-0.aspx</Value>
</Values>
</CommandSet>
<CommandSet priority="3">
<Part>PreReq::true</Part>
<Description>Checking for a legitimate version of SQL Server 2005-2008 R2</Description>
<Command>isInstalled</Command>
<Values>
<Value>Microsoft SQL Server 2008::true</Value>
<Value>Microsoft SQL Server 2005::true</Value>
<Value>Microsoft SQL Server 2008 R2::true</Value>
</Values>
<Success>SQL Server Check Passed.</Success>
<Error>Microsoft SQL Server 2005, 8, or 8 R2 or higher Must be installed Link: http://www.microsoft.com/sqlserver/2008/en/us/try-it.aspx"</Error>
</CommandSet>
<CommandSet priority="4">
<Part>PreReq::true</Part>
<Description>Checking for a legitimate version of BizTalk Server 2009-2010</Description>
<Command>isInstalled</Command>
<Values>
<Value>Microsoft BizTalk Server 2009::false</Value>
<Value>Microsoft BizTalk Server 2010::false</Value>
</Values>
<Success>BizTalk Server Check Passed.</Success>
<Error>Microsoft Biztalk Server 2009 or higher Must be installed Link: http://www.microsoft.com/biztalk/en/us/try-it.aspx</Error>
</CommandSet>
<CommandSet priority="5">
<Part>PreReq::true</Part>
<Command>isInstalled</Command>
<Description>Checking to see if the ESB tooklit MSI had been properly run.</Description>
<Values>
<Value>Microsoft BizTalk ESB Toolkit 2.0::true</Value>
</Values>
<Success>ESB 2.0 Toolkit passed.</Success>
<Error>Microsoft BizTalk ESB Toolkit 2.0 Must be installed Link: http://www.microsoft.com/downloads/details.aspx?FamilyID=BC86CF1E-EF29-4B19-95F7-388F64555090&amp;displaylang=en&amp;displaylang=en</Error>
</CommandSet>
<CommandSet priority="6">
<Part>PreReq::true</Part>
<Command>isInstalled</Command>
<Description>Checking for .NET Framework 3.5 SP1.</Description>
<Values>
<Value>Microsoft .NET Framework 3.5 SP1::false</Value>
</Values>
<Success>Microsoft .NET Framework 3.5 SP1 passed.</Success>
<Error>Microsoft .NET Framework 3.5 SP1 must be installed Link: http://www.microsoft.com/downloads/details.aspx?familyid=130F7986-BF49-4FE5-9CA8-910AE6EA442C&amp;displaylang=en</Error>
</CommandSet>
<CommandSet priority="7">
<Part>PreReq::false</Part>
<Command>isInstalled</Command>
<Description>Checking for Microsoft Chart Controls for Microsoft .NET Framework 3.5</Description>
<Values>
<Value>Microsoft Chart Controls for Microsoft .NET Framework 3.5::false</Value>
</Values>
<Success>Microsoft Chart Controls for Microsoft .NET Framework 3.5 is installed properly.</Success>
<Error>Enterprise Library 4.1 should be installed Link: http://www.microsoft.com/downloads/details.aspx?FamilyId=1643758B-2986-47F7-B529-3E41584B6CE5&amp;displaylang=en</Error>
</CommandSet>
<CommandSet priority="8">
<Part>PreReq::false</Part>
<Command>isInstalled</Command>
<Description>Checking for Enterprise Library 4.1</Description>
<Values>
<Value>Enterprise Library 4.1::false</Value>
</Values>
<Success>Enterprise Library 4.1 is installed properly.</Success>
<Error>Enterprise Library 4.1 should be installed Link: http://www.microsoft.com/downloads/details.aspx?FamilyId=1643758B-2986-47F7-B529-3E41584B6CE5&amp;displaylang=en</Error>
</CommandSet>
<CommandSet priority="9">
<Part>PreReq::false</Part>
<Command>isInstalled</Command>
<Description>Checking for Visual Studio 2008 SDK 1.1</Description>
<Values>
<Value>Visual Studio 2008 SDK 1.1::true</Value>
</Values>
<Success>Visual Studio 2008 SDK 1.1 is installed properly.</Success>
<Error>Visual Studio 2008 SDK 1.1 should be installed Link: http://www.microsoft.com/downloads/details.aspx?FamilyID=59ec6ec3-4273-48a3-ba25-dc925a45584d&amp;DisplayLang=en</Error>
</CommandSet>
<CommandSet priority="10">
<!-- Command means it runs before configuration:: true/false to control the process "User Interaction Required before Next Step" -->
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Import/Install C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Microsoft.Practices.ESB.ExceptionHandling.msi</Description>
<!-- ::true/false Checks for <32-64 bit> -->
<Values>
<Value>PreparedApp::BTSTASK.EXE ImportApp /Package:"Program Files\Microsoft BizTalk ESB Toolkit 2.0\Microsoft.Practices.ESB.ExceptionHandling.msi" /Overwrite</Value>
</Values>
</CommandSet>
<CommandSet priority="11">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Import/Install C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\Microsoft.Practices.ESB.CORE.msi</Description>
<Values>
<Value>PreparedApp::BTSTASK.EXE ImportApp /Package:"Program Files\Microsoft BizTalk ESB Toolkit 2.0\Microsoft.Practices.ESB.CORE.msi" /Overwrite</Value>
<Value>true</Value>
</Values>
</CommandSet>
<CommandSet priority="12">
<Part>Command</Part>
<Command>runSQLScript</Command>
<Description>Give SQL Service account permissions to all of the BAM related databases</Description>
<Values>
<Value>USE BAMArchive GO CREATE USER NT SERVICE\SQLSERVERAGENT FOR LOGIN NT SERVICE\SQLSERVERAGENT GO USE BAMPrimaryImport GO CREATE USER NT SERVICE\SQLSERVERAGENT FOR LOGIN NT SERVICE\SQLSERVERAGENT GO USE BAMStarSchema GO CREATE USER NT SERVICE\SQLSERVERAGENT FOR LOGIN NT SERVICE\SQLSERVERAGENT GO</Value>
</Values>
</CommandSet>
<CommandSet priority="13">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>bm deploy-all -DefinitionFile:"Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bam\Microsoft.BizTalk.ESB.BAM.Exceptions.xml"</Description>
<Values>
<Value>PreparedApp::BM.EXE deploy-all -DefinitionFile:"Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bam\Microsoft.BizTalk.ESB.BAM.Exceptions.xml"</Value>
</Values>
</CommandSet>
<CommandSet priority="14">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>bm deploy-all -DefinitionFile:"Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bam\Microsoft.BizTalk.ESB.BAM.Itinerary.xml"</Description>
<Values>
<Value>PreparedApp::BM.EXE deploy-all -DefinitionFile:"Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bam\Microsoft.BizTalk.ESB.BAM.Itinerary.xml"</Value>
</Values>
</CommandSet>
<CommandSet priority="15">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Launch ESBConfigurationTool</Description>
<Values>
<Value>Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bin\ESBConfigurationTool.exe</Value>
</Values>
</CommandSet>
<CommandSet priority="16">
<Part>Command</Part>
<Command>runIfRegistryExists</Command>
<Description>Launch UDDI Configuration</Description>
<Values>
<Value>SOFTWARE/Microsoft/UDDI</Value>
<Value>Program Files\Microsoft BizTalk ESB Toolkit 2.0\Bin\Microsoft.Practices.ESB.UDDIPublisher.exe</Value>
</Values>
<Success>Launching ESBConfigurationTool. Must fill in every field, if this step fails uncheck SSL settign in UDDI MMC and Re-run</Success>
<Error>UDDI Doesn't exist.</Error>
</CommandSet>
<CommandSet priority="17">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Creating Signed Key</Description>
<Values>
<Value>C:\Projects\Microsoft.Practices.ESB\Keys\sn -k Microsoft.Practices.ESB.snk</Value>
</Values>
</CommandSet>
<!-- Setup Powershell -->
<CommandSet priority="18">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Creating Signed Key</Description>
<Values>
<Value>powershell Set-ExecutionPolicy unrestricted</Value>
</Values>
<Success>Creating Signed Key</Success>
<Error></Error>
</CommandSet>
<CommandSet priority="19">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Run C:\Projects\Microsoft.Practices.ESB\Source\Samples\DynamicResolution\Install\Scripts\Setup_bin.cmd</Description>
<Values>
<Value>C:\Projects\Microsoft.Practices.ESB\Source\Samples\DynamicResolution\Install\Scripts\Setup_bin.cmd</Value>
</Values>
</CommandSet>
<CommandSet priority="20">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Run C:\Projects\Microsoft.Practices.ESB\Source\Samples\Itinerary\Install\Scripts\Setup_bin.cmd</Description>
<Values>
<Value>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Itinerary\Install\Scripts\Setup_bin.cmd</Value>
</Values>
</CommandSet>
<CommandSet priority="21">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Run C:\Projects\Microsoft.Practices.ESB\Source\Samples\MultipleWebServices\Install\Scripts\Setup_bin.cmd</Description>
<Values>
<Value>C:\Projects\Microsoft.Practices.ESB\Source\Samples\MultipleWebServices\Install\Scripts\Setup_bin.cmd</Value>
</Values>
</CommandSet>
<CommandSet priority="22">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Run C:\Projects\Microsoft.Practices.ESB\Source\Samples\MultipleWebServices\Install\Scripts\Setup_bin.cmd</Description>
<Values>
<Value>C:\Projects\Microsoft.Practices.ESB\Source\Samples\MultipleWebServices\Install\Scripts\Setup_bin.cmd</Value>
</Values>
</CommandSet>
<CommandSet priority="23">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Run C:\Projects\Microsoft.Practices.ESB\Source\Samples\DynamicResolution\Install\Scripts\Setup_bin.cmd</Description>
<Values>
<Value>C:\Projects\Microsoft.Practices.ESB\Source\Samples\DynamicResolution\Install\Scripts\Setup_bin.cmd</Value>
</Values>
<Success></Success>
<Error></Error>
</CommandSet>
<CommandSet priority="24">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Run C:\Projects\Microsoft.Practices.ESB\Source\Samples\DynamicResolution\Install\Scripts\DynamicResolution_Install.cmd</Description>
<Values>
<Value>C:\Projects\Microsoft.Practices.ESB\Source\Samples\DynamicResolution\Install\Scripts\DynamicResolution_Install.cmd</Value>
</Values>
</CommandSet>
<CommandSet priority="25">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Run C:\Projects\Microsoft.Practices.ESB\Source\Samples\Jms\Install\Scripts\JMS_Install.cmd</Description>
<Values>
<Value>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Jms\Install\Scripts\JMS_Install.cmd</Value>
</Values>
</CommandSet>
<CommandSet priority="26">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Run C:\Projects\Microsoft.Practices.ESB\Source\Samples\Jms\Install\Scripts\Setup_bin.cmd</Description>
<Values>
<Value>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Jms\Install\Scripts\Setup_bin.cmd</Value>
</Values>
</CommandSet>
<CommandSet priority="27">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Run C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\Install\Scripts\Management_Install.cmd</Description>
<Values>
<Value>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\Install\Scripts\Management_Install.cmd</Value>
</Values>
</CommandSet>
<!-- Run C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\Install\Scripts\Management_Install.cmd -->
<CommandSet priority="28">
<Part>End</Part>
<Command>Message</Command>
<Description>Point to the rest of installation. Building the App, setting Build variables.</Description>
<Values>
<Value>Start at step 17: http://www.biztalkgurus.com/blogs/biztalksyn/archive/2009/06/10/getting-up-and-running-with-biztalk-esb-toolkit-2-0.aspx</Value>
</Values>
</CommandSet>
</Commands>
</DeploymentObject>
<DeploymentObject name="EDIGuidance">
<!-- If you have SQL Scripts to Run This is the default (if not connection string found in SQL command) -->
<SQLConnectionString></SQLConnectionString>
<!-- RunAsUser an RunAsPassword are only filled if you need to do impersonation. -->
<RunAsUser></RunAsUser>
<RunAsPassword></RunAsPassword>
<PrepareCommands>
<PreparedApp>
<Name>BM.EXE</Name>
<File>Program Files\Microsoft BizTalk Server 2009\Tracking\BM.exe</File>
<Description>To run the BAM management utility, you must be member of the dbowner SQL Server Database role in the BAM Primary Import, BAM Star Schema, and BAM Archive databases. You must also have dbowner permissions on the BAM Notification databases.</Description>
<OnError>Bam management utility could not be found. </OnError>
</PreparedApp>
<PreparedApp>
<Name>BTSTASK.EXE</Name>
<File>Program Files\Microsoft BizTalk Server 2009\BTSTASK.exe</File>
<Description>BTSTask</Description>
<OnError>BTSTASK utility could not be found. Please point the BTSTASK.EXE PreparedApp entry to the exe</OnError>
</PreparedApp>
<PreparedApp>
<Name>SCRIPTDIRECTORY</Name>
<File>c:\projects\autodeploy\scripts</File>
<Description>Default scripts location.</Description>
<OnError>Your scripts directory was not found this by default is c:\projects\autodeploy\scripts\ please change the PreparedApp element on EDI GUidance to point to the autodeploy\scripts directory.</OnError>
</PreparedApp>
<PreparedApp>
<Name>RULESCOMPOSER</Name>
<File>Program Files\Common Files\Microsoft BizTalk\Microsoft.RuleComposer.exe</File>
<Description>Default scripts location.</Description>
<OnError>Your scripts directory was not found this by default is c:\projects\autodeploy\scripts\ please change the PreparedApp element on EDI GUidance to point to the autodeploy\scripts directory.</OnError>
</PreparedApp>

</PrepareCommands>
<Commands>
<CommandSet priority="1">
<Part>PreReq::false</Part>
<Command>Message</Command>
<Description>Shameless EDIGuidance Promotion</Description>
<Values>
<Value>EDIGuidance By ediguidance.codeplex.com,Karl Rissland and the team @ EDIGuidance.Codeplex.com. E-Mail if you would like to be part of our team.</Value>
</Values>
</CommandSet>
<CommandSet priority="2">
<Part>Command</Part>
<Command>doesDirectoryExist</Command>
<Description>Shameless EDIGuidance Promotion</Description>
<Values>
<Value>c:\projects\AutoDeployer\EDIGuidance.Zip</Value>
<Value>Unzip EDIGuidance into the "C:\projects" folder. Once completed and you see c:\projects\EDIGuidance\</Value>
</Values>
</CommandSet>
<CommandSet priority="3">
<Part>PreReq::false</Part>
<Command>doesFileExist</Command>
<Description>Checking for deployrules.</Description>
<Values>
<Value>PreparedApp::SCRIPTDIRECTORY\deployrules.exe</Value>
</Values>
<Success>Deploy rules found!</Success>
<Error>This step may be skipped if you plan on manually deploying your vocabularies and rules. Otherwise please follow this link : http://go.microsoft.com/fwlink/?LinkId=146125 Download the package, Run setup.bat and then move the deployrules.exe from the \bin directory into the c:\projects\autodeploy\scripts\ directory. If your auto deploy directory resides in a different location, please alter this deployment.xml to point the SCRIPTSDIRECTORY to your proper path.</Error>
</CommandSet>
<CommandSet priority="4">
<Part></Part>
<Command>isInstalled</Command>
<Description>Microsoft BizTalk Server 2009 Hotfix.</Description>
<Values>
<Value>Microsoft BizTalk Server 2009 Hotfix See KB article 977428::false</Value>
</Values>
<Success>Microsoft BizTalk Server 2009 Hotfix [See KB article 977428
is installed properly.</Success>
<Error>Microsoft BizTalk Server 2009 Hotfix See KB article 977428 should be installed to avoid compilation errors. Link: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=977428&amp;kbln=en-us</Error>
</CommandSet>
<CommandSet priority="5">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Description>Add c:\projects\EDI Guidance\Main\SRC\BamDefFile.xml</Description>
<Values>
<Value>PreparedApp::BM.EXE update-all -DefinitionFile:"c:\projects\EDI Guidance\Main\SRC\BamDefFile.xml"</Value>
</Values>
</CommandSet>
<!-- TO DO REFILL THIS OUT-->
<CommandSet priority="6">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Values>
<Value>PreparedApp::BM.EXE update-all -DefinitionFile:"c:\projects\EDI Guidance\Main\SRC\BamDefFile.xml"</Value>
</Values>
</CommandSet>
<!--Load EDI Guidance SQL helper scripts -->
<CommandSet priority="7">
<Part>Command</Part>
<Command>runSQLScript</Command>
<Value>c:\projects\edi guidance\main\src\database\CREATEEDIToolsGetNewInterchangesSP.sql</Value>
<Description>CreateEDIToolsGetNewInterchangesSP.sql found at C:\projects\EDI Guidance\Main\src\Database</Description>
</CommandSet>
<!-- Auto Deploy Vocabularies -->
<!-- Auto Deploy rules InboundItineraryResolution-->
<CommandSet priority="8">
<Part>Command</Part>
<Command>RunIfFileExists</Command>
<Values>
<Value>PreparedApp::SCRIPTDIRECTORY\DeployRules.exe</Value>
<Value>PreparedApp::SCRIPTDIRECTORY\DeployRules.exe /M c:\projects\EDI Guidance\Main\Src\BRE\EDIGuidance.InBoundItineraryResolution.1.15.xml /P </Value>
</Values>
<Description>Auto Deploy rules InboundItineraryResolution</Description>
</CommandSet>
<!-- Auto Deploy rules OutBoundItineraryResolution-->
<CommandSet priority="9">
<Part>Command</Part>
<Command>RunIfFileExists</Command>
<Values>
<Value>PreparedApp::SCRIPTDIRECTORY\DeployRules.exe</Value>
<Value>PreparedApp::SCRIPTDIRECTORY\DeployRules.exe /M c:\projects\EDI Guidance\Main\Src\BRE\EDIGuidance.OutBoundItineraryResolution.1.3.xml /P </Value>
</Values>
<Description>Auto Deploy rules OutBoundItineraryResolution</Description>
</CommandSet>
<!-- Auto Deploy rules PropertyResolution-->
<CommandSet priority="10">
<Part>Command</Part>
<Command>RunIfFileExists</Command>
<Values>
<Value>PreparedApp::SCRIPTDIRECTORY\DeployRules.exe</Value>
<Value>PreparedApp::SCRIPTDIRECTORY\DeployRules.exe /M c:\projects\EDI Guidance\Main\Src\BRE\EDIGuidance.PropertyResolution.1.2.xml /P </Value>
</Values>
<Description>Auto Deploy rules Property Resolution</Description>
</CommandSet>
<CommandSet priority="11">
<Part>message</Part>
<Command>Message</Command>
<Values>
<Value>Please check the Business Rules Composer to see if the vocabularies were deployed.</Value>
</Values>
<Description>Message</Description>
</CommandSet>
<CommandSet priority="12">
<Part>Command</Part>
<Command>RunIfFileExists</Command>
<Values>
<Value>PreparedApp::RULESCOMPOSER</Value>
<Value>PreparedApp::RULESCOMPOSER</Value>
</Values>
<Description>Run Rules Composer for visual confirmation </Description>
</CommandSet>
<CommandSet priority="13">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Values>
<Value>C:\Projects\EDI Guidance\Main\Src\Install\BRE_StaticSupport.reg</Value>
</Values>
</CommandSet>
<CommandSet priority="14">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Values>
<Value>PreparedApp::BTSTASK AddResource -Source:C:\Projects\EDI Guidance\Main\Src\Orchestrations\bin\Debug\Microsoft.Practices.ESB.PipelineComponents.dll -Type:BizTalkAssembly -Options:GacNow /Overwrite</Value>
</Values>
</CommandSet>
<CommandSet priority="15">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Values>
<Value>PreparedApp::BTSTASK AddResource -Source:C:\Projects\EDI Guidance\Main\Src\Orchestrations\bin\Debug\Microsoft.Practices.ESB.Itinerary.PipelineComponents -Type:BizTalkAssembly -Options:GacNow /Overwrite</Value>
</Values>
</CommandSet>
<CommandSet priority="16">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Values>
<Value>PreparedApp::BTSTASK AddResource -Source:C:\Projects\EDI Guidance\Main\Src\Orchestrations\bin\Debug\Microsoft.BizTalk.Samples.EDIGuidance.Schemas.dll -Type:BizTalkAssembly -Options:GacNow /Overwrite</Value>
</Values>
</CommandSet>
<CommandSet priority="17">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Values>
<Value>PreparedApp::BTSTASK AddResource -Source:C:\Projects\EDI Guidance\Main\Src\Orchestrations\bin\Debug\Microsoft.BizTalk.Samples.EDIGuidance.Pipelines.dll -Type:BizTalkAssembly -Options:GacNow /Overwrite</Value>
</Values>
</CommandSet>
<CommandSet priority="18">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Values>
<Value>PreparedApp::BTSTASK AddResource -Source:C:\Projects\EDI Guidance\Main\Src\Orchestrations\bin\Debug\Microsoft.BizTalk.Samples.EDIGuidance.Orchestrations.dll -Type:BizTalkAssembly -Options:GacNow /Overwrite</Value>
</Values>
</CommandSet>
<CommandSet priority="19">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Values>
<Value>PreparedApp::BTSTASK AddResource -Source:C:\Projects\EDI Guidance\Main\Src\Orchestrations\bin\Debug\Microsoft.BizTalk.Samples.EDIGuidance.Maps.dll -Type:BizTalkAssembly -Options:GacNow /Overwrite</Value>
</Values>
</CommandSet>
<CommandSet priority="20">
<Part>Command</Part>
<Command>runCommandLine</Command>
<Values>
<Value>PreparedApp::BTSTASK AddResource -Source:C:\Projects\EDI Guidance\Main\Src\Orchestrations\bin\Debug\Microsoft.BizTalk.Samples.EDIGuidance.HelperComponents.dll -Type:BizTalkAssembly -Options:GacNow /Overwrite</Value>
</Values>
</CommandSet>

<!-- EDIT ESB.CONFIG -->
<CommandSet priority="21">
<Part>Command</Part>
<Command>addXElement</Command>
<Values>
<Value>Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config</Value>
<Value>/local-name()='configuration' and namespace-uri()=''/local-name()='esb' and namespace-uri()=''/local-name()='itineraryServices' and namespace-uri()=''/local-name()='itineraryService' and namespace-uri()=''</Value>
<Value>&lt;itineraryService id="C4CE6621-D4A8-44f6-A9EA-292A7460CB94" name="EDIPropertyService" type="Microsoft.BizTalk.Samples.EDIGuidance.Orchestrations.EDIPropertyService, Microsoft.BizTalk.Samples.EDIGuidance.Orchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7238d11e949b827e" scope="Orchestration" stage="None"/&gt;</Value>
</Values>
</CommandSet>
<CommandSet priority="22">
<Part>Command</Part>
<Command>addXElement</Command>
<Values>
<Value>Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config</Value>
<Value>/local-name()='configuration' and namespace-uri()=''/local-name()='esb' and namespace-uri()=''/local-name()='itineraryServices' and namespace-uri()=''/local-name()='itineraryService' and namespace-uri()=''</Value>
<Value>&lt;itineraryService id="C6C03732-1E53-4b3c-AEE4-80A09E4FF4BB" name="EDIPostBatchService" type="Microsoft.BizTalk.Samples.EDIGuidance.Orchestrations.EDIPostBatchService, Microsoft.BizTalk.Samples.EDIGuidance.Orchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7238d11e949b827e" scope="Orchestration" stage="None"/&gt; </Value>
</Values>
</CommandSet>
<CommandSet priority="23">
<Part>Command</Part>
<Command>addXElement</Command>
<Values>
<Value>Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config</Value>
<Value>/local-name()='configuration' and namespace-uri()=''/local-name()='esb' and namespace-uri()=''/local-name()='itineraryServices' and namespace-uri()=''/local-name()='itineraryService' and namespace-uri()=''</Value>
<Value>&lt;itineraryService id="9BFDE334-4F57-42ca-BFBE-03440CAC5C0F" name="EDIProcess997Service" type="Microsoft.BizTalk.Samples.EDIGuidance.Orchestrations.EDIProcess997Service, Microsoft.BizTalk.Samples.EDIGuidance.Orchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7238d11e949b827e" scope="Orchestration" stage="None"/&gt; </Value>
</Values>
</CommandSet>
<CommandSet priority="24">
<Part>Command</Part>
<Command>addXElement</Command>
<Values>
<Value>Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config</Value>
<Value>/local-name()='configuration' and namespace-uri()=''/local-name()='esb' and namespace-uri()=''/local-name()='itineraryServices' and namespace-uri()=''/local-name()='itineraryService' and namespace-uri()=''</Value>
<Value>&lt;itineraryService id="7C7C4FDA-221A-4b5b-B0F9-B2878492CB77" name="EDIProcess997WithTimeoutService" type="Microsoft.BizTalk.Samples.EDIGuidance.Orchestrations.EDIProcess997WithTimeoutService, Microsoft.BizTalk.Samples.EDIGuidance.Orchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7238d11e949b827e" scope="Orchestration" stage="None"/&gt;</Value>
</Values>
</CommandSet>
<CommandSet priority="25">
<Part>Command</Part>
<Command>addXElement</Command>
<Values>
<Value>Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config</Value>
<Value>/local-name()='configuration' and namespace-uri()=''/local-name()='esb' and namespace-uri()=''/local-name()='itineraryServices' and namespace-uri()=''/local-name()='itineraryService' and namespace-uri()=''</Value>
<Value>&lt;itineraryService id="2E79D097-655D-49bb-9B29-0935BC002787" name="EDIGenerateTransactionAcksService" type="Microsoft.BizTalk.Samples.EDIGuidance.Orchestrations.EDIProcess997Transactions, Microsoft.BizTalk.Samples.EDIGuidance.Orchestrations, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7238d11e949b827e" scope="Orchestration" stage="None"/&gt; </Value>
</Values>
</CommandSet>
<CommandSet priority="26">
<Part>End</Part>
<Command>Message</Command>
<Values>
<Value>If you have the itinerary designer open, you will need to close and reopen the itinerary for the changes to take affect. To verify the changes, add an orchestration extender and drop down the service name list. You should see the 5 Itinerary Services we added to the config file.</Value>
</Values>
</CommandSet>
<CommandSet priority="27">
<Part>End</Part>
<Command>Message</Command>
<Values>
<Value>If you have further questions about EDI Guidance please contact ediguidance.codeplex.com @ </Value>
</Values>
</CommandSet>
</Commands>
</DeploymentObject>
</AutoDeploy>

Last edited Sep 23, 2010 at 3:22 PM by MarkRowe, version 5