Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 3 > Batch XML Reference > Context variables

Context variables

Table of contents
No headers

You can reference system and job properties from within a job as context variables , allowing you to do things like specify a file path based on the system’s usage directory or compare a date against the selection date against which the job was run.

The following table shows the syntax used to reference Cloud Cruiser context variables. Many of these variables reference directories defined in Directory structure:




System installation directory


Name of the current job


Name of the current process


Select date in yyyyMMdd format


Day of the month of the select date, as two digits


Month of the select date, as two digits


Year of the select date, as four digits


Beginning of the select date, in milliseconds, since the beginning of the Unix epoch.

For more information, see Unix time.


End of the select date, in milliseconds, since the beginning of the Unix epoch.


Time zone of the Cloud Cruiser server


Default location for job files


Root directory for all batch logs


Root directory for all processing


Process specific processing directory


Directory for sample jobs


Default location for scripts to execute as job step


Directory for email templates


Default location for usage data not in CC Record file format

In this example, the environment variable ${env.baseDir} is part of a file resource specification.

<bean id="sampleCSVReader" class="com.cloudcruiser.batch.collect.SmartFlatFileCollector">
  <property name="resource" value="file:${env.baseDir}/samples/sample.csv.txt" />
  <property name="feedConfig" ref="sampleCSVFeed"/>
Last modified


This page has no custom tags.


This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP