dtjcache script

Displays or expires the contents of one or all of the Blueworx Voice Response voice segment, VoiceXML or CCXML caches. New versions of any expired contents will be fetched when an application next requests the file from the cache . Content in the process of being loaded cannot be expired until fully loaded. Optionally, it can also expire and delete from the disc one or more VoiceXML documents older than a specified age or date.

The dtjcache command runs shell script /var/dirTalk/DTBE/native/aix/dtjcache which:

Lists the contents of one or all of the Blueworx Voice Response voice segment, VoiceXML, or CCXML caches.
Expires a single VoiceXML document or CCXML document, identified by URL.
Expires one or more audio files, VoiceXML documents, or CCXML documents, older than a specified age or date.
Expires and deletes from the disc one or more VoiceXML documents, older than a specified age or date.
Expires one audio file identified by URL, or all audio files in the audio file cache.

Expiry messages from dtjcache are written to the DTJ log.n.log files under message DTJ3139. List actions do not log messages.

Audio files specified by file:// URIs may not expire immediately from the audio cache. They may be delayed until the next audio recycle time, which by default, is 30 minutes-separated. http:// files work immediately. Grammar files can be displayed in the VoiceXML cache, but expiring them may not have the desired effect, as some speech recognition servers such as the WebSphere Voice Server server caches a compiled version. If the grammar caching needs to change, ensure that you also expire the WebSphere Voice Server entry on that server.

Even if the -delete option is specified, because previously cached documents have been pre-loaded, expiring something in a cache will only have an effect on the program in memory when the internal processes try to fetch it again from the cache.Blueworx Voice Response may well have current copies loaded into memory, which will not be affected until those preloaded versions are used up. For example, on a 30-browser system, it might take 31 calls to see the change reflected. The expiry value displayed attempts to take the max-age and max-stale into account. However, applications that specify max-age and max-stale could override this. The -delete option expires the specified VoiceXML document or documents from the cache immediately and deletes deletes their cached file contents from the disc.

Expiring a file in the cache does not affect copies of the file already loaded from the cache. For example, a multi-call CCXML document will not be affected unless it uses a <goto> element, or a <createccxml> element, or anything else that starts up a new CCXML browser. VoiceXML browsers will not be updated until they are loaded, and because VoiceXML browsers can preload, it may take longer for updated files to be used by VoiceXML applications. Even expired VoiceXML files deleted from the disc can still be available in memory until a browser is used and reloads. Audio files are not updated until it is safe to do so without overwriting the resource (which could be being used by another application).