Configure a Spring Boot Project
The Camunda Spring Boot Application created in previous step uses the default and best practice configuration, embedded in a starter.
There are several ways to customize or override the configuration. The easiest is to provide a set of parameters in the
The full list of supported configuration parameters can be found here.
Let’s create an
application.yaml file in the
src/main/resources folder with the following content:
camunda.bpm: admin-user: id: kermit password: superSecret firstName: Kermit filter: create: All tasks
This configuration will result in the following:
- Admin user “kermit” with the provided password and first name will be created.
- Default filter with the name “All tasks” will be created for Tasklist.
Build and Run
Now you can rebuild and rerun the application again. Don’t forget to call
mvn clean before calling
mvn install again.
Now when you open
http://localhost:8080/ in your browser, it does not ask you for admin user creation, but asks for login and password.
You can use “kermit/superSecret”, which we configured before, to access the Camunda web applications.
After you logged in, you can go to Tasklist and see that a filter named “All tasks” was created, though it does not contain any tasks so far.
Catch up: Get the Sources of Step-2.
You can checkout the current state from the GitHub repository.
If you have not cloned the repository yet, please execute the following command:
git clone https://github.com/camunda/camunda-get-started-spring-boot.git
To checkout the current state of the process application please execute the following command:
git checkout -f Step-2Or download as archive from here.