Bloomreach

Bloomreach Documentation version

This article covers a Bloomreach Experience Manager version 11. There's an updated version available that covers our most recent release.

Run the Project

Run your project to access it from your browser.

The project is configured to deploy and run all three web applications in one go, using Maven's Cargo plug-in.

Cargo is a Java EE container management tool that we use through Maven to start and deploy web applications in Tomcat. To learn more about Cargo and its use by Hippo projects refer to Run and develop with Cargo.

To run the project, issue the following command from the project root directory:

mvn -Pcargo.run -Drepo.path=storage

By default, the repository content is stored in the directory target/storage. This has the effect that when you run mvn clean, the repository content, along with all changes and additions you made during development, are erased. To avoid accidents in this area, it is a best practice to specify a different location for storing the repository, outside the target directory. This is expressed by the repo.path parameter in the command above.

You can now access the CMS UI at http://localhost:8080/cms. The following user accounts are set up by default (username / password):

  • admin / admin
  • editor / editor
  • author / author

As a developer, you will typically log in as administrator.

At http://localhost:8080/cms/console, you can log into the CMS Console. The CMS Console gives you UI access to the JCR repository used by the CMS. You can use it for debugging purposes, or as a means to manage the repository in ways not facilitated by the CMS UI.

You can also access the website at http://localhost:8080/site. As the project has only just been created, the site is still pretty empty. All you will get is a 404 response.

The Essentials setup application can be accessed at http://localhost:8080/essentials/. You will use it to add functionality and configuration to your project.

Note that any changes you write to the repository may be lost if you (or a peer developer) build a new repository. The repository's Automatic Export tool helps you preserve repository changes in your project by writing your changes back to the project's source files (the bootstrap modules). This tool is turned on by default. You can control it from in the lower left corner of the CMS or the top menu of the Console. Your VCS helps identifying changes to the project sources caused by Automatic Export.

Finally, the logs for the website and the CMS can be found at:

  • target/tomcat8x/logs/hippo-site.log
  • target/tomcat8x/logs/hippo-cms.log

Continue to add features to your project.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?