Overview

The data that are administrated by iPLAss are named as 'Entity'. Entity is equivalent to the 'Table' of RDB. Each Entity has 'Properties', which are equivalent to the columns of a 'Table' in the concepts of RDB. Applicaion’s managers can define and manage data on web browser. Besides defining data, the administrators can also configure on how the data are presented (such as which data should be visible, should it be an input field, pull-down button etc., and whether to show data in orders) to the customer. The modified changes will reflect on webpages immediately after a page refresh. In iPLAss, the objects which serve as the definition of the data and how the data behave in the application, are called as 'Metadata'. There are several more kinds of Metadata other than Entity. They can be managed from the web console.

The user can create, update, delete, and search the defined Entities. In addition, the function of version control, full text search, automatic numbering, recycle bin, LOB data storages are provided. Entity has 'Event Listeners' property as the equivalent of 'trigger' in RDB. By defining event Listeners, the user can accomplish and customize the logics that are not provided by iPLAss.

The control panel to manage data is constructed automatically. By defining the 'Role' from the security mechanisms, the developer can decide in detail about how an entity is presented to different viewers. The entity has several preset views to define how it is presented, such as Searching Overview, Detailed view, Calendar view, Tree View. Developers can create custom logic and functions if the given GUI does not meet specific requirements. In addition, We provide material-design based control panel to manage data (Material Design Components, commonly known as MDC) . MDC is designed to be responsive to the display size.

It records the history logs of the data operations. It is possible to display the history logs of the entities on the Data Management GUI of the web pages, or on the Web console for administrators.

The user can choose to encrypt the data when saving the entity data to the database. The encryption can be configured specific to each property. However, if the database provides their own encryption features, it is recommanded to use the entryption function provided by the database in priority. Please consider the iPLAss encryption mechanism as the secondary option in this case, and use it only when there is difficulty to utilize the encryption provied by the database.

iPLAss supports the embedment of developer customized logics into the automatically constructed user interfaces. In addition, when building the websites for the consumers, the developer can fully customize the page view/functions with the given MVC based frameworks. In accompany with the frameworks, other mechanics such as the content cache mechanisms and the security coding support for XSS/CSRF solutions are also supported. The code implementation can be done by Java and Groovy. The view logic implementation can be done by JSP and Groovy Template (a JSP-like template languagge based on Groovy). In the case of Groovy/Groovy Template, the changes will instantly reflect on the site without the requirements of compilation or deployments.

RESTful WebAPI that manage the defined entities can be published if needed. In addition, the Web API with implemented custom logics can be published. The security feature such as CSRF Token, OAuth2 scope managements, CORS preflight reqest control, OData compliant service endpoint (reference only) are supplied. Web API is in the form of REST or SOAP/WSDL.

The reports can be generated in form of PDF/Excel. The reports is generated by creating/inputting the templates and then inject the Entities' data into the given templates. JasperReports, Apache POI, JXLS are used as the engine of the report generator.

Built in authentication mechanism（ID/password based, RememberMe based）provided. In addition, the authentication provider interfaces are provided for additional customized authentication functions.

Role based Authorization mechanism provided. The Authorization module can allocate/manage the authority over entity, action, WebApi etc. depending on the roles and groups of the user.

OAuth2 Authorization Server/OpenID Connect Provider features are provided. For third party applications (OAuth2 Client/OpenID Connect Relying Party), it is possible to add the access control via custom WebApi（Resource）scopes and OpenID Connect based authentications.

The provided 2-step verification functions include the one-time-code via mail/SMS, and the knowledge based verifications.

The on-behalf-of login access is provided. The administrator or the preset user can log in as specific user(authority-wise) to manipulate the data.

SAML2.0’s Identity Provider, Service Provider are supplied with our system. Single sign on and services under to SAML2.0 standards are available.

