Additional Steps To Perform On The javacontainerN Directory After Applying A Siebel PatchSet That Includes Fixes To The Java Web Container
(Doc ID 2274640.1)
Last updated on APRIL 02, 2019
Applies to:Siebel CRM - Version 16.0 [IP2016] to 16.19 [IP2016] [Release V16]
Information in this document applies to any platform.
In Siebel IP2016 release, there is a Java Web Container which provides additional functionality/support for SHA2 certificates as well as Java 64 bit support for Siebel application. The Java Web Container includes various files under the /siebsrvr/javacontainer/ directory.
There may be cases where a defect occurs with the Java Web Container, Siebel provides a patchset to address it. However, in addition to the Siebel PatchSet installation files, the Java Web Container files under the /siebsrvr/javacontainer/ directory needs to be updated with those from the PatchSet.
In cases as such, some additional steps need to be performed manually on the Java Web Container files under the /siebsrvr/javacontainer/ directory after the patchset installation is completed.
For instance, a recent behavior in document SHA2 JAVACONTAINER UTFDATAFORMATEXCEPTION INVALID BYTE 2 SBL-EAI-00247 (Doc ID 2270804.1), with bug 25667276 (SHA2 JAVACONTAINER UTFDATAFORMATEXCEPTION INVALID BYTE 2 SBL-EAI-00247) has been reported, where the javacontainer convert special characters to UTF-16 whilst keeping all the rest, including XML prolog in UTF-8. As a result, the Siebel XML converter called automatically upon receiving an outbound web service RESPONSE fails.
In this occurrence, the bug 25667276 is fixed in PatchSet 16.13. However, the fix also requires the /javacontainer/ directory and files be updated with those from the Patchset.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document