Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 10 Current »

For GEODI classifier OWA installation, you have to download Manifest.xml file with the method stated below and then forward it to Exchange Admin.

Conditions for Connection

  • This extention is installed on Outlook Web App or Exchange On-Premises/Exchange Online.

  • OWA server must access to GEODI server and SSL must be defined for GEODI address. Make sure this address is valid from UI.

  • User name and password must be created in such that they’ll not be changed and they should not get changed. In the case of change, same procedure must be repeated.

Creating Manifest File

  1. GEODI will create manifest file automatically. Download .xml file by pressing “Download Manifest” button in setup tab which itself is in GEODI Classifier settings.

  2. You can make an Add-In upload from Microsoft 365 Admin Center/Built-In Apps for all defined users or desired ones.

  3. After this process, the system will start distribution. Distribution phase may end between 3-24 hours.

ingilizce manifest sayfası.png

Troubleshooting

 OWA add-in doesn't appear while sending an e-mail in an On-Prem Exchange environment.

This is an issue that must be solved in Microsoft side. You should take the actions in the link below. It should work afterwards. You don’t have to re-create the manifest file.

https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/outlook-on-send-addins?tabs=classic#install-outlook-add-ins-that-use-on-send

 Add-in cannot be seen by OWA e-mail users.

There may be several reasons.

  1. Is the GEODI server running?

  2. Make sure that typed down GEODI URL address in the UI was correct before the manifest file is created. If it was wrong, the manifest creation and uploading must be repeated.

  3. Microsoft OWA servers must see the GEODI server. If you are using Exchange Online, GEODI address must be public.

  4. SSL must have been defined for the GEODI address. Be sure that SSL is defined and that it is not expired.

 Suddenly stopped working!

  1. Is the GEODI server running?

  2. Is the project that is used to create the manifest file still active? If not, revert the project or re-create it. In case of re-creation, the manifest process must be repeated.

  3. Is the TokenUser and its password still valid. If not, the manifest process must be repeated.

 Pop-up doesn't appear.

  1. SSL must have been defined for the GEODI address. Be sure that SSL is defined and that it is not expired.

  2. If SSL definitions are not done on GEODI server (done over a LoadBalancer for example), “ServerUri” must be defined in SystemSettings.json folder.

 There has been a change in classification rules. Is it necessary to re-upload the manifest file?

All classification changes made in the project where you defined and created a manifest file are automatically reflected. There is no need to re-upload.

 Can i create the manifest file with many projects and perform an Exchange upload?

  1. It can be done for testing or to do classification definitions over specific users.

  2. You can create a manifest file by creating different projects.

  3. If the manifest files will be used on the same Exchange server, you should definitely contact with our Technical Support Team. They will you about the issue.

  • No labels