1.1.3 Description

The GWWS server is the Web service gateway for Tuxedo applications, the core component of SALT. The GWWS gateway server provides communication with Web service programs via SOAP 1.1/1.2 protocols and RESTful protocols. The GWWS server has bi-directional (inbound/outbound) capability. It can accept SOAP and RESTful requests from Web service applications and pass Tuxedo native calls to Tuxedo services (inbound). It also accepts Tuxedo ATMI requests and passes SOAP or RESTful calls to Web service applications (outbound). GWWS servers are used as Tuxedo system processes and are described in the *SERVERS section of the UBBCONFIG(5) file.

The CLOPT option is a string of command-line options passed to the GWWS server when it is booted. The GWWS server accepts the following CLOPT options:

-i InstanceID

Specifies the GWWS instance unique ID. It is used to distinguish multiple GWWS instances provided in the same Tuxedo domain. This value must be unique among multiple GWWS items within the UBBCONFIG file.

Note:

The InstanceID value must be pre-defined in the <WSGateway> section of the SALT Deployment File.

-a <scheme>://<host>:<port>

Web administration is disabled by default. In order to enable admin capabilities, the GWWS server must be configured in the UBBCONFIG file using the -a option as follows:

-a <scheme>://<host>:<port>.

Note:

Use the following URL to access the Web Admin Console:

<scheme>://<host>:<port>/admin

<scheme>

Can be 'http' or 'https'. If using 'https', GWWS must be configured for SSL capabilities by adding private-key and certificates in the same manner as securing application Web Services with SSL.

<host>

The name or IP address of the admin URL listening endpoint.

<port>

The port value of the admin URL listening endpoint.