The methods in package Ax.ext.cache are intended to load caches programmatically in order to speed up operations.

1 Cache methods

1.1 Ax.ext.cache.loadDatabase

Loads the cache containing the database metadata

Ax.ext.cache.loadTable('database_code', 'table_name')

1.2 Ax.ext.cache.loadTable

Loads the cache containing table metadata

Ax.ext.cache.loadTable('database_code', 'table_name')

1.3 Ax.ext.cache.loadObject

Load the caches involved with the execution of an object.

Ax.ext.cache.loadObject('database_code', 'jrep_code')

1.4 Ax.ext.cache.loadMenu

Loads the caches involded with the loading of application menus.

Ax.ext.cache.loadMenu('database_code', 'user_code')

1.5 Ax.ext.cache.loadRestApiContext

Loads bean caches associated with the programmable REST webservice APIs


2 Configuring server warm Up

During a server re-start lifecycle, you may want to preload some caches to provide fast feedback to application access. You can use previous cache commands in the server initialization script to configure cache loading according application needs.

The configuration database used by the Axional Studio servers allows defining one or more scripts to be executed on service boot phase. You should use the menu option "Initial scripts" in the "Application server" section:

We should add an entry using the transactional form with including an JS script definition like the following one:

    Ax.ext.cache.loadDatabase( 'wic_acme'                     );
    Ax.ext.cache.loadTable   ( 'wic_acme', 'wic_jdic_coldata' );
    Ax.ext.cache.loadTable   ( 'wic_acme', 'wic_jdic_coldata' );
    Ax.ext.cache.loadObject  ( 'wic_acme', 'wic_jrep_object'  );

More info on Axional Studio configuration and administration options can be found here.