Comments on: Everything You Need to Know about BDC: Part 1 of 8

By: Everything You Need to Know about BDC: Part 8 of 8 | SharePoint Magazine

Everything You Need to Know about BDC: Part 8 of 8 | SharePoint Magazine — Fri, 12 Feb 2010 12:21:42 +0000

[...] Part 1, BDC Purpose and technical architecture [...]

By: Everything You Need to Know about BDC: Part 5 of 8 | SharePoint Magazine

Everything You Need to Know about BDC: Part 5 of 8 | SharePoint Magazine — Fri, 06 Nov 2009 08:45:58 +0000

[...] Part 1, BDC Technical Architecture [...]

By: fdaske

fdaske — Sun, 26 Jul 2009 18:05:44 +0000

A more simple approach even for Windows SharePoint Services: The SharePoint Business Data List Connector (BDLC) provides the complete read-only features of a common SharePoint list for almost any external data sources in 3 simple steps only:

- enter connection string
- enter select statement
- choose primary key(s)

Then your data are in a real SharePoint list. Updates are done in backround very fast (batch update, changed data only). So you have ALL list features available, e.g. notifications and workflows, if external data records changed and business actions must be taken.

http://www.layer2.de/EN/PRODUCTS/Pages/SharePoi...

By: Me

Me — Tue, 14 Jul 2009 20:21:58 +0000

Might be useful if you actually linked through to the various parts of the series. Duh.

By: Randy Williams

Randy Williams — Tue, 14 Apr 2009 06:11:42 +0000

If both 01 and 02 servers are part of the same farm as web front ends (WFE), there's no need to transfer web parts between the servers. This is handled automatically (although I do assume that you have some type of network load-balancer in place) since both servers share the same configuration and content. You will want to make sure both servers can connect to the SQL Server for the BDC web parts to render. You might find this other blog post I wrote helpful when troubleshooting connections to SQL Server: http://www.synergyonline.com/blog/blog-moss/Lis...

By: jabailo

jabailo — Fri, 10 Apr 2009 09:47:36 +0000

That makes it clear, thank you!

I'm working on a farm that has two web servers. The 01 server doesn't have 1433 and the 02 server does. I set up my web parts page on 01. I am guessing then that I need to build on the 02 server…wonder if there's an easy way to transfer my web parts page to run via the 02 server (?)

By: Randy Williams

Randy Williams — Fri, 10 Apr 2009 09:08:38 +0000

Hi,

If you're using TCP/IP sockets as your network protocol for SQL Server, then you will need to make sure that your web server can deliver TCP 1433 (and 1434, I think) packets to SQL. In this way, your SharePoint web server (or web front end as we say) is the client to SQL Server. Hope this helps answer.

By: jabailo

jabailo — Thu, 09 Apr 2009 09:50:43 +0000

If the Sharepoint database is remote from the Sharepoint web server (MOSS07), then does the LOB need connectivity (port 1433 for SQL Server) to the web server (farm) or database server.

By: markus

markus — Wed, 18 Feb 2009 11:17:09 +0000

HI All,
I have created a webpart which has 3 fields. One of the field will be provided by a BDC which has already created. Can you show me how to add a BDC into a webpart programmatically.

Thanks,
Markus

By: Randy Williams

Randy Williams — Thu, 27 Nov 2008 11:33:01 +0000

Hi Fred,

Article 2 has been written already and should be published shortly. I think I provide pretty good guidance on how both a stored procedure and an ad hoc select statement would work in the context of a finder/specific finder/IdEnumerator methods. Let me know what you think when it comes out. If I missed something, let me know, and I'll try to fill it in.

By: Fred H

Fred H — Wed, 26 Nov 2008 00:24:04 +0000

Randy,
Great intro. I look forward to the remainder of your series very much!

If I could wish for one thing from your Part 2 article on AD files it would be for some valuable explanation and tip on how to taylor stored procedures to fit within the BDC framework. I understand that you have to write seperate procs for the Finder method and Specific Finder method but I'm having a hard time wrapping my head around how make that work, practically, when adapting an existing business proc that doesn't really require this delineation-other than for the BDC.

By: Randy Williams

Randy Williams — Mon, 24 Nov 2008 11:37:09 +0000

Hi Steve,

I considered mentioning MashPoint here, but opted to keep it out. Thanks for putting in a plug for it.

By: Stephen Hughes

Stephen Hughes — Tue, 18 Nov 2008 09:53:16 +0000

Brilliant topic, I was in a positoin a few months ago trying to figure out how to use the BDC. After much pain I have been able to work my way through it with help froma couple of sites. This topic will be a great help to all those trying to understand the BDC.

Look forward to Part 2

By: Steve Gaitten

Steve Gaitten — Tue, 18 Nov 2008 00:10:53 +0000

Randy,

Nice job on the intro to BDC, I'm looking forward to the rest of the series.

I would also recommend that anyone who is interested in the BDC should take a few minutes to learn about MashPoint from Bamboo Solutions. [http://community.bamboosolutions.com/blogs/mashpoint/default.aspx] MashPoint is a free platform from Bamboo, modeled on the BDC. MashPoint has virtually all the capabilities of MashPoint and more and is available for both MOSS and WSS.

It's also worth mentioning that Bamboo's complete gallery of over 40 SharePoint Web Parts is currently being updated so that all relevant Web Parts can be configured to display data directly from the BDC or MashPoint. The first two Bamboo products to support these data sources are the Calendar Plus Web Part and the Chart Plus Web Part. These two Web Parts are great ways to visualize a BDC or MashPoint connected data source. In the coming days, we will issue updates to Data-Viewer Web Part enabling configurable datasheet views of external data sources, and many other popular Bamboo products.

-S