Forum Replies Created
-
AuthorPosts
-
February 22, 2007 at 2:03 PM in reply to: Hi to all gurus :) . CustomComponent for my pipeline qustion: #17767
Without the use of an existing DLL, it's going to be hard. You'll need to have the internal format of .PDF-files.
February 22, 2007 at 1:59 PM in reply to: Verifing if the host account is added toe the role in MQSAgent Com+ application #17766After you opened Component Services, perform the following:
– expand 'Component Services', 'Computers', 'My Computer', 'COM+ Applications', 'MQSAgent2', 'Roles', 'CreatorOwner', 'Users'
– check if the user running the Host Instance for the MQ Series adapter is addedif it is not, right-click 'Users' and choose New/User from the context menu
Good luck!
And you can also have a look at this blog: http://excel.codebetter.com/blogs/jeff.lynch/default.aspx
The MS TechNet also might contain usefull information:
http://www.microsoft.com/technet/prodtechnol/comm/2007/csbizintegrate.mspxI guess is that you forgot to close your bracket after 'Products' and namespace-uri=''
try this:
"/*[local-name()='Contract' and
namespace-uri()='http://ClaimSchemas.s_ExcelContract'%5D/*%5Blocal-name()='Products'
and namespace-uri()='']/*[local-name()='Product' and
namespace-uri()=''][" + strCount + "]");-weak architect
Yeah, good point. I should have mentioned that. Glad you got it working though.
Cheers Rich, this is one of the problems as I have dont have access to the Instructions, so I guess it's MSDN then.
Cheers
John
Thanks for the reply, it works fine though you should have mentioned that i have to restart the host instance every time I change something in the assembly, would have saved me some time 😉
February 21, 2007 at 5:03 PM in reply to: Custom pipeline "Allow Unrecognized message" property not working #17757Where are you looking for it? If you have an MSDN subscription, it's available under BizTalk downloads. The edition of BIzTalk doesn't matter.
I know you probably won't want to hear the typical answer…but the included product documentation and of course, MSDN are probably going to be your best assets.
-Rich
I am also having no luck finding this adapter. I have Biztalk Server 2006 Standard edition. Could it be that I need the enterprise edition or the developer's edition?
Set the breakpoint in your assembly's code (make sure the assembly is in the GAC for BizTalk to use), then do "debug –> attach to process" and choose the "btsntsvc.exe" which is the standard BizTalk host service. Then when the orchestration calls your code it should jump into it.
February 21, 2007 at 8:26 AM in reply to: Custom pipeline "Allow Unrecognized message" property not working #17751thanks tomasr again for your help,
so what i am trying to do now, is to create a custom pipeline (my first ever actually), and inside the pipeline i am trying to promote the MessageType property and set it explicitly to the message type that my orchestration expects. i am thinking that then the subscription will work and the message will be handed to the orchestration.
will that work? if yes do you have any guidliness/samples that i could use?
thanks a lot.
I realize you are rolling your own component to achieve this, but you might want to take a look at FarPoint Spread for BizTalk. Spread for BizTalk is a BizTalk Server 2006 Pipeline Disassembler that parses Excel XLS files into XML that map to schemas created through a Spreadsheet Schema Wizard that is integrated into Visual Studio 2005.
Please check out our Spread for BizTalk Resource Center: http://www.FarPointSpread.com/BizTalk.
-Robby
February 21, 2007 at 6:40 AM in reply to: Custom pipeline "Allow Unrecognized message" property not working #17746If you don't want to introduce a routing orchestration that receives generic messages and then tries to figure out what each one means and routes them to the right orchestration (which might be costly in performance terms), then your best bet (and the best solution) would be to write a custom pipeline component and make it part of the receive pipeline.
That component will have to figure out a way to see the real type of message from the message contents and correctly promote the appropriate properties. Sure sounds like a good spot for a probing component (seach google for IProbeMessage for details and samples)
-
AuthorPosts