- COM: In process component, not reachable accross process boundaries and machines. In your case the com connector must be registered on pc1 to use com.
- DCOM: Out of process component, reachable accross machine boundaries. Keep in mind to register as dcom server on the machine running the com connector (pc2) and as dcom client (client side proxy) on the machine you'd like to talk to the com connector (pc1). Using this method, you have to configure the dcom server and perhaps the client manually with DCOMCNFG.EXE.
- COM+: Register the com connector in the component services of a machine (formally known as distributed transaction coordinator). This gives you the widest range of possibilities. You can configure the com connector as "in process" or "out of process"-component and a lot more (the user the com connector is running with, object creation and -livetime, etc.). Try to register the com connector on pc1 with COM+. If it works, try to migrate to pc2 using COM+.
In my cases the COM+ method works best. I had some trouble with the COM method and IIS. As I read in the online help, using the com connector with IIS is only possible via COM+.
I hope i could give you some hints.
Regards
Andreas Gahr
-----Urspr�ngliche Nachricht-----
Von: ddjy [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 18. Mai 2004 07:33
An: [EMAIL PROTECTED]
Betreff: [development-axapta] Axapta + BizTalk
Hi all,
Can you help me in my situation. I'm trying to install following
environment
PC1 - BizTalk 2002, SQL Server 2000 (for BizTak purposes BizTalk),
Commerce
Gateway Server, MS Server 2000 (and its IIS)
PC2 - Axapta 3 (sp2), Commerce Gateway Client, MS Windows XP
Professional
So, I have all this stuff installed and I have a problem.
I'm able to post purchase order (PO) and I have an appropriate
record in
Axapta Gateway Queue. Then I post this record to Biztalk and I see a
file
there. That's ok. Then I use Biztalk's "receive functions" to send
the file
to an appropriate port and here is a following error in Event Viewer
Internal error -500 in gateway.asp in the line 34.
Here is this line
=============
set businessConnector = Server.Createobject
("AxaptaComConnector.Axapta.2.1")
=============
so, this COM - object exists on PC2 only and it's supposed that PC1
can use
it by DCOM technology but...
But it doesn't work.
I installed all this stuff to one PC and all was ok. No problems at
all in
both directions. But I don't know how to mend it. Does anyone has
any idea?
Probably, I should customize this "AxaptaComConnector.Axapta.2.1"
COM-object as DCOM on PC1 manually? But I thought that Axapta had to
do
it...
Anyway, I'm very interested how to fix it and I'll do appreciate
your help.
Thanks.
Yahoo! Groups Links
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
