MQSeries.net :: View topic

saibaba · Posted: Fri Aug 31, 2012 7:22 am Post subject:

My Goal is to store username and password in Broker using policy sets and bindings. I am using a Soap requestnode in my message flow.
I follwed all the instructions from the below link

http://www.ibm.com/developerworks/websphere/library/techarticles/1008_fan/1008_fan.html

When I try to deploy the code to the execution group I get thebelowerror. I am trying for basic authentication only.

egin running task [Deploying [ADVPOC.bar] to execution group [Sai]]

BIP2087E: Broker MB7BROKER was unable to process the internal configuration message.

The entire internal configuration message failed to be processed successfully.

Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.

BIP4041E: Execution group 'Sai' received an invalid configuration message. See the following messages for details of the error.

The broker was asked to deploy a message flow which contained properties that were not recognized by the broker. This typically results from a message flow requiring a version or type of node that is not supported by the broker installation.

Check that the message flow is only using properties or nodes that are supported on the broker. Check that all necessary user-defined extensions are installed and that they are of a version that is compatible with the message flow.

BIP3726E: Failed to setup SOAP transport for node createDocument_ObjectService_prod.Request.

The SOAP nodes rely on the configuration of the SOAP transport layer within the broker, and this has not been initialised correctly. The node will not be operational until the problems have been corrected.

Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3728E: Configuration of WS-Security layer using policy set 'adv' and policy set binding 'consumeradv' failed.

WS-Security configuration requires correctly initialised policy set and policy set binding information in order to succeed. An error has occurred whilst attempting to use policy set 'adv' and policy set binding 'consumeradv'. Common causes are:
1: Either the policy set name or policy set binding name is missing from the node (or flow) configuration.
2: If X.509 tokens are being used, including implicit usage such as signing or encryption, the keystore and/or truststore is not be set correctly.
However, this may be an internal error, possibly due to a faulty installation. A review of the exception text may indicate a solution.

Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3727E: com.ibm.wsspi.wssecurity.core.SoapSecurityException: CWWSS5381E: Unable to resolve the expected refe... (data of len 127 truncated)

The SOAP nodes are built on top of the broker WS-Security layer, and this layer has returned a configuration exception, the text of which is included in the message.

Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3701E: A Java exception was thrown whilst calling the Java JNI method 'method_com_ibm_broker_axis2_Axis2NodeRegistrationUtil_registerSyncRequestNode'. The Java exception was 'BIP3726E: com.ibm.broker.axis2.MbSoapException: Failed to setup Axis2'. The Java stack trace was 'Frame : 0 com.ibm.broker.axis2.MbSoapException: Failed to setup Axis2
'.

Correct the error, and if necessary redeploy the flow.

The task was unsuccessful: The deployment was unsuccessful. Check error messages above for explanation.