Integrating Microsoft Office 365

yuuvis® RAD 10.x

The 'office365' and 'dashlet365' services integrate Microsoft Office 365 in order to display and allows users to collaborate on Word, Excel, and PowerPoint documents.

One of the following Microsoft licenses is required: Microsoft 365 Business Standard or higher, Microsoft 365 Apps for Business, Microsoft 365 Apps for Enterprise, Office 365 E3 or Office 365 E5, and corresponding Microsoft accounts for the users.

File Sizes

A 60-second timeout as well as a size limit for file transfers are specified for displaying and editing files.

Application	Mode	Size limit	Comment
Word	Display	-	The only limit in terms of size is imposed by the timeout.
Word	Edit	100 MB
Excel	Display	25 MB
Excel	Edit	25 MB
PowerPoint	Display	-	The only limit in terms of size is imposed by the timeout.
PowerPoint	Edit	300 MB	There is an additional size limit of typically 100 MB for files embedded in PowerPoint files. Embedded '.wav' files have a size limit of 100 KB.

Configuration

The Office services are installed via yuuvis® RAD service-manager. They must be activated, integrated, and configured. Office documents are then opened in the Microsoft Office 365 dashlet using these configurations.

Office documents that are attached to an e-mail are not opened in the Microsoft Office 365 dashlet; instead, they are opened as a PDF in the content preview.
In yuuvis® RAD services-admin only the 'office365' service is displayed.

Activation

The Office services are activated via the <service-manager>\config\servicewatcher-sw.yml configuration file.

Change the value of the instances parameter for the 'office365' service from 0 to 1.

This change is activated with a time delay. If necessary, restart yuuvis® RAD service-manager.

The following sections must be added again in the servicewatcher-sw.yml configuration file when updating from yuuvis® RAD 9.x to yuuvis® RAD 10.x.

- name: office365
  type: microservice
  profiles: prod,cloud,red
  instances: 1
  memory: 1024M
  port: 7880
  path: ${appBase}/office365/office365-app.jar
  options:
  - -Dfile.encoding=UTF-8
  
- name: dashlet365
  type: webresource
  path: 'C:\Program Files (x86)\OPTIMAL SYSTEMS\yuuvis RAD\service-manager\data\webresource\public\dashlet365\dashlet365.zip'

Enter the path and file name of dashlet365.zip as the path for 'dashlet365'. Default: C:\Program Files (x86)\OPTIMAL SYSTEMS\yuuvis RAD\service-manager\data\webresource\public\dashlet365\dashlet365.zip.
Paths that contain spaces require single quotes.

Integration

Integration is achieved via the <service-manager>\config\gateway-prod.yml configuration file located in the routing.endpoints section.

routing.endpoints: 
  ...
  - name: 'dashlet365'
    url: 'http://client/dashlet365'
  - name: 'office365'
    url: 'http://office365/api'
                                                            

After saving the configuration file, you will need to restart the 'gateway' service.

Configuration

You will need the following data from OPTIMAL SYSTEMS in order to configure authentication: OPTIMAL SYSTEMS tenant ID and OPTIMAL SYSTEMS tenant secret. The data is available on request.

Enter this data for the connection and authentication in the <service-manager>\config\office365-prod.yml configuration file.

tenant:
  id: OS-Tenant-ID
  secret: OS-Tenant-Secret
  provider-url: https://provider.prod.enaio.io/
  host-url: https://host.prod.enaio.io/
  working-dir: ${enaio.data.path}/o365
  recovery:
    enable: true 
                                                            