Authenticating the SAS Connection

When you run a SAS Data Extract job, you actually run two jobs—in the first job Oracle Clinical creates a SAS file, and in the second job SAS creates a SAS view from the file created in first job.

Note:

For command line execution of the SAS file, the user must log in as opapps.

In the first job, Oracle Clinical generates a connect string based on the specified authentication method to be used when the SAS file is executed.

There are two authentication methods and at any point in time, all DX jobs and SAS files must use the same option. You must enter the SAS_CONNECTION value in the OCL_STATE local reference code list: either ORACLE_WALLET or SAS_ENCRYPTION. The default value is ORACLE_WALLET.

Note:

Plan to continue to use a single option consistently. Each time you change from one to the other you must regenerate all files generated using the other option so users can view them. Also, at any point in time, all SAS jobs must use the same option.

For more information , see:

• Using Oracle Wallet for SAS Authentication
  
• Using SAS Encryption for SAS Authentication
  

Using Oracle Wallet for SAS Authentication

This is the default option. The connect string generated for Oracle Wallet is:

connect to oracle(user='oc_end_user 'password=''path='dbname');

Although the individual user ID is specified in the file, the connection is actually made with this account's grant to the ocpsub proxy account, which is stored in the Wallet.

• If your SAS server is the same as the database server, and you set ORACLE_WALLET as the authentication method, the SAS connection is set up automatically—opapps retrieves the OCPSUB database password from the opapps wallet

• If your SAS server is on a different machine from the database and you want to use ORACLE_WALLET, you must first set up the Oracle Wallet on the SAS server, as described in the Oracle Clinical Installation Guide.

Using SAS Encryption for SAS Authentication

The connect string for the SAS encryption method is:

connect to oracle(user='SAS_PROXY_USER oc_end_user 'pw="&dbpass" path='dbname');

To set up a SAS connection using SAS encryption, see the SAS chapter in the Oracle Clinical Installation Guide.