blob: 19c54dbafd38bfeb514baf1fc6350adbfecad294 [file] [log] [blame]
PSIS\u001B[0m
${project.name}
${project.description}
Maven URL:
\u001B[33mmvn:${project.groupId}/${project.artifactId}/${project.version}\u001B[0m
\u001B[1mDESCRIPTION\u001B[0m
The config mbean management bundle exposes a Config MBean that can used with any JMX client (for instance JConsole).
The config MBean allows quite the same actions that can be performed using config:* commands:
\u001B[36mlist()\u001B[0m
\u001B[36mcreate(pid)\u001B[0m
\u001B[36mdelete(pid)\u001B[0m
\u001B[36mrproplist(pid)\u001B[0m
\u001B[36mrpropdel(pid,key,bypassStorage)\u001B[0m
\u001B[36mrpropappend(pid,key,value,bypassStorage)\u001B[0m
\u001B[36mrpropset(pid,key,value,bypassStorage)\u001B[0m
Just as with the config:* commands, the Config MBean is able to flush changes into the etc files.
\u001B[1mSEE ALSO\u001B[0m
\u001B[36mDiagnostic\u001B[0m and \u001B[36mRemote Management via JMX\u001B[0m for the Karaf User Guide.