Blueworx Voice Response for AIX Version 4.2 has improved cache control in Fix Pack 2 (fix level 220.127.116.110).
By running the dtjcache command you can:
- List the contents of one or all of the Blueworx Voice Response voice segment, VoiceXML, or CCXML caches.
- Expire a single VoiceXML document or CCXML document, identified by URL.
- Expire one voice segment identified by URL, or all Voice Segments in the Voice Segment cache.
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.
The dtjcache command runs shell script:
Output from dtjcache is written to stdout.
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.
Expiring something in a cache will only have an effect when the internal processes fetch it 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.
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. Audio files are not updated until it is safe to do so without overwriting the resource (which could be being used by another application).
Lists the file names stored in all caches (default) or a cache specified by the -cache parameter.
Lists all files in all caches (default) or a cache specified by the -cache parameter, with full details including expiry time, file size and creation time.
Expires everything in all caches (default) or in a cache specified by the -cache parameter. You will be prompted for confirmation.
Specifies the type of cache to expire or display file names for. Valid values are:
The default is all.
When used with the expire action, expires without prompting for confirmation.
When used with the expire action, reads a specified ASCII file listing the names of cached files (one per line) and expires each entry.
whitespace-separated list of cached files
When used with the expire action, expires each entry in the list.
Prints this help information.
Prints this help information.
To list all files in the voice segment cache with full details including expiry time, file size, and creation time:
dtjcache -action listDetails -cache audio
To expire everything in all caches after confirmation:
dtjcache -action expire -cache all
To expire everything in all caches without prompting for confirmation:
dtjcache -action expire -cache all -force
To read a file named file.txt, treating each line as something that should be expired in the VoiceXML cache:
dtjcache -action expire -cache vxml -batchFile file.txt
To expire a specified CCXML document (/var/dirTalk/DTBE/invoked.ccxml) in the CCXML cache:
dtjcache -action expire -cache ccxml file: ///var/dirTalk/DTBE/invoked.ccxml