|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Error placing in Queue - Wrong type in both mapped and sourc |
« View previous topic :: View next topic » |
Author |
Message
|
akidase |
Posted: Wed Nov 05, 2014 10:09 pm Post subject: Error placing in Queue - Wrong type in both mapped and sourc |
|
|
Centurion
Joined: 10 Jan 2011 Posts: 124
|
Code: |
Function:CHARACTER:ImbSecurityManager::retrieveIdentityToPropagate
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2720
Text:CHARACTER:Wrong type in both mapped and source token
Insert
Type:INTEGER:5
Text:CHARACTER:username, usernameAndPassword
Insert
Type:INTEGER:5
Text:CHARACTER: |
I am not getting what the error is.
Ouput node - Pass All is placed for Message Context.
I tried the below since iibadm is the user who runs Broker.
setmqaut -m IIB_DEV_01 -t qmgr +all
setmqaut -m IIB_DEV_01 -n Security_Profile1 -t q -p iibadm +setall
setmqaut -m IIB_DEV_01 -n Security_Profile1 -t q -p iibadm +setid
Since the message has mqm user
setmqaut -m IIB_DEV_01 -n Security_Profile1 -t q -p mqm +setall
setmqaut -m IIB_DEV_01 -n Security_Profile1 -t q -p mqm +setid
Security Profile1 doesn't have any details. All are set to None.
Let me know of any other details required. |
|
Back to top |
|
 |
martinb |
Posted: Thu Nov 06, 2014 12:12 am Post subject: |
|
|
Master
Joined: 09 Nov 2006 Posts: 210 Location: UK
|
So I guess you have MQOutput node with property "Message Context" set to "Pass All", which means the Integration Bus with be setting the MQPMO_PASS_ALL_CONTEXT option of the MQPMO of the MQI.
Part of the context being set will be the MQ user, and when you have a security profile associated with the node that defines that the user should be taken from the Properties tree, using the fields "IdentityMapped.." or "IdentityMapped..".
In your case the error is telling you that you have not provided a suitable "Identity..." in the Properties tree. There needs to be one with "Identity...Type" of "username" or "usernameAndPassword"
If you don't want to override the user identity, and have the user identity the Broker is running as propagated then you should not be associating a Security Profile with the node. Note that if you have associated a Security Profile with the flow, it will apply to all nodes, unless they explicitly set a different profile. |
|
Back to top |
|
 |
akidase |
Posted: Thu Nov 06, 2014 12:23 am Post subject: |
|
|
Centurion
Joined: 10 Jan 2011 Posts: 124
|
Martin, Thanks for your reply.
I didn't set any security profiles AFAIK..I checked in Broker - right click.. properties->security..
There wasn't anything there. |
|
Back to top |
|
 |
akidase |
Posted: Sun Nov 09, 2014 12:46 am Post subject: |
|
|
Centurion
Joined: 10 Jan 2011 Posts: 124
|
It seems to work if we change Properties and set "usernameAndPassword" to the message's IdentitySourceType right before it reached the ErrorQueue output node.
Any idea why this is happening. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|