Re: Using stored procedure properly

I'd recomend to study the "SQL Adapter Samples" articles in the BizTAlk 2006
Help. There are good explanations and examples.

--
Regards,

Leonid Ganeline

Microsoft Certified Technology Specialist: BizTalk Server 2006
http://geekswithblogs.net/leonidganeline/


"golddog" <golddog@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B33D4A86-5FC4-4B6D-8BE8-9659F5ECFA89@xxxxxxxxxxxxxxxx
I've spent most of the day reading different sites/Apress books, I don't
understand the problem.

I've finally gotten to the point of having my custom xslt transform the
incoming message into the outgoing message. I tested this by initially
using
a file adapter on the send port, so I could easily see the output.

Now I'm trying to switch the port to use an SQL Adapter to call a stored
procedure which inserts data.

So, first I added the SQLService.xsd file via adding a generated item.
Not
knowing what I should put in for the document element root name, I put in
"RequestRoot". (Wait for it...)

Next, go over to my port, switch the transport to SQL, configure the
connection, namespace, and response root.

Seems like everything's going o.k., but when I drop off a file, I get an
error in the admin console:

-------------
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5754
Date: 4/18/2007
Time: 2:56:56 PM
User: N/A
Computer: ACG-DEV-BIZTALK
Description:
A message sent to adapter "SQL" on send port
"Patient_Record_Request_Result_Port" with URI "SQL://******/" is
suspended.
Error details: HRESULT="0x80040e14" Description="Could not find stored
procedure 'RequestRoot'."
----------

I find no evidence anywhere that the request root name is tied to the
stored
procedure to be called, but there we are.

Finally, I don't understand the relationship between the SQLService.xsd
and
the actual run of the orchestration. By that I mean, there's nowhere I
selected SQLService.xsd as the "xsd to use with this
message/port/adapter".
If I add another one, I get another orchestration.

So, a couple of things:

1) Does anyone have experience with this sort of problem, and can give me
some guidance?

2) Re: the SQLService/orchestration/port/adapter relationship, I *REALLY*
don't feel like reconstructing an orchestration if/when I need to change
the
procedure or xsd. Can anyone point me in the direction of how all those
things are tied together, so I can change if necessary?

Thanks.


.

Relevant Pages

  • Re: System.OutOfMemoryException was thrown
    ... Receive Location configured with the Sql Adapter picks up messages that ... Send Port subscribes to the above messages and then Send Ports Send ... Logical Port in orchestration is then bound to physical MQ port end point. ... Exception type: PersistenceItemException ...
    (microsoft.public.biztalk.general)
  • Re: SQL Adapter or call SQL from C# Helper class
    ... Here I mention only Send Port functionality. ... And ADO.NET client of SQL is more flexible, more manageable then "BizTalk" ... The SQL Send Port + Orchestration are clumsy. ...
    (microsoft.public.biztalk.general)
  • Re: Error while Processing the input file instance....
    ... It looks as if your orchestration is not bound to your send port properly. ... "A BizTalk Enthusiast" ... > Health and Activity Tracking tool for more detailed information on this ...
    (microsoft.public.biztalk.general)
  • RE: Batching
    ... Currently batching is only supported with some accelerators like HL7. ... receives individual messages (from orchestration) and batches them ... In Visual Studio .Net 2003, BizTalk Explorer, you should find ... Receive Port named "BatchControlPort". ...
    (microsoft.public.biztalk.general)
  • Re: SQL Adapter or call SQL from C# Helper class
    ... Database configuration settings separated out in to the send port ... Visibility of the data travelling back and forth between the BizTalk ... within an xml schema, an orchestration, and a stored procedure - all very ...
    (microsoft.public.biztalk.general)
Loading