Today’s challenges for the enterprise is to keep its collaborators and partners up-to-date, being able to deploy solutions easily and integrated under a single umbrella, making the business to evolve to its full potential. riverPortals™ is here to solve that!
riverPortals™ build from ground zero as a Rich Internet Application (RIA), based on the world’s famous ZK® Framework, is a JAVA based application that combines a full and strong MVC pattern.
Listed in a ZK® website as a must-look application, just go to http://zkoss.org and search for riverPortals™ to learn a bit more about what this leading organization publishes about our solution.
Download PDF brochure here.
riverPortals™ comes in two flavors, Enterprise Edition (EE) and Community Edition (CE), this list of features will describe which feature to which version belongs to.
Six main features describe riverPortals™ best:
- Collaboration / Intranet / RIA
- Web Content Management System (WCMS)
- Knowledge Management System (KMS)
- Document Publishing System (DPS)
- POJO Based Application Container
- Customizable look and feel to match corporate policies.
- Domain management. Each domain is independent from context, and multiple domains can be created on a single installation.
- Full i18, localizable to match regional deployments.
- Extensive use of riverLets / portlets-like mashups that aggregate JAVA MVC, AJAX, HTML, ZK™, JSF, JSP and more.
- Ability to create HTML content mashups, providing a WCMS feature, with rich text editors for creating and editing.
- Allows creating pages from within the portal with active zones, from which riverLets can be customized to present a dashboard-like view, all movable via drag-n-drop UI components.
- Creation and customization of user menus, bound to user security profiles.
- Security management like traditional portal system does, based on users and groups, but being able to extend to LDAP, Kerberos, XML, DB Custom or any other, by extending the Portal’s API.
- CMS-Like help system, i18 localizable.
- Domain Themes management. Allows creating one or more themes per domain. Each theme containing its own set of colors and images.
- File server explorer, tightly integrated in the Portal, with a file visor based upon file’s MIME type. The explorer can be extended to incorporate any visor possible by implementing the classes for this in the riverPortals™ API. [ EE Only ]
- License management for every deployed component within the portal.
- Governance persistence achieved via H2 (default) or Oracle.
- Document Publishing System (DPS). Allowing the transformation of documents (MS-Office or Open Office) to PDF or HTML renditions. This feature is part of the File explorer characteristic of riverPortals™ EE, enriching the WCMS capabilities to not only content created manually on the portal.
- Complex Web applications, deployed via POJO based components, following riverPortals™ API.
- Data Access Definitions per domain, targeting any enabled database via riverDAO™ API. So far we provide access for Oracle, MySQL & PostgeSQL. These Data Access Objects (DAO) can be used by any UI-POJO application deployed on riverPortals™.
- Properties management system. riverPortals™ as well as other River Software Technology applications rely on property files, that can be easily managed via an intuitive user interface. Custom set of property files can be created to hold important configuration information for any third party component running under the context of riverPortals™ or within the same JVM via riverSDK™ API.
- User Messages Management System, which allows creating and administering messages that are presented to the end user via the UI interface or via log files. All i18 localizable, with the ability to use placeholders for computed information.
- File System Monitor (FSM). Each domain can contain a copy of riverFSM™, which allows to create components based on EDA over the file system for most common events. This allows extending functionality to achieve other type of user experience. riverFSM™ plays an important role for the DPS since a listener is attached to a file-system-folder in order to allow transformation of documents into other renditions. Also plays an important role in Nilus™ SOA platform.
