jwgoldstein Absent Member.
Absent Member.
3824 views

New Installation issues with Service Desk

Hi,

I have just installed Service Desk 6.1 that I downloaded from Novell site on the 14th of July 2011.

I am installing it on SLES11 SP1 64bit, the machine has 2GB RAM and I have installed Java 64bit

sdesk-dev:~/apps # java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)

When I open the URL http://localhost:8700/LiveTime/WebObjects/LiveTime

I get;

HTTP Status 404 - Servlet WOServletAdaptor is not available

type Status report

message Servlet WOServletAdaptor is not available

description The requested resource (Servlet WOServletAdaptor is not available) is not available.
Apache Tomcat/6.0.29

LiveTime starts;

sdesk-dev:~/apps # service livetime start
Starting LiveTime...
Using CATALINA_BASE: /usr/local/ServiceDesk/Server
Using CATALINA_HOME: /usr/local/ServiceDesk/Server
Using CATALINA_TMPDIR: /usr/local/ServiceDesk/Server/temp
Using JRE_HOME: /usr/java/jre1.6.0_26
Using CLASSPATH: /usr/local/ServiceDesk/Server/bin/bootstrap.jar
LiveTime started successfully

I have read some forums and I do not know where to start looking for this problem.

Cheers,

Jonathan
0 Likes
4 Replies
wirtzal Absent Member.
Absent Member.

Re: New Installation issues with Service Desk

Hi Jonathan,

I don`t know exactly in which config file you must look at. I think it was the "server.conf" . There you can configure the min. and max. MB for java runtime of ServiceDesk.
Your specification for your system (with 2GB RAM) must be a little bit smaller.
e.g. java max.MB=2048 (original) -> change into 1536 or else.
You can see via netstat -ln if the port (8700) is used and if the application is running.
Best practise is to give your machine at least 3GB RAM (or 4).

Regards,
Alex
0 Likes
jwgoldstein Absent Member.
Absent Member.

Re: New Installation issues with Service Desk

Hi wirtzal,

I could not find the "server.conf" file, this is a VM, I increased the RAM to 3.5GB, re-installed JAVA from the JAVA.COM website and then re-installed ServiceDesk. I get exactly the same error message and if I do a netsat -ln | grep 8700 I get

tcp 0 0 :::8700 :::* LISTEN



wirtzal;2121699 wrote:
Hi Jonathan,

I don`t know exactly in which config file you must look at. I think it was the "server.conf" . There you can configure the min. and max. MB for java runtime of ServiceDesk.
Your specification for your system (with 2GB RAM) must be a little bit smaller.
e.g. java max.MB=2048 (original) -> change into 1536 or else.
You can see via netstat -ln if the port (8700) is used and if the application is running.
Best practise is to give your machine at least 3GB RAM (or 4).

Regards,
Alex
0 Likes
wirtzal Absent Member.
Absent Member.

Re: New Installation issues with Service Desk

sorry, my fault 😉

The java config is in the /usr/local/ServiceDesk/Server/bin/catalina.sh
There you can configure the max MB for JAVA appl.
Also you can see if the java directory is the right one.

Alex
0 Likes
jwgoldstein Absent Member.
Absent Member.

Re: New Installation issues with Service Desk

Hi,

I managed to sort the problem out, it seems that there was an issue with the FQDN of the server, sorted that out in YAST, and the JAVA error is gone now.

thanks for the assistance.

Cheers,

Jonathan

wirtzal;2122414 wrote:
sorry, my fault 😉

The java config is in the /usr/local/ServiceDesk/Server/bin/catalina.sh
There you can configure the max MB for JAVA appl.
Also you can see if the java directory is the right one.

Alex
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.