OSB 11g: Unable to Send Message to MQ after Configuring MQ Channel Security Exit (Doc ID 1576238.1)

Last updated on OCTOBER 12, 2015

Applies to:

Oracle Service Bus - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

Customer is using IBM configuration known as Channel security exit
http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fap12500_.htm
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=%2Fcom.ibm.mq.csqzae.doc%2Fic17470_.htm

Channel security exit is implemented via third party tool known as Capitalware.

http://www.capitalware.biz/mqausx_overview.html

Capitalware authenticates the user's UserID and Password (and possibly Domain Name) against the server's native OS system (or domain controller) or a remote LDAP server. Basically Capitalware secure access of MQ channels via username/password. Customer is using client-side security exit.
Customer created MQ connection resource and a business service for sending message to the MQ Queue. Customer configured username and password in service account required by security channel exit and associated it with MQ connection.  Refer to OSB_configuration .docx. But while connecting to MQ queue manager, OSB is sending a blank password with the proper username.

Changes

 Configuring MQ channel security exit 

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