make it easier to view the results as the returned JSON is not beautified (another possiblity is a tool such as Postman). Important : all URLs are relative to the private Apache Unomi URL, by default: extension). MIGRATION In order to migrate the data from ElasticSearch 5 to 7, Unomi provides a migration tool that is directly integrated. In these migration steps the following is assumed: Apache Unomi 1 an example you can simply use the default values. Be careful because the first address that the tool will ask for is the target (ElasticSearch 7) cluster, not the ES 5 one. Note that it is also possible

MIGRATION STEPS In order to migrate the data from ElasticSearch 5 to 7, Unomi provides a migration tool that is directly integrated. In this migration the following is assumed: the ElasticSearch 5 cluster an example you can simply use the default values. Be careful because the first address that the tool will ask for is the target (ElasticSearch 7) cluster, not the ES 5 one. Note that it is also possible (for example Kibana or ElasticSearch monitoring indices) they will not be migrated by this migration tool. Once the migration has completed, you can start the new Unomi instance using: unomi:start You

these tests is to run them from a continuous integration server such as Jenkins, Apache Gump, Atlassian Bamboo or others. Note : the integration tests require a JDK 7 or more recent ! Apache Unomi 1

as: • The correct wiring of your Spring IoC container contexts. • Data access using JDBC or an ORM tool. This can include such things as the correctness of SQL statements, Hibernate queries, JPA entity Thus, the setup cost is incurred only once per test suite, and subsequent test execution is much faster. In this context, the term “test suite” means all tests run in the same JVM — for example, all in the scope of the same transaction as the application code. When used in conjunction with an ORM tool, be sure to avoid false positives. In addition, you may want to create your own custom, application-wide

.................................................................................. 524 A.2.9. The tool schema .......................................................................................... expressions does still require Java 5+ though) and is backed by genuine POJOs. When using AOP as a tool to configure enterprise services then XML can be a good choice (a good test is whether you consider this category because they are often created programmatically using the new operator, or by an ORM tool as a result of a database query. The @Configurable annotation marks a class as eligible for Spring-driven

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 16. Build Tool Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 17.9.5. Use a Higher-level Database Migration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 Execute Flyway Database more advanced users: • Spring Boot Applications Deployment: Cloud Deployment | OS Service • Build tool plugins: Maven | Gradle • Appendix: Application Properties | Configuration Metadata | Auto-configuration