3 Setting Profile Values
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.
This chapter contains the following topics:
- How to Log In to Oracle Applications Profile Forms
This is the login procedure for Oracle Applications Profile Forms - Setting Native Client Encoding
The value for this profile determines the encoding used when uploading and downloading files from the client. - Using Character Semantics for Work Area Table Installation
If your data includes multibyte unicode characters, your data may sometimes not fit into character columns in the Oracle Life Sciences Data Hub Table instances you create because you are using byte semantics (which is the default behavior). - Gathering Work Area Schema Statistics
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. - Creating a New Tablespace for Work Area Schema Objects
By default, Oracle Life Sciences Data Hub internal application tables and user-defined Work Area tables are all contained in the same 8K block size tablespace. - Setting the Default Value for: Force Output Validation Status to Development
Oracle Life Sciences Data Hub 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. - Setting the Maximum Number of Nested Domains
In Oracle Life Sciences Data Hub you define Library Domains to contain object definitions, Application Areas and, if you allow Domain nesting, other Domains. - Adding the Direct SQL Option to SAS Libraries
his profile allows you to add the SAS option DIRECT_SQL=NOWHERE to your SAS libraries. - Allowing User Preferences for SAS Clients
This profile allows you to set the default User Preference for SAS client across your site and stores individual users' preferences. - Set Default SAS Number Format
The default value in Oracle Life Sciences Data Hub for SAS number format is 8, which does not support precision. - Set Processing Type for OC Data Extract Incremental Adapter
This profile allows you to set the default processing type for the incremental Oracle Clinical data extract adapter, which uses incremental-mode processing and is therefore faster than the regular OC data extract adapter, which uses full-mode processing. You can specify transactional processing with or without audit. - Turn debugging on or off
Enable or disable the recording of debugging statements for database processes. - Setting Password Requirements
A password expiration utility is available if the System Administrator requires that all users convert to case sensitive passwords upon the next login. - Oracle LSH: BIP Endpoint
This profile stores the namespace value of Oracle BI Publisher webservices: - Attachment File Upload Restriction Default
This profile allows more file types to be uploaded than are allowed under E-Business Suite recommended security settings.
How to Log In to Oracle Applications Profile Forms
This is the login procedure for Oracle Applications Profile Forms
Parent topic: Setting Profile Values
Setting Native Client Encoding
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 Life Sciences Data Hub 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.
Parent topic: Setting Profile Values
Using Character Semantics for Work Area Table Installation
If your data includes multibyte unicode characters, your data may sometimes not fit into character columns in the Oracle Life Sciences Data Hub 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:
- This profile setting does not take effect until you edit the Oracle Warehouse Builder Runtime.properties file as described in the Oracle Life Sciences Data Hub Installation Guide in the OWB section of the chapter on installing Oracle LSH itself.
- 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.
- 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:
Parent topic: Setting Profile Values
Gathering Work Area Schema Statistics
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 Life Sciences Data Hub 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:
Parent topic: Setting Profile Values
Creating a New Tablespace for Work Area Schema Objects
By default, Oracle Life Sciences Data Hub 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.
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.
Parent topic: Setting Profile Values
Setting the Default Value for: Force Output Validation Status to Development
Oracle Life Sciences Data Hub 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.
In a Program definition, if this attribute is set to Yes, outputs of instances of the Program definition 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.
Parent topic: Setting Profile Values
Setting the Maximum Number of Nested Domains
In Oracle Life Sciences Data Hub 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.
Parent topic: Setting Profile Values
Adding the Direct SQL Option to SAS Libraries
his profile allows you to add the SAS option DIRECT_SQL=NOWHERE to your SAS libraries.
TThis 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:
Parent topic: Setting Profile Values
Allowing User Preferences for SAS Clients
This profile allows you to set the default User Preference for SAS client across your site and stores individual users' preferences.
Oracle Life Sciences Data Hub 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:
Parent topic: Setting Profile Values
Set Default SAS Number Format
The default value in Oracle Life Sciences Data Hub for SAS number format is 8, which does not support precision.
To change the default value to BEST, change the value of this profile to Yes.
- Log in. See How to Log In to Oracle Applications Profile Forms.
- In the Profile field, enter
LSH: Default SAS Number Format BEST
. - Click Find.
- In the Site column:
- Select
No
to make the default SAS number format value equal to 8. This is the default value. - Select
Yes
to make the default SAS number format value equal to BEST, which supports precision in numbers and is the best value if you load files that do not have a SAS number format specified.Note:
If you change this setting, running any existing Load Sets having target Table instances with Number columns that have the old default value of 8 will end with a warning if you load files that do not have a SAS number format specified. This is because the metadata comparison will show a difference between the source and target.
- Select
- 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.
Parent topic: Setting Profile Values
Set Processing Type for OC Data Extract Incremental Adapter
This profile allows you to set the default processing type for the incremental Oracle Clinical data extract adapter, which uses incremental-mode processing and is therefore faster than the regular OC data extract adapter, which uses full-mode processing. You can specify transactional processing with or without audit.
Parent topic: Setting Profile Values
Turn debugging on or off
Enable or disable the recording of debugging statements for database processes.
The setting applies to all users. The system reads the value of the profile once per user session, so you may need to restart the application tier for a changed setting to take effect.
Parent topic: Setting Profile Values
Setting Password Requirements
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.
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 Business Intelligence Publisher)
This profile must be set to Insensitive if you are using Oracle Life Sciences Data Hub Programs of type Business Intelligence Publisher to enable users to log in to BI Publisher using their single sign-on credentials. - Setting Password Length Requirement
This profile determines the minimum number of characters required in a user's Oracle Life Sciences Data Hub login password. - Setting "Hard to Guess" Requirement
This profile enforces requirements that make it more difficult to guess what another user's password might be. - Enabling "Forgot Your Password?" Functionality
For Oracle Life Sciences Data Hub, Oracle recommends a setting of 40 for the Local Login Mask profile. - Setting a Limit on Log-In Attempts
This profile option determines the maximum number of logins a user can attempt before the user's account is disabled. - Setting a Time Limit on Password Reuse after Resetting Password
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.
Parent topic: Setting Profile Values
Setting Password Case Sensitivity (Required for Business Intelligence Publisher)
This profile must be set to Insensitive if you are using Oracle Life Sciences Data Hub 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.Parent topic: Setting Password Requirements
Setting Password Length Requirement
This profile determines the minimum number of characters required in a user's Oracle Life Sciences Data Hub 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.
Parent topic: Setting Password Requirements
Setting "Hard to Guess" Requirement
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 Life Sciences Data Hub.
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.
Parent topic: Setting Password Requirements
Enabling "Forgot Your Password?" Functionality
For Oracle Life Sciences Data Hub, 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.
Parent topic: Setting Password Requirements
Setting a Limit on Log-In Attempts
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 is set to 3, it locks the account if the user enters incorrect password three 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.
Parent topic: Setting Password Requirements
Setting a Time Limit on Password Reuse after Resetting Password
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 five 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
or0
- 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.
Parent topic: Setting Password Requirements
Oracle LSH: BIP Endpoint
This profile stores the namespace value of Oracle BI Publisher webservices:
services/PublicReportService_v11
Note:
Do not change this profile in any way. Oracle Life Sciences Data Hub uses this profile for Oracle LSH BI Publisher Programs.Parent topic: Setting Profile Values
Attachment File Upload Restriction Default
This profile allows more file types to be uploaded than are allowed under E-Business Suite recommended security settings.
Changing the setting is required to support submitting Load Sets and creating Table Descriptors from some types of files, including sasb7dat files.
Parent topic: Setting Profile Values