The publisher is not bundled with a MIM server. Before installing, you need to have a valid MIM server and a valid Java runtime environment (1.4 or later).
The publisher install file (pub2-2.0.x.zip) is made available to you upon purchase.
Copy pub2-2.0.x.zip to the $LIMHOME directory. Extract the file with:
unzip pub2-2.0.x.zip
A basic publisher directory structure will be created for you where:
pub2/ - contains basic scripts.
pub2/config - contains a sample subscriber configuration.
pub2/spool - contains the spool directory where the publisher writes its output.
pub2/tmp - Internal use for the publisher.
pub2/lib - The necessary libraries used by the publisher.
pub2/template - This contains a sample load_updates_post.sh
By default, the MIM server does not keep a track of changes. The change log must be enabled by adding the following to your $LIMHOME/.xmimrc file.
advUpdatesLogging: yes
 | See the "MIM Server xmimrc File" appendix in the MIM Data and Development Guide for more information on working with the .xmimrc file. |
Sometimes .xmimrc files are shell scripts. In this case, you must add this line instead:
echo "advUpdatesLogging: yes"
Restart the server for the new setting to take effect. With this enabled, the server will begin logging each change to the time-series data. This does not include changes made to metadata.
 | Be careful! Turning on this switch will cause the server to log each and every change made to the server. If the publisher is not consuming these files regularly, they will continue to grow until they eventually fill the remaining space on the drive. |
After the load_updates script has applied data to your server, it
should then invoke the publisher. This is done using the
load_updates_post.sh script. It is not enabled by default. To enable the
load_updates_post.sh script, copy the sample that is included with the
publisher then install to $LIMHOME. Next, you will need to modify the
$LIMHOME/.limrc file and set LUSPOST=yes.
You can double-check that load_updates_post.sh is working. You should see the publisher startup, fetch 0 records, and then exit.