Advice on additional setup options and basic troubleshooting in OpenText AppWorks Gateway.
The AppWorks Gateway provides information in the gateway.log file, which is
located in the
<Tomcat_Home>\logs directory. The log level for the AppWorks
Gateway is set via a
log4j properties file in the
To set the log level to a higher level, for example, debug, take the following steps:
Stop the Apache Tomcat service.
log4j properties file in the
Change the log level to debug.
Start the Apache Tomcat service.
Note: Once you have completed any troubleshooting tasks, return the log level to its lower level to prevent excessive log file creation.
The AppWorks Gateway provides information in the gateway.log file, which is located in the
<Tomcat_Home>\logs directory. Set the log level to a higher level, as described above.
The AppWorks Gateway proxy also logs information in the gateway.log file when the log level is set to debug.
Information is also available in the default Catalina logs such as catalina
For debugging, first check the Catalina log for errors, and if necessary check the localhost-access_logs.
Commonly reported issues revolve around OpenText Directory Services (OTDS) configuration. On the initial AppWorks Gateway configuration, there is a chance that the OTDS configuration will fail either due to port conflicts, memory issues, resource conflicts with existing OTDS data, or failure to communicate with an external OTDS due to firewall blocking requests or mistyped configuration information. The Catalina logs will show exceptions in the OTDS configuration. For more information, review the OTDS logs which can provide additional information. These logs can be found in the
used to host your OTDS installation. The OTDS log files are also available in the OTDS Web Client. Errors relating to port conflicts and resource name conflicts will be clearly indicated in the logs. Other error cases may require further investigation. Beyond initial configuration of the AppWorks Gateway, there are very few error scenarios that would be indicated in the logs. The primary issue that can occur relates to authentication errors. If the user has entered a correct password, but cannot authenticate, these issues will not be captured in the log files. The following steps are recommended to troubleshoot authentication errors.
Review the AppWorks Gateway node information to verify the database and OTDS connections. Sign into the AppWorks Gateway and click Overview in the left pane.
Double check that the credentials and server URL were typed correctly. This isoften the problem.
Try connecting using a different client.
Try using the fully qualified name. For example
<username>@otag for internally created users,
<username>@<domain> for OTDS synced users.
Log in to the OTDS Web client and check that the user’s account hasn’t expired or been locked.
Add a new user in the AppWorks Gateway. Then, sign in to OTDS Web client and verify that the new user was added to the otag partition.
The AppWorks Gateway provides information in the
gateway.log file which is located in the
<Tomcat_Home>\logs directory. Your feature might also have a service log that is also located in this directory.
The Deployments page in the AppWorks Gateway provides information on the deployment status of your features. From this page, you can also redeploy or refresh the feature if the original deployment runs into issues.
In AppWorks Gateway 16.1 and above the Gateway is capable of making external HTTP calls via an HTTP forward proxy, using JAVA_OPTS.
A good example of this is for the routing of Google Cloud Messaging (GCM) communications when the environment within which AppWorks is installed only permits outbound HTTP communication to the public Internet via an HTTP proxy.
The example settings shown below are from a Linux installation of AppWorks Gateway.
Stop the Apache Tomcat service.
setenv.sh script in a text editor.
Add the following values and edit the hostnames and ports to match your environment.
export CATALINA_OPTS="$CATALINA_OPTS -Dhttp.proxySet=true"
export CATALINA_OPTS="$CATALINA_OPTS -Dhttp.proxyHost=proxysyd.cloud.yourserver.com"
export CATALINA_OPTS="$CATALINA_OPTS -Dhttp.proxyPort=80"
export CATALINA_OPTS="$CATALINA_OPTS -Dhttps.proxyHost=proxysyd.cloud.yourserver.com"
export CATALINA_OPTS="$CATALINA_OPTS -Dhttps.proxyPort=80"
export CATALINA_OPTS="$CATALINA_OPTS -Dhttp.nonProxyHosts=\"localhost|127.*|syd-awgw-p01|syd-awgw-p01.appworks.cloud.yourserver.com|syd-awdba-p01.appworks.cloud.yourserver.com\""
Dhttp.proxyHost is the address of the HTTP Proxy Server
Dhttp.proxyPort is the HTTP listening port for the HTTP Proxy
Dhttps.proxyPort is the HTTPS listening port for the HTTP Proxy
Dhttp.nonProxyHosts contains the short name and FQDN of the AppWorks Server
syd-awdba-p01.appworks.cloud.yourserver.com is the OTDS Server used by AppWorks
We must NOT proxy requests via the HTTP Forward Proxy to:
setenv.sh file and start the Apache Tomcat service.
Tip: Select the Active Push Notification Logging check box in the Notifications section of the AppWorks Gateway, and then check the
gcm.logto confirm that GCM messages are being sent correctly.
Tip: Use cURL, via a terminal session. to check the server host itself can connect to GCM via the HTTP Forward proxy. This should return an HTTP 200 response (adjust the proxy address and port to match your environment)
curl -v -I -x proxysyd. cloud.yourserver.com:80 https://gcm-http.googleapis.com
Previous OpenText AppWorks Gateway Online Help versions
This article has been updated to note that the AppWorks Gateway proxy also logs information in the gateway.log file when the log level is set to debug. The same updates are available in the PDF version of the AppWorks Gateway Installation and Administration Guide, labelled as version 2, and available from the Getting Started page, the Software Downloads page, and from the Release Notes for 16.2.1 page.
You need to sign in before voting.