Enabling modules in web application (Java)
When building your SDL Digital Experience Accelerator (DXA) sample application, you can enable different modules.
About this task
You enable modules through profiles. These are the profiles that you can currently enable in the DXA example Web application:
| Module name | Profile |
|---|---|
| 51Degrees | 51degrees-module |
| Context Expression | context-expressions-module |
| Contextual Image Delivery | cid-module |
| Google Analytics | googleanalytics-module |
| Media Manager | mediamanager-module |
| Search | search-module |
| SmartTarget | smarttarget-2013sp1-module or smarttarget-web8-module |
Procedure
To enable modules in the DXA sample application, run the following command:
-P<modules-names>
Example:
-Psearch-module,cid-module
What to do next
- If you enabled the 51Degrees module, you need to specify a Spring Profile property for it to function. See Working with 51Degrees module for Java.
- To enable Web developers to retrieve and respond to the published context expressions, Context Expressions Extension requires some artifacts deployment on the presentation server and additional configuration. See documentation for SDL Tridion 2013 SP1 (deprecated) and SDL Web 8.
- Once the Context Expression module is installed for the Java version of DXA, the device database repository will load automatically at that start of the web application. To disable the automatic loading of the device database repository, set the
dxa.tridion.2013.context.repository.load.enabledproperty tofalse. For more information, see DXA Java configuration.