Install SAS on a UNIX Computer
In this section:
- Modify SAS 9.4 and opa_settings on UNIX
- Install SAS on the Same UNIX Computer as Oracle Clinical
- Install SAS on a Different UNIX Computer from Oracle Clinical
Parent topic: Set Up SAS
Modify SAS 9.4 and opa_settings on UNIX
Oracle Clinical supports SAS 9.4. You can validate your Oracle Clinical installation, and then upgrade to SAS 9.4 later. The SAS/ACCESS Interface to Oracle requires Oracle SQL*NET on the computer with the SAS software installation.
Follow these instructions on the SAS server—whether SAS is on the same computer or a different one from Oracle Clinical. See:
Parent topic: Install SAS on a UNIX Computer
Prepare the SAS Template File
Make the following modifications to the SAS template file:
Parent topic: Modify SAS 9.4 and opa_settings on UNIX
Install SAS on the Same UNIX Computer as Oracle Clinical
Oracle recommends installing SAS on the same server computer as the Oracle Clinical database server installation, following instructions in this section:
Set REMOTE_OS_AUTHENT to FALSE
See Set Initialization Parameters for more information.
Parent topic: Install SAS on the Same UNIX Computer as Oracle Clinical
Set Up a SAS Connection
You can set up a SAS connection to the Oracle database in two ways—using Oracle Wallet or SAS encryption. The Oracle Clinical Installer sets the SAS_CONNECTION value in the OCL_STATE reference codelist to ORACLE_WALLET.
Oracle Wallet
This is the default option. The SAS connection is set up automatically.
SAS Encryption
Manually set SAS_ENCRYPTION as the SAS_CONNECTION long value in the OCL_STATE local reference codelist. In addition:
Parent topic: Install SAS on the Same UNIX Computer as Oracle Clinical
Install SAS on a Different UNIX Computer from Oracle Clinical
Oracle recommends installing SAS on the same UNIX server computer as the Oracle Clinical database server installation.
If you choose to install SAS on a UNIX server computer different from that of the Oracle Clinical database server installation, it must be on the same intranet and you need to set up a connection to SAS.
For more information, see:
- Establish the Connection to SAS on a Different Computer
- Set Up SAS Security on a Different Computer
- Configure Private and Public Keys for Using SSH with SAS
Parent topic: Install SAS on a UNIX Computer
Establish the Connection to SAS on a Different Computer
To set up SAS on a different UNIX server computer:
Note:
The following procedure uses secure shell (ssh) to establish the connection to SAS.NFS
- Use Network File System (NFS) protocol to make the directory on the Oracle Clinical server pointed to by the $RXC_USER /sas_view visible to the SAS server.
- Export this directory with write privileges because the SAS scripts generated by Oracle Clinical produce SAS view descriptors that are created in this directory tree.
Note:
By default the $RXC_USER environment variable is the opapps home directory.Create opapps on the SAS Server
- Create the opapps UNIX user account on the SAS server.
- Create a group for opapps and put it in the group.
- Link
/etc/group
with/etc/logingroup
on the SAS server if it is not the primary group for opapps.
Check init.ora
- Open the init.ora file.
- Verify that the REMOTE_OS_AUTHENT initialization parameter is set to FALSE for the Oracle Clinical database instance in the init.ora file:
REMOTE_OS_AUTHENT=FALSE
See Set Initialization Parameters for more information.
Create a Shell Script
Create a shell script that forces a "SAS" invocation on the Oracle Clinical database server to run as a remote shell on the SAS server that invokes the SAS engine, passing it the name of the SAS file:
Set Up SAS Security on a Different Computer
You can set up a SAS connection to the Oracle database in two ways—using Oracle Wallet or SAS encryption. The Oracle Clinical Installer sets the SAS_CONNECTION value in the OCL_STATE reference codelist to ORACLE_WALLET.
Oracle Wallet
This is the default option. You do not need to change the OCL_STATE reference codelist SAS_CONNECTION value, but you must enter the SAS server as the REMOTE_SAS_SERV value in OCL_STATE. See the Oracle Clinical Administrator's Guide for information.
And, on the SAS server:
- Create an opapps account in the same way you did on database server with default shell C Shell. See Complete the Setup of the opapps Account.
- Log on as opapps.
- Set the environment variables in .cshrc so you can connect to the database using SQL*Plus.
- Set up the Oracle Wallet on the SAS server. You may use the same Wallet password
that you used during Oracle Clinical installation
or a different
one:
mkstore -wrl wallet_location -create -nologo
Example wallet location: /pharm/home/opapps/wallet
- Enter your password, then enter it again.
- Add OCPSUB credentials:
mkstore -wrl wallet_location -createCredential db_connect_string OCPSUB
- Enter information as follows at the prompts:
- Enter your secret password: Enter the OCPSUB password.
- Re-enter your secret password: Re-enter the OCPSUB password.
- Enter wallet password: Enter the Wallet password created above.
- Create sqlnet.ora in opapps home. Specify the Wallet path. For
example:
WALLET_LOCATION=(SOURCE =(METHOD = FILE)(METHOD_DATA =(DIRECTORY = /pharm/home/opapps/wallet)))SQLNET.WALLET_OVERRIDE = TRUE
where
/pharm/home/opapps/wallet
is the wallet path - In the opapps home, add the following in .cshrc:
setenv TNS_ADMIN $HOME
- Test the Wallet connection:
- Open another telnet/putty session of SAS server and log in as opapps.
- Try connecting. It should not require specifying a password.
sqlplus /@db_connect_string sql> show user
You should see the OCPSUB user.
SAS Encryption
To set up a SAS connection using SAS encryption, follow instructions in Set Up a SAS Connection.
Configure Private and Public Keys for Using SSH with SAS
If you are installing SAS on a different server on an intranet, do the following to establish an SSH connection from the PSUB server to the SAS server.
Oracle Clinical DB Server
Perform the following tasks on the Oracle Clinical UNIX database server computer:
- Log in to the Oracle Clinical UNIX database server computer as the opapps user.
- Use ssh-keygen to create a password-less set of identity keys:
ssh-keygen -t rsa -N ''
The system prompts for the file into which you want to save the set of identity keys.
- Press Return to accept the default location. This process creates two files in the user's home directory:
- ~/.ssh/id_rsa This file contains the private key that represents your identity on that particular machine. Note that the private key is neither world nor group readable. You should never transfer the private key from the machine or change its modes.
- ~/.ssh/id_rsa.pub This file contains the public key, which is world readable. The ssh program and other programs can use the public key to encrypt messages that only you can decrypt using the private key. The -N ' ' argument to the ssh-keygen command specifies that no passwords are associated with the public keys.
- Transport the file id_rsa.pub to a location on the SAS Server (for example, /tmp) using a secure method as defined by the policies of your organization.
SAS Server
Perform the following tasks on the SAS Server computer:
- Log in to the SAS Server computer as opapps.
- In the home directory Create the .ssh directory if it does not exist, and set the permission to 700:
mkdir .ssh chmod 700 .ssh cd ~/.ssh
- Append the contents of the id_rsa.pub file in the /tmp directory to the authorized_keys file in the GUEST1_HOME/.ssh directory. For example:
cat /tmp/id_rsa.pub >> authorized_keys
- Change the permission of the authorized_keys file to 600:
chmod 600 authorized_keys
Verify SSH
To test the ssh setup from the Oracle Clinical Database server: