Forum Replies Created
-
Posts
-
Chris…
If u cant kill the empty iterations use a custom XSLT.
I have experienced the power of it and yours is a simple thing to be done using XSLT.
Ok, sorry, fixed it on my own. I compiled the tutorials which is right but I forgot to change the .net-version in inetmgr from 1.1 to 2.
Afterwards getting an access violation to the mii-metabase. Simply went to system – software and repaired the net 2.0 framework (installed the framework before the iis which results in problems to the user configuration, I think) and the web services are working.
Henry,
Does the system do validation of HIPAA extended rules levels 3-6? Is the HIPAA accelerator by Covast?
What does the task manager look like? Is anything consuming an extraordinary amount of CPU cycles?
-wa
Thanks a bunch Henry, this actually makes sense. The machine I'm doing this on had 1gb of ram, we upgraded it to 3gb and it improved it a little but not by much. It still bogs down when you have too many messages, almost feels like there is something that needs to be done to the database to optimize it.
Yuo have to use XMLSendPipeline to be able to apply maps on the port!
PassThrough won't work!
BR,
/Roba_Koops – this should actually say:
– turn off validation and see that you'll get 2 occurs of loveit
and 2 occurs of hateit when you run. You need to now kill the
empty iterations of loveit and hateit.– wa
[quote user="NISHIL"]
Chris,
You would laugh at yourself if I tell you the solution.
Wht u did is perfectly fine.
Just right Click your Map….Properties.
Set "Validate Test Map Output" to False.
Or
Set Min Occurs to 0 for both HateIt and LoveIt node in Output Schema.
The Obvious reason is…..the first time the "mostFavourite" node is selected so the node "Loveit" is created at Destination.
Now the next node to be created is "HateIt" in Output Xml File as Min occurs is not set to 0.
Hope you find it Useful.
[/quote]
Nishil – this solution doesn't give him a valid message – he requires both loveit and hateit. What he really wants to do is populate the data as shown, and he says he always gets "mostfavorite" and "leastfavorite."
Chris
– tie "foo" to a looping functoid and tie that to both "loveit" and "hateit".
– turn off validation and see that you'll get 2 occurs of mostfavorite and 2 occurs of leastfavorite when you run. You need to now kill the empty iterations of loveit and hateit.
– tie the logical output from both "= mostfavorite" and "= leastfavorite" functoids, which you used for the value mappers, to "loveit" and "hateit" respectively. What this does is sent a 'false' to the node and keep it from being created when not true.
in summary, create all possible iterations and kill the unwanted ones.
– weak architect
You need to define an element for the 160 bytes and then an element for the rest of the message, to consume that.
What is is doing is satisfying the criteria of 160 bytes defined by your schema and then assuming that subsequent data are additional message in a batch.
-wa
Chris,
You would laugh at yourself if I tell you the solution.
Wht u did is perfectly fine.
Just right Click your Map….Properties.
Set "Validate Test Map Output" to False.
Or
Set Min Occurs to 0 for both HateIt and LoveIt node in Output Schema.
The Obvious reason is…..the first time the "mostFavourite" node is selected so the node "Loveit" is created at Destination.
Now the next node to be created is "HateIt" in Output Xml File as Min occurs is not set to 0.
Hope you find it Useful.
I got the same problem and have no idea how to fix it. I tried to give full permission on every related databases but it didn't cha,ge anything.
Does anybody have any idea?
Thanks for your help.
Julian –
try to read about message and context properties. Maybe that's the problem.
http://blogs.msdn.com/dhtoran/archive/2005/07/07/436395.aspx
http://www.digitaldeposit.net/blog/2007/01/property-promotion-inside-orchestration.html
