Table of Contents
Last week, some of our users reported to us that they encountered a bug in the XML Hierarchy Transformer.
Updated
There is a special workflow whose first element is the XML Hierarchy Transformer. The workflow is deployed even if the web service is used.
When calling the SOAP web service from the user interface, the following error occurs:
Could not call ‘XML Hierarchy Transformer’ service, routine ‘XMLDocToXMLHier’ in ‘Yesterday’s XML Transformer’ step. And (sbl-bpr – 00162)
later [Version: V8 and above]
The information in this help document applies to all platforms.
Goal
The client actually has an inbound integration, if the inbound knowledge is ISO-8859-1, UTF-8, or UTF-16, the effort works well.
But when using ISO-8859-15, the XML EAI transformer (XMLDocToIntObjHier method) doesn’t work because: –
Fatal XML parser error at line 1, column 45: An exception has occurred! Type: TranscodingException, Message: Failed to create encoding converter: ISO-8859-15(SBL-EAI-00247)
This only happens on the Linux platform (looks like it’s time to work well on Windows and Solaris).
Workaround
Now the change request is created and assigned to SR:-
ERRORCA 10589812 – On Linux: – Failed to create converter associated with encoding: ISO-8859-15
At the time of this writing, the replacement request is still open, and also indicates that this is a bug in the Siebel version of the Xerces Linux parser.
Links
Error: 10589812 name=”REF”> – ON LINUX: – CANNOT CREATE ENCODING CONVERTER: ISO-8859-15
Apply What Will Be:
Siebel System Software – Versions: 6.0.1 [2848] to 8.1.1 [21112] – Versions: V6 to In v8
The information in this document applies to each platform.
This document was previously published as Siebel Troubleshooting Steps 49.
Goal
Last Revision 8 Date
August 2008
Reader Instructions
You will almost certainly be provided with a troubleshooting guide
that will help resolve your particular problem. Wherever possible, diagnostic tools are
document versions to assist in troubleshooting.
Troubleshooting Details
eai Siebel Toolkit StatusIt is from a set of commercial conversion services. With these business services, you can write professional business service scripts or create workflow procedures that convert data to and from various formats, such as converting MIME data into a Siebel integration object instance. In addition to the general commercial EAI service, there are also enterprise-specific converters such as the FINS IAA-XML converter.
This document provides troubleshooting guidelines for the three main Siebel EAI XML transformers that convert the incoming and outgoing property set data into an XML document:
- XML Transformer
- XML Hierarchy Transformer (new in Siebel 7.0.4)
- EAI XML Transformer
-
Incorrectly specified with an empty input argument. For illustrative purposes only, the input XML document or set is empty, contains invalid data, or is definitely in an invalid format.
You will receive error messages if you try to use our XML EAI Transformer to convert an asset set that is not a Siebel Addition object. If you return an XML document that is not suitable to be converted by the Siebel message, you will also get errors. Since the transformation of the integration object depends on the metadata, problems also arise if the definition of the integration object does not exist in Siebel SRF, or even if your XML element and attributes do not actually contain the definition of the integration object.
-
Problems with encoding conversion
You will get errors if your main XML prolog uses a specific channel (i.e. “encoding=’UTF-8′”), but your actual data is stored as UTF-16. Another common mistake is that your document is encoded as ISO-8859-1 and then contains Western European language specific classes like: ) but you eat “utf-8” in XML-Prolog.
For previous versions linked to Siebel version 6, it is possible to properly encode the input document, but the mapping of input and output characters specified in the XML document is not well supported by the included XML parser due to the Siebel version 6. Version 6 of Siebel suffered from limited character set support. There were ways to read ISO-8859-1, but all documents were created in UTF-8 unless a custom group service was written.
In Siebel version 7.5 and higher, the list ofSupported character sets for input and output XML documents. For a complete list of safe character sets, go to the “List” screen under “Values” and ask “Type means *CHAR_ENCODING_CD”
Speed up your computer today with this simple download.
Les Problèmes Avec XML Hierarchy Converter Devraient être Résolus
Los Problemas Con XML Hierarchy Converter Deben Resolverse
Problemen Met XML Hiërarchie Converter Moeten Worden Opgelost
Należy Rozwiązać Problemy Z Konwerterem Hierarchii XML
I Problemi Con XML Hierarchy Converter Dovrebbero Essere Risolti
Problem Med XML Hierarchy Converter Bör Lösas
< br>
These three transformer domain experts have similar functionality in that they take serialized data such as an XML document and transform it into a hierarchical knowledge structure such as a set of properties. They also perform the reverse process.
Updated
Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!
To receiveFor more information about these commercial Siebel Air Compressor services and the use of XML in Siebel integration, see Siebel Bookshelf Version 8.> 0 XML Reference: Siebel Enterprise Application Integration > XML representation of integration object instances.< /p >
Can the XML hierarchy be converted to an XML document?
NOTE. There have always been other commercial conversion services such as the EAI Integration Object to XML Hierarchy Converter and EAI MimePropSet Converter that convert the two types of property sets. This document does not cover these types of Ripper Tools services, but they are discussed in the XML Reference.
Presentation
name=”aref1″>
