Configuring the TIBCO Openspace Date Time Format
Date and time stamps are often used in Openspace. For example, the gadget status bar sometimes shows a timestamp and you can specify a start date and end date in the Process Instances Measures gadget.
- TranslatorMessages_ll_CC.properties file. The date and time for the majority of the gadgets in Openspace is configured using this file.
- CommonMessages_ll_CC.properties file. Currently, this file is used by the Data Views gadget only.
- ll is a lowercase, two-letter ISO 639 language code. For a list of language codes, visit the following web site: http://www.loc.gov/standards/iso639-2/langhome.html.
- CC is an uppercase, two-letter ISO 3166 country code. For a list of country codes, visit the following web site: http://www.iso.org/.
- For example, the CommonMessages_ll_CC.properties file is available in C:\Program Data\amx-bpm\tibco\data\tibcohost\Admin-AMX BPM-AMX BPM Server\data_3.2.x\host\plugins\com.tibco.os.dataview_1.0.0.017\resources\dataview\locale.
- For example, the TranslatorMessages_ll_CC.properties file is available C:\ProgramData\amx-bpm\tibco\data\tibcohost\Admin-AMX BPM-AMX BPM Server\data_3.2.x\host\plugins\com.tibco.openspace.login_1.7.0.036\resources\locale.
See "Openspace Configuration Overview" in the TIBCO Openspace Customization Guide for information about the location of these files.
Both the files contain the core messages that are used by most of the gadgets across Openspace. You must configure both a TranslatorMessages_ll_CC.properties file and a CommonMessages_ll_CC.properties file for each language you want Openspace to support.
The format of both files is the same. The patterns making up the various dateTimePattern properties are made up of meta characters as defined in Google Web Toolkit. The table below shows the meta characters you can use.
| Symbol | Meaning | Presentation | Example |
|---|---|---|---|
| G | era designator | Text | AD |
| y | year | Number | 1996 |
| M | month in year | Text or Number | July (or) 07 |
| d | day in month | Number | 10 |
| h | hour in am/pm (1-12) | Number | 12 |
| H | hour in day (0-23) | Number | 0 |
| m | minute in hour | Number | 30 |
| s | second in minute | Number | 55 |
| S | fractional second | Number | 978 |
| E | day of week | Text | Tuesday |
| a | am/pm marker | Text | PM |
| k | hour in day (1-24) | Number | 24 |
| K | hour in am/pm (0-11) | Number | 0 |
| z | time zone | Text | Pacific Standard Time |
| Z | time zone (RFC 822) | Number | -0800 |
| v | time zone (generic) | Text | Pacific Time |
| ’ | escape for text | Delimiter | ’Date=’ |
| " | single quote | Literal | ’o’ ’clock’ |
The following table shows some example patterns.
| Example | Formatted Text |
|---|---|
| "yyyy.MM.dd G 'at' HH:mm:ss vvvv" | 1996.07.10 AD at 15:08:56 Pacific Time |
| "EEE, MMM d, ''yy" | Wed, July 10, '96 |
| "h:mm a" | 12:08 PM |
| "hh 'o''clock' a, zzzz" | 12 o'clock PM, Pacific Daylight Time |
| "K:mm a, vvv" | 0:00 PM, PT |
| "yyyyy.MMMMM.dd GGG hh:mm aaa" | 01996.July.10 AD 12:08 PM |
See http://www.gwtproject.org/javadoc/latest/com/google/gwt/i18n/client/DateTimeFormat.html for more information.
If a dateTimePattern1 property is not defined in the locale specific TranslatorMessages_ll_CC.properties file then the property value falls back to the property defined in the TranslatorMessages.properties file.
The common=filename property in the data views config.properties file configures the Data Views gadget to use the date time patterns that are available in the CommonMessages_ll_CC.properties file. For example, if your filename is exampleMessages_11_CC.properties then the common property must be common=example.