|
Home > Archive > BizTalk Server General > January 2006 > BAM API Remote Calls
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
BAM API Remote Calls
|
|
|
| Hi
We are looking at using the BAM API from our components to gather business
data. My question is what is the best practice around using remote
components. e.g. biztalk is running on Server A but our component that wants
to use BAM is running on Server B (that does not have BizTalk installed.)
Is their a way to do this If not is there any way to do it BizTalk 2006?
Thanks
| |
| Keith Lim 2006-01-19, 6:07 pm |
| The documentation for this is still in progress, but available in BizTalk
2006 is that, from any box without Biztalk installation, you can just
install the required EventStream DLL's and you are able to use the
DirectEventStream (synchronous API) and BufferedEventStream (asynchronous
API) and point them to a licensed Biztalk server installation.
HTH,
Keith Lim [MSFT]
--------------------[vbcol=seagreen]
business[vbcol=seagreen]
wants[vbcol=seagreen]
Thanks,
Keith Lim [MSFT]
My BizTalk BAM Blog: http://blogs.msdn.com/keithlim/default.aspx
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
| |
|
| Thanks very much for your reply.
So the servers that are just running our components (to call bam on a
licensed biztalk server) do not have to be licensed for BizTalk?
Thanks again
Rob
"Keith Lim (MSFT)" wrote:
> The documentation for this is still in progress, but available in BizTalk
> 2006 is that, from any box without Biztalk installation, you can just
> install the required EventStream DLL's and you are able to use the
> DirectEventStream (synchronous API) and BufferedEventStream (asynchronous
> API) and point them to a licensed Biztalk server installation.
>
> HTH,
> Keith Lim [MSFT]
>
>
>
> --------------------
> business
> wants
>
> Thanks,
> Keith Lim [MSFT]
> My BizTalk BAM Blog: http://blogs.msdn.com/keithlim/default.aspx
> --
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
> Note: For the benefit of the community-at-large, all responses to this
> message are best directed to the newsgroup/thread from which they
> originated.
>
>
| |
| Keith Lim 2006-01-24, 6:04 pm |
| That's correct Rob. If I get futher info on this soon, I will reponse it
here. Otherwise, please wait for the official documentation (that comes
with the 2006 release). If you can't find anything on this subject, feel
free to post question on this again and I will make sure you get the info.
You are not alone on this, many other customers what this as well.
Thanks,
Keith Lim [MSFT]
--------------------[vbcol=seagreen]
<RNqPc2UHGHA.1236@TK2MSFTNGXA02.phx.gbl>[vbcol=seagreen]
BizTalk[vbcol=seagreen]
(asynchronous[vbcol=seagreen]
that[vbcol=seagreen]
installed.)[vbcol=seagreen]
2006?[vbcol=seagreen]
rights.[vbcol=seagreen]
Thanks,
Keith Lim [MSFT]
My BizTalk BAM Blog: http://blogs.msdn.com/keithlim/default.aspx
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
|
|
|
|
|