The “AOO OnePoint Portal” is a framework for user authentication and access to all of your web-based applications.
We think you will be impressed by the speed, ease of use, power, functionality, and scalability of the portal and the applications that we deploy within it. Perhaps more importantly, we hope that we can provide you with something that fits your goals as an organization and gives you a solid return on investment.
Often the question comes: “Is this really running on an IBM Power System?” We assure you that it is – we pride ourselves on streamlined programs. Your IBM server is already a great value, and we will help you get even more out of it. Some of the other characteristics you will find in “AOO OnePoint Portal” includes:
The portal provides a single point of entry for everyone using applications deployed within its run-time environment. Login credentials can be securely validated against the IBM system profile, the OnePoint user profile, or a user-defined program. Attached to each user profile are specific permissions for the applications that they can access. Administrators, teachers, students, parents, aides, and staff all pass through the Portal, but all have access to only those programs and records that administrators allow. Web application developers will often include a separate login for each application that they develop. The portal is configured to pass session information to any program running within its run-time environment.
This program runs in any web browser, but provides a desktop-like experience. Web applications run smoothly within the main frame, giving continuity to your portal experience. Easy to access tabs to the right of the main frame show you which applications you have running and let you switch between or close applications. Above the main frame, a drop-down list of your open applications also creates ease of access to all of the applications you have running with the portal, and a menu snapshot lets you quickly return to the menu.
Navigation and Menus
The intuitive navigation system is easy to use and makes it possible to run potentially thousands of applications within the run-time environment. The navigation is hierarchical, user-defined, and can be organized into work areas, library lists, menus, sub-menus, and individual programs. Once an application, or several applications, have been launched, you can quickly toggle between them and the menu using the drop-down list, or the tabs to the right of the main frame.
Administrators have finite control over which menus and applications each user can access. Permissions can be assigned to each user or to user groups. For example, an administrator might create groups for teachers, parents, students, or office staff, set the group permissions, and then quickly assign users to those groups. Administrators also control the definitions for OnePoint applications. From the Portal Administration menu, administrators can define program messages, set custom filters, customize pop-up lists, control how applications display data, specify file attachment types and locations, manage user-defined attributes, and more.
The portal uses a centralized architecture to define and store the common data used by all of our applications. For example, a person's name, contact information, notes, attached files, and other attributes are all managed by the portal. That person might be a student, parent, guardian, administrator, aide, donor, customer, secretary, or anything else you care to define. In a school district setting you might need that person record for your grade book, class schedule, lunch program, graduation requirement tracker, discipline system, locker assignments, and the list goes on and on. Applications running within the portal reference that single person record, eliminating the need for duplicate records for each system and the confusion, problems, incongruous data, and extra work that come with that type of system. A report library can be configured to store a reference to any report generated by an application running under the portal for future access.
Through native database modernization, it is possible to implement a solution with minimum disruption using a low-risk, gradual, iterative process to ensure no loss of business continuity and to support parallel databases during the process. This iterative, gradual and non-disruptive process allows implementation without the use of surrogates, without Level ID changes (in Phase 1) or necessarily access to source code (for maximum ROI and value, you will need the source code if you want to completely modernize your application). This can be achieved with minimal risk or down time.
The final result is a modern application architecture with a clear separation between the database, the user interface and business unique application logic. This means that companies can reclaim their agility, regain their competitive advantage and respond more rapidly to changes in the business environment.
Soli Deo Gloria