Creating Temporary Files
Tell Automator to create temporary files that contain processing information about each file that goes through the workflow. These are called PGN files.
To do this, use one of these methods.
-
Start the workflow by running Automator with the -o parameter, which points to a directory where the PGN files must go. Example:
ForesightAutomator.exe - o"C:\Foresight\Systems\OpMonLoggingDir" …
-
Start the workflow with Foresight Studio with the “eyeball” toolbar button turned on so that it looks open:
In this case, the PGN files always go to the OpMonLoggingDir under Foresight’s Systems directory.
Either method causes Automator to create a PGN file for each file input into the workflow. In any case, the directory where the PGN files go must match a collect directory in OMProcessor.props
, which is in TIBCO Foresight® Operational Monitor’s root directory.
As OMProcessor puts them in the Foresight Operational Monitor database, they are deleted.
If OMProcessor fails to import them into the database, they are moved to the fail directory and an email is sent to the addresses named in OMProcessor.props.
Because these are stored as temporary files, processing does not have to wait if the database is slow or the network is down. You do not have to shut down the workflow if these resources are not available.
Importing Temporary Files into the Database
OMProcessor.jar
takes PGN files and places their information in the Foresight Operational Monitor database.
OMProcessor is a background Java application which runs continually to process messages.
It resides in its own particular root folder, where it keeps an archive of its processed messages and any/all message failures it encounters:
-
The archive folder have a time stamped folder structure with new archive files being created every hour.
-
The fail folder contains any message files which caused fundamental processing difficulties. Every day, a new file is created to log failures.
Start OMProcessor from the command line or from the OMProcessor.bat
file in Foresight Operational Monitor’s bin directory. It continues to run until stopped, perusing the collect directories specified in OMProcessor.props
, and putting any PGN files into the database.
OMProcessor Command Line
All parameters are optional, and include:
-
Root folder - Location of the root folder. If the -root parameter is not specified, then the program looks for the
OMProcessor.props
file in the current working directory, and exits if it cannot find it. -
Alerts - Override the properties file by enabling or disabling e-mail alerts.
-
0 - Do not send email alerts
-
1 – Send email alerts
-
OMProcessor Example Commands
This uses OMProcessor.bat
(which is in Foresight Operational Monitor’s bin directory). It points the processor to C:\OM\OMRoot
and turns off email alerts.
OMProcessor.bat –root C:\OM\OMRoot –alerts 0
This is the same command using OMProcessor.jar
directly:
Java -jar OMProcessor.jar –root C:\OM\OMRoot –alerts 0