| Author |
Message
|
| nimisha.parihar |
 Posted: Wed Dec 15, 2010 4:39 am Post subject: Confuguring port for HTTP requests |
 |
|
Apprentice
Joined: 03 Nov 2010
Posts: 41
|
| Can we configure MB to listen to any port other than the default port (7080) for HTTP requests ? |
|
| Back to top |
|
 |
| good_bee |
| Posted: Wed Dec 15, 2010 4:41 am Post subject: |
|
|
Newbie
Joined: 15 Nov 2010
Posts: 5
|
| yes you can configure what ever port you like for HTTP, HTTPS requests... |
|
| Back to top |
|
|
| nimisha.parihar |
| Posted: Wed Dec 15, 2010 5:33 am Post subject: |
|
|
Apprentice
Joined: 03 Nov 2010
Posts: 41
|
It'll be great if you can let me know how to do that as well.
I used the following command -
mqsichangeproperties <<broker_name>> -b httplistener -o HTTPSConnector -n port -v <<port to listen to>>
Finally stopped and restarted the broker. But no success.
I also tried with the command -
mqsichangeproperties <<broker_name>> -b httplistener -o HTTPSConnector -n explicitlySetPortNumber -v <<port to listen to>>
but this gives the following error -
BIP2051E: Broker <<brokername>>(UUID dbaf068a-2a01-0000-0080-a16dec7007a0) could not process an internal configuration message to completion, the problem was ca
used by 'httplistener'.
The configuration message could not be processed and was rejected.
Use the inserts within this message to determine the cause of the problem. Correct the broker's configuration and redeploy using the Message Brokers To
olkit, mqsideploy command or Config Manager Proxy application. Contact your IBM support center if you are unable to resolve the problem.
BIP2087E: Broker <<brokername>> 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, cont
act your IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP2051E: Broker <<brokername>>(UUID dbaf068a-2a01-0000-0080-a16dec7007a0) could not process an internal configuration message to completion, the problem was ca
used by 'Change : HTTPSConnector : explicitlySetPortNumber'.
The configuration message could not be processed and was rejected.
Use the inserts within this message to determine the cause of the problem. Correct the broker's configuration and redeploy using the Message Brokers To
olkit, mqsideploy command or Config Manager Proxy application. Contact your IBM support center if you are unable to resolve the problem.
BIP8036E: Negative response received.
This command sends an internal configuration message to the broker, the response received indicated that the internal configuration message was unsucces
sful.
Check that the WebSphere MQ transport is available. Check the system log for further information. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Dec 15, 2010 5:38 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| mqsichangebroker BROKER1 -P 8888 |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 15, 2010 6:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You may need to ensure that the biphttplistener stops as well as the broker. It doesn't always.
If you issue mqsistop, and still see the biphttplistener running, just kill it. |
|
| Back to top |
|
|
| nimisha.parihar |
| Posted: Wed Dec 15, 2010 11:51 pm Post subject: |
|
|
Apprentice
Joined: 03 Nov 2010
Posts: 41
|
thanks all..
The command works good  |
|
| Back to top |
|
|
| pdmenon |
| Posted: Thu Dec 16, 2010 12:16 am Post subject: |
|
|
Voyager
Joined: 05 Apr 2010
Posts: 80
|
Nimisha, Follow this.. it works like charm
mqsistop <brokername>
mqsichangebroker <brokername> -P <DesiredPortno>
mqsistart <brokername>
mqsireportproperties <brokername> -b httplistener -o HTTPConnector -a {You can see the updated properties} |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Dec 16, 2010 1:07 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
mqsireportbroker BROKER1
also shows the HTTP port, at least until WMB 7 when it doesn't (APAR opened). |
|
| Back to top |
|
|
| pdmenon |
| Posted: Thu Dec 16, 2010 2:11 am Post subject: |
|
|
Voyager
Joined: 05 Apr 2010
Posts: 80
|
| Yes zpat as you said, mqsireportbroker BROKER1 this also works fine for reporting.. |
|
| Back to top |
|
|
|
|
