Ben Runchey’s Integration Dev Blog

a.k.a Ben’s spot to put stuff he does not want to forget

What I Learned Yesterday 4

Bit of knowledge for you terminal services users.  If a machine is just wacko and you cannot quite get things to clean up when it comes to the number of terminal server connections  use mstsc /console at the command line to run the remote desktop tool.  This switch will ignore the max number of administrative connections to a server.

A pretty cool Biztalk documentation utility for finding out how all of those really great posters map back to the help file can be found at the BizTalk server team blog here.  Check this one out!.

While the use of the WSS adapter within BizTalk makes life a lot easier, installing it in your environment when your SharePoint site is on another server is a different story.  It is not that this is hard, but it is not really clear.  So I had to put together a document help out a SharePoint admin at a client of mine so that we could get the adapter web service installed on the SharePoint server.  Find the document here

The solution I am currently working on uses a few document libraries within SharePoint to  keep track of what status a file is in.  We tried to use Views exclusively, but the problem here was getting the security right.  And since we wanted to allow for custom views still, it was too big of a pain.  So we created different document libraries and assigned rights at the document library level, it made things much easier.  The next need was to get all of the necessary Columns and views set up correctly across these three Document Libraries in an automated fashion.  So I created this little application which takes in an XML file to drive the process using the SharePoint object model.  You can download it here.  While this is not the world’s greatest utility, it works and can be used as a basis for future needs. 

Also while working with Sharepoint Object model to create a view within a Document Library that only includes the files set the “Scope” property of the SPView object you are working with to “SPViewScope.Recursive”.  While I think this is understandable, why is it that the API for doing things always seems to have a few areas where they just cannot name things the same (or even remotely the same in this case) as what you see through the UI.  In the UI this is the “Folders” area of the view

I have been doing software for a while now (last 11 years), and I am a big fan of breaking down bigger problems into its smaller core parts, solving each, and then reassembling them to create the solution.  This is for one main reason, smaller is usually simpler.  Smaller teams, smaller problem domain, etc.  While eventually we have to pay the piper and assemble our small parts into the grand solution, even this can be broken into a few core parts.  I found a good arguement for small teams here that I have to agree with.

Upgrading BizTalk 2006 to BizTalk 2006 R2 nuance:  to get the WCF adapters and EDI/AS2 options installed you have to run the installation AGAIN after upgrading.  The upgrade only upgrades your existing configuration.  The additional install will allow you to add the WCF and EDI/AS2 options to your configuration.  Again this makes sense, but is not really clear from reading the documentation.


January 25, 2008 - Posted by | What I Learned Yesterday | ,

No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: