Newbie on Documentum

appuq

I installed DCTM on on windows 2022/sqlserver, oracle jdk 17.0.0.8 . I saw the install put three services Connection Broker,Repository service and a Java Methods Server.The java Methods server is actually calling startmethodserver.cmd which is actually a call to E:\Documentum\tomcat10.1.13\bin\startup.bat .This service is set to automatic and if it called TC I think one would see my default port of 9080 bound. However, it doesn't give me much to go on. If I go and execute the actual TC startup.bat the 9080 is bound and I can execute the three URLs like this(the console window stays in this case)

http://myserver.mydomain.net:9080/ACS/servlet/ACS http://myserver.mydomain.net:9080/DmMethods/servlet/DoMethod
http://myserver.mydomain.net:9080/DmMail/servlet/DoMail

in looking through some forums I found IPv6 is a problem so I have a directive to make it use IPV4 and I disabled IPV6 in my network adapter as well

I can use Documentum Server Manager to start the Repo, start broker, execute IDQL, IAPI, and so on. The Windows command file looks suspicious as I am seeing a unix shell script esac in a Windows command. Can one of you who knows this tell if that is ignorable?

netstat -ano|find "9080" never gives any output unless I start TC manually using the batch file…

startmethodserver.cmd listing

set JAVA_HOME=E:\Documentum\java64\JAVA_LINK

set CATALINA_HOME=E:\Documentum\tomcat10.1.13

set CATALINA_OPTS= -Xms1024m -Xmx2048m

ERROR=0

echo $"Starting Tomcat"

E:\Documentum\tomcat10.1.13\bin\startup.bat

esac

exit $ERROR

appuq

OT support said one cannot use openlogic 17 JDK and hence I put Oracle JDK 17.0.0.8 That seemed to hold

Brian Dinneen

I am confused!! What is your question?

appuq

One of the three services that it installs is an embedded Tomcat(Java Method Server), it wasn't starting because of conflicting environment variables.OT support thought it was the OpenJDK I used in lieu of Oracle JDK but as I said it was an offending environment variable. Once it was fixed it worked. I was getting confused because the batch file it used to start the service had directives that looked more appropriate in a shell script but as I said they were red herrings.

Thanks for the post-learning things as I am installing it.

Michael McCollough

@appuq

I believe I see one of your concerns. What version of Documentum are you installing?

set JAVA_HOME=E:\Documentum\java64\JAVA_LINK

set CATALINA_HOME=E:\Documentum\tomcat10.1.13

set CATALINA_OPTS= -Xms1024m -Xmx2048mERROR=0

echo $"Starting Tomcat"

E:\Documentum\tomcat10.1.13\bin\startup.bat

esac  - This does not belong and will give an error (but script will continue).

        I will see if I can find this in our OOTB scrips and if so put a task to fix that. 


exit $ERROR

appuq

When I used the downloaded file and was attempting the install based on openlogic JDK17 I got a standard error the JVM cannot be found documentum_server_23.4_windows64_sqlserver.zip

Googling around after setting the java every way I could it worked only after I put this little did I know that it would be the root of all evil. It was Windows 2022 Azure Datacenter edition.

This made the installer happy and the full install happened note this is to get to the installer.

However, as I mentioned the Java Method Server did not work from the service.OT support thought it was the Openlogic JDK so that was tried it still did not fix it so I started looking in the Tanuki wrapper and put debug etc. If you are fixing things inside the Java method server conf is a line 11 (missing the jar extension). if the wrapper is set to DEBUG it will spit that line out anyway it didn't seem to affect anything so support said to leave it as it is.

BTW if you want to look at my case

CS0379342

Michael McCollough

I have validated your finding and have reported for fixing. It is not breaking anything and most do start it as a service and would never see:

But I do thank you for noticing this and reporting it so we can improve it.