If the GWWS server fails to start, check the following:

• Oracle Tuxedo service contract configuration
  • Check if the Oracle Tuxedo service contract definition is correct in the Oracle Tuxedo Service Metadata Repository.
  • Check if the Oracle Tuxedo Service Metadata Repository Server - TMMETADATA - is booted successfully.
• GWWS server license

  The GWWS server requires an extra license from Oracle to enable functionality. Check to make sure it has been installed properly.

• GWWS server HTTP listen port configuration.

  Check the GWWS server listen /WS-Addressing endpoints defined in the SALT configuration files. Avoid port conflicts with other applications.

• GWWS instance ID

  Check the GWWS instance ID to make sure the two names defined in UBBCONFIG and SALTDEPLOY file are consistent.

• UBBCONFIG file MAXWSCLIENTS definition.

  Make sure that MAXWSCLIENTS is defined in the UBBCONFIG file *MACHINE section on the computer where the GWWS server is deployed.

• RESTART=Y and REPLYQ=Y parameters

  If the GWWS server is set to RESTART=Y in the UBBCONFIG file, REPLYQ=Y must also be defined.

• SALTCONFIG file

  Make sure the binary version SALTCONFIG file is compiled successfully and the environment variable SALTCONFIG is set correctly for the GWWS server.