| Author |
Message
|
| northwilks |
 Posted: Thu Nov 21, 2013 10:53 am Post subject: SAP mqsisetdbparms password case sensitive |
 |
|
Novice
Joined: 11 Feb 2013
Posts: 13
|
We are running WMB V7 fp5
Attempting to deploy a passthru adapter SAP >> Broker, so inadapter, for the first time to test. I have this successfully working on a development system.
I used mqsisetdbparms to establish the password.
mqsisetdbparms MDERPTST1BRK -n eis::A1.idocpassthrough.inadapter -u userid -p xxxxx
Also created configurable service.
On deploy to TEST I receive a fail.
BIP3414E: An Attempt to attach the message flownode xxx, in message flow on adapter component 'A1.idocpassthrough.inadapter' failed. Reason code jco connection (103) JCO_ERROR_LOGON_FAILURE: Unable to get to repository
(I typed that since I was only supplied a picture, there was more)
Based on my investigation, it appears to be a userid password issue?
Which means my mqsisetdbparms is not working?
I found IC54904: ERROR CONNECTING TO SAP SYSTEM USING MIXED CASE PASSWORD, which talks about passwords being case sensitive. But is this true only for IN adapters? because with the deploy of a OUTadapter which used a second mqsusetdbparms worked. both had lower case password on command.
You'd think I'd just try this but my deploy must be done by another group which takes at least 24 hr turnaround and all steps must be pre-defined. So no realtime debugging. And it works on Dev system. If not working by Nov 26, no chance of retry until Jan.
The main difference between Dev and Test system, on our TEST system the broker runs on a separate server from the SAP server. But I do not think that is the cause.
I also had the program id registered on SAP server. I had hoped this would 'auto register' but I initially thought that was my issue and had it done (by another group). No effect on fail during deploy of passthru.
Last but of info, I used a different userid when using the adapter creation wizard so in the BTK looking at adapter I see the original ID. But I assume this is overidden by the mqsisetdbparms command.
Any advice would be appreciated. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Thu Nov 21, 2013 11:08 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Did you restart the execution group after you ran mqsisetdbparms?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| northwilks |
| Posted: Thu Nov 21, 2013 11:55 am Post subject: |
|
|
Novice
Joined: 11 Feb 2013
Posts: 13
|
Update: I just verified that passwords on our SAP are case sensitive.
Therefore the mqsisetdbparms should have worked with lowercase password.
So maybe the mqsisetdbparms is not overriding what is on the adapter in the inadapter node set up during adapter creation.
Is there a way to see what userid is being used during the deploy? |
|
| Back to top |
|
|
| northwilks |
| Posted: Thu Nov 21, 2013 12:00 pm Post subject: |
|
|
Novice
Joined: 11 Feb 2013
Posts: 13
|
'Did I restart execution group'
This was mt seq
Create exec group
mqsisetdbparms
Create config service
Deploy Message flow
I guess thant mean NO. I ?incorrectly? assumed as long as I did it before the deploy I would be okay. But since I did not stop and restart it, it would use the userid and password on the adapter as defined?
It is the start/create of execution group where the dbparms get picked up? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Nov 21, 2013 12:05 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
| northwilks |
| Posted: Thu Nov 21, 2013 12:15 pm Post subject: |
|
|
Novice
Joined: 11 Feb 2013
Posts: 13
|
Thank you.
Sorry for not catching that.
I will schedule another deploy to stop and start the execution group.
Can I do the mqsisetdbparms before I even create the execution group on my deploy to Production?
Avoid a restart?
So...
mqsisetdbparms
create execution group
create config service
deploy message flow |
|
| Back to top |
|
|
|
|
