Kay,

Yes it can.  I suggest that in addition to the Knowledge Center documentation you also have a look at the blog by Jason Tavoularis.  

Connecting to Sharepoint will require a few parameters on the JDBC connection:
AuthenticationMethod=HttpHeader;AuthHeader=Authorization;SecurityToken="Bearer xxxxxxxxxxxxxxxx"
(Replace xxxxxxxxxxxxx with the contents of your security token.)

Also, if you wish to customize the manner in which the driver captures data from the API (choose your own schema, table, column names, etc.) or call multiple APIs to generate multiple tables in one schema, then use the ' Config="filename" ' method of invoking the driver.  

Rather than start from nothing for the config file contents, in the AUTOREST schema generated by a ' Sample="apiurl" ' invocation, capture the JSON value in the Configuration table, Content column.  This is the machine generated version of the config file which maps REST API JSON into Cognos database entries. Copy that JSON into a text editor, pretty-print it, and adjust as needed per the documentation and your need for specific data elements.

Save that file to a location visible to the Cognos system (e.g. the dropbox accessible via sftp).  You may have to determine from a system administrator the full root path name to that folder so you can specify it in the ' Config="filename" ' parameter.

Kay,

Yes it can.  I suggest that in addition to the Knowledge Center documentation you also have a look at the blog by Jason Tavoularis.  

Connecting to Sharepoint will require a few parameters on the JDBC connection:
AuthenticationMethod=HttpHeader;AuthHeader=Authorization;SecurityToken="Bearer xxxxxxxxxxxxxxxx"
(Replace xxxxxxxxxxxxx with the contents of your security token.)

Also, if you wish to customize the manner in which the driver captures data from the API (choose your own schema, table, column names, etc.) or call multiple APIs to generate multiple tables in one schema, then use the ' Config="filename" ' method of invoking the driver.  

Rather than start from nothing for the config file contents, in the AUTOREST schema generated by a ' Sample="apiurl" ' invocation, capture the JSON value in the Configuration table, Content column.  This is the machine generated version of the config file which maps REST API JSON into Cognos database entries. Copy that JSON into a text editor, pretty-print it, and adjust as needed per the documentation and your need for specific data elements.

Save that file to a location visible to the Cognos system (e.g. the dropbox accessible via sftp).  You may have to determine from a system administrator the full root path name to that folder so you can specify it in the ' Config="filename" ' parameter.

Kay,

I am wondering if you were ever able to get your data source set up to connect to SharePoint?  

Kay,

Yes it can.  I suggest that in addition to the Knowledge Center documentation you also have a look at the blog by Jason Tavoularis.  

Connecting to Sharepoint will require a few parameters on the JDBC connection:
AuthenticationMethod=HttpHeader;AuthHeader=Authorization;SecurityToken="Bearer xxxxxxxxxxxxxxxx"
(Replace xxxxxxxxxxxxx with the contents of your security token.)

Also, if you wish to customize the manner in which the driver captures data from the API (choose your own schema, table, column names, etc.) or call multiple APIs to generate multiple tables in one schema, then use the ' Config="filename" ' method of invoking the driver.  

Rather than start from nothing for the config file contents, in the AUTOREST schema generated by a ' Sample="apiurl" ' invocation, capture the JSON value in the Configuration table, Content column.  This is the machine generated version of the config file which maps REST API JSON into Cognos database entries. Copy that JSON into a text editor, pretty-print it, and adjust as needed per the documentation and your need for specific data elements.

Save that file to a location visible to the Cognos system (e.g. the dropbox accessible via sftp).  You may have to determine from a system administrator the full root path name to that folder so you can specify it in the ' Config="filename" ' parameter.