In a JAMS HA (Highly Available) configuration, it is helpful to keep log files in a central location. JAMS can keep log files on a local disk during the Job Execution, and move the log file to a common, centralized location upon the Job completion. The History view and Monitor view will point to the central location when the Job completes.
Before You Begin
The JAMS Scheduler Service will need access to this remote/central location. It is recommended to have this service running under the same domain account on both the primary and secondary JAMS Servers. For more information, see Change the Account Running JAMS.
Storing Log Files in a Central Location
- Click Configuration from the Shortcuts menu.
- Select the System tab.
- In the Common Log Location field, set the value for a common path that both the primary and secondary JAMS Servers can access.
Storing Log Files in a Sub-Directory in the Central Location
You can use JAMS Folder properties to move log files to a subdirectory within the common log location. Because JAMS folders inherit the master common log location from the Configuration menu, specify the sub-directory only in the Job properties.
For example, to send all log files from the JAMS Accounting Folder to the location below, set the Log Location to "AccountingSubDirectory".
- Ensure the sub-directory folder exists in both of the locations the specified in Default Log Location (primary and secondary JAMS Server) and Common Log Location fields.
- Click Definitions from the Shortcuts menu.
- Right-click the folder and select Properties.
- Click the Properties tab.
- In the Log Location field, enter the sub-directory folder, such as AccountingSubDirectory.
- Click Save and Close.
Can the common log location have a "Space" ?
Yes, the common log location can have a space in the path.
Why are the Folders not created by jams when a new target is defined where they should end up?
Hello Michael, that feature has not been added to JAMS currently. If this is something you'd like to see in the future, please submit a formal enhancement request https://support.jamsscheduler.com/hc/en-us/requests/new?ticket_form_id=360000558451.
Could we change the common log location in a HA environment without restarting any of the JAMS services? Or do we need maintenance downtime to update common log location?
In JAMS v7 you can change the common log location without restarting any JAMS services. In V6 the JAMS Scheduler restart is required, but will not impact any jobs or create any down time.
Thanks. We are on v7, so I will be updating the common log without restarting any JAMS services. Another question, once the common log has been updated, is there any issue retrieving older logs if I do not move those old logs to the new location?
No there should not be. The original history record was created with the old location, and as long as the old location and file exists, you should have no issues viewing the old log after the location has been changed.
When updating the common log locations in HA for v7.3.381, do you suggest to update the Active first then followed by Passive host? Or the sequence doesn't really matter?
Hello Doreen, use the active scheduler. Both schedulers use the same database to look at and write to the information, but you want to ensure the database is updated properly, so use the active scheduler.