Question
Sopra Steria Group
FR
Last activity: 7 Jan 2020 10:07 EST
Run a Connector Rest on a Data-page with scope Node, 7.3.1
Hi everyone,
My team and I have a issue with our development.
Our need is to call a REST Service with a data-page to retrieve a token and a refresh-token but we do not want to call this service everytime.
We used the scope "Node" on data-page to share the token and we added a when rule to refresh or not the Data-page.
When we test a activity which call the Connector, it works well. But with data-page we have this: "the server responded with an HTTP 404 code, indicating that the resource does not exist. // The body of the service's response, which is set up for mapping in the Connector rule, was empty for this service call."
When we test in thread scope and requestor scope, it works well.
How can we manage the service call in node scope? And why it works on thread and requestor scope and not in node scope?
Regards
Accepted Solution
Sopra Steria Group
FR
Hi everyone,
My issue is solved.
I test my Data-page only in my session and in check-out edition. I never commit, so I think that when I launch the data-page on node, the rule resolution of the node take the connector which is not in my ruleset. When I commit the rule, it finally works..
BPM Company
NL
1. Am I right then that if you're running the data page (through Actions/Run) using Requestor scope, it works.
But when you just switch it to Node, you're getting 404 error?
2. How's the URL for REST connector is set up? Could you provide screenshots of your configuration (DP and the connector)
BPM Company
NL
Could you then check on Tracer - during the execution of activity "pyInvokeRESSTConnector", look into a step page (usually, it's =unnamed=), the property pyResourcePath. It should containt the resourse URI
Sopra Steria Group
FR
The property contains the good URI for the Thread and Requestor.
Except for the node which contain dummy/dummy/token instead of dummy/token.
Will edit when i'll find why
Accepted Solution
Sopra Steria Group
FR
Hi everyone,
My issue is solved.
I test my Data-page only in my session and in check-out edition. I never commit, so I think that when I launch the data-page on node, the rule resolution of the node take the connector which is not in my ruleset. When I commit the rule, it finally works..