# File: owb/bin/admin/Runtime.properties # # This file contains Control Center property values. The properties defined in this file # override any property values stored in the Control Center repository and is read once # during Control Center service startup. # # The Control Center service must be restarted for any changes to this file to become # active. # # This file provides a default for all Control Center repositories. For defaults on a per # repository basis then create a new file suffixed with the repository name in upper case. # e.g. Runtime_MYREPOS.properties. # # This file should be under strict operating system access control with update privilege # by the DBA only and read access by the user running the Control Center service # (normally the user running the Oracle service). # # Remember that the backward slash character '\' is used as an escape character so '\\' # is the equivalent to '\'. # # 1. External Activity Security - Constraints # ~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ # # The behaviour of the following operators can be restricted: Shell (External Process), # SQLPlus, FTP, OMBPlus. # # This is required because, by default, the Control Center service is executed using the # same security context as the Oracle service. # # The following properties can be use to control the operator behaviour: # # property.RuntimePlatform.0.NativeExecution.FTP.security_constraint # property.RuntimePlatform.0.NativeExecution.Shell.security_constraint # property.RuntimePlatform.0.NativeExecution.SQLPlus.security_constraint # property.RuntimePlatform.0.NativeExecution.OMBPlus.security_constraint # # With the following values: # # NATIVE_JAVA # SCHEDULER # DISABLED # # Where NATIVE_JAVA uses the Java 'Runtime.exec' interface (Default), SCHEDULER uses a # DBMS Scheduler external job submitted by the Control Center repository owner which is # executed by the default operating system user configured by the DBA. DISABLED prevents # execution via these operators. # # Note that this option does not effect the users ability to schedule jobs through OWB, # only those executions which would have been performed through native Java. # # The Java Activity Operator creates an Operating System process to instantiate Java # Classes using the java executable. By default the java executable is taken from the # Control Center Service path. However the following property can be defined to set # which executable or script is used # # property.RuntimePlatform.0.NativeExecution.JavaOSProcess.executable # # # 2. External Activity Security - Proxy Command # ~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ # # This additional feature is provided to force the execution of the constrained operators # through a proxy command. This could be used to prevent execution of unauthorized # commands or to change the security context at the operating system level. # # The following properties can be used to pre-pend a command and parameter_list # (optional) to the user specified command and parameter_list: # # property.RuntimePlatform.0.NativeExecution.FTP.proxy_command # property.RuntimePlatform.0.NativeExecution.FTP.proxy_parameter_list # property.RuntimePlatform.0.NativeExecution.Shell.proxy_command # property.RuntimePlatform.0.NativeExecution.Shell.proxy_parameter_list # property.RuntimePlatform.0.NativeExecution.SQLPlus.proxy_command # property.RuntimePlatform.0.NativeExecution.SQLPlus.proxy_parameter_list # property.RuntimePlatform.0.NativeExecution.OMBPlus.proxy_command # property.RuntimePlatform.0.NativeExecution.OMBPlus.proxy_parameter_list # # For example: # # property.RuntimePlatform.0.NativeExecution.SQLPlus.proxy_command = # c\:\\windows\\system32\\cmd.exe # property.RuntimePlatform.0.NativeExecution.SQLPlus.proxy_parameter_list = # ?/c?c\\:\\\\bin\\\\exec.bat? # # Note: For proxy_parameter_list, a single backslash '\' must be entered as a sequence of # four backslashes '\\\\' as both the parameter_list decoder and the properties file both # use backslash as an escape character. # # 3. Version Checking Management # ~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~ # # The following boolean property (true | false) controls whether the version of the # Control Center service is validated against the Control Center repository: # # property.RuntimePlatform.0.skip_version_check # # 4. Connection Pooling # ~~ ~~~~~~~~~~~~~~~~~~ # # These properties control the use of the Control Center connection pool. The pool # can improve performance in an environment where connections to the database are # being made frequently. # # The "connection.pooling" property turns the pooling on or off (on | off). e.g. # # connection.pooling=on # # The "connection.max_pool_size" property controls the maximum number of open connections # in the pool. The value -1 is treated as unlimited and 0 is equivalent to turning the # pooling off. e.g. # # connection.max_pool_size=50 # # # The "connection.max_reallocations" property control the number of times that the # connection is reallocated from the pool before being closed. The value -1 is # treated as unlimited and 0 is equivalent to turning the pooling off. e.g. # # connection.max_reallocations=-1 # # 5. Garbage Collection # ~~ ~~~~~~~~~~~~~~~~~~ # # The following properties allow for the turning the explicit garbage collection. # This is useful in a multi-CPU system where the implicit garbage collector my not # be called efficiently. # # The "garbage_collect.interval" property sets the number of jobs that will be run # before the explicit garbage collector will be run. A value of zero or less turns # the feature off. e.g. # # garbage_collect.interval=100 # # The "garbage_collect.on_idle" property controls whether explicit garbage collection # is called when the Control Center is idle (i.e. has no active jobs). The valid # values are 'true' or 'false'. e.g. # # garbage_collect.on_idle=true # # The "garbage_collect.limit" property configures the explicit garbage collector to # be called when the used memory percentage rises above the specified limit. A value # of zero or less turns this feature off. A high value is recommended as a Java VM # will tend to optimize its memory usage. e.g. # # garbage_collect.limit=90 # # 6. Connection Timezone # ~~ ~~~~~~~~~~~~~~~~~~~ # # This property controls the setting of the Control Center connection timezone. The # settings of the timezone is required to support TIMESTAMP WITH LOCAL TIMEZONE # calculations. This property should be used when the default behaviuor does work as # required. If not set the default behaviour is SERVICE. # # connection.timezone=NONE # # The property supports the following keyword values: # # SERVICE # DATABASE # NONE # # Where SERVICE uses the timezone of the Java VM that is running the Control Center service. # This can be overridden by added the -Duser.timezone JAVA VM argument in the run_service script. # Be aware that if you enter a timezone that is not known to the JVM then the JVM will pick a # default timezone. e.g. +02:00 or Windows can result in GMT+02:00, not +02:00 or Europe/Paris. # An optimization also removes the GMT prefix. # # Where DATABASE uses the timezone offset of the database. # # Where NONE does not initialize the session with a timezone. This may cause TIMESTAMP WITH # LOCAL TIMEZONE calculations to fail. # # The property can also be set with an Oracle Database timezone or offset. e.g. # # connection.timezone=+02:00 # # 7. JVM Timezone # ~~ ~~~~~~~~~~~~ # # This property controls the setting of the Control Center JVM timezone. The # settings of the timezone is required to support TIMESTAMP WITH LOCAL TIMEZONE # calculations. This property should be used when the default behaviuor does work as # required. If not set the timezone is retrieved from the host operating system. # The setting of this property is equivalent to adding -Duser.timezone to the JVM # argument list. If both are set then this value is taken in preference. # # user.timezone=GMT # # or # # properties.JVM.0.System.user.timezone=GMT # # 8. Connection OCI Fix # ~~ ~~~~~~~~~~~~~~~~~~ # # This property controls whether a dummy OCI connection is made prior to any thin # JDBC connection. This is necessary to ensure that the correct OCI shared libraries # are loaded in order to resolve an issue where a Discoverer deployment loads a set # of OCI shared libraries that are incompatible with a later use of Change Management. # # The "connection.oci_fix" property turns the OCI fix on or off (on | off). e.g. # # connection.oci_fix=on # # 9. JVM Properties # ~~ ~~~~~~~~~~~~~~ # # Any properties prefixed by "properties.JVM.0.System." will have the prefix # removed and will be added into the JVM's System properties. This is equivalent to # adding properties using the -D directive to the JVM's command line. # #properties.JVM.0.System.http.proxyHost=proxy.oracle.com #properties.JVM.0.System.http.proxyPort=80 #properties.JVM.0.System.http.nonProxyHosts=*.oracle.com #properties.JVM.0.System.user.language=fr #properties.JVM.0.System.user.region=FR # # 10. Runtime logging # ~~ ~~~~~~~~~~~~~~~~ # # These properties control where OWB places runtime log files, and the maxomum size # of those files. # #property.RuntimePlatform.0.max_number_logfiles=99999 #property.RuntimePlatform.0.logfile_max_size=0 #property.RuntimePlatform.0.exceptions=%RTHOME%/owb/log/OWBSYS.log #property.RuntimePlatform.0.messages=%RTHOME%/owb/log/OWBSYS.log # # # FTP, Shell amd SQLPlus operator are disabled by default # property.RuntimePlatform.0.NativeExecution.FTP.security_constraint = DISABLED property.RuntimePlatform.0.NativeExecution.Shell.security_constraint = DISABLED property.RuntimePlatform.0.NativeExecution.SQLPlus.security_constraint = DISABLED property.RuntimePlatform.0.NativeExecution.OMBPlus.security_constraint = DISABLED