Extending web services for emails

I’m wanting to support creation of emails via web services but I’m not sure what the best approach would be. Do I create my own web service, override DocumentManagement and put the CreateEmail method in there? I thought I would just model this method on CreateDocument but not sure how I get it to create an Email subtype. Would I just set .fType to “Email”?

I am working through the Creating a New Service and Creating a New SDO pages for CS 10.5 but don't really see how it should hang together.

Any pointers would be greatly appreciated.

Find more posts tagged with

Comments

eLink User

Hi Rob, Did you get what you wanted anyways this is not much of a help but I noticed when debugging how enterprise connect does the email it does it almost in a modern(REST ful) way.If you are watching this space more and more ot dev is turning into the REST ful areas frankly I don't really know the merits and demerits of either way.When I did this as a OI extension there was almost negligible code I wrote,all I was doing is basically setting the request object with the right params.Extending OI is very easy but if you do require synchronous output it can be tricky.

Writing your own soap web service is very rigid.One follows the "HelloWorld" example and when confident the oscript part works,then battle one or two days to get it as a .net service.I have not attempted this in CS10.5 but I don't recall overriding any OT code other than basically orphanning objects into ones ospace. There are some weird namespace rules otherwise the service(client code) will bark at you even if the oscript part works.I was not interested in making a java version.Hugh Ferguson is your go to guy for Java based qns...I had forgotten java for the most part so working through ANT build was very painful.Nevertheless I did get the WSDL to show up and get into livelink.

My personal opinion is if you trace the EC route and get a handle on the REST framework it might be easier.I also think OT is already going to make email happen soon I read somewhere.

..appu appnair appunair

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

Vanderpoel_Rob

Hi Appu,

Thanks for your response.

With regards to the email aspects of this work I'm reasonably comfortable with this as I've already extended Object Importer to handle emails, by looking at the Outlook integration as you suggested.

What's not clear to me is what I need to orphan into my ospace from the Document Management service and how to link in the email subtype. Basically how to link all the components together to extend the web service.

Fortunately, I only need to be able to support .NET with the web service.

My understanding is that there will be support for emails in CS16 but that's someway off, especially before the customer would be installing it.

Cheers

Rob

eLink User

Hi, there is a module available from OT Services EMEAwhich handles Outlook E-Mail import via all channels by extending the Document Properties module. I can provide more info tomorrow when I am back in the office. Regards, Michael--Michael FrommeSent via a mobile device

Vanderpoel_Rob

Hi Michael, I look forward to hearing about this

Rob