Vanii we may need to consider the coordination support in w-m cluster setup
as well.
On Tue, Sep 29, 2015 at 11:45 AM, Vanii Thiyagarajah wrote:
> Yes Malaka. Salesforce streaming API connects using *long polling*. In
> here the server hold the connection for a period of time, Server can return
Yes Malaka. Salesforce streaming API connects using *long polling*. In here
the server hold the connection for a period of time, Server can return the
connection at the moment When it has the information.
Thanks
On Mon, Sep 28, 2015 at 6:50 PM, Malaka Silva wrote:
> Hi Vanii,
>
> Your approach
Hi Gimantha,
I used dummy attribute to find it's aggregate value and get distinct
values. And it worked for my case.
Another thing Gimantha, It seems /analytics/aggregates API doesn't support
pagination. in earlier /analytics/search API we had "start" and "count"
attribute to support pagination.
@Rukshan, I think you have to call group by on "api" field also, otherwise
you will loose some api values. As per the current implementation, we group
by the given field and aggregate numeric values. So for the current API to
work properly there should be some numeric values to process. you can use
Hi Vanii,
Your approach looks good. But should the behavior be busy-waiting rather
than polling?
On Mon, Sep 28, 2015 at 5:54 PM, Vanii Thiyagarajah wrote:
> Hi,
>
> Salesforce ESB Custom Inbound endpoint allows to consume the Salesforce
> streaming data. It creates the connection with Salesfor
Hi,
Salesforce ESB Custom Inbound endpoint allows to consume the Salesforce
streaming data. It creates the connection with Salesforce and listens the
data periodically.
step1: Create the pushTopic record in salesforce account using developer
console.
PushTopic pushTopic = new PushTopic();
Hi All,
We have changed following method names as bellow:
*[Previous method name]* -->* [Current method name]*
updatedDocument -->updateDocument
getDocuments -->listDocuments
performBulkOperatioin -->performBulkOperations
Thank you,
Sajitha
--
View this message in context:
http://wso2-oxyg
Hi Kalyani,
as Buddhima Suggest to implement the custom inbound[1] first start with
sample [2] inbound and then try to implement basic NIO operations[3]. and
refer existing file inbound[4] working flow it guide you to get better
understand about Inbound.
[1]
http://isurur.blogspot.com/2014/12/i
Hi Kalyani,
In this case it'll be busy waiting. Therefore it's not purely listening.
Also we have to provide coordination support for this as well.
Considering the above best would be to do it as a polling transport and
implement the logic as one time task.
Similar is done in MQTT inbound. [1]
On Mon, Sep 28, 2015 at 12:30 PM, Lakshani Gamage wrote:
> Hi all,
>
> These are the design decisions taken in database modification discussion.
>
> *In IS Point of View,*
>
>- When a new XACML policy is being added, user can define, for which
>SP-IDP combination the XACML policy is valid
Hi Gimantha,
i could group by multiple attribute as you explained and it working well.
Other thing is we need group by query to find the distinct attribute of the
result set.
sql ex:
select api from myTable group by user.
Here api is not a int value and it is string. So does group by should
sup
On Mon, Sep 28, 2015 at 12:30 PM, Lakshani Gamage wrote:
> Hi all,
>
> These are the design decisions taken in database modification discussion.
>
> *In IS Point of View,*
>
>- When a new XACML policy is being added, user can define, for which
>SP-IDP combination the XACML policy is valid
Hi All,
I had discussion with Buddhima about Local File Inbound/Connector. He
suggested some resources on Custom Inbound.
Please find the discussion in above mail.
Thanks
On Mon, Sep 28, 2015 at 12:28 PM, Kalyani Yogeswaranathan
wrote:
>
> -- Forwarded message --
> From: Buddh
Hi all,
These are the design decisions taken in database modification discussion.
*In IS Point of View,*
- When a new XACML policy is being added, user can define, for which
SP-IDP combination the XACML policy is valid. (We can define valid policy
SP-IDP combinations in the "target" tag
14 matches
Mail list logo