 |
 |
|
Basic Technology
Yes, OpenLayer will take your Client Server application and will turn it into a true web based application. No client side engine or client install is needed. Simply access your application via HTTP or HTTPS protocol OpenLayer produces a true open user interface. It takes advantage of the mature Business Logic Server and couples it with a robust user interface server. Yes, OpenLayer unitizes standard HTTP / HTTPS protocol. The user machine does not need to connect to the server continuously. OpenLayer manages each session and will terminate and role back if necessary any transactions that were incomplete as a result of the user's machine disconnecting. There are several instances when your server session may be broken without the user being aware of it. In such situations, OpenLayer either completes or aborts the session in a graceful way, performing role-backs where needed, so that your server resources are freed-up. OpenLayer can utilize standard application driven security or integrate with enterprise level security. OpenLayer can be easily integrated with any kind of authentication and authorization mechanism. OpenLayer can call the authorization external module before requesting the transaction from the back-end server.
OpenLayer creates additional Open UI objects which, upon activation can call any combination of PRO-IV or Open Logic (Java, .Net, etc.). Transactions can be initiated by a URL including a login request to insure proper security authentication. All User Pages are automatically generated and driven by the back-end server. OpenLayer determines if there iare any changes in the UI. If there are no changes, existing pages are used. User Interface
OpenLayer transforms your existing User Interface screens to pure HTML / JS pages. OpenLayer adjusts white spaces to balance your screen contents; all date fields are automatically converted to use calendar controls, all lines and boxes are drawn as collapsible panels, all paging areas / screens are converted to sortable, adjustable grids, and mandatory fields are bold (or any other format defined in css). Overall your screens look better. OpenLayer’s architecture is designed to support all client server technologies. A configuration file contains metadata defining your applications’ technology stacks and any “creative or innovative” programming techniques used in your client user interface. OpenLayer does not require any changes in your application or core technology, your QA cycle to implement OpenLayer is very quick.
Also, after OpenLayer is adopted, your application can continue to use your standard client to access the application, since no changes have been made in the application or core.
This eliminates any risk to adding OpenLayer- thus ZERO Quality Risk.
Even after OpenLayer is adopted, your application can continue to use your standard client to access the application, due to no change in the application or core.
This eliminates the risk - and it is a ZERO Quality Risk product implementation.
OpenLayer transforms your user interface and adds some advanced controls by default. For example: if OpenLayer detects that the input field is a DATE field, it adds a Date Control to pick the date, for all paging screens, a GRID control is generated so that you can sort, resize, and reposition elements.
Tab controls are used for all pop-up windows. The parent tabs are disabled for editing, but the user can click on parent tabs (any level) and view and copy the data to the clipboard.
OpenLayer adds a layer to your communication protocol and exchanges the user interface in form of Object notations; it does not interfere with your business logic. All of your business logic will by default be honored.
Configurable UI
The User Interface can be configured and served. Configuration can be either for all users, a group of users, or a single user. System wide permission can be granted for end user configuration.
As part of configuration, fields and buttons can be hidden. These are just hidden from the user interface and not from the server. Current values of the hidden fields are retained and communicated back to the server on a required basis.
Mandatory fields can not be hidden. Also, optional fields can be converted to required fields.
When all of the fields of a given row are hidden, the row is eliminated from the user interface. This allows the screen data area to shrink so smaller screen resolutions can be used.
This feature enables you to serve a lighter version of your application without making any changes in the application code. This is especially effective when dealing with smaller browsers like mobile devices.
The user, group, and system configuration are saved as objects on the OpenLayer server and not on the client. This feature insures that users will view the same format no matter where the application is accessed.
OpenTalk
OpenTalk is an extension built upon the core infrastructure of OpenLayer. It takes advantage of the powerful architecture and infrastructure of OpenLayer and provides your application an ability to "break out of jail" and communicate with other applications simply by using HTTP post and get methods.
OpenTalk encapsulates transactions into web services which can be served to a Service Request.
You can make a request to the OpenLayer server via HTTP request and launch any transaction. OpenLayer provides the data to your applications’ un-modified function insuring complete application integrity.
No - You do not need any further extensions. OpenTalk can get the required data via HTTP Post, and populate the data in your existing screen function. In case of any error from the application server, OpenTalk returns the error back to the caller as HTTP response.
OpenAccess
OpenAccess framework is intended to provide an abstraction for scalable data retrieval from heterogeneous data sources your business logic server can handle. Thus, it serves a different purpose than other standard data-centric frameworks, such as ODBC, JDBC, which have significant focus on data updates.
The request to OpenAccess is in JSON (JavaScript Object Notation), a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language. These are universal data structures. Virtually all modern programming languages support them in one form or another. It makes sense that a data format that is interchangeable with programming languages also be based on these structures.
JSON is the Fat-Free alternative to XML. JSON is a programming language / model data interchange format. It is minimal, textual, and a subset of JavaScript. It is lightweight and very easy to parse.
|
OpenLayer – A Brand New Way To Think, A Brand To Way To Grow, A Brand New Way To Save !
|
|
|
