The Rhino SDK configuration is stored in the config directory of the Rhino home directory.
This contains configuration files for Rhino and JVM settings.
| File | Purpose | ||
|---|---|---|---|
config_variables |
Basic Rhino configuration. The most common settings can be configured here |
||
jvm_args |
All JVM configuration arguments including Java system properties for configuring Rhino.
|
||
logging.xml |
Log keys, levels and appenders. Configuration of tracers as used by Resource Adaptors and Services is managed separately with the Rhino management interface |
||
rhino-config.xml |
Configuration of Rhino facilities such as the timer facility and monitoring statistics collection. |
||
defaults.xml |
Default settings for access control, limiters, logging, persistence and SNMP. Not used after first boot. |
||
init_*_db.sql |
Scripts for initialising the Rhino management database |
||
jetty.xml |
Configuration for the embedded Jetty web server used by the embedded REM instance. |
||
mlet.conf |
Security permissions for JMX MLets. Configure if custom access permissions for management are required. Usually this is only required in production Rhino deployments. |
||
persistence.xml |
Database configuration for persistent storage of Rhino settings, profiles and JDBC data sources. |
||
rhino.jaas |
JAAS authentication settings. Configures how Rhino authenticates users of the management API and tools. |
||
rhino-boot.policy |
Java security policy for the Rhino starter. Usually this should not be changed. |
||
rhino.policy |
Java security policy for the Rhino application server. Edit this if you are developing a service with native components or additional database drivers. In general services and resource adaptors should have security permissions set in their respective descriptor files. |
||
rmissl.jmxr-adaptor.properties |
Location of SSL keystores for JMX authentication |
||
runtime.xml |
Configuration of Symmetric Activation for production Rhino clusters. Not functional in the Rhino SDK. |
