cancel
Showing results for 
Search instead for 
Did you mean: 

Getting Started

ollit
Champ in-the-making
Champ in-the-making
Hello,

i ahve installed Alfresco 3.4.a on my local machine. Download source was http://wiki.alfresco.com/wiki/Download_Community_Edition.

Installation went fine with all components and i soon could bet it to work. So i followed the getting started for the Web Quick Start and importet the example files and folders.

If i want to look at the webpage (http://localhost:8080/wcmqs/) i get a page with nothing in it. Looking in the files all index files are empty. There is no navigation implemented. I get the impression that the example filkes are incomplete.

regards Olli
38 REPLIES 38

utmichael
Champ in-the-making
Champ in-the-making
It's running on 8080. On the last install I did I selected the Easy install and the only change I made was to install to the 😧 drive instead on the C: drive. I took all the default ports and left the ip adrress for Tomcat 127.0.0.1, that way I could setup the WQS and hit the site with the complete default setup and it didn't work.

Thanks for your quick response!

Default locale: Active code page: 437 US ASCII

bremmington
Champ on-the-rise
Champ on-the-rise
OK. I was concerned that there may have been an issue with certain locales (fixed on the current code line), but I know that many people in the US have Web Quick Start running fine.

I'm not sure how technical you are, but in order for me to work out what may be happening it would be really useful if you would make a little change and let me know the result.
  1. Stop Alfresco

  2. Below your Tomcat folder you will see a file located at "webapps/wcmqs/WEB-INF/classes/log4j.xml". Open this file in a text editor, and completely replace its content with this:

  3. <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE log4j:configuration PUBLIC "-//LOGGER" "../dtd/log4j.dtd">
    <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
       <appender name="console" class="org.apache.log4j.ConsoleAppender">
          <param name="Target" value="System.out" />
          <layout class="org.apache.log4j.PatternLayout">
             <param name="ConversionPattern" value="%-5p: %c - %m%n" />
          </layout>
       </appender>
       <appender name="file" class="org.apache.log4j.DailyRollingFileAppender">
          <param name="File" value="webquickstart.log" />
          <param name="Append" value="true" />
          <param name="Encoding" value="UTF-8" />
          <param name="DatePattern" value="'.'yyyy-MM-dd" />
          <layout class="org.apache.log4j.PatternLayout">
             <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c] %m%n" />
          </layout>
       </appender>
       <logger name="org.alfresco.wcm">
          <level value="debug" />
       </logger>
       <root>
          <priority value="warn" />
          <appender-ref ref="console" />
          <appender-ref ref="file" />
       </root>
    </log4j:configuration>

  4. Start Alfresco

  5. From your browser, make a single request for "http://localhost:8080/wcmqs/". Note that it is important that you use "localhost" and not "127.0.0.1".

  6. In your Tomcat folder you should see a new file located at "bin/webquickstart.log". Please copy the content of that file into a reply on this forum thread
As I say, I'm not sure whether you are technical or not, so please come back to me if any of that makes no sense.

Regards

utmichael
Champ in-the-making
Champ in-the-making
I'm the sys admin for our group, so I do understand some technical speak. Here's what I'm seeing.

I updated the log4j file and it's not writing any logs. It's also not giving any error messages in the stdout log when restarting tomcat.

The only thing I see in the logs is when I hit the http://localhost:8080/wcmqs/ is this debug message in the stdout log:

DEBUG: org.alfresco.wcm.client.exceptionresolver.RepositoryExceptionResolver - Resolving exception from handler [org.alfresco.wcm.client.controller.GenericTemplateAssetController@15ac99]: org.alfresco.wcm.client.exception.RepositoryUnavailableException
DEBUG: org.alfresco.wcm.client.exceptionresolver.RepositoryExceptionResolver - Resolving to default view '500page' for exception of type [org.alfresco.wcm.client.exception.RepositoryUnavailableException]
DEBUG: org.alfresco.wcm.client.exceptionresolver.RepositoryExceptionResolver - Exposing Exception as model attribute 'exception'

bremmington
Champ on-the-rise
Champ on-the-rise
Thanks. Strange about the log file - it must be there somewhere - but that snippet that you entered gives some clues.

