Hi Kasun,

Yes it's available for all the inbound protocols and functionality is
available since esb 4.9.0 alpha release.

On Tue, Jun 16, 2015 at 10:44 AM, Kasun Indrasiri <[email protected]> wrote:

> Hi Malaka,
>
> Do we support this capability in the current inbound implementation?
>
> On Mon, May 11, 2015 at 8:34 PM, Malaka Silva <[email protected]> wrote:
>
>> Hi,
>>
>> This will cover the following requirement.
>>
>> *Use Case:*
>> User should be able to use the same CAPP across all the environments.
>> However some parameters like file urls, endpoints etc are different in each
>> environment.
>> Solution with the improvement: Environment specific values can be
>> maintained in registry and can be used in inbound configuration.
>>
>> Following is the new configuration to support parameter values from
>> registry entries.
>>
>> <inboundEndpoint xmlns="http://ws.apache.org/ns/synapse";
>>  name="wso2File"  sequence="request"  onError="fault"  protocol="file"
>>    suspend="false">
>>    <parameters>
>>       <parameter name="interval">1000</parameter>
>>       <parameter name="transport.vfs.ActionAfterErrors">NONE</parameter>
>>       <parameter
>> name="transport.vfs.LockReleaseSameNode">false</parameter>
>>       <parameter name="transport.vfs.AutoLockRelease">false</parameter>
>>       <parameter name="transport.vfs.ActionAfterFailure">NONE</parameter>
>>       <parameter name="transport.vfs.ActionAfterProcess">NONE</parameter>
>>       <parameter name="sequential">false</parameter>
>>       <parameter name="transport.vfs.FileURI"
>> *key="conf:/repository/esb/esb-configurations/test"*/>
>>       <parameter name="transport.vfs.DistributedLock">false</parameter>
>>       <parameter name="transport.vfs.Locking">enable</parameter>
>>    </parameters>
>> </inboundEndpoint>
>>
>> When entering from UI need to prefix the value with key:
>>
>> eg:- *key:conf:/repository/esb/esb-configurations/test*
>>
>>
>>  [image: Inline image 1]
>>
>>
>>
>>
>>
>> On Mon, May 11, 2015 at 9:57 AM, Malaka Silva <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> I am planning to add the dynamic parameter support for Inbound Endpoints.
>>>
>>> Currently with polling inbound transport configurations (VFS/JMS), we
>>> are specifying parameters in the configuration level.  But it is a painful
>>> scenario when moving these artifacts among different environments, since
>>> the defined parameters for these inbound endpoints services are specific to
>>> the deployed environment.
>>>
>>> With the change we can use the registry to store the parameters like
>>> bellow.
>>>
>>> <inboundEndpoint xmlns="http://ws.apache.org/ns/synapse";
>>>  name="wso2File"  sequence="request"  onError="fault"  protocol="file"
>>>    suspend="false">
>>>    <parameters>
>>>       <parameter name="interval">1000</parameter>
>>>       <parameter name="transport.vfs.ActionAfterErrors">NONE</parameter>
>>>       <parameter
>>> name="transport.vfs.LockReleaseSameNode">false</parameter>
>>>       <parameter name="transport.vfs.AutoLockRelease">false</parameter>
>>>       <parameter name="transport.vfs.ActionAfterFailure">NONE</parameter>
>>>       <parameter name="transport.vfs.ActionAfterProcess">NONE</parameter>
>>>       <parameter name="sequential">false</parameter>
>>>       <parameter name="transport.vfs.FileURI">
>>> *conf:/repository/esb/esb-configurations/tes*t</parameter>
>>>       <parameter name="transport.vfs.DistributedLock">false</parameter>
>>>       <parameter name="transport.vfs.Locking">enable</parameter>
>>>    </parameters>
>>> </inboundEndpoint>
>>>
>>> Related Jira [1]
>>>
>>> [1] https://wso2.org/jira/browse/ESBJAVA-3595
>>>
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Tech Lead
>>> M: +94 777 219 791
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>> Skype : malaka.sampath.silva
>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>> Blog : http://mrmalakasilva.blogspot.com/
>>>
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> http://www.wso2.com/
>>> http://www.wso2.com/about/team/malaka-silva/
>>> <http://wso2.com/about/team/malaka-silva/>
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>
>>
>>
>> --
>>
>> Best Regards,
>>
>> Malaka Silva
>> Senior Tech Lead
>> M: +94 777 219 791
>> Tel : 94 11 214 5345
>> Fax :94 11 2145300
>> Skype : malaka.sampath.silva
>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>> Blog : http://mrmalakasilva.blogspot.com/
>>
>> WSO2, Inc.
>> lean . enterprise . middleware
>> http://www.wso2.com/
>> http://www.wso2.com/about/team/malaka-silva/
>> <http://wso2.com/about/team/malaka-silva/>
>>
>> Save a tree -Conserve nature & Save the world for your future. Print this
>> email only if it is absolutely necessary.
>>
>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/
<http://wso2.com/about/team/malaka-silva/>

Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to