“EAI XML Write To File” Business Service- IgnoreCharSetConvErrors Property Not Working. (Doc ID 2186403.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Workflow - Version 8.1.1.14.10 [IP2014] and later
Information in this document applies to any platform.

Symptoms

On : 8.1.1.14.10 [IP2014] version, Siebel Workflow

“EAI XML Write to File” Business Service- IgnoreCharSetConvErrors property not working.

IgnoreCharSetConvErrors = false in "EAI XML Write to File" seems to no longer work after an application upgrade from 8.1.1.9 to 8.1.1.14.

A workflow process in our system is used to create XML file has an output.

We use Business Service "EAI XML Write to File" and the method name 'WriteEAIMsg' with the input Argument IgnoreCharSetConvErrors = false.

In 8.1.1.9 this Workflow should fail in creating .XML file with the following error:

Error Msg = Error invoking service 'EAI XML Write to File', method 'WriteEAIMsg' at step 'Write Siebel Msg to XML File'.(SBL-BPR-00162)
--
'EAI XML Write to File' service with method 'WriteEAIMsg' failed while generating XML to be written to file 'E:\MARCDATA\XML\XMLCREATION\RC\20141222\MARCXML_RC_1-MMV8RA.XML'.
(SBL-EAI-04266)
--
The XML hierarchy cannot be converted to an XML document.(SBL-EAI-04112)
--
Character '0x000b' cannot be represented in XML(SBL-EAI-00245)

Instead of workflow failing, our workflow error exception handling routine would create a custom error log for saving any control character (0x000b) found in the SR.

After we upgraded Siebel from 8.1.1.9 to 8.1.1.1.14, the workflow process is no longer generating the custom error log, instead it is replacing the question mark symbol (?) and successfully creating XML file.

Our requirement is that if there is any control characters/special characters found in the SR, we don’t want to process and send the SR to external system.

We like to know what changes in Siebel is replacing the control character with ? in 8.1.1.14.
Why does it seem as if IgnoreCharSetConvErrors is set to "True" after the upgrade when it is indeed set to False. This worked as expected in 8.1.1.9

I am attaching the old custom error log file, which system used to create in 8.1.1.1.9 and the new XML file which is created in 8.1.1.14 with the character "?"

We currently are running 8.1.1.14 patchset 10 in development and test and 8.1.1.14 in patchset 6 in Production.

 


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms