Job Scheduler

Replacements with ${paramName} don't work in JobSchedulerManagedExecutableJob if the job is run outside the Managed Jobs environment

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Improvement
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 1.3.1
Fix Version/s: 1.3.2
Component/s: Managed Jobs

Description:

Hide

If ${paramName} replacements are configured for JobSchedulerManagedExecutableJob in the XML configuration, the Job Scheduler will try to replace these with environment variables already on startup.
As the configured parameters propably don't exist as environment variables, {paramName} will be replaced by whitespace, leaving nothig for JobSchedulerManagedExecutableJob to replace.
(The {paramName} parameters work in ManagedJobs because they are read from the database at runtime)

Show
If ${paramName} replacements are configured for JobSchedulerManagedExecutableJob in the XML configuration, the Job Scheduler will try to replace these with environment variables already on startup. As the configured parameters propably don't exist as environment variables, {paramName} will be replaced by whitespace, leaving nothig for JobSchedulerManagedExecutableJob to replace. (The {paramName} parameters work in ManagedJobs because they are read from the database at runtime)

Activity

Ascending order - Click to sort in descending order

There are no comments yet on this issue.

People

Assignee:

Andreas Liebert

Reporter:

Andreas Liebert
Votes:

0

Watchers:

0

Dates

Created:

25 July 2007 16:00

Updated:

23 August 2007 10:39

Resolved:

25 July 2007 16:02

Time Tracking

Estimated:

30m

Remaining:

0m

Logged:

30m