Creating a psft_env.sh Script

If you are running as a non-root user, the BASE_DIR/pt/psft_env.sh script will not be available if you run the DPK setup script using one of the deploy_only options. For example:

  • psft-dpk-setup.sh --env_type midtier --deploy_only

  • psft-dpk-setup.sh --env_type midtier --deploy_only --deploy_type tools_home

  • psft-dpk-setup.sh --env_type midtier --deploy_only --deploy_type app_home

  • psft-dpk-setup.sh --env_type midtier --deploy_only --deploy_type app_and_tools_home

In this case, the BASE_DIR/pt/psft_env.sh file is not installed automatically. You must create and run the script to set the required environment variables.

Use the following as a template, and make the necessary modifications for your environment.

In this example, <BASE_DIR> refers to the DPK deployment location, and <psftsuser> is the non-root user. 

# User specific aliases and functions
export _JAVA_OPTIONS=-Djava.security.egd=file:/dev/./urandom


export TNS_ADMIN=<BASE_DIR>/db
export ORACLE_HOME=<BASE_DIR>/pt/oracle-client/19.3.0.0
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH
export PATH=.:$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$ORACLE_HOME/perl/bin:$PATH

TUXDIR=<BASE_DIR>/pt/bea/tuxedo
if [ -d $TUXDIR ]; then
  export TUXDIR=$TUXDIR/tuxedo22.1.0.0
  export PATH=$TUXDIR/bin:$PATH
  export LD_LIBRARY_PATH=$TUXDIR/bin:$TUXDIR/lib:$LD_LIBRARY_PATH
fi

export PATH=<BASE_DIR>/pt/ps_home8.63.04/appserv: <BASE_DIR>/pt/ps_home8.63.04/setup:$PATH

export LANG=C
if [ -d <BASE_DIR>/pt/ps_home8.63.04 ]; then
CWD=$PWD
cd <BASE_DIR>/pt/ps_home8.63.04 && . psconfig.sh
cd $CWD
fi
export PS_CFG_HOME=/home/<psftuser>/pscfg_pt863_lnx

Save the file as psft_env.sh in BASE_DIR/pt, and source it to set the environment variables. For example, use this command: 

source BASE_DIR/pt/psft_env.sh