When a tenant hosts a service to be used by external parties, it should ideally have a short URL. Shorter URLs are easier to be memorized and typed, which eliminates the need to log-in to access the service. Also, tenant information and other descriptive attributes are hidden in shorter URLs, and they are more convenient in hard-copy productions.
...
The steps below explain how to use URL mapping.
1.
- Log
...
- in to the
...
- management console and select
...
- Services
...
- > List
...
- under the
...
- Main
...
- menu.
...
...
- From the Deployed Services
...
- page
...
...
- that appears, click a service to which you want to map the end point URL.
- The service's dashboard opens.
...
Click the "URL Mappings" link.
4. The "URL Mappings" window opens. Click the "Add New Mapping" link.
...
- It contains a link for URL Mapping. Click it.
- In the URL Mappings page that opens, click Add New Mapping link and enter a URL mapping name.
...
...
- The added URL mapping appears in the
...
- URL Mapping
...
- page. For example,
...
Here the suffix
...
localhost
...
- comes from
...
<PRODUCT_
...
HOME>/repository/conf/etc/url-mapping-config.xml. By default, the suffix is localhost and the URL mappings limit is 1. You can configure your own suffix and
...
- limit
...
- per service in the mentioned configuration file.
...
- With this shortened endpoint URL, you can access the service's WSDL files, tryit tool and rest calls
...
- as follows:
- http://examplemap.localhost:port?wsdl - to access the wsdl of your service
...
- http://examplemap.localhost:port?tryit - to access the tryit tool of your service
...
...
- http://examplemap.localhost:port /getQuote - to access rest call of your service
- To access your own domain, a cname is required. If a cname is not available at the moment, you can use /etc/hosts file in ubuntu or Windows\Syst em32\drivers\et c\hosts file in windows to put your domain entries pointing to the local ip. For example,
| Code Block |
|---|
127.0.0.1 exampleapp.localhost |
...