- Platform choice:
- Virtual Server 2005 R2 x86 or x64 is supported
- Recommended against running production environments on VPC
- 3rd Party: See KB article 897615
- Architecture considerations:
- Recommended NOT to virtualize SQL
- Restricted to 32-bit SharePoint, so this reduces addressable memory
- No hard-and-fast rules as to how performance changes when you go from physical to virtual
- SharePoint 2003-2007 migration webcast - http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032330523&CountryCode=US
- Infopath integration with the BDC - Other than using BDC data in list/library columns in InfoPath forms, you can write a web service to make use of the BDC’s Runtime Object Model:
The Runtime object model is designed for use by the Business Data Catalog clients and applications. The Runtime object model has two major functions:
- It offers an intuitive, object-oriented interface that abstracts the underlying data sources. The Runtime object model insulates the client from learning application-specific coding paradigms, and allows clients to access all business applications in a single, simplified way. Because of the Runtime object model, calling a method on an SAP application is very similar to calling a method on Siebel or executing a query in SQL.
- It allows you to read the metadata objects from the metadata database and execute the business logic described there. The runtime object model is cached and fast, so clients that just need to query the metadata database for metadata information use the Runtime object model.