Release 10.1A: OpenEdge Application Server:
Administration

> ## Constructing URLs

> In this manual, the URL path to a specific WSA instance is referred to as `wsa-root-url`. When you install the WSA, the installation procedure prompts you for a `wsa-root-url` value for the sample WSA instance (wsa1). Thereafter, every time you create a new WSA instance you must provide a new `wsa-root-url` value for that instance. The value is stored in the wsaUrl property in `ubroker.properties`.

> The `wsa-root-url` has the following syntax:

> Syntax
>     http[s]://host:port[/web-server-context]/wsa-webapp-context/wsa-instance

> Note: If the WSA URL `host` is named `localhost`, it must be changed to the name of the host machine when Web services are deployed for network access.

> In the above syntax, use the optional element, /`web-server-context`, if the WSA runs in a JSE that runs in a separate Web server. Omit the optional element if the WSA runs in a JSE that runs stand-alone.

> In order to create a WSA instance, you need to construct the URL for the `wsa-root-url`. The URL components in the syntaxes each describe a specific part of the WSA instance configuration, as shown in Table 5–1.

> Table 5–1: URL components
> This URL component... | Which is specified in... | Names...
> --- | --- | ---
>     web-server-context
> | The Web server configuration file. | The connection between the JSE and the Web server (if any).
>     wsa-webapp-context
> | The JSE configuration file. | A particular Web application within the JSE context.
>     wsa-instance
> | The WSA Web application descriptor file. | A unique WSA instance.

> Typically, `web-server-context`, `wsa-webapp-context`, and `wsa-instance` are assigned aliases (actual values) by providers—the people who are responsible for the hardware and software in the OpenEdge WSA environment. Aliases typically do not consist of physical names related to the system or to file paths, but rather names meaningful to providers.

> For example, consider the sample Web service system elements and aliases in Table 5–2.

> Table 5–2: Sample aliases for URL components
> URL component | Sample alias
> --- | ---
>     web-server-context
>     bedrock
>     wsa-webapp-context
>     quarry
>     wsa-instance
>     fred

> Given the aliases in Table 5–2:

> - The WSA running in the context of the JSE running in the context of a separate Web server has the following URL:

>     http://servicehost:80/bedrock/quarry/fred

> - The WSA running in the context of the JSE running stand-alone has the following URL:

>     http://servicehost:8080/quarry/fred

> Any URL subpaths specified by the client that lie beyond `wsa-root-url` are delivered to the WSA instance for it to interpret and use. For example, to access the WSDL documents associated with a particular WSA instance, append the `/wsdl` subpath to `wsa-root-url`, as shown in bold:

>     http://servicehost:80/bedrock/quarry/fred/wsdl

> Given this URL, an HTTP message travels through the Web server, through the JSE, then to the WSA instance, `fred`. Then, the WSA instance is passed the relative path, `/wsdl`, which tells it to perform a WSDL-related operation.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095