Infrastructure at your Service
Last week, when I was working on how to setup the Kerberos SSO for D2 3.1 SP1, I faced some issues due to a documentation that doesn’t seem to be up to date… In fact, our version is D2 3.1 SP1 and there is no specific documentation for SP1. In consequence, I read the D2 3.1 Installation Guide and the D2 4.0 Installation Guide. The first time I read the D2 3.1 documentation, I found…
At one of my customers, I experienced a problem with the Documentum Administrator (DA), which did not display the correct Index Agent status. In this blog post, I will explain how I found the source of this problem and of course also how I solved this issue. But first, some background facts: The Documentum Administrator (DA) is displaying “not responding” for the Index Agent, however the Index Agent is running well. No solutions are mentioned…
To be compliant with the customer’s security rule, I had to configure SSL for a JBoss application server that holds the Documentum Foundation Services (DFS). I used the following procedure: 1. Generate a keystore Change it to a temporary location, e. g. /var/tmp/SSL: keytool -genkey -dname “cn=dms.test.org, ou=DEV, o=NICE, l=Delemont, s=Switzerland, c=CH” -keyalg “rsa” -validity 730 -alias tomcat -keysize 2048 -keystore dfs.keystore Enter keystore password: xxxx Enter key password for (RETURN if same as keystore…
The Documentum job dm_FTIndexAgentBoot does not start anymore and we have the following job status: The job object indicated the job was in progress. In this blog posting, I will describe how to analyze and solve this issue. Analysis The Index Agent does not start automatically when the repository is started although the option start_index_agents = T in server.ini is set. When the server is started, the dm_FTIndexAgentBoot job is normally executed, but not in…
