Skip Headers
Oracle® Warehouse Builder Concepts
11g Release 2 (11.2)

E10581-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

A Oracle Warehouse Builder Design Center and Runtime Preferences

This appendix describes the preferences available in Oracle Warehouse Builder.

This appendix contains the following topics:

About Design Center Preferences

Oracle Warehouse Builder provides a set of user preferences that enable you to customize your user interface and environment. You set preferences from the Design Center by selecting an object and clicking Design on the Design Center menu.

Preferences are organized, and each preference contains values that you set according to your design needs. You may also view and set preferences from the Oracle Warehouse Builder client console menu under Tools>Preferences.

Oracle Warehouse Builder has the following preferences:

Code Template Editor Preferences

The Code Template Editor preferences provide settings for how the editor is laid out on screen. It enables management of screen real estate while you are editing a Code Template.

  • Vertical Layout Horizontal Spacing: Specify the screen width for vertical layout. The default is 80.

  • Horizontal Layout Horizontal Spacing: Specify the screen width for horizontal layout. The default is 25.

  • Direction of Auto Layout: Specify how the editor is automatically laid out on screen when opened. The default is Vertical.

  • Vertical Layout Vertical Spacing: Specify the screen height for vertical layout. The default is 5.

  • Horizontal Layout Vertical Spacing: Specify the screen height for horizontal layout. The default is 40.

Control Center Monitor Preferences

Use the Control Center Monitor category to set preferences that control the display of components in the Control Center. When you use the Control Center to deploy or execute objects, the Job Details window displays the results of deployment or execution. The Control Center Monitor preferences enable you to control which items to display in the object tree of the Job Details window.

Note:

Oracle Warehouse Builder displays the Job Details window only if you select the Show Monitor preference under the Process node of the Deployment preferences category.

If this option is not selected, then you can view the Job Details window by double-clicking the row representing the deployment or execution job in the Control Center Jobs panel of the Control Center.

The Control Center Monitor category contains the following preferences:

  • Show Project: Select this option to display the project name in the Job Details window object tree. When this option is selected, the object tree displays a node for the named project, and all the objects are displayed under this project node.

  • Show Module: Select this option to display the name of the module to which the object being deployed or executed belongs in the Job Details window. When this option is selected, the object tree displays a node for the module. Expand the module node to view the object details.

  • Show Location: Select this option to display the location name in the object tree of the Job Details window.

  • Show Action: Select this option to display and access the actions that can be performed on the object in the object tree of the Job Details window. The actions that can be performed are: Create, Drop, Deploy, and Upgrade.

  • Show Type: Select this option to display the type of object in the object tree of the Job Details window. When you select this option, a node is displayed for the type of object and the objects are listed under the respective nodes.

Data Profiling Preferences

Use the Data Profiling category to set the preferences for data profiling.

This category contains the following preferences:

  • Data Rule Folder Name: Use this option to set the name of the folder that contains the data rules equals data profiling.

  • Default Profile Location: Use this option to set the default location that is used to store the data profiling results. You can override this setting by selecting a different location as your profile location. In the Data Profile Editor, from the Edit menu, select Properties. Use the Data Locations tab to change the default profile location.

Deployment Preferences

The Deployment category enables you to set deployment preferences such as displaying the deployment monitor, prompting for execution parameters, and showing completion messages. It enables you to control some popup windows that are displayed by the Control Center Manager during object deployment.

Deployment preferences are divided into two sections: "Process" and "Monitor". Expand the Deployment node in the Preferences dialog box. Click the node for which you want to set preferences.

Process

The Process node sets the following deployment options:

  • Pause After Compile: Select this option to pause deployment after script generation. It means that you must explicitly deploy an object after it is successfully generated.

  • Prompt for Commit: Select this option to prompt the user to commit design time changes before a deployment. When you deploy objects from the Design Center, if there are any unsaved design changes, then Oracle Warehouse Builder prompts you to save these changes by displaying Oracle Warehouse Builder Warning dialog box. Click Save to commit unsaved design changes. Click Cancel to terminate the deployment.

    If you do not set this option, then Oracle Warehouse Builder saves any design changes before the deployment job.

  • Prompt for Job Name: Select this option to prompt the user for the name of a deployment job. When this option is not selected, Oracle Warehouse Builder assigns a default job name.

  • Prompt for Execution Parameters: Select this option to prompt the user for the values of execution parameters. If you do not select this option, then Oracle Warehouse Builder uses the default value of parameters during the execution. Oracle Warehouse Builder does not prompt you to provide the parameter values.

  • Show Monitor: Select this option to display the Job Details window when you deploy or execute an object. This dialog box displays details of the objects being deployed, deployment progress, and deployment status.

  • Show Deployment Completion Message: Select this option to display an alert indicating that the deployment job has completed.

  • Show Design Center Deployment Job: Select this option to display the Control Center Jobs dialog box when you deploy an object from the Design Center. The Control Center Jobs dialog box, which is similar to the Jobs panel of the Control Center Manager, contains the Deployment, Execution, and Scheduled tabs. Use this option to view the status of a deployment job while deploying using the Design Center.

