ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » mqsideploy log

Post new topic  Reply to topic
 mqsideploy log « View previous topic :: View next topic » 
Author Message
lanny boy
PostPosted: Fri Jul 21, 2006 6:21 am    Post subject: mqsideploy log Reply with quote

Voyager

Joined: 24 Nov 2003
Posts: 79
Location: UK

I am working on automating our releases procedures.

Everything is working perfectly. However i can't figure out how to get confirmation that the deploy was successful. I can see that the deploy was successfully initiated. The details below are for a deploy that i know would fail. However i can't see any feedback telling me this.

Any ideas on how to get this confimation? Is the event log based on a phsical file that i can interrogate?

C:\>mqsideploy -b brokerA -e default -bar mybar.bar -r -connection brokerA.configmgr

BIP1039I: Deploying BAR file mybar.bar to broker 'brokerA' (execution group 'default') ...

BIP1520I: Deploy operations successfully initiated.

The Configuration Manager has processed the deploy request and initiated the dep
loy of configuration data to the following brokers. Active brokers: brokerA.
Deleted brokers: .

Open the Event Log Editor to check the outcome of the operations. There will be a separate set of log messages for each broker.

C:\>

I am running WBIMB V5 CSD08 on Windows XP
Back to top
View user's profile Send private message
mqmatt
PostPosted: Sun Jul 23, 2006 3:53 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

V6 is your answer - in v6, the mqsideploy command waits for all deploys to fully complete before returning - and gives you a lot more feedback in the process.

Thinking back to the dim and distant days of v5 (it's a long time since I looked at the code), you may like to check the value of %ERRORLEVEL% after your deployment. A non-zero value would be the last three digits of the BIP error message that happened to be received before the command exited.

-Matt
Back to top
View user's profile Send private message
lanny boy
PostPosted: Wed Aug 16, 2006 5:59 am    Post subject: Reply with quote

Voyager

Joined: 24 Nov 2003
Posts: 79
Location: UK

Hi Matt,

thnaks for your reply.

I have just noticed something very strange though. I am still running WBIMB v5 but have installed the V6 toolkit on my desktop.

When i ran the mqsideploy command again the result of the deploy was displayed see below.

[exec] BIP1039I: Deploying BAR file 'C:\Build/builds/deploy.bar' to broker 'broker' (execution group 'deploy') ...

[exec] BIP1520I: Deploy operations successfully initiated.

[exec] The Configuration Manager has processed the deploy request and initiated the deploy of configuration data to the following brokers. Active brokers:
broker . Deleted brokers: .

[exec] Open the Event Log Editor to check the outcome of the operations. There will be a separate set of log messages for each broker.

[exec] BIP2056I: Broker broker successfully processed the entire internal configuration message.

[exec] An internal configuration message was processed to completion.

[exec] No user action required.

[exec] BIP4040I: The Execution Group 'default' has processed a configuration message successfully.

[exec] A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.

[exec] No user action required.
[echo] Completed deploying BAR file C:\Build/builds/deploy.bar


However i cannot get the this behaviour to repeat itself. It simply stopes at the line:-

[exec] Open the Event Log Editor to check the outcome of the operations. There will be a separate set of log messages for each broker.


Do you know the reason behind this inconsistent behaviour?

thanks
Back to top
View user's profile Send private message
lanny boy
PostPosted: Wed Aug 16, 2006 6:56 am    Post subject: Reply with quote

Voyager

Joined: 24 Nov 2003
Posts: 79
Location: UK

This was caused by the result of the deploy taking too long to come back. I extended the timeout vaue on the command and this resulted in the deploy information being returned
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » mqsideploy log
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.