Advanced system care 3.4.2 serial key or number

The metadata available in this repository is a work in progress. It reflects the latest reference metadata information provided by the UN System and other international organizations on data and statistics for the Tier I and II indicators in the global indicator framework. This repository will be further updated and periodically reviewed in cooperation with the respective data compilers.

In addition:

Please send your feedback and suggestions for improvements to statistics@un.org.

3.2.1.1 server

Example

Required/Optional

Required. You can have a maximum of one open and close tags in the element in a given configuration file.

Description

The element opens and closes the content area of the server configuration file. In terms of the file's hierarchy, all the other elements are subordinate to the element.

3.2.1.2 compatible

Example

Required/Optional

Optional. You can have a maximum of one element in your server configuration file.

Description

The element is available for backward compatibility with Oracle Reports 6i clients (, , , , , 6i Forms). When is set to , Reports Server will make use of an executable file named that listens for requests from a 6i client and forwards them to a 10g server.

The element attribute is described in Table 3-2.

If you use the element, you must also have an entry for Reports Server in the file as you would have had for the 6i version of Reports Server. The installer configures the file for the default Reports Server; that is, .

For example:

You can bypass this requirement by turning compatibility off. To turn compatibility off, remove the element from the Reports Server configuration file.

3.2.1.3 cache

Example

Required/Optional

Optional. You can have a maximum of one element in your server configuration file. If no cache element is specified, the default is used ().

Description

The element is available for specifying the Java class that defines the server's cache implementation. You can use the default cache Java class or develop your own implementation through the OracleAS Reports Services Cache API.

The element attribute is described in Table 3-3.

You can also enter from zero to multiple properties under the element. Properties are name/value pairs recognized and understood by the implementation class you register under . For example, if you use the default cache Java class that is provided with OracleAS Reports Services, your configuration entry might look like this:

In the preceding example, is measured in megabytes, and , which points to the location of the cache, is specified for a Windows platform. On UNIX, use UNIX standards, for example:

The default cache Java class also provides the following properties:

• is the maximum number of files allowed in the cache. For example:

  <property name="maxCacheFileNumber" value="250"/>

• lists any report parameters you want to be ignored when Reports Server constructs the cache key. (The cache key is used by Reports Server to determine if an incoming job request matches existing output in the cache.)

  <property name="ignoreParameters" value="param1,param2"/>

3.2.1.4 engine

Example

Required/Optional

Required. You must have at least one element in your configuration file, and you can have more than one.

Description

The element identifies the fully qualified Java class that starts an engine and provides a number of attributes that set operational controls on the engine. You can use the default engines provided with OracleAS Reports Services or develop your own implementation through the OracleAS Reports Services Engine API. As an example of a custom engine, you may have developed an engine to execute an operating system command should an event occur in your database.

The element attributes are described in Table 3-4.

Properties

You can also optionally enter multiple properties under the element. The only requirement is that they be name/value pairs recognized by the Java class that implements the Oracle Reports engine.

andproperties: If you use the default engine Java class that is provided with OracleAS Reports Services, your configuration entry might look like this:

In this example, and are set up for a Windows environment (UNIX would be and):

• The property identifies the default directory you will use for report definition files. It overrides path information specified in the environment variable.

• The property identifies the name and location of the temporary directory OracleAS Reports Services will use for its temporary files. If this value is unspecified for a default engine, OracleAS Reports Services will use the temporary directory specified in the environment variable. If is also not specified, OracleAS Reports Services will use your operating system's default temporary directory.

The attribute is not specified because this configuration uses the default class.

property: Oracle Reports 10g Release 2 (10.1.2) introduces the property for engine logging. Including this property in your configuration element enables you to diagnose whether or not a specific function in a report run completed successfully. The diagnostic log provides information on important checkpoints or tasks in the engine during a report run. This information is useful in cases where the engine stops responding, resulting in "hanging" jobs.

To turn on the engine diagnosis option, your configuration element might look like this:

When the property is set to , the engine creates separate diagnostic files from the Reports Server and engine trace files. Diagnostic files are in the same location as the trace files (see Section 20.1.2, "Report Trace"). Every engine creates two diagnostic files per instance (that is, per engine lifetime). For example:

Each diagnostic log is a new file, with the timestamp included in the file name. Diagnostic files are not appended to or replaced for different instances of the same engine.

The engine diagnosis option provides more detailed information than report tracing, which is typically used to debug the execution of a report to provide information such as the file currently formatting, or report trigger currently running.

3.2.1.5 security

Example

Required/Optional

Optional. If you do not enter a element in the configuration file, Reports Server is not secure. You can have from zero to multiple elements in your configuration file.

Description

The element identifies the fully qualified Java class that controls server access. You can use the default security class provided with OracleAS Reports Services, which relies on security features available through OracleAS Portal (included with Oracle Application Server), or develop your own implementation through the Reports Server Security API.

The element attributes are described in Table 3-5.

You can associate multiple properties with the element. The only requirement is that they be name/value pairs recognized by the Java class that implements Reports Server security. For example, if you use the default security Java class that is provided with OracleAS Reports Services, your configuration entry might look like the example provided.

The value of is set by the Installer upon installation. Reports Server uses this entity to connect to Oracle Internet Directory. Components of the Oracle Application Server can all connect to Oracle Internet Directory, 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 OracleAS Reports Services entity is of the following format:

For example:

