Background

The API Gateway database contains a large number of configuration directives that are used to specify how the Gateway operates. This includes published services, the policy documents for those services, or any dependency documents such as a WSDL or XSD. If dependencies cannot be fully resolved at initialization time then the API Gateway application may fail to initialize. This document will prescribe the steps necessary to get the Gateway application to start in order to correct any discrepancies in the dependencies that may occur.

Presentation

The API Gateway will appear to start normally but will halt all logging after either one or both the following logs are recored:

com.l7tech.server.service.ServiceMetricsServicesImpl: Database flusher beginning

com.l7tech.server.service.ServiceMetricsServicesImpl: Using default value (31536000000) for missing system property: com.l7tech.service.metrics.maxDailyAge

The API Gateway will not be accessible through any of the defined listen ports and none of those ports will be active or listening.

Resolution

A system configuration property can be set to adjust the behavior of the Gateway with respect to how certain dependencies are resolved or mapped. The following procedure will describe that process:

1. Log into the API Gateway node  as the ssgconfig user
2. Select Option #3: Use a privileged shell (root)
3. Open the system configuration file in a text editor: /opt/SecureSpan/Gateway/node/default/etc/conf/system.properties
4. Append the following line: com.l7tech.service.wsdlimportfix.enabled=false
5. Save the file and exit the editor
6. Restart the API Gateway appliance
7. Repeat the procedure on each Gateway node in the cluster.