This is an old revision of the document!


Configure the Stages Server

Local Message Customization

The messages shown on the Stages Graphical User Interface (GUI) can be customized to the terminology used within an organization. This also applies to the textual representations for the configured news application categories.

Each message possesses a standard definition which can be overwritten by local definitions. These local messages can be configured in the file <font inherit/Courier New,Courier,monospace;;inherit;;inherit><PKITHOME>/WEB-INF/classes/ LocalPKit.properties</font> and its localized versions (e.g. <font inherit/Courier New,Courier,monospace;;inherit;;inherit><PKITHOME>/WEB-INF/classes/ LocalPKit_de.properties</font>). At system startup, your messages will be automatically merged into the message pool of Stages.

The format of the message files conforms to the Java property files standard (“name = value”). Detailed information concerning the definition of messages can be found in the Stages Metamodeling Guide document.

Use the standard messages files <font inherit/Courier New,Courier,monospace;;inherit;;inherit><PKITHOME>/WEB-INF/classes/PKit.properties</font> and <font inherit/Courier New,Courier,monospace;;inherit;;inherit><PKITHOME>/WEB-INF/classes/PKit_de.properties</font>to lookup the keys of the respective messages.

Note: Do not change the <font inherit/Courier New,Courier,monospace;;inherit;;inherit><PKITHOME>/WEB-INF/classes/PKit.properties</font> files themselves, because upgrades would overwrite the changes.