The commented out property, , illustrates the old method of specifying security. provides the connection information to enable the Reports Server access to OracleAS Portal security features. The property attributes and are available for encrypting the information within the property. Once the and attributes are entered, the property value will be encrypted automatically by Reports Server after you restart the server. When you next open the configuration file, the password information will be scrambled, and will be set to . If you forget the password you entered in the configuration file, you can delete the property and reenter it with new values, making sure to set to .

3.2.1.6 oidconnection

Example

Required/Optional

Optional.

Description

The 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:

• The number of connections to keep open in the pool when Reports Server is initialized.

• 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 element attributes are described in Table 3-6.

For Reports Servlet, you can specify Oracle Internet Directory connection pooling parameters using the , , and properties in the file, as described in Section 3.4.12, "Specifying Oracle Internet Directory Connection Pooling Parameters".

3.2.1.7 destination

Example

Required/Optional

Optional. If you do not enter a element in the server configuration file, the provided destination classes will be used (printer, e-mail, file, cache, and OracleAS Portal—which is an exception in that it requires an entry in the server configuration file so that you may specify the userid and password the server will use to log in to the portal). You can have from zero to multiple elements in your server configuration file.

Description

Use the element to register destination types with the server. There is no need to register default destinations. You may need to configure the OracleAS Portal, FTP, or WebDAV destinations, as follows:

• OracleAS Portal: The entry for this destination is created by default in the server configuration file, but it is commented out. To start using this destination, you must uncomment the entry, and also provide appropriate property values (for example, the value for the property).

• FTP and WebDAV: The entries for these destinations are created by default in the server configuration file, and are not commented out. Thus, they are configured and available by default. If you need to send the output to an FTP or WebDAV server that requires a proxy, you will need to edit the file available in the default location (), then uncomment the property in the element and specify the complete path to the file as the value. For example:

You must register any new destination types you create through the OracleAS Reports Services Destinations API.

The element attributes are described in Table 3-7.

You also have the option of entering multiple properties under the element. The only requirement is that they be name/value pairs recognized by the Java class that is a subclass of the Reports Server Destination Java class. For example:

In this example, the property provides connect information to enable Reports Server to access OracleAS Portal. The and attributes are included to automatically invoke encryption on the value the next time Reports Server is started.

Should your destination implementation require additional information, specify the information in the pluginParam element.

3.2.1.8 networkConfig

Example

where:

is a custom Reports network configuration file that is located in the directory. Oracle Reports will use the Reports Server discovery mechanism specified in this file.

Required/Optional

Optional. By default, Oracle Reports uses the file in the directory to decide the Reports Server discovery mechanism. Uncomment this element to specify a custom network configuration file.

Description

This element specifies the network configuration file that will be used for Reports Server discovery. For more information, refer to Section 3.3, "Configuring the Reports Server Discovery Mechanism".

If is enabled, then the Reports Server will register itself to the COS naming service. Oracle Reports clients will then contact the naming service to get the Reports Server reference. The element attribute is described in Section 3.3.1.3, "namingService".

3.2.1.9 job

Example

Required/Optional

Required. You must have at least one element and can have more than one.

Description

The element works in collaboration with the engine and security elements. Use to identify a job type and specify which engine and which security implementation should be used with that type of job. For example, you may have developed an engine to execute an operating system command should an event occur in your database. Using OracleAS Reports Services's event-driven publishing API, you identify the event as a specific job type. When the event occurs, the job type information is sent to Reports Server, which looks up the job type under the element in its configuration file, and follows the direction provided in the element's attributes to the engine (and, if applicable, security implementation) specified for that type of job.

The element attributes are described in Table 3-9.

3.2.1.10 notification

Example

Required/Optional

Optional. If you do not enter a element in the configuration file, the notification function is disabled. You can have from zero to multiple elements in your configuration file.

Description

Use the 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 element attributes are described in Table 3-10.

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 runtime commands and to specify the email address where 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 . You can specify one or both types of . You can send each to the same address or each to a different addresses.

A 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 element:

With the default notification implementation, it's not necessary to specify a path to the success or failure text files, provided they're in the default location: . Otherwise, enter the directory path along with the filenames according to the requirements of the platform that hosts the server.

3.2.1.11 log

Example

Required/Optional

Optional. You can have a maximum of one element in your server configuration file.

Description

The 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 element attribute is described in Table 3-11.

3.2.1.12 jobStatusRepository

Example

Required/Optional

Optional. You can have a maximum of one element in your server configuration file.

Description

The 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 is a binary file and, therefore, cannot be used to publish job status information within your application. The provides a means of including status information in your application by providing additional ways of storing it.

The default class, , stores information in a database. Use the Oracle Reports APIs to create your own implementation of the Reports Server Job Repository interface () that stores information wherever you wish.

The element attribute is described in Table 3-12.

The element allows for zero or multiple properties for passing options into the repository. The only requirement is that the class you specify in the server configuration file must recognize the name/value pairs you introduce.

The element might look like this in your server configuration file:

In this example, the value for the property is the login for access to the database that stores the repository. The and attributes are used to invoke encryption on the login information once Reports Server is restarted.

3.2.1.13 trace

Example

Required/Optional

Optional. You can have a maximum of one element in your server configuration file.

Description

Use the element to create a file for tracing your report's execution and to specify the objects and activities you want to trace. The element controls tracing only for the server and the engine.

Reports Server uses the executable for submitting a print job. For logging for Windows, when you enable tracing for Reports Server using either or , a printing diagnostic log () is created in the log directory () for . This log file will contain information regarding the messages that can be used to diagnose any printing issues, such as spooler problems.

By default, trace files are generated in . If job tracing is specified, trace files are generated in .

The element attributes are described in Table 3-13.