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 » IBM MQ Installation/Configuration Support » IC01-Message Flow Versioning and Command Line Deploy Utils.

Post new topic  Reply to topic
 IC01-Message Flow Versioning and Command Line Deploy Utils. « View previous topic :: View next topic » 
Author Message
matthewz
PostPosted: Fri Aug 23, 2002 9:08 am    Post subject: IC01-Message Flow Versioning and Command Line Deploy Utils. Reply with quote

Newbie

Joined: 23 Aug 2002
Posts: 1
Location: Atlanta

Any suggestions on how the following can be done would be greatly appreciated?:

1) Check out a message flow from CVS in XML format
2) Use command line utilities to:
a) import the Message Flow from XML file(previously exported)
b) deploy the imported Message Flow(s) to a destination

I am trying to use "IC01" Support Pac which supplies the "Command-line Utilities" and "Version 2.1 of the Control Center" on an NT machine.

-------------------------------------------------------------------------------------

When I try to "import" a Message Flow that has been previously exported from the Control Center:

C:\Program Files\IBM\MQSeries Integrator 2.0\Tool> mqsiimportmsgflows C:\RateReply.xml -l

I get:

BIP1018S: Unexpected exception in utility ImportMsgFlows; method getMsgFromXML.

An exception was caught by the ImportMsgFlows utility in method getMsgFromXML. The exception text is
: com.ibm.ivm.tools.model.ToolsModelException: BIP0006E Incorrect parameters were supplied. This is
an internal error. The method was: com.ibm.ivm.tools.model.LogEntry.LogEntry. Turn on Control Cent
er tracing to capture details of the error. Retry the operation and contact your IBM support center.
. The current operation will end.

Retry the operation if possible. If the exception still occurs, contact your IBM support center.

-----------------------------------------------------------------------------------

Even when I try the File->Import to Workspace... option, I still get the message: BIP0634L - "The import operation only imports those resources in the import file that eiter do not exist in the shared configuration repository or that are currently checked out to you".

-------------------------------------------------------------------------------------

Yet, the IC01(support pack) does not include a command-line utility that resembles "checkout".

If anyone has any experience using the IC01 Support Pack or some other useful ways to deploy message flows from a source repository to a broker using the command line and not a GUI, I would appreciate hearing about it.

Thanks,

Matt
Back to top
View user's profile Send private message Send e-mail
whiting
PostPosted: Thu Aug 29, 2002 9:47 am    Post subject: Version control through CVS Reply with quote

Acolyte

Joined: 26 Mar 2002
Posts: 64
Location: Greenville, SC

Matthew,
I haven't used the command line utilities, but I have imported message flows through the Control Center that have been retrieved from CVS.

If you're using MQSI 2.0.[12] then you must check out the flows before you import the file from CVS (assuming that the flow already exists).

If you're using 2.1 then I believe that there is a check box in the import dialog to import flows even if the flow exists and is not checked out.

Is the file that you checked into CVS an "export" of the message flow generated from the Control Center?

//Bill Whiting
Back to top
View user's profile Send private message Send e-mail
CoolDude
PostPosted: Sat Nov 19, 2005 9:53 am    Post subject: Reply with quote

Apprentice

Joined: 17 Jan 2004
Posts: 39

We ran into same issue and before we increase the Memory of the mqsideploybat command. we checked couple of things

1. mqsi id is having access to the ConfigMgr database
2. mqsi id is having access to the ConfigMgr box

In our case the mqsi id is messed up on the ConfigMgr box and we removed and recreated the id and added it to all the required groups and reissued the deploy command.

This seemed to resolve the problem. I do not have more details on how this fixed the issue but just wanted to log it in here.
_________________
Correct Me from Wrong . If i am correct Appreciate Me
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 » IBM MQ Installation/Configuration Support » IC01-Message Flow Versioning and Command Line Deploy Utils.
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.