Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't access the webapp #9

Open
GoogleCodeExporter opened this issue Feb 22, 2016 · 6 comments
Open

Can't access the webapp #9

GoogleCodeExporter opened this issue Feb 22, 2016 · 6 comments

Comments

@GoogleCodeExporter
Copy link

I finally got the build working and then attempted to deploy the artifact 
test-analytics-1.0-SNAPSHOT.war
Tomcat deploys the war fine but I cannot access the webapp. I used the tomcat 
manager to deploy and then click on the link in the manager console which gives 
me this:

Unable to connect
      Firefox can't establish a connection to the server at localhost:8443.

Any suggestions?

Original issue reported on code.google.com by [email protected] on 3 Feb 2012 at 10:22

@GoogleCodeExporter
Copy link
Author

hi, I have the same problem. I believe that this error is due to the fact that 
test analytics webapp redirects to port 8433 by default. The webapp container 
needs to be configured properly to handle that. However, after enabling this 
port in Tomcat's 'conf/server.xml' file, I still have problems, this time 
'Access to requested resource is denied'.

It would be good to have SOME documentation how to easily install this tool... 
:/

Original comment by [email protected] on 14 Sep 2012 at 11:53

@GoogleCodeExporter
Copy link
Author

have anyone got it to work? In that case which source and instructions did you 
use?

Original comment by [email protected] on 18 Jun 2013 at 11:49

@GoogleCodeExporter
Copy link
Author

It has been a year.  Same problem.  Any solution?

Original comment by [email protected] on 21 Oct 2014 at 2:19

@GoogleCodeExporter
Copy link
Author

Sorry, new to Tomcat.  Didn't realize tomcat needs key information in addition 
to what was already defined for Apache.

Original comment by [email protected] on 21 Oct 2014 at 4:11

@GoogleCodeExporter
Copy link
Author

Hi,

I am able to deploy and fix the issue by creating a self signed certificate and 
keystore and configured it in tomcat server.xml file.

But now i am getting "HTTP Status 403 - Access to the requested resource has 
been denied". 

Please assist, whats wrong i am doing.

Original comment by [email protected] on 6 Jul 2015 at 6:55

@GoogleCodeExporter
Copy link
Author

I got this mostly working a few years ago (some features like the heatmap 
weren't working). These are the rough steps I followed, hope it helps!

        ○ Checkout the project from Google Code
            § git clone https://code.google.com/p/test-analytics/ 
        ○ Download a Java JDK
            § http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
            § Set your JAVA_HOME environment variable, e.g. C:\Program Files\Java\jdk1.7.0_21
            § Add %JAVA_HOME%\bin to the BEGINNING of your PATH variable
        ○ Download Maven and follow instructions to set up %M2% and %M2__HOME%
            § http://maven.apache.org/download.cgi
            § Make sure to add %M2% to PATH
        ○ Navigate to …\test-analytics\testanalytics_frontend and open a command window
        ○ Type "mvn package" to generate the war file/SNAPSHOT
            § It will probably fail the first time; when it does, download the following jar file and place it in this directory:
                □ https://gwt-dnd.googlecode.com/files/gwt-dnd-3.1.1.jar
                □ %HOME%\.m2\repository\com\google\code\gwt-dnd\gwt-dnd\3.1.1
        ○ Download Google App Engine SDK (I chose the one for Java)
            § https://developers.google.com/appengine/downloads#Google_App_Engine_SDK_for_Java
        ○ IF YOU WANT TO DEPLOY TO GOOGLE APP ENGINE, SKIP TO "Set up a test Google App Engine Project", OTHERWISE FOR LOCAL DO THE NEXT 3 STEPS
            § You may need to edit the appengine-web.xml files (there are two) in the generated code (test-analytics\testanalytics_frontend\target\test-analytics-1.0-SNAPSHOT) to include the following
                □ <threadsafe>true</threadsafe>
            § Navigate to appengine-java-sdk-1.8.0\bin, open a command prompt and run the command
                □ dev_appserver.cmd --address=0.0.0.0 --port=8080 war
                □ Where "war" is the path to the SNAPSHOT directory, e.g.
                    ® D:\appengine-java-sdk-1.8.0\bin>dev_appserver.cmd --address=0.0.0.0 --port=8080 D:\projects\test-analytics\testanalytics_frontend\target\test-analytics-1.0-SNAPSHOT
            § Your app should now be available on http://yourcomputername:8080/
        ○ Set up a test Google App Engine project
            § https://appengine.google.com/
        ○ Edit the appengine-web.xml files (there are two) in the generated code (test-analytics\testanalytics_frontend\target\test-analytics-1.0-SNAPSHOT) to include the following
            § <threadsafe>true</threadsafe>
            § <application>YOUR APPLICATION NAME</application>
            § <property name="com.google.testing.testify.risk.frontend.url" value="https://YOUR APPLICATION NAME.appspot.com" />
        ○ Navigate to appengine-java-sdk-1.8.0\bin, open a command prompt and run the command
            § appcfg.cmd update war
            § Where "war" is the path to the SNAPSHOT directory, e.g.
            § appcfg.cmd update D:\projects\test-analytics\testanalytics_frontend\target\test-analytics-1.0-SNAPSHOT
            § Log in with your Google email and password when prompted
                □ I had to set up an application-specific password at https://www.google.com/settings/security because I have 2-step verification (authenticator) enabled
        ○ ??
        ○ Profit! Your app should be up and hosted by Google

Original comment by [email protected] on 16 Jul 2015 at 7:48

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant