You can configure Oracle Enterprise Scheduler interaction with applications by setting application properties. On the Application Properties page in Fusion Middleware Control, you can set values for properties that are defined by Oracle Enterprise Scheduler or properties specified for the application in its deployed configuration.
Oracle Enterprise Scheduler defines the following properties that you configure on the Application Properties page:
RequestFileDirectory: Specifies the directory for request and log output. The default is "{ESS_ENV:jrfServerLogPath}/ess_request/".
RequestFileDirectoryShared: Specifies a flag indicating whether the request file directory is shared. The default is "false".
PerlCommand: By default, Oracle Enterprise Scheduler uses the Java agent handler for requests in standard and extended mode. It always uses the Perl agent handler for requests in Fusion mode. To use the Perl agent handler in standard and extended request modes, you must add the PerlCommand
property to the ess-config.xml
file associated with the hosting application running the process job as shown in the following example.
<EssProperties>
<EssProperty key="RequestFileDirectory" value="/tmp/ess/requestFileDirectory"/>
<EssProperty key="RequestFileDirectoryShared" value="false"/>
...
<EssProperty key="PerlCommand" value="/usr/bin/perl"/>
</EssProperties>
You can use token substitution to specify environment dependent values like directory names.
The Oracle Enterprise Scheduler Perl agent handler requires Oracle Perl version 5.10 or later. Instructions for installing Perl to support process jobs can be found in the chapter "Configuring Perl to Support Process Jobs" in Oracle Fusion Middleware Administrator's Guide for Oracle Enterprise Scheduling Service.
EssCallbackClientSecurityPolicyURI: Specifies the security policy URI used in the WS-Security
headers for web service invocations from Oracle Enterprise Scheduler for web service callbacks. The default is null.
ClusterMode: Specifies whether the server instance is in standalone or extended mode. This is a read-only and immutable property.
HostingAppPolicyStripe: An Oracle Enterprise Scheduler configuration property that is applicable only for the pre-deployed native hosting application. This property is pre-configured in the pre-deployed native hosting application to support multiple security stripes that can be leveraged by SOA and OSB applications. There is no static definition of policy stripes in the pre-deployed native hosting application's ejb-jar.xml
file. The list of stripes (for additional components) can be extended dynamically using a runtime configuration MBean, Fusion Middleware Control or WLST scripts.
ServerURL: The value of this property value is a string with the following format:
http://
host:
port
It is used at runtime to determine the ESSWebService
end point address and is published as part of the ESSWebService
concrete WSDL.
CallbackServerURL: The value of this property is a string with the following format:
http://
host:
port
It is used at runtime to determine the end point address of Oracle Enterprise Scheduler callback web services (including EssAsyncCallbackService
, and EssWsJobAsyncCallbackService
). These end point addresses are published as part of the respective WSDLs.
To edit application properties:
Oracle Enterprise Scheduler provides the means by which EJB and web service jobs can define a named abstract job location. The job location is specified by the Oracle Enterprise Scheduler SYS_logicalClusterName
system property and specifies a logical cluster name (LCN). If the job definition for an EJB or web service job specifies a value for an LCN, certain environment-specific properties are specified using Oracle Enterprise Manager Fusion Middleware Control at the hosting application level rather than in the job definition. All job definitions with the same LCN share the value of the properties entered in the hosting application configuration properties using Oracle Enterprise Manager Fusion Middleware Control.
Note:
The terms "logical cluster" and "job location" can be used interchangeably.
To use the job location feature:
Note:
You can also delete job locations and properties by selecting them in the table and then clicking Delete Job Location or Delete Property.