| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| The PIF data could not be found for the integration server |
« View previous topic :: View next topic » |
| Author |
Message
|
| KIT_INC |
 Posted: Wed Nov 14, 2018 7:49 am Post subject: The PIF data could not be found for the integration server |
 |
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
I am running IIB V10.0.0.9 on WIN7
I have a simple message flow to convert xml to CSV
FileInput -- compute --TraceNode-- Fileoutput
The message flow is an independent resource in a project with a project reference to CSV_TEST_LIB.
CSV_TEST_LIB is a shared library containing the DFDL schema.
This is what I see in the toolkit
CSV_TEST_LIB.
Schema Definition
default Namespace
VerySimpleCSV.xsd
http://www.ibm.com/dfdl/CommonSeperatorFormat
CommonSeperatorFormat.xsd
..
I have the message flow and the CSV_TEST_LIB deployed to the default EG
This is what I see in the toolkit after deployment
Integration Nodes
IIB10
default
DFDL_SIMPLIFY_ERROR_MSG_MF
CSV_TEST_LIB
DFDL_SIMPLIFY_ERROR_MSG_MFompute
The ESQL in compute node looks like
SET OutputRoot.Properties.MessageType = '{}:VerySimpleCSV';
SET OutputRoot.DFDL.VerySimpleCSV.Record[1].Name=InputRoot.XMLNSC.ErrorMessage.ErrorHeader.TimeStamp;
SET OutputRoot.DFDL.VerySimpleCSV.Record[1].Value=InputRoot.XMLNSC.ErrorMessage.ErrorHeader.ServiceName;
SET OutputRoot.DFDL.VerySimpleCSV.Record[2].Name=InputRoot.XMLNSC.ErrorMessage.ErrorHeader.SourceApp;
SET OutputRoot.DFDL.VerySimpleCSV.Record[2].Value=InputRoot.XMLNSC.ErrorMessage.ErrorHeader.DestinationApp;
Trace node output shows (some business data masked with xxxx )
2018-11-14 09:03:14.677046 21976 UserTrace BIP4060I: Data ''( ['GENERICROOT' : 0x24fb7950]
(0x01000000:Name):Properties = ( ['MQPROPERTYPARSER' : 0x25b0a140]
(0x03000000:NameValue):MessageSet = NULL
(0x03000000:NameValue):MessageType = '{}:VerySimpleCSV' (CHARACTER)
(0x03000000:NameValue):MessageFormat = NULL
(0x03000000:NameValue):Encoding = NULL
(0x03000000:NameValue):CodedCharSetId = NULL
(0x03000000:NameValue):Transactional = NULL
(0x03000000:NameValue):Persistence = NULL
(0x03000000:NameValue):CreationTime = NULL
(0x03000000:NameValue):ExpirationTime = NULL
(0x03000000:NameValue):Priority = NULL
(0x03000000:NameValue):ReplyIdentifier = NULL
(0x03000000:NameValue):ReplyProtocol = 'FILE' (CHARACTER)
(0x03000000:NameValue):Topic = NULL
(0x03000000:NameValue):ContentType = NULL
(0x03000000:NameValue):IdentitySourceType = NULL
(0x03000000:NameValue):IdentitySourceToken = NULL
(0x03000000:NameValue):IdentitySourcePassword = NULL
(0x03000000:NameValue):IdentitySourceIssuedBy = NULL
(0x03000000:NameValue):IdentityMappedType = NULL
(0x03000000:NameValue):IdentityMappedToken = NULL
(0x03000000:NameValue):IdentityMappedPassword = NULL
(0x03000000:NameValue):IdentityMappedIssuedBy = NULL
)
(0x01000000:Name):DFDL = ( ['dfdl' : 0x250bbc50]
(0x01000000:Name):VerySimpleCSV = (
(0x01000000:Name):Record = (
(0x03000000:NameValue):Name = '2018-11-08 09:59:25.094751' (CHARACTER)
(0x03000000:NameValue):Value = 'xxxx' (CHARACTER)
)
(0x01000000:Name):Record = (
(0x03000000:NameValue):Name = 'xxxxx' (CHARACTER)
(0x03000000:NameValue):Value = 'xxxxxxx' (CHARACTER)
The user trace shows error
2018-11-14 09:22:55.529208 21976 >> ImbDFDLWriter::getDFDLSerializer , 'Throwing exception', 'F:\build\S1000_slot1\S1000_P\src\MTI\MTIforBroker\DfdlParser\ImbDFDLWriter.cpp', 305, 'BIP5846', 'The PIF data could not be found for the integration server
The only thing I did to tell IIB about the DFDL schema is by properties MessageType = '{}:VerySimpleCSV'
Is there anything else I need to do ? What other PIF data does the broker need ? |
|
| Back to top |
|
 |
| timber |
| Posted: Wed Nov 14, 2018 8:11 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
| The message flow is an independent resource |
Any good reason why you are not putting this message flow into an Application? I suspect that it would work just fine if you did that. |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Wed Nov 14, 2018 9:18 am Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
| Quote: |
| Any good reason why you are not putting this message flow into an Application |
The test case is build from an existing legacy flow using MRM but output to MQ. So we just create the test flow as an independent resource.
Anyway, I tried your suggestion and move the flow to an application. I just created an application and use 'move' to move the flow from under independent resource to under the new application.
Now I have in my toolkit
XML2CSV (application)
Flow
DFDL_SIMPLIFY_ERROR_MSG_MF.msgflow
ESQL
DFDL_SIMPLIFY_ERROR_MSG_MFompute.esql
Referenced Libraries
CSV_TEST_LIB
After deployment, I can see
Integration Nodes
IIB10
default
XML2CSV
CSV_TEST_LIB
I ran the flow with user trace on. The error in the trace is a little different, but I think it still means it cannot get to the DFDL schema.
2018-11-14 11:59:21.783728 18356 ParserException BIP5828E: The DFDL serializer could not locate a message model for the application ''XML2CSV''.
The DFDL serializer is attempting to serialize a message tree, but a message model for the application ''XML2CSV'' cannot be located. |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Wed Nov 14, 2018 10:18 am Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
I added the line
SET OutputRoot.Properties.MessageSet='{CSV_TEST_LIB}';
The error goes away. I still have other problem to fix after IIB gets the schema. But it looks like both
Properties.MessageType and Properties.MessageSet are needed. It will be nice if this is documented in the info center. |
|
| 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
|
|
|
|
