CODEWITHSUNDEEP
ibm-mqmessagebrokeribm-integration-busextended-sql
WENzER
WENzER

Reputation: 305

WMB Bar File Migration from v7.1 to IIB9

11 Am currently migrating ESQL Message flow and Bar file codes from V7.1 to IIB9. For doing this I need to convert messageflows in to subflows. Then for creating bar files in mqsicreatebar command I chose 'deployAsSource' option. After creation of bar files I noticed that my bar files include all ESQL and subflows which were part of compilable main message flow which I have provided in mqsicreatebar. When I deployed this bar to execution group I noticed that every ESQL and subflows are also deployed. Ideally only main messageflow should have deployed on Execution Group. Is there anything or option am not choosing while this migration, please suggest.

Upvotes: 0

Views: 932

Answers (1)

Adam Rice
Adam Rice

Reputation: 890

In the toolkit, open up the Bar editor.

On the 'Prepare' tab, over on the right-hand side is a list of 4 checkboxes. One of these is 'Compile and in-line resources' - check this.

In the main editor page, make sure that only msgflows are selected. Build and Save.

When you look inside the bar file, you should only have CMF files.

EDIT: OP wanted to use the cmd line for generating the bar file. Here is a command that I used:

mqsicreatebar -data C:\Users\Adam\IBM\IIBT10\workspace -b C:\Users\Adam\cmd.bar -p Foo -o /Foo/foo1.msgflow

The mqsicreatebar command documentation might be useful for you.

I think using the deployAsSource option was a mistake in this case. Here's what the doc has to say about that option.

-deployAsSource (Optional) Include this parameter to deploy applicable resource files without compiling them. When the -deployAsSource parameter is used, any applicable resources are added to the BAR file as source files, and are not compiled into message flow .cmf files.

You cannot include both the compiled (.cmf) and source (.msgflow) versions of a message flow in a BAR file.

Upvotes: 1

Related Questions