Time zones

Setting the time zone

You can set the time zone of origin for a job with the usageTimeZone property of the processInfo bean. To properly support Daylight Savings Time, use a specific time zone ID such as US/Pacific rather than a generic offset such as GMT-0700. If you do not set the usageTimeZone property, usage data is assumed to originate in the server time zone.

For example, for data collected from a source in California you would specify the following:

<property name="usageTimeZone" value="US/Pacific"/>

For more information about the processInfo bean, see Processes and feeds.

During the Transformation step, you can also set the time zone for state and shift logs. For example, you can use the stateChangeTimeZone property of ApplyStateChanges to set the time zone for the state change records so that timestamps are properly converted to the same Greenwich Mean Time (GMT) as the usage data:

<bean class="com.cloudcruiser.batch.CCRecordTransformTasklet">
  <property name="processors">
    <list>
      <bean class="com.cloudcruiser.batch.transform.ApplyStateChanges">
        <property name="active" value="true"/>
        <property name="stateChangeTimeZone" value="GMT‐08:00"/>
        ...
      </bean>
    </list>
  </property>
</bean>

When adding a shift identifier, you can use the scheduleTimeZone property of AssignShift to set the time zone for the shift schedule records so that start times are properly converted to the same time zone as the usage data.

Time zone syntax

The syntax for time zone values is based on the Java TimeZone class.

• A generic offset can be specified as follows:
  GMT Sign Hours : Minutes
GMT Sign Hours Minutes
GMT Sign Hours
• Sign: one of: + or -
• Hours: Digit or Digit Digit
• Minutes: Digit Digit
• Digit: one of: 0 1 2 3 4 5 6 7 8 9