Monitor

The Monitor node sets the following deployment monitoring options:

  • Show Monitor Tree: Select this option to show the Job Details window when you perform a deployment or execution.

  • Show Monitor Results: Select this option to display the deployment or execution results in Control Center Manager.

  • Show Monitor Logfile: Select this option to display the log file in the Control Center Manager.

Environment Preferences

The Environment category enables you to set generic preferences that control the client environment such as displaying welcome pages for wizards and recycle bin preferences.

You can set the following environment preferences:

  • Recycle Deleted Objects: Select this option to move deleted objects to the recycle bin. If this option is not selected, any objects you delete are lost and you have no way of recovering them.

  • Allow Optimize Repository Warning on Startup: Select this option to collect schema statistics when you log on to Oracle Warehouse Builder. Collecting schema statistics improves repository performance. If this option is selected, at log on, Oracle Warehouse Builder determines if statistics must be gathered for the repository schema. If statistics must be gathered, a warning dialog box is displayed asking to gather statistics now. Click Yes to collect schema statistics and optimize the repository.

    If you do not select this option, you can still collect schema statistics from the Design Center by selecting Optimize Repository from Tools menu.

  • Show Delete Confirmation Dialog Box: Select this option to display a dialog box that asks for a confirmation before deleting an object. When this option is selected, if you delete an object, Oracle Warehouse Builder Warning dialog box is displayed. Click Yes to delete the object. Click No to cancel the Delete operation and retain the object.

  • Hide All Wizard Welcome pages: Select this option to hide the welcome page of all wizards. Every wizard in Oracle Warehouse Builder starts with a Welcome page that summarizes the steps to follow to complete that task. To display the Welcome page for all wizards, deselect this preference.

  • Empty Recycle Bin on Exit: Select this option to empty the contents of the recycle bin when you exit Oracle Warehouse Builder client. Deselect this option to save the recycle bin objects across sessions.

  • Default Workspace: Select this option to set the default workspace for the logged in user to use. A drop-down list shows the workspaces for which the logged in user is registered. The initial setting is for the first workspace that you own or for which you were registered.

    Note:

    You can access public views from your default workspace. From your default workspace, when you log in to SQL*Plus, you can access public views (design-time public views or run time public views) without needing to call a separate procedure.

    If you try to access public views from any workspace other than the default, then you must call: WB_workspace_management.set_workspace(<wksp_name>, <wksp_owner>).

    If you want to switch to a workspace other than the default one, then you can call the WB_workspace_management.set_workspace procedure. You must have the ACCESS_PUBLICVIEW_BROWSER system privilege to retrieve useful information from the public views. Otherwise, you get "0 rows returned." You must ask the workspace owner or workspace admin to grant the system privilege ACCESS_PUBLICVIEW_BROWSER.

Expert Editor Preferences

The Expert Editor preferences provide settings for how the editor is laid out on screen. It enables management of screen real estate while you are editing a Code Template.

  • Vertical Layout Horizontal Spacing: Specify the screen width for vertical layout. The default is 80.

  • Horizontal Layout Horizontal Spacing: Specify the screen width for horizontal layout. The default is 25.

  • Direction of Auto Layout: Specify how the editor is automatically be laid out on screen when opened. The default is Vertical.

  • Vertical Layout Vertical Spacing: Specify the screen height for vertical layout. The default is 5.

  • Horizontal Layout Vertical Spacing: Specify the screen height for horizontal layout. The default is 40.

Generation/Validation Preferences

The Generation/Validation category enables you to set preferences related to generation and validation of Oracle Warehouse Builder design objects. Use these preferences to control what is displayed in the Generation Results dialog box or Validation Results dialog box. These dialog boxes are displayed when you generate or validate an object from the Design Center.

