topic Re: Viability Study - WORKDESK in Alfresco Archive

Viability Study - WORKDESK

dmralfing — Fri, 08 Nov 2013 09:26:04 GMT

I have installed workdesk in my machine and I´m trying to do a demo in order to evaluate if it can cover most of the requirements for a big project. The problem is that I only have seen a document called "Alfresco_Workdesk_Configuration_Guide_4.1.1.pdf", but it´s far from complete. Can I find any ot

Re: Viability Study - WORKDESK

deko — Fri, 08 Nov 2013 12:34:07 GMT

Hi dmralfing,

Where have you found/downloaded the Workdesk Configuration guide? There should be at least also a Workdesk Installation Guide available, as well as other documents being ready to released. In general you can find related Alfresco products documentation at http://docs.alfresco.com

If you are interested in demos you can have a look at YouTube, where lots of Workdesk demo videos are available. If you are interested in an out of the box sample show case, it makes sense to download the Workdesk trial package, which connects against an online Alfresco repository and comes preconfigured with a full "Customer Management" show case and the required documents (e.g. scenario guide, etc.)

The combobox you are talking about is the Role Selector combo box being a feature of the so called DB Role manager in Workdesk. It enables the currently logged-in user to switch between his different roles and getting role dependent views of his work. Of course this combo box does not appear out of the box but the DB Role Manager (see corresponding section in Configuration Guide) must be configured for differnet user roles/groups.

When it comes to configuration help there are several places to find help, depending on which configuration file (e.g. owplugins.xml, owbootstrap.xml) you are editing. For owbootstrap.xml, where DB Role Manager is configured, you will find lot of inline documentation in addition to the official Workdesk documents. For configuring owplugins.xml, we recommend using the graphical user interface configurator, which comes with an online help displaying help pages for every plugin and every plugin configuration node.

I hope I could help you with this information and pointed you correctly to all the required locations to dive deeper into Workdesk and enjoying the Workdesk experience. Have a nice weekend!

Best regards,
Dennis

Re: Viability Study - WORKDESK

dmralfing — Fri, 08 Nov 2013 13:26:00 GMT

I already have seen demos in internet, what I want is to prove the things doing my own demo for my customer!,

I have Workdesk Trial 4.1.1.1.

I have changed it to appoint to my own local alfresco repository.
Is it the Community or Enterprise edition?
I would like to have any "out of the box sample show case", but connecting with my own Alfresco repository for a demo. Where can I get that samples?. I already knew the link you showed me http://docs.alfresco.com, but I don´t see around there more advanced documentation about workdesk.
I still have some questions:
1. I configure the owbootstrap.xml adding this:


   <RoleManager>

      <ClassName>com.wewebu.ow.server.roleimpl.dbrole.OwDBRoleManager</ClassName>
      
      <Version>4.1.1</Version>

      <DbTableName>OW_ROLE</DbTableName>

      <DesignName>default41</DesignName>
      
        <AvailableDesigns>
            <Design displayName="Alfresco Workdesk 4.1 Design">default41</Design>
        </AvailableDesigns>

        <SchemeVersion>3</SchemeVersion>
      
      <SecurityAdmin pluginid="com.wewebu.ow.Admin">
             <User>Administrator</User>
             <User>admin</User>
      </SecurityAdmin>

      <MasterRoles enable="true">
         <MasterRoleGroup name="Administrator">
            <Role>Administrator Role</Role>
         </MasterRoleGroup>
         <MasterRoleGroup name="Human Resources" memberOfAll="true">
            <Role>HR Manager</Role>
            <Role>HR User</Role>
         </MasterRoleGroup>
         <MasterRoleGroup name="Office User">
            <Role>Office User</Role>
         </MasterRoleGroup>

      </MasterRoles>
      
      <ConfigCategories>ROLE_CATEGORY_PLUGIN,
                        ROLE_CATEGORY_SEARCH_TEMPLATE,
                        ROLE_CATEGORY_STANDARD_FUNCTION
      </ConfigCategories>
      
   </RoleManager>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

…but is still doesn´t appears the user roles combo, I don´t know if I have done something wrong in the code!. Moreover, I don´t know how you can associate every user role with different set of plugins/user interface elements, it´s not well explained in Alfresco_Workdesk_Configuration_Guide_4.1.1.pdf.
When you say "inline documentation" for the owbootstrap.xml do you mean the same code I can see commented in the same file?. if not where can I get it?, And the graphical user interface for owplugins.xml?
I don´t want you to do my job, only to show me the path, I´m so lost!
Thank you very much deko

