November 17th, 2008 by Kyle
Tags: BlazeDS, config, config file, configuration, deployment, j2ee war, LCDS, services-confg.xml, token, tokens, war
Posted in: BlazeDS, Flex, LCDS
Kind of related to an earlier post: Deploying Multiple LCDS wars to the same servlet container
I found out that you can specify config file tokens as JVM args. This makes deploying the same war file to various deployments that have slight variations for certain parameters easier, since you can deploy the same war, but “tokenize” (and/or use some of the default tokens).
http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/lcds/help.html?content=lcarch_4.html
“You can also use custom run-time tokens in service configuration files; for example, {messaging-channel} and {my.token}. You specify values for these tokens in Java Virtual Machine (JVM) options. The server reads these JVM options to determine what values are defined for them, and replaces the tokens with the specified values. If you have a custom token for which a value cannot be found, an error is thrown. Because {server.name}, {server.port}, and {context.root} are special tokens, no errors occur when these tokens are not specified in JVM options.”
No Comments »
