Technical information

Here and on subsequent pages we provide useful pieces of technical information to render using the connectors easier.

First, it’s important to note that, since connectors are installed on the client’s infrastructure, the client is responsible for its operation and maintenance. Thus, have in mind the minimum machine requirements needed to get a connector running.

It’s important that the machine’s time is updated so as to avoid errors when validating access tokens. The gateway creates a new token for every request made using a connector, and the connector needs to validate the token. If the machine’s time is different from the gateway’s, there may be problems when running the requests.

The minimum requirements are identified in tables on pages that are specific for a connector type. The tables also specify the connection properties for each connector, which must be informed as environment variables on the API Manager, and information regarding performance based on our tests (number of requests supported by default memory, latency, among others) so that you can scale connector usage.

these are the paged by connector type available as of now:

Also, we recommend that the client’s infrastructure and team be capable of providing load balancing and monitoring solutions.

The monitoring of hybrid environments is the responsibility of the client, and you can use the tools of your choice.

You can monitor the health of the connectors. To do so, we provide an exporter for Prometheus, which generates detailed metrics information on the application.

On the Health and Monitoring page, you can see useful technical information regarding this, including the endpoints to monitor your connector.

Finally, the page Connector Configuration lists and describes configuration options that can be modified, adapting the connector to the client’s scenario.

Deployment models

Connectors can be deployed by using Docker/Docker Compose, Kubernetes, or by running a .jar file.

Java 11 is a minimum requirement to run the .jar file.

Example using Docker Compose:

version: '3.3'
services:
  connector-aws-lambda:
    image: sensedia/connector-aws-lambda:latest # você pode alterar
    mem_limit: 200m  # você pode alterar
    ports:
      - "7090:7090"
      - "7017:7017"
    environment:
      SERVER_PORT: 7090
      JAVA_OPTS: "-Djava.security.egd=file:/dev/./urandom -XX:+UseParallelGC -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=7017"
      CONNECTOR_ID: "123" # você deverá alterar com base na informação do connector-manager
      FACTOR: "123" # você deverá alterar com base na informação do connector-manager
      ENABLE_LOG: "true"
      LEVEL_LOG: "SEVERE"

Thanks for your feedback!

EDIT

Share your suggestions with us!
Click here and then [+ Submit idea]