| Author |
Message
|
| lbart |
 Posted: Fri Jul 10, 2009 5:47 am Post subject: Config Manager Repositoy Access in Unix - BERNARD |
 |
|
Novice
Joined: 18 May 2006
Posts: 13
Location: Manchester
|
Hi,
Can anyone tell me how to access Bernard on a Unix system. I have done some research and everything I find seems to tell you how to access Bernard from a Windows perspective using the mqsicmrv command, can't find anything that explains how to access this on Unix. tried the mqsicmrv command on Unix but I just get an error:
The java class is not found: com.ibm.broker.config.ConfigManagerException
Any help would be much appreciated.
Thanks |
|
| Back to top |
|
 |
| nvenkatesh |
| Posted: Fri Jul 10, 2009 6:03 am Post subject: |
|
|
Apprentice
Joined: 29 Jan 2007
Posts: 45
|
Simple workaround if you just want to view it and you dont have some sort of automation programs built around this command.. Just copy bernard from the unix machine to windows and access it from there.
Please also share with us what you are going to do with that..
Thanks,
Venkatesh |
|
| Back to top |
|
|
| lbart |
| Posted: Fri Jul 10, 2009 6:12 am Post subject: |
|
|
Novice
Joined: 18 May 2006
Posts: 13
Location: Manchester
|
Hi thanks yes I already thought of doing that but was hoping for an easier method. We currently have a situation where the Config manager is waiting for a Outstanding deploy to complete and have tried everything to remove this using various methods. The only thing left to try is to check for the entry in the Config Manager Repository (Bernard) and remove it from the table. Other wise we will have to rebuild the broker and config manager.
Just for info this is WMB v6.1 on Unix AIX5.3, both Config Manager and Broker are on the Unix Box.
Thanks |
|
| Back to top |
|
|
| dk27 |
| Posted: Fri Jul 10, 2009 6:19 am Post subject: |
|
|
Acolyte
Joined: 28 Apr 2008
Posts: 51
|
| Use configmgr proxy. It is safe and simple way to check what in the config manager database... |
|
| Back to top |
|
|
| lbart |
| Posted: Fri Jul 10, 2009 6:29 am Post subject: |
|
|
Novice
Joined: 18 May 2006
Posts: 13
Location: Manchester
|
Hi, Yes I am currently in the Config Manager Proxy on my windows machine which runs my toolkit and am also in the Config Manager Repository Viewer and neither allows me to see Bernard on the Unix box. The Config Manager Proxy list info about the execution groups and flows deployed and the Config Manager Repository Viewer will not make a remote connection to the Config Manager.
Do you have anymore info on how to use the Config Manager Proxy to view and edit Bernard as I can't see it. It does have an option to cancel outstanding deploys which I have tried but this is just doing the same as cancelling a deploy using the mqsideploy command as far as I can tell.
Thanks |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 10, 2009 6:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The ConfigMgr Proxy API Exerciser will allow you to connect to a remote ConfigMgr, including one on Unix. It does not run in the Toolkit.
If you are having trouble running standard mqsi* commands on a unix platform, you need to ensure that you have sourced the mqsiprofile in your current shell first.
If you are attempting to directly manipulate the ConfigMgr's private internal datastore, then you should not be doing so outside of the supervision of the Message Broker support team.
What are you actually trying to do with the mqsicmrv command? |
|
| Back to top |
|
|
| nvenkatesh |
| Posted: Fri Jul 10, 2009 6:48 am Post subject: |
|
|
Apprentice
Joined: 29 Jan 2007
Posts: 45
|
| lbart wrote: |
| Do you have anymore info on how to use the Config Manager Proxy to view and edit Bernard as I can't see it. |
Neither mqsicmrv nor configmgr proxy provide you the facility to edit Bernard directly.
Only the config manager proxy allows you to "indirectly" edit the db in the sense you can send commands like cancel deploy, start flow, etc via its interface.
Thanks,
Venkatesh |
|
| Back to top |
|
|
| lbart |
| Posted: Fri Jul 10, 2009 6:55 am Post subject: |
|
|
Novice
Joined: 18 May 2006
Posts: 13
Location: Manchester
|
mqjeff, thanks for your response, i will answer your points.
1) I know the ConfigMgr Proxy API allows remote connections, I mention above I have done this, its the Config Manager Repository Viewer which doesn't.
2) I know it doesn't run in the Toolkit.
3) I am not having trouble running mqsi commands.
4) I am attempting to directly manipulate the Config Mgr's Repository. It used to be easy with 2.1 as it was a DB2 database and have solved this issue previously in 2.1.
Ventatesh, thanks for your response, I have tried the commands from the CMP API interface without success.
Here is the error I recieve when trying to delete a msgflow out of an execution group:
(10/07/09 15:45:41) (Log entry) {message=BIP1510E, detail=BIP1510E: Deployment failed; a deployment is already in progress to broker 'DVMB02'.
A request was issued for the Configuration Manager to deploy to broker 'DVMB02'. This request cannot be
processed because the Configuration Manager has not yet received a response to a previous deployment
request submitted to that broker. To ensure that the deployed configuration is consistent with the
reported configuration, the more recent deployment request has been discarded.
If you are deploying the publish/subscribe topology or topic hierarchy, no brokers in the domain will
have received the new deployment message. There can be no outstanding deployments in the domain before
deployment of such a configuration can occur.
Wait for the outstanding deployment to complete before retrying the operation. Check the Event Log editor
or Configuration Manager Proxy to verify that all responses to the outstanding deployment have been received
and processed.
If the outstanding deployment request does not complete in a suitable period of time, check that all brokers
exist and are running, all WebSphere MQ queue managers are running, and all channels between queue managers
are started. Check that deployment messages have been correctly delivered to the target brokers, and have
not been put to the dead letter queue. Correct all problems that you find.
If, following these actions, the deployment does not complete, cancel the deploy operation by using one of
the following methods:
1. Right-click the broker in the workbench and then selecting the 'Cancel Deployment' option, or 2.
Run the mqsideploy command with the -c option, or
3. Include the BrokerProxy.cancelDeployment() method in a Configuration Manager Proxy application.
If you cancel the deployment operation, the cancelation does not stop the deployment message from being
processed by the broker. It forces the Configuration Manager to remove any outstanding deployment locks
that might be associated with the broker. If a broker subsequently processes a deployment message that
you have canceled in this way, the deployed configuration might become inconsistent with the reported
configuration., source=ConfigMgr, timestamp=Fri Jul 10 15:43:00 BST 2009}
(10/07/09 15:45:41) (Reference property) parent.uuid=c27e344e-1a01-0000-0080-c2344f5f36c5
(10/07/09 15:45:41) (Reference property) uuid=9696344e-1a01-0000-0080-c2344f5f36c5
(10/07/09 15:45:41) (Reference property) commsmessage.lastinbatch=true
(10/07/09 15:45:41) (Reference property) configmanagerproxy.osname=Windows XP
(10/07/09 15:45:41) (Reference property) deployment.identifier=cfsdom\i14804
(10/07/09 15:45:41) (Reference property) deployment.type=delta
(10/07/09 15:45:41) (Reference property) userid=i14804
(10/07/09 15:45:41) (Reference property) configmanagerproxy.hostname=cfsdom
(10/07/09 15:45:41) (Reference property) commsmessage.configobjecttype=ExecutionGroup
(10/07/09 15:45:41) (Reference property) commsmessage.operationtype=deploy
(10/07/09 15:45:41) (Reference property) configmanagerproxy.noeventlog=false
(10/07/09 15:45:41) <---- cmp.exerciser.ExerciserAdministeredObjectListener.processActionResponse()
(10/07/09 15:45:43)
(10/07/09 15:45:43) DeployResult.getCompletionCode() = failure
(10/07/09 15:45:43) DeployResult.getLogEntries() : BIP1510E: Deployment failed; a deployment is already in progress to broker 'DVMB02'.
(10/07/09 15:45:43) DeployResult.getCompletionCodeForBroker(<DVMB02>) = failure
(10/07/09 15:45:43) DeployResult.getLogEntriesForBroker(<DVMB02>) : BIP1510E: Deployment failed; a deployment is already in progress to broker 'DVMB02'.
(10/07/09 15:45:43)
(10/07/09 15:45:43) <---- cmp.exerciser.ClassTesterForMessageFlowProxy.testDeleteMsgFlow |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Jul 10, 2009 7:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lbart wrote: |
It used to be easy with 2.1 as it was a DB2 database and have solved this issue previously in 2.1.
|
It used to be easy but was never a really good idea. Also that was then and this is now - db structure is different, it's used differently, etc, etc.
I think the key point here is "solved this issue" - what issue? Presumably this issue is leading you towards manipulating the db to fix it; perhaps if you elucidated what the "issue" was we could offer some other suggestions to fix it? Is it as simple as deleting a flow from an execution group?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 10, 2009 7:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| lbart wrote: |
| 4) I am attempting to directly manipulate the Config Mgr's Repository. |
Open a PMR. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jul 10, 2009 11:53 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Search for "cancel + deploy" in the WMB Info Center. The instructions work and will allow you to move on.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jul 10, 2009 9:31 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Also make sure that the channel between the broker and the config qmgr is running correctly. The message you get is often a direct result of either
- the inability of the message broker to consume the control message:
If the message is in the broker eg input queue you may have to bounce the broker. If the message is not there check next point
- make sure that the configmgr qmgr is able to talk to the broker's qmgr.
- If that does not clear your pending deployment use the toolkit or the java api-proxy to ignore pending deployment...
You should not and will not manipulate the DB outside from the application!
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ramires |
| Posted: Sat Jul 11, 2009 6:08 pm Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
|
| Back to top |
|
|
| lbart |
| Posted: Mon Jul 13, 2009 5:19 am Post subject: |
|
|
Novice
Joined: 18 May 2006
Posts: 13
Location: Manchester
|
Hi and thanks for the info so far.
Vitor, the issue is that we are unable to do any kind of removal or deploy of a messageflow without receiving the above error. It does allow us to stop and start flows but nothing else to this broker. All the normal ways of cancelling an outstanding deploy fail.
Peter, I have looked in the info centre and used the various suggestions for cancelling an outstanding deploy, they don't work in this situation.
Fjb, communication is working fine between the Toolkit and the Config Manager, the Config Manager as I mentioned previously is on the Unix Machine along with the broker. The broker has been recycled and no msgs exists in the broker Qmgr waiting to be processed. In addition the Toolkit and api-proxy cancel deployment commands don't work in this
situation.
Ramires, thanks for the good info I will try some of these suggestions and get back to the forum.
Thanks |
|
| Back to top |
|
|
| lbart |
| Posted: Mon Jul 13, 2009 5:34 am Post subject: |
|
|
Novice
Joined: 18 May 2006
Posts: 13
Location: Manchester
|
ramiers, tried the suggested command:
mqsicmdt DVCM02 CUUIDLOCKS
java.sql.SQLException: Failed to start database '/var/mqsi/components/DVCM02/BERNARD', see the next exception for details.
at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
at org.apache.derby.jdbc.Driver30.getNewEmbedConnection(Unknown Source)
at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:562)
at java.sql.DriverManager.getConnection(DriverManager.java:208)
at com.ibm.broker.config.util.DisplayTable.main(DisplayTable.java:52) |
|
| Back to top |
|
|
|
|
