Uploaded image for project: 'Jahia Community'
  1. Jahia Community
  2. JAHIA-3594

Installation Process: no redirect any more in the browser. You need to check the JahiaInstallationREADME file at root of your install to know the url to access to the config wizard. Not trivial for a secretary.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • xCM 6.0
    • xCM 6.0.0
    • None
    • 22771

    Description

      There is no automated redirection and intialzsation of a new browser instance when launching Jahia the first time. The user needs to know (or to find in some readme file) the url to access to the config wizard. The process was more simple based on Jahia 5.0.

      Please reuse the same batch init file than with Jahia 5.0. This clearly ease the installation process for Jahai newbies.

      Moreover it would be great to also indicate clearly in the console the url to access to the wizard (or to the default Jahia page: warning the context should be correct if the end-user change the default context) in case the browser does not automatically open (for whatever reason). For the moment the console is not verbose enough and the end-user does not know when he can access to the url or not (sorry not everybody is a technical J2EE developer)!

      So after the line:
      INFO: Server startup in 16144 ms
      We could add some mentions of the Jahia default url. This does not cost a lot I think

      22 oct. 2008 10:06:05 org.apache.catalina.core.AprLifecycleListener init
      INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java
      Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Common Files\Sonic Shared;;C:\Program Files\UltraEdit;C:\Program Files\QuickTime\QTSystem\;C:\Program Fi
      22 oct. 2008 10:06:05 org.apache.coyote.http11.Http11Protocol init
      INFO: Initialisation de Coyote HTTP/1.1 sur http-8080
      22 oct. 2008 10:06:05 org.apache.catalina.startup.Catalina load
      INFO: Initialization processed in 1351 ms
      22 oct. 2008 10:06:05 org.apache.catalina.core.StandardService start
      INFO: D�marrage du service Catalina
      22 oct. 2008 10:06:05 org.apache.catalina.core.StandardEngine start
      INFO: Starting Servlet Engine: Apache Tomcat/6.0.18
      [GC 87424K->2080K(1034048K), 0.0216868 secs]
      log4j:WARN No appenders could be found for logger (com.sun.faces.config.ConfigureListener).
      log4j:WARN Please initialize the log4j system properly.
      [GC 89504K->4262K(1034048K), 0.0232503 secs]
      22 oct. 2008 10:06:21 org.apache.coyote.http11.Http11Protocol start
      INFO: D�marrage de Coyote HTTP/1.1 sur http-8080
      22 oct. 2008 10:06:21 org.apache.jk.common.ChannelSocket init
      INFO: JK: ajp13 listening on /0.0.0.0:8009
      22 oct. 2008 10:06:21 org.apache.jk.server.JkMain start
      INFO: Jk running ID=0 time=0/47 config=null
      22 oct. 2008 10:06:21 org.apache.catalina.startup.Catalina start
      INFO: Server startup in 16144 ms

      TestRail: Results

        Attachments

          Activity

            People

              ielsayed Islam El-Sayed (Inactive)
              scroisier Stephane Croisier (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                TestRail: Runs

                  TestRail: Cases

                    Packages

                      Version Package
                      xCM 6.0