I'm fairly new to the SOAP driver, only have one of them running right
now, supporting a "cloud" hosted application (directory data to the
hosted app via the Subscriber channel). Last night, the service provider
had a (scheduled) service outage. During the outage, events on the
subscriber channel returned:

[11/15/12 23:19:15.242]:HostedAppName ST:HostedAppName: Response code and
message: 500 Internal Server Error
[11/15/12 23:19:15.254]:HostedAppName ST:HostedAppName: The following
bytes (which are base64 encoded) were received
as a response to our request on the subscriber channel. They cannot be
converted to XML:
[11/15/12 23:19:15.255]:HostedAppName ST:HostedAppName:
JuYWwgU2VydmVyIEVycm9yPC9IMT4KVGhlIHNlcnZlciBlbmNv dW50ZXJlZCBhbiBpbnRlcm5hbCBlcnJvciBvcgptaXNjb25maW d1cmF0aW9u
IGFuZCB3YXMgdW5hYmxlIHRvIGNvbXBsZXRlCnlvdXIgcmVxdW VzdC48UD4KUGxlYXNlIGNvbnRhY3QgdGhlIHNlcnZlciBhZG1p bmlzdHJhdG
9yLAogeW91QHlvdXIuYWRkcmVzcyBhbmQgaW5mb3JtIHRoZW0g b2YgdGhlIHRpbWUgdGhlIGVycm9yIG9jY3VycmVkLAphbmQgYW 55dGhpbmcg
BlcnJvciBtYXkgYmUgYXZhaWxhYmxlCmluIHRoZSBzZXJ2ZXIg ZXJyb3IgbG9nLjxQPgo8SFI
bi1TZXJ2ZXItMTBnLzEwLjEuMi4yLjAgT3JhY2xlLUhUVFAtU2 VydmVyIFNlcnZlciBhdCB3d3cuZXZlcmJyaWRnZS5uZXQgUG9y dCA0NDM8L0
[11/15/12 23:19:15.259]:HostedAppName ST:SubscriptionShim.execute()
[11/15/12 23:19:15.259]:HostedAppName ST:
<nds dtdversion="2.0">
<product build="20090519_235451" instance="HostedAppName"
version="3.5.4">Identity Manager Driver for SOAP</p
<contact>Novell, Inc.</contact>
<status level="error" type="driver-general">
<description>The response received on the subscriber channel was
not valid XML. Consider writing a ByteA
rrayModifiers Java extension if you need to convert the results to XML.</

The base64 belch isn't really all that useful, but it translates to:

<TITLE>500 Internal Server Error</TITLE>
<H1>Internal Server Error</H1>
The server encountered an internal error or
misconfiguration and was unable to complete
your request.<P>
Please contact the server administrator,
you@your.address and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.<P>
More information about this error may be available
in the server error log.<P>
<ADDRESS>Oracle-Application-Server-10g/ Oracle-HTTP-Server
Server at www.hostedappname.net Port 443</ADDRESS>

So now I'm trying to decide how best to handle this. I'm thinking I could
replace the "error" status with a "retry", which should cause the engine
to keep trying to send the last event until the outage is resolved. Or, I
could replace the "error" with "fatal", if I recall correctly, which
would cause the driver to shut down, requiring manual intervention before

Given this output, is there anything better I could be doing to handle it?

David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.