That error indicates that the Quick Start web application can't connect to the Alfresco repository, and, assuming that you used the standard installer and don't have any other Alfresco instances running on the same machine, this may mean that some kind of error occurred when bringing the repository up. Can you login to Share successfully (http://localhost:8080/share/)?

calamarz
Champ in-the-making
Champ in-the-making
Hello i've the same problem with a 3.4a Version, it's a bug https://issues.alfresco.com/jira/browse/ALF-4721?page=com.atlassian.jira.plugin.system.issuetabpanel....

I try a 3.4b (download here: http://dev.alfresco.com/downloads/nightly/dist/) on my fresh install (Ubuntu 10.04 64 bits) the problem persists

bremmington
Champ on-the-rise
Champ on-the-rise
Thanks calamarz. That particular bug was closed back on 4th October. It's possible that it's reoccurring, but we can't reproduce it here - and many people have it working successfully - so we could use some help to identify what might be different on the machines where it's failing. Would you mind telling me what locale you have set as the default on your machine?

bremmington
Champ on-the-rise
Champ on-the-rise
I've just completed a series of tests including installing both 3.4.a and 3.4.b nightly build on Ubuntu 10.04 64-bit (using English, Norwegian, and Arabic installs). They all worked without any problem, but then I thought about what assumptions I'd made when installing, and I think I know what's causing the problem.

The Web Quick Start API connects and authenticates to the Alfresco repository. It has a few properties that it uses to do this: "wcmqs.api.alfresco", "wcmqs.api.user", and "wcmqs.api.password". In 3.4.b (the nightly build) these can be overridden by placing the required values in a file named "wqsapi-custom.properties" located in the directory "tomcat/shared/classes/alfresco/extension". By default, these properties are:

wcmqs.api.alfresco=http://localhost:8080/alfresco
wcmqs.api.user=admin
wcmqs.api.password=admin

so they need changing if you use a port different to 8080 and an admin password different from "admin".

In 3.4.a, the way to override these properties is a little different. In that version, create a file named "wcmqs-api.properties" in the folder "tomcat/shared/classes/alfresco". In that file, copy the following:

wcmqs.api.alfresco=http://localhost:8080/alfresco
wcmqs.api.user=admin
wcmqs.api.password=admin
wcmqs.api.alfresco.cmis=%{wcmqs.api.alfresco}/service/cmis
wcmqs.api.alfresco.webscript=%{wcmqs.api.alfresco}/service/api/

and then edit the values as necessary.

This is a fault in the way the installation works, and we'll work on correcting that over the next day or two on the 3.4.b stream. Apologies for the inconvenience that this has caused, and thanks for reporting it.

Regards

bremmington
Champ on-the-rise
Champ on-the-rise
The installer has just been fixed on HEAD, so the next nightly build will contain that fix.

Note that if you choose a port other than 8080 when installing then you will have to alter the "Host Port" property on the folder named "Quick Start Editorial" that you will find in the Document Library after importing the Web Quick Start data. This is set to 8080 by default.

In this situation, the steps needed to do that are:
  1. Install Alfresco with Web Quick Start (select the port number that you want - "8888", for example)

  2. In Share, create a new Share site

  3. Customise the dashboard of the Share site to include the Web Quick Start dashlet

  4. Use the Web Quick Start dashlet to import the Web Quick Start data

  5. Go in to the document library and navigate into the "Alfresco Quick Start" folder

  6. In the list of actions available for the "Quick Start Editorial" folder select "Edit Metadata"

  7. In the form that appears change the "Host Port" property to be 8888 and then click "Submit"

georgo
Champ in-the-making
Champ in-the-making
Hi, I'm having the same issue. I changed admin's password and want to use the user alfresco to connect with CMIS. I'm using alfresco-community-3.4.b and changed the username/password in these files:

fgrep -RH .user=alfresco *

tomcat/shared/classes/alfresco/extension/wcmqs-api.properties:wcmqs.api.user=alfresco
tomcat/shared/classes/alfresco/extension/wqsapi-custom.properties:wcmqs.api.user=alfresco
tomcat/shared/classes/alfresco/wcmqs-api.properties:wcmqs.api.user=alfresco
tomcat/webapps/wcmqs/WEB-INF/classes/alfresco/wcmqs-api.properties:wcmqs.api.user=alfresco
virtual-tomcat/conf/alfresco-virtserver.properties:alfresco.server.user=alfresco

I enabled the debug flag in log4j and get this error:


DEBUG: org.alfresco.wcm.client.exceptionresolver.RepositoryExceptionResolver - Resolving exception from handler [org.alfresco.wcm.client.controller.GenericTemplateAssetController@1006ab6]: org.alfresco.wcm.client.exception.RepositoryUnavailableException: org.apache.chemistry.opencmis.commons.exceptions.CmisConnectionException: Parsing exception!
DEBUG: org.alfresco.wcm.client.exceptionresolver.RepositoryExceptionResolver - Resolving to default view '500page' for exception of type [org.alfresco.wcm.client.exception.RepositoryUnavailableException]
DEBUG: org.alfresco.wcm.client.exceptionresolver.RepositoryExceptionResolver - Exposing Exception as model attribute 'exception'

Am I missing a property file?

thanks in advance,
Jorge

bremmington
Champ on-the-rise
Champ on-the-rise
Jorge

Presumably you have created the "alfresco" user in the repository and have specified the correct password for that user in the WQS properties file? What permissions have you given that user?