You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

The net.dante.otrs.OTRSOutlookCalendar JAVA class take one integer parameter which is the number of minutes to subtract from the current time, in order to determine the date and time range of the tickets required.

In a nutshell, the OTRSOutlookCalendar  retrieves all of the tickets from the sde.otrs_incidents table that have changed in the last 60 minutes. For each record, the application creates a calendar appointment within the Microsoft Outlook Calendar called otrs_nm. Once completed, the application creates the special Yellow coloured appointment to signify the date and time the OTRSOutlookCalendar class ran

The class uses the standard AuditLog class to write log message to /tmp/otrs/Outlook-YYYYMMDD.log. The location and name of the log file is configurable from within the otrs.properties file

MySQL Database Connection

The OTRSConsumer connects to one MySQL databass:

sde database on test-msr.geant.net using user reportsUser

Microsoft Outlook Calendar Connection

The OTRSOutlookCalendar connects to the Microsoft Outlook Calendar called otrs_nm using a third party JAVA library called JWebServices (http://www.independentsoft.com/jwebservices/index.html). The JWebServices relies on the Microsoft Restful API End-Point: https://outlook.office365.com/EWS/Exchange.asmx and requires a username of OTRS-NM@dante.net and a password that is stored in KeyPass

Each Calendar event within the Calendar has a unique identifier e.g.

AAMkADY4NWY1ZGZjLWVlODctNDc0My1iYjZhLWI1YTQzOTkxZWRiZQBGAAAAAACQIcYyjiQ4RaeXxPnW1anTBwBQg5gjlEzhTIaEr3IDbZFDAAAAAAEOAACJtx6ztQJURpaELxuim/rjAAEENyAHAAA=

There is a special Calendar event which is created as a Yellow coloured appointment. It signifies the date and time the OTRSOutlookCalendar was run. This gives the end-users a visual check to ensure the service is running correctly.

The unique identifier for this event is stored within the  sde.outlook_incidents table with a ticket_number set to 9999999999999999



  • No labels