ESB Toolkit 2.0

Windows 2008 R2, UDDI 3.0 and No Admin Links

Andy Morrison — Fri, 10 Dec 2010 14:25:53 GMT

Windows 2008 R2 might end up giving me a heart attack at some point.

Yesterday I installed and configured UDDI 3.0 as part of an ESB 2.0 install & config. After configuring UDDI 3.0, if I browsed to the localhost/uddi virtual directory from IIS, all of the links would show up in UDDI. If opened up IE and went to the UDDI site only the Home and Search links would show up.

You've probably already guessed at what the "fix" was... I had to Run IE as Administrator. Then when I browse to the UDDI site all of the links show up.

ESB Toolkit 2.0 EndPointConfig (HTTPS with WCF-BasicHttp and the ESB Toolkit 2.0)

Andy Morrison — Thu, 11 Mar 2010 15:36:36 GMT

Earlier this week I had an ESB endpoint (Off-Ramp in ESB parlance) that I was sending to over http using WCF-BasicHttp. I needed to switch the protocol to https: which I did by changing my UDDI Binding over to https: No problem from a management perspective; however, when I tried to run the process I saw this exception:

Event Type: Error

Event Source: BizTalk Server 2009

Event Category: BizTalk Server 2009

Event ID: 5754

Date: 3/10/2010

Time: 2:58:23 PM

User: N/A

Computer: XXXXXXXXX

Description:

A message sent to adapter "WCF-BasicHttp" on send port "SPDynamic.XXX.SR" with URI "https://XXXXXXXXX.com/XXXXXXX/whatever.asmx" is suspended.

Error details: System.ArgumentException: The provided URI scheme 'https' is invalid; expected 'http'.

Parameter name: via

at System.ServiceModel.Channels.TransportChannelFactory`1.ValidateScheme(Uri via)

at System.ServiceModel.Channels.HttpChannelFactory.ValidateCreateChannelParameters(EndpointAddress remoteAddress, Uri via)

at System.ServiceModel.Channels.HttpChannelFactory.OnCreateChannel(EndpointAddress remoteAddress, Uri via)

at System.ServiceModel.Channels.ChannelFactoryBase`1.InternalCreateChannel(EndpointAddress address, Uri via)

at System.ServiceModel.Channels.ChannelFactoryBase`1.CreateChannel(EndpointAddress address, Uri via)

at System.ServiceModel.Channels.ServiceChannelFactory.ServiceChannelFactoryOverRequest.CreateInnerChannelBinder(EndpointAddress to, Uri via)

at System.ServiceModel.Channels.ServiceChannelFactory.CreateServiceChannel(EndpointAddress address, Uri via)

at System.ServiceModel.Channels.ServiceChannelFactory.CreateChannel(Type channelType, EndpointAddress address, Uri via)

at System.ServiceModel.ChannelFactory`1.CreateChannel(EndpointAddress address, Uri via)

at System.ServiceModel.ChannelFactory`1.CreateChannel()

at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.GetChannel[TChannel](IBaseMessage bizTalkMessage, ChannelFactory`1& cachedFactory)

at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.SendMessage(IBaseMessage bizTalkMessage)

MessageId: {1170F4ED-550F-4F7E-B0E0-1EE92A25AB10}

InstanceID: {1640C6C6-CA9C-4746-AEB0-584FDF7BB61E}

I knew from a previous experience that I likely needed to set the SecurityMode setting for my Send Port. But how do you do this for a Dynamic port (which I was using since this is an ESB solution)?

Within the UDDI portal you have to add an additional Instance Info to your Binding named:

EndPointConfig

Then you have to set its value to:

SecurityMode=Transport

Like this:

The EndPointConfig is how the ESB Toolkit 2.0 provides extensibility for the various transports. To see what the key-value pair options are for a given transport, open up an itinerary and change one of your resolvers to a “static” resolver by setting the “Resolver Implementation” to Static. Then select a “Transport Name” ”, for instance to WCF-BasicHttp. At this point you can then click on the “EndPoint Configuration” property for to see an adapter/ramp specific properties dialog (key-value pairs.)

Here’s the dialog that popped up for WCF-BasicHttp:

I simply set the SecurityMode to Transport. Please note that you will get different properties within the window depending on the Transport Name you select for the resolver.

When you are done with your settings, export the itinerary to disk and find that xml; then find that resolver’s xml within that file. It will look like endpointConfig=SecurityMode=Transport in this case. Note that if you set additional properties you will have additional key-value pairs after endpointConfig=

Copy that string and paste it into the UDDI portal for you Binding’s EndPointConfig Instance Info value.

SQL Server does not exist or access denied : 08001 when deploying Microsoft.BizTalk.ESB.BAM.Exceptions.xml

Andy Morrison — Thu, 25 Feb 2010 20:34:02 GMT

When deploying the Microsoft.BizTalk.ESB.BAM.Exceptions.xml BAM activity (as part of the Core ESB Toolkit install) we ran into this error:

---

OLE DB error: OLE DB or ODBC error: DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied : 08001

Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of ‘bam_ExcByApplication’, Name of ‘bamExcByApplication’

---

The issue was that we used a SQL Server Alias while configuring BizTalk to point to our backend SQL servers. This apparently led to the alias name being embedded into the Analysis Services artifact generation when we tried to deployed the BAM Activity. We had the SQL Server Alias on the two BizTalk application servers. We did not have it on the two Analysis Services cluster nodes. Once we added it to the SSAS nodes we were able to successfully deploy the activity.

ESB Toolkit 2.0 Portal 401 Exception

Andy Morrison — Thu, 25 Feb 2010 18:57:31 GMT

I had this exception in the Application Event Log after trying to bring up the portal in IE (after a newly installed and configured BizTalk & ESB platform):

---

Exception information:
Exception type: WebException
Exception message: The remote server returned an error: (401) Unauthorized.

---

I was working in a two (application) server BizTalk environment but I only had this exception on one server. The portal came up fine on the other server.

I looked at IIS log files and found a 401 for /ESB.Exceptions.Service/ExceptionService.svc/GetUserSettings

I browsed to the /ESB.Exceptions.Service/ExceptionService.svc in IE and saw this in the Application Event Log:

---

Exception information:

Exception type: NotSupportedException

Exception message: Security settings for this service require Windows Authentication but it is not enabled for the IIS application that hosts this service.

---

Uhh... I did have that configured: Windows Integrated was turned on and Anonymous was turned off.