The Generation/Validation category contains the following preferences:

  • Show Project: Select this option to display the project node in Validation Results dialog box or the Generation Results dialog box.

  • Show Module: Select this option to display the module node in Validation Results dialog box or the Generation Results dialog box.

  • Show Location: Select this option to display the location node in Validation Results dialog box or the Generation Results dialog box.

  • Show Action: Select this option to display the action node in Validation Results dialog box or the Generation Results dialog box.

  • Show Type: Select this option to display the type node in Validation Results dialog box or the Generation Results dialog box.

Lineage and Impact Analysis Preferences

The Lineage and Impact Analysis preferences provide settings for how the editor is laid out on screen. It enables management of screen real estate while you are editing a Code Template.

  • Vertical Layout Horizontal Spacing: Specify the screen width for vertical layout. The default is 80.

  • Horizontal Layout Horizontal Spacing: Specify the screen width for horizontal layout. The default is 25.

  • Direction of Auto Layout: Specify how the editor is automatically be laid out on screen when opened. The default is Vertical.

  • Vertical Layout Vertical Spacing: Specify the screen height for vertical layout. The default is 5.

  • Horizontal Layout Vertical Spacing: Specify the screen height for horizontal layout. The default is 40.

Logging Preferences

The Logging Preferences category enables you to set log file options such as file location, file size, and types of messages saved to any log file. The log file contains messages relating to your design process. By default a message log is saved to the default location.

The Logging Preferences category contains the following preferences:

  • File Path: This option specifies the location where the log files are saved. Enter the complete path or use the Browse button to select the location. The default location is OWB_HOME\owb\bin\admin.

  • File Name: This option specifies the name of the log file. Do not include a file extension when you specify a file name.

  • Maximum Size (Kb): This option specifies the maximum file size for the log file(s) in Kb. There are two log files: <logfilename>.0, and <logfilename>.1. When the maximum size of the first log file <logfilename>.0 is reached, Oracle Warehouse Builder starts writing to the second log file, <logfilename>.1. When the maximum size of the second one is reached, Oracle Warehouse Builderstarts overwriting the first log file.

  • Log Error Messages: Select this option to write all error messages to the log file.

  • Log Warning Messages: Select this option to write all warning messages to the log file.

  • Log Information Messages: Select this option to write all information messages to the log file.

Mapping Editor Preferences

The Mapping Editor preferences provide settings for how the editor is laid out on screen. It enables management of screen real estate while you are editing a Code Template.

  • Vertical Layout Horizontal Spacing: Specify the screen width for vertical layout. The default is 80.

  • Horizontal Layout Horizontal Spacing: Specify the screen width for horizontal layout. The default is 25.

  • Direction of Auto Layout: Specify how the editor is automatically be laid out on screen when opened. The default is Vertical.

  • Vertical Layout Vertical Spacing: Specify the screen height for vertical layout. The default is 5.

  • Horizontal Layout Vertical Spacing: Specify the screen height for horizontal layout. The default is 40.

Naming Preferences

The Naming Preferences category enables you to set naming preferences by selecting whether you want to view objects in Business Name or Physical Name mode. You can also set how you want to propagate object name changes, and whether you want to synchronize names with the target.

The Naming Preferences category contains the following preferences:

  • Naming Mode: Selects whether to display objects using their physical or business names.

  • Propagate Name Changes: Propagates name changes from the current naming mode to the other naming mode (physical to business naming mode, and vice versa.)

  • Synchronize: Selects whether to synchronize names with the target object, or to keep names as-is.

About Naming Modes

Oracle Warehouse Builder maintains a business name and a physical name for each object stored in the repository. A business name is a descriptive logical name for an object. A physical name is the actual object name recognized by the repository.

When you generate DDL scripts for a named object, the physical names are used. Physical names must conform to the syntax rules for basic elements as defined in the Oracle Database SQL Language Reference.

Names must be unique within their category:

  • Module names must be unique within a project.

  • Warehouse object names must be unique within a warehouse module. This includes the names of tables, dimensions, cubes, mappings, materialized views, sequences, views and indexes.

  • Transformation names must be unique within a transformation package.

Business Name Mode Use Business Name mode to create a business name for an object or to change the business name of an existing object. When this mode is selected, Oracle Warehouse Builder editors, wizards, and property sheets display the business names of objects.

A business name must conform to these rules:

  • The length of a name cannot exceed 200 characters.

  • The name must be unique within its category.

  • All source modules reflect the case of the imported source and are subject to the double-quotes rules as defined in the Oracle Database SQL Language Reference.

Copy operations from a source to a target in a mapping are not case-sensitive.

When you create a business name, Oracle Warehouse Builder generates a corresponding, valid physical name that resembles the business name. If you create a business name that duplicates an existing physical name, then Oracle Warehouse Builder appends an underscore and a number to create a unique name.

Physical Name Mode Use Physical Name mode to create a physical name for an object or to change the physical name of an existing object. When this mode is selected, Oracle Warehouse Builder editors, wizards, and property sheets display the physical names of objects. Physical names are converted to UPPERCASE.

An object's physical name must conform to these rules:

  • Contain no more than 30 characters.

  • Conform with the basic syntax rules for schema objects as defined by Oracle Database SQL Language Reference.

    Note:

    A collection can have a physical name containing up to 200 characters.

Oracle Warehouse Builder prevents you from entering an invalid physical name. For example, you cannot enter a duplicate name, a name with too many characters, nor a name that is a reserved word.

Setting the Name Mode To create or change a business name for an object, Oracle Warehouse Builder must be in Business Name mode. To create or change a physical name for an object, Oracle Warehouse Builder must be in Physical Name mode.

The default naming preferences for Oracle Warehouse Builder are as follows:

  • Mode: The default setting for the mode is physical name mode.

  • Propagation: The default propagation setting is to propagate physical name to business name.

Icons for the name mode and name propagation settings are located in the lower-left corner of the editors. These icons indicate the current naming preference setting.

Oracle Warehouse Builder saves your naming preferences across sessions. The Name Mode preference is stored in a file on the client workstation. If you use Oracle Warehouse Builder from another workstation, your preferences may be different.

Process Flow Editor Preferences

The Process Flow Editor preferences provide settings for how the editor is laid out on screen. It enables management of screen real estate while you are editing a Code Template.

  • Vertical Layout Horizontal Spacing: Specify the screen width for vertical layout. The default is 80.

  • Horizontal Layout Horizontal Spacing: Specify the screen width for horizontal layout. The default is 25.

  • Direction of Auto Layout: Specify how the editor is automatically be laid out on screen when opened. The default is Vertical.

  • Vertical Layout Vertical Spacing: Specify the screen height for vertical layout. The default is 5.

  • Horizontal Layout Vertical Spacing: Specify the screen height for horizontal layout. The default is 40.

Recent Logons Preferences

The Recent Logons preferences enables you to set preferences regarding the most recent logons. The table on this page displays details of the most recent logons. The details include the repository user name, host name, port number, and service name.

Use the Maximum Logons Remembered field to specify the number of recent logons for which Oracle Warehouse Builder client should store details. For example, if you set this field to 4, the table displays details of the four most recents logons.

To modify the details of a particular logon, click the detail you want to modify and enter the new value.

To delete a recent logon, right-click the row header and select Delete.

Security Parameters

Note:

Only administrators can edit the security preferences.

The Security Parameters category contains the following settings:

Persist Location Password in Metadata

This option determines whether location passwords are persisted across Oracle Warehouse Builder design sessions.

By default, this option is deselected, which is the more secure setting. Oracle Warehouse Builder retains location passwords for the length of the design session only. That is, the first time you start tools such as the Data Viewer or Debugger, you must enter the appropriate location passwords.

If this option is selected, then Oracle Warehouse Builder persists encrypted versions of location passwords in the workspace. The result is that you can start tools such as the Data Viewer and Debugger without entering passwords each time.

See Also:

"Encrypting Passwords to Warehouse Builder Locations" in Oracle Warehouse Builder Installation and Administration Guide for more information about the encryption methodology.

Share Location Password During Runtime

This parameter determines whether the location passwords that users enter during the design phase can be shared with other users. For example, assume that user Dev1 designs mapping MAP1. To access the sources and targets for this mapping, Dev1 defines the locations to each source and target, including a user name and password. When other users subsequently attempt to execute MAP1 or view data associated with it, Oracle Warehouse Builder preference determines whether each user must enter the password each time in the Design Center, or the first time in the Control Center.

