| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP3484E: On runtime with Custom Paths |
« View previous topic :: View next topic » |
| Author |
Message
|
| akil |
 Posted: Fri Jul 04, 2014 5:03 am Post subject: BIP3484E: On runtime with Custom Paths |
 |
|
Partisan
Joined: 27 May 2014
Posts: 338
Location: Mumbai
|
Hi
I hope I am clear when I am trying to explain the problem.
I get the following trace at runtime, for a missing XSD.
In the developer studio all is green (no warnings, no errors), I do a mqsipackagebar from the command line and deploy. Since the XSD is in a separate library that is referenced by the project, and the library is inside a folder (called finacle), I add it as follows
| Code: |
mqsipackagebar -a bpm -k bpm.app finacle/*
|
In the Integration Explorer view ( from the developer toolkit ), I can see the XSD as deployed, as a library will full name as finacle/BalInq.libzip.
Am I missing a step or do I need to move the libraries back into the root path of the workspace?
| Code: |
2014-07-04 18:11:51.170940 4222 UserTrace BIP3964I: The Mapping node ''X'' in message flow ''Mapping'' is about to process the mapping routine ''{default}:X''.
The Mapping node is about to process the named mapping routine.
Check the following messages to see the progression of the mapping process.
2014-07-04 18:11:51.181496 4222 UserTrace BIP3484E: ''Error: Could not resolve schema /BalInq.xsd.''
An embedded component has written the diagnostic message included here.
Refer to the appropriate message in the embedded component's documentation.
2014-07-04 18:11:51.181648 4222 Error BIP3944E: The map script generation for QName ''{default}:X'' has failed, with the following details: Location: ''Could not resolve schema /BalInq.xsd.'' Internal Error Number: ''0'' Error Message: ''Could not resolve schema /BalInq.xsd.''.
The generation of the map has failed.
Review and resolve the problems indicated in the message from the map generation.
2014-07-04 18:11:51.182092 4222 Error BIP3120E: Exception condition detected on input node 'X.HTTP Input'.
The input node 'X.HTTP Input' detected an error whilst processing a message. The message flow has been rolled-back and a fault message returned to the requesting client. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
|
_________________
Regards |
|
| Back to top |
|
 |
| akil |
| Posted: Fri Jul 04, 2014 9:45 am Post subject: |
|
|
Partisan
Joined: 27 May 2014
Posts: 338
Location: Mumbai
|
I don't get this error if I compile the BAR using the toolkit ( right click on the app, create bar ), and in this case when I deploy the bar, I see that the referenced XSD is deployed within application.
I don't yet know what's the correct mqsipackagebar command for this, but I at least have a way to proceed.
If someone could suggest, what's incorrect with the way I am using mqsipackagebar, it'll be great.
_________________
Regards |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jul 04, 2014 7:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Are you using the package bar command suggested by the toolkit? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| akil |
| Posted: Fri Jul 04, 2014 10:53 pm Post subject: |
|
|
Partisan
Joined: 27 May 2014
Posts: 338
Location: Mumbai
|
Hi
The command suggested by the toolkit did not work. It is as below
| Code: |
iibadm@iib:~/code/iib$ mqsipackagebar -a bpm.bar -w . -k bpm.app
Successfully added file 'X.msgflow' to the broker archive.
Successfully added file 'X.xsd' to the broker archive.
Successfully added file 'IBMdefined/CommaSeparatedFormat.xsd' to the broker archive.
Successfully added file 'IBMdefined/RecordSeparatedFieldFormat.xsd' to the broker archive.
Successfully added file 'X_Compute.esql' to the broker archive.
Successfully added file 'inwardClearingValidationReportFormat.xsd' to the broker archive.
Successfully added file 'X.map' to the broker archive.
BIP1849W: The application 'bpm.app' references project 'BalInq' which does not exist.
BIP1849W: The application 'bpm.app' references project 'LoanAcctAdd' which does not exist.
BIP1849W: The application 'bpm.app' references project 'loanDisbursement' which does not exist.
BIP1849W: The application 'bpm.app' references project 'RetCustAdd' which does not exist.
Application file 'bpm.app.appzip' successfully added to the broker archive.
BIP1863W: Command completed with warnings.
|
So I tried the following
| Code: |
iibadm@iib:~/code/iib$ mqsipackagebar -a bpm.bar -w . -k bpm.app finacle/custom finacle/common finacle/common1
Successfully added file 'X.msgflow' to the broker archive.
Successfully added file 'X.xsd' to the broker archive.
Successfully added file 'IBMdefined/CommaSeparatedFormat.xsd' to the broker archive.
Successfully added file 'IBMdefined/RecordSeparatedFieldFormat.xsd' to the broker archive.
Successfully added file 'X_Compute.esql' to the broker archive.
Successfully added file 'inwardClearingValidationReportFormat.xsd' to the broker archive.
Successfully added file 'X.map' to the broker archive.
BIP1849W: The application 'bpm.app' references project 'BalInq' which does not exist.
BIP1849W: The application 'bpm.app' references project 'LoanAcctAdd' which does not exist.
BIP1849W: The application 'bpm.app' references project 'loanDisbursement' which does not exist.
BIP1849W: The application 'bpm.app' references project 'RetCustAdd' which does not exist.
Application file 'bpm.app.appzip' successfully added to the broker archive.
Successfully added file 'RecBillPmtModCustom.xsd' to the broker archive.
Successfully added file 'AcctLienAddCustom.xsd' to the broker archive.
......
-----
Successfully added file 'BOCustHoldAndPositionInqCustom.xsd' to the broker archive.
Successfully added file 'ACHDebitAuthModCustom.xsd' to the broker archive.
Library file 'finacle/custom.libzip' successfully added to the broker archive.
Successfully added file 'FIServiceRequestHeader.xsd' to the broker archive.
......
......
Successfully added file 'FICommonHeader.xsd' to the broker archive.
Library file 'finacle/common.libzip' successfully added to the broker archive.
Successfully added file 'BankInfo.xsd' to the broker archive.
Successfully added file 'AcctType.xsd' to the broker archive.
Successfully added file 'PostAddr.xsd' to the broker archive.
Successfully added file 'AcctId.xsd' to the broker archive.
Library file 'finacle/common1.libzip' successfully added to the broker archive.
BIP1863W: Command completed with warnings.
|
But the above fails, I suppose that is because of the warning being shown BIP1948W.
When I deploy the bar created by the command line, and then see the execution group in the explorer, I see it as follows :
http://www.pinterest.com/pin/133911788895101914/
However, If I do the build of the BAR from the developer toolkit, I see the following in the explorer, there is a difference ,but I do not know how to get this kind of build from the command line.
http://www.pinterest.com/pin/133911788895101925/
The code is laid out in the following way on the filesystem .
| Code: |
iibadm@iib:~/code/iib$ ll . finacle/
.:
total 212
drwxr-xr-x 12 iibadm iibadm 4096 Jul 4 23:36 ./
drwxrwxr-x 14 iibadm iibadm 4096 Jul 3 11:38 ../
drwxrwxr-x 8 iibadm iibadm 4096 Jul 4 14:56 .git/
-rw-rw-r-- 1 iibadm iibadm 682 May 15 13:55 .gitignore
drwxrwxr-x 3 iibadm iibadm 4096 Jul 2 23:17 .metadata/
drwxrwxr-x 2 iibadm iibadm 4096 Jul 4 18:46 BARfiles/
drwxrwxr-x 2 iibadm iibadm 4096 Jul 5 00:02 GeneratedBarFiles/
-rw-rw-r-- 1 iibadm iibadm 97 May 27 18:31 README.md
drwxrwxr-x 3 iibadm iibadm 4096 Jul 4 18:47 bpm.app/
-rw-rw-r-- 1 iibadm iibadm 105458 Jul 5 11:37 bpm.bar
-rw-rw-r-- 1 iibadm iibadm 332 May 15 13:55 demo.env
-rw-rw-r-- 1 iibadm iibadm 522 May 15 13:55 dev.env
drwxrwxr-x 9 iibadm iibadm 4096 Jul 4 23:22 finacle/
drwxrwxr-x 3 iibadm iibadm 4096 Jul 4 14:56 gefu.app/
-rw-rw-r-- 1 iibadm iibadm 38431 Jul 2 21:56 gefu.bar
drwxrwxr-x 2 iibadm iibadm 4096 Jul 4 14:56 gefu.ddp/
-rw-rw-r-- 1 iibadm iibadm 535 May 15 13:55 rbuat.env
drwxrwxr-x 4 iibadm iibadm 4096 Jul 2 15:45 vplus.app/
drwxrwxr-x 2 iibadm iibadm 4096 Jun 19 20:31 vplus.ddp/
finacle/:
total 52
drwxrwxr-x 9 iibadm iibadm 4096 Jul 4 23:22 ./
drwxr-xr-x 12 iibadm iibadm 4096 Jul 4 23:36 ../
drwxrwxr-x 2 iibadm iibadm 4096 Jul 4 15:52 BalInq/
drwxrwxr-x 2 iibadm iibadm 4096 Jul 4 15:48 LoanAcctAdd/
drwxrwxr-x 2 iibadm iibadm 4096 Jun 17 11:03 RetCustAdd/
drwxrwxr-x 2 iibadm iibadm 4096 Jun 17 12:30 common/
drwxrwxr-x 2 iibadm iibadm 4096 Jul 4 15:48 common1/
drwxrwxr-x 2 iibadm iibadm 20480 Jun 17 10:58 custom/
drwxrwxr-x 2 iibadm iibadm 4096 Jun 17 12:29 loanDisbursement/
iibadm@iib:~/code/iib$
|
_________________
Regards |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jul 06, 2014 6:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
So let's see:
You have your workspace all set up and all the projects referenced are in the workspace.
Your package bar command is exactly as described in the toolkit when you create the bar file from the toolkit. (see hint at bottom of top bar window...)
All your libraries etc are referenced in the application. (you reference all libraries and other components. No 2nd level referencing)
And you say your result is not the same? Prove it and open a PMR with that proof.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| akil |
| Posted: Sun Jul 06, 2014 7:38 pm Post subject: |
|
|
Partisan
Joined: 27 May 2014
Posts: 338
Location: Mumbai
|
Hi
Will open a PMR as you suggested, If you could just tell me about one thing that I have stumbled upon, it'll help.
The command suggested by the toolkit is the following, it is the same for both the cases that I mentioned below.
| Code: |
mqsipackagebar -a <barName> -w <rootLocation> -k bpm.app
|
Folder Structure 1: This works
| Code: |
-bpm.app
-- .project
-- X.map
-- IBMDefined\
-- IBMDefined\CommaSeparatedFormat.xsd
-- finacle
-- finacle\BalInq
-- finacle\BalInq\BalInq.xsd
|
Folder Structure 2: This does not work
| Code: |
-bpm.app
-- .project
-- X.map
-- IBMDefined\
-- IBMDefined\CommaSeparatedFormat.xsd
- finacle
-- finacle\BalInq
-- finacle\BalInq\BalInq.xsd
|
It appears to me that something needs to be passed on the command line for Folder Structure 2, which I am not doing. In folder structure 2, the resources are in 2 separate folders (bpm.app & finacle) , while in folder structure 1, all the resources are within 1 parent folder (bpm.app).
_________________
Regards |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jul 06, 2014 10:23 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
No. Something's definitively fishy in case 2.
I would say you need to:
- create an empty workspace
- check out all the dependent projects into the workspace
- check out the main project (app) into the workspace
- Verify that the dependencies resolve correctly (i.e.) verify that the dependent project and libraries appear under the main project / app /service
Note that this is not a physical relationship, i.e. you will not find a project folder underneath the application folder. It just means that the references are correct.
I would only undergo this check with the toolkit IF the build was not successful!
- run mqsipackage bar with the recomended settings
- if unsucessful run mqsicreatebar with the corresponding settings (here just -a appname -clean -deployAsSource)
- retry mqsipackage bar (mqsicreatebar rebuilt the .metadata folder)
- If still unsuccessful, start over again documenting each step and submit a PMR to IBM with the documentation.
The checkout order of the projects might just matter.
Make sure you check out first the most imbricated references (example library b referenced by a library a), then the library a, then application app referencing BOTH library a and library b...
I do not remember seeing it mentioned anywhere in the documentation, but the .metadata folder might need to be present for a successful mqsipackage bar... Anyway the steps above should allow you to find out, and submit a PMR with the needed traces and information.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
