This discussion is now locked
Posted by Mr. Nicolás Gómez-Sellés on 13 July 2009 at 12:29
I need this book, even if in a draft format, but neither PDF nor HTML seems to be available on line. How can I get it quickly? Thanks.
Posted by John Montgomery on 14 July 2009 at 7:40
The draft web page is intriguing. Share the rest of the story with us.
Posted by Ted Bosal on 10 August 2009 at 8:20
Lack information about 4.5. In Content Engine v4.5 is new tool - FileNet Configuration Manager
Posted by Mr. Frik Briers on 26 February 2010 at 3:46
Is there any information available for Process Analyser in a High Availability Solution?
Posted by Tilo Soennichsen on 23 June 2010 at 11:23
could you please mention how to enter all AD DC for fail-over. CE help mention this for CE only, but how to set this up for WAS in a Federated Directory setup? And does it for FileNet only need to be in CE and WAS?
Here for CE the info:
Posted by Garry Stewart on 16 November 2010 at 9:48
If you are implementing PE farms I'd suggest that you review PMR 48771-999-649 and 49473-999-649 regarding setting the WAS parameter com.ibm.CORBA.ConnectionMultiplicity on the AE servers. Our implementation had all of the PE workload going to only one of the PE servers in the PE farm until we implemented this parameter.
Posted by Josip Bosnjak on 2 June 2011 at 11:33
PE Farm - Health Checks - Frequency and timeout of those?
- Do health checks on both ports, 32776 and 32777
- Check the answer of port 32776 to contain string "PE Server"
- Do health checks every 30 seconds, set timeout to 91 sec.
Concern: it could take too long, to take out a not responding PE. Too many work might accumulate in the meantime.
The suggestion 30/91 might be from a time, where computers were slower etc. Any experience with lower settings? Thanks.
Posted by Mr. Jochen Kerscher on 11 July 2013 at 3:26
Please be aware of this _very_ important change with IS4.1.2 FP6+ (just shortly after the Redbook was published):
Configuring Image Services 4.1.2 (FP6 and above) for HA cluster environment
Create virtual_server_name.txt file:
Contents: cluster name