Share Location Password During Run time works with "Persist Location Password in Metadata". The most secure mode, and the default behavior, is for both options to be deactivated. In this case, each user, including Dev1, must enter their password for each Design Center session and for the first time they attempt to use that location in the Control Center. Depending on your security requirements, you may want each user to define their own location for a given source or target

If both Share Location Password During Runtime and "Persist Location Password in Metadata" are activated, then any user can access a schema given that any user previously defined the location. Therefore, user Oper2 can execute MAP1 given that Dev1 or any other user previously defined the location with valid credentials.

Default Metadata Security Policy

This parameter specifies the default security policy to be applied. Minimum security enables all users full control over objects that any newly registered user creates. Maximum security, however, restricts access to the newly registered user who created the object, and to Oracle Warehouse Builder administrators.

This setting is not retroactive. That is, if you change this setting in an existing Oracle Warehouse Builder implementation, then the setting does not affect existing users and existing objects. You must manually change the security settings on existing objects.

See Also:

"Managing Security" in Oracle Warehouse Builder Installation and Administration Guide for more information about changing the security settings manually.

About Runtime Preferences

This file contains the Control Center property values. The properties defined in this file override any property values stored in the Control Center repository and is read during Control Center service startup. The Control Center service must be restarted for any changes to this file to become active. The file provides a default for all Control Center repositories. For defaults on per repository basis, a new file is created suffixed with the repository name in upper case.

Runtime_MYREPOS.properties.

The file is under strict operating system access control with update privileges only by the DBA, and read access by the user running the Control Center service. The backward slash character '\' is used as an escape character so '\\' is the equivalent to '\'.

Runtime.Properties file has the following features:

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

The following values are used to control the operator behaviour:

  • 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 that is executed by the default operating system user configured by the DBA. DISABLED prevents execution through these operators.

Note:

This option does not effect the users ability to schedule jobs through Oracle Warehouse Builder.

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

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 are used to pre-pend a command and parameter_list. This is 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 use backslash as an escape character.

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

Connection Pooling

Connection Pooling 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). For example:

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. For example:

connection.max_pool_size=50

The "connection.max_reallocations" property controls the number of times 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. For example:

connection.max_reallocations=-1

Garbage Collection

The following properties enable turning the explicit garbage collection. This is useful in a multi-CPU system where the implicit garbage collector may not be called efficiently.

  • The "garbage_collect.interval" property sets the number of jobs that are run before the explicit garbage collector is run. A value of zero or less turns the feature off. For example:

    garbage_collect.interval=100
    
  • The "garbage_collect.on_idle" property controls the explicit garbage collection when the Control Center is idle or has no active jobs. The valid values are 'true' or 'false'. For example:

    garbage_collect.on_idle=true
    
  • The "garbage_collect.limit" property configures the explicit garbage collector 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 tends to optimize its memory usage. For example:

    garbage_collect.limit=90
    

Connection Timezone

This property controls the setting of the Control Center connection time zone. The settings of the time zone is required to support TIMESTAMP WITH LOCAL TIMEZONE calculations. This property is necessary when the default behaviuor does work as required. If not set the default behaviour to SERVICE.

connection.timezone=NONE

The property supports the following keyword elements:

  • SERVICE

  • DATABASE

  • NONE

where, SERVICE uses the time zone 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. If you enter a time zone that is not known to the JVM, then the JVM picks a default time zone like +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 time zone offset of the database.

NONE, does not initialize the session with a time zone. This causes TIMESTAMP WITH LOCAL TIMEZONE calculations to fail.

The property can also be set with an Oracle Database time zone or offset. For example:

connection.timezone=+02:00

JVM Timezone

This property controls the setting of the Control Center JVM time zone. The settings of the time zone is required to support TIMESTAMP WITH LOCAL TIMEZONE calculations. This property is necessary when the default behavior works as required, else set the time zone as 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 these values are taken in preference.

user.timezone=GMT

or

properties.JVM.0.System.user.timezone=GMT

Connection OCI Fix

This property controls whether a dummy OCI connection is made before any Thin JDBC connection. This is necessary to ensure that the correct OCI shared libraries are loaded 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). For Example:

connection.oci_fix=on

JVM Properties

Any properties prefixed by "properties.JVM.0.System." has the prefix removed and is 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

Runtime Logging

Runtime logging properties controls the runtime logging files that are placed by Oracle Warehouse Builder.

  • 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 and 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