Configuration has yet to be fully verified, Kemp Support will gladly assist if your iManage traffic is not flowing as expected.
1 Introduction
iManage by Corporate Business Solutions is a full-featured HR solution that was designed to improve the organization of a Human Resources department.
1.1 Document Purpose
This section details a configuration for a specific application that has been provided by a customer but has yet to be fully tested.
This specific configuration will ensure that your iManage servers are highly-available, scalable, and secure.
Configuration has yet to be fully verified, Kemp Support will gladly assist if your iManage traffic is not flowing as expected.
2. Configuration Required
1 Virtual Services Required which is going to be a Wildcard Port.
2.1 Global Configuration
No Changes Required.
3 Virtual Service Configuration:
3.1 iManage
> New Virtual Service
> Enter IP Address
> Port = *
> Name = iManage
> Add New Virtual Service
3.2 Standard Options
> Disable L7
> Persistence = Source IP
> Timeout = 1 Hour
> Scheduling Method = Lease Connection
3.3 Real Servers
> Checker Parameter Type = ICMP
> Enter Real Server IP Address
> Port = *
> Forwarding Method = NAT
If you have successfully Load Balanced your iManage environment by implementing this specific configuration, please give a thumbs up or please leave a comment on a possible alteration that was required to make it function. Thank you
purchasing
after several days with no good results ran across this and it worked! thank you Darren!
we have a VLM2000 so my settings above were a little different but not much. I thought just doing a simple http/https virtual service and the normal persistent option would work out of the box for iManage, but not at all. I ended up doing the wildcard for my port and removed all the other extra ports and took off transparency and there you go, connected. Much appreciated!
Alfred