community
Configuration FAQ
Questions about Teamwork configuration
For more information about Teamwork configuration read the user guide.
Can I clean data after some tests?
We assume now that you are logging in as administrator, so you don’t have security related problems. One way is to repeat installation on an empty database.
Otherwise, notice that Teamwork is structured with referential integrity; hence you cannot delete areas until there are objects in the area. It would be very dangerous to "cascade delete" from area to the other objects, as tasks, resources, documents, issues etc., possibly thousands of objects, would be deleted with one click.
Any area created with the wizard page has several roles on it. In this case, if one wants to delete it, one way is simply to rename it to a wanted area; otherwise one has to delete all the roles of the area, and then delete the area.
I can't configure Teamwork to support my language characters
1. Check whether your database is configured to support UTF-8 encoding.
In the case of MySql, you can add some properties to JDBC connection url in config.properties file:
url=jdbc:mysql://localhost/teamwork?useUnicode=true&characterEncoding=utf-8
2. Check whether you web server is configured to support UTF-8 URI encoding.
We found out that Tomcat by default does not correctly encode URLs: in order to get correct encodings, you must set
URIEncoding="UTF-8"
In the connector configuration for example:
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" URIEncoding="UTF-8"/>
How do I verify/change Teamwork memory settings?
On Windows: if you are using the windows service: open a command console (
tomcat6w //ES//teamwork8080
and an application will open and in the "Java" tab you can modify memory settings. Arougher method is go to Start -> Run, and run "regedt32.exe". There should be an entry at HKEY_LOCAL_MACHINE -> SOFTWARE -> Apache Software Foundation -> Procrun 2.0 -> [Tomcat service name]. If you are launching using the tw.bat, edit the file, change the -Xms64m -Xmx128m settings to a higher range.
On Linux: open the teamworkLinux.sh script, and
On OSX: if you are launching by script by hand, open the teamworkOsx.sh script, and change the -Xms64m -Xmx128m settings to a higher range. If you are launching Teamwork as service, change in [teamwork root folder]/launchdScript.sh the line "export JAVA_OPTS=-Xmx512M $JAVA_OPTS" (if it is #export JAVA_OPTS=-Xmx512M $JAVA_OPTS, remove the #).
You may also want to widen the PermGen space: e.g. -Xms512m -Xmx1024m -XX:PermSize=128M -XX:MaxPermSize=256M
Doing this or that, I get a blank screen. The error shown by the error page is not informative.
In order to see complete errors, check out the application logs, in
[…]WEB-INF/log/platform.log
. You can also see the logs through the web interface if you are administrator:
tools -> administration -> debug -> see log .
Change labels or translate the interface
See 17.5.5 and 17.5.6 of the user guide.
See here .
This usually happens when there was originally an exception at setup; so schema update and basic data creation was not af first completed. You stop logging an exception by simply going to tools -> administration -> global settings, checking "setup notified admin wizards", saving, and at next restart there should be no error in logs.
Configuration is explained in the user guide (Chapter 9), found here.
How it works is explained here:
http://twproject.blogspot.com/2007/04/integrate-your-java-agenda-and-ical.html
We don't get notifications by e-mail
Proceed as follows:
1. set the SMTP server: login as administrator, go to tools -> administration -> global settings, and set and test the SMTP parameters.
Every user that wants notifications:
1. must have an e-mail address set in his "person" editor data
2. should update subscriptions settings, by going say on the assignment editor, and chack the subscription by e-mail column.
Customizing images and login page in Teamwork
Images in Teamwork have this structure: some images are in the supporting platform, and hence are in
[ROOT]/commons/skin/[name of the skin]
all these images are "skinned", hence unique for each skin (which you set in options).
others are unique to Teamwork, and hence are in
[ROOT]/application/teamwork/images
and some of these are skinned.
In particular, the logo is skinned, and hence is in
[ROOT]/application/teamwork/images/[name of the skin]
with name "logo.gif" and "logo_positive.gif".
You can also create an entirely customized skin, by creating a new folder in
[ROOT]/commons/skin/[your new name]
say by copying an existing one, and then by choosing this folder in your options (the options simply list the folders there existing. Recall to create such folder also in
[ROOT]/application/teamwork/images/[your new name]
So actually the entire appearance can be customized.
For the login page, the background image is
[ROOT]/application/teamwork/images/[name of the skin]/logInBgnd.gif
typically
[ROOT]/application/teamwork/images/cyan/logInBgnd.gif
and this can be changed too.
Identifier case sensitiity in MySQL
See here .
Some pages like operator load don't work on MySQL
If you are getting exception in the log like "Caused by: java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost.", this is a MySQL JDBC bug, see
http://forums.mysql.com/read.php?39,203407,217196#msg-217196
You can "fix" it by disabling query cache as wrote in the link.
Teamwork tells me that the licensed operators have exceded
Teamwork says that because probably you have a hidden user.
To find it, try to check the field called “People” in the resource search form , on the right will appear some new fields , one of them is called “include hidden” ,check also that.
Now click on search and the hidden users will appear in the list.
Problem after migration of a MySql database from Windows to Linux:
When a MySql database is restored on Linux from a backup file created on Windows maybe the names of some tables have been transformed to lower case.
Check these Teamwork tables after the migration of the database:
olpl_persistenttext (correct name : olpl_persistentText)
olpl_flowmailattacher (correct name : olpl_flowMailAttacher)
olpl_i18nentry (correct name : olpl_i18nEntry )
twk_discpointtype (correct name : twk_discPointType)
twk_discpointstatus (correct name : twk_discPointStatus)
Here is the script you should run on your MySql to correct the names of these tables:
alter table olpl_persistenttext rename to olpl_persistentText;
alter table olpl_flowmailattacher rename to olpl_flowMailAttacher;
alter table olpl_i18nentry rename to olpl_i18nEntry;
alter table twk_discpointtype rename to twk_discPointType;
alter table twk_discpointstatus rename to twk_discPointStatus;
Teamwork and PostgreSql
See here how to configure your database and application to have them work properly.
