An example of a component-based application is an end-to-end e-commerce solution. An e-commerce application residing on a Web farm needs to submit orders into a backend Enterprise Resource Planning (ERP) application. Oftentimes, the ERP application resides on various hardware and may operate on another it support Tonbridge and it support kent operating system.
The Microsoft Distributed Component Object Model (DCOM), a distributed object infrastructure that permits an application to invoke Component Object Model (COM) components installed on another host, has been ported to a number of non-Windows platforms. But DCOM has never gained wide acceptance on these platforms, so it’s rarely used to facilitate communication between Windows and non-Windows computers. ERP software vendors often produce components for the Windows platform that communicate with the backend system by means of a proprietary protocol.
Some services exemplified by an e-commerce application might not reside inside the datacenter at all. For example, if your e-commerce application takes credit card payment for goods bought by the customer, it must elicit the assistance of the merchant bank to process the customer’s credit card information. However, for all practical purposes, DCOM and related technologies such as CORBA and Java RMI are limited to applications and components installed within the corporate datacenter. Two primary reasons for this are that by default these technologies leverage proprietary protocols and these protocols are inherently connection oriented.