Re: Viability Study - WORKDESK

deko — Fri, 08 Nov 2013 16:20:18 GMT

Hi again,

First of all please let me note that I edited your last post and removed the hyperlink you added, as one has to register to download a Workdesk trial and to receive the download URL, so it should not be accessible by every forums user and even worse the trial is connected to your account only 🙂

1. As you have downloaded a trial of Workdesk, it is preconfigured to connect against an online Alfresco repository and against an online database persisting the DB Role Manager permissions for each user/role. You changed owbootstrap.xml now to point to your local Alfresco instance. Have you changed your data source to connect to a local DB instance also? I guess you are using Apache Tomcat for deployment, so the data source is configured under webapps/workdesk/META-INF in the context.xml file. You need to point that to a local DB instance (if installed you could use the PostgreSQL instance coming with Alfresco) and you need to run the DB scripts to create the database and the required tables (this is described in detail in the Installation guide), especially table OW_ROLE (see node DbTableName in your code snippet), which is holding DB Role Manager information.

2. Yes, when I say "inline documentation" for the owbootstrap.xml, I talk about the code you can see commented in the same file. The DB Role Manager node is described there also. Do you know and understand what you have enabled in your code snippet?

3. Where do your users/groups come from (see node authentication in owbootstrap.xml)? Workdesk does not come with any users at all, all users and groups are either pulled out of an external LDAP system or are defined in Alfresco.

4. In your snippet you have a node SecurityAdmin. You have to define an Administrator user there, who will be able then to access the "Administration" plugin (pluginid="com.wewebu.ow.Admin") in the Workdesk UI and to setup, which user/group should have access to which plugins.

5. In your code snipper you have configured the node ConfigCategories with an element ROLE_CATEGORY_PLUGIN, i.e. the security Admin then will be able to define access to all plugins for different user groups in the "Administration" plugin in Workdesk. There are more categories (see inline help), e.g. using category ROLE_CATEGORY_SEARCH_TEMPLATE enables the security admin to define which searches shall appear for which user groups in the Workdesk "Search" master plugin. If a category is not configured, the access to the category is set to DENIED by default in code of Workdesk.

6. Do you understand the concept of the Role Selector combobox? Different users might see different things in Workdesk without using the combo box at all. For example, you defined for users of group A a different set of plugins than for users of group B. So if user of group A logs in he/she will see different plugins than what user of group B sees after login. The dropdown is only useful, if there a users in different roles and they want to switch between their roles and change between different views.

7. If you want to configure the combo box, you need to configure the node MasterRoles in your snippet:



<MasterRoles enable="true">
         <MasterRoleGroup name="Administrator">
            <Role>Administrator Role</Role>
         </MasterRoleGroup>
         <MasterRoleGroup name="Human Resources" memberOfAll="true">
            <Role>HR Manager</Role>
            <Role>HR User</Role>
         </MasterRoleGroup>
         <MasterRoleGroup name="Office User">
            <Role>Office User</Role>
         </MasterRoleGroup>
 
      </MasterRoles>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

The name attribute for a MasterRoleGroup is defining the name as it appears in the combobox later. The Role node then configures user groups (from LDAP or Alfresco) that shall be mapped to this combobox selection.

If your groups are pulled out of your Alfresco instance, the default format for the role definition should be GROUP_groupname.

Examples for your code snippet:

- If a user logs in to Workdesk, who is member of group/role "Office User" and "Administrator Role" in LDAP OR Alfresco, the combobox will appear for that user, showing the entries "Administrator" and "Office User". The startup role would be the role matching first in the definition order in owbootstrap.xml, means "Administrator" but this can later be changed in the "Settings" master plugin.

- If a user logs in to Workdesk, who is not a member of any of those groups/roles defined, he won´t see a combobox at all.

There are additional examples in the Configuration and Installation guide and I want you to refer there please.

With DB Role manager, you picked one of the most powerful Workdesk features 🙂 Hope that you now know how to solve your issues.

Best regards,
Dennis

Re: Viability Study - WORKDESK

