-
Notifications
You must be signed in to change notification settings - Fork 36
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #37 from sreelathas/work-branch-2019
Mobile Foundation Quartz Updates
- Loading branch information
Showing
1 changed file
with
21 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
--- | ||
title: Mobile Foundation Quartz Updates | ||
date: 2019-09-13 | ||
tags: | ||
- MobileFirst_Platform | ||
version: | ||
- 8.0 | ||
author: | ||
name: Smitha Tv | ||
--- | ||
|
||
|
||
Mobile Foundation runtime bundles the required libraries including a few third party libraries. Mobile Foundation uses Quartz job schedulers and includes *quartz2.2.0.jar*. | ||
|
||
Quartz contains an *update check* feature that connects to the [server](http://www.terracotta.org/), to check if there is a new version of Quartz available for download. This check runs asynchronously and does not affect the startup/initialization time of Quartz, and it fails gracefully if the connection cannot be made. If the check runs, and an update is found, it will be reported as available in Quartz’s logs. | ||
|
||
The above update check can be disabled using the flag, | ||
`org.quartz.scheduler.skipUpdateCheck = true` | ||
Liberty deployment of Mobile Foundation creates a `jvm.options` file and during deployment through Server Configuration Tool, the newly created `jvm.options` file will include this property. | ||
|
||
In the case of WebSphere Application Server (WAS) deployments, the above JNDI property needs to be added in the environment property of the Mobile Foundation application from the WAS admin console. |