Livelink Architectural Sizing Study

[Rheoman]

We have just implemented Livelink 9.5 were I work. We want to make it available for all users. What are the factor to consider in carrying out an architectural sizing study for users across five locations via WAN link.

 

[appnair]

Engage OpenText performance evaluation enagagement .They will have tools/enough knowledge on the usability,latencies and what not.It also will depend on how and what livelink is used for(for eg is LL mainly documents thru Gui,webdav,lapi,Is it gonna be search centric,is it gonna be workflow centric)

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[ggriffit]

I agree with AppNair, you really need to get some people who know how to do this otherwise there could be issues, so OT or one of their Partners.

The main things they need is your current state, how busy is your network, spec of machines etc. Additionally we use a Usage Profile which is a plan of how many concurrent users, what actions most users will perform etc.

These factors will give them an idea of the size of servers, throughput, what network / firewalls etc are required.

If you need more details then let us have some more details on your environment.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[Rheoman]

Thank you very much for your responses. We currently have LL application installed on a DL580 server and the databases on a different DL580. The configurations of the servers are the same ie W2k3 SP2,Dual Intel(R) Xeon MP CPU 2.83GHz, 8GB RAM. They are connected to SAN volumes totalling 300GB. Both servers are in the same location.

We have also added LL Explorer and Records Mgt module. We are using LL for documents and Records Management now and have five locations with almost 4500 employees. Most of the users are located across two locations connected via 2MB WAN LINK (Fibre).

Most users will use search a lot and may progress to use workflow. There may be as much as 1500 concurrent users when LL is made available to all users.

Pls let me know other additional information you may need to assist as much as you can.

 

[ggriffit]

I'd be tempted to look at adding another server at the front end so you have some load balancing and redundancy, and also vertically scale so you can seperate out the LL Explorer users from the web users. I'd run 5 threads to start with and use the ISAPI rather than the CGI to start with. Depending on the number of documents you have you may also need to add some Partitions on another server depending on the memory usage.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[appnair]

Also from this spec since I don't feel a lot of resource busy ness,a loadbalanced solution should be the most efficient.Try to use a hardware LB with LL.Ww LB'ng is almost a failure with LL.Also stay away from the curent fad of VM'ng on any prod servers.Also put wantsummarytimings=true in your opentext.ini file in the options section and re-start.You should be able to look at your usage based on vba and the timings.csv files burntIsapi is definitely more efficient,if on cgi you should consider the recievebeforesend=true also.Please keep a very shallow permissions structure on our taxonomy as well giving some real good thought on its purpose as well

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937