| Author |
Message
|
| lehare |
 Posted: Mon Feb 20, 2006 12:33 am Post subject: Bar File creation confusion [solved] |
 |
|
Apprentice
Joined: 25 Jul 2005
Posts: 48
|
Hi Guys -
i'm using WBI 5.0.6 windows 2000 - i have created 1 message flow and 2 message sets - when i create a bar file as a container to all three of them -whilst in the bar creation wizard, the wizard seems NOT to see the message flow ... but it can 'see' the 2 message sets.
but before i installed fix pac 6 - i was able to add message flows to a bar file now i cant  - could the 'new' fix pack brought this bug along?
regards lehare
Last edited by lehare on Mon Feb 20, 2006 4:02 am; edited 1 time in total |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Mon Feb 20, 2006 1:52 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Sorry to suggest the obvious  but first check that the message flow is a message flow project? |
|
| Back to top |
|
|
| lehare |
| Posted: Mon Feb 20, 2006 2:29 am Post subject: |
|
|
Apprentice
Joined: 25 Jul 2005
Posts: 48
|
yes it is a message flow project ...
the following is the error i get whilst trying to add the message flow to the bar:
Processing file .project
File .project can not be added to archive file as it undeployable.
Processing file CustomerFlow.esql
File CustomerFlow.esql can not be added to archive file as it is undeployable.
Processing file CustomerFlow.msgflow
File CustomerFlow.msgflow can not be added to archive file as it si udneployable.
-------
this message flow has a 'sub flow' and this subflow is in another project but i referenced this project in the CustomerFlow.msgflow
------
in the read me file for the broker toolkit 5.1 http://www-306.ibm.com/software/integration/mqfamily/support/readme/all51_read.html
on the paragraph 'After Installation' on point number 8
is says something like "ESQL compilation restriction: if you create a subflow, and choose to distribute this as a plug-in project, calls to ESQL global routines within the subflow might not be generated correctly when you add a message flow that contains the subflow to a BAR file. When you deploy the BAR file, it will fail.
Workaround: Implement one of the following options:
* Include all routines at module-level within the subflow.
* Add the subflows to your workspace, and update the project that contains the calling message flow to reference the subflow project (or projects)."
can this have something to do with the error?
thanx - lehare |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Mon Feb 20, 2006 3:34 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi lehare,
Please confirm that you DID NOT make ANY changes to the code or projects after the installation of the service pack....
We cannot see why the code would fail with installation of a service pack,hence it has to be the code...
Is the subflow in the toolkit ? Did you try a rebuild on the subflow and the main flow ? Are there any errors next to the projects...
Regards. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Feb 20, 2006 3:46 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
You might like to try "Project -> Clean -> Clean all projects" and/or restarting the toolkit. Similar problems have been fixed by this in the past.
-Matt |
|
| Back to top |
|
|
| lehare |
| Posted: Mon Feb 20, 2006 4:01 am Post subject: |
|
|
Apprentice
Joined: 25 Jul 2005
Posts: 48
|
the sub flow that i was referensing in my main flow was created in the schema com.ibm.text.util - i compiled the message to the default schema and now the message flow can now be added to the bar file.
but i still don't see how the sub flow being in the 'com.ibm.text.util' schema in a referenced project can cause this glitch...
but the problem is 'solved'
thanx guys |
|
| Back to top |
|
|
|
|