dmralfing — Mon, 11 Nov 2013 13:52:27 GMT

Ok, I have installed the scripts according to the installation guide - I´m using MySQL -. The problem is that I 'm blind because I can't see any log about workdesk. I have copied the log4j.properties from "WORKDESK/WEB-INF/conf/fncm5" to "WORKDESK\WEB-INF\classes". I have checked that I only have one log4j JAR in the WAR libs - log4j-1.2.16.jar - and I don´t have more JARS related with log4j neither in the WAR nor the tomcat.
You can see here my log4j:


# Alfresco Workdesk
# Copyright © Alfresco Software, Inc. All Rights Reserved.

# If you are not familiar with log4j please consult http://logging.apache.org/log4j/1.2/manual.html

# Set root logger level
#log4j.rootLogger=DEBUG,workdesk_console
#log4j.rootLogger=DEBUG,workdesk_console_detailed
#log4j.rootLogger=DEBUG,workdesk_file,workdesk_file_rolling
#log4j.rootLogger=DEBUG,workdesk_file_rolling

# for productive environments use:
log4j.rootLogger=ERROR,workdesk_console

# workdesk_console is set to be a ConsoleAppender
log4j.appender.workdesk_console=org.apache.log4j.ConsoleAppender
# workdesk_console uses PatternLayout
log4j.appender.workdesk_console.layout=org.apache.log4j.PatternLayout
##define pattern: Date format(iso8601) [thread] LOG-Type AWD-Module [username] - messages|separator character
log4j.appender.workdesk_console.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c [%x] - %m%n
# log4j.appender.workdesk_console.layout.ConversionPattern=%-4r [%t] %-5p %c - %m%n

# workdesk_console_detailed is set to be a ConsoleAppender
# Warning: It's use should be avoided unless execution speed is not an issue!
log4j.appender.workdesk_console_detailed=org.apache.log4j.ConsoleAppender
# workdesk_console_detailed uses PatternLayout.
log4j.appender.workdesk_console_detailed.layout=org.apache.log4j.PatternLayout
##define pattern: Date format(iso8601) [thread] LOG-Type AWD-Module [username] {fully qualified class name of the caller.method name} - messages|separator character
# optional %l=Used to output location information of the caller which generated the logging event or %L=line number 
log4j.appender.workdesk_console_detailed.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c [%x] {%C{2}.%M} - %m%n
# log4j.appender.workdesk_console_detailed.layout.ConversionPattern=%-4r [%t] %-5p %c - %m%n
# additional settings see: http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html


##Definition of simple FileAppender workdesk_file
#log4j.appender.workdesk_file=org.apache.log4j.FileAppender

## Configuration of simple FileAppender
## define file location tomcat-home specific
#log4j.appender.workdesk_file.File=${catalina.base}/logs/workdesk-fncm5.log
## define file location relative to root where server or server-profile was started
## ATTENTION: if you don't have permission to create folder and the folder not exist
## the logger will not work.
#log4j.appender.workdesk_file.File=./logs/workdesk-fncm5.log
## define absolute file location
#log4j.appender.workdesk_file.File=C:/temp/logs/workdesk-fncm5.log
log4j.appender.workdesk_file.File=D:/ALFRESCO-CORE/tomcat/logs/workdesk/workdesk-fncm5.log
log4j.appender.workdesk_file.layout=org.apache.log4j.PatternLayout
log4j.appender.workdesk_file.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c [%x] - %m%n


##Definition of rolling FileAppender workdesk_file_rolling
#log4j.appender.workdesk_file_rolling=org.apache.log4j.RollingFileAppender

##Configuration of rolling FileAppender
#log4j.appender.workdesk_file_rolling.File=${catalina.base}/logs/workdesk-fncm5-rolling.log
log4j.appender.workdesk_file_rolling.File=D:/ALFRESCO-CORE/tomcat/logs/workdesk/workdesk-fncm5-rolling.log
##Max size of the log files before backup
log4j.appender.workdesk_file_rolling.MaxFileSize=8KB
##Keep backup file, file name will be attached with .n (n is 1 to MaxBackupIndex)
log4j.appender.workdesk_file_rolling.MaxBackupIndex=4
log4j.appender.workdesk_file_rolling.layout=org.apache.log4j.PatternLayout
log4j.appender.workdesk_file_rolling.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c [%x] - %m%n

# perf4j
## To turn off this logger, set the level to "OFF". To activate logger, use level "INFO".
log4j.category.org.perf4j.TimingLogger=OFF

# FileNet P8
log4j.category.com.filenet=WARN
log4j.category.com.filenet.wcm.api.impl.RemoteCommand=ERROR

# FileNet P8 PE
log4j.category.filenet.pe=WARN
log4j.category.filenet.pe.rpc=ERROR
log4j.category.filenet.vw.api=ERROR
log4j.category.filenet.vw.server=ERROR

# FileNet P8 5.x
log4j.category.filenet_tracing=WARN
#log4j.logger.filenet_tracing.api=DEBUG
#log4j.logger.filenet_tracing.api.timer=DEBUG
#log4j.logger.filenet_tracing.api.detail.moderate.summary=DEBUG
#log4j.logger.filenet_tracing.api.detail.moderate=DEBUG
#log4j.logger.filenet_tracing.api.detail=DEBUG
#log4j.logger.filenet_tracing.error=DEBUG

# Apache
log4j.category.org.apache=WARN

# Spring
log4j.category.org.springframework=WARN
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Why I´m not seeing any log file in the path D:/ALFRESCO-CORE/tomcat/logs/workdesk?

Re: Viability Study - WORKDESK

deko — Mon, 11 Nov 2013 14:13:29 GMT

Hi again,

Why did you copy the properties file from "WORKDESK/WEB-INF/conf/fncm5" to "WORKDESK\WEB-INF\classes" at all? You don´t have to copy the properties file at all, as it is used straight from where it is currently located.

Why did you use the fncm5 configuration folder? This one is used for native IBM FileNet P8 5.x connections. I guess you are still using the opencmis_trial configuration folder or at least a copy of it, which also comes with it´s own log4j.properties file. Please use this one for loggin Workdesk.

You just need to change file pathes as you have it done in your snippet for the file appender, but you need to change the root logger level, so that the file appender is used at all:


log4j.rootLogger=ERROR,workdesk_file,workdesk_file_rolling
‍‍‍

Hope you are able to see log files now.

Best regards,
Dennis

Re: Viability Study - WORKDESK

dmralfing — Mon, 11 Nov 2013 15:05:00 GMT

Ok, I have copied+pasted the lines in the Alfresco_Workdesk_Installation_Guide_4.1.1.pdf in the log4j.properties and it creates a workdesk.log, although it doesn´t indicates nothing related with the databases. How do I know it the database configurations is or not created ok?. Making queries I see all the tables empties.

Re: Viability Study - WORKDESK

deko — Mon, 11 Nov 2013 16:45:00 GMT

If your log level is set to DEBUG and your DB connection is working fine, you should see at least the following lines after you logged in to Workdesk:

2013-11-11 17:39:52,028 [http-bio-8080-exec-9] DEBUG owd.core [] - OwConfiguration.applicationInitalize: start reading the bootstrap configuration data…
2013-11-11 17:39:52,034 [http-bio-8080-exec-9] DEBUG owd.core [] - OwConfiguration.createJdbcDataSource: Initializing datasource successfully.
2013-11-11 17:39:52,034 [http-bio-8080-exec-9] DEBUG owd.core [] - OwConfiguration.createJdbcDataSource: Initializing Spring Jdbc template successfully done.
2013-11-11 17:39:52,034 [http-bio-8080-exec-9] DEBUG owd.core [] - OwConfiguration.applicationInitalize: DB <DefaultDataSource> of owbootstrap.xml, JNDIName = java:/PostgreSQLDS

The easiest way to verify a working DB connection in frontend is to change something that would be written into ATTRIBUTE_BAG table: You could change for example the column order or column width of a result list colum in an Adaptable list view and check whether this information is still stored even after you restarted your application server or whether there are then entries in your OW_ATTRIBUTEBAG table.

Best regards,
Dennis

Re: Viability Study - WORKDESK

deko — Mon, 11 Nov 2013 16:49:48 GMT

If your DB connection is not working, there is the following checklist for you:

- Did you configure your DefaultDataSource node in owbootstrap.xml?
- Did you configure the corresponding Data Source in context.xml under (TOMCAT)/webapps/workdesk/META-INF?
- Are server and port of the data source accessible at all and not blocked by a firewall or similar?
- Did you provide the JDBC driver under (TOMCAT)/libs?

Best reagrds,
Dennis

Re: Viability Study - WORKDESK

dmralfing — Mon, 11 Nov 2013 17:09:00 GMT

It only prints a couple of lines in the log with all the DEBUGs activated, I don´t understand why. I put here the files:
1. This is my log4j.properties:


log4j.rootLogger=DEBUG,A1
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c [%x] - %m%n
log4j.category.com.filenet=DEBUG
log4j.category.com.filenet.wcm.api.impl.RemoteCommand=ERROR
log4j.category.filenet_tracing=DEBUG
log4j.category.org.apache=DEBUG
log4j.category.org.springframework=DEBUG
log4j.appender.workdesk_file=org.apache.log4j.FileAppender
log4j.appender.workdesk_file.file=C:/DANI/ALFRESCO-SHARE/logs/workdesk/workdesk.log
log4j.appender.workdesk_file.layout=org.apache.log4j.PatternLayout
log4j.appender.workdesk_file.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c [%x] - %m%n
log4j.appender.workdesk_file.append=true
log4j.rootLogger=ERROR,workdesk_file,workdesk_file_rolling
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

2. This is my workdesk.log


2013-11-11 17:54:11,750 [main] INFO  owd.core [] - com.wewebu.ow.server.servlets.OwConfigurationInitialisingContextListener.contextInitialized: started…
2013-11-11 17:54:11,776 [main] DEBUG owd.core [] - OwConfiguration.applicationInitalize: start initializing the application logger…
‍‍‍‍

Re: Viability Study - WORKDESK

dmralfing — Mon, 11 Nov 2013 17:41:30 GMT

I´m gonna copy/paste what I have configured for the databases. The port isn´t locked, neither the port
nor the server, that won´t be a problem. If it´s something wrong, anyway I hope that the log file tell me
what´s the matter, no?. This are the files I have modified:

1. This is the context.xml:


<?xml version="1.0" encoding="UTF-8"?>
<Context path="/workdesk" debug="100" privileged="true" reloadable="true">    
    <Resource name="java:/MySQLDS"
        auth="Container"
        type="javax.sql.DataSource"
        factory="org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory"
        username="owd"
        password="abs"
        driverClassName="org.gjt.mm.mysql.Driver"
        url="jdbc:mysql://localhost:5432/alfresco?autoReconnect=true"
        maxWait="1000"
        removeAbandoned="true"
        maxActive="30"
        maxIdle="10"
        removeAbandonedTimeout="60"
        logAbandoned="true"
        validationQuery="select 1"/> 
</Context>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

2. In the owbootstrap.xml I put:


   <DefaultDataSource>
      <JNDIName>java:/MySQLDS</JNDIName>
   </DefaultDataSource>
‍‍‍‍‍

3. The JAR files: I have the JARs in the lib inside the WAR and also in the Tomcat Lib, in both.
This files are:


commons-collections-3.2.1.jar
mysql-connector-java-5.1.25-bin.jar
commons-pool-1.5.4.jar
commons-dbcp-1.3.jar
‍‍‍‍‍‍

And this is the script I have executed for mysql - copied from the documentation -


drop schema owdemo;
== This lines I have done myself, I don´t know if there is necessary to give all privileges but I don´t mind because it´s a demo ==
create database owdemo default character set utf8 collate utf8_bin; 
grant all on owdemo.* to 'owdemo'@'localhost' identified by 'owdemo' with grant option; 
grant all on owdemo.* to 'owdemo'@'localhost.localdomain' identified by 'owdemo' with grant option;


== Create_MySQL_Database.sql ==
GRANT USAGE ON *.* TO 'owdemo'@'localhost';
DROP USER 'owdemo'@'localhost';
DROP DATABASE IF EXISTS owd;
CREATE USER 'owdemo'@'localhost' IDENTIFIED BY 'owdemo';
GRANT ALL PRIVILEGES ON *.* TO 'owdemo'@'localhost' WITH GRANT OPTION;
CREATE DATABASE owd;

== OwMySQL_CreateAttributeBagTable.sql ==
DROP TABLE IF EXISTS `owd`.`OW_ATTRIBUTE_BAG`;
CREATE TABLE  `owd`.`OW_ATTRIBUTE_BAG` (
  `UserName` varchar(128) NOT NULL,
  `BagName` varchar(128) NOT NULL,
  `AttributeName` varchar(256) NOT NULL,
  `AttributeValue` varchar(1024) NOT NULL,
  PRIMARY KEY (`UserName`,`BagName`,`AttributeName`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

== OwMySQL_CreateDBHistoryManagerTable.sql==
DROP TABLE IF EXISTS `owd`.`OW_HISTORY`;
CREATE TABLE  `owd`.`OW_HISTORY` (
  `EventIndex` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `OW_HIST_Type` int(10) unsigned NOT NULL,
  `OW_HIST_ID` varchar(128) NOT NULL,
  `OW_HIST_Status` int(10) unsigned DEFAULT NULL,
  `OW_HIST_Time` datetime DEFAULT NULL,
  `OW_HIST_User` varchar(255) NOT NULL,
  `OW_HIST_Summary` varchar(2048) DEFAULT NULL,
  `ObjectDMSID` varchar(255) DEFAULT NULL,
  `ObjectName` varchar(1024) DEFAULT NULL,
  `ParentDMSID` varchar(255) DEFAULT NULL,
  `ParentName` varchar(1024) DEFAULT NULL,
  `Custom1` varchar(2048) DEFAULT NULL,
  `Custom2` varchar(2048) DEFAULT NULL,
  `Custom3` varchar(2048) DEFAULT NULL,
  PRIMARY KEY (`EventIndex`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

== OwMySQL_CreateDBRoleManagerTable.sql
DROP TABLE IF EXISTS `owd`.`OW_ROLE`;
CREATE TABLE  `owd`.`OW_ROLE` (
  `ROLE_ID` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `ROLE_NAME` varchar(255) NOT NULL,
  `ROLE_RESOURCE` varchar(255) NOT NULL,
  `ROLE_ACCESS` int(11) NOT NULL DEFAULT '-1',
  `ROLE_ACCESS_MASK` int(11) NOT NULL DEFAULT '-1',
  `CATEGORY` int(10) unsigned NOT NULL,
  PRIMARY KEY (`ROLE_ID`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Viability Study - WORKDESK

d_evil — Tue, 12 Nov 2013 08:10:14 GMT

Hi dmralfing,

you are showing a lot of configuration,
but compare your JDBC definition to the inforamtion you posted:


url="jdbc:mysql://localhost:5432/alfresco?autoReconnect=true"<— DB connection to "alfresco" 
‍‍‍


GRANT USAGE ON *.* TO 'owdemo'@'localhost';
DROP USER 'owdemo'@'localhost';

DROP DATABASE IF EXISTS owd;<— DB of script is "owd"


CREATE USER 'owdemo'@'localhost' IDENTIFIED BY 'owdemo';<— look also on the user name 

GRANT ALL PRIVILEGES ON *.* TO 'owdemo'@'localhost' WITH GRANT OPTION;

CREATE DATABASE owd;

‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Are you really accessing the right Database?
Look closely where you have create the tables for workdesk, and configure it the right Database in JDBC definition.
Also there is no need to duplicate the jdbc-driver libraries in Tomcat/lib and Application-War, if you have jdbc-driver already placed into Tomcat/lib the War-JDBC lib will be ignored.

Regarding logging, Workdesk contains in WEB-INF/conf/<configurationLabel>/log4j.properties
look into that files, it will overwrite the WEB-INF/classes configuration of Log4j when starting the application.

Regards,
D.evil

Re: Viability Study - WORKDESK

deko — Tue, 12 Nov 2013 08:55:12 GMT

Hi dmralfing,

As D.evil mentioned correctly you have some misconfigured files:

1. You used the original DB scripts that create a DB named "owd" and a user "owdemo" (see script content). In your context.xml file I can see that your URL points to a database named "alfresco" and your user is "owd". You need to fix it by using correct values in your context.xml.

2. I guess you are using Workdesk to connect against an Alfresco system. Why are you using the log4j.properties file from "Filenet" (see category in your config file)? You do not have to copy anything from the guides, but there is a log4j.properties file in every configuration folder under workdesk/WEB-INF/conf/configurationFolder/ that can be used out of the box, only that File appender, log level and log file location need to be configured correctly. The two log lines you see so far are OK and just show that the Workdesk application started fine. As soon as you log in to Workdesk with a user, you should see much more lines.

3. As D.evil also already mentioned, there is no need to have duplicate versions of the JDBC driver. Please locate it under Tomcat/libs and you are fine.

After having corrected the steps above you should be fine and DB connection with Workdesk should be running.

Best regards,
Dennis

Re: Viability Study - WORKDESK

dmralfing — Wed, 13 Nov 2013 13:45:00 GMT

Ok, you are right about the schema name, it was wrong.
But I can´t configurate the log4j.properties. It´s for opencmis, can you tell me what´s wrong?. I can´t see the traces!


log4j.rootLogger=ERROR,workdesk_console,workdesk_file_rolling

log4j.appender.workdesk_console=org.apache.log4j.ConsoleAppender
log4j.appender.workdesk_console.layout=org.apache.log4j.PatternLayout
log4j.appender.workdesk_console.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c [%x] - %m%n
log4j.appender.workdesk_console_detailed=org.apache.log4j.ConsoleAppender
log4j.appender.workdesk_console_detailed.layout=org.apache.log4j.PatternLayout
log4j.appender.workdesk_console_detailed.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c [%x] {%C{2}.%M} - %m%n

log4j.appender.workdesk_file.File=C:/DN/ALFRESCO-SHARE/logs/workdesk/workdesk-opencmis.log
log4j.appender.workdesk_file.layout=org.apache.log4j.PatternLayout
log4j.appender.workdesk_file.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c [%x] - %m%n

log4j.appender.workdesk_file_rolling.File=C:/DN/ALFRESCO-SHARE/logs/workdesk/workdesk-opencmis-rolling.log
log4j.appender.workdesk_file_rolling.MaxFileSize=8KB
log4j.appender.workdesk_file_rolling.MaxBackupIndex=4
log4j.appender.workdesk_file_rolling.layout=org.apache.log4j.PatternLayout
log4j.appender.workdesk_file_rolling.layout.ConversionPattern=%d{ISO8601} [%t] %-5p %c [%x] - %m%n

log4j.category.org.perf4j.TimingLogger=OFF
log4j.category.org.apache=WARN
log4j.category.org.springframework=WARN
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Viability Study - WORKDESK

dmralfing — Wed, 13 Nov 2013 14:02:53 GMT

SorrY, I forgot to add the FileAppender as you said, the log4j is already working!

Re: Viability Study - WORKDESK

dmralfing — Wed, 13 Nov 2013 15:20:51 GMT

It appears a javax.naming.NameNotFoundException telling that the JNDI name is not associated to the context. But you can see that I have the same name "java:/MySQLDS" in both (context.xml and owbootstram.xml), so It should associate it right. Moreover I think I´m using the opencmis due to I set it in the web.xml. I copy/paste you the relevant files:


   <DefaultDataSource>
      <JNDIName>java:/MySQLDS</JNDIName>
   </DefaultDataSource>
‍‍‍‍‍

In the file "WORK-DESK/WEB-INF/conf/opencmis/owbootstrap.xml" I have:


<?xml version="1.0" encoding="UTF-8"?>
<Context path="/workdesk" debug="100" privileged="true" reloadable="true">   
    <Resource name="java:/MySQLDS"
        auth="Container"
        type="javax.sql.DataSource"
        factory="org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory"
        username="owd"
        password="abs"
        driverClassName="org.gjt.mm.mysql.Driver"
        url="jdbc:mysql://localhost:5432/owd?autoReconnect=true"
        maxWait="1000"
        removeAbandoned="true"
        maxActive="30"
        maxIdle="10"
        removeAbandonedTimeout="60"
        logAbandoned="true"
        validationQuery="select 1"/> 
</Context>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

In the web.xml I have:


        <param-value>deploy#WEB-INF/conf/opencmis</param-value> 
‍‍‍

Re: Viability Study - WORKDESK

deko — Wed, 13 Nov 2013 16:11:00 GMT

Hi again,

This might be a caching issue now:

Please check (TOMCAT)/conf/Catalina/localhost and delete cached versions of a workdesk.xml file there, so that it will be redeployed from META-INF/context.xml. In addition you might even clear other cached files under (TOMCAT)/work/Catalina/localhost/workdesk

Best regards,
Dennis