Management Console

Hello,

My Management Console is not working correctly. I have done a new installation (version 11.7.3.2), and everything appears to be correct (varified by a Rep from SAP). I can log into Management Console and even to the Welcome page, but when I click on the “Administrator” link then I get a HTTP Status 500 error along with root cause error below.

Has anyone had any similar problems with this?

Thanks,

root cause

java.lang.NoClassDefFoundError: com.acta.repo.ALRepoObject
com.acta.webapp.admin.report.AwHomePage.getAdapterJobServers(Unknown Source)
com.acta.webapp.admin.report.AwHomePage.initReport(Unknown Source)
com.acta.webapp.admin.report.AwHomePage.drawView(Unknown Source)
com.acta.webapp.mdreport.common.DIView.PrintReport(Unknown Source)
com.acta.webapp.mdreport.common.DIViewController.PrintReport(Unknown Source)
com.acta.webapp.mdreport.reportframework.JCActaGenericSection.PrintReport(Unknown Source)
com.acta.webapp.mdreport.common.DIFrame.PrintReport(Unknown Source)
com.acta.webapp.mdreport.common.DIMainFrame.PrintReport(Unknown Source)
com.acta.webapp.mdreport.common.DIBaseReport.PrintMainFrame(Unknown Source)
com.acta.webapp.mdreport.common.DIBaseReport.PrintReportImpl(Unknown Source)
com.acta.webapp.mdreport.common.DIBaseReport.PrintReport(Unknown Source)
com.acta.webapp.admin.servlet.AwHomeServlet.doPostSafe(Unknown Source)
com.acta.webapp.mdreport.reportframework.JSActaHttpServlet.doPost(Unknown Source)
com.acta.webapp.mdreport.reportframework.JSActaHttpServlet.doGet(Unknown Source)
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
com.acta.webapp.mdreport.servlet.JSFilter.doFilter(Unknown Source)


Nodak7 :norway: (BOB member since 2007-01-02)

what is the OS on which DI Web server is installed ?
what is the tomcat that you are using ? DI shipped tomcat or your own tomcat ?

do a search or find for the following file in the %LINK_DIR%\ext or $LINK_DIR\ext folder

ALRepoObject.class


manoj_d (BOB member since 2009-01-02)

Hey Manoj,

The OS in Linux and I am using the DI Shipped Tomcat.

Thank you for the info, I will check it out right now!


Nodak7 :norway: (BOB member since 2007-01-02)

what is the Java version that DI is using? for 11.7 release you should use JDK 1.4.2 not JDK 1.5


manoj_d (BOB member since 2009-01-02)

We had to download JDK version 1.4.2 for this install, because it had detected another version higher than 1.4.2. Do you think it is still trying to access the higher version of JDK?

Thanks


Nodak7 :norway: (BOB member since 2007-01-02)

to check what java version or java home is used by DI, do the following
cd $LINK_DIR/bin
. ./al_env.sh
echo $JAVA_HOME
check the output whether its pointing to correct java version

echo $PATH
check if $JAVA_HOME/bin that is used by DI is before any other Java

you can change the Java version used by DI by defining JAVA_HOME in al_env.sh and exporting it

if your java version is 1.4 then the problem colud be with the diAdmin.war file deployement, you ca try redploying the war file, for this
stop the DI web service (from svrcfg)
cd $LINK_DIR/ext/webserver in this there will be a folder named diAdmin and there will be file named diAdmin.war, mv the diAdmin folder to someother location or rename it, start the web server it will deploy the diAdmin again


manoj_d (BOB member since 2009-01-02)

Thank you Manoj!!! I think it is so great for helping out so much!! You are a Great Man!!!

I will give this a shot.

Thank you again!


Nodak7 :norway: (BOB member since 2007-01-02)

Manoj and anyone interested,

I did change the path for the JDK, but I was getting the same results.

It was not until I blew away the existing installation and started fresh with the correct JDK path that it finally worked.

Thank you again Manoj!


Nodak7 :norway: (BOB member since 2007-01-02)