AnsweredAssumed Answered

Alfresco v3.4b + OpenWorkDesk

Question asked by unknown-user on Dec 9, 2010
Latest reply on Dec 19, 2010 by unknown-user

i am Manuel Mueller from the WeWebU-Project-Team at HS-Coburg. This is the issue i told Mr. Pausch and Mr. Michel about.

I set up the latest Alfresco v3.4b on a german Windows XP SP3 in VMWare Workstation 7.
CPU: Intel Core2Duo 3Ghz
RAM: 1024MB
I followed the steps in the Quick-Start-Guide -> "OWDCE_QSG_B_EN_300.pdf"

Installed OpenWorkDesk-Community-Edition (OWD_3.1.0.0Sprint_2_Community_Edition_bin) into "C:Alfrescotomcatwebappsow"
The error i get when trying to log into OpenWorkDesk is:

Fehler: Keine Verbindung zu den Web-Services möglich
Fehlerquelle: OECM
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(
   at java.lang.reflect.Method.invoke(
   at com.wewebu.ow.server.ui.OwAppContext.handleRequest(
   at com.wewebu.ow.server.ui.OwWebApplication.handleRequest(
   at org.apache.jsp.default20_jsp._jspService(
   at org.apache.jasper.runtime.HttpJspBase.service(
   at javax.servlet.http.HttpServlet.service(
   at org.apache.jasper.servlet.JspServletWrapper.service(
   at org.apache.jasper.servlet.JspServlet.serviceJspFile(
   at org.apache.jasper.servlet.JspServlet.service(
   at javax.servlet.http.HttpServlet.service(
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(
   at org.apache.catalina.core.StandardWrapperValve.invoke(
   at org.apache.catalina.core.StandardContextValve.invoke(
   at org.apache.catalina.core.StandardHostValve.invoke(
   at org.apache.catalina.valves.ErrorReportValve.invoke(
   at org.apache.catalina.core.StandardEngineValve.invoke(
   at org.apache.catalina.connector.CoyoteAdapter.service(
   at org.apache.coyote.http11.Http11AprProcessor.process(
   at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(
Caused by: com.wewebu.ow.server.exceptions.OwServerException: Keine Verbindung zu den Web-Services möglich
   at com.wewebu.ow.server.ecmimpl.cmis.OwCMISNetwork.loginDefault(
   at com.wewebu.ow.server.ecmimpl.cmis.ui.OwCMISLoginSubModul.onLogin(
   … 26 more
Caused by: Unsupported Content-Type: text/html;charset=UTF-8 Supported ones are: [text/xml]
   at $Proxy262.getRepositories(Unknown Source)
   at com.wewebu.ow.server.ecmimpl.cmis.OwCMISNetwork.loginDefault(
   … 27 more

This is my owbootstrap.xml from "C:AlfrescotomcatwebappsowWEB-INFconfcmis"

<?xml version="1.0" encoding="UTF-8"?>
WeWebU OpenWorkdesk
WeWebU Software AG, Herzogenaurach/Germany
Copyright © 2005-2010. All rights reserved.
For licensing read the license.txt file or go to:

<!– ============================================================
   Please read the documentation carefully if you want to use this feature.
   All scalar tags directly beneath the <bootstrap> tag
   support mandator configuration placeholder's, i.e.: {$<Placeholdername>}.
   Most scalar tags directly beneath the <EcmAdapter>,<FieldManager>,<RoleManager> and <HistoryManager> tag
   support mandator configuration placeholder's, i.e.: {$<Placeholdername>}.
   The following attributes support mandator configuration placeholder's, i.e.: {$<Placeholdername>}
   Tags with attribute "optionid" support selective configuration.

   optionid           An option ID attribute if you define several options for a single configuration node.
                The ID is selected in the rolemanager via selective configuration.
                  Leave empty if you do not have options.
=========================================================================== –>

<!– ==========================================================================

        Content Management Interoperability Services (CMIS)


        Additional Libraries:


                following libraries are needed:
                - cmis.jar
                - webservices-api.jar
                - webservices-extra-api.jar
                - webservices-extra.jar
                - webservices-rt.jar
                - log4j-1.2.8.jar (or higher)


        Initial folders in the default objectstore:

                In order to operate correctly, the default objectstore needs to be
                initialized with some folders, where the adapter can store vital
                The folder structure should have the following structure:

                        /owpreferences             (all users must have write access for this folder)
                        /owbpmviewtemplates        (BPM only - is not supported right now)


        Application Objects

                Application Objects like Searchtemplates / virtual folders. have the following default storage locations.

                        /other                    history searches, virtual folders
                        /owsearchtemplates        search templates for search plugin, defined with <SearchTemplates>
                        /recordtemplates          record templates
                        /owbpmviewtemplates       cross view search templates for BPM - is not supported right now)




                        Specifies a list of folder class names in order to create a subfolder
                        structure on record instantiations. When created, record folder classes
                        automatically copy a predefined directory structure from:


                        Default: Configure the folder class names of all your physical records here.



                        Specifies a list of folder class names to be used as semi virtual

                        virtualfolder         = the searchtemplate of the virtual folder structure
                                                for folders at level 2 and deeper
                        folderclassname       = the name of the folder class to be used as semi
                                                virtual folder
                        includephysicalchilds = "true" or "false". Determines if existing physical
                                                folders are also supposed to appear in the directory
                                                structure at level 2 and deeper


                                Defines a virtual folder property (search criteria) for mapping the
                                value of a corresponding physical folder property.

                                folderproperty    = is the symbolic name of the property of the physical


                    List of initial values for Properties per object class overriding the P8 default values.
                    You have to create an ObjectClass tag for each object class you wish to override the default
                    P8 behavior for.

                    <ObjectClass name="….">

                        Defines the initial property values for one object class identified by its symbolic name.
                        You have to define a Property tag for each property you wish to define the initial value.

                        <Property name="…">value</Property>

                            Defines the initial value for one property identified by its symbolic name of that
                            object class.
                            NOTE FOR DATE VALUES:
                            You have to define date values always as yyyy-MM-dd'T'HH:mm:ssZ, e.g. 2007-06-06T15:47:00+02:00
                            or as yyyy-MM-dd'T'HH:mm:ss.S'Z'Z, e.g. 2007-06-06T15:47:00.799+02:00.
                            The keyword "{today}" (without quotes) can be used for the current Date / Time.


                      List of name properties per object class overriding the P8 default name properties (DocumentTitle for document classes,
                      FolderName for folder classes).
                    You have to create an ObjectClass tag for each object class you wish to override the default
                    behavior for. Only one name property is allowed per object class.

                    <ObjectClass name="….">

                        Defines the name property for one object class identified by its symbolic name.

                            property name of the name property identified by its symbolic name.


            Override filenet's classification of system / user properties and define for each property
            whether it should be treated as system or as user property

            <Property type="system|user">….</Property>

                Defines that the property identified by its symbolic name should be trasted as "system"
                or as "user" property.


                        Override FileNet authentication, use LDAP directly instead.
                                mode="NONE" : ignore, use FileNet API to authenticate
                                mode="LDAP" : use LDAP directly to authenticate


                                Define a external cross adapter for federation.
                                Insert the contents of the external <EcmAdapter> node here.

                                This setting is only available with the OwFNCMCrossNetwork adapter specified in <ClassName>.
                                OwFNCMCrossNetwork is more an example adapter for federation
                                and should be subclassed to tailor your needs.

                                See also <ExternalAttachmentProperties>.
               <XMapping>   Define mapping to use for the embedded adapter.
                  <usermappings>   Define the login mappings.
                     <usermap name="" group="">   Define a login mapping. Attribute name for a username, attribute group for a group name.
                                          If both are empty, specifies the default mapping to use.
                        <user>username</user>         The username
                        <password>password</password>   and password to use in the embedded adapter.


                  <propertymappings>   Define mapping of property symbol names.
                     <propertymap name="symbol name to map">symbolname of embedded adapter</propertymap>   Define a symbolname mapping


                                Define a list of properties in the order they should be displayed.

                                true = the object classes and related properties are cached for the whole application
                                      (default behavior even if this tag is missing)
                                false = the object classes and related properties are read for each user

=========================================================================== –>

                     <usermap name="" group="">

                     <propertymap name="cmis:document.cmis:name">ow_Filename</propertymap>
                     <propertymap name="cmis:document.cmis:creationDate">ow_Last-Modified</propertymap>
                  <Authentication mode="NONE"/>
            <!– use this adapter overload if you have defined a ExternalCrossAdapter

                <!– Enter the WSDL location for the config of your local Alfresco System –>


            <WSDLACL>…currently not supported…</WSDLACL>
            <!– Alfresco (Cloud) online CMIS WSDL location –>

            <SemiVirtualRecordClasses optionid="">
                        <SemiVirtualRecordClassName virtualfolder="virtualfolder_ratedjournal.xml" folderclassname="F:owd:journal" includephysicalchilds="true">
                            <VirtualFolderProperty folderproperty="OW_ObjectPath">OwSearchPath</VirtualFolderProperty>
                        <SemiVirtualRecordClassName virtualfolder="virtualfolder_publisherjournal.xml" folderclassname="F:owd:publisherJournal" includephysicalchilds="false">
                            <VirtualFolderProperty folderproperty="F:owd:publisherJournal.owd:publisher">D:owd:article.owd:author</VirtualFolderProperty>
            <!– Application object location e.g.
               WEB-INF/cmis_hr (default: WEB-INF/cmis or empty)
                <PreferedPropertyOrder optionid="">

                <CreationInitialValues optionid="">
                    <!– ObjectClass name="TestDocument1">
                        <Property name="TEST_STRING">hello, world!</Property>
                        <Property name="TEST_DATE">{today}</Property>
                    </ObjectClass –>
                <NameProperties optionid="">
                    <!– ObjectClass name="TestDocument1">
                    </ObjectClass –>

                <PreferredPropertyType optionid="">
                    <!– Property type="system">MimeType</Property –>

              <Authentication mode="NONE"/>
              <Authentication mode="LDAP" recursionlevel="0">
                  < ! - -
                  - - >






               Day index at which the week should begin, 0-based (defaults to 0, which is Sunday)
               for DatePicker selection.

                <FieldControls optionid="">

                        <FieldControl fieldclass="com.wewebu.ow.server.fieldctrlimpl.OwFieldManagerControlModifiedProperties" javatype="com.wewebu.ow.server.history.OwHistoryModifiedPropertyValue">

                        - allowNullValue - for "true" an empty entry (corresponding to a null value) is displayed in the drop down list when this field is rendered. 
                        <FieldControl fieldclass="com.wewebu.ow.server.fieldctrlimpl.OwLastDaysDateControl" javatype="com.wewebu.ow.server.fieldctrlimpl.OwLastDaysDate" allowNullValue="true">

                        <FieldControl fieldclass="com.wewebu.ow.server.fieldctrlimpl.OwNextDaysDateControl" javatype="com.wewebu.ow.server.fieldctrlimpl.OwNextDaysDate">

                        <FieldControl fieldclass="com.wewebu.ow.server.fieldctrlimpl.OwFieldManagerControlObject" javatype="com.wewebu.ow.server.ecm.OwObject">

                        <FieldControl fieldclass="com.wewebu.ow.server.fieldctrlimpl.OwFieldManagerControlClass" javatype="com.wewebu.ow.server.ecm.OwClass">
                        <!– <FieldControl fieldclass="com.wewebu.ow.server.fieldctrlimpl.OwFieldManagerControlNote" objecttype="F:owd:dossier.owd:dossierComment" >
                  </FieldControl> –>

                  <!– <FieldControl fieldclass="com.wewebu.ow.server.fieldctrlimpl.OwFieldManagerControlImage" objecttype="F:owd:dossier.owd:dossierPicture" >
                  </FieldControl> –>



<!– ==========================================================================



         <Event eventtype="HISTORY_EVENT_TYPE_PLUGIN_INVOKE_VIEW" eventid="*"/>
         <Event eventtype="HISTORY_EVENT_TYPE_PLUGIN_INVOKE_EDIT" eventid="*"/>


<!– ==========================================================================

   (Allows everything for all users)

         List of users that act as site administrators and can edit sitesettings.         
         Name of the design that should always be used.
         Leave empty to switch design by the role or the jsppage
         (e.g. http…/ow/<designname>.jsp opens the <designname> design).
=========================================================================== –>






<!– ==========================================================================

=========================================================================== –>



<!– ==========================================================================


=========================================================================== –>

   <!– Use the JavaScript Data Control rather than HTML comboboxes for date selection. –>

<!– ==========================================================================
    The name of the datasource to be used as a default for components that need
    a table space.
    DBMS currently supported are:
                Access (just for testing db history manager)
=========================================================================== –>

   <!– DefaultDataSource>
   </DefaultDataSource –>

   <!– DefaultDataSource>
   </DefaultDataSource –>
   <!– DefaultDataSource>
   </DefaultDataSource –>
   <!– DefaultDataSource>
   </DefaultDataSource –>         

   <!– DefaultDataSource>
   </DefaultDataSource –>

<!– ==========================================================================
   Classname of a the default folder, used to create simple folders.
=========================================================================== –>

<!– ==========================================================================
   Client wildcard definitions
   Each entry represents a wildcard that can be used in the client application
   and will automatically translate to the native wildcard in the repository.
      <wc>      Wildcardentry with wildcard character
      type      The wildcard type as defined in OwWildCardDefinition.WILD_CARD_TYPE_…
               can be the fieldname or a number
=========================================================================== –>
   <ClientWildCardDefinitions optionid="">
      <wc type="WILD_CARD_TYPE_MULTI_CHAR">*</wc>
      <wc type="WILD_CARD_TYPE_SINGLE_CHAR">?</wc>

<!– ==========================================================================
   List of classnames, which act as records:
    Specifys a list of folder class names in order to resolve the containment
   relationship between documents and records (visible in document properties
   -> files tab).
   Default: Configure the folder class names of all your physical and semi-
   virtual records here.
=========================================================================== –>
   <RecordClasses optionid="">

<!– ==========================================================================
   HTTP settings
=========================================================================== –>
   <!– SSL Mode
             0 : none
             1 : ssl session enforced –>


<!– ==========================================================================
    The temp directory (e.g. used for document upload). Define a path absolute or relative
    to the deployment, but be sure the path is assigned to a folder with read/write right.
    If the tempDir location, but not exist we will try to create and use it.
    sample definition absolute:
      Win:  <TempDir>C:/Temp/</TempDir>
      Unix: <TempDir>/usr/tmp</TempDir>
    sample defintion relative to deployment:
    If no temporary directory is defined, we use the environment information/properties (
    to get the location of server or OS temp dir. If this variable is also empty the
    deployment location is used as temporary directory.       
=========================================================================== –>

<!– ==========================================================================
    Exception handling behavior
    true = display messagebox when user causes an error, false = show default exception
=========================================================================== –>

<!– ==========================================================================
   Local language settings
=========================================================================== –>
   <!– The default language
      detectbrowserlocale      Detect the language of the users browser, default = true.
         true = override defaultlocal
         false = use defaultlocal    
   <defaultlocal detectbrowserlocale="true">en</defaultlocal>

    <!– The available language which the user can select from (must be installed with resource bundle) –>
    <availablelocals display='true'>
      <!– for German also de_au.gif (Austria) or de_ch.gif (Swiss) flag available –>
      <lang icon="/images/lang/de.gif" displayname="Deutsch">de</lang>
      <!– for English also en_gb.gif (British) flag available  –>
      <lang icon="/images/lang/en.gif" displayname="English">en</lang>
      <lang icon="/images/lang/ro.gif" displayname="Română">ro</lang>
      <!– <lang icon="/images/lang/debugmode.gif" displayname="Debug Mode (for developers only)">debugmode</lang> –>

<!– ==========================================================================
    URL parameter codec configuration. The URL parameter codec is used
    to shorten OWD URLs by encoding URL parameter into a shorter parameter set
    that relies on internally stored cookies.
        Configures the amount of time an encoded URL parameter map is valid.
        After that the parameter map is considered expired and links that rely
        on are considered out of date / expired and will not produce the desired response.
        Attributes :
            days    = days until the parameter map expires considering the URL parameter map encoding time 
            hours   = hours until the parameter map expires considering the URL parameter map encoding time
            minutes = minutes until the parameter map expires considering the URL parameter map encoding time                              
            seconds = seconds until the parameter map expires considering the URL parameter map encoding time
        The encoded parameter maps will expire after 2 days and 12 hours from the moment they are created :
        <URLLifeTime days="2" hours="12"/>
        Configures the attribute bag storage name for the parameters maps.
        In order to prevent name conflicts in attribute bags usage unique bag names prefixes should
        be specified here.
        Attributes :
            codecprefix     = a string prefix to be used in codec internal bag names
            cookieprefix    = a string prefix to be used in codec internal bag names that will store
                                cookie based parameter maps
            user            = user to be used when storing codec attribute bags
        Example :
        <AttributeBags codecprefix="c_cod_bag_" cookieprefix="c_cc_"  user="OW_GLOBAL"/>
        The parameter map codec encodes a parameter map into another parameter map containing
        one cookie defining parameter. 
        Attributes :
            name = string name of the URL parameter
        Example :
        <URLParameter name="cp"/>
=========================================================================== –>
        <URLLifeTime days="1825"/>
        <AttributeBags codecprefix="pc_master_bag_" cookieprefix="pc_c_"  user="OW_GLOBAL"/>
        <URLParameter name="cp"/>

<!– ======================================================================
   Class name for combobox renderer component.
   Available class names:    - ExtJS based combobox renderer.    - Classic HTML combobox renderer.
=========================================================================== –>       

I tested the <WSDLxxxx>-Urls in a browser and they seem to work. So i am not sure where my mistake occurs or if it is a bug.

Another problem is that after the installation of Alfresco with all services the System becomes unbelievable slow. Tomcat eats up at least 40% of CPU and 400-500MB of RAM without any user-interaction.

I will now reset the virtual machine and try Alfresco v3.4a as a base since it seems it has been tested successfully according to ->

If that wont work i will try Alfresco v3.3 as a base.

Manuel Mueller

seems there is no download anymore for v3.4a, at least i did not find it at
since the downloadlinks there refer always to v3.4b

so luckily i found at least v3.3g after some searching there ->