Oracle ATG Web Commerce - Token Substitution in Configuration Files

Token Substitution in Configuration Files

The build and updateconfig targets are responsible for generating the JAR files that contain module configuration files. As part of this task, the targets must replace any tokens in the configuration files before packaging them into a JAR. The following table lists the tokens that are used in the configuration files along with the names of the source files and properties where the actual values reside.

Token	File	Property
`module_name`	`module-name``/build.properties`	`module.name`
`install_unit`	`buildtools/environment.properties`	`install.unit`
`module_root_parent`	`buildtools/environment.properties`	`module.root.parent`
`default_context_root`	`buildtools/common.properties`	`default.context.root`
`default_mobile_context_path`	`buildtools/common.properties`	`default.mobile.context.path`

The module_name, install_unit, and module_root_parent tokens are used by the Store.EStore module in the /atg/dynamo/service/j2ee/J2EEContainer.properties file.

The default_context_root token is used by:

The Store.EStore module in the following properties files:
The Store.Fulfillment module in the /atg/store/inventory/BackInStockTemplateEmailInfo.properties file.
The Store.EStore.Versioned module in the atg/userprofiling/ExternalProfileTools.properties file.
The Store.Mobile module in the following properties files:

The default_mobile_context_path token is used by:

The Store.EStore module in the /atg/dynamo/servlet/dafpipeline/AccessControlServlet.properties file.
The Store.Mobile module in the following properties files:

Copyright © 1997, 2013 Oracle and/or its affiliates. All rights reserved. Legal Notices