The pages auto-generated via definitions are implemented with multiple languages. (The supported language includs: Japanese, English, Chinese (Simplified, traditional), Tai languages) If additonal language is required, it can be added by preparing the language-corresponded resource files. In addition, the utility function to add descriptions of custom logics in multiple languages is provided.

It is possible to have the Entity Data to support multiple languages. The Entity with multi-language enabled may display different values depending on the user languages.

Mail, SMS, Push Notificaton, and Webhook are managed by the corresponding templates. We povide the function to inject the dynamic parameters when sending the messages. Parameter injection can be accomplished by the Groovy, and can also be accomplished by complicated hard coding logics.

For the implementation of the mail messages, the port for JavaMail, Amazon SES, SendGrid are provided.

For the implementation of the SMS message, the port of Twilio is provided.

For the implementation of the push notifications, the support for Firebase Cloud Messaging is provided.

It is possible to manage the endpoint, the authentication credential, and the payload of the webhook as metadata.

The mechanism allows the logical division of the data and logics base on tenants so having multiple tenants will not interfere each other even in a single application server/DataBase server. Additional tenants can be created without interupting the server’s availability.

It is possible to set the data shared accross multiple tenants. For example, you can set the postal code master table a shared table for all tenant, so they can use the same data set.

The user can freely set the searching criteria and searching entries. For the data output in lists, the user can either save the snapshot of the lists, or the searching criteria. The saved data and the criteria can be reused later.

A preset custom search that the user can specify the aggregation methods and searching criteria, and also customize the output in the form of aggregations or graphics. The application administrator can preset the customized searchs, which then can be distributed to the end-users. Multiple aggregations/graphs can be ensembled and summarized to the dashboard.

Simple BI was designed so that the end-user can input the targeting data and the corresponding searching criteria and then freely accquire the wanted graphics and aggregation results.

Workflow can be defined uppon entity data. The workflow provides variaty of utilities processes, such as the process to grant approval to specific user, to define mail-messages, to update the entity data, and to create custom logics to Workflow. In addition, it is available to define the conditional forks, joins, and timer.

It is used to trigger specifc task in specified times intervals. The intervals can be configured to many forms such as "cron" type from Linux. Custom logics and workflow can be executed through job scheduler.

Admin Console is the tools for the developers and administrators. It provides the functions to accquire data and even the metadata; modifying and moving the data over environments; run the search queries and testing tools; accquiring the server logs and etc.

We provided the CUI tools which help with the usage of iPLAss based systems. The batch application that help with adding/deleting tenants is also provided.

The Gradle Plugin for developers are provided.

We provides the feature to collect application metrics and link them to the monitoring system. A module using Micrometer is provided in the standard as an implementation of metric collection and linkage to the monitoring system.

Amazon AppFlow to provide data integration functionality between iPLAss and external systems (SaaS and AWS services).
Provides a custom connector implementation (Zip file that can be deployed to AWS Lambda) as standard to integrate iPLAss into AppFlow as a data flow source or destination.

The login functionality for the consumer sites is provided. The adminisrator can also enable the RememberMe and 2-step verification systems.

The feature of login with social media are provided, such as login with Facebook and X (Twitter) accounts. Depending on the settings, other services corresponding to Facebook, X (Twitter), OpenID Connect can be accomplished.

The registration page and functions for new customers to sign up are provided. In addition, the functionalities like mail activation while signing up, and the user profiles update after the sign up are provided.

We provides the tool-pages to reset passwords for the users who forget about their own passwords.

iPLAss provide the feature of access management on static sites, contents (or the dynamic contents output to CMS servers.) When anonymous user trying to access the limited static contents, they are redirected to the iPLAss login pages. In the case of a logged in user, the system will check whether the user possesses the authority. There is no problem to have iPLAss deployed on a different server/ domain from the contents in need for protections. The plugin was designed to meet the standards of Apache HTTP Server, IIS, JavaEE Server, Serverless(JavaScript) module (Agent).