The pdadmin server task create command

WebSEAL supports both standard non-secure TCP (HTTP) and secure SSL (HTTPS) junctions between WebSEAL and back-end Web application servers. The junction between WebSEAL and the back-end server is independent of the type of connection (and its level of security) between the client (browser) and the WebSEAL server.

Mandatory command options...

Host name of the back-end application server	-h option
Junction type: tcp, ssl, tcpproxy, sslproxy, local	-t option
Junction point	mount point

Command syntax:

pdadmin> server task instance_name-webseald-host-name create -t type -h host_name jct_point

For example:

pdadmin> server task web1-webseald-cruz create -t tcp -h doc.ibm.com /pubs

Always use the fully qualified domain name of the back-end server when specifying the argument to the -h option.

WebSEAL also supports HTTP/2 connections. To create an HTTP/2 junction, use the -o option. The following parameters are available:

h2

Enable HTTP/2 protocol to junction server.

pch2c

Enable HTTP/2 protocol to proxy server.

sni=<hostname>

Send the string <hostname> in the SSL/TLS handshake as the Server Name Indicator(SNI) value.

Parent topic: Standard WebSEAL junction configuration