Run the Project
Info: Start your project to access the web applications in your browser.
The project is set up to deploy and run all three web applications simultaneously using Maven's Cargo plugin.
Info: Cargo is a Java EE container management tool used through Maven to start and deploy web applications in Tomcat. For details about Cargo and its integration with Bloomreach Content projects, see Run and develop with Cargo.
Start the Project
Run the following command from the project root directory:
mvn -Pcargo.run -Drepo.path=./storage
By default, repository content is stored in target/storage. Running mvn clean deletes this directory, which removes all repository data and changes made during development. To prevent data loss, specify a repository location outside the target directory using the repo.path parameter, as shown above.
Access the Applications
After starting the project, access the following applications:
-
CMS UI: http://localhost:8080/cms
Default user accounts (username / password):
- admin / admin
- editor / editor
- author / author
Developers typically log in as the administrator.
-
CMS Console: http://localhost:8080/cms/console
Info: The CMS Console provides UI access to the JCR repository used by the CMS. Use it for debugging or managing repository data not available through the CMS UI.
-
Website: http://localhost:8080/site
The site is empty after project creation. Accessing this URL returns a 404 response.
-
Essentials Setup Application: http://localhost:8080/essentials/
Use this application to add features and configuration to your project.
Repository Changes and Automatic Export
Repository changes may be lost if a new repository is built locally or by another developer. The Automatic Export tool helps preserve repository changes by exporting them to the project's source files (bootstrap modules). This tool is enabled by default. Control it from the lower left corner of the CMS or the top menu of the Console. Use your version control system to track changes made by Automatic Export.
Log Files
Application logs are available at:
target/tomcat9x/logs/site.logtarget/tomcat9x/logs/cms.log