A fix is available
APAR status
Closed as program error.
Error description
Oozie Workflow Invoker fails to work when Ooozie client is configured using kerberos authentication
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This problem only manifests itself when the Oozie client is configured to use kerberos authentication. **************************************************************** PROBLEM DESCRIPTION: When the Oozie client is configured to use kerberos authentication. The java layer produces an exception stack and an HTTP error even if https is specified and the correct port for the connection. **************************************************************** RECOMMENDATION: If kerberos authentication is in use for the Oozie client the patch will be required. ****************************************************************
Problem conclusion
n the problem case the java layer needs to use the AuthOozieClient interface in preference to the OozieClient interface. This change is programmed by setting the environment variable OOZ_AUTHM to the string -authmode. If not set the code behaves as previously.
Temporary fix
Comments
APAR Information
APAR number
JR58913
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
B50
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-12-22
Closed date
2018-02-20
Last modified date
2018-02-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
RB50 PSY
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.5"}]
Document Information
Modified date:
03 September 2021