Oracle® Warehouse Builder Concepts 11g Release 2 (11.2) Part Number E10581-01 |
|
|
View PDF |
This appendix describes the preferences available in OWB.
This appendix contains the following topics:
OWB 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 under categories, and each preference contains values that you set according to your design needs. You may also view and set preferences from the OWB client console menu under Tools>Preferences.
The Appearance category contains the Locale preference. Use the Locale list to set the language you want the client text to display. This list displays the language options for the client. OWB prompts you to restart the computer in order to use the new language setting.
Note:
The Locale selection does not define the character set of the OWB repository. The Locale appearance preference only affects the text and menu options on the client user interface. The repository character set is determined by the settings in Oracle Database.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:
OWB 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.
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 as a result of 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.
The Deployment category enables you to set deployment preferences such as displaying the deployment monitor, prompting for execution parameters, and showing completion messages. This enables you to control some of the 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. This 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 OWB prompts you to save these changes by displaying the OWB Warning dialog box. Click Save to commit unsaved design changes. Click Cancel to terminate the deployment.
If you do not set this option, then OWB 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, OWB 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 OWB uses the default value of parameters during the execution. OWB 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.
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 in to OWB. Collecting schema statistics improves repository performance. If this option is selected, at log on, OWB determines if statistics must be gathered for the repository schema. If statistics must be gathered, a warning dialog box is displayed asking if you want 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, the OWB 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 OWB 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 the OWB 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 runtime 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 pubic views. Otherwise, you will get "0 rows returned." You may need to ask the workspace owner or workspace admin to grant the system privilege ACCESS_PUBLICVIEW_BROWSER
.
The Generation/Validation category enables you to set preferences related to generation and validation of OWB 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.
The Code Template Editor preferences provide settings for how the editor will be laid out on screen. This 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 will 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.
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_ORACLE_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, OWB starts writing to the second log file, <logfilename>.1
. When the maximum size of the second one is reached, OWB starts 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.
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.
OWB 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, OWB editors, wizards, and property sheets display the business names of objects.
A business name must conform to these rules:
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, OWB generates a corresponding, valid physical name that resembles the business name. If you create a business name that duplicates an existing physical name, then OWB appends an underscore and a number in order 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, OWB 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.OWB 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, OWB must be in Business Name mode. To create or change a physical name for an object, OWB must be in Physical Name mode.
The default naming preferences for OWB 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.
OWB saves your naming preferences across sessions. The Name Mode preference is stored in a file on the client workstation. If you use OWB from another workstation, your preferences may be different.
See Also:
Oracle Database SQL Language ReferenceIMPORTANT:
Only administrators can edit the security preferences.
The Security Parameters category contains the following settings:
Persist Location Password in Metadata
This option determines whether or not location passwords are persisted across OWB design sessions.
By default, this option is deselected, which is the more secure setting. OWB 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 OWB 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 Windows and UNIX for more information about the encryption methodologyShare Location Password During Runtime
This parameter determines whether or not 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 username and password. When other users subsequently attempt to execute MAP1
or view data associated with it, the OWB preference determines whether or not each user must enter the password each time in the Design Center, or the first time in the Control Center.
Share Location Password During Runtime works in conjunction 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 once 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 OWB administrators.
This setting is not retroactive. That is, if you change this setting in an existing OWB 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 Windows and UNIX for more information about manually changing the security settings