Nebular Blog

Here is a great post on your options, howto's etc.

http://blogs.msdn.com/sharepoint/archive/2007/07/20/installing-windows-server-2008-with-windows-sharepoint-services-3-0.aspx

Sharepoint Server sharepoint services, windows 2008

From Thiago Almeida :

Yes the adapter will work.

You need to make sure the adapter is configured on the bts side successfully (manual config here:http://blogs.breezetraining.com.au/mickb/2009/11/02/BizTalk2009ConfiguringTheSharePointAdapterManually.aspx)

Grab the existing WSSv3 Adapter WS and copy it to the SP2010 environment.

The trick is to add an entry into the Rebinding section of the WebService Web.config

Something like:

OldVersion=11.0.0.0 NewVersion=14.0.0.0

This tells .NET that when the WS is looking for v11 of the Microsoft.SharePoint.dll (v11) use Microsoft.SharePoint.dll (v14)

The SP2010 APIs are ‘mostly’ backwards compatible, certainly around SPLists and SPListItems they are.

 

As always with LOB/Advanced adapters they are often very technology and version dependent. In this case illustrated by :

SP2010 APIs are ‘mostly’ backwards

And its not officially supported. Naturally I’m not going to recommend using the SharePoint adapter for a Critical production system.

back to the your own custom developed interoperable services interfaces.

The supported SharePoint adapter for 2010 will be released later with BizTalk Server 2009R2.

BizTalk Server, Sharepoint Server biztalk, sharepoint 2010

This poster was just uploaded to Microsoft Downloads and I think it is very good high level overview of the ESB Toolkit for Biztalk.

Can be downloaded from:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=844322c2-7a14-4e81-8558-c7941273dd5d

BizTalk Server

In SQL-Server 2005 Microsoft introduced DMVs which are great for index tuning.

Old news, but I have used it a couple of times recently, so I thought I would post a link to this excellent article:

http://www.sql-server-performance.com/articles/per/Identify_Missing_Indexes_Using_SQL_Server_DMVs_p1.aspx

SQL-Server

The BizTalk product group has announced that the next release of BizTalk will be named 2010 and not 2009 R2.

I think it is good, because 2006 and 2006R2 always confused customers and this will make it easier to explain.

Following is list of key capabilities added to the release:

1. Enhanced trading partner management that will enable our customers to manage complex B2B relationships with ease

2. Increase productivity through enhanced BizTalk Mapper. These enhancements are critical in increasing productivity in both EAI and B2B solutions; and a favorite feature of our customers.

3. Enable secure data transfer across business partners with FTPS adapter

4. Updated adapters for SAP 7, Oracle eBusiness Suite 12.1, SharePoint 2010 and SQL Server 2008 R2

5. Improved and simplified management with updated System Center management pack

6. Simplified management through single dashboard which enables IT Pros to backup and restore BizTalk configuration

7. Enhanced performance tuning capabilities at Host and Host Instance level

8. Continued innovation in RFID Space with out of box event filtering and delivery of RFID events

.. and support for Windows 2008 R2 as well.

BizTalk Server

Developer dashboard is a huge improvement to SharePoint development.

In this article Wictor Wílen explains the basics. 

Sharepoint Server sharepoint 2010

http://blog.mastykarz.nl/imtech-spmetal-definition-extension/

I am building a complete SharePoint data layer in SharePoint 2010 out of SharePoint lists. What i really fear is a solution where I end up building and customizing an lot of xml configuration files. Instead i have found one way to make my life easier and my development faster.

• Create a new site (Blank template)
• Create lists as needed in SharePoint Design/SharePoint UI.
• Save the site as a Site Template
• Download the Site Template to a local folder (from site gallery)
• Import to a new SharePoint Project.
  • Take only the lists (and possible the pages if needed)
  • Ignore related fields and what not.
• Set the project to Farm Deployment. (havent tried sandbox from this perspective).

If i try to deploy at this point, the following error occurs:

Error : “Unable to create cross web relations..”

<Field List="Lists/Dataleverandoer" ShowField="ID" Required="TRUE" Type="Lookup" Description="" DisplayName="DataleverandørID" ID="{ba0303fa-4815-4628-8c54-69a922fef705}" Name="NewColumn2" WebId="{576B7339-EF14-4DDF-8759-F9CB6B61676A}" Group="" StaticName="NewColumn2" SourceID="{$ListId:Lists/Indberetning;}" ColName="int1" RowOrdinal="0" Hidden="FALSE" CanToggleHidden="TRUE" EnforceUniqueValues="FALSE" UnlimitedLengthInDocumentLibrary="FALSE" Indexed="TRUE" RelationshipDeleteBehavior="Restrict" />

It happens because the WebId from the original site has been imported.

• Replace WebId="{576B7339-EF14-4DDF-8759-F9CB6B61676A}" with an empty “" value WebId="".
• Deploy.

 Its a one way deployment. i’ll have to change fields and lists on the test site and do it all over, or i can start to configure in the exported project. Either way it has saved me tons of custom configuration hours. 

I have several ideas to improve on this process, but for now this will do ;)

Sharepoint Server sharepoint 2010

I had some trouble getting my relative SharePoint URL's correct.

The solution was quite simpel.

Remember to add “runat=”server” :

<a href="<%$SPUrl:~Site/Udmelding/Udmelding.aspx%>"

title="Udmelding"

runat="server">

Udmelding

</a>