Table Attribute of the jobRecovery Element. The jobStatusRepository element is defined in rwserverconf. You can have a maximum of one jobStatusRepository element in your server configuration file. The jobStatusRepository element specifies the Java class that implements a job status repository.
It provides an additional means over the persistFile element of storing job status information. The persistFile is a binary file and, therefore, cannot be used to publish job status information within your application. The jobStatusRepository element provides a means of including status information in your application by providing additional ways of storing it. The default class, oracle. JobRepositoryDB , stores information in a database. JobRepository that stores information wherever you wish.
The jobStatusRepository element attribute is described in Table Table Attribute of the jobStatusRepository Element. You can also optionally enter multiple property sub-elements for the jobStatusRepository element for passing options into the repository.
The jobStatusRepository element might look like this in your server configuration file:. The log element is defined in rwserverconf. You can have a maximum of one log element in your server configuration file.
The log element is available for backward compatibility. It invokes the generation and population of a reports log file. The log file is automatically generated and stored in the following path the path is the same for Windows and UNIX :. The log element attribute is described in Table Table Attribute of the log Element. Describes the type of jobs that are logged. This is in addition to the default server activities that are logged. Choose from the following options:.
The jobRepository element is defined in rwserverconf. Required in a high availability HA environment. Optional in a non-HA environment. You can have a maximum of one jobRepository element in your server configuration file. The jobRepository element enables you to store all job information in the database instead of the file system that is, in DAT files.
This element is mandatory if you want to use high availability HA , because Reports Servers in the group share job information, which is possible only if the job information is stored in the database, and not individual DAT files. The notification element is defined in rwserverconf. If you do not enter a notification element in the configuration file, the notification function is disabled. You can have from zero to multiple notification elements in your configuration file.
Use the notification element to specify a Java class that defines the type of notification that should be sent when a job succeeds or fails. You can use the default notification class, which provides for notification through e-mail, or design your own with the Oracle Reports Notification API.
The notification element attributes are described in Table Table Attributes of the notification Element. A keyword, unique within a given configuration XML file, that identifies a particular notification element. If you use the default email notification implementation, use the pluginParam element to specify the outgoing SMTP mail server to be used to send the mail. Use the command line keyword notifysuccess and notifyfailure to specify the email address where notification should be sent for more information, see Appendix A, "Command-Line Keywords".
For example, you can include these commands in your runtime URL:. With the default e-mail implementation, you can specify only one address for each type of notification. You can specify one or both types of notification. You can send notification each to the same address or each to a different addresses. A notification element in the server configuration file might look like this:.
Some mail servers may validate the sender's domain name. If the notification fails because of this domain name validation, then you must add the following property as part of the notification element:. Otherwise, enter the directory path along with the filenames according to the requirements of the platform that hosts the server. The oidconnection element is defined in rwserverconf.
The oidconnection element specifies Oracle Internet Directory connection pooling parameters for Reports Server. In a production environment, you can use this parameter to provide granular control over Oracle Internet Directory connection pooling of Reports Server, namely:. Upon exhausting the available connections, the number of new connections to be added to the pool when a new request arrives.
The timeout for closing idle open Oracle Internet Directory connections to reduce the resource usage. The oidconnection element attributes are described in Table Table Attributes of the oidconnection Element. Initial number of Oracle Internet Directory connections to be created when Reports Server is initialized. For Oracle Reports Servlet rwservlet , you can specify Oracle Internet Directory connection pooling parameters using the oidconnection element in the rwservlet.
The orbClient element is defined in rwserverconf. If you do not specify the orbClient element in your server configuration file, the default values will be used. The orbClient element specifies the name of the public key file that the client will use to connect to Reports Server. Reports Server uses the public key to verify the signature sent by the client when it tries to connect to Reports Server.
Reports Server only accepts clients whose signature can be verified through this public key. You can have from zero to multiple orbClient elements in your server configuration file.
The orbClient element attributes are described in Table Table Attributes of the orbClient Element. Identifies the public key file that the client will use to connect to Reports Server. The default file is stored in the rwrun. Oracle Reports Services provides default client public and private key files, clientpub. These key files are in place for all components of Oracle Reports Services You can regenerate public and private key files to replace the default key pair.
To do this, at the command prompt use the following command:. To do this, you must unjar the file, place the regenerated private key into it, and rejar the file. The persistFile element is defined in rwserverconf.
You can have a maximum of one persistFile element. The persistFile element identifies the file that records all job status. It is used by Reports Server to restore the server to the status it held before shutdown. It is named persistFile because the file remains intact, or persists, even when the server is brought down and restarted. The server persistent file is created automatically the first time you start the server or the first time you start the server after the current server persistent file has been deleted or renamed.
If you want to rename this file but continue using it, enter the new name in the server configuration file before you actually rename the file, then restart the server. The persistFile element attribute is described in Table Table Attribute of the persistFile Element.
The name and, optionally, the path of the server persistent file. You can leave the path off if the file is kept in its default directory:. The identifier element is defined in rwserverconf. You can have a maximum of one identifier element in your server configuration file. The identifier element is automatically written to the configuration file by the Reports Configuration Assistant when you first install Oracle Reports. This user name and password is then encrypted and written to rwserver.
Any Reports Server started after the installation will have this identifier information stored in its configuration file. For a non-secured Reports Server, the values of the identifier element is used when:. In either of these cases, you must provide the authid in the command line that matches the values specified in the identifier element. To provide a specific password as the password is a pseudo random number , you must do the following:.
Restart Reports Server. Edit the targets. You should restart Reports Server, immediately, after making this change. Reports Server automatically encrypts the user name and password and resets encrypted to yes. The values should now read as follows:. For a secure Reports Server, the authentication is done by the security infrastructure; that is, by using the Oracle Internet Directory repository. Thus, you cannot pass the values in the identifier element to shut down a Reports Server or launch Reports Queue Manager through the console window.
For more information on rwservlet. The property element is defined in rwserverconf. See the following element descriptions for information about specifying the property element in rwserver. The queue element is defined in rwserverconf. You can have a maximum of one queue element in your server configuration file. If you have no queue element, the default maxQueueSize , , will remain in effect.
Use the queue element to specify the maximum number of jobs that can be held in a completed job queue. Oracle Reports Services has three queue components:.
The queue element provides the allowable value for each of these components. This element is applicable only to the completed job queue. Thus, if the number of jobs exceeds the specified maximum value, that completed job queue will automatically purge its oldest jobs.
The scheduled job queue and the in-progress job queue remain unaffected. By default reports server queue size is jobs. If you increase the queue size to more than , and use Reports Queue Manager rwrqm. When a queue size of or greater is required, use Oracle Reports Servlet rwservlet to manage and monitor the Reports Server jobs queue. The queue element attribute is described in Table Table Attribute of the queue Element. The folderAccess element is defined in rwserverconf.
The folderAccess element defines read and write access to file system folders for both secured and non-secured Reports Server, Reports Application in-process Reports Server , or Oracle Reports Runtime.
Separate directory names with a semicolon ;. The security element is defined in rwserverconf. If you do not enter a security element in the configuration file, Reports Server is not secure. You can have from zero to multiple security elements in your configuration file. The security element identifies the fully qualified Java class that controls server access. The security element attributes are described in Table Table Attributes of the security Element.
A keyword, unique within a given configuration XML file that identifies a particular security element. This can be a text string or a number, for example for 11 g :. Default for 11g: oracle. Default for backward compatibility: oracle.
The default relies on security features available through Oracle Portal. You can associate multiple properties with the security element. The value of all the properties is set by the Installer upon installation. Components of the Oracle Fusion Middleware can all connect to Oracle Internet Directory and Oracle Portal, but each component may have different privileges in the directory. Hence, each component needs to identify itself through its own entity name to Oracle Internet Directory when it connects.
The Oracle Reports Services entity is of the following format:. The proxyServer element is defined in rwserverconf. Element that specifies the name, port and protocol of proxy server to be used in order to connect to external network. The proxyServer element attributes are described in Table Table Attributes of the proxyServer Element.
The domain element is defined in rwserverconf. Element that specifies the name of the proxy server for which proxy setting should not be used. The domain element has no attributes. The bypassProxy element is defined in rwserverconf. The element that provides a list of domains which specifies name of the proxy server for which proxy setting should not be used.
The bypassProxy element has no attributes. It includes the domain sub-element see Section 7. The proxyServers element is defined in rwserverconf. The proxyServers element has no attributes. It includes the proxyServer sub-element see Section 7.
The proxyInfo element is defined in rwserverconf. Element specifying proxy servers used by reports and the bypass hosts for which proxy should not be used. The webLayout element is defined in rwserverconf. The webLayout element attributes are described in Table Table Attributes of the webLayout Element.
The dbProxyKey element is defined in rwserverconf. Solution Area. Chapter 12, "NLS and Bidirectional Support" contains additional detailed information about this environment variable, including a table of valid values. The string used to indicate a positive monetary value. The string used to indicate a negative memory value. The character used to separate items in a list. The decimal character and thousands separator for monetary values. The decimal character and grouping separator for numeric values.
The default value is Cookies save encrypted user names and passwords on the client-side when users log on to a secured Oracle9 i AS Reports Server to run report requests. We'll send a magic link to your inbox. Email Address. All Sign in options. Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox. Newsletter Topics Select minimum 1 topic. Register or Login. Welcome back!
0コメント