• New calendar REST service in the 9.0 version of the extension library

    By Dave Delay 6 years ago

    Included in the first 9.0 version of the extension library (released last week) is a new REST service for accessing Domino calendar data.  I just posted a developer guide in the documentation section:

     

    http://www.openntf.org/Projects/pmt.nsf/D528CE874EFFDEC886257B5B0080CA65/%24file/Domino%20Calendar%20Service.pdf

     

    Since the calendar service depends on core C&S APIs added in IBM Notes and Domino Social Edition, it requires 9.0.  It will not work on Domino 8.5.3.

     

    Because this is the first public version of the calendar service, we are anxious to get your feedback.  Please try it and let us know what you think.

     

    Thanks.

     

    -- The Domino REST services team

    • HREF file path returns

      By John T Robertson 6 years ago

      I was testing out the 9.0 services and found that the ".../api/calendar and the ".../api/mail" call returned invlid HREF strings if the file name contains ".nsf". The JSON return looks like:

      {
        "calendars":[
          {
            "owner":{
              "displayName":"",
              "distinguishedName":"",
              "homeServer":"",
              "email":""
            },
            "links":[
              {
                "rel":"events",
                "href":"http:\/\/\/Mail\/.nsf.nsf\/api\/calendar\/events"
              },
              {
                "rel":"invitations",
                "href":"http:\/\/\/Mail\/.nsf.nsf\/api\/calendar\/invitations"
              }
            ]
          }
        ]
      }

      All of users are set up with fully qualified file names. - "filepath\filename.nsf"

      I searched the Discussions and Defects and could not find any reports of this issue. The other parts of JSON, calls to messages or events, appear correct.

      Any thoughts?

      John

       

      • Known problem ...

        By Dave Delay 6 years ago

        Yes.  Sorry about that.  We also discovered that problem and we've fixed it.  The fix will be in the next release of the extension library.  While you are waiting for the fix, you can workaround the problem by removing the .nsf from the file name in your test user's person record.

         

        FYI, there is a another change coming too.  In the next release, the calendar service responses will include relative URLs.  So you should see this:

         

              "links":[
                {
                  "rel":"events",
                  "href":"\/Mail\/.nsf\/api\/calendar\/events"
                },
                {
                  "rel":"invitations",
                  "href":"\/Mail\/.nsf\/api\/calendar\/invitations"
                }
              ]

         

        Relative URLs work better in some configurations where there is a proxy between the client and the Domino server hosting the calendar service.

         

        Thanks.

         

        -- Dave

    • Downloads disabled?

      By Mike Brown 6 years ago

      I can't download the library.  The project status says "Disabled" and "Downloads Disabled".

      I am logged into OpenNTF.  Am I missing something?

      • Can't reproduce ...

        By Dave Delay 6 years ago

        Mike,

         

        I just downloaded the latest 9.0.1 version of the extlib.  I also downloaded the latest 9.0 version.  Both downloaded without problems.

         

        Please respond with a link to the page that's giving you trouble.

         

        Thanks.

         

        -- Dave

    • Can't get Calendar API installed

      By Mike Brown 6 years ago

      I've installed the my siteupdate nsf and imported the xml from the (extracted) updateSiteOpenNTFExtended.zip files.  I've also added the OSGI_HTTP_DYNAMIC_BUNDLES variable in the notes.ini to point to my siteupdate nsf.  (NB: the readme.pdf shows this variable with spaces instead of underscores!)

      But I don't get the "Calendar" option for the Enabled Services field of my Web Configuration doc.  At my server console, a tell osgi ss com.ibm.domino.services command gives the following output:

      [08946:00002-3584325440] 17/11/2013 04:13:16   id       State       Bundle

      [08946:00002-3584325440] 17/11/2013 04:13:16   17       <<LAZY>>    com.ibm.domino.services.mail_9.0.1.v00_01_20131029-1400
      
      [08946:00002-3584325440] 17/11/2013 04:13:16   20       INSTALLED   com.ibm.domino.services.freebusy_9.0.1.v00_01_20131029-1400
      
      [08946:00002-3584325440] 17/11/2013 04:13:16   182      <<LAZY>>    com.ibm.domino.services_9.0.0.v00_00_20130301-1506
      

      I.e. it doesn't show the calendar services as it does on the readme.pdf example.

      The server is Domino 9.0 on 64-bit Linux. 

       

      • Please install the last 9.0 version ...

        By Dave Delay 6 years ago

        Mike,

         

        It looks like you've installed the 9.0.1 version of the extlib, but that won't work if your Domino server is 9.0.  Please install this version of the extlib instead:

        http://www.openntf.org/internal/home.nsf/release.xsp?databaseName=CN=NotesOSS2/O=NotesOSS!!Projects/pmt.nsf&documentId=ECF0C3D8AEE6962886257C0C006914E5&action=openDocument

         

        By the way, if you have access to a 9.0.1 server, you shouldn't need to install the extlib at all.  The calendar service is built into 9.0.1.

         

        Also, when you get to the point where you are enabling the calendar service, you won't find "Calendar" in the keyword list.  You'll have to type the word "Calendar".  (In other words, the keyword list lets you add new entries.)

         

        Thanks.

         

        -- Dave

        • Upgraded

          By Mike Brown 6 years ago

          Thanks again, Dave.

           

          I've upgraded my test server to 9.0.1 and have got a little further now.

    • Code 403: Forbidden?

      By Mike Brown 6 years ago
      I've now upgraded to Domino 9.0.1, but all my attempts to query the calendar API result in the following JSON returned:
      
      {
          "code":403,
          "text":"Forbidden"
      }

       

      Please see following blog post for my test server entry details:

      http://www.browniesblog.com/A55CBC/blog.nsf/dx/14112013075113MBRSG4.htm?opendocument&comments#anc1

       

      You can see that using the URLs on that post, my test server Calendar entry returns results.  But using the new API gives the 403.  Examples of API calls that I've tried:

      http://184.73.169.93:8080/mail/testmail.nsf/api/calendar/events

      http://184.73.169.93:8080/api/calendar