Firewall Friendly IPs

Know more about the allowed IPs and the ports to open for cloud connectivity.

Allowed IP Addresses

webMethods.io Integration connects with most third-party services easily and instantly. However, in some cases you may need to connect to your servers from specific IP addresses and access resources that lie behind a protective firewall. This can be achieved in webMethods.io Integration. We provide a set of static IP addresses that you need to allow in your firewall. This allows webMethods.io Integration to make connections to your servers (in order to SSH or to access services like MySQL) and run the integrations successfully.

Software AG Cloud products are available in several geographical regions, operated by different infrastructure providers. Currently, webMethods.io Integration is available on Amazon Web Services (AWS) and Microsoft Azure. Based on the infrastructure provider and the associated region selected by you at the time of creating your tenant, you need to allow relevant IPs to establish connectivity. Once you add the allowed IP addresses available on the Software AG Cloud Regions website, you should be able to connect to your resources from webMethods.io Integration.

Tenant URL and Software AG Cloud Region

This section helps you to identify the Software AG Cloud Region based on your tenant URL. Once you identify your cloud region, go to the Software AG Cloud Regions website and click the Show IP option for information on the allowed IP addresses.

webMethods.io Integration

Sample Tenant URL Software AG Cloud Region
https://tenantname.int-aws-us.webmethods.io/integration US1 Oregon AWS
https://tenantname.int-az-us.webmethods.io/integration US2 East Azure
https://tenantname.int-aws-de.webmethods.io/integration EU2 Frankfurt AWS
https://tenantname.int-az-eu.webmethods.io/integration EU3 West Azure
https://tenantname.int-az-au.webmethods.io/integration AU1 Australia East Azure

webMethods.io B2B

Sample Tenant URL Software AG Cloud Region
https://tenantname.int-aws-us.webmethods.io/b2b US1 Oregon AWS
https://tenantname.int-az-us.webmethods.io/b2b US2 East Azure
https://tenantname.int-aws-de.webmethods.io/b2b EU2 Frankfurt AWS
https://tenantname.int-az-eu.webmethods.io/b2b EU3 West Azure
https://tenantname.int-az-au.webmethods.io/b2b AU1 Australia East Azure

webMethods.io API Gateway

Sample Tenant URL Software AG Cloud Region
Non CA3S based:
https://tenantname.gateway.webmethodscloud.com/apigatewayui/#/login
CA3S based:
https://tenantname.apigw-aw-us.webmethods.io/apigatewayui/#/login
US1 Oregon AWS
Non CA3S based:
https://tenantname.gateway.webmethodscloud.de/apigatewayui/#/login
CA3S based:
https://tenantname.apigw-aw-eu.webmethods.io/apigatewayui/#/login
EU2 Frankfurt AWS
https://tenantname.apigw-az-au.webmethods.io/apigatewayui/#/login AU1 Australia East Azure
https://tenantname.apigw-az-us.webmethods.io/apigatewayui/#/login US2 East Azure
https://tenantname.apigw-az-eu.webmethods.io/apigatewayui/#/login EU3 West Azure

webMethods.io API Portal

Sample Tenant URL Software AG Cloud Region
https://api.webmethodscloud.com/#tenantname/ US1 Oregon AWS
https://apiportal-az-au.webmethods.io/#tenantname/ AU1 Australia East Azure
https://apiportal-az-us.webmethods.io/#tenantname/ US2 East Azure
https://apiportal-az-eu.webmethods.io/#tenantname/ EU3 West Azure
https://api.webmethodscloud.de/#tenantname/ EU2 Frankfurt AWS
https://api.webmethodscloud.eu/#tenantname/ EU1 Ireland AWS

webMethods Cloud Container

Sample Tenant URL Software AG Cloud Region
https://tenantname.container.webmethodscloud.com/integration/ US1 Oregon AWS
https://tenantname.container.webmethodscloud.eu/integration/ EU1 Ireland AWS
https://tenantname.container.webmethodscloud.de/integration/ EU2 Frankfurt AWS

webMethods.io Embed

Sample Tenant URL Software AG Cloud Region
https://tenantname.int-aws-us.webmethods.io/embed US1 Oregon AWS
https://tenantname.int-aws-de.webmethods.io/embed EU2 Frankfurt AWS

Allowed IPs and ports to open for cloud connectivity

The following table describes the IPs to be allowed and the ports to open for cloud connectivity. Locate the region your tenant belongs to and allow the relevant IP addresses.

IP address categories Description and ports to open Use cases
NAT Gateway IPs If there is a direct communication from the cloud system to your on-premises server and if you are using a REST Application to connect to your system, allow the NAT Gateway IPs. Open the port number of your on-premises servers, if your on-premises environment has exposed any server to the cloud or outside world for cloud to on-premises direct connectivity.
For example, if you are running JBoss server on port 443, expose port 443 on your data center and also allow the traffic from the NAT Gateway IPs.
  • Applicable only for direct cloud to on-premises connectivity
  • Not required for Hybrid connectivity
UM IPs and UM Load Balancer IPs Allow outbound traffic from on-premises to the cloud by allowing the cloud Universal Messaging (UM) IPs and Load Balancer (LB) IPs and also open the ports 443, 8443, 7443. Note that port 7443 is applicable for Microsoft Azure data centers only.
  • Applicable for only Hybrid connectivity where on-premises Integration Server connects to the LBs and the cloud UM servers.
Load Balancer IPs Applicable for connectivity between on-premises to cloud systems, that is, outbound traffic from on-premises to the cloud. Allow the Load balancer IPs and also open the ports 443, 8443, 7443. Note that port 7443 is applicable for Microsoft Azure data centers only.
  • Hybrid connectivity
  • Web application
  • REST API or SOAP API invocation or FlowService invocation over HTTPs
  • On-premises to cloud connectivity
Custom Domain Load Balancer IPs If you are using custom domains, allow the custom domain Load Balancer IPs and also open the ports 443, 8443, 7443. Note that port 7443 is applicable for Microsoft Azure data centers only.
  • Hybrid connectivity
  • Web application
  • REST API or SOAP API invocation or FlowService invocation over HTTPs
  • On-premises to cloud connectivity

To have the Mysql/MSSQL/FTP connectivity working for webMethods.io Integration US1 Oregon AWS based tenants, allow the following IPs:

To have the Mysql/MSSQL/FTP connectivity working for webMethods.io Integration EU2 Frankfurt AWS based tenants, allow the following IPs:

Once you add these addresses to your firewall, you should be able to connect to your resources from webMethods.io Integration easily. If not, contact Software AG Global Support and the Software AG Cloud Operations teams with the required details.