This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: ES/COM+ FAQ and On The Road to Indigo: A Prescriptive Guide
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
Two extremely useful things for me today: the first is the ES/COM+ FAQ that Robert pointed us to that we have been using to troubleshoot a nasty firewall issue with ES all day:
With Windows 2000 (SP3 or QFE 18.1) or Windows Server 2003 COM+ applications can be configured to use a static endpoint. This allows you to open only 2 ports in the firewall. Port 135 for the RPC and the specific port for the COM+ application.
Unfortunately, that isn't the answer yet and we we still have the problem after doing everything in every document so far.
The second is extremely useful for figuring out what to do with today's distributed .NET architectures for Indigo. As Christian blogs, “Rich Turner blogs about On the road to Indigo: Prescriptive Guidance for Today's Technologies Part of this blog: plans with Enterprise Services: It is planned to extend the ES/COM+ infrastructure to talk Indigo on the wire so that ES/COM+ components can call and be called by Indigo Services.“