| Oracle® Life Sciences Data Hub System Administrator's Guide Release 2.2.2 E55498-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Life Sciences Data Hub System Administrator's Guide Release 2.2.2 E55498-01 |
|
|
PDF · Mobi · ePub |
This section contains the following topics:
Oracle Applications includes a set of profiles whose settings affect the way your application looks and behaves. You must have the System Administrator responsibility to set profile values at the site level.
For further information, see the Oracle E-Business Suite System Administrator's Guide - Maintenance at http://download.oracle.com/docs/cd/B53825_08/current/acrobat/121samg.pdf.
Open your Oracle LSH URL.
Log on with the system administrator account. An E-Business Suite screen opens.
In the Main Menu pane, expand the System Administrator (not System Administration) node, then the Profile node, and then click System.
A new browser screen opens with several windows open and the Find System Profile Values window on top.
Tip:
If you lose the Find System Profiles window at any point, click the Search icon in the toolbar or click System Profiles in the Top Ten list.The value for this profile determines the encoding used when uploading and downloading files from the client. It must be set to UTF-8. The system administrator can set it at the site level. Individual users (or the system administrator) can set it at the user level in the Oracle LSH User Preferences user interface. The user setting overrides the site setting.
The shipped default value is WE8MSWIN1252.
To change the default value, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter FND: Native Client Encoding or some part of that string followed by the wild card: %
Click Find. The System Profiles pop-up window appears with the profile displayed.
Click in the Site column. An ellipsis (...) appears on the right-hand side of the field.
Click the ellipsis (...). A pop-up box appears.
Click UTF-8 and then OK.
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Close the window.
If your data includes multibyte unicode characters, your data may sometimes not fit into character columns in the Oracle LSH Table instances you create because you are using byte semantics (which is the default behavior). You can set this profile to Yes to use character semantics instead of byte semantics across your Oracle LSH installation.
Using byte semantics, a character column's length is the same as the number of bytes the column can contain. For example, a character column with a length of 2 can contain either two 1-byte characters or one 2-byte character, but it cannot contain one 2-byte character and one 1-byte character together. If you try to write more bytes of data into a column than it can hold, you get an error like ORA-12899: value too large for column ??? (actual: 3, maximum: 2).
Using character semantics, the column length is the same as the number of characters—including multibyte characters—the column can contain. For example, a character column with a length of 2 can store two 1-byte characters, two 2-byte characters, or one of each. Oracle Applications always uses byte semantics, but Oracle Warehouse Builder supports character semantics as well.
Note:
The maximum size of Oracle character columns is 4000 bytes regardless of whether you use byte or character semantics. A character column with a length of 4000 can store 4000 bytes—for example, 4000 1-byte characters or 2000 2-byte characters—but the total number of bytes cannot exceed 4000 using either byte or character semantics.Note:
The type of semantics in effect at the time a Table instance is first installed or reinstalled during a Full Work Area installation determines the type of semantics the Table instance uses.A Table instance first installed using byte semantics (when Use Character Semantics is set to No) continues to use byte semantics even if you change the profile value to Yes and even if you reinstall the Work Area using an Upgrade installation. To apply character semantics to the Table instance you must do an installation of type Full. Full installation deletes the data in the Table instance.
Similarly, if you first install a Table instance when Use Character Semantics is set to Yes, it continues to use character semantics even if you set the profile value back to No—until you do a Full installation.
To use character semantics, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter LSH: Use Character Semantics for Workarea Installation
Click Find.
In the Site column:
Select YES to use character semantics.
Select NO to use byte semantics (the default value).
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Click the X in the upper right corner of the System Profile Values window to close the window.
You can set a profile to gather statistics on user-defined tables in a Work Area during the post-processing phase of job executions writing to tables. By default, Oracle LSH does not gather table statistics during job execution.
If you set the profile value to YES, the system gathers statistics on any user-defined table that has no statistics or stale statistics.
A table is considered to have stale statistics when it has been modified by more than 10% since statistics were last gathered. For example, if a table has 100 records and a job modifies (inserts, updates, or deletes) a total of 8 records, the system does not gather statistics during post-processing of the job. However, if the next job modifies 3 rows in the table, the cumulative number of rows modified since the last time statistics were gathered is 11, which is more than 10% of the original number of rows, and the system gathers the statistics during the post-processing phase of the second job.
To set this value, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter LSH: Gather Work Area Schema Statistics
Click Find.
In the Site column:
Select YES to gather statistics as described above
Select NO if you do not want to gather statistics as described above
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Click the X in the upper right corner of the System Profile Values window to close the window.
By default, Oracle LSH internal application tables and user-defined Work Area tables are all contained in the same 8K block size tablespace. As data grows or when there are huge data loads in progress, there is cache contention between the DMLs coming from LSH user interface and the DMLs from backend jobs, and user interface performance may be impacted.
To resolve this, create a new tablespace with a different block size and use that tablespace for all Work Area schemas and objects. Tablespaces with different block sizes do not use the same buffer cache, so the cache contention is eliminated.
For information on moving existing tables into the new tablespace, see My Oracle Support article ID 1518355.1; see "Finding Information and Patches on My Oracle Support".
To set this value, do the following:
Create a new tablespace with a 16K block size (or another size that is different from 8K).
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter LSH: Tablespace for Workarea schema objects
Click Find.
In the Site Level box, enter the name of the tablespace you created for this purpose. Be sure to use uppercase letters.
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Click the X in the upper right corner of the System Profile Values window to close the window.
Oracle LSH Program definitions have an attribute that determines how all outputs of all instances of that Program definition receive their initial validation status. You can set the default value in a profile.
If this attribute is set to Yes, outputs of Program instances are always created with a validation status of Development. If set to No, the outputs inherit the validation status of the Execution Setup that produced them, which in turn can inherit its validation status from the Program instance.
The shipped default value is No.
To change the default value, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter LSH: Force Output Validation Status to Development or some part of that string followed by the wild card: %
Click Find. The System Profiles pop-up window appears with the profile displayed.
Click in the Site column. An ellipsis (...) appears on the right-hand side of the field.
Click the ellipsis (...). A pop-up box appears.
Click Yes or No and then OK.
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Close the window.
In Oracle LSH you define Library Domains to contain object definitions, Application Areas and, if you allow Domain nesting, other Domains. See "Designing an Organizational Structure" in the Oracle Life Sciences Data Hub Implementation Guide for further information. Use the Domain Nest Value profile to determine whether Domain nesting is allowed in your implementation and, if it is, how many levels of Domain nesting are allowed:
If the domain nest value is set to 1, no nesting of Domains is allowed. Your implementation cannot have Domains contained in other Domains.
If the value is set to 2, which is the default, a top-level Domain can contain a child Domain, but the child Domain cannot contain a Domain.
If the value is set to 3, child Domains can contain Domains, but those Domains cannot contain other Domains. The maximum setting is 9.
Note:
The setting of the domain nest value profile does not affect the total number of Domains allowed, only the number of nested levels allowed. For example, if the value is set to 2, child Domains cannot contain Domains. However, parent Domains can contain any number of child Domains.To change the maximum number of nested Domains allowed in your Oracle LSH implementation from the default value of 2, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
Click in the Profile enter LSH: Domain Nesting Levels or some part of that string followed by the wild card: %
Click Find. The System Profiles pop-up window appears with the profile displayed.
In the Site column, enter any value between 1 and 9, inclusive.
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Close the window.
This profile allows you to add the SAS option DIRECT_SQL=NOWHERE to your SAS libraries. This SAS option prevents SAS WHERE clauses and PROC SQL-generated or -specified WHERE clauses from being passed to the DBMS for processing.
The default value is null, which has the same effect as a setting of NO: the DIRECT_SQL=NOWHERE is not included in your SAS libraries.
To add the option to your SAS libraries, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter LSH: Include Direct SQL option to SAS library
Click Find.
In the Site column:
Select YES to add the SAS option DIRECT_SQL=NOWHERE to your SAS libraries
Select NO if you do not want to add the option to your SAS libraries
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Click the X in the upper right corner of the System Profile Values window to close the window.
This profile allows you to set the default User Preference for SAS client across your site and stores individual users' preferences.
Oracle LSH ships with a single value for the SAS IDE Client user preference: SAS PC, which supports PC SAS for Windows. If your users need to use a different SAS client, for example, SAS EG, you can extend the lookup SAS IDE Client to display additional clients on the Life Sciences Data Hub User Preferences screen. Users can then select the client they prefer.
Note:
If you do not set a default value, users are required to set a value in the User Preferences screen in order to launch any SAS client.To set the default SAS Integrated Development Environment (IDE) Client for your site, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter LSH: SAS IDE Client
Click Find.
In the Site column:
Select SAS_PC to make PC SAS for Windows the default preference across your site.
Select a different value—one you have entered through the SAS IDE Client lookup— to make that client the default.
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Click the X in the upper right corner of the System Profile Values window to close the window.
If this profile is set to Yes, the system "freezes" existing snapshot labels and the same snapshot cannot be applied to the same Table instance more than once:
Existing snapshot labels cannot be removed.
Existing snapshot labels cannot be moved from one timestamp to another timestamp.
At runtime, if a snapshot label is specified for application to a table instance where it already exists, the job completes with a warning and the label is not applied to those tables where it already exists.
The shipped default value is No.
To change the default value, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter LSH: Freeze Snapshot Labels or some part of that string followed by the wild card: %
Click Find. The System Profiles pop-up window appears with the profile displayed.
Click in the Site column. An ellipsis (...) appears on the right-hand side of the field.
Click the ellipsis (...). A pop-up box appears.
Click Yes and then OK.
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Close the window.
Oracle recommends that you use the profile settings described in this section to provide optimal security in login password usage, including:
Setting Password Case Sensitivity (Required for BIP 10g and 11g)
Setting a Time Limit on Password Reuse after Resetting Password
A password expiration utility is available if the System Administrator requires that all users convert to case sensitive passwords upon the next login. This utility expires all passwords in FND_USER, including that of SYSADMIN and default Vision accounts, and can be run as a SQL Script ($FND_TOP/sql/AFCPEXPIRE.sql) or as a Concurrent Program (FNDCPEXPIRE_SQLPLUS).
For more information see the Oracle E-Business Suite System Administrator's Guide - Maintenance at http://docs.oracle.com/cd/E18727_01/doc.121/e12894/T202991T202995.htm.
This profile must be set to Insensitive if you are using Oracle LSH Programs of type Business Intelligence Publisher to enable users to log in to BI Publisher using their single sign-on credentials.
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter Signon Password Case
Click Find.
In the Site column, use the drop-down list to replace the default value, Sensitive, with Insensitive.
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Click the X in the upper right corner of the System Profile Values window to close the window.
Note:
Passwords for existing user accounts must be reset after you change this setting.This profile determines the minimum number of characters required in a user's Oracle LSH login password. The default setting is 5. Oracle recommends a setting of 8 or more for use with Oracle LSH.
To set the password length requirement, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter Signon Password Length
Click Find.
In the Site column, replace the default value, 5, with 8 (or a higher number, if you choose).
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Click the X in the upper right corner of the System Profile Values window to close the window.
This profile enforces requirements that make it more difficult to guess what another user's password might be. These requirements come as a package; you must either accept or reject the whole. Oracle recommends a setting of Yes (to accept the package) for use with Oracle LSH.
To set the "Hard to Guess" requirement, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter Signon Password Hard To Guess
Click Find.
Click in the Site column. An ellipsis (...) appears on the right-hand side of the field.
Click the ellipsis (...). A pop-up box appears.
Click Yes and then OK.
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Click the X in the upper right corner of the System Profile Values window to close the window.
For Oracle LSH, Oracle recommends a setting of 40 for the Local Login Mask profile. This setting displays a "Forgot your password?" link on the Login page. If the user clicks this link, the system loads a page where the user can enter his or her username.
The user then receives an email stating, "Password reset requires approval." The user needs to click one of the choices "Approve" or "Reject" that automatically generate an email response. If the user ignores the notification, the request expires in four hours.
To create the local login mask, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter Local Login Mask
Click Find.
In the Site column, replace the default value, 32, with 40.
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Click the X in the upper right corner of the System Profile Values window to close the window.
This profile option determines the maximum number of logins a user can attempt before the user's account is disabled. To reinstate the account a system administrator must unlock the account and reset the password. For example, if the value set is 3, it will lock the account if the user enters incorrect password 3 times.
To set a limit on login attempts, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter Signon Password Failure Limit
Click Find.
In the Site column, enter the limit you choose; for example: 3
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Click the X in the upper right corner of the System Profile Values window to close the window.
This profile will set the minimum number of days that a user must wait after changing his or her password before being allowed to reuse a password. The user can use the new password once and then must wait the number of days you set before he or she can reuse the password.
For example, if the value of this profile is set to 5, a user who changes his or her password cannot reuse the password until 5 days after they reset.
If the profile value is set to the number 0, then there is no restriction on password reuse.
To set a limit on login attempts, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
In the Profile field, enter Signon Password No Reuse
Click Find.
In the Site column, enter the non-negative integer you choose; for example, 5 or 0
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Click the X in the upper right corner of the System Profile Values window to close the window.
Oracle keeps an audit trail of all data changes in some of its internal metadata tables in shadow journaling tables, which helps to satisfy regulatory requirements. However, you must explicitly turn this feature on.
Instructions for changing this profile value are included in the Oracle Life Sciences Data Hub Installation Guide, so it should already be done.
To change the default value, do the following:
Log in. See "How to Log In to Oracle Applications Profile Forms".
Uncheck Site and check Application.
Click the elipses (...) in the Application field. The Applications window opens.
Enter %life% in the Find field and click Find to bring up Oracle Life Sciences Data Hub, then click OK.
In the Profile field, enter AuditTrail:Activate or some part of that string followed by the wild card: %
Click Find. The System Profiles pop-up window appears with the profile displayed.
Select Yes and then OK.
In the File menu, select Save and Proceed. The system displays a message that the transaction is complete.
Click OK. The transaction message pop-up disappears.
Close the window.
The BIP 10g endpoint profile, named LSH: BIP Endpoint, stores the namespace value of Oracle BI Publisher 10g web services:
services/PublicReportService_v11
Note:
Do not change this profile in any way. Oracle LSH uses this profile for Oracle LSH BI Publisher 10g Programs.The BIP 11g endpoint profile, named LSH: BIP11G Endpoint, stores the namespace value of Oracle BI Publisher 11g web services:
services/v2
Note:
Do not change this profile in any way. Oracle LSH uses this profile for Oracle LSH BI Publisher 11g Programs.The profile value LSH: REPORT SET INSTALL LOCK WAIT TIME is used to configure the wait time for the DB lock used in LSH Report Sets. The DB lock is acquired to serialize the concurrent Report Set Definition and Install events. Default value of the wait time is 20 seconds. Oracle recommends not changing this value.
|
 Copyright © 2006, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
