Running Captiva 7 on a Closed Network

I am working with a customer who runs Captiva on a closed network (i.e., no Internet access).  I recently upgraded their environment from Captiva 6 to Captiva 7.  One of the first things I noticed was that the InputAccel Administrator now took about 7 minutes to start.  Most of the modules wouldn’t run as services because they timed out before they started, and when run as a foreground application, they too took several minutes to launch.  This was weird, and certainly not the experience I had in my VMware DEV environment.

Long story short:  the IT guys were able to capture the network traffic and discovered that the apps were trying to reach several different servers at several different IP address on the Internet.  We finally figured out that the apps were trying to verify publisher certificates.  When they finally got tired of trying, then they would run.

The remedy was to turn off:

  • check for publisher’s certificate revocation
  • check for server certificate revocation

in Internet Options : Advanced.

Curious that this wasn’t an issue in their Captiva 6 environment.  Anyway, C7 is humming along now.


About Scott
I have been implementing Documentum solutions since 1997. In 2005, I published a book about developing Documentum solutions for the Documentum Desktop Client (ISBN 0595339689). In 2010, I began this blog as a record of interesting and (hopefully) helpful bits of information related to Documentum, and as a creative outlet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: