DCOM provides a standardized basis for creating and integrating distributed software components. External client applications can use DCOM as infrastructure for their communication with SAP servers, to access R/3 components. With this technology, R/3 components such as BAPIs or remote function modules appear as COM objects and use the runtime environment of the Microsoft Transaction Server (MTS). The DCOM Connector provides a C++ Template Library developed by SAP, which you can use to create COM objects from business objects of the R/3 system and administer them. The two scenarios below describe the different uses of the DCOM Connector: PC Client Applications

Client applications on a frontend use DCOM to access COM objects installed on one or more MTS servers. In such a scenario, all you need to do is distribute the client application software to different PCs. It is not necessary to install any additional SAP software on the PC, since MTS components are accessed remotely. The DCOM Connector allows you to q Concentrate on programming the client application without having to consider the RFC protocol. q Simplify table handling with ADO using standard tools (for example, Data Bound Control). q Use comfortable development environments (VB 5/6) for developing the clients. WEB Scenario You use Active Server Pages (ASP) to create WEB pages whose HTML coding contains executable scripts on the server side. ASP communicates with the MTS via DCOM to access MTS components. The MTS can run on the same machine as the web server (IIS), but this is no requirement.

Download SAP Tutorial Book: The DCOM Connector Manual