Derby Server and Administration Guide - Managing the Derby Network Server
remotely by using the servlet interface
-----------------------------------------------------------------------------------------------------------------
Key: DERBY-1200
URL: http://issues.apache.org/jira/browse/DERBY-1200
Project: Derby
Type: Bug
Components: Documentation
Versions: 10.1.2.3
Environment: DITA source file
Reporter: Halley Pacheco de Oliveira
Priority: Minor
Fix For: 10.1.2.3
In this part of the manual is written:
For example, if derby.war is installed in WebSphere Application Server with a
context root of cns, the URL of the server is:
http://<server>[:port]/derby/derbynet
I'm not an expert in WebSphere, but I don't thin so. With a context root of cns
the URL should be, in my opinion:
http://<server>[:port]/cns/derbynet
When I installed this war file in Tomcat I received the message:
OK - Deployed application at context path /derby
And I'm accessing the servlet using the URL:
http://localhost:8080/derby/derbynet
I think that the URL in the manual should not be changed, and the context root
should be changed to "derby", discarding "cns". The diff file that I'm sending
do this.
There is another problem: I didn't find the derby.war file in
$DERBY_INSTALL/frameworks/NetworkServer/war directory, I found it in the
directory $DERBY_INSTALL/lib/
I also would like to see this chapter improved with an example of installing
and using the servlet with Tomcat. I did this in four steps:
1) Copying the files derby.jar and derbynet.jar to $CATALINA_HOME/common/lib/
2) Including the lines:
DERBY_INSTALL=<directory>
and
-Dderby.system.home=$DERBY_INSTALL/frameworks/NetworkServer/bin
in Tomcat initialization script, to have derby.system.home in the same
directory of NetworkServerControl scripts.
3)Using "Select WAR file to upload" in Tomcat Web Application Manager to upload
$DERBY_INSTALL/lib/derby.war
4)Using the URL http://localhost:8080/derby/derbynet to access the servlet.
I think this could be a good example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira