The post is just working journal about steps I took to get the Developer Edition 6.6 up and running.
1. Downloaded the installer file from Documentum Developer Edition.
2. Extracted the zip file to a local temporary location.
3. Started the installer by running documentumSetup.exe, and then followed each window the installer showed.
4. After the installer finished the installation, a welcome page showed and listed links to DA, Webtop and Retention Policy Services Administrator.
5. Checked the system, 4 new Documentum related services were created in the system:
– Documentum Docbase Service documentum
– Documentum Docbroker Service Docbroker
– Documentum Java Method Server
– Documentum Master Service
6. The link to Webtop, DA, and Retention Policy Services Administrator worked well for the newly installed Documentum and repository.
As the newly created repository documentum was working as expected, then I tried to create a new repository with the developer edition. Here are several things I found out:
– The executable Server_Configuration_Program.exe found under C:\Documentum\product\6.6\install should be used for creating new repositories.
– The name of the Database Administrator was ‘sa’, and its password was ‘documentum-1’. The information is needed when using the bundled SQL server.
– During repository creation, the step of running headstart.ebs failed.
In its output file, it showed ‘Failed to update docbase config object’. Having checked the ebs source file, it seemed the variable FTVendorStr was still using ‘fast’ with 6.6. After I added the following line to force the Full-text indexing to use Lucene, the script went through.
FTVendorStr = "lucene"
References
Documentum Content Server Developer Edition