A brief introduction to AppWorks, OpenText's Enterprise Application Development and Management platform.
AppWorks consists of the following parts:
The AppWorks Gateway is the server-side component of AppWorks, which connects to the OpenText EIM Suite through AppWorks Services. There is at least one service for each OpenText product. Each service exposes an AppWorks-compatible RESTful API. Developers can create their own AppWorks Service to integrate with third-party products.
Most of OpenText's mobile applications, including ECM Everywhere 10, are powered by AppWorks.
AppWorks is not an integrated Development Environment (IDE), which typically allows developers to create a user interface by dragging and dropping UI elements in a WYSIWYG environment. We encourage AppWorks App developers to use the IDE they are most familiar with, whether that is Eclipse, Visual Studio or Notepad++.
AppWorks is not a single application. It needs a server component to connect to the back-end and manage apps, and clients to run them. The apps that run inside the client are deployed and managed through the server’s administration tool.
AppWorks Apps are reliant on associated AppWorks Services that connect to a repository. AppWorks Apps can use additional functionality provided by AppWorks Components.
AppWorks Services are modules, written in Java, that connect to enterprise systems, normally the OpenText EIM Suite, although services connecting to third-party systems can be developed. Each service exposes an AppWorks compatible API to be consumed by AppWorks Apps that run inside AppWorks Clients.
Because they are HTML5 apps, AppWorks Apps are by definition cross-platform, written once and available to users on mobile devices (Android and iOS) as well as through web browsers and soon on desktop for Windows and Mac, all from a single code base.
AppWorks Apps are deployed and managed using the AppWorks Gateway and run inside customizable AppWorks Clients.
The image above shows the difference between the AppWorks Client and the AppWorks App. AppWorks Clients are native applications. AppWorks Apps run inside the AppWorks Clients.
The AppWorks Clients are managed through the administration tool of the AppWorks Gateway. AppWorks Apps are pushed out to the AppWorks Clients.
The AppWorks Client can be rebranded, with its own app name, icon and other graphics, color scheme and certificate. Within the AppWorks Gateway, Audience Management is used to push AppWorks Apps to a particular AppWorks Client, based on the name of the client. This means that not all clients display the same apps, even when they connect to the same server. Also, AppWorks Apps can be made available to certain groups of users or individually named users.
AppWorks Clients are available for web browsers, iOS (App Store) and Android (Google Play), with other mobile platforms (BlackBerry and Windows Phone), as well as the Windows and Mac OS X desktop, currently being considered.
AppWorks Clients are fully customizable (app names, icons and other graphics, color schemes, certificates).
AppWorks Apps consume RESTful APIs exposed by the AppWorks Gateway to access the entire OpenText EIM Suite.
Static offline content can be packaged within the AppWorks App, which is deployed with the app through the AppWorks Gateway. Other offline support is entirely up to the developer of the AppWorks Apps, who can use the offline capabilities of HTML5.
The AppWorks Gateway provides the single sign-on, centralized app and audience management as well as seamless app updating capabilities. AppWorks is modular and extensible, which allows developers to easily integrate with third party products and services.
You need to sign in before voting.