log4j LoggingEvent. The log4j LoggingEvent is transformed as a Map containing the log details (level, logger name, message, …). This Map is sent to the appenders. The collector allows you to remotely the line into a typed Object (Long, Integer or String) before send it to the EventDispatcher data map. IDENTITY PARSER The identity parser doesn’t actually parse the line, it just passes through. It’s custom DecanterCamelEventExtender: public interface DecanterCamelEventExtender { void extend(Map decanterData, Exchange camelExchange); } You can inject your extender using setExtender(myExtender)

log4j LoggingEvent. The log4j LoggingEvent is transformed as a Map containing the log details (level, logger name, message, …). This Map is sent to the appenders. The collector allows you to remotely public interface DecanterCamelEventExtender { void extend(Map decanterData, Exchange camelExchange); } It’s very similar to the Decanter Camel "forwards" the data (collected by the collectors) to a JMS broker. The appender sends a JMS Map message to the broker. The Map message contains the harvested data. karaf@root()> feature:install decanter-appender-jdbc

hazelcast.web.WebFilter map-name my-sessions purpose of the Cellar DOSGi is to leverage the Cellar resources (Hazelcast instances, distributed map, etc), and to be very easy to use. DOSGi is provided by installing the optional feature cellar-dosgi Topic is the distributed topic used to broadcast events. It is common for all event types. • Shared Map is the distributed collection that serves as shared resource. We use one per event type. • Event

get the log level of a specific logger. As this operation supports the ALL keyword, it returns a Map with the level of each logger. • setLevel(level, logger) to set the log level of a specific logger update(pid, properties) updates a configuration identified with pid with the provided properties map. 4.9. Artifacts repositories and URLs The main information provided by a feature is the set of OSGi list of parameters which is interpreted as a map in the order "key1 value1 key2 value2". So the command will add a PropertiesLoginModule with parameters map users -> /tmp/users to the selected realm.

• update(pid, properties) updates a configuration identified with pid with the provided properties map. CONFIGURATION 69 Artifacts repositories and URLs // TODO temp The main information provided by karaf@root()> list = [1 2 a b] 1 2 96 SCRIPTING a b You can also create a map if you put variables assignation in the array: karaf@root()> map = [Jan=1 Feb=2 Mar=3] Jan 1 Feb 2 the new directive, and call methods on the objects: karaf@root> map = (new java.util.HashMap) karaf@root> $map put 0 0 karaf@root> $map 0 0 SCRIPTING 99 EXAMPLES The following examples

purpose of the Cellar DOSGi is to leverage the Cellar resources (Hazelcast instances, distributed map, etc), and to be very easy to use. DOSGi is provided by installing the optional feature cellar-dosgi Topic The distributed topic used to broadcast events. It is common for all event types. • Shared Map The distributed collection that serves as shared resource. We use one per event type. • Event Handler retrieved. The following code snippet shows what happens when a command is sent for execution: public Map execute(Command command) throws Exception { if (command == null) { throw new Exception("Command