callout com+ via proxystub

hi,

i have developed a post callout routine. When i install the component
on the crm server as com+ it works fine.

Now i install the component on a other server as com+. I create a
proxstub/msi-package and install this on the crm server.

When i use the com+ proxy on the crm server with a own testtool it
works also fine, but when i use the crm webclient the server doesn't
make the callout to my compontent.

Have anybody a idea whats happen or what's wrong?

Thank's for help

Ralf

Matt
Fri Aug 26 13:12:10 CDT 2005

Best guess is that you are losing some authentication. I would shy away from
this approach as you have some potential performance issue sin the future with
this and if the other server is down, the callout will fail and this will impact
your online response of your users.

If you truly need to send the processing to another machine, look into other
ways, like MSMQ, to pass the message to the other server and then process it.
This makes the callout pretty trim and can the queue up messages if the other
server is down.

Matt Parks
MVP - Microsoft CRM

----------------------------------------
----------------------------------------
On 26 Aug 2005 10:48:33 -0700, "Ralf" <ralf.hille@tec-si.net> wrote:

hi,

i have developed a post callout routine. When i install the component
on the crm server as com+ it works fine.

Now i install the component on a other server as com+. I create a
proxstub/msi-package and install this on the crm server.

When i use the com+ proxy on the crm server with a own testtool it
works also fine, but when i use the crm webclient the server doesn't
make the callout to my compontent.

Have anybody a idea whats happen or what's wrong?

Thank's for help

Ralf

Ralf
Sat Aug 27 05:21:07 CDT 2005

in general i have understand the benefit when i use MSMQ.

Also is the aspect that the other server is down a important point of
view to make a stable program.

But it is not clear for me why the ms crm is not able to use com+ via
proxystub.

But with your idea/aspect i try to design a local com+ component as a
wrapper. Inside i can try a late binding of other com+ component and
can catch any problem is the other server is down or other problems in
the communication i can store a message in a MSMQ.

thanks

Ralf

MJ
Mon Aug 29 11:22:12 CDT 2005

Matt has the right approach here for the reasons you've both listed. The
reason the CRM platform can't instantiate your component is because the code
explicitly forbids it. At least that's the way I remember it. I'd have to go
look at the 1.x code again, but I'm pretty sure it's forcing a
CLSCTX_LOCAL_SERVER and the COSERVERINFO pulls in the local server name. I
opened a bug or two against this design in the 1.x timeframe but was
overruled for security and stability reasons.

Queue-based callouts are your friends :)