Tolven RC1

From DOC

Contents 1 System Configuration 1.1 Plugin Framework 1.2 JBoss Location 1.3 Third-party Libraries 1.3.1 Jasper Reports 1.3.2 JSCH Library removed 1.4 Database 1.4.1 Add missing index 2 Application Configuration 2.1 Rule Refactor

System Configuration

Notes in this category apply to the Tolven system configuration, typically affecting the Tolven system administrator.

Plugin Framework

The Tolven Plugin Framework (TPF) significantly improves the configurability of Tolven while at the same time reducing the need for CVS access for routine customizations. Previous versions of Tolven allowed both a developer install and a binary install. These procedures are eliminated and replaced with binary installation and configuration procedures.

Going on to customize Tolven now uses the binary install. Source code is provided in self-contained Jars which facilitate debugging and browsing. Customizations can be seamlessly integrated with Tolven's plugins and integrated into the final form, such as the tolven.ear file) without modifying the core deployment procedures. This provides a side benefit in that both local and Tolven updates can be included in the running system without having to build or distribute a new kit.

Of course the live source code is still in CVS but it has become complex and dynamic enough that Tolven no longer provides an official CVS-based developer installation procedure. The Tolven developers, for example, only check out the plugin project they are working on, not all 100+ projects that now exist in Tolven.

JBoss Location

The Tolven prepared JBoss is now installed separately. Download tolven-jboss-config-4.2.2.GA.zip and unzip it wherever you like. If, on Windows, you unzip to c:\, then it will be located at c:\tolven-jboss-4.2.2.GA\.... It is not recommended that you install it in the tolven-config directory.

Tolven no longer supports the Start Menu entry for JBoss. The start scripts can be located in the bin/ directory of the above install. You can provide your own shortcut to these scripts.

The Tolven configuration process will deploy to this JBoss location and therefore, the application server location must be specified in tolven-config/plugins.xml (the global property called appserver.home).

<property name="appserver.home" value="your-appserver-homeDir" />

There are a number of related properties in the plugins.xml. Please follow the instructions for a new installation.

Third-party Libraries

Jasper Reports

JasperReports was upgraded from jasperreports-3.0.1 to jasperreports-3.1.4. JasperReports deprecated the use of DTD based JRXML validation and introduced XML schema based JRXML validation (see release notes for 3.0.1 at http://jasperforge.org/website/jasperreportswebsite/trunk/index.html). The previous compiler will not recognize the new schema format, but the new one recognizes both. The new compiler is installed automatically during the upgrade step.

Another important note is that we no longer embed fonts in the reports, since there is simply no real need. The example reports now refer to Helvetica fonts, and as part of the PDF rendering specification either this font or one close to it (e.g. Arial), will be used during rendering. This will also make the PDFs smaller.

JSCH Library removed

The JavaSecureChannel library has been removed from Tolven because it is no longer used by Tolven.

Database

Add missing index

The placeholderId entity should be indexed as follows: CREATE INDEX ph_index1

 ON app.placeholder_id
 USING btree
 (account_id, id_root, id_extension);

This index has been added to runtime initialization for Legacy PostgreSQL, single-schema PostgreSQL, and single-schema Oracle.

Application Configuration

Rule Refactor

Rules are now handled differently.

• Rules handle both TRIM (as usual) and CCR messages (new). Previously, CCR messages were handled by hard-coded Java rules.
• The package name in a rule file is now significant and has been changed to reflect this. As a convention, the package name is the name of the account type that it applies to (echr, ephr). Other names may be used as well. the file name is unimportant.
• Two new rule files (packages) have been created: common.drl (package common) contains rules that apply regardless of account type. sharing.drl (package sharing) contains sharing rules, regardless of account type. As a result, common and sharing rules are removed from echr.drl and ephr.drl files.
• The class of the app global variable has changed. The line should now read: global org.tolven.app.AppEvalAdaptor app;
• Previously, one rule package was loaded per account type. Now, all rules are loaded together. Therefore, you should not repeat a rule in two packages unless you intend for it to execute twice. Most rules have a built-in affinity to a particular account type because they include a condition that matches on a particular metadata item such as "echr:patient...".
• Rules are now compiled during upload instead of at runtime. A package containing a compile error will not be added to the database.
• A new table stores all versions of rule packages. Previously, rules were stored in the accountType entity.