Why does TIBCO Adapter (Tfor Siebelthrow a deserialization error when it is deployed in Administrator?
Article ID: KB0084719
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Siebel | - |
| Not Applicable | - |
Description
Resolution:
TIBCO Adapter for Siebel throws the following deserialization error when it is deployed in Administrator:
--------------------------------------------------------------------------------------------------
Subscription service <service_name> failed to deserialize the event received on subject <subject_name> and SDK exception thrown is "Operation error: in file %1. "null. The Repository URL is <repoURL> and the Configuration URL is <configURL>
--------------------------------------------------------------------------------------------------
The issue is that the adapter is not able to deserialise the message(both for RV and JMS transport) if an external .xsd schema is referenced.
This issue occurs because the xsd's and custom AESchemas will not be included in the .dat file created during deployment. You can open the dat file in a text editor and search for the schema refernces to confirm this.
Workaround:
To avoid this error,define the Custom Schemas under AESchemas/ae/siebel folder only.
If the reference is still missing(in the project created by Administrator during deployment), then before building the archive in Designer, please update the References section, in SharedArchive, till .aeschema:
TIBCO Adapter for Siebel throws the following deserialization error when it is deployed in Administrator:
--------------------------------------------------------------------------------------------------
Subscription service <service_name> failed to deserialize the event received on subject <subject_name> and SDK exception thrown is "Operation error: in file %1. "null. The Repository URL is <repoURL> and the Configuration URL is <configURL>
--------------------------------------------------------------------------------------------------
The issue is that the adapter is not able to deserialise the message(both for RV and JMS transport) if an external .xsd schema is referenced.
This issue occurs because the xsd's and custom AESchemas will not be included in the .dat file created during deployment. You can open the dat file in a text editor and search for the schema refernces to confirm this.
Workaround:
To avoid this error,define the Custom Schemas under AESchemas/ae/siebel folder only.
If the reference is still missing(in the project created by Administrator during deployment), then before building the archive in Designer, please update the References section, in SharedArchive, till .aeschema:
Issue/Introduction
Why does TIBCO Adapter (Tfor Siebelthrow a deserialization error when it is deployed in Administrator?
Feedback
Yes
No
Powered by
