I have a out of proc COM server (ATL based) and a Java app that instantiates objects from this COM server on the same machine.
What more is needed to DCOM enable it? Is work needed on the COM server only or server and client?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a out of proc COM server (ATL based) and a Java app that instantiates objects from this COM server on the same machine.
What more is needed to DCOM enable it? Is work needed on the COM server only or server and client?
Usually all you need is to have the proxy interface registered on the client side (as well as on the server-side) via regsvr32. If your ATL objects are all IDispatch based, and thats how you call them (not via a custom interface) then a default proxy is already registered on Windows Machines.
At that point you should only need to specify the machine name of the server where the actual objects reside.
As with any DCOM remoting you may have issues with DCOM permissions from the client to the server, which can be typically be resolved by using DCOMCnfg on the server side (Possibly on the client as well, if callbacks are being used). And of course potential Firewall problems – you may need to allow an exception for port 135 (RPC Mapper used by DCOM) to get through on the server.