• Created by Unknown User (jguo13@gmail.com) on Aug 29, 2015

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

Compare with Current View Page History

Version 1 Next »

  • 1 .NET
  • 2 Microsoft Visual Studio Express 2012
  • 3 Configuration Settings
  • 4 Set “ClearCategories” to false
  • 5 Basic Installation Steps
  • 6 Detailed Installation Steps (Optional, use when needed)
  • 7 Agent Logs:
  • 8 Troubleshooting
    • 8.1 Issue of digitally signing
    • 8.2 Issue of access denied
  • 9 Agent Logs
  • 10 Agent Functioning
  • 11 Message Deliver
  • 12 Exchange Logs/tools

 

The Microsoft Exchange Email Server Plugin can be configured to automatically save the organization's incoming and outgoing emails to Patricia.  This will occur where a valid case reference is found in the subject line, and/or within the first 4 lines of the email content.  Once a valid case reference has been located the email is automatically saved to Patricia.   For emails being received directly into an inbox within the organization, a color-coded category can be set and automatically applied to all emails that have been saved to Patricia.  An example is provided in the screen shot below:

 

 

 

A ‘Do Not Save’ string can be set allowing email authors to selectively disable the save functionality, if for any reason it is not desirable for a given email to be saved to a case.  The string is specified in table PAT_DMS_SETTINGS, the relevant key is auto.save.skip.subject.key.

 

Software on Development Machine

.NET

 

Microsoft Visual Studio Express 2012

Download Microsoft Visual Studio Express 2012 from http://www.microsoft.com/en-us/download/details.aspx?id=34673 (select file "wdexpress_full.exe" to download)


The source code can be downloaded here: https://dl.dropboxusercontent.com/u/13110611/nuxeo/pi-nuxeo-exchange.zip


When open the source code with Visual Studio, we need to:

1) Change the .Net framework according to the Exchange server version.

2) Change log4net reference.

3) Copy the two Exchange DLL files from the Exchange server to the development machine: Microsoft.Exchange.Data.Common.dll and Microsoft.Exchange.Data.Transport.dll

4) Change the two exchange data API related references for these two DLLs.

5) Change to "Release" from the dropdown list in toolbar.

and then we can rebuild the solution and get files we need from the release folder.

Software on Exchange Server

 

When using PowerShell or Exchange Management Shell, please always run it as administrator. Otherwise, there will be permission issues.

 

Configuration Settings

 

NameDescriptionDefault Value
CategoryValueValue that the category header should be set to.Default value is “Saved”
CreateEML

Indicates whether an EML file has to be written out.

The file will be saved in the same location as the dll.

Default value is false.
IncludeCaseRefsInHeaderIf this property is true, case references will be included in header, and in Outlook user may see multiple tags of case references in addition to the tag "Saved". If it is set to false, then only "Saved" tag will be shown in user's Outlook.Default value is true.
SavedDateHeaderNameThe header that is stamped to indicate the date it was processed.Default value is “X-Pi-Saved-Date”
SavedListHeaderNameThe header that is stamped to indicate the case reference list it was saved.Default value is “X-Pi-Saved-List”
ServiceAddressREST service address where the mime data is sent.No default value. Mandatory field and the value has to be specified.
SubjectPrefixPrefix that the subject has to be prefixed with.Default is null, meaning it is not prefixed with anything.
WebProxyAddressProxy address. Can be used for debugging with fiddler.Default is null meaning no proxy used.

Set “ClearCategories” to false

Keywords (also known as Categories) are stripped from the message by default.  This can be disabled using the  "Set-TransportConfig –ClearCategories $false" cmdlet.

Execute the following command in Exchange Management Shell:

Set-TransportConfig –ClearCategories $false

Otherwise, the category will not be shown in Outlook.

 

Basic Installation Steps

  1. Get the latest source code and re-compile again the correct version of Exchange Servers dlls and .NET framework. Example files can be downloaded from here: ex2010-release-20140606.zip (for Exchange Server 2010) or ex2013-release-20140605.zip (for Exchange Server 2013)
  2. Create a folder to store the plugin DLL and XML files on the hub server. Eg: C:\TransportAgents (Please just use this one if possible)
  3. Set config files.  Set username/password in MailAgent.cs.  Make sure this user has unrestricted access rights to the Patricia documents drive.
  4. Unpack it to: C:\ex2010-release-20140605\
  5. Copy all DLL and XML files extracted to to the newly created folder, including:
    1. log4net.dll
    2. log4net.xml
    3. PI.PiNuxeoAgent.dll
    4. PiNuxeoAgentConfig.xml
  6. Run a new 'Exchange Management Shell' as Administrator (close all opened 'Exchange Management Shell' windows)
  7. Change the current directory to C:\ex2010-release-20140605\
  8. Run command: .\InstallAgentExch2010.ps1

 

Detailed Installation Steps (Optional, use when needed)

Installation of the Transport Agent involves the following:

Please note that the installation script AgentInstall.ps1 does all the steps from step 3 onwards.

  1. Create a folder for the dll on the hub server. Eg: C:\TransportAgents.
  2. Copy all files from the release location to the newly created folder.
  3. Give NetworkService full permissions to this folder.

 In the screen shot below the permissions are given to c:\TransportAgents.


  • No labels