Edge Runtime

The following errors are observed.

Error Solution
docker: Error response from daemon: driver failed programming external connectivity on endpoint EdgeServer11 (afc5df00b5502d0a004ad015a883b7f4c3c15d790f05a43a3603ced834c9d949): Bind for 0.0.0.0:5554 failed: port is already allocated. This error appears because the port number (for example, 5554 in the error message) specified in the command is already in use by another service or application. Provide a port number that is not in use and rerun the command.
docker: Error response from daemon: Conflict. The container name "/EdgeServer11" is already in use by container "f5c1b38b8c2e21580daecbec6ec9d31535a1d1a772305fed9258f2779e5b09f5". Remove (or rename) that container to be able to reuse that name. This error appears because there is an edge runtime that is registered with the same name. Use a unique name and register the edge runtime. If you want to use the same name for the edge runtime, delete the client registration details from the OAuth 2.0 page and reuse the name to register the new edge runtime. You must have administrative privileges to delete the client registration details.
The edge runtime <EDGE_Runtime_NAME> is unavailable. This error can appear because of one of the following scenarios:
  • You are trying to run a deploy anywhere flow service with the edge runtime whose token has expired, or whose client registration details do not exist.
  • The edge runtime has stopped abruptly.
  • The edge runtime is not reachable due to network connectivity issues.

Delete OAuth tokens associated with an edge runtime

Do not delete any of the OAuth tokens that are associated with the edge runtime. If you delete the OAuth token, then the error message The Edge Server is unavailable appears and you cannot run the integrations by using the affected edge runtime.

Register an edge runtime by using an expired token

You cannot use expired tokens to register an edge runtime. Always register an edge runtime with a valid token.

Use the name of an edge runtime that has been unregistered when registering a new edge runtime

You can create an edge runtime by using the same name of an unregistered edge runtime.

Note: Though the registration does not happen, the runtime is setup in the container. Therefore, if you want to use the same name to register an edge runtime by using a valid token, first delete the client registration details from the OAuth 2.0 page.

Restart an edge runtime that is stopped

You cannot restart edge run times that are stopped.

Who can view and access existing edge runtime nodes?

Currently, you must be an administrator to get access to the control plane.

Define what edge run times can a developer view and use in their projects

Currently developers can select any edge runtime in the given tenant.

What happens if the connection between the edge runtime and the Cloud is not available? Which functions are still available? What functionality is lost?

Cloud runtime functions. The edge runtime does not function due to network interruption, which may be the infrastructure or the user's internet issues. The edge runtime resumes functioning after the connection is restored.

What components are available with Integration Runtimes in the Edge only?

Components (deploy anywhere flow services, packages that are imported through Git to the project) that get deployed to your edge runtime are available.

Share code and definitions between Cloud and Edge

Within a project, you can share code and definitions.

What kind of adapter notifications, SOAP, REST endpoints are possible?

Not supported.

How to maintain users, accounts, ACLs for the Edge connections?

Not supported.

Will the user data be synchronized?

Not supported.