Hosting business component

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Technical Evangelists,

Currently, I create separate window service to host different business
component. Is there a better way to do this? One of the way I can think of is
webservice.

Please advise.

Thank you very much.

RedDevil
 
Hello Red,

Could you describe what kind of app you are developing and what are the requirements?

Enterprise Services as an option for hosting. Btw, for such cases your can
consider using BizTalk.


---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

RD> Technical Evangelists,
RD>
RD> Currently, I create separate window service to host different
RD> business component. Is there a better way to do this? One of the way
RD> I can think of is webservice.
RD>
RD> Please advise.
RD>
RD> Thank you very much.
RD>
RD> RedDevil
RD>
 
Hi Mike,

Thanks for your reply.

Actually, these business components are written in VC++ (ATL Window Service)
and I intend to port this to .NET. In these window services, besides, doing
its main functionality, it has to do to audit trail logging as well as
sending notification to indicate the service is still alive. It uses DCOM to
communicate between 2 business components.

In the .NET platform, I'm thinking of alternative way to host these business
components instead of using window service.

I hope my explanation shed some light for you. :)
 
Hello Red,

What the reason of rewriting your services? Why not, for example, just wrap
them into web-services?!

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

RD> Hi Mike,
RD>
RD> Thanks for your reply.
RD>
RD> Actually, these business components are written in VC++ (ATL Window
RD> Service) and I intend to port this to .NET. In these window
RD> services, besides, doing its main functionality, it has to do to
RD> audit trail logging as well as sending notification to indicate the
RD> service is still alive. It uses DCOM to communicate between 2
RD> business components.
RD>
RD> In the .NET platform, I'm thinking of alternative way to host these
RD> business components instead of using window service.
RD>
RD> I hope my explanation shed some light for you. :)
RD>
RD> "Michael Nemtsev" wrote:
RD>
Hello Red,

Could you describe what kind of app you are developing and what are
the requirements?

Enterprise Services as an option for hosting. Btw, for such cases
your can consider using BizTalk.

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo

RD> Technical Evangelists,
RD>
RD> Currently, I create separate window service to host different
RD> business component. Is there a better way to do this? One of the
way
RD> I can think of is webservice.
RD>
RD> Please advise.
RD>
RD> Thank you very much.
RD>
RD> RedDevil
RD>
Click to expand...
Click to expand...
 
Hi Mike,

More of support issue. There are only 2 developers who are proficient in
VC++, my colleague and I. He is now on different project and I'm more in
project management as well system design and my new team members are .NET
trained. :)


Michael Nemtsev said:
Hello Red,

What the reason of rewriting your services? Why not, for example, just wrap
them into web-services?!

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

RD> Hi Mike,
RD>
RD> Thanks for your reply.
RD>
RD> Actually, these business components are written in VC++ (ATL Window
RD> Service) and I intend to port this to .NET. In these window
RD> services, besides, doing its main functionality, it has to do to
RD> audit trail logging as well as sending notification to indicate the
RD> service is still alive. It uses DCOM to communicate between 2
RD> business components.
RD>
RD> In the .NET platform, I'm thinking of alternative way to host these
RD> business components instead of using window service.
RD>
RD> I hope my explanation shed some light for you. :)
RD>
RD> "Michael Nemtsev" wrote:
RD>
Hello Red,

Could you describe what kind of app you are developing and what are
the requirements?

Enterprise Services as an option for hosting. Btw, for such cases
your can consider using BizTalk.

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/
"The greatest danger for most of us is not that our aim is too high
and we miss it, but that it is too low and we reach it" (c)
Michelangelo

RD> Technical Evangelists,
RD>
RD> Currently, I create separate window service to host different
RD> business component. Is there a better way to do this? One of the
way
RD> I can think of is webservice.
RD>
RD> Please advise.
RD>
RD> Thank you very much.
RD>
RD> RedDevil
RD>
Click to expand...
Click to expand...
Click to expand...
 
Hello Red,
to do to audit trail logging as well as sending notification to indicate
the >>service is still alive. It uses DCOM to communicate between 2 business
components

So as was mentioned you can:
1) the keep the same scheme, only porting to the .NET - the same services
the same communication, albeit instead of dcom use pipes :) or smth like
this, but not dcom :)

2) use webservices. but the best case will be to move business logic to the
additional layer, apart from notification services and notification services.
And keep webservice as simple as possible. This allows u to change the hoster
without any changes in business logic

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

RD> Hi Mike,
RD>
RD> More of support issue. There are only 2 developers who are
RD> proficient in VC++, my colleague and I. He is now on different
RD> project and I'm more in project management as well system design and
RD> my new team members are .NET trained. :)
 
Hi Mike,

Thanks. Appreciated.

Michael Nemtsev said:
Hello Red,
to do to audit trail logging as well as sending notification to indicate
the >>service is still alive. It uses DCOM to communicate between 2 business
components

So as was mentioned you can:
1) the keep the same scheme, only porting to the .NET - the same services
the same communication, albeit instead of dcom use pipes :) or smth like
this, but not dcom :)

2) use webservices. but the best case will be to move business logic to the
additional layer, apart from notification services and notification services.
And keep webservice as simple as possible. This allows u to change the hoster
without any changes in business logic

---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

RD> Hi Mike,
RD>
RD> More of support issue. There are only 2 developers who are
RD> proficient in VC++, my colleague and I. He is now on different
RD> project and I'm more in project management as well system design and
RD> my new team members are .NET trained. :)
Click to expand...
 
Back
Top