WCF: Set up environment to use Transport level security (SSL)

We should install the certificate to the server that hosts the services with Transport level security.

For tests we could use the self-made certificate, for production we recommend to use the certificate issued by the industrial certificate provider as the VeriSign.

1. Install Microsoft .NETFramework2.0 Software Development Kit (SDK) (x64) [http://www.microsoft.com/downloads/details.aspx?familyid=1AEF6FCE-6E06-4B66-AFE4-9AAD3C835D3D&displaylang=en]. It is installed by default to the “C:\Program Files\Microsoft.NET\SDK\v2.0 64bit\Bin ” folder.

2. [Optionally, only if you also have server certificate and want to refresh it]”C:\Program Files\Microsoft.NET\SDK\v2.0 64bit\Bin\certmgr.exe” -del -r LocalMachine -s My -c -n MyCompany-HTTPS-Server

3. “C:\Program Files\Microsoft.NET\SDK\v2.0 64bit\Bin\makecert.exe” -sr LocalMachine -ss My -n CN= MyCompany-HTTPS-Server -sky exchange -sk MyCompany-HTTPS-Key

4. Install the new certificate to the IIS by the Web Server Certificate Wizard. Open IIS Admin, choose the Default web-site, Properties, Directory Security tab, Secure communication – Server Certificate button, it starts the Web Server Certificate Wizard .


To expose the service metadata by HTTPS and HTTP use:

<behaviors>
<serviceBehaviors>
<behavior name=”ServiceBehavior_Name”>
<serviceMetadata httpGetEnabled=”true” httpsGetEnabled=”true” />
<serviceDebug includeExceptionDetailInFaults=”false” />
</behavior>
</serviceBehaviors>
</behaviors>

To expose the service metadata by HTTPS or HTTP only, change attribute the httpsGetEnabled or httpGetEnabled to false.


[2] Transport Security Overview – http://msdn.microsoft.com/en-us/library/ms729700.aspx

Time Off

Time Off

I’m taking a few weeks off after working at Tech Ed for the last couple of weeks.


I have seen some great stuff already this trip, like the Space Shuttle launch in Orlando, a great air show in Quebec City, the Colorado Rockies, and today Mount Rushmore.  I’ll post some pictures when I get a chance.

BuildCop

Code criminals beware… there are a number of ‘cops’ on patrol. :-). As if FxCop, StyleCop and MapCop weren’t enough, we now have BuildCop.
But seriously, this looks like another nifty tool for a teams arsenal. Its written by GAX Guru Jelle Druyts and his post about it is here. From the blurb on the site
BuildCop […]

BizTalk Server 2006 – BTARN 3.5 Configuration Tips

Just a quick post to those of you planning to use the BizTalk Accelerator for RosettaNet 3.5. There are a few little “issues” that you need to know about before you get started.

Accounts, Hosts & Host Instances

BTARN 3.5 requires the use of Hosts that have the Authentication Trusted option enabled. This has to be configured BEFORE you create any Host Instances. I recommend creating a new Service Account, a new In-Process Host, a new Isolated Host and then a new Host Instance for each of these as shown in the table below. You will also need to create new HTTP and SQL Send Handlers and Receive Handlers as well.

Note: The In-Process Host Instance account and Isolated Host Instance account must be the same for BTARN to work properly!

Service Account: Domain\AccountName
In-Process Host: RosettaNetApplication
In-Process Host Instance: RosettaNetApplication
Isolated Host: RosettaNetIsolatedHost
Isolated Host Instance: RosettaNetIsolatedHost
SQL Send Handler: RosettaNetApplication
SQL Receive Handler: RosettaNetApplication
HTTP Receive Handler: RosettaNetIsolatedHost
HTTP Send Handler: RosettaNetApplication

Installation & Configuration

Don’t use “localhost” for your BizTalk Server or Web Server name when running the Configuration Wizard. Use the NetBIOS name of your BizTalk Server machine and the NetBIOS name of your Web Server machine instead. The Configuration Wizard will fail with a strange error if you use default “localhost”.

Why? I have no earthly idea but I will be submitting this to the BizTalk team as a bug!

One final note

All the BTARN bits are deployed to the BizTalk Application 1 by default. I’m still trying to find a way to isolate the RosettaNet bits (schemas, maps, pipelines, ports and orchestrations) in their own BizTalk Apllication much like the new EDI/AS2 bits are. I’ll post if I find an easy way to accomplish this.

Happy Integrations!

Currently listening to: Dave Koz – Castle of Dreams

BizTalk 2004 SP2 Upgrade

I installed an SP2 upgrade over the weekend on BizTalk 2004. Here were the take aways.

1. Always have the BizTalk user account as God mode for the SQL server that hosts the BizTalk Databases.

2. Shrink the MsgBox and Tracking Databases before installing the SP2 upgrade. (http://msdn2.microsoft.com/en-us/library/bb203857.aspx for the MsgBoxDb and KB894253 for the Tracking DB)

3. If the database file sizes don’t decrease use the following SQL methods:

dbcc shrinkdatabase(<DatabaseName>)
dbcc shrinkfile (<DatabaseName>, <size in MB>)