Unix script ( bin\setenv.bat on Windows) is not used by the Apache Karaf Service Wrapper. To configure Apache Karaf started by the Service Wrapper, you have to tune the etc/karaf- wrapper.conf file launchctl stop org.apache.karaf.KARAF launchctl remove org.apache.karaf.KARAF In this file, you can configure the different environment variables used by Apache Karaf. The Service Wrapper installer automatically ############################################################ # # These properties are used to configure Karaf's ssh shell. # # # Via sshPort and sshHost you define the address you can login into Karaf

of operations on dedicated ObjectName that Apache Karaf Decanter 2.x - Documentation - 6 you configure via cfg file. The decanter-collector-jmx feature installs the JMX collector, and a default configuration Keystore type (default is JKS) #ssl.keystore.type=JKS # Security (SASL) # For SASL, you have to configure Java System property as explained in http://kafka.apache.org/documentation.html#security_ssl The # SQL Query to retrieve data query=select * from TABLE This configuration file allows you to configure the datasource to use and the SQL query to perform: • the datasource.name property contains the

bin/setenv Unix script (bin\setenv.bat on Windows) is not used by the Apache Karaf Service Wrapper. To configure Apache Karaf started by the Service Wrapper, you have to tune the etc/ karaf-wrapper.conf file. option to the wrapper:install command, the file is etc/karaf-yourname.conf. In this file, you can configure the different environment variables used by Apache Karaf. The Service Wrapper installer automatically ############################################################ # # These properties are used to configure Karaf's ssh shell. # # # Via sshPort and sshHost you define the address you can login into Karaf

Keystore type (default is JKS) #ssl.keystore.type=JKS # Security (SASL) # For SASL, you have to configure Java System property as explained in http://kafka.apache.org/documentation.html#security_ssl karaf@root()> translog settings, ...) for indices globally, # in this file. # # Note, that it makes more sense to configure index settings specifically for # a certain index, either when creating it or by using the index multicast discovery (enabled by default): # #discovery.zen.ping.multicast.enabled: false # # 2. Configure an initial list of master nodes in the cluster # to perform discovery when new nodes (master

not used at all, meaning the node or the cluster are not updated at all (at sync time). You can configure the sync policy (for each resource, and each cluster group) in the etc/ org.apache.karaf.cellar containers (pods) accordingly. After a Cellar node starts up, Kubernetes discovery service will configure Hazelcast with currently running Cellar nodes. Since Hazelcast follows a peer-to-peer all-shared

not used at all, meaning the node or the cluster are not updated at all (at sync time). You can configure the sync policy (for each resource, and each cluster group) in the etc/ org.apache.karaf.cellar containers (pods) accordingly. After a Cellar node starts up, Kubernetes discovery service will configure Hazelcast with currently running Cellar nodes. Since Hazelcast follows a peer-to-peer all-shared