Description
This DIM receives a product from its source and builds a BackWeb "infopak". This infopak is published onto a BackWeb server that is on the same host as PAM.
Configuration Variables
backWebServerHostThe hostname (x.y.z) of the machine on which the BackWeb the BackWeb server residesbackWebTCPPort
The port number that the BackWeb server uses for TCP service (default 81)backWebUDPPort
The port number that the BackWeb server uses for UDP service (default 370)backWebConsolePort
The backweb console port number (default 6789)backWebChannelName
The backweb channel name as set by the backweb console. (default "CDA")backWebSegrulesStart
The first rule in the block of rules allocated for PAM (default 1)backWebSegrulesEnd
The last rule in the block of rules allocated for PAM (default 10)backWebExposureGroup
The name of the exposure group to publish to.backWebTopicName
The name of the topic that this DIM publishes infopaks with.If this field is empty, the DIM will look at the "topic" attribute of the product. The "topic" attribute can be set by the "product_topic" attribute of any Juggler or PIM.
If an invalid topic is specified then anyone subscribed to the channel will receive the infopaks.
Topics match backweb segmentation rules that are prefixed with "pam_". See segmentation rules below.
Result
A BackWeb infopak, consisting of: a script file(.bis), a frame file (.bif), and any additional files.
Segmentation rules
A BackWeb channel (as of server version 2) consists of a site. However, for many applications it is desirable to serve multiple sub-channels of information from a single TCP/IP site. This has necessitated developing a subchannel concept using BackWeb segmentation rules. Below is an initial description of a subchannel as implemented in PAM (specifically for BackWeb).Each sub-channel should have a simple name. A BackWeb segrule needs to be created (using the BackWeb console) of the proper form. The form is:
Exists(<varname>) and <varname>="subscribed"
Where<varname>
is the prefixed topicName. An example subchannel segmentation rule might look like:
Exists(pam_pushtech) and pam_pushtech = "subscribed"
This segmentation rule would be used to publish products that have a topic of "pushtech"How it works
1) The DIM obtains a list of canned infopak files (except an info file) from an infopak template directory (supportdir/BackWeb). It builds a custom script file to "flash" messages one at a time. It identifies and copies files referenced from its input product. A summary file is also built from the product. These files are then copied into the DIM's working directory.2) The DIM finds out the location of its working directory (relative to the root of the PAM system) and the location of the PAM system (IP address, port number, and protocol).
3) An info file is built (using the segmentation rules it finds for the BackWeb server), and publishes this infopak onto the BackWeb server.
4) The file/garbage collection system deletes the temporary files created in the working directory. The working directory itself is not deleted.
Notes
This DIM is built to work with version 2.0 of the BackWeb server.
Revised: 7 July 1998