| Author |
Message
|
| Esa |
 Posted: Mon Feb 27, 2012 11:34 pm Post subject: BIP2293E when deploying DFDL flow |
 |
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
BIP2293E: Invalid configuration message containing attribute value 'DFDL': not valid for target attribute 'messageDomainProperty' on object ...
I have selected DFDL for message domain in the MQInput node, but I cannot deploy the flow. The flow project references the library where the DFDL schema resides. I have deployed the library successfully.
Is it that you only can use DFDL parser with flows that belong to an application? My flow is in an independent resource Message Flow project. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Feb 28, 2012 1:33 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Is it that you only can use DFDL parser with flows that belong to an application? |
No, that's not the answer. DFDL is 'just another domain' like XMLNSC or MRM etc. You can ( well, should be able to  ) use DFDL anywhere that you can use MRM.
One possibility is that you have a broken installation. Does DFDL work at all on this broker? |
|
| Back to top |
|
|
| Esa |
| Posted: Tue Feb 28, 2012 3:59 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| kimbert wrote: |
| One possibility is that you have a broken installation. |
How can you verify that? At least .../dfdl/lib contains jar files. Although I was under the impression that broker would use a C++ implementation...
| kimbert wrote: |
| Does DFDL work at all on this broker? |
Does not seem to. I managed to deploy the flow by changing message domain to BLOB in the MQInput and adding a RCD after it. But in the debugger the BLOB remains after the RCD and after it there is 'Unknown parser name' 'DFDL'.
The broker runs on AIX. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Feb 28, 2012 5:50 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I thought so. Sounds as if your installation is missing ImbDFDLParser.lil or one of its dependencies. Are you sure it's a v8 installation?
| Quote: |
| I was under the impression that broker would use a C++ implementation |
It does. But the runtime also uses the DFDL compiler which is a Java application. That's only used at deploy time. Actual parsing and writing is performed by the C++ implementation - but only on machines that have one  |
|
| Back to top |
|
|
| Esa |
| Posted: Tue Feb 28, 2012 6:06 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
Yes, I found the C parser in dfdlc directory. But ImbDFDLParser.lil is missing from lil directory. However, a file named imbdfdl.lil is present.
I have checked the installation log and found no errors but this:
| Code: |
[Stderr] exec(): 0509-036 Cannot load program dspmqver because of the following errors:
[Stderr] 0509-150 Dependent module /usr/lib/libmqmcs_r.a(shr.o) could not be loaded.
[Stderr] 0509-103 The module has an invalid magic number. |
But that should not have anything to do with the missing DFDL parser. In the beginning of the log there are several error messages related to graphical installation interface, but then the installation seem to have fallen down to the command line interface.
Should we try to uninstall the product and then try to install with the command line installer from the beginning?
Or maybe there is a prerequisite that the installation script does not check? |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Feb 28, 2012 6:33 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| a file named imbdfdl.lil is present |
OK - that's the name I meant to quote anyway. Not sure why you're getting those symptoms if that file is present and correct.
You could try
- checking the dependencies of imbdfdl.lil using a dependency checking tool appropriate to your platform, or
- re-install and see whether the problem goes away.
If those don't uncover/fix the problem then it's PMR time. |
|
| Back to top |
|
|
| Esa |
| Posted: Mon Mar 05, 2012 7:10 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| The broker user id was configured to run V7 mqsiprofile. After that was corrected the deployments don't fail any more. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Mar 05, 2012 7:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Esa wrote: |
| The broker user id was configured to run V7 mqsiprofile. |
| Esa wrote: |
| After that was corrected the deployments don't fail any more. |
 |
|
| Back to top |
|
|
|
|
