FREE SDK (SOFTWARE DEVELOPEMENT KIT)
Interprise Suite comes with free SDK, or Software Development Kit, which gives developers the ability to extend the existing functionalities of Interprise Suite by developing and integrating "plug-ins" into the application, modify the existing functionalities of the application and create entirely new applications based on the Inteprise Platform.
The Interprise Platform is a flexible software framework that provides an ideal base for independent software vendors (ISVs), developers / integrators and resellers to develop applications with extended connection and customization capabilities.
With Interprise Suite free SDK, our customers also benefit from the Interprise SDK Resource Center, where the design and architecture of the Interprise Platform are introduced, and include quickstarts and executable programs that demonstrate the capabilities of the plug-in factory. Also included in the Interprise SDK Resource Center is the Guidance Package. It aids the developer in the implementation of the best practices for the creation of Interprise Platform-compatible plug-ins through automation. As you create new solutions using the Plugin Factory recipes, the Interprise SDK Guidance Package displays the corresponding guidance that outline the requirements and the steps in running the Interprise Plug-in Factory Recipes.
- A Development Platform Where Existing Applications Can Also Be Rewritten To Run On Top Of
- Applications That Utilize The Interprise Platform Are Called “Interprise Platform-Powered Applications”
- Interprise Framework API
- Interprise Suite API
- Compliant With XML Standards - Uses XML (A General Purpose Markup Language And An Open Standard) In Transferring Data Between The Interprise Platform Layers
- N-Tier Structure - By Having Different Layers For The Application, It Would Be Easier To Upgrade Plug-In Solutions Without Breaking The Upgrade Path Or Hurting The Stable Base Code
- Designed From The Ground Up To Accommodate Web Services
- Developed Around Microsoft .NET Framework 4.0 Technology
Divided into two parts :
The Interprise Framework API contains the code that handles the back-end system functions that manage the front-end business functionalities, ensuring consistent performance between Interprise Platform - powered applications. These include tasks such as plug-in and data management, connectivity, security settings and others.
The Interprise Suite API contains the code that handles business functionality based on the modules of the Interprise Suite application. It includes thousands of business-related functions such as CRM, Inventory, Banking, Accounting and more.
INTERPRISE PLATFORM ADVANTAGES
- Promotes An Extendable Architecture Where Programs Called "Plug-Ins" Connect And Interact With The Application. These Plug-Ins Can Contain Any Functionality That The Application Needs
- Permits Additional Plug-Ins To Be Added To An Application Or Existing Plug-Ins To Be Modified Without Interfering With System-Specific Operations And Breaking The Upgrade Path
- Allows Developers To Modify And Extend Functionalities Of Inteprise Platform - Powered Applications With More Freedom Than With Any Other Application, Business Or Otherwise
INTERPRISE PLATFORM BENEFITS FOR CUSTOMERS / DEVELOPERS / RESELLERS / ISV's
- Developers, Resellers And ISVs Can Utilize The API Or The Source Code To Create New Business Solutions To Meet The Different Needs Of Their Customers. And Using The Interprise Plug-In Factory, The programmer Can Create Plug-Ins Faster And Easier
- Fiscal Year Or Calendar-Based Budgeting
- Anyone Can Have A Stake In Customizing The Interprise Platform; The Possibilities Seem Endless
INTERPRISE PLUG-IN FACTORY
Developer level customizations involve the creation and modification of plug-ins using the API or the source code. The API’s exposed elements can be used to create plug-ins that work with the application. Developers can use the source code to modify the pre-existing functionalities of the plug-ins of the application. The Interprise Resource Center, however, will focus on creating plug-ins using the API through the Interprise Plugin Factory.
When creating programs, developers usually end up setting the projects or classes they need and typing long lines of code, sometimes repetitively. Errors can seep in the programs due to wrong spelling, incomplete structures and invalid references. Intuitive development environments such as Visual Studio 2010 reduce these sources of errors a great deal yet logic errors can still persist. This is especially true in modular applications where one application can consist of a large number of interconnected programs. Developers therefore have to keep track of their relationships as well.
The creation of the Interprise Platform - powered plug-in applications requires different software layers to be constructed and interconnected. These layers are then collected as a project and compiled into a DLL which is connected to the main application as a plug-in. If done manually, the developer will have to write code that initializes the plug-in to the Interprise Platform and code that defines the function of the plug-in. The initialization code follows a pattern and could be tedious to write. For this purpose, the SDK includes the Interprise Plugin Factory, a Visual Studio 2010 guidance tool that initializes these software layers and the necessary code within them. This simplifies the developer’s task by letting them focus on the code that defines the plug-in’s custom functionality. Be reminded, however, that this does not “dumb down” the task of programming plug-ins by reducing plug-in creation as a simple point-and-click operation. Knowledge regarding how the application operates and programming essentials are still required; the time spent on typing code is nonetheless reduced. Beginners will find this tool extremely helpful and instructive, as it will give them further insight into the plug-in internals.
Different layers of the Interprise Platform were developed in order to properly present information to the end users.
- Presentation Layer
- Facade Layer
- Business Layer
- Web Service Layer
- Data Layer
The Presentation Layer is also known as the "user interface." This layer is responsible for presenting information processed by the other layers in a way that is understandable by the user. The Presentation Layer can display the processed information in a number of presentation hosts such as desktop computers, browsers and handheld devices. The best example for this is AspDotNetStorefront for Interprise Suite, an integrated web store and shopping cart solution fully integrated into Interprise Suite. Interprise Suite provides the interface for the back office processes of the company and the result reflects on the AspDotNetStoreFront web store that is displayed in a web browser.
The Facade Layer is a thin business logic that acts as the intermediary between the Presentation Layer and the Business Layer. This layer resides in the client (or the user's computer) along with the Presentation and the Business Layers and handles the data exchange between the two although it is not concerned with how the Presentation Layer presents the data. The format that this data is presented is in XML. This allows the type of user interface to be flexible while the processes beneath it operate as it usually does. The Facade Layer also routes requests and data accordingly if the connection to the database is through LAN/WAN or through the Internet (using Web services).
The Business Layer, also called the "business rule", contains the business logic that is used by the application. This layer interacts with the Facade Layer and is the only layer that can communicate with the Data Layer directly. As you can see in the representation above, the business layer resides on both the client and the server. The reason for this is to support the connection protocol where the user may connect directly through LAN or remotely through the internet via web services.
The Web Service Layer transports data to and from a central database over the internet. The format of this data is in XML which is an open standard in markup language that can be read and processed by other seemingly disparate applications. The diagram below depicts how data is passed from the client workstations or the Presentation layer to the Facade layer (business logic responsible for detecting whether the user will connect through LAN or Internet) and over the internet through the Web Service layer.
The Data Layer is also called the "database" of the application and holds persistent data used by the application. More precisely, this is an SQL Server database that contains the data used by the application. The Business Rule communicates with the Data Layer through queries and stored procedures. As seen in the image on the right, the Data Layer (or the database) is usually located within a separate database server where the user can connect to through LAN or internet.