
See Section 4.1.7.1, "Complete the Setup of the opapps Account".

See the Oracle Clinical Administrator's Guide for information.Ĭreate an opapps account in the same way you did on database server with default shell C Shell. 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. home/opapps/bin/sas -log $LOGNAME $3 $4 $5 $6 "

Path_to_sas_script_on_SAS_server is the sas file created in the OPA_BIN directory on the SAS server Server_name is the SAS server connected through ssh SASDIR is the directory RXC_SAS_VIEW where SAS view is created and folder is NFS mounted comes as inputįILENAME is the SAS log file name comes as input RXC_LOG1 is the path of the log directory in the SAS server Path_to_sas_script_on_SAS_server -log $LOGNAME $3 $4 $5 $6 " Ssh server_name /bin/sh -c ".profile setenv This creates the sas_proxy_password_encoded_file which stores the encrypted password of the sas_proxy_user db user (where pwd.sas is the name of the temporary file you created):Ĭreate 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:Ĭreate the shell script on the Oracle Clinical database server in a publicly visible directory, such as opapps/bin. Run the file created in Step 4 to encrypt the file. Proc pwencode in=' password' out=pwfile method=sas002 Log in to the PSUB server as RXC_SAS_VIEW owner and set the environment:Ĭreate a temporary SAS file named pwd.sas to contain the password for the sas_proxy_user account:įilename pwfile 'sas_proxy_password_encoded_file' Run the script ocl_grant_revoke_sas_proxy_user.sql in the install directory to grant or revoke user connections through proxy account sas_proxy_user Grant proxy connection for each database user account who needs to submit SAS Data Extract jobs:Īlter user grant connection through sas_proxy_user Log in to the database as system user and create the sas_proxy_user database account:Ĭreate user sas_proxy_user identified by

Manually set SAS_ENCRYPTION as the SAS_CONNECTION long value in the OCL_STATE local reference codelist.
