|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Deploy sample code problem |
« View previous topic :: View next topic » |
Author |
Message
|
cots |
Posted: Mon Aug 18, 2003 9:54 am Post subject: Deploy sample code problem |
|
|
Centurion
Joined: 16 Jun 2003 Posts: 105
|
I tried to run a sample code from redbook#: SG246875 using running time environment setup. when I deployed the integration flow: I got an error of:
BIP1758E: Invalid message flow type found when deploying message flows.
When deploying message flow data, an attempt was made by a message flow type to override the value of a nonexistent property of run-time message flow type Compute. The property in question is 'validateFixup'. The message flow type in error is the one that embeds Compute, and may be identified from label ORDER_UC6_V0.getOrderId3.castMsgIdToStringAndAppend.
This is probably caused by a message flow type that corresponds to a run-time node having been replaced by a later version with different property names. Update the message flow type in error to use the correct property name. However if the problem persists, turn on Configuration Manager tracing to capture details of the problem, and contact your IBM support center.
Here are ESQL form the compute node:
------------------------------------------------------------
SET OutputRoot = InputRoot;
-- Enter SQL below this line. SQL above this line might be regenerated, causing any modifications to be lost.
DECLARE oid CHARACTER;
SET oid=SUBSTRING(CAST (InputRoot.MQMD.MsgId AS CHARACTER) FROM 3 FOR 48);
SET OutputRoot.XML.order.order_id=oid;
-------------------------------------
I have mq5.3 csd04 and mqsi5.2.1 csd03. I even tried to set oid = 'red' but it still didn't work.
Can anyone help to fix this problem? even if I have to hardcode the changes to fix the problem
Thanks in advance |
|
Back to top |
|
 |
Craig B |
Posted: Mon Aug 18, 2003 11:05 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003 Posts: 316 Location: UK
|
This error usually occurs when a message flow contains the new validation attributes that were introduced in V2.1 CSD03, but the broker has not been upgraded to CSD03 (above) level of code. This would mean that the broker will not be able to process these attributes in the message flow.
Another possibility is that a message flow with validation attributes has been imported into a configMgr that has not been enabled for validation.
Did you import the sample message flow?? What CSD levels are you configMgr and broker running at? _________________ Regards
Craig |
|
Back to top |
|
 |
cots |
Posted: Mon Aug 18, 2003 11:31 am Post subject: |
|
|
Centurion
Joined: 16 Jun 2003 Posts: 105
|
yes, I did import the sample messae flow. How do I check broker CSD and Configmgr CSD? I found a CSD in the registry HKEY_LOCAL+MACHINE\SOFTWARE\IBM\WebSphereMQIntegrator\CurrentVersion\CSDS Appliced\CSD03 installed
is that the right place?
To make it simple, I have broker and CM on the same box for now. |
|
Back to top |
|
 |
Craig B |
Posted: Mon Aug 18, 2003 12:51 pm Post subject: |
|
|
Partisan
Joined: 18 Jun 2003 Posts: 316 Location: UK
|
Well if you have your broker and configMgr on the same box, then they must be running at the same CSD level. From your registry it would seem that you have CSD03 installed. In this same registry folder, you should see LatestCSD showing 4 (CSD00 was 1) if you have CSD03 installed.
In my last response I mentioned that the other possibility was if your configMgr hasn't had validation enabled, and the sample exported messageflow has validation attributes within it. If you configMgr was created prior to CSD03, then you will have a configMgr that does not understand these validation attributes. To pick these validation options up, you need to delete you configMgr (without deleting the data ... ie no options on the mqsideleteconfigMgr command) and then recreate it with the exact same options that you created it with to pick up the existing tables.
Or if you did not want to go through this trouble, another alternative would be to take a copy of the XML msgflow export file and take out the validation entries that are causing the trouble. If you look in the export file, then you will see Attribute Groups such as the following :
Code: |
<AttributeGroup xmi.label="validation">
<Attribute xmi.label="validateFixup" type="ValidateFixupSWIFT" encoded="false" xmi.uuid="" valueMandatory="false" value="none" attributeOwner=""/>
<Attribute xmi.label="validateAllValueConstraints" type="ValidateAllValueConstraintsSWIFT" encoded="false" xmi.uuid="" valueMandatory="false" value="yes" attributeOwner=""/>
<Attribute xmi.label="validateFailureAction" type="ValidateFailureAction" encoded="false" xmi.uuid="" valueMandatory="false" value="exception" attributeOwner=""/>
<Attribute xmi.label="validateMaster" type="ValidateMasterSWIFT" encoded="false" xmi.uuid="" valueMandatory="false" value="none" attributeOwner=""/>
</AttributeGroup>
|
These are then entries in your message flow sample that are causing the problem If you remove all these attributeGroups that have an xml.label="validation" then the flow should be ok. But thats up to you as to whether you see this as being less painful _________________ Regards
Craig |
|
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
|
|
|
|