Hi,
I was looking at the portability issue for xlangs....typically the
implementation in a xlang is tied to the particular machine on which
it is created.
Any way we can configure this....to make it machine independent...

any configuration or stuff like that....

[ Post a follow-up to this message ]

Xlang Scheduler is a COM+ application and a schedule instance runs in the
context of that.  So in that sense, it is bound to a machine once a
schedule starts execution.  A clustered Xlang Engine would be bound to the
virtual machine.  What type of 'portability' are you looking for?

Sincerely,


Everett Yang
DSI - Microsoft BizTalk Server

This posting is provided “AS IS” with no warranties, and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn

[ Post a follow-up to this message ]

Hi,
I am looking at deployment portability primarily.
For eg. I am doing my development in dev environment where directory
structure is different from my production environment where I want to
finally deploy my xlangs for execution...now since the ports and
channels are bound to the local system resources like file system
etc....
how do i ensure deployment portability...

Thanks,

Ambrish



evyang@online.microsoft.com (Everett Yang) wrote in message news:<cNRNZXl#DHA.744@cpmsft
ngxa06.phx.gbl>...
> Xlang Scheduler is a COM+ application and a schedule instance runs in the
> context of that.  So in that sense, it is bound to a machine once a
> schedule starts execution.  A clustered Xlang Engine would be bound to the
> virtual machine.  What type of 'portability' are you looking for?
>
> Sincerely,
>
>
> Everett Yang
> DSI - Microsoft BizTalk Server
>
> This posting is provided ?AS IS? with no warranties, and confers no rights
.
> Subscribe at
> [url]http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp[/ur
l]
> &SD=msdn

[ Post a follow-up to this message ]

Ports and Channels are not bound to any file system.  They are all stored
in your InterchangeBTM database.

Sincerely,


Everett Yang
DSI - Microsoft BizTalk Server

This posting is provided “AS IS” with no warranties, and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn

[ Post a follow-up to this message ]

Hi Ambrish,

My first impression is that you force your developers to use the same file
structure on the dev and test machines as already exists in production.
There's no excuse for a developer to make it hard on the Configuration
Manager.

--- Nick

"ambs" <ambrish.jhaveri@iflexsolutions.com> wrote in message
news:16f63e0e.0402232108.2ee555ce@posting.google.com...
> Hi,
> I am looking at deployment portability primarily.
> For eg. I am doing my development in dev environment where directory
> structure is different from my production environment where I want to
> finally deploy my xlangs for execution...now since the ports and
> channels are bound to the local system resources like file system
> etc....
> how do i ensure deployment portability...
>
> Thanks,
>
> Ambrish
>
>
>
> evyang@online.microsoft.com (Everett Yang) wrote in message
news:<cNRNZXl#DHA.744@cpmsftngxa06.phx.gbl>... 
the 
the 
rights. 
http://support.microsoft.com/defaul...msdn/nospam.asp
 

[ Post a follow-up to this message ]