DevOps Edition for Continuous Integration 10.5 | Service Development Help | Building Services | About Service Run-Time Parameters | About URL Aliases for Services | Creating a Path Alias for a Service
 
Creating a Path Alias for a Service
Use the HTTP URL alias property in the Properties view to create a path alias to use when invoking the service in a URL.
When creating a path alias for a service, keep the following in mind:
*When you add, edit, or delete an HTTP URL alias property in a service, the property is automatically updated on the Integration Server when the service is saved.
*Integration Server stores the HTTP URL alias information in the node.ndf file of the service. Because the property is encoded in the node.ndf file, it is propagated across servers through package replication.
*URL aliases for services are saved in memory on the Integration Server. The server checks for URL aliases before processing the client HTTP requests.
*When specifying the alias URL, you must spell it exactly as it is defined on the server. Alias URLs are case sensitive.
*URL alias strings must be unique on the server. The server cannot register a URL alias if one already exists with the same name on the server, even if it belongs to a different package.
*To troubleshoot alias URLs that cannot register, open the Package > Management > PackageName screen in the Integration Server Administrator and view the information under Load Warnings. The alias URLs that generated warnings when the package was installed are displayed here with a brief explanation.
* To create an alias for a service URL
1. In the Package Navigator, open the service that you want to configure.
2. In the Run time category of the Properties view, next to the HTTP URL alias property, enter an alias string for the URL that will invoke the service.
Important: Do not use reserved characters in the URL alias string. Alias strings that contain reserved characters are invalid and will not work.
3. On the File menu, click Save.

Copyright © 2017-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.