| Author |
Message
|
| smdavies99 |
 Posted: Tue Sep 17, 2013 1:18 am Post subject: GlobalCache and Multiple Networks |
 |
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
The answer to this is probably staring me in the face but....
Broker 8.0.0.2, Server 2008 R2 Fully Patched
My dev system is a VM with TWO network interfaces.
| Code: |
C:\scripts\wbiscripts\devbrkr>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . : localdomain
Link-local IPv6 Address . . . . . : fe80::58b5:2578:f045:dc71%13
IPv4 Address. . . . . . . . . . . : 192.168.109.153
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : localdomain
Link-local IPv6 Address . . . . . : fe80::645c:3f4f:e17b:1cf8%11
IPv4 Address. . . . . . . . . . . : 192.168.98.239
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.98.2
Tunnel adapter isatap.localdomain:
|
If I specify
| Code: |
| <broker name="DEVBRKR" listenerHost="192.168.98.239"> |
in the policy xml file AND then associate the broker with it by:-
| Code: |
mqsichangebroker DEVBRKR -b \\192.168.98.239\scripts\cache\DEVBRKR_Cache_Policy.
xml
BIP8071I: Successful command completion.
|
The command only works if the second network config is disabled( 192.168.109.153)
If I enable the adapter and then try to start the broker I get the following messages in the eventlog.
| Code: |
Log Name: Application
Source: WebSphere Broker v8002
Date: 9/17/2013 10:08:53 AM
Event ID: 7195
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Broker8002
Description:
( DEVBRKR.EG_1 ) The policy in the policy file ''\\192.168.98.239\scripts\cache\DEVBRKR_Cache_Policy.xml'', specified for the cache manager, is invalid.
The broker, with name ''DEVBRKR'' and listener host ''192.168.109.153'', is not defined in the policy.
The policy must include a definition for this broker.
The broker configuration has not been changed.
Ensure that this broker is defined in the policy.
If the broker is already defined, check that the name and listener host specified for this broker match the name and listener host specified in the policy.
|
The questions are:-
1) what is the best way to create this environment where you have multiple network adapters.
2) The target system is a MSCS Cluster (broker in Active Passive mode). How can I overcome this apparent problem with IP binding? should I try to do it with the cluster IP address.
_________________
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 |
|
 |
| jhart |
| Posted: Tue Sep 17, 2013 6:00 am Post subject: |
|
|
Novice
Joined: 12 Dec 2012
Posts: 19
Location: IBM Hursley, UK
|
On point 1 :
| Code: |
| mqsichangeproperties DEVBRKR -o CacheManager -n listenerHost -v 192.168.98.239 |
This is described in the following topic: http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/topic/com.ibm.etools.mft.doc/bn23787_.htm
| Quote: |
| The broker names and listener hosts specified in the policy must match the values defined for the brokers. |
The broker level property tells the cache components which hostname to bind to. The value in the policy file is just for lookup - imagine if you had brokers called DEVBRKR on multiple machines, each broker needs to be able to identify itself in the policy file.
There is an affinity between cache components and hostnames / IP addresses. If this is all on one machine, you can safely use "localhost". If not, you need to be explicit (each catalog server needs to know about itself and all other catalog servers before starting up).
There's some extra capability in this area, in IIBv9, specifically to allow container servers to come up on a choice of hostnames. See:
http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.etools.mft.doc/be23815_.htm) |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Sep 17, 2013 6:28 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I tried to use localhost
| Quote: |
policy.xml file
<broker name="DEVBRKR" listenerHost="127.0.0.1">
|
this is the output
| Code: |
C:\scripts\wbiscripts\devbrkr>mqsideletebroker DEVBRKR
BIP8071I: Successful command completion.
C:\scripts\wbiscripts\devbrkr>create_DEVBRKR.bat create
mqsicreatebroker DEVBRKR -i wbiuser -a S1taadmin -q DEVBRKR
AMQ8110: WebSphere MQ queue manager already exists.
BIP8071I: Successful command completion.
mqsichangebroker DEVBRKR -b none -r 12809-12830
mqsichangebroker DEVBRKR -b \\127.0.0.1\scripts\cache\DEVBRKR_Cache_Policy.xml
BIP7195E: The policy in the policy file ''\\127.0.0.1\scripts\cache\DEVBRKR_Cach
e_Policy.xml'', specified for the cache manager, is invalid.
The broker, with name ''DEVBRKR'' and listener host ''192.168.109.153'', is not
defined in the policy.
The policy must include a definition for this broker.
The broker configuration has not been changed.
Ensure that this broker is defined in the policy.
If the broker is already defined, check that the name and listener host specifie
d for this broker match the name and listener host specified in the policy.
BIP8081E: An error occurred while processing the command.
An error occurred while the command was running; the command has cleaned up and
ended.
|
Using localhost in place of 127.0.0.1 fails in the same way. The broker is still trying to bind to the ip address of the second adapter.
_________________
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 |
|
|
| jhart |
| Posted: Tue Sep 17, 2013 6:31 am Post subject: |
|
|
Novice
Joined: 12 Dec 2012
Posts: 19
Location: IBM Hursley, UK
|
Hi - please read the first bit of my reply first 
You can use localhost - but you have to set it at the broker level as well as in the policy file:
| Code: |
mqsichangeproperties DEVBRKR -o CacheManager -n listenerHost -v localhost
<broker name="DEVBRKR" listenerHost="localhost"> |
|
|
| Back to top |
|
|
| jhart |
| Posted: Tue Sep 17, 2013 6:34 am Post subject: |
|
|
Novice
Joined: 12 Dec 2012
Posts: 19
Location: IBM Hursley, UK
|
Sorry - those should be in two different code blocks, for clarity:
| Code: |
| mqsichangeproperties DEVBRKR -o CacheManager -n listenerHost -v localhost |
| Code: |
| <broker name="DEVBRKR" listenerHost="localhost"> |
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Sep 17, 2013 6:39 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
How do you specify the policy file in your solution?
AFAIK, somewhere I need to do a
mqsichangebroker <brokername> -b <path to policy file>
Is this to be done after the mqsichangeproperties you showed in your reply?
_________________
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 |
|
|
| jhart |
| Posted: Tue Sep 17, 2013 6:51 am Post subject: |
|
|
Novice
Joined: 12 Dec 2012
Posts: 19
Location: IBM Hursley, UK
|
Yes - that's correct. Update the broker-level listenerHost property first. Then set the policy file. Apologies for not making that clear.
By the way - to reduce restarts, you can set the policy file with mqsichangeproperties too - and then restart afterwards :
| Code: |
mqsichangeproperties DEVBRKR -o CacheManager -n listenerHost -v localhost
mqsichangeproperties DEVBRKR -o CacheManager -n policy -v \\127.0.0.1\scripts\cache\DEVBRKR_Cache_Policy.xml
mqsireload DEVBRKR |
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Sep 17, 2013 6:51 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Ok. I think I've got it
1) create broker
2) start broker
3) mqsichangebroker DEVBRKR -o CacheManager -n listenerHost -v localhost
4) stop broker
5) mqsichangebroker DEVBRKR -b \\127.0.0.1\scripts\cache\DEVBRKR_Cache_Policy.xml
| Code: |
C:\scripts\wbiscripts\devbrkr>mqsireportbroker DEVBRKR
BIP8927I: Broker Name 'DEVBRKR'
Last mqsistart path = 'C:\IBM\MQSI\8.0.0.2'
mqsiprofile install path = 'C:\IBM\MQSI\8.0.0.2'
Work path = 'C:\ProgramData\Application Data\IBM\MQSI'
Broker UUID = ''
Process id = '0'
Queue Manager = 'DEVBRKR'
User lil path = ''
User exit path = ''
Active user exits = ''
LDAP principal = ''
LDAP credentials = ''
ICU converter path = ''
Trusted (fastpath) Queue Manager application = 'false'
Configuration change timeout = '300' seconds
Internal configuration timeout = '60' seconds
Statistics major interval = '60' minutes
Operation mode = 'advanced'
Fixpack capability level = '' (effective level '8.0.0.1')
Broker registry format = 'v8.0'
Administration security = 'inactive'
Multi-instance Broker = 'false'
Shared Work Path = 'none'
Start as WebSphere MQ Service = 'undefined'
HTTP listener port = '7080'
Cache manager policy = '\\127.0.0.1\scripts\cache\DEVBRKR_Cache_Policy.xml'
Cache manager port range = '2800-2819'
BIP8071I: Successful command completion.
C:\scripts\wbiscripts\devbrkr>
|
slightly convoluted but I think this is the way to do 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 |
|
|
| jhart |
| Posted: Tue Sep 17, 2013 7:10 am Post subject: |
|
|
Novice
Joined: 12 Dec 2012
Posts: 19
Location: IBM Hursley, UK
|
Note - don't get confused between mqsichangebroker and mqsichangeproperties.
You cannot set the listenerHost with mqsichangebroker. Policy file can be set with either.
The incantation in my previous post uses mqsichangeproperties for both (assumes the broker is already running) and reduces the number of restarts. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Sep 17, 2013 8:10 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Thanks. I've got it now.
_________________
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 |
|
|
|
|
