| Author |
Message
|
| tatyeong |
 Posted: Tue Jun 15, 2010 6:33 pm Post subject: Configurable Service for SAPConnection |
 |
|
Acolyte
Joined: 16 Apr 2010
Posts: 52
|
Hi,
I am trying to use configurable service for SAP connection details such as applicationHost, gatewayHost and client number.
Notice that there is no properties for SAP userID and password. Does that mean this has to be hardcoded in the inadapter and outadapter object, and be deployed along to Production eventually? |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Wed Jun 16, 2010 4:22 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
|
| Back to top |
|
|
| tatyeong |
| Posted: Wed Jun 16, 2010 7:25 am Post subject: |
|
|
Acolyte
Joined: 16 Apr 2010
Posts: 52
|
Thanks!
I had the impression that this command is more for database setting. Didn't know it can be used to set the user ID and password for SAP adapter. |
|
| Back to top |
|
|
| tatyeong |
| Posted: Thu Jun 17, 2010 2:02 am Post subject: |
|
|
Acolyte
Joined: 16 Apr 2010
Posts: 52
|
Here's what I did.
Remove the SAP user ID and password from the sap outadapter in the WMB toolkit.
Deploy to WMB runtime
Stop the broker
Run the command - mqsisetdbparms testbroker -n eis::test.outadapter -u userID -p password
Start the broker
When I tried to send a message through the message flow. I got this error
"BIP3450-throw a RecordNotFoundException--Exception in connecting to SAP:Incomplete logon data".
It seems that it could not pick-up the ID and password from the broker runtime? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jun 17, 2010 2:51 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Don't you have to tell the SAP adapter about 'test.outadapter' ?
With other nodes, this is done in the node properties.
I'd make sure that this is defined in the SOAP nodes and then redeploy.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| tatyeong |
| Posted: Thu Jun 17, 2010 5:57 pm Post subject: |
|
|
Acolyte
Joined: 16 Apr 2010
Posts: 52
|
| test.outadapter is the name given to the adapter object when it is being created in WMB toolkit, and is already defined in the node properties |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jun 17, 2010 9:31 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
There are instances (recorded here) where to get some things recognised by broker you have to restart at least twice.
Have you looked for these posts and seen if they might also apply to your situation?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| tatyeong |
| Posted: Tue Jun 22, 2010 4:05 am Post subject: |
|
|
Acolyte
Joined: 16 Apr 2010
Posts: 52
|
Apparently the 'eis::' in mqsisetdbparms testbroker -n eis::test.outadapter -u userID -p password
is the root cause. Once I remove that it is now able to read the user ID and password from the runtime |
|
| Back to top |
|
|
|
|