The issue was that I did not run the set command for NTAuthenticationProviders (specified in this KB: http://support.microsoft.com/kb/215383) on that server. I had previously ran the set command on the other server in my environment before running the Microsoft.Practices.ESB.UDDIPublisher.exe

Error 194008: An error occurred reading the, esb, Section in the config file.

Andy Morrison — Tue, 09 Feb 2010 20:30:31 GMT

I ran into the error, below, because the host instance didn't have permissions to read the C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\esb.config file. Also, don't forget to restart your host instance (or run iisreset) after you update your permissions.

Event Type: Error
Event Source: BizTalk ESB Toolkit 2.0
Event Category: None
Event ID: 6060
Date:  2/9/2010
Time:  2:03:58 PM
User:  N/A
Computer: XXXXXXXXXXXXX
Description:
Error 194008: An error occurred reading the, esb, Section in the config file.

Source: Microsoft.Practices.ESB.Resolver.ResolverMgr

Method: System.Collections.Generic.Dictionary`2[System.String,System.String] Resolve(Microsoft.Practices.ESB.Resolver.ResolverInfo, Microsoft.BizTalk.Message.Interop.IBaseMessage, Microsoft.BizTalk.Component.Interop.IPipelineContext)

Error Source: Microsoft.Practices.ESB.Resolver

Error TargetSite: Microsoft.Practices.ESB.Configuration.ESBConfigurationSection get_ESBConfig()

Error StackTrace:    at Microsoft.Practices.ESB.Resolver.ResolverConfigHelper.get_ESBConfig()
   at Microsoft.Practices.ESB.Resolver.ResolverMgr.get_ResolverProviderCache()
   at Microsoft.Practices.ESB.Resolver.ResolverMgr.GetResolver(ResolverInfo info)
   at Microsoft.Practices.ESB.Resolver.ResolverMgr.Resolve(ResolverInfo info, IBaseMessage message, IPipelineContext pipelineContext)

ESB Itinerary Selector: Parameter name cannot be null or an empty string. Parameter name: key

Andy Morrison — Tue, 02 Feb 2010 19:43:59 GMT

Event Type: Error

Event Source: BizTalk ESB Toolkit 2.0

Event Category: None

Event ID: 6060

Date: 1/31/2010

Time: 7:06:00 AM

User: N/A

Computer: WS03_OFFICE07

Description:

Parameter name cannot be null or an empty string.

Parameter name: key

Source: Microsoft.Practices.ESB.Resolver.ResolverMgr

Error Source: Microsoft.Practices.EnterpriseLibrary.Caching

Error TargetSite: Void ValidateKey(System.String)

Error StackTrace: at Microsoft.Practices.EnterpriseLibrary.Caching.Cache.ValidateKey(String key)

at Microsoft.Practices.EnterpriseLibrary.Caching.Cache.GetData(String key)

at Microsoft.Practices.EnterpriseLibrary.Caching.CacheManager.GetData(String key)

at Microsoft.Practices.ESB.Cache.Cache`1.Get(String key, Boolean returnAndRemove)

at Microsoft.Practices.ESB.Cache.Cache`1.Get(String key)

at Microsoft.Practices.ESB.Resolver.ResolverMgr.GetResolver(ResolverInfo info)

at Microsoft.Practices.ESB.Resolver.ResolverMgr.Resolve(ResolverInfo info, IBaseMessage message, IPipelineContext pipelineContext)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The issue was that I had the BRI string like this: BRI:// instead of BRI:\\ in the pipeline component's configuration. The latter is the correct way…

Multi-Server ESB Toolkit 2.0 Install (including the Management Portal)

Andy Morrison — Tue, 02 Feb 2010 15:20:41 GMT

[Source: http://geekswithblogs.net/andym/archive/2010/02/02/137753.aspx]

I recently had the pleasure of installing and configuring the ESB Toolkit 2.0 in a multi-server environment. There are some notes on how to do this in the official documentation but they’re not exhaustive and they don’t include details on how to install the management portal in a multi-server environment.

Prerequisites:

· Install and Configure BizTalk in your multi-server environment

· Install and Configure UDDI in your multi-server environment:

o You install and configure the Database components on the SQL Server! Yes, your DBAs are going to be unhappy about this.

o Install and configure the other UDDI components on your BizTalk Servers

o If you have a named SQL instance see Raj’s post here in order to get UDDI configured: http://rajsinghblog.wordpress.com/2009/10/26/configuring-uddi-on-a-non-default-clustered-sql-instance/

o Note that you can only run the Notification Service component on server (I assume you could cluster it but we didn’t get into this…)

ESB Toolkit 2.0 Installation and Configuration:

· Follow the documentation for “Installing the ESB Toolkit Core” on all of your servers

· Please note that you can use the “File” configuration in a multi-server environment. To me, it seems that the docs are pushing the “SSO” configuration but you don’t have to use “SSO” for a multi-server environment. Just run the configuration tool on the second to “n” server and point toward the already created databases. Also I have heard that people have had a lot of problems with the SSO configuration

· Double check the esb.config file and make sure all of the settings are correct

· Watch out for this one during configuration: Exception calling "Create" with "0" argument(s): "Create failed for Login 'MyDomain\BizTalk Server Administrators'." See this for how to fix: http://social.msdn.microsoft.com/Forums/en/biztalkesb/thread/5ea700b9-dd91-4dcf-b442-7ada6210f44f

· You may need to turn Kerberos on for IIS before you can successfully execute the Microsoft.Practices.ESB.UDDIPublisher.exe: http://support.microsoft.com/kb/215383

· Make sure you unpack the samples C:\Program Files\Microsoft BizTalk ESB Toolkit 2.0\ESBSource.zip following the official documentation. (Basically just follow all of the instructions in the “Installing the ESB Toolkit Core” section of the docs

ESB Management portal Installation and Configuration in a Multi-Server Environment:

· Keep in mind that the portal is a sample

· You can’t use the Management_Install scripts on a server that doesn’t have Visual Studio on it because the scripts require the Visual Studio 2008 SDK to function; the Visual Studio 2008 SDK requires Visual Studio for it to be installed… obviously VS won’t be installed in a multi-server environment

· The Portals solution (.sln) does include a setup project. I wanted a debug build so I had to open the solution (on my developer workstation) and in Visual Studio and use Configuration Manager to make sure that the setup project would be built for a “debug” build

· Build the solution, on your developer workstation, and find the .msi that was created for the portal

· Now on each sever in your group, perform the following:

· Create an application pool, in IIS, named EsbPortalNetworkAppPool and have it run under Network Service

· Install the .msi on your first server; the .msi creates the appropriate Virtual Directories (but doesn’t configure them correctly, see the authentication changes, below); use the application pool you created, when prompted. This creates four virtual directories one for the portal and one for each of its three services. Please note that this installs the portal, the ESB.BAM.Service, ESB.Exceptions.Service and the ESB.UDDI.Services to c:\inetpub\wwwroot

· Create the ESBAdmin db using the C:\projects\Microsoft.Practices.ESB\ESBSource\Source\Samples\Management Portal\SQL\ESB.Administration Database.sql file; it blew up at the bottom (find the “Create BizTalk Server Administrators Login” section) because my BizTalk Admin and BizTalk App Users groups were named differently; I manually added the appropriate permissions in SQL Server

· Update the C:\Inetpub\wwwroot\ESB.Portal\web.config with the correct db location and group names (connectionStrings and authorization nodes)

· Update the C:\Inetpub\wwwroot\ESB.Exceptions.Service\web.config to point to the EsbExceptionDb (connectionStrings node)

· Update the C:\Inetpub\wwwroot\ESB.BAM.Service\web.config to point to the BAMPrimaryImport db (connectionStrings node)

· Add Windows Integrated to the ESB.Exceptions.Service, ESB.BAM.Service and ESB.Portal virtual directories

· Removed Anonymous from ESB.Exceptions.Service, ESB.BAM.Service and ESB.Portal virtual directories

· Update the SQL permissions for the ESB Exception Db using the statements found in this thread http://social.msdn.microsoft.com/Forums/en/biztalkesb/thread/1fb510a8-9f4b-4e1e-9261-3273b037786c Props to that guy for banging his head against the wall and figuring out those permissions

· Follow the installation and configuration steps for the “Installing the ESB Management Portal Alert Service” and “Installing the ESB Management Portal UDDI Publishing Service” sections. We did this on one server in the group, no more.

· We also followed the “Configuring Exception Management InfoPath Form Template Shares” section but I don’t see how that is necessary at this point.

Update 2/10/2010:

Make sure your host instance service accounts have access to the esb.config file
In order to use the esbimportutil.exe to deploy itineraries I had to copy the Microsoft.Practices.Modeling.Common, Microsoft.Practices.Modeling.Services and Microsoft.Practices.Modeling.ExtensionProvider (not sure on the last one but the first two are definately needed) assemblies from a developer workstation to the GAC on the server(s)

Update 2/22/2010

Update the EmailTransformation.xslt (for the ESB Portal Alert Service) so that the hyperlinks that it generates point to the server name/dns name for the environment you are installing in

I hope this helps. If I run into issues or I find that I need to correct this post I will update it…