Author |
Message
|
Shyam Kishor |
Posted: Thu Sep 10, 2015 3:04 am Post subject: How to use remote CCDT file in IIB9 as MQ service. |
|
|
Newbie
Joined: 10 Sep 2015 Posts: 4
|
Firstly I have updated CCDT file in a remote system after that I am using that CCDT file in an another system as MQ service.I am getting exception while configuring the CCDT file on Console like unable to process configuration message and problem caused by BrokerRegistry.
C:\Windows\system32>mqsichangeproperties IB9NODE -o BrokerRegistry -n mqCCDT -v "C:\Users\miracle\Desktop
AMQCLCHL.TAB"
BIP2051E: Broker IB9NODE (UUID 63d3c6ee-7311-4ad5-b1af-328323bc9e46) could not process an internal config
ration message to completion, the problem was caused by 'brokerregistry'.
The configuration message could not be processed and was rejected.
Other thing is that without configuring I am able to deploy the flow on integration node but it's not increasing the number of OPEN INPUT COUNT in MQ Explorer so we can't trigger the flow. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 10, 2015 4:18 am Post subject: Re: How to use remote CCDT file in IIB9 as MQ service. |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Shyam Kishor wrote: |
Firstly I have updated CCDT file in a remote system |
Updated how? What tool / steps did you follow?
Shyam Kishor wrote: |
C:\Windows\system32>mqsichangeproperties IB9NODE -o BrokerRegistry -n mqCCDT -v "C:\Users\miracle\Desktop
AMQCLCHL.TAB"
BIP2051E: Broker IB9NODE (UUID 63d3c6ee-7311-4ad5-b1af-328323bc9e46) could not process an internal config
ration message to completion, the problem was caused by 'brokerregistry'.
The configuration message could not be processed and was rejected. |
There's no more text than that? No accompanying events in the Windows event log?
Shyam Kishor wrote: |
Other thing is that without configuring I am able to deploy the flow on integration node but it's not increasing the number of OPEN INPUT COUNT in MQ Explorer so we can't trigger the flow. |
So there's no client definition and you're surprised the flow isn't connecting to the queue? Functioning as designed there. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
smdavies99 |
Posted: Thu Sep 10, 2015 4:23 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Assuming that IB9NODE refers to a V9 Broker then...
Are you sure that this setting is available for IIB V9?
I can see it there in V10 but not in 9.0.0.3
For V10
Code: |
E:\IBM\IIB\10.0.0.1>mqsireportproperties V10BROKER -o BrokerRegistry -a
BrokerRegistry
uuid='BrokerRegistry'
brokerKeystoreType='JKS'
brokerKeystoreFile=''
brokerKeystorePass='brokerKeystore::password'
brokerTruststoreType='JKS'
brokerTruststoreFile=''
brokerTruststorePass='brokerTruststore::password'
brokerCRLFileList=''
httpConnectorPortRange=''
httpsConnectorPortRange=''
brokerKerberosConfigFile=''
brokerKerberosKeytabFile=''
allowSSLv3=''
mqCCDT=''
modeExtensions=''
operationMode='enterprise'
adminMessageLogging=''
mqKeyRepository=''
shortDesc=''
longDesc=''
BIP8071I: Successful command completion.
E:\IBM\IIB\10.0.0.1>
|
But for a V9 broker
Code: |
W:\IBM\MQSI\9.0.0.3>mqsireportproperties V9BROKER -o BrokerRegistry -r
BrokerRegistry
uuid='BrokerRegistry'
brokerKeystoreType='JKS'
brokerKeystoreFile='D:\SSL_Keystore\V9BROKER.jks'
brokerKeystorePass='brokerKeystore::password'
brokerTruststoreType='JKS'
brokerTruststoreFile='D:\SSL_Keystore\V9BROKER.jks'
brokerTruststorePass='brokerTruststore::password'
brokerCRLFileList=''
httpConnectorPortRange=''
httpsConnectorPortRange=''
brokerKerberosConfigFile=''
brokerKerberosKeytabFile=''
modeExtensions=''
operationMode='enterprise'
shortDesc=''
longDesc=''
BIP8071I: Successful command completion.
W:\IBM\MQSI\9.0.0.3>
|
_________________ 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 |
|
 |
mqjeff |
Posted: Thu Sep 10, 2015 4:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
IIB v10 is the only version of IIB that can use a client connection to it's queue manager.
In fact, outside of JMS, IIB v9 and earlier can't use a client connection for anything. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 10, 2015 4:32 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
smdavies99 wrote: |
Assuming that IB9NODE refers to a V9 Broker then...
Are you sure that this setting is available for IIB V9? |
Good catch - I missed the subject line!
You can't establish a client connection in IIBv9. The feature's new for IIBv10.
 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Shyam Kishor |
Posted: Thu Sep 10, 2015 6:10 am Post subject: How to use remote CCDT file in IIB9 as MQ service. |
|
|
Newbie
Joined: 10 Sep 2015 Posts: 4
|
In IIB9 We have option to establish the client connection to it's queue manager.
MQ Input node->Basic properties->Browse MQ servies->Create a new service->select type of connection as Remote client connection using CCDT file.
Coming to IIB10 ---
I also tried with IIB10 where able to configure CCDT file and also command executed successfully but I am getting exception like unable access configuration message when deploying the Flow . |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Sep 10, 2015 6:20 am Post subject: Re: How to use remote CCDT file in IIB9 as MQ service. |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Shyam Kishor wrote: |
In IIB9 We have option to establish the client connection to it's queue manager. |
No.
You don't.
You have the option to configure an MQ Service application to talk to a remote queue manager.
In every version before v10, the Broker/Integration Server MUST run on the same machine as an MQ queue manager. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
|