Buildin Features of Open-jACOB

Core Engine Rule Engine Reporting Designer DB-Layer UI


Contact: info AT openjacob DOT org
Hot deployment of Applications
 Hot deployment is VERY hot for development. The time savings you will realize when your developers can simply run their build and have the new code auto-deploy instead of build, shutdown, startup is massive.
It is possible to upload a new jACOB application at runtime. Neither the WebApplication must stop/start nor do any user have to logout and interrupting the current work.
Load Balancing (*)
 One major issue for large Internet sites is how to handle the load of the large number of visitors they receive. This is routinely encountered as a scalability problem as a site grows. The load balancing methods in a Open-jACOB Cluster (Open-jACOB can be run in a cluster too!!) manage the selection of an appropriate jACOB server in a cluster. By means of a load balancer user sessions could be uniformly distributed across all Open-jACOB nodes.

(*) only in the enterprise edition
Job Scheduling
 Jobs are scheduled to run when a given Trigger occurs. Triggers can be created with nearly any combination of the following directives:
  • at a certain time of day (to the millisecond)
  • on certain days of the week
  • on certain days of the month
  • on certain days of the year
  • not on certain days listed within a registered Calendar (such as business holidays)
  • repeated a specific number of times
  • repeated until a specific time/date
  • repeated indefinitely
  • repeated with a delay interval
Jobs are given names by their creator and can also be organized into named groups.
Any job can be run once for:
  • each user
  • each application
  • each cluster node
  • each cluster


Multiple Database Support (*)
 One Application in Open-jACOB can access multiple and different type of databases at the same time and in the same UI, without any line of code. The data source could be a persistent store like a RDBMS, an external service like a B2B exchange, or a repository like an LDAP database. The business component that relies on the Open-jACOB data access layer, uses the simpler interface exposed by the data layer for its clients. The data layer completely hides the data source implementation details from its clients. Because the interface exposed by the data layer to clients does not change when the underlying data source implementation changes, this pattern allows to adapt to different storage schemes without affecting its clients or business components.

(*) SQL-Server, Oracle, Informix, DB2 and mySQL only in the enterprise edition
Changeable User Authentification
 You can automatically add end-user authentication (sign-in) and role-based access control as a standard feature to your applications. This authentication feature is based on your own user and role data in your database, making it easy to set up and administer.
Monitor your Application
 TODO: Describe this feature