Network requirements for services
- 06 Mar 2023
- 1 Minute to read
- Print
- DarkLight
Network requirements for services
- Updated on 06 Mar 2023
- 1 Minute to read
- Print
- DarkLight
Article Summary
Share feedback
Thanks for sharing your feedback!
Description
The Agile.Now server uses network addresses optimised for data security and network availability. All services require TCP port 443, with a valid SSL.
| OutSystems Platform-as-a-Service (Paas) | On-site install |
|---|---|
| Two types of web addresses are in use by PaaS, utilising both internal and public addresses. Agile.Now will connect to whichever is the most suitable for any given situation. | In OutSystems On-Site installs, only a single network address is used (as configured in ServiceCenter) |
Agile.Now network requirements
| Address used (PaaS x2 / On-Site x1) | Source | Destination | Port | Protocol | Notes |
|---|---|---|---|---|---|
| Public | Agile.Now Web Application | Front-End Modules | 443 | TCP | Links to open modules directly in Service Studio |
| Public | Agile.Now Web Application | Front-End BDD testing application | 443 | TCP | Links to run unit tests via built-in BDD |
| Public | Agile.Now Web Application | Front-End end-to-end tests | 443 | TCP | Links to run end-to-end tests |
| Public | Agile.Now Front-End Probe | Agile.Now Server | 443 | TCP | Status signals (not containing data) is sent |
| Internal | Front-End Agile.Now Probe | Agile.Now Server | 443 | TCP | Probe application when installed on Front-End registers itself with Agile.Now server |
| Internal | Agile.Now Server | Front-End Agile.Now Probe | 443 | TCP | Agile.Now Server will fetch data from the Front-End probe; include information on applications, modules, versions and BDD tests |
| Internal | Agile.Now Server | Front-End where OutSystems Discovery installed (normally DEV) | 443 | TCP | Agile.Now server will fetch data from OutSystems Discovery application |
| Internal | Agile.Now Front-Ends | Agile.Now Server | 443 | TCP | Agile.Now Webhook for realtime updates |
External connectivity requirements
Agile.Now includes connectivity to external services, both built-in and custom integration that can be built. The scope of this document does not cover user-built integrations and should be documented by the user themselves.
Project Management tools
| Purpose | Source | Destination | Port | Protocol | Notes |
|---|---|---|---|---|---|
| Atlassian JIRA | Agile.Now Server | https://company.atlassian.net/jira/software/ | 443 | TCP | Agile.Now connects to JIRA in order to track Issues and Projects |
| Azure DevOps | Agile.Now Server | https://dev.azure.com/company/ | 443 | TCP | Agile.Now connects to DevOps in order to track Issues and Projects |
| Rally Software | Agile.Now Server | https://rally1.rallydev.com/ | 443 | TCP | Agile.Now connects to Rally in order to track Issues and Projects (coming soon) |
| Your own custom integration | Agile.Now Server | https://projecttool.company.tld | 443 | TCP | Agile.Now allows custom integrations to be done using integration libraries (as of version 2.4.0) |
Automated Testing Tools
| Purpose | Source | Destination | Port | Protocol | Notes |
|---|---|---|---|---|---|
| Ghost Inspector | Agile.Now Server | https://app.ghostinspector.com/account | 443 | TCP | Agile.Now connects to Ghost Inspector in order to run automated testing |
| Your own custom integration | Agile.Now Server | https://testingtool.company.tld | 443 | TCP | Agile.Now allows custom integrations to be done using integration libraries (as of version 2.3.0) |
OutSystems SaaS Tools
| Purpose | Source | Destination | Port | Protocol | Notes |
|---|---|---|---|---|---|
| AI Mentor Studio (previously Architecture Dashboard) | Agile.Now Server | aimentorstudio.outsystems.com architecture.outsystems.com | 443 | TCP | Agile.Now uses the AI Mentor SaaS to help reduce technical debt in your code |
Was this article helpful?
