KB How to Reconfigure Microsoft Exchange Server Maximum s per minute limitation

Transcription

1 KB How to Reconfigure Microsoft Exchange Server Maximum s per minute limitation STEP BY STEP GUIDE December 6

2 CORPORATE HEADQUARTERS st Place NE Redmond Washington USA PH +1 (425) FAX +1 (425) EMEA HEADQUARTERS 26 Worple Road Wimbledon London UK PH (0) FAX (0) APAC HEADQUARTERS 9 Shenton Way #06-02 Singapore PH FAX [ ] The information provided relates to pre-release software products, may include features only available after installation of additional add-ins, and may be substantially modified before the commercial release. This information is provided for informational purposes only, and SourceCode Technology Holdings, Inc. makes no warranties, expressed or implied, with respect to this document or the information contained within it SourceCode Technology Holdings, Inc. All rights reserved. SourceCode software products are protected by one or more U.S. patents. Other patents pending. SourceCode, K2, K2 blackpearl and K2 blackpoint are registered trademarks or trademarks of SourceCode Technology Holdings, Inc. in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. PAGE 2

3 CONTENTS CONTENTS...3 INTRODUCTION...4 How To...4 PERFORMANCE ENHANCEMENT...7 PAGE 3

4 INTRODUCTION Introduction K2 SmartActions, which utilizes as a means of notifying the end user of a worklist item may encounter a limitation owing to the number of s that the Microsoft Exchange server will permit the K2 Server to send per minute. This limitation may not be encountered as much under previous circumstances as not all process instances would have relied on . The differentiator for K2 SmartActions is that is one of the primary means of user notification with the potential for multiple s being sent per process instance per default activity. The information below will enable a System Administrator to reconfigure the Microsoft Exchange server to permit a higher volume of messaging to be permitted by the K2 Server Service Account. The following error message may have been encountered in the error logs: Message submission rate for this client has exceeded the configured limit. This configuration will effectively disable the limitation for each machine hosting K2 Server; which is by default limited to 30 message submissions per minute. HOW TO The following steps will enable the user to reconfigure the Microsoft Exchange Server 1. Open the Exchange Management Console 2. Expand the nodes for Microsoft Exchange On-Premises > Server Configuration > Hub Transport 3. Click New Receive Connector for the K2 Server or K2 Server Cluster PAGE 4

5 4. Enter a Name for example K2 Server and set the Select the intended use for this Receive connector to Custom : 5. Click Next. 6. Clear the list. 7. Add IP addresses for the machine on ports 25 and 587. The simplest configuration is to use All IP addresses this can be specified using the radio box for IPv4 and by using the IP address : for IPv6. a. Click specify an IP address b. Enter the IP address and port and then click Ok. PAGE 5

6 8. The final result is shown below with the included IP addresses 9. Set the FQDN. 10. Click Next. 11. Clear the list. 12. Click Add > IP and Mask to add addresses for any K2 Servers, using the subnet mask : PAGE 6

7 a. Populate the IP Address of the K2 Server as shown below Complete the wizard. 13. Open the Exchange Management Shell (PowerShell) and type in the following command: Set-ReceiveConnector "<MachineName>\K2 Servers" -Messageratelimit // For example: Set-ReceiveConnector "DLX\K2 Servers" -Messageratelimit RELIABILITY ENHANCEMENT Introducing this configuration change can result in a reliability enhancement between the K2 Server and the Microsoft Exchange server. The end result being that Exchange will not rate limit K2 Server; and thus will not reject messages. It would also imply that for situations where more than 30 end user notifications are sent per Worklist Items, all recipients would receive their work list item notification s instead of only the first 30. PAGE 7