Kadro Solutions Logo
Your Framework For Business Automation
 
solutions

KadroWorks

 
Kadro Data Assistant

KadroWorks
Many e-Business solutions are designed and built without regard to a solid component-based architecture and a supporting framework. The values lost in these implementations are typically performance, scalability, robustness, extendibility and maintainability. class="bodymedium">

A good component-based framework provides the reusable building blocks for developing top quality application services; the framework continually evolves and matures with each application feature that is re-factored as a generic, shareable component.

The application services are atomic; they can exist in the framework as standalone software components or combined with other application services. The framework is responsible for providing the "integration hooks" to enable the application services to share resources and information.

Our component framework, KadroWorks, is core to our custom and product solutions. It is currently not sold separately but as part of other solutions.

KadroWorks is a Java servlet framework used for building robust and scalable web applications. Below is a summary of the features and functionality available in the current release.

Base Functionality

  • Extends Sun's Java servlet API for building custom web applications.
  • Java-enabled application server independent (Allaire?s JRun, Orion Application Server, ServletExec, IBM WebSphere, ATG Dynamo, BEA WebLogic, iPlanet Application Server).
  • Supports Java?s native platform independence.
  • Enhanced database connection pooling mechanism to improve efficiency and reliability.
  • Built-in session management that includes the support for SSL, secure login and session tracking.
  • Enables dynamic publishing of HTML pages with ability to populate any portion of the HTML page at run time.
  • Built-in support for remote access to SMTP (email) servers.

Increased functionality given to web page developer

  • HTML page elements can be controlled and changed in the HTML code without knowledge of the Java servlet code.
  • HTML page error settings are controlled in the HTML code.
  • Built-in features for processing HTML forms including field validation and error handling.
  • Ability to dynamically attach JavaScript functions to HTML components. Also includes a built-in JavaScript function library.
  • Build working HTML prototypes with no Java code development eliminating the time consuming transition from static html to dynamic servlet pages.
  • Introduction of variables to allow the HTML developer to pull well-known information from the system without writing code. For instance, if you wanted to put the user's name on a page, you would simply have to add a variable reference to the user's name (e.g. ). No java code would have to be written.
  • Introduction of layouts. Layouts give the HTML developer the ability to create a standard layout that their pages will fall into. Then all of the content pages only need to contain the content. So to change the global look & feel of the site requires changes only to a single HTML file greatly reducing site maintenance costs.
  • Enhanced library of components to deal with the most common form data types (phone, SS#, Credit Card #, etc.)
  • Default navigation between forms and pages controlled through HTML.

Increased ability to configure

  • Servlets are highly configurable from standard configuration files.
  • Ease in administration: Configurations can be changed on the fly without restarting the servlet.

System monitoring

  • Built-in statistics gathering covering transactions, database connections, errors encountered, etc.
  • Built-in monitor page for reviewing base statistics.
  • Remote web-based monitoring capability.

Logging

  • Built-in server logging capabilities to provide application-level diagnostics and tracking.
  • Tracks the user generating the log
  • All logs associated with particular transaction are flagged with associated transaction id.
  • Remote logging capability (for monitoring or debugging purposes)

Servlet Development

  • Reduced time and effort to develop a dynamic page.
  • Enhanced and integrated database mapping components.
  • Integrated html form builder.
  • Integrated default behavior for form processing and error handling.

Integrated HTML Parser

  • Parser supports all HTML W3C 4.0 elements, all Netscape-specific elements, all IE-specific elements, several Kadro Solutions-only components, and many extensions to the standard set of components.
  • Future support for XML and WML.
  • In addition, the parser will support importing a file of one format, say XML, and outputting an HTML or WML file based on a set of user-defined mapping rules.

Built-in Account Management

All account management features can be customized per account type. This means that the system administrator can have a completely different policy on session expiration, password expiration, and all related password settings.
  • Integrated password encryption/decryption.
  • Supports create account, delete account, login, logout, account enable, account disable, change password, and reset password. Support for temporary accounts (e.g. accounts can expire).
  • Configurable password rules
    • Minimum length.
    • Maximum length.
    • Dictionary word checking with minimum word size.
    • Password history list requiring users to input a password different than previous N passwords.
    • Force password to be different than account name.
    • Force password to contain multiple character types (lowercase alpha, uppercase alpha, number, symbol).

Page and Component Security

In conjunction with the built-in account management, page-level and component-level security can be added directly to the template files. The framework will automatically forbid users from accessing pages based on supplied security rules. In addition, individual components on a page can be hidden based on the user accessing the page.

Automatic Error Handling

Default handling of Page Not Found, Internal Server Error and Forbidden error cases. On all Page Not Found and Internal Server Error errors, information is gathered and saved for later debugging purposes including current session data, logged-in account, exception occurred, page being accessed, etc. The user will also be automatically prompted to provide instant feedback on what they were doing when the error occurred. The user comments will be attached to the error report.