Michael Bell
2010-03-02 21:37:00 UTC
I am trying to write a client app that needs to access a Groupwise 6.5
server running on Linux. The client app needs ability to do certain
things that are supported by the Object API, (which is, as per Object
API documentation: With the Object API, you can create your own client
application. It provides access to the Address Book, documents, mail
messages, appointments, tasks, notes, and phone messages.)
However, it is my understanding that Object API is based on OLE
Automation, and therefore
1) cannot run on linux, and
2) does not support remote calls (e.g. run client from Windows to
access Groupwise server on Linux).
It is also my understanding that soap interface is supported only with
Groupwise 7 and 8. Assuming what I have said is accurate, what then is
my best option?
You have no good options really. You are correct in all yourserver running on Linux. The client app needs ability to do certain
things that are supported by the Object API, (which is, as per Object
API documentation: With the Object API, you can create your own client
application. It provides access to the Address Book, documents, mail
messages, appointments, tasks, notes, and phone messages.)
However, it is my understanding that Object API is based on OLE
Automation, and therefore
1) cannot run on linux, and
2) does not support remote calls (e.g. run client from Windows to
access Groupwise server on Linux).
It is also my understanding that soap interface is supported only with
Groupwise 7 and 8. Assuming what I have said is accurate, what then is
my best option?
understandings. There was soap available on 6.5 (/soapdev-enabled IIRC),
but it is VERY buggy and unsupported.
You would have to write a windows server component that served as your
proxy to do anything. You'd deploy a windows server component using
object api and expose an xml/soap/rest interface and call it. That's
reasonably feasible. But of course it's going to have a fair amount
extra work, some performance degradation, and some folks have struggled
with memory leaks with long time COM usage.
If all you need is to create messages, use SMTP. Basic access?POP/IMAP.
But of course these are quite limited as far as exposing the richness of
GW options.
Even GW 6.5 on linux is only sort of stable [ and 6.5 itself is no
longer supported] - I'd STRONGLY recommend considering an upgrade.