Highlighted
Super Contributor.
Super Contributor.
597 views

SOAP Driver odd behaviour

Hi, I am using the SOAP driver (without the SPML and DSML Packages - as we use different schemata).
Main Problem:

within the publisher etp I use the heartbeat to issue an SOAP Document to find changed entires. This works fine, I get a response document back into ITP. Here I can do with that document what I need to do. So I transform this into an regular "instance" document. For some reason this instance does not go to the eta. After the Schema mapping it is gone. The same happens also if i do not manipulate the response document. They will not make it back to the calling rule.

The same applies to status, but this is normal behaviour...

<nds dtdversion="2.0">
<source>
<product build="20170208_0924" instance="HISinOne - Students" version="4.0.0.4">Identity Manager Driver for SOAP</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status event-id="0" level="success" xmlns:his="http://www.his.de/ws/AccountService" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.xxxxxx.de/webservice/services2/StudentService201812/"/>
</status>
<instance class-name="InetOrgPerson" event-id="0" src-dn="158038">
<attr attr-name="studentId">
<value>158038</value>
</attr>
<attr attr-name="personId">
<value>219823</value>
</attr>
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.xxxxxx.de/webservice/services2/StudentService201812/"/>
</instance>
</output>
</nds>
[01/31/19 16:24:41.883]:HISinOne - Students ST:Applying policy: %+C%14Citp-0200-Handle Instances and Build Documents%-C.
[01/31/19 16:24:41.883]:HISinOne - Students ST: Applying to status #1.
[01/31/19 16:24:41.883]:HISinOne - Students ST: Applying to instance #2.
[01/31/19 16:24:41.883]:HISinOne - Students ST:Policy returned:
[01/31/19 16:24:41.884]:HISinOne - Students ST:
<nds dtdversion="2.0">
<source>
<product build="20170208_0924" instance="HISinOne - Students" version="4.0.0.4">Identity Manager Driver for SOAP</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status event-id="0" level="success" xmlns:his="http://www.his.de/ws/AccountService" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.xxxxxx.de/webservice/services2/StudentService201812/"/>
</status>
<instance class-name="InetOrgPerson" event-id="0" src-dn="158038">
<attr attr-name="studentId">
<value>158038</value>
</attr>
<attr attr-name="personId">
<value>219823</value>
</attr>
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.xxxx.de/webservice/services2/StudentService201812/"/>
</instance>
</output>
</nds>
[01/31/19 16:24:41.885]:HISinOne - Students ST:Applying policy: %+C%14Citp-0300-Check for ADD%-C.
[01/31/19 16:24:41.885]:HISinOne - Students ST: Applying to status #1.
[01/31/19 16:24:41.885]:HISinOne - Students ST: Evaluating selection criteria for rule 'Insert correct Attributes and Association to ADD'.
[01/31/19 16:24:41.885]:HISinOne - Students ST: (if-operation equal "add") = FALSE.
[01/31/19 16:24:41.885]:HISinOne - Students ST: Rule rejected.
[01/31/19 16:24:41.885]:HISinOne - Students ST: Applying to instance #2.
[01/31/19 16:24:41.885]:HISinOne - Students ST: Evaluating selection criteria for rule 'Insert correct Attributes and Association to ADD'.
[01/31/19 16:24:41.886]:HISinOne - Students ST: (if-operation equal "add") = FALSE.
[01/31/19 16:24:41.886]:HISinOne - Students ST: Rule rejected.
[01/31/19 16:24:41.886]:HISinOne - Students ST:Policy returned:
[01/31/19 16:24:41.886]:HISinOne - Students ST:
<nds dtdversion="2.0">
<source>
<product build="20170208_0924" instance="HISinOne - Students" version="4.0.0.4">Identity Manager Driver for SOAP</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status event-id="0" level="success" xmlns:his="http://www.his.de/ws/AccountService" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.xxxxx.de/webservice/services2/StudentService201812/"/>
</status>
<instance class-name="InetOrgPerson" event-id="0" src-dn="158038">
<attr attr-name="studentId">
<value>158038</value>
</attr>
<attr attr-name="personId">
<value>219823</value>
</attr>
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.xxxxx.de/webservice/services2/StudentService201812/"/>
</instance>
</output>
</nds>
[01/31/19 16:24:41.887]:HISinOne - Students ST:Applying schema mapping policies to input.
[01/31/19 16:24:41.887]:HISinOne - Students ST:Applying policy: %+C%14C0100-SMP%-C.
[01/31/19 16:24:41.887]:HISinOne - Students ST: Mapping class-name 'InetOrgPerson' to 'idmEntry'.
[01/31/19 16:24:41.888]:HISinOne - Students ST: Mapping attr-name 'studentId' to 'idmHISStudentID'.
[01/31/19 16:24:41.888]:HISinOne - Students ST: Mapping attr-name 'personId' to 'idmHISIdent'.
[01/31/19 16:24:41.888]:HISinOne - Students ST:Resolving association references.
[01/31/19 16:24:41.888]:HISinOne - Students ST:Processing returned document.
[01/31/19 16:24:41.888]:HISinOne - Students ST:Processing operation <status> for .
[01/31/19 16:24:41.888]:HISinOne - Students ST:
DirXML Log Event -------------------
Driver: \IDMS-TEST\haw\res\DriverSet\HISinOne - Students
Channel: Subscriber
Status: Success
[01/31/19 16:24:41.888]:HISinOne - Students ST:Processing operation <instance> for .

This is the last I can see in the trace.

Any Idea?
thanks in advance
Labels (1)
0 Likes
8 Replies
Super Contributor.
Super Contributor.

Re: SOAP Driver odd behaviour

BTW - I already simplified the instance document. Normally I had added an association element as well, but this did not make any difference.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: SOAP Driver odd behaviour

ukrause;2494628 wrote:
Hi, I am using the SOAP driver (without the SPML and DSML Packages - as we use different schemata).
Main Problem:

within the publisher etp I use the heartbeat to issue an SOAP Document to find changed entires. This works fine, I get a response document back into ITP. Here I can do with that document what I need to do. So I transform this into an regular "instance" document. For some reason this instance does not go to the eta. After the Schema mapping it is gone. The same happens also if i do not manipulate the response document. They will not make it back to the calling rule.

The same applies to status, but this is normal behaviour...

<nds dtdversion="2.0">
<source>
<product build="20170208_0924" instance="HISinOne - Students" version="4.0.0.4">Identity Manager Driver for SOAP</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status event-id="0" level="success" xmlns:his="http://www.his.de/ws/AccountService" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.xxxxxx.de/webservice/services2/StudentService201812/"/>
</status>
<instance class-name="InetOrgPerson" event-id="0" src-dn="158038">
<attr attr-name="studentId">
<value>158038</value>
</attr>
<attr attr-name="personId">
<value>219823</value>
</attr>
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.xxxxxx.de/webservice/services2/StudentService201812/"/>
</instance>
</output>
</nds>
[01/31/19 16:24:41.883]:HISinOne - Students ST:Applying policy: %+C%14Citp-0200-Handle Instances and Build Documents%-C.
[01/31/19 16:24:41.883]:HISinOne - Students ST: Applying to status #1.
[01/31/19 16:24:41.883]:HISinOne - Students ST: Applying to instance #2.
[01/31/19 16:24:41.883]:HISinOne - Students ST:Policy returned:
[01/31/19 16:24:41.884]:HISinOne - Students ST:
<nds dtdversion="2.0">
<source>
<product build="20170208_0924" instance="HISinOne - Students" version="4.0.0.4">Identity Manager Driver for SOAP</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status event-id="0" level="success" xmlns:his="http://www.his.de/ws/AccountService" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.xxxxxx.de/webservice/services2/StudentService201812/"/>
</status>
<instance class-name="InetOrgPerson" event-id="0" src-dn="158038">
<attr attr-name="studentId">
<value>158038</value>
</attr>
<attr attr-name="personId">
<value>219823</value>
</attr>
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.xxxx.de/webservice/services2/StudentService201812/"/>
</instance>
</output>
</nds>
[01/31/19 16:24:41.885]:HISinOne - Students ST:Applying policy: %+C%14Citp-0300-Check for ADD%-C.
[01/31/19 16:24:41.885]:HISinOne - Students ST: Applying to status #1.
[01/31/19 16:24:41.885]:HISinOne - Students ST: Evaluating selection criteria for rule 'Insert correct Attributes and Association to ADD'.
[01/31/19 16:24:41.885]:HISinOne - Students ST: (if-operation equal "add") = FALSE.
[01/31/19 16:24:41.885]:HISinOne - Students ST: Rule rejected.
[01/31/19 16:24:41.885]:HISinOne - Students ST: Applying to instance #2.
[01/31/19 16:24:41.885]:HISinOne - Students ST: Evaluating selection criteria for rule 'Insert correct Attributes and Association to ADD'.
[01/31/19 16:24:41.886]:HISinOne - Students ST: (if-operation equal "add") = FALSE.
[01/31/19 16:24:41.886]:HISinOne - Students ST: Rule rejected.
[01/31/19 16:24:41.886]:HISinOne - Students ST:Policy returned:
[01/31/19 16:24:41.886]:HISinOne - Students ST:
<nds dtdversion="2.0">
<source>
<product build="20170208_0924" instance="HISinOne - Students" version="4.0.0.4">Identity Manager Driver for SOAP</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status event-id="0" level="success" xmlns:his="http://www.his.de/ws/AccountService" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.xxxxx.de/webservice/services2/StudentService201812/"/>
</status>
<instance class-name="InetOrgPerson" event-id="0" src-dn="158038">
<attr attr-name="studentId">
<value>158038</value>
</attr>
<attr attr-name="personId">
<value>219823</value>
</attr>
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.xxxxx.de/webservice/services2/StudentService201812/"/>
</instance>
</output>
</nds>
[01/31/19 16:24:41.887]:HISinOne - Students ST:Applying schema mapping policies to input.
[01/31/19 16:24:41.887]:HISinOne - Students ST:Applying policy: %+C%14C0100-SMP%-C.
[01/31/19 16:24:41.887]:HISinOne - Students ST: Mapping class-name 'InetOrgPerson' to 'idmEntry'.
[01/31/19 16:24:41.888]:HISinOne - Students ST: Mapping attr-name 'studentId' to 'idmHISStudentID'.
[01/31/19 16:24:41.888]:HISinOne - Students ST: Mapping attr-name 'personId' to 'idmHISIdent'.
[01/31/19 16:24:41.888]:HISinOne - Students ST:Resolving association references.
[01/31/19 16:24:41.888]:HISinOne - Students ST:Processing returned document.
[01/31/19 16:24:41.888]:HISinOne - Students ST:Processing operation <status> for .
[01/31/19 16:24:41.888]:HISinOne - Students ST:
DirXML Log Event -------------------
Driver: \IDMS-TEST\haw\res\DriverSet\HISinOne - Students
Channel: Subscriber
Status: Success
[01/31/19 16:24:41.888]:HISinOne - Students ST:Processing operation <instance> for .

This is the last I can see in the trace.

Any Idea?
thanks in advance


I seem to recall seeing something like this in the past, but I can't find a reference for it now. What happens if you strip the operation-data off of the instance?
0 Likes
Highlighted
Super Contributor.
Super Contributor.

Re: SOAP Driver odd behaviour

makes no difference, unfortunately.

<nds dtdversion="2.0">
<source>
<product build="20170208_0924" instance="HISinOne - Students" version="4.0.0.4">Identity Manager Driver for SOAP</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status event-id="0" level="success" xmlns:his="http://www.his.de/ws/AccountService" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<operation-data Query-Result="true" event-id="0" method="POST" parent-node-1="output" soap-action="http://www.his.de/ws/StudentService201812/findStudent" url="https://bewerbung-test.haw-hamburg.de/webservice/services2/StudentService201812/"/>
</status>
<instance class-name="InetOrgPerson" event-id="0" src-dn="158038">
<association>158038</association>
<attr attr-name="studentId">
<value>158038</value>
</attr>
<attr attr-name="personId">
<value>219823</value>
</attr>
</instance>
</output>
</nds>
[02/01/19 06:52:50.298]:HISinOne - Students ST:Applying schema mapping policies to input.
[02/01/19 06:52:50.298]:HISinOne - Students ST:Applying policy: %+C%14C0100-SMP%-C.
[02/01/19 06:52:50.298]:HISinOne - Students ST: Mapping class-name 'InetOrgPerson' to 'idmEntry'.
[02/01/19 06:52:50.298]:HISinOne - Students ST: Mapping attr-name 'studentId' to 'idmHISStudentID'.
[02/01/19 06:52:50.298]:HISinOne - Students ST: Mapping attr-name 'personId' to 'idmHISIdent'.
[02/01/19 06:52:50.298]:HISinOne - Students ST:Resolving association references.
[02/01/19 06:52:50.299]:HISinOne - Students ST:Processing returned document.
[02/01/19 06:52:50.299]:HISinOne - Students ST:Processing operation <status> for .
[02/01/19 06:52:50.299]:HISinOne - Students ST:
DirXML Log Event -------------------
Driver: \IDMS-TEST\haw\res\DriverSet\HISinOne - Students
Channel: Subscriber
Status: Success
[02/01/19 06:52:50.299]:HISinOne - Students ST:Processing operation <instance> for .
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SOAP Driver odd behaviour

On 2019-01-31 17:24, ukrause wrote:
> within the publisher etp I use the heartbeat to issue an SOAP Document
> to find changed entires.


How exactly do you do this?

Do you set a local variable to the result of a query?

--
Norbert
--
Norbert
0 Likes
Highlighted
Super Contributor.
Super Contributor.

Re: SOAP Driver odd behaviour

Hi Norbert,
yes, I set a local variable with the SAOP Call as Content and use another variable which calls the srcCommandProcessor and should contain the returned Document at the end. But the result is visible within ITP but never makes it back to the calling rule in the etp.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: SOAP Driver odd behaviour

ukrause;2494662 wrote:
Hi Norbert,
yes, I set a local variable with the SAOP Call as Content and use another variable which calls the srcCommandProcessor and should contain the returned Document at the end. But the result is visible within ITP but never makes it back to the calling rule in the etp.


Can you post the entire level 3 trace of this (use pastebin.com or susepaste.org) event being processed?
0 Likes
Highlighted
Super Contributor.
Super Contributor.

Re: SOAP Driver odd behaviour

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SOAP Driver odd behaviour

> yes, I set a local variable with the SAOP Call as Content and use
> another variable which calls the srcCommandProcessor and should contain
> the returned Document at the end.
> But the result is visible within ITP
> but never makes it back to the calling rule in the etp.


The lv in the calling rule on the publisher thread is set in to the
result of the srcCommandProcessor call in line 204. It is a nodeset with
one element node:

<status level="success">Document scheduled for execution on Subscriber
channel.</status>

However, as the message indicates, the actual SOAP call is done on the
subscriber thread (line 594).
The result goes into the input policy set (line 646), the schema mapping
(line 885) and the association processor (line 890).
It does not go into pub-etp because this is the subscriber thread
(follow the orange line in the "fish bone" diagram.)


--
Norbert
--
Norbert
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.