Cloud Cruiser became HPE Consumption Analytics on Nov. 1, 2018. You'll still see the old name in places while we update this site.

 

 

Consumption Analytics Documentation
Home > Documentation for older versions > Cloud Cruiser 4 > Collecting, transforming, and publishing > ETL workbooks > System parameters

System parameters

Table of contents
No headers

You can reference system and workbook properties from within either a collection or a flow as system parameters. This enables 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.

You can also create your own workbook parameters to pass values to a collection or flow at run time. For more information, see ETL workbooks.

The following table lists all system parameters using the syntax with which you reference them from a flow or batch job. Many of these parameters reference directories explained in Directory structure:
 

Variable

Description

${env.baseDir}

System installation directory

${env.jobName}

Name of the current job. This might be a collection or flow from a workbook, a legacy batch job, an internal job, or a report job.

${env.processName}

Name of the current process. In the case of a collection or flow, this is the workbook name.

${env.selectDate}

Select date in yyyyMMdd format

${env.selectDay}

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

${env.selectMonth}

Month of the select date, as two digits

${env.selectYear}

Year of the select date, as four digits

${env.selectDateStartMillis}

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

For more information, see Unix time.

${env.selectDateEndMillis}

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

${env.selectZone}

Time zone of the HPE Consumption Analytics Portal server

${env.jobsDir}

Directory for job files

${env.logsDir}

Root directory for all batch logs

${env.processingDir}

Root directory for all processing. Each process creates a child directory here.

${env.processDir}

Directory for the current process

${env.samplesDir}

Directory for sample jobs

${env.scriptsDir}

Default location for scripts to execute as job step

${env.templateDir}

Directory for email templates

${env.usageDir}

Default location for usage data not in CC Record file format

In this example, the system parameter ${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"/>
</bean>
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
    Powered by MindTouch ®