130 likes | 264 Views
ABM Annual Channel Partner Conference 2013. Developer Session. Topics. ABM Application Server Technology Overview Current Functionality Roadmap Existing dlls and transaction engine Custom Fields. ABM Application Server - Technology.
E N D
ABM Annual Channel Partner Conference 2013 Developer Session
Topics • ABM Application Server • Technology Overview • Current Functionality • Roadmap • Existing dlls and transaction engine • Custom Fields
ABM Application Server - Technology • DataSnap (Previously known as MIDAS) is a DCOM-based software technology that enables Rapid Application Development of multi-tier database applications • Provides the ability for client applications to invoke methods that are implemented on a Server. • DataSnapautomatically generates the necessary interface for the Client to communicate with the Server. (Proxy class generation similar to WSDL) • Statefuland Stateless service • REST (REpresentational State Transfer) of JSON objects
ABM API Design Approach • Minimise redundant information by not repeating object information in multiple places. • Offer API methods that provide a client with all the needed information in a single call. • Describe everything that seems reasonable for the expected use without going overboard • Parameterised to allow control over what information to get
ABM Application Server – Current Functionality • Basic details for • Customers • Suppliers • Products • Jobs
Platforms • Windows required to run the application server • Client applications can be written for any platform using your existing tools • Delphi Firemonkey supports development for • Windows • iOS • Mac OS • Android
Demonstration Server Instance Running Web browser demonstration Client Application Development
Roadmap Fill out all objects with Get and Put functions Transaction data available as well Transaction processing ABM core programs to migrate to application server framework
Roadmap Current focus has been on requirements for ABM Mobile Applications What do you need?
Wiki All developer resources will be moving to the new wiki Collaboration and contribution encouraged Let’s take a look…
Existing Dlls and Transaction Engine • Not going anywhere • ABMConnect.dll provides access to some library functions • To be rapidly taken over by the application server • ABMConnect.dll provides access to core ABM UI • ABMTransEng.ocx remains • Web Transaction Engine? Application server
Custom Fields • More options? • Read Only • Invisible • Lookup lists • More?
Other Integration Improvements? • Sockets? • Greater variety of parameters (static text) • More? • Multiple programs on a single socket (other than Actions menu and toolbars) • Reports? • Other?