As more and more small businesses are deploying open platform operating systems and tools such as various blends and PHP / MySQL, we would like to share the experience of implementing Microsoft Great Plains in these mixed OS environments . If you are using Oracle and Unix, you can consider this methodology, but only a brief overview on Java and EJB nuances is described in a separate article.
1. Overview of MS Great Plains platform. The GP workstation is written in the C shell named Great Plains Dexterity. In the early 1990's, the independence of DB and OS platform was designed when it was paradigm. But when Microsoft bought Great Plains Software 7 years ago, Microsoft Dexterity was disregarded and the GP itself was exposed via .Net platform and Microsoft Visual Studio C # and VB developers, in particular via eConnect. In addition, GP is only available on the Microsoft SQL Server DB platform. To put these things in mind, Microsoft Great Plains versions 10.0 and 9.0 are considered committed to Microsoft technologies such as SQL Server, .NET, Windows, MS Office: Sharepoint, Excel.
2. Cross-platform SQL query. When doing from Microsoft SQL Server 2005 or 2000 side, we usually use Linked Server which needs to try ODBC connection to Linux World. A similar structure, if you are on Oracle, you can connect MS SQL Server
3. Web service. Using eConnect, you can open GP objects of non-Microsoft developers via XML Web services. You can use the eConnect interface directly, or you can wrap it with a custom web service interface
4. eConnect exercise. In eConnect's core, MS SQL Server encrypted stored procedure is set and it is possible to process GP master records and transactions: SOP Entry, POP Receiving, Customers, Vendors eConnect has restrictions on GP architecture Yes. One of the typical FAQs is why you can not post GP batches to eConnect. This is a limitation, but you can use Albaspectrum bulletin server to break it. eConnect initially was dedicated to e-commerce software developers to enable the GP ERP platform as back-office accounting for the e-commerce front end
Integration technology. Here too eConnect will appear. Rather, GP Integration Manager, a traditional Great Plains integration tool, has recently been redesigned on eConnect, IM performance has improved significantly. IM can read tab-compliant text files and ODBC compliant queries. When programming integration, instead of deploying a regular destination connector, you should give priority to eConnect destination connector (older connector is GP server and GP workstation is used as OLE server and GP We will verify the business logic of Great Plains directly on the screen.)
