Hostnames and URLs for APPSeCONNECT

Hostnames and URLs for APPSeCONNECT

APPSeCONNECT requires a number of URLs that will enable seamless communication between agents and our cloud portal. This document will help you to list all the URLs and ports required to be exempted for unrestricted access such that the Agents could communicate correctly with the cloud services.

Destination URL Purpose
The Platform https://portal.appseconnect.com The main portal is where the integration developer does every configuration.  iPaaS Platform.
The API https://admin.appseconnect.com The API stack is used to download User info and custom metadata.
Storage https://appsdrive.blob.core.windows.net/ Represents configuration store, where most of the configuration created in Platform is stored.
Storage https://appsdatalake.blob.core.windows.net/ Represents transactional store, where all metadata related to sync is uploaded.
Service Bus https://aec-prod.servicebus.windows.net  In Memory event hub, which tracks any important event raised on the agent. It also uses sb:\\ protocol to communicate
Service Bus https://appseconnect.servicebus.windows.net Hook for Service bus, required to execute real-time proxies. Service Bus represents a brokered service communication architecture. It also uses sb:\\  protocol to communicate
SignalR Server https://services.appseconnect.com  Represents the real-time communication channel for web sockets. The Agent connects to the socket using wss:\\ protocol to the service.
Document Database https://aecprod.documents.azure.com/  APPSeCONNECT document database, which is used by the new ProcessFlow engine.
Realtime Proxy URL https://(subdomain).appseconnectapi.com/ The real-time communication channel is created to post messages to the agent in real-time. This URL needs to be configured on the application webhook such that the data could be passed in the URL. The subdomain here is configured by the customer.

Integrate-Business-Apps-through-APPSeCONNECT

Real-Time Touchpoints

It is highly recommended to use Proxy to configure real-time configurations, but if you still require to communicate using a local server’s public IP, you need to exempt 80 ports of that machine, such that the local port could be correctly opened. The port and the URL could be configured in settings of the APPSeCONNECT agent or from Portal.

For proxy or API management, the URL will be in *.appseconnectapi.com format. The * is the subdomain chosen by the customer

Ports For Exemption

In addition to these URLs, we also need local ports to be opened as follows:

  1. APPSeCONNECT Agent opens a listener at Port: 59050
  2. APPSeCONNECT Service opens a listener at Port: 59051

These ports need to be exempted from the firewall such that the Inter-process communication between the service and the local agent application could be made.

All communications are through HTTPS (256 BIT Encrypted) only.

Thank you!

Integrate-Business-Apps-through-APPSeCONNECT

APPSeCONNECT is a smart and robust business application integration platform that seamlessly connects all your business applications with each other to streamline operations and facilitate the free flow of data across the platforms. By moving into the region of iPaaS, APPSeCONNECT proves to be a best-in-the-class platform that easily connects systems and automates the business process.

Now, you can easily connect all your business applications under one single platform to automate the business process and increase your productivity and efficiency!

Search

Our integrations are dynamic in nature. The mentioned offerings are the cumulative possibilities of the platform (actual scenarios are specifically organization/business-dependent). For any disparity, please refer to the latest version of the integration brochures.