Configuration and Systems Information
Important Files and Directories
These files and directories are on the back-end Foresight Operational Monitor server. Although they might be displayed on the portal server also, they are not used there except perhaps for the SQL files.
File or Directory |
Default Location |
Purpose |
---|---|---|
*.sql |
\SqlServerScripts and \OracleScripts directories under installation .zip file. |
Creates and sets up the Foresight Operational Monitor database. Please see the readme.txt file provided with the scripts for instructions. |
|
OperationalMonitor\version \java directory |
Program that imports temporary (PGN) files into the Foresight Operational Monitor database. |
|
OperationalMonitor\version \bin directory |
Runs OMProcessor.jar, which picks up PGN files and puts their contents in the Foresight Operational Monitor database. See OMProcessor Command Line. |
|
Under the root directory |
Properties file for OMProcessor. It must be pre-set to appropriate values during installation. See Properties File. |
Temporary files (“PGN files”) |
Specified by Automator’s -o parameter |
These are files waiting for OMProcessor to pick them up and put them in the Foresight Operational Monitor database. Default location is OpMonLoggingDir under Foresight’s Systems directory. See Putting Tracking Informationinto the Input Files. |
root directory |
OperationalMonitor\version |
Holds OMProcessor.props, log files, archived data, and the fail folder. You can specify it with the OMProcessor command-line parameter -root. |
arch directory |
Under the root directory |
Holds emergency troubleshooting files for use by TIBCO Foresight staff. |
fail directory |
Under the root directory |
Holds PGN files that OMProcessor was not able to put into the database. You must get an email alert and must call TIBCO Foresight support immediately. It might be necessary to shut down OMProcessor multiple times if files start accumulating in the fail directory. |
|
ForesightAutomator\bin directory |
Inserts a job ID into a validation DTL file. Necessary for Foresight Operational Monitor, Transaction Insight, and Foresight® Archive and Retrieval System to link to one another. Always run your DTL files through this before importing into Transaction Insight or Foresight Archive and Retrieval System. For an example of how to use this program, see the environment InboundOM workflow. Its FileIDInsert component runs this program. |
|
ForesightAutomator\bin directory |
When run with the -o command-line option, creates PGN files. |