viernes, 25 de mayo de 2012 20:44
My team is in the process of migrating/transitioning/rewriting applications written in Oracle Forms and PL/SQL to InfoPath, T-SQL and Visual Studio C#. We are all quite novice at this since we are are proficient Oracle programmers, but management has decided to go the Microsoft Sharepoint way. We have a whole lot of Oracle forms (custom-built applications) and reports (custom-built applications) that need to be rewritten in a mere four months. I am not asking for vendors/contractors to assist us, but I am soliciting advice as to what experienced Microsoft developers think is the best approach. In addition, I would really like a easy to follow, step by step, set of instructions as to how to use InfoPatch 2010 to create a data entry and query form that utilizes SQL Server tables. I have looked several places and am not having any luck. Our mandate is to have everything in a Sharepoint 2010 environment by 30 September 2012, I know, stop laughing, so really good advice in the very short term would be most helpful. For now, we cannot advance to Sharepoint 2012, etc., so that is not an option either.
So bottom line: Need to develop in Sharepoint 2010 environment against existing SQL Server tables with data moved from an Oracle database. Got very short suspense. Got lots of customized data entry forms and reports, based upon SQL Server tables, to create. Got 4 Oracle programmers struggling to learn Microsoft. Constructive advice only please.
Todas las respuestas
domingo, 27 de mayo de 2012 14:14
SharePoint is designed to use Business Connectivity Services when talking to external data sources. Making use this technology will bring you many benefits (Business Connectivity Services Benefits).
Please take a look at these articles:
- Business Connectivity Services in SharePoint Server 2010
- Using Business Connectivity Services in SharePoint 2010
- External Content Type in SharePoint Designer – SQL Server
- Creating BCS Applications
Moreover you may pull the data from Oracle database Oracle external content type
You may customize the forms. They can be modified by using InfoPath 2010 allowing you to provide validation, conditional formatting, calculations on fields and many other operations Modifying external list forms with infopath 2010
DmitryLightning Tools Check out our SharePoint tools and web parts | Lightning Tools Blog
- Marcado como respuesta Glenn Sn martes, 29 de mayo de 2012 15:00
domingo, 27 de mayo de 2012 16:22
Data Entry Forms:
BCS + InfoPath 2010
You could migrated all the reports to SQL Server Reporting Services (SSRS). In an integrated mode, all reports can reside in SharePoint 2010.
domingo, 27 de mayo de 2012 17:10
I don’t think that BCS is required here. I suppose data from oracle has to be migrated in SharePoint lists so this work has to be done by some custom utility. Or may be excel import and export can be used to move the data from oracle to SharePoint. As I understand once SharePoint application is live, Oracle forms application will be scrapped so there is no benefit of keep the data in oracle and use the same via BCS.
Regarding the forms and report you are correct. for forms infopath tool will be used and for report better to use the SQL reporting services.
domingo, 27 de mayo de 2012 22:57
If I understand correctly, I don't think we are looking at migrating Oracle data to SharePoint since SP cannot be an RDBMS repository. The data will have either reside in Oracle or will have to be migrated to SQL Server. We want to use SP UI to interact with database i.e. Add/Update/View leveraging External Content Type or BCS. Depending on whether we want to have the service layer outside SP or within SP, BCS would come into play. Based on the complexity of the forms, InfoPath or custom SP pages can be used for UI. Another factor is whether we will use SP UI to only interact with data in Oracle or have replica/related information in SP List while using BCS.
lunes, 28 de mayo de 2012 8:28
Correct SP can’t be a RDBMS repository however data was in RDBMS because till now some legacy application were being used to manipulate this data. Since now new SP UI layer will be used instead of legacy application so keeping the data in Oracle will not add any value. Better we should move this data from Oracle to SharePoint List. If some other legacy system will still use this data then it wouldn’t be possible to migrate then we have to use the BCS only.
lunes, 28 de mayo de 2012 9:32
It seems you're getting pretty close to having an approach, my thought on the subject:
- SharePoint lists are no replacement for a relational database (lists are missing stuff like transactility, advanced relations etc). I don't know about the complexity of your data, but my guess is that you want keep the data in Oracle or migrate it to SQL Server, but not migrate it to lists. Migrating it to SQL Server has the advantage that it will make it easier to interact with using SharePoint technologies that were mentioned in this thread, such as SSRS and BCS.
- If you're using BCS ECTs and external lists, add/update/delete/viewing/searching data will be really easy. I guess this is the approach recommended by Dimitry, and since you're pressed for time, this sounds like a really good plan.
- Indeed, InfoPath pages will be the premier choice for forms, if they can't handle the complexity, you can always switch to using SharePoint web parts or application pages, or even SSRS reports. My advice would be to be pragmatic about this, don't say now: we'll build everything using InfoPath.
- If you're replicating data to SharePoint lists, forget about BCS, but use BizTalk (and its SharePoint adapter) instead. However, to me, this sounds like a bad approach that is error prone and hard to manage.
lunes, 28 de mayo de 2012 11:02Lovely reply Margriet.
lunes, 28 de mayo de 2012 18:44Agree, moreover setting up BizTalk just for this requirement may not be worth it.
lunes, 28 de mayo de 2012 20:34
I only worry, is it ok to keep the data in Oracle or SQL server and manipulate the same in info path performance wise?