Author |
Message
|
smdavies99 |
Posted: Sun Aug 16, 2015 11:15 pm Post subject: IIB 9.0.0.3 Toolkit Bar file builder |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Some of my applications can be built with the 'compile and inline' option set. Some can't.
for example
Code: |
Processing file PRC_BATCH.
Failed to add file PRC_BATCH to archive file.
Processing file PRC_BATCH\PRC_BATCH\PRC_BATCH.esql.
Failed to add file PRC_BATCH\PRC_BATCH\PRC_BATCH.esql to archive file.
ESQL files referenced from the message flows (.msgflow) cannot be added to the BAR when the "Compile and in-line resources" build option is selected in the Broker Archive editor.
To include each ESQL file in your BAR file as an individual resource, clear "Compile and in-line resources" and rebuild the BAR file.
|
The same thing also happens this application with IIB10(10.0.0.1) Toolkit.
Does anyone have any insights as to why this might be happening?
The ESQL in the 'offending' file is pretty straightforward. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Aug 17, 2015 4:35 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Is the ESQL file in a shared library?
Is it in the right Broker Schema for what's associated with the compute node?
Do you have the same problem when you drop the application/service (or the message flow if you're not using applications/services) on the EG directly?
How about using Debug?
You might, perhaps, also get more information from the Toolkit .log file. |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Aug 17, 2015 4:56 am Post subject: Re: IIB 9.0.0.3 Toolkit Bar file builder |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
smdavies99 wrote: |
Some of my applications can be built with the 'compile and inline' option set. Some can't.
for example
The same thing also happens this application with IIB10(10.0.0.1) Toolkit.
Does anyone have any insights as to why this might be happening?
The ESQL in the 'offending' file is pretty straightforward. |
If the ESQL file contains a function called from a mapping node, it cannot be inlined... _________________ MQ & Broker admin |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Aug 17, 2015 5:00 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Quote: |
Is the ESQL file in a shared library? |
No. The .esql mentioned is the primary ESQL file for the flow
Quote: |
Is it in the right Broker Schema for what's associated with the compute node? |
It does not matter if a 'BROKER SCHEMA' is used or not
Quote: |
Do you have the same problem when you drop the application/service (or the message flow if you're not using applications/services) on the EG directly?
How about using Debug?
|
This is building the .bar file rather than deploying it.
This Message Flow project was converted from a V7 project that has been in production use for more than three years.
Other projects were converted at the same time and don't show this problem.
As for the toolkit log file.
Code: |
!SESSION 2015-08-17 15:55:39.024 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=JRE 1.7.0 IBM J9 2.6 Windows Server 2008 R2 x86-32 20150406_242981 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR9_20150406_1443_B242981
JIT - tr.r11_20150401_88894
GC - R26_Java726_SR9_20150406_1443_B242981
J9CL - 20150406_242981
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
Framework arguments: -showlocation -product com.ibm.etools.msgbroker.tooling.ide
Command-line arguments: -os win32 -ws win32 -arch x86 -showlocation -product com.ibm.etools.msgbroker.tooling.ide -data W:\Data\workiib9
!ENTRY org.eclipse.ui 4 4 2015-08-17 15:55:45.355
!MESSAGE Invalid preference page path: Websphere Application Server
!ENTRY org.eclipse.wst.common.project.facet.core 4 0 2015-08-17 15:55:46.488
!MESSAGE Project facet jst.jsf has not been defined. It is used in plugin com.ibm.etools.javaee.cdi.core.
!ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:11.319
!MESSAGE NLS missing message: BarEditor_WLM in: com.ibm.etools.mft.bar.editor.messages
!ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:11.319
!MESSAGE NLS missing message: ResourceSelectionDialog_includeReferencedLibrary in: com.ibm.etools.mft.bar.editor.messages
!ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:11.319
!MESSAGE NLS missing message: ResourceSelectionDialog_includeReferencedLibraryTooltip in: com.ibm.etools.mft.bar.editor.messages
ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:21.789
!MESSAGE NLS unused message: ESQLCompiler_BAR_canAdd_notsubflow in: com.ibm.etools.mft.bar.compiler.messages
!ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:21.789
!MESSAGE NLS missing message: ESQLCompiler_BAR_canAdd_notesql in: com.ibm.etools.mft.bar.compiler.messages
!ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:21.797
!MESSAGE NLS unused message: PD_HELP_POPUP_RELATED_HELP_SECTION_TITLE in: com.ibm.etools.mft.flow.msgFlowStrings
!ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:21.798
!MESSAGE NLS unused message: PROPERTY_LEVEL_HELP_POPUP_OPEN_DYNAMIC_HELP_LINK_TEXT in: com.ibm.etools.mft.flow.msgFlowStrings
!ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:21.798
!MESSAGE NLS unused message: PD_HELP_POPUP_DECORATOR_HOVER_HELP in: com.ibm.etools.mft.flow.msgFlowStrings
!ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:21.798
!MESSAGE NLS unused message: PROPERTY_LEVEL_HELP_POPUP_MORE_INFO_LINK in: com.ibm.etools.mft.flow.msgFlowStrings
!ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:21.798
!MESSAGE NLS unused message: PROPERTY_LEVEL_HELP_POPUP_SECTION_HOVER_HELP in: com.ibm.etools.mft.flow.msgFlowStrings
|
Perhaps these mean something
Code: |
ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:21.789
!MESSAGE NLS unused message: ESQLCompiler_BAR_canAdd_notsubflow in: com.ibm.etools.mft.bar.compiler.messages
!ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:21.789
!MESSAGE NLS missing message: ESQLCompiler_BAR_canAdd_notesql in: com.ibm.etools.mft.bar.compiler.messages
|
_________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Aug 17, 2015 5:11 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
AH.... they certainly do.
Subflows with .subflow extension are new since V8 and AFAIK will not compile inline.
If you want a subflow to compile in line you need to have it as resource with the .msgflow extension.
Hope this helps  _________________ MQ & Broker admin |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Aug 17, 2015 5:34 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
.subflow vs .msgflow
some of the other projects that were convered to applications (which required conversion of subflows to .subflow types) do compile with the inline option selected.
As can be seen in the linked image (names obfuscated)
 _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Aug 17, 2015 5:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
smdavies99 wrote: |
Quote: |
Do you have the same problem when you drop the application/service (or the message flow if you're not using applications/services) on the EG directly?
How about using Debug?
|
This is building the .bar file rather than deploying it. |
Right... but dropping it on a local EG does both. So does simply running debug. It might, somehow, give a better or at least different result.
smdavies99 wrote: |
As for the toolkit log file.
Code: |
!ENTRY org.eclipse.osgi 2 1 2015-08-17 15:56:21.789
!MESSAGE NLS missing message: ESQLCompiler_BAR_canAdd_notesql in: com.ibm.etools.mft.bar.compiler.messages
|
|
That says it can't find the ESQL file.
Try building the project manually. And then try clean building it. |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Aug 17, 2015 5:59 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Quote: |
That says it can't find the ESQL file.
Try building the project manually. And then try clean building it.
|
The applicatino builds and runes perfectly if the Inline option is not selected.
Clean building makes no difference
Quote: |
Right... but dropping it on a local EG does both. So does simply running debug. It might, somehow, give a better or at least different result.
|
deploying the top level .msgflow file does deploy. However these .bar files are going to be sent 200+ miles so the drag/drop won't work.
Out of 19 different applications THREE have this problem. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Aug 17, 2015 6:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
I'm not asking you to drag/drop to a remote EG.
I'm asking you to drag/drop to an EG that's on the same machine as the Toolkit.
And run Toolkit Debug on the flow. |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Aug 17, 2015 11:25 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
I did drop the flow onto a local broker. I was saying that this won't be possible for the target system because there is no toolkit access to the broker.
I'm not sure what this would actually do that is different from what I've already done.
As I have already said the flow builds and runs fine if the 'compile and inline' is not selected.
That is where the problem lies. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
fjb_saper |
Posted: Mon Aug 17, 2015 2:22 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Do you have a new style MAP in the flows in question?
Something is specific to those flows that prevent you to do an inline compile...
Find out what is going on that is not happening in the flows that do compile in line... Node only present in the ones that don't compile etc...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Aug 17, 2015 10:05 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
fjb_saper wrote: |
Do you have a new style MAP in the flows in question?
Something is specific to those flows that prevent you to do an inline compile...
Find out what is going on that is not happening in the flows that do compile in line... Node only present in the ones that don't compile etc...  |
Good question. However there are no mapping nodes used anywhere on this site. The transformations are not simple ones. A lot of data enrichment goes on.
Let me restate these points again.
1) The bar file builds fine if the inline option is not selected.
2) The resulting bar file runs perfectly in an 9.0.0.3 Broker.
3) Three of the 19 flows show this problem when building with the inline flag.
4) No Mapping nodes are used.
5) All flows have been operational in a V7.0.0.4 environment since June 2013
6) All have been migrated to an 9.0.0.3 environment and work perfectly.
7) The one used as an example for this post has had a few lines of ESQL changed to rectify a long standing auditing problem.
8 ) The flow has the same problem building in the 10.0.0.1 toolkit. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Aug 18, 2015 4:05 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
What is uniquely present in the 3 flows that don't build with the inline flag that is not present in the 16 others?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Aug 18, 2015 4:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
smdavies99 wrote: |
I did drop the flow onto a local broker. I was saying that this won't be possible for the target system because there is no toolkit access to the broker.
I'm not sure what this would actually do that is different from what I've already done. |
It might have indicated a different issue - but I guess it probably doesn't use the inline option for these automatic builds. |
|
Back to top |
|
 |
smdavies99 |
Posted: Tue Aug 18, 2015 4:47 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
fjb_saper wrote: |
What is uniquely present in the 3 flows that don't build with the inline flag that is not present in the 16 others?  |
It might be because those flows have constants and some stored procedures declared outside Modules.
That does seem to be a common factor. More investigation needed though. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
|