Excerpt from Todd’s Blog
What would you say if I told you that you could create a MOSS BDC Application
Definition without writing a single line of code? How about if the process took
less than 20 clicks of your mouse?You’d probably say, I’ve seen that crazy Application Definition XML file and I
think you are pulling my leg. You might recall seeing the contents of the nasty
XML file during a demo at a recent SharePoint conference and think to yourself, there’s
no way, this is too good to be true.Well, as you can probably guess by now, this is possible with the help of an application
I created called the MOSS BDC MetaData Manager. The application allows you to
point and click your way to BDC euphoria (if there is such a thing), and requires
no knowledge of C#, VB.NET or XML. If you can use a computer then you can use
this tool. Seeing that you are using a computer and found your way to this web
page, you already qualify!
Source: Todd
Baginski’s SharePoint 2003 and MOSS 2007 Blog : MOSS BDC MetaData Manager
Random Posts
Loading…
Rickey,I must say i am really impressed with the BDC metadata manager and i m not just saying it, i really think its a great feature! I am also excited about it because it is something i am planning to use in our next project! But i have some confusion.let me give you some background first.We have built a web application that integrates with the Active Directory to import user’s data in its SQL server database when he hits the application. The application is being used by a large enterprise containing around 25 domains. Now we are going rebuild the application on MOSS (Microsoft Office SharePoint Server) 2007 platform. This time we need a much scalable solution to the identity management problem because it would involve synchronizing users data with some other systems already running on the network.We have two options for synchronizing identity data:1. Using MIIS (Microsoft Identity and Integration Server 2003)2. Using "Business Data Catalog" in MOSS 2007According to what i understand, BDC also allows us to address the same issue by synchronizing the identity data from heterogeneous data sources including AD, DBMS, SAP, text based files etc. The solution will be used by more than 200K users in the enterprise, so performance of the server is going to be a huge issue. I am really not sure about depending on the BDC feature since I believe there should a a very good reason Microsoft has built this feature separately in a server class product MIIS. I am looking for some comparative data on both so that I can make a better decision. Do you really think BDC MetaData Manager can handle synchronization of 200K+ user accounts on a scheduled basis, and also involve 3rd part systems exposing identity data?Any help in this regards will be highly appreciated.Thanks!Akhlaq Khan.