Currently there are 6 7 delivery methods you can utilize in your process:
FILE – message will be created in defined server folder
FTP - message will be created in defined FTP folder
SFTP - message will be created in defined SFTP folder
JMS - message will be created and sent by Java Message Service
MQS - message will be created and sent by Message Queuing Service
EMAIL - message will be created and sent to defined emails list
HTTP - message will be sent to defined URL
In this page:
Table of Contents | ||
---|---|---|
|
...
Add varHTTPDistribution parameter to w_config_custom.inc
Code Block language xml <COL TAG="varHTTPDistribution" EXPRESSION="'Y'"/>
In eagle_wrf_generic_extract workflow on eagle_ml-2-0_default_cm_file_distribution step, open Custom Parameters and add RemoteFileName parameter with value like this:
Code Block language xml createVariable('cmReplyTo', 'dynamic:ver;2.0!url;http://127.0.0.1:5000!');
This string defines cmReplyTo parameter, which contains url to reply with or without options.
cmReplyTo can have options defined like this:
Code Block dynamic:ver;2.0!url;http://127.0.0.1:5000!user;username!password;password_value!
String should start with dynamic:
parameter_name;parameter_value! separated by ; and each pair should end with !
List of possible cmReplyTo options:
Option Name | Option Value (Example) |
---|---|
ver | 1.0 or 2.0 |
url | |
user | username |
password | password_value |
soapaction | soapaction_value |
soapheader | soapheader_value |
soapversion | soapversion_value |
cert | https_certificate |
certpass | https_certificate_password |
key | https_key |
certtype | https_certificate_type |
To trigger HTTP Distribution, RTR should contain ExtractDeliveryMethod parameter with HTTP value:
Code Block |
---|
<taskParameter> <name>ExtractDeliveryMethod</name> <dataType>S</dataType> <value>HTTP</value> </taskParameter> |
...