Hello,

regarding Outlook "Integration" - this seems to be a nice solution:

http://www.hdt-software.com/en/itsm4outlook

(I don't work for hdt software).

Maybe they have a calendar integration, too?

Regards
Rüdiger

> Jason Miller <jason.mil...@gmail.com> hat am 1. Dezember 2016 um 22:27 
> geschrieben:
> 
>     **
>     What version of Exchange are you working with?
> 
>     I have a similar requirement, to work with shared calendars but I have 
> been holding out until we upgrade to Exchange 2016 and have access to the new 
> REST web services. I looked at some of the SOAP stuff, while powerful, I 
> didn't want to go the hard route when the easy route was right around the 
> corner.
> 
>     
> https://blogs.technet.microsoft.com/exchange/2015/05/05/exchange-server-2016-architecture/
> 
> 
> 
>     Extensibility
> 
>     (scheduled for a future CU): Office 365 introduced the REST APIs (Mail 
> https://msdn.microsoft.com/office/office365/APi/mail-rest-operations , 
> Calendar 
> https://msdn.microsoft.com/office/office365/APi/calendar-rest-operations , 
> and Contact 
> https://msdn.microsoft.com/office/office365/APi/contacts-rest-operations  
> APIs), and now these APIs are available in Exchange Server 2016. The REST 
> APIs simplify programming against Exchange by providing a familiar syntax 
> that is designed with openness (e.g., open standards support JSON, OAUTH, 
> ODATA) and flexibility (e.g., granular, tightly scoped permission to access 
> user data). These APIs allow developers to connect from any platform, whether 
> it be web, PC, or mobile. SDKs exist for.NET, iOS, Android, NodeJS, Ruby, 
> Python, Cordova, and CORS for use in single page JavaScript web apps.
> 
>     What about Exchange Web Services (EWS)? All existing applications that 
> leverage EWS will continue to work with Exchange Server 2016. We are, 
> however, focusing new platform investments on the REST APIs and the apps for 
> Office extensibility model. We expect to make significantly fewer investments 
> in EWS so that we can focus our resources on investing in a single modern API 
> that will, over time, enable most of the scenarios that our partners 
> currently use EWS.
> 
> 
> 
>     On Wed, Nov 30, 2016 at 8:22 AM, Irving, Isabel (ACCESS LLP) 
> <isabel.irv...@access.uk.com mailto:isabel.irv...@access.uk.com > wrote:
> 
>         > > Oh yes good point, I'll make enquiries about the certificate.
> > 
> >         We have generally found that remedy's web services are pretty 
> > limited.  If one single web service doesn't include ALL the methods then it 
> > doesn't seem to work. E.g. in this case the WSDL seems to refer to xsd 
> > files which in turn refer to other xsd files.
> > 
> >         In the past we've had someone built a "wrapper" application so that 
> > remedy can be presented with a simple WSDL that contains all the methods in 
> > one place.
> > 
> >         So I'm beginning to think that simply consuming an existing web 
> > service isn't going to be that simple after all..
> > 
> >         -----Original Message-----
> >         From: Action Request System discussion list(ARSList) 
> > [mailto:arslist@ARSLIST.ORG mailto:arslist@ARSLIST.ORG ] On Behalf Of 
> > Grooms, Frederick W
> >         Sent: 30 November 2016 14:41
> >         To: arslist@ARSLIST.ORG mailto:arslist@ARSLIST.ORG
> >         Subject: Re: Outlook Integration
> > 
> >         Since you are using HTTPS have you loaded the certificate into the 
> > keystore (or told SoapUI which certificate to use)?
> > 
> >         -----Original Message-----
> >         From: Action Request System discussion list(ARSList) 
> > [mailto:arslist@ARSLIST.ORG mailto:arslist@ARSLIST.ORG ] On Behalf Of 
> > Irving, Isabel (ACCESS LLP)
> >         Sent: Wednesday, November 30, 2016 6:19 AM
> >         To: arslist@ARSLIST.ORG mailto:arslist@ARSLIST.ORG
> >         Subject: Outlook Integration
> > 
> >         Hello!
> > 
> >         We're looking to create a room booking system which would also 
> > integrate with Outlook.  We're on Outlook 2007 and Remedy 8.1.
> > 
> >         My preference would be to use web services because that is tried 
> > and tested in our environment.
> > 
> >         Has anyone else tried this?
> > 
> >         What we've tried so far is connecting to the Services.wsdl in SOAP 
> > UI.  If I just put the wsdl URL in "Initial WSDL" field it prompts me for a 
> > username, password and domain and after entering that, I get this error:
> > 
> >         Error loading [https://webmail.access.uk.com/ews/Services.wsdl 
> > https://webmail.access.uk.com/ews/Services.wsdl ]: 
> > org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: 
> > Unexpected end of file after nul I get EXACTLY the same error if I 
> > intentionally put in wrong credentials.
> > 
> >         The email team have created a user for me to test with, and that 
> > user has "exchange impersonation rights".  Is that necessary or should it 
> > also work if I connect as myself (i.e. a normal outlook exchange user).
> > 
> >         Any pointers?  I feel like this should be a straightforward 
> > operation but maybe it isn't...
> > 
> >         Thanks!
> >         Isabel
> > 
> > 
> >         Server Information
> >         Application server version: 8.1.00 201301251157 Operating system: 
> > SunOS 5.10 On Sun Solaris virtual cluster
> > 
> >         Database
> >         Database version: 11.1.0.6.0 - 64bit Production On Sun Solaris 
> > virtual cluster
> > 
> >         Mid Tier Version
> >         8.1.SP02 Patch 001 201505281150 Hotfix
> >         Installation Directory
> >          Web Server Information
> >         Apache Tomcat/7.0.53
> >         Operating System Name
> >         Windows Server 2012
> >         Java Version
> >         1.7.0_80
> > 
> >         Glasgow - UK Council of the Year 2015
> > 
> >         
> > _______________________________________________________________________________
> >         UNSUBSCRIBE or access ARSlist Archives athttp://www.arslist.org 
> > "Where the Answers Are, and have been for 20 years"
> > 
> > 
> >         Glasgow - UK Council of the Year 2015
> > 
> >          ***Disclaimer****
> > 
> >          This e-mail and any attachments are for the intended addressee(s) 
> > only and may contain confidential and/or privileged material. If you are 
> > not a named addressee, do not use, retain or disclose such information. 
> > This email is not guaranteed to be free from viruses and does not bind 
> > Access in any contract or obligation. SERVICE GLASGOW LLP trading as ACCESS 
> > Registered in Scotland. No: SO301705 Registered Office: 220 High Street, 
> > Glasgow, G4 0QW
> > 
> >         
> > _______________________________________________________________________________
> >         UNSUBSCRIBE or access ARSlist Archives athttp://www.arslist.org
> >         "Where the Answers Are, and have been for 20 years"
> > 
> >     > 
>     _ARSlist: "Where the Answers Are" and have been for 20 years_
> 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to