ESB Guidance 2.0

regisma — Mon, 09 Mar 2009 13:48:00 GMT

Cette semaine, j'ai installé la CTP2 de l'ESB Guidance V2.0 http://www.codeplex.com/esb .

Après avoir installé correctement les pré-requis (BTS2009 + BAM), cela s'est fait en 30mns montre en main. Voici ci-dessous la procédure que j'ai suivi, c'est une synthèse de ce que j'ai trouvé sur le Net et dans les documentations (installation et utilisateur).

ESB V2.0 Guide d’Installation

1. Prerequisites

1.1. IIS 7.0

1.2. Microsoft BizTalk Server 2009 Enterprise Edition Beta

1.3. Microsoft SQL Server 2008

1.4. Infopath

1.5. Microsoft Visual Studio 2008 SP1

1.6. Enterprise Library 4.0

1.7. Unity Application Block 1.1

1.8. Windows PowerShell 1.0

1.9. Microsoft Chart Controls for Microsoft .NET Framework 3.5 - Required by ESB Management portal

1.10.Microsoft BizTalk Adapter Pack v2 CTP4 - Required by SQL LOB Adapter Sample

1.11.Microsoft WCF LOB Adapter SDK SP2 CTP4 - Required by SQL LOB Adapter Sample

1.12. Microsoft Visual Studio 2008 SDK 1.1 - Required by Itinerary Designer in Visual Studio 2008

1.13. Microsoft UDDI Services 3 - Required by UDDI resolver and dependent samples

1.14.BTS 2009 BAM Tools - Required by Itinerary and Exception BAM tracking

2. Installation ESB Guidance V2

2.1. Start BizTalk Server 2009 Administration Console

2.2. Install the ESB Guidance 2.0 CTP2 January 2009 msi. This step will unpack the necessary files needed to install the ESB Guidance and create necessary registry entries. The itinerary designer is also installed and available from Visual Studio 2008.

2.3. From C:\Program Files\Microsoft ESB Guidance 2.0 CTP2 - January 2009

Import the Microsoft.Practices.ESB.CORE msi into BizTalk using BizTalk Administration tool.

2.4. CD “C:\Program Files\Microsoft ESB Guidance 2.0 CTP2 - January 2009”

Install the BizTalk installer package, named Microsoft.Practices.ESB.CORE msi

2.5. Configure the Exception Management Database, the Exception Web Services, the Itinerary Database and the Core Web Services:

CD “C:\Program Files\Microsoft ESB Guidance 2.0 CTP2 - January 2009\bin”

ESBConfigurationTool.exe

2.6. Install BAM Itinerary tracking:

CD “C:\Program Files\Microsoft ESB Guidance 2.0 CTP2 - January 2009\Bam”

“C:\Program Files\Microsoft BizTalk Server 2009\Tracking\bm” deploy-all -DefinitionFIle:" Microsoft.BizTalk.ESB.BAM.Itinerary.xml"

2.7. Install exception handling BAM tracking:

"C:\Program Files\Microsoft BizTalk Server 2009\Tracking\bm" deploy-all -DefinitionFIle:" Microsoft.BizTalk.ESB.BAM.Exceptions.xml"

2.8. Install UDDI

"C:\Program Files\Microsoft BizTalk Server 2009\bin\ Microsoft.Practices.ESB.UddiPublisher.exe"

3. Installing Samples

3.1. The samples are contained in the source code zip and must be unpacked. The recommended location to unpack the source is C:\projects\microsoft.practices.esb\source. Some of the samples have hardcoded file paths and this should provide a more seamless installation with less issues.

Open a “Visual Studio 2008 Command Prompt”

Gacutil.exe is located in “C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin” set your environment accordingly

Reference to this path is in file “C:\Projects\microsoft.practices.esb\Source\Core\Install\Scripts\ESBFunctions.ps1”, in function “GacOperation”

3.2. Do the installation following the list ordering below:

· Exception Handling – This is where the GlobalBank.ESB BizTalk application is created

o Installation:

CD “C:\Projects\microsoft.practices.esb\Source\Samples\Exception Handling\Install\Scripts”

Setup_bin.cmd

o Configure InfoPath Form Template shares:

1. In Windows Explorer, navigate to the folder \Source\Exception Handling\Source\ESB.ExceptionHandling.InfoPath.Reporting\Publish within the source folder where you installed the ESB Guidance. This folder contains the InfoPath template used to render exception information serialized by the ESB Exception Management Framework.

2. Share this Publish folder using the name Publish, with Read permission for all users. In Windows Server 2003, you can do the following:

2.1. Right-click the Publish folder in Windows Explorer, click Properties, and then click the Sharing tab.

2.2. Click Share this folder and accept the default value Publish (the folder name).

2.3. Click the Permissions button and confirm that the Read check box contains a check mark for the Everyone account group.

2.4. Click OK in each of the two dialog boxes.

3. In Windows Explorer, navigate to the folder \Source\Samples\Exception Handling\Source\ESB.ExceptionHandling.InfoPath.Resubmit\Publish within the source folder where you installed the ESB Guidance. This folder contains the InfoPath template used to demonstrate the Repair and Resubmit use case within the sample application.

4. Share this Publish folder using the name PublishResubmit, with Read permission for all users, as described in step 2.

o Testing: To run the Repair and Resubmit Custom Exception Handler sample

5. Before you run this sample for the first time, ensure that the receive location and send port URLs point to the appropriate directories in the \Source\Samples\Exception Handling\Test\Filedrop folder. The receive location should specify the folder EAIProcess.RequestPort, and the send port URLs should specify the folders EAIProcess.PostApproval and EAIProcessHandler.PostDecline.

6. If the GlobalBank.ESB application is not already running, use the BizTalk Administration Console to start it.

7. Start the sample by copying the sample file named Request_EAIProcessHandler.xml, located in the \Source\Samples\Exception Handling\Test\Data folder, to the folder specified for the EAIProcess.RequestPort_FILE receive location: \Source\Samples\Exception Handling\Test\Filedrop\EAIProcess.RequestPort.

8. Open the folder named EAIProcessHandler.PostDecline (within the \Source\Samples\Exception Handling\Test\Filedrop folder). You will see the "Declined*" message generated by the exception handling orchestration.

9. Open the folder named EAIProcessHandler.RepairSubmit (within the \Source\Samples\Exception Handling\Test\Filedrop folder). You will see a "RepairSubmit" message generated by the exception handling orchestration.

10. Double-click the RepairSubmit file to open it within the appropriate InfoPath template. You will see the message ready for edit and resubmission.

11. Change the value of the Unit Price field from 0 to 2, and then click the Submit button located on the toolbar of the InfoPath form to submit the edited document back to BizTalk for processing. The submit process uses a BizTalk-configured HTTP receive location.

12. Navigate to the EAIProcess.PostApproval folder (within the \Source\Samples\Exception Handling\Test\Filedrop folder). You will now see the "Approval*" document containing the updated value for the unit price.

13. Http Error 404:

BizTalk HTTP Adapter is implemented as an ISAPI application. Make sure BtsHttpReceive.dll is an allowed Web Services Extensions in IIS. Add an entry for instance "BizTalk HTTP Adapter" on the Web Service Extension folde , add the path to BtsHttpReceive.dll (C:\Program Files\Microsoft BizTalk Server 2009\HttpReceive\BTSHTTPReceive.dll)

14. Http Error 405:

your virtual directory does not have execute permissions

· Namespace

o Installation:

CD “C:\Projects\microsoft.practices.esb\Source\Samples\Namespace\Install\Scripts”

Setup_bin.cmd

· Dynamic Resolution

o Installation:

CD “C:\Projects\microsoft.practices.esb\Source\Samples\DynamicResolution\Install\Scripts”

Setup_bin.cmd

· Itinerary

o Installation:

CD “C:\Projects\microsoft.practices.esb\Source\Samples\Itinerary\Install\Scripts”

Setup_bin.cmd

· Scatter Gatherer

o Installation:

CD “C:\Projects\microsoft.practices.esb\Source\Samples\ScatterGather\Install\Scripts”

Setup_bin.cmd

· Multiple Web Services

o Installation:

CD “C:\Projects\microsoft.practices.esb\Source\Samples\MultipleWebServices\Install\Scripts”

Setup_bin.cmd

· SqlAdapter

o Installation:

CD “C:\Projects\microsoft.practices.esb\Source\Samples\SqlAdapter\Install\Scripts”

Setup_bin.cmd

· Transformation Service

o Installation:

CD “C:\Projects\microsoft.practices.esb\Source\Samples\TransformServices\Install\Scripts”

TransformServices_Install.cmd

· Resolver Service

o Installation:

CD “C:\Projects\microsoft.practices.esb\Source\Samples\ResolverService\Install\Scripts”

Setup_bin.cmd

· Biztalk Operations

o Installation:

CD “C:\Projects\microsoft.practices.esb\Source\Samples\BiztalkOperations\Install\Scripts”

Setup_bin.cmd

· Management Portal

o Installation:

CD “C:\Projects\microsoft.practices.esb\Source\Samples\Management Portal\Install\Scripts”

Management_Install.cmd

o Portal URL:

http://localhost/ESB.Portal

http://localhost/ESB.Portal/Default.aspx

http://localhost/ESB.Portal/Reports/Reports.aspx

4. Others

4.1. If your BizTalk Server 2009 project uses the SQL adapter, you must install SQLXML 3.0 SP3. You can install SQLXML 3.0 SP3 from http://go.microsoft.com/fwlink/?LinkID=122479.

This is the error you will get if SQLXLK3.0 is not installed:

A message sent to adapter "SQL" on send port "ALL.Exceptions" with URI "SQL://(local)/EsbExceptionDb/" is suspended.

Error details: Could not load file or assembly 'Microsoft.Data.SqlXml, Version=3.2.2917.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.

ESB Guidance build de Juin 2007.

regisma — Tue, 26 Jun 2007 11:47:00 GMT

La version de Juin 2007 est disponible (correction de problèmes et mise en accord avec BTS 2006 R2): http://www.codeplex.com/esb

Pour mémoire, il existe aussi un site Microsoft ESB: http://www.microsoft.com/biztalk/solutions/soa/esb.mspx

Regis Mauger's blog : ESB

ESB Guidance 2.0

ESB V2.0 Guide d’Installation

1. Prerequisites

ESB Guidance build de Juin 2007.