| Author |
Message
|
| dosttumhara1810 |
 Posted: Tue Jan 11, 2011 2:42 am Post subject: mqsisetdbparms command |
 |
|
Voyager
Joined: 01 Dec 2010
Posts: 76
|
hi all,
I have created an .outbound SAP adapter and i want it to pick login UN and PWD from configurable service. I have defined a configurable service for this adapter with same name as that of adapter and set the UN and pwd using mqsisetdbparms command. But after trying it lot many times we found that .outbound adapter is not picking Un and pwsd from configurable service rather it is picking login details from .outbound adapter file present in the message set created from Adapter connection wizard..I am using MB v 6.1.0.4. Do i need any patches for that, i mean do i need to upgrade MB. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Jan 11, 2011 2:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Going to 6.1.0.8 is certainly a good idea.
Whether or not it will solve this particular issue is a different question.
The list of fixes included in 6.1.0.8 is available online, and should allow you to determine if there are any fixes that will likely apply.
But I'd start by double-checking the syntax you've used for the mqsisetdbparms command and make sure you've done all the right things to associate a security identity with this adapter connection. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Jan 11, 2011 3:03 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Is the DSN defined in the mqsisetdbparms the same name as the configurable serive and the same name as the adapter?
A user trace will show you all the properties passed to the SAP node at the time the node is called. Was this how you ascertained the problem in the first place?
_________________
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 |
|
|
| dosttumhara1810 |
| Posted: Tue Jan 11, 2011 4:19 am Post subject: Hi grandmaster |
|
|
Voyager
Joined: 01 Dec 2010
Posts: 76
|
i am using this command
mqsisetdbparms BRK1 -n eis::GetAddress.outbound -u <username> - p <****> |
|
| Back to top |
|
|
| dosttumhara1810 |
| Posted: Tue Jan 11, 2011 4:31 am Post subject: |
|
|
Voyager
Joined: 01 Dec 2010
Posts: 76
|
I am using these commands
$ mqsisetdbparms MQBRK -n eis::GetAddress.outadapter -u D1CWMBSc -p ********
BIP8071I: Successful command completion.
$
$ mqsireportproperties MQBRK -c SAPConnection -o AllReportableEntityNames -r
SAPConnection
GetAddress.outadapter
RFCTraceLevel='1'
RFCTraceOn='false'
RFCTracePath=''
applicationServerHost='test.centre1.abc.com client='120'
gatewayHost=''
gatewayService=''
rfcProgramID=''
systemNumber='00'
BIP8071I: Successful command completion.
$
Timestamps are formatted in local time, local time is GMT.
Trace written by version 6104; formatter version 6104
2011-01-11 12:17:34.336324 4137 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'GetAdd.MQInput'.
2011-01-11 12:17:34.415896 4137 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'GetAdd.MQInput' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2011-01-11 12:17:34.463916 4137 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'GetAdd.MQInput' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2011-01-11 12:17:34.518784 4137 UserTrace BIP6061I: Parser type ''XMLNSC'' created on behalf of node 'GetAdd.MQInput' to handle portion of incoming message of length '157' bytes beginning at offset '364'. Parser type selected based on value ''XMLNSC'' from previous parser.
2011-01-11 12:17:51.367192 4137 UserTrace BIP2231E: Error detected whilst processing a message in node 'GetAdd.SAP Request'.
The message broker detected an error whilst processing a message in node 'GetAdd.SAP Request'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2011-01-11 12:17:51.367272 4137 RecoverableException BIP3442E: An exception occurred in adapter node ''SAP Request'', which is using adapter component ''GetAddress.outadapter''..
This message broker node ''SAP Request'' attempted to process a message and communicate with an EIS using an adapter component ''GetAddress.outadapter''. An error occurred during this processing.
See the following messages for details of the error.
2011-01-11 12:17:51.367284 4137 RecoverableException BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is ''Exception in connecting to SAP:Incomplete logon data.''. This error was detected by the adapter. The following message describes the diagnostic information that is provided by the adapter ''Exception in connecting to SAP:Incomplete logon data.''.
Inspect the diagnostic information that is provided by the adapter. Further diagnostic information might be written to user trace. Inspect user trace for further information.
2011-01-11 12:18:17.626754 4137 UserTrace BIP2638I: The MQ output node 'GetAdd.MQOutput1' attempted to write a message to queue ''EPOS.FAILURE'' connected to queue manager ''''. The MQCC was '0' and the MQRC was '0'.
2011-01-11 12:18:17.626870 4137 UserTrace BIP2622I: Message successfully output by output node 'GetAdd.MQOutput1' to queue ''EPOS.FAILURE'' on queue manager ''''.
Threads encountered in this trace: |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Jan 11, 2011 4:32 am Post subject: Re: Hi grandmaster |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| dosttumhara1810 wrote: |
i am using this command
mqsisetdbparms BRK1 -n eis::GetAddress.outbound -u <username> - p <****> |
Ahh 
Try the mqsisetdbparms without the eis::
Here is a 'matching pair' of commands from my test broker.
| Code: |
mqsicreateconfigurableservice %1% -c SAPConnection -o getWorkOrder.outadapter -n ... -v ...
mqsisetdbparms %1% -n getWorkOrder.outadapter -u hello -p world
|
The broker name is passed as an argument.
_________________
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 |
|
|
| dosttumhara1810 |
| Posted: Tue Jan 11, 2011 5:11 am Post subject: |
|
|
Voyager
Joined: 01 Dec 2010
Posts: 76
|
Thanks a lot..Grand Master..You are really Grand master..Hats off to you.
  |
|
| Back to top |
|
|
| jbanoop |
| Posted: Fri Jun 24, 2011 7:45 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
Does anyone know if this is still the case (that we dont have to have the eis:: while issuing the mqsisetdbparms?) ?
The documentation still shows up with the eis::...
Env: 7.0 Fix Pack 1 on UNIX |
|
| Back to top |
|
|
| jbanoop |
| Posted: Fri Jun 24, 2011 7:49 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
|
| Back to top |
|
|
| bobbee |
| Posted: Wed Jul 15, 2015 1:33 pm Post subject: |
|
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
I am at IIB v9.0.0.3.1 Is this still true. the EIS:: did not work. So I tried this and still got an error. When I put the UID/PASSWORD in the adapter it work like a charm.
mqsicreateconfigurableservice BRKDEV01 -c SAPConnection -o CBS_INBOUND_GR_ROUTER2.inadapter -n applicationServerHost,client,rfcProgramID,SAPSystemID,systemNumber -v ibmfird0.portsmouth.uk.ibm.com,549,IIB-GR01,FIR,09
mqsisetdbparms BRKDEV01 -n eis::CBS_INBOUND_GR_ROUTER2.inadapter -u RBRODERICK -p backtothefuture
I get the following error:
| Code: |
BIP2087E: Broker 'BRKDEV01' 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 'CBS_Inbound_01' received an administration request that encountered an exception.
While attempting to process an administration request, an exception was encountered. No updates have been made to the configuration of the execution group.
Review related error messages to determine why the administration request failed.
BIP3414E: An attempt to attach the message flow node 'CBS_INBOUND_ROUTER_ADAPTER' in message flow 'CBS_IIB_INBOUND_GR_ROUTER_MF' to the adapter component 'CBS_INBOUND_GR_ROUTER2.inadapter' failed. Reason: com.sap.conn.jco.JCoException: (101) JCO_ERROR_CONFIGURATION: Server default repository destination FIR.527234 is invalid: Initialization of repository destination FIR.527234 failed: Parameter containing a user ID is missing: neither user nor user alias nor external ID nor SSO ticket nor X.509 certificate is specified.
The message flow node failed to register with the adapter component to receive events. The node cannot function correctly until it has attached to the adapter component.
Identify the adapter that is required by the node. Ensure that it is deployed to the correct execution group, and that the connection details on the .inadapter and the configurable service are correct. In addition, check the system log or Windows Event Viewer for further errors. If the problem persists, redeploy the message flow that contains the node and the adapter component that the node requires. The reason given in the error message might provide additional information about what caused the problem.
BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is 'com.sap.conn.jco.JCoException: (101) JCO_ERROR_CONFIGURATION: Server default repository destination FIR.527234 is invalid: Initialization of repository destination FIR.527234 failed: Parameter containing a user ID is missing: neither user nor user alias nor external ID nor SSO ticket nor X.509 certificate is specified'.
This error was detected by the adapter. The following message describes the diagnostic information that is provided by the adapter 'com.sap.conn.jco.JCoException: (101) JCO_ERROR_CONFIGURATION: Server default repository destination FIR.527234 is invalid: Initialization of repository destination FIR.527234 failed: Parameter containing a user ID is missing: neither user nor user alias nor external ID nor SSO ticket nor X.509 certificate is specified'.
Inspect the diagnostic information that is provided by the adapter. Further diagnostic information might be written to user trace. Inspect user trace for further information.
|
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jul 16, 2015 4:34 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
So did you try the mqsisetdbparms without the eis:: prefix? Did you remember to bounce the broker after you ran mqsisetdbparms?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bobbee |
| Posted: Thu Jul 16, 2015 7:22 am Post subject: |
|
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
| it was the bounce. I had to delete everything this AM and reset it back up along with 10 other QMGRS. When i get done with the scripts I am going to try it again. But I am sure it will work after the recycle. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jul 16, 2015 8:42 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
There is an RFE (can't remember the link) that is for a command that would extract ALL the broker config into an editable and re-usable file.
so of
mqsidumpbrokerconfig MYBROKER -f mybroker.xml
This would help you out I am sure.
You might like to consider voting for it....
_________________
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 |
|
|
| bobbee |
| Posted: Thu Jul 16, 2015 10:00 am Post subject: |
|
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
| do you get that now when you go to IBExplorer, connect to the broker and EXPORT config services ??????? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jul 16, 2015 10:32 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| bobbee wrote: |
| do you get that now when you go to IBExplorer, connect to the broker and EXPORT config services ??????? |
That is only part of it. What about all the HTTPConector settings, the WebUi settings, EG settings etc etc etc.
A dump of everything in a form that can be edited AND used to create a fully configured broker in seconds is what I'm on about.
With IIB V10 and its use of Cloud and other technologies like Docker, being able to spin up a fully configured broker in seconds is IMHO a big plus.
Sure you can install the runtime in 45 seconds but then things take longer.
That kinds defeats the idea of cloud elacticity IMHO.
_________________
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 |
|
|
|
|
