To post a new topic, please Log in or register

FAQ: TeamWox Groupware installation

Liliya
8
Liliya 17/05/2010 12:00 | #

What to do if WebDav on Windows 7 is working slower?

If you work on Windows 7 and have mentioned that WebDAV is running slower, do the following:

  1. Disable the WebDAV drive (through the right mouse button menu)
  2. Close Internet Explorer (if it's running)
  3. Select Internet Options in the Control Panel. On the Advanced tab, click the Reset button. You don't need to tick the checkbox to delete personal settings. Perform the Reset and press OK:



  4. Reopen IE8 and configure the proxy settings. Remove the checkmark from "Automatically detect settings":


  5. Reconnect the WebDAV drive
This is not the error of the TeamWox server, but a bug in Windows 7. The solution is published on the Microsoft tech center forum.
TeamWox SDK: Search and Filtering - Part 2

Filtering is a selection of data subset with retaining the way this data is displayed in a module. In this article we will talk about how to use TemaWox search technology to solve a typical problem for many modules - filtering a large number of records.

Airat
87
Airat 01/06/2010 14:54 | #

Why can't I set up WebDAV folder on Mac OS X?

  1. Open Disk Utility, located in the Macintosh HD > Applications > Utilities folder, and select the WebDAV disk in the left column.
  2. Click the First Aid tab in the Disk Utility window.
  3. Click the Repair Disk Permissions button on the First Aid tab.
  4. Restart the computer.
Airat
87
Airat 05/07/2010 18:06 | #

What are the existing means of integration of TeamWox with other systems?

There are several ways to integrate TeamWox with other information systems:
  1. "Chat" and "Service Desk" modules. These modules have components for integration with the web site of your company, allowing you to arrange an additional channel of communication between the clients and the managers of your company. The "Chat" gives you the opportunity to create an on-line consultation service for clients, and the "Service Desk" module provides the acceptance of requests from customers, and allows them to track their requests processing on your web site.

  2. The use of the HTTP protocol. For integration of TeamWox with your company's web site or any other information system, an additional module is developed for the website, or a code/script is added to the site, which exchanges information with TeamWox via HTTP. The add-on of a website emulates requests, which are sent by the web browser when the user is working in TeamWox. Thus, this method is used to synchronize the databases of potential clients, registered on our website www.teamwox.com, and the databases of our current clients in our corporate TeamWox.

  3. Import/export of data. For information exchange within the system, there is a built-in import/export mechanism. Currently two types of file formats are supported for import and export: CSV files and HTML files (formats, compatible with the programs MS Excel and OpenOffice Calc). In TeamWox this method is used for simultaneous import of a user list, a list of organizations, transactions in "Accounting", etc. TeamWox SDK allows you to implement support of formats of your choice, for import or export.

  4. Standalone Database Management System (DBMS) Firebird. By default TeamWox uses the embedded version of the Firebird. The access to the database is thus limited to one application - the TeamWox server. If you wish to build a specific complex report, you can install a detached DBMS Firebird on your computer (this product is free - http://www.firebirdsql.org/), and reconfigure TeamWox (one line in the configuration file). Access to the database with a detached Firebird can be carried out on multiple applications, including applications for the generation of specific reports, which can be developed using any programming language and any tool that supports working with Firebird.

  5. Additional custom reports for modules included in the delivery of TeamWox. If you want your custom reports to be accessible from the TeamWox interface, then with the help of TeamWox SDK, you can develop a module that will contain custom reports for any of the modules, included in standard delivery. Reports from these modules will be added to the TeamWox interface into the list of reports of the required module.

  6. Add-on for eBank. If you need to perform integration with a payment system or a system of client-bank, you can use TeamWox SDK to develop a plug-in module "eBank", which will provide access to your payment system and synchronize the information about transactions and payments, which will be reflected in the "Accounting" module.

  7. TeamWox module. For implementing an additional functionality of TeamWox, you have the opportunity to develop a separate module, using TeamWox SDK, which will be presented in a separate tab and will have the necessary user interface (pages, forms, etc.). The module can exchange information with other information systems. An example of the use of this method is the TeamWox module "MetaTrader 4", which provides integration with MetaTrader 4 server, and deals with the issue of organizing the TeamWox workplace for managers, who work with brokerage company clients.
Airat
87
Airat 06/07/2010 15:18 | #

I've added a user to the outsource group, with very limited access rights, but now the user cannot even log in the system. What could be the problem?

Most likely you've completely blocked the "Server" group rights together with authentication modes.
You need to allow at least the basic right to access "Server" module and enable "Allow to authenticate by login".
Airat
87
Airat 07/07/2010 16:19 | #

I've installed TeamWox server recently, but cannot access it today. The logs show that the service is launched, and the ports are unoccupied. What might be the reason for the problem?

The TeamWox service is configured to run automatically during the Windows start. When TeamWox starts it requires an IP address to which you have binded it during the installation:

If you are using ADSL/Wi-Fi and other routers to access the Internet, the IP address can be allocated during the installation of the connection.
This can happen after the TeamWox system has been launched. For such cases, we recommend to choose "any" for the IP address during the installation.

In order to ensure that TeamWox system is loaded without errors, you need to make the following changes:

  1. Stop TeamWox service by running the command "updater.exe /stop" (see console commands).
  2. Change a value of "server_ip" parameter or create it, if it doesn't exist in the TeamWox system configuration file (teamwox.cfg file in \config folder), specify "0.0.0.0" there. This will allow TeamWox system to occupy all available addresses instead of requiring the presence of a specific IP address.

  3. Bind your SSL certificate to IP address "0.0.0.0" by "teamwox.exe /certinstall" command (see console commands).
  4. Bind your TeamWox domain name to your local computer IP address by changing "hosts" file located in "C:\Windows\System32\drivers\etc" directory:

  5. Launch the TeamWox server by "updater.exe /start" command (see console commands).

After this is done, the TeamWox server will work with reference to the IP address "0.0.0.0" and won't require allocation of specific IP address at startup.

Airat
87
Airat 02/11/2010 17:46 | #

What are the requirements of VPS to install TeamWox server?

Recommended configuration is: 

  • Windows 2003 Server SP2, Windows 2008 Server.
  • 2- or 4-core CPU (Intel Core 2 Duo, AMD Phenom and higher).
  • 2 Gb RAM or more for 64x version.
  • Storage: 100 Gb. Space occupied by the system depends on the TeamWox users activity (amount of mail, uploaded files, tasks, etc.).
     
Airat
87
Airat 04/11/2010 13:00 | #

How to configure your workplace for working with TeamWox? 

Once you have installed and configured the TeamWox server, you need to configure the workplaces in order to be able to access the TeamWox.

1. If you use default SSL certficate, you should add MetaQuotes Software CA to the list of trusted authorities in the browser

By default TeamWox server uses the SSL certificate issued by the unauthorized center MetaQuotes Software CA, although it's qualitative and full-functional, this certificate has a serious disadvantage - web browsers don't trust it and generate warning messages. In order to avoid appearance of such messages, you have to import the certificate to the list of trusted root certificates in your browser. To do this you need MetaQuotesSoftwareCA.cer file, it can be found on TeamWox server \config folder or it can be downloaded at TeamWox authorization page:

 Authorization page

 After that do the following steps, according to the browser used on the workplace:

  • Internet Explorer
    Open the menu Tools > Internet Options > Content > Certificates > Trusted Root Certification Authorities, and click the "Import..." button. The Certificate Import Wizard shows up. 
  • Mozilla Firefox
    Open the Tools > Options > Advanced > Encryption > View Certificates > Authorities > click the "Import..." button. Choose MetaQuotesSoftwareCA.cer file.
  • Opera
    Open the Settings > Preferences > Advanced > Security > Manage Certificates.. > Authorities > click the "Import..." button. Choose MetaQuotesSoftwareCA.cer file.
  • Google Chrome
    Open the Tools > Options > Under the Hood tab > Manage certificates >Trusted Root Certification Authorities, and click the "Import..." button. The Certificate Import Wizard shows up.

Another solution is to purchase an authorized SSL certificate for your TeamWox. See for details the article How to Get a Legal SSL Certificate for TeamWox

2. In the case of accessing TeamWox within the local network, hosts file on the user's PC should be edited

If a user access TeamWox locally, you should bind domain name of your TeamWox to the local IP address of the server. It can be done through editing hosts file in operating system on user computer. Navigate to the file "C:\Windows\system32\drivers\etc\hosts" and open it using a standard Notepad. At the end of it add the following entry:

<local IP address of the server> <domain name of the TeamWox server>

e.g. 192.168.1.1 mydomain.tmwox.com and save the changes.


3. In the case of accessing TeamWox within the local network, it is recommended to add the domain name to the list of exceptions for proxy in the browser settings 

If you use a non-transparent proxy server to access Internet, then there is usually a proxy server address and a port, indicated in the browser settings on the client's computer. In order to save traffic, meaning access TeamWox within a local network, you should indicate TeamWox domain name in your browser settings as an exception to the rule of connection through the proxy server:

  • Internet Explorer
    Open the Tools > Internet Options > Connections > LAN Settings > Advanced, in the 'Exceptions' text box type the address of your TeamWox, and click 'Ok'.

  • Mozilla Firefox
    Open the Tools > Options > Advanced > Network > Settings, in the 'No proxy for' text box type the URL of your TeamWox and click 'Ok'.

  • Opera
    Open the Settings > Preferences > Advanced > Network > Proxy servers, in the "Do not use proxy on the addresses below" field add the domain name of your TeamWox.
  • Google Chrome
    Open the Options > Under the Hood tab > Change proxy settings > Connections > LAN Settings > Advanced, in the 'Exceptions' text box type the address of your TeamWox, and click 'Ok'.
After configuring these settings, check the accessibility of the TeamWox server from a client computer using the telnet command. In order to do this, open the Start > Run, type cmd and press Enter. You will see a command prompt, in which you have to type:
telnet <domain name of the TeamWox server> 443

If after pressing the Enter button you will see a black screen, with a blinking cursor in the upper left corner, it means the connection has been performed. You can open the browser page https://mydomain.tmwox.com and begin using the TeamWox system.

If connection wasn't established, it means that you should check your firewall and antivirus settings on the client computer, as well as on the server side.

Shafigullin
95
Shafigullin 29/08/2011 11:13 | #

Can I install TeamWox server on VDS?

Yes, you can use virtual environment for TeamWox server installation for evaluation purposes.

We strictly do not recommend to install working TeamWox server on a virtual machine! While the load on a server increases, more CPU capacity is needed. As a result, forced "capture" of physical server resources occurs (because of the peculiarities of many virtual machines). And all that ends in hardware failure.

Shafigullin
95
Shafigullin 29/08/2011 11:15 | #

Please, explain how I can install your TeamWox on my web-hosting.

In case you have a place for your web-resource, you won't be able to install TeamWox server there. To install TeamWox server you should have a computer managed by Microsoft OS beginning from Windows XP SP3 up to Windows Server 2008.
Shafigullin
95
Shafigullin 29/08/2011 11:17 | #

I have a website. How can I install TeamWox there?

TeamWox is a web server by its nature and can be installed only on a Windows platform. You cannot install TeamWox server on an existing web service.
Back to topic list  | 12345678

To add comments, please Log in or register