...
When you configure a Data Connector applet to get data from or send data to an external web service, you can send hard-coded values to that web service in the request object. You can also send custom configuration values that are encrypted and stored by NewVoiceMedia. For example, your web service might require a password to access it. Instead of hard-coding the password in the Data Connector applet for anyone with access to the applet to see, you can request that NewVoiceMedia encrypts and stores this password for you in a custom configuration setting. You can then send the password in the request to the configured web service.To insert
You can use Data Source values in the following ways:
- If you are defining the web service interaction using XML, to insert a custom configuration value into a request, use a placeholder in the Url element, Key or Value element of a header, or the CDATA section of the Body element.
...
- If you are using a template to define the web service interaction, to insert a custom configuration value into a request, use a placeholder in any required request parameter fields.
Placeholders must be in the format #(CustomConfigurationKey). Replace CustomConfigurationKey with CustomConfigurationKey with the name of the custom configuration setting that contains the value you want to use in the request.
| Expand | ||
|---|---|---|
| ||
For example, using the placeholder #(WebServicePassword) the value of the setting called WebServicePassword is decrypted and sent in the request. You can use the placeholder in the following places:
|
...
...
When the call reaches this applet, #(WebServicePassword) is replaced with the decrypted WebServicePassword and the web service uses the password accordingly. |
If the custom configuration setting does not exist or has no value, the call is routed to the Interface Failure applet.
If the custom configuration setting is null, the placeholder is removed.