Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Breeze™ Collaboratory

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 09-13-2016, 06:13 AM
ander548 ander548 is offline
Whiz
 
Join Date: Jun 2016
Posts: 37
ander548 has 10 reputation points
Default Use variable for Rest Uri in Rest Service snap-in

If I use a variable {test} in the Rest Uri of the Rest Service snap-in (http://test.com/api?id={test}) then that seems to work as long as it LOOKS like a real Uri, but if I use a variable in a way that makes the Rest Uri appear like it's not a valid Uri ({test}), then I get an error "Rest Service: The RestUri is invalid". I would like to have the full Uri set as a property so is this possible?
Reply With Quote
  #2  
Old 09-14-2016, 07:40 AM
aanurag aanurag is offline
Member
.
 
Join Date: Sep 2016
Posts: 6
aanurag has 10 reputation points
Default

ED has this validation check

if (
url not starts with "http://") {
e.add("REST Service: The RestUri is invalid.");
}


can you work with url like

(http://{test})

otherwise ED would have to remove the validation in code
Reply With Quote
  #3  
Old 09-14-2016, 08:13 AM
bjliu bjliu is offline
Aspiring Member
 
Join Date: Sep 2016
Posts: 1
bjliu has 10 reputation points
Default

Anurag is correct about the URL validation.

Practically, the variables are supposed to be either the path variables or the parameters. They are supposed to have different values in real time for each execution.

The Web Service server address (FQDN or IP) and resource URI are supposed to be fixed for each Rest Service task as other properties of the Rest Service task , e.g. Authentication, username, password, return data schema, etc., are fixed and valid for one server and resource URI.

Even though you may use http://{test} in request URI, the Rest Task itself would not work if other properties would not work for all possible URIs.

Please refer to the Help on the Rest URI of the Call Rest Service task:
<LI class=li> Rest URI (mandatory) – The URI of the web service that is being invoked.
The path variable or the request parameter is in the curly brackets {}. Its name should contain only alphanumeric characters. For example,
  • http://hostort/your-rest-resources/{pathVar1}/{pathVar2}/...
  • http://hostort/your-rest-resources?param1={requestParam1}&param2={requestPa ram2}
  • http://hostort/your-rest-resources/ (There is no variable/parameter in the URL. There could be some in the payload.)

For a REST resource URI, for example, http://www.thomas-bayer.com/sqlrest/...est/CUSTOMER/2 or http://www.thomas-bayer.com/sqlrest/CUSTOMER/3, replace the exact customer number 1, 2, or 3 with a run-time parameter. Then, fill in the Rest URI value with http://www.thomas-bayer.com/sqlrest/CUSTOMER/{pathVar1}.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 09:45 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.