box in the Apache Unomi server. There are two ways to register rules : either by building a custom OSGi bundle plugin or using the REST API to directly send a JSON representation of the rule to be saved contains both system properties and configuration properties. These settings are then fed to the OSGi and other configuration files using placeholder that look something like this: contextserver.publicAddress=${org $MY_KARAF_HOME/etc/unomi.custom.system.properties (and create it if you haven’t yet) file: org.osgi.service.http.port.secure=9443 org.osgi.service.http.port=8181 If you change these ports, also make sure you adjust the

contains both system properties and configuration properties. These settings are then fed to the OSGi and other configuration files using placeholder that look something like this: Default values are secured. For each trusted third party server, you need to add these 3 lines : org.osgi.service.http.port.secure=9443 org.osgi.service.http.port=8181 org.apache.unomi.cluster.public.address=http://localhost:8181 following command: And the corresponding rule can be deleted using the following command: INJECT AN OSGI SERVICE IN A GROOVY SCRIPT It’s possible to use the services provided by unomi directly in the groovy

provider's ClassLoader (for full visibility in OSGi) * Spring-enriched JPA proxies are created in the application's ClassLoader (making any vendor interfaces work in OSGi) * fixed AbstractEntityManagerFactoryBean's fixed spring-core.jar's manifest to contain correct OSGi Import-Package declaration * removed superfluous DynamicImport-Package declarations from OSGi manifests * all decorator proxies are using identity SimpleMetadataReaderFactory uses ResourceLoader's ClassLoader for loading annotation classes (for OSGi compatibility) Package org.springframework.jdbc * JdbcTemplate explicitly detects and skips null

provider's ClassLoader (for full visibility in OSGi) * Spring-enriched JPA proxies are created in the application's ClassLoader (making any vendor interfaces work in OSGi) * fixed AbstractEntityManagerFactoryBean's fixed spring-core.jar's manifest to contain correct OSGi Import-Package declaration * removed superfluous DynamicImport-Package declarations from OSGi manifests * all decorator proxies are using identity SimpleMetadataReaderFactory uses ResourceLoader's ClassLoader for loading annotation classes (for OSGi compatibility) Package org.springframework.jdbc * JdbcTemplate explicitly detects and skips null

provider's ClassLoader (for full visibility in OSGi) * Spring-enriched JPA proxies are created in the application's ClassLoader (making any vendor interfaces work in OSGi) * fixed AbstractEntityManagerFactoryBean's fixed spring-core.jar's manifest to contain correct OSGi Import-Package declaration * removed superfluous DynamicImport-Package declarations from OSGi manifests * all decorator proxies are using identity SimpleMetadataReaderFactory uses ResourceLoader's ClassLoader for loading annotation classes (for OSGi compatibility) Package org.springframework.jdbc * JdbcTemplate explicitly detects and skips null

fixed spring-core.jar's manifest to contain correct OSGi Import-Package declaration * removed superfluous DynamicImport-Package declarations from OSGi manifests * all decorator proxies are using identity SimpleMetadataReaderFactory uses ResourceLoader's ClassLoader for loading annotation classes (for OSGi compatibility) Package org.springframework.jdbc * JdbcTemplate explicitly detects and skips null InstrumentationSavingAgent class anymore (for parent- last class loaders) * spring-context.jar includes optional OSGi imports for "context:annotation- config"'s autodetection purposes * Spring reference documentation

Connecting to a Neo4j database Using the embedded mode Neo4jSession Spring Data Neo4j repositories Repository example Gemfire Solr Connecting to Solr Spring Data Solr repositories Elasticsearch Connecting Using a custom layout Understanding how the Gradle plugin works Publishing artifacts to a Maven repository using Gradle Configuring Gradle to produce a pom that inherits dependency management Configuring <repository> spring-snapshots https://repo.spring.io/snapshot true repository>

Neo4j repositories ........................................................................ 111 Repository example ...................................................................................... ................................................... 233 67.9. Publishing artifacts to a Maven repository using Gradle .................................... 233 Configuring Gradle to produce a pom that <repository> spring-snapshots https://repo.spring.io/snapshot true repository>

Neo4j repositories ........................................................................ 111 Repository example ...................................................................................... ................................................... 233 67.9. Publishing artifacts to a Maven repository using Gradle .................................... 233 Configuring Gradle to produce a pom that ground. Manual installation You can download the Spring CLI distribution from the Spring software repository: • spring-boot-cli-1.5.22.RELEASE-bin.zip • spring-boot-cli-1.5.22.RELEASE-bin.tar.gz Cutting

Connecting to a Neo4j database Using the embedded mode Neo4jSession Spring Data Neo4j repositories Repository example Gemfire Solr Connecting to Solr Spring Data Solr repositories Elasticsearch Connecting Using a custom layout Understanding how the Gradle plugin works Publishing artifacts to a Maven repository using Gradle Configuring Gradle to produce a pom that inherits dependency management Configuring ground. Manual installation You can download the Spring CLI distribution from the Spring software repository: spring-boot-cli-1.5.22.RELEASE-bin.zip spring-boot-cli-1.5.22.RELEASE-bin.tar.gz Cutting edge