SecureTransport specific named variable sets

Named variable sets separate variables into logical groups. Named variable sets use the following syntax:

${name['variable']}

or

${name.variable}

SecureTransport uses the following named variable sets:

  • ${sess['variable']} – used with SecureTransport session variables including LDAP
  • ${env['variable']}, ${stenv['variable']}, or ${stenv.variable} – used with SecureTransport predefined environment variables
  • ${pesit['variable']} – used with SecureTransport PeSIT variables described in PeSIT variables

LDAP session variables can be used with the sess named variable set. You can also develop an agent that contains the session variables you want to use. All session variables must be prefixed with STSESSION_.

The env named variable set contains the entire environment, including any non- SecureTransport-specific variables. Environment variables accessed using stenv are preprocessed to remove the DXAGENT_ prefix, and upper case characters are converted to lower case characters. For example, to use the environment variable DXAGENT_TARGET, write the following expression:

${env['DXAGENT_TARGET']}

or use the stenv named variable set and access the variable as:

${stenv['target']} or ${stenv.target}

SecureTransport-specific named variable set examples

The following table shows examples of SecureTransport-specific named variables:

Example Example return value
${sess['STSESSION_LDAP_DIR_homeDirectory']} /home/user1
${sess['STSESSION_LDAP_DN']} cn=john,ou=People,dc=tp,dc=axway,dc=com
${sess['STSESSION_LDAP_DIR_uidNumber']} 1000
${env['DXAGENT_HOMEDIR']} /home/user2
${stenv['homedir']} /home/user2
${env['DXAGENT_FULLSOURCE']} /st/monitor/download/test.xml
${stenv['fullsource']} /st/monitor/download/test.xml
${stenv.rawsource} AS2OriginalFile
${stenv.site_target} OriginalFile

Related Links