search

PILLUTLAAVINASH / google-enterprise-connector-manager

Automatically exported from code.google.com/p/google-enterprise-connector-manager
0 stars 0 forks source link

Tomcat "HTTP Status 404 - /connector-manager/" error after fresh install #146

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Follow "Google Enterprise Connector for MS
SharePoint Server 2007" and "Google Administering Connectors.
2. Install "connector-windows-1.3"
3. Visit connector-manager URL. (http://the.server:8081/connector-manager

What is the expected output? What do you see instead?
Expect to see something other than a "HTTP Status 404 -
/connector-manager/" error.

What version of the product are you using? On what operating system?
"connector-windows-1.3", JDK 1.5, Win2003, GB1001 (5.0.G24 VM1)+

Please provide any additional information below.

http://groups.google.com/group/Google-Search-Appliance-Help/browse_thread/thread
/f0b8a6c91302d235#

Original issue reported on code.google.com by csuwebse...@gmail.com on 29 Apr 2009 at 8:14

GoogleCodeExporter commented 8 years ago 
The Connector Manager Web Application does not have any content outside the 
WEB-INF
to be served.  Since there's no home page or index page it returns a 404 if you 
try
to access the root of the Web App.

If you want to test your server and Web App you should use the TestConnectivity
Servlet.  In your case you should be able to access it using:

  http://the.server:8081/connector-manager/testConnectivity

Note, the URL is case sensitive so make sure to use 'testConnectivity'.

Depending on the version of the Connector Manager, this should return an XML 
response
something like the following:

<CmResponse>
  <Info>Google Enterprise Connector Manager ...</Info>
  <StatusId>0</StatusId>
</CmResponse>

The StatusId of 0 indicates all is fine.

Original comment by mgron...@gmail.com on 1 May 2009 at 1:35

GoogleCodeExporter commented 8 years ago 
Rakesh wrote:

[An] HTTP Status 404 is returned which gives the impression that the 
connector manager has not been installed OR has problems

The connector Manager should return an informative response like the one 
displayed for /testConnectivity

In past customers have reported the above and requested to display some 
informative text to ensure that the connector service is up and running. 
Not many customers go through the entire documentation to know that there 
is a /testConnectivity feature available to test the same.

John L wrote:

I just tested a simple static index.html page in the root directory
(/webapps/connector-manager) and it is returned by this URL. The consensus
is to add a redirect to the testConnectivity servlet. We could use HTML or JSP:

<meta http-equiv="refresh" content="0;url=testConnectivity" />

<% response.sendRedirect("testConnectivity"); %>

Original comment by jl1615@gmail.com on 4 May 2009 at 5:41

GoogleCodeExporter commented 8 years ago 
Issue 149 has been merged into this issue.

Original comment by jl1615@gmail.com on 4 May 2009 at 5:42

GoogleCodeExporter commented 8 years ago 
Fixed: Submitting mgronber/fix-issue-146@1885 - Submitted r1887.

Description:

Fix for Issue 146.  Added an index.html page to each of the WAR files that
redirects to the TestConnectivity Servlet.  This way, when the Web Application
is deployed on a server the customer can navigate to the root of the Web
Application (http://<host>:<port>/connector-manager) and get some status
information about the server rather than a 404.

Tests Passed:

  - All Unit tests.
  - Tested without redirect and link on index page will navigate to the
    TestConnectivity Servlet.

ChangeLog:

A source/html/index.html
  - New Home Page for Web Application that redirects to the TestConnectivity
    Servlet.

M build.xml
  - Added property for web content location and added FileSet to each of the WAR
    targets.

Original comment by mgron...@gmail.com on 6 May 2009 at 6:44

GoogleCodeExporter commented 8 years ago

Original comment by Brett.Mi...@gmail.com on 16 May 2009 at 9:18