Highlighted
jaredjennings
New Member.
700 views

cmd:execute($destCommandProcessor,$LV_CMD_XML)

In a SOAP driver, I'm making a call to the SOAP API using cmd:execute($destCommandProcessor,$LV_CMD_XML)
The response is picked-up on the pub channel and executed again. Is this something with missing operation-data in the XML message that I'm posting ($LV_CMD_XML)?

A SNIP on the response, which is what I think is firing the second call.
[06/28/17 07:45:11.862]:PlanView ST:            Applying schema mapping policies to input.
[06/28/17 07:45:11.863]:PlanView ST: Applying policy: %+C%14CPV-SchemaMap%-C.
[06/28/17 07:45:11.864]:PlanView ST: Resolving association references.
[06/28/17 07:45:11.864]:PlanView ST: Processing returned document.
[06/28/17 07:45:11.865]:PlanView ST: Processing operation <ReadResponse> for .
[06/28/17 07:45:11.868]:PlanView ST: Direct command from policy result
Labels (1)
Tags (2)
0 Likes
1 Reply
Knowledge Partner
Knowledge Partner

Re: cmd:execute($destCommandProcessor,$LV_CMD_XML)

On 6/28/2017 11:24 AM, jaredjennings wrote:
>
> In a SOAP driver, I'm making a call to the SOAP API using
> cmd:execute($destCommandProcessor,$LV_CMD_XML)
> The response is picked-up on the pub channel and executed again. Is this
> something with missing operation-data in the XML message that I'm
> posting ($LV_CMD_XML)?
>
> A SNIP on the response, which is what I think is firing the second
> call.
>
> Code:
> --------------------
> [06/28/17 07:45:11.862]:PlanView ST: Applying schema mapping policies to input.
> [06/28/17 07:45:11.863]:PlanView ST: Applying policy: %+C%14CPV-SchemaMap%-C.
> [06/28/17 07:45:11.864]:PlanView ST: Resolving association references.
> [06/28/17 07:45:11.864]:PlanView ST: Processing returned document.
> [06/28/17 07:45:11.865]:PlanView ST: Processing operation <ReadResponse> for .
> [06/28/17 07:45:11.868]:PlanView ST: Direct command from policy result
> --------------------
>
>

I think we need more trace than that Jared.


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.