Structure of an InterSystems Web Application URL

http or https, depending on whether or not you have configured your web server to use TLS. InterSystems strongly recommends the use of TLS.

The IP address or DNS name where your web server is available. When the web server is on the same machine as the client, this is usually localhost.

The port number over which your web server is listening for requests. You do not need to specify a port number unless your web server is listening for requests on a port other than the standard ports for HTTP (80) or HTTPS (443).

A string which uniquely identifies one of your InterSystems IRIS application servers.

If you do not need to discriminate between multiple InterSystems IRIS instances, you can configure the Web Gateway to serve web applications at URLs which omit this portion of the path, as in the preceding example. However, if you serve multiple InterSystems IRIS instances using a single web server and you must access a web application unique to one instance (such as an instance’s Management Portal), you must configure your web server and Web Gateway to route requests to the instance using this identifier as a prefix to the application path. This identifier is the CSPConfigName for the instance. By default, an instance’s CSPConfigName is its instance name, in all lowercase characters. However, it can be configured.

If the application in the preceding example were exclusively available on the InterSystems IRIS application server named iris2, then you could configure the /iris2 path within the web server and Web Gateway configurations to serve the application at the following URL:https://yourhost.com/iris2/criticalapp/MainDashboard.csp