datango collaborator Installation manual
Table of contents System requirements 4 Installing required applications 5 Microsoft.NET Framework 2.0 5 Windows Installer 6 Java Runtime Environment (JRE) 7 Installing MS SQL Server Express Edition 8 Settings 10 Installing the Tomcat server 12 Configure a secure connection (SSL) 14 Change of memory allocation 15 Installing the datango collaborator 17 Server Install Page 17 Step 1 SQL Server Connection: 18 Step 2 Database Initialization 19 Step 3 Various settings 20 Step 4 collaborator initialization 21 Finish installation process 22 License Manager 23 Single sign-on 25 Setup 25 Settings for Mozilla Firefox 27 Settings for Internet Explorer 27 Import of user structures 28 Import from an excel file 29 Import from a LDAP structure 31 Working with collaborator and producer 33 How to connect 33 Step 1: Select Server 34 Step 2: Select workarea 35 Step 3: Personal group 37 First Steps 39 Table of contents 2
Updating the datango collaborator 40 Note for LDAP based user structures 42 Up to datango collaborator 2010 version 8.0.0 build 865 42 With datango collaborator 2010 and above version 8+ 43 Table of contents 3
System requirements Operating system: Microsoft Windows Server 2003 Microsoft Windows Server 2008 Microsoft Windows Server 2012 Microsoft Windows XP Service Pack 2 Microsoft Windows 7 Note: Please note that a licensed version of Microsoft SQL Studio is required, when using the collaborator with a IA64 based environment - since the Express version only supports x64 and EMT64 based hardware configurations. Note the limitations according to each Express version as well. Processor: Intel Core 2 Quad Processor or equivalent with at least 2,2 GHz or higher Memory: At least 2 GB RAM Hard disk: At least 10 GB free Required Applications (included in software pack): Windows Installer in version 3.1 or higher Microsoft.NET Framework 2.0 Java Runtime Environment (JRE) in version 6 Update 1.6 or higher Microsoft SQL 2005/2008/2008R2/2014 (Express Edition) Apache Tomcat in version 6.0.16 or higher 4
Installing required applications Microsoft.NET Framework 2.0 Microsoft.NET Framework 2.0 is essential for the installation of Microsoft SQL 2005 Express Edition. It has to be implemented in the operating system previously. Without.NET Framework 2.0 the installation process of Microsoft SQL 2005 Express Edition will be aborted. You can check as follows, whether Microsoft.NET Framework has been installed on your operating system before and, if so, in which version it has been installed: Go to Start -> Settings -> Control Panel Choose Add or Remove Programs Choose Programs and Features in Windows Vista. Search for the entry Microsoft.NET Framework 2.0 (Service Pack x) in the list of the installed programs. If there is no such entry, you have to install it. 5
Windows Installer Installing Microsoft SQL 2005 Express Edition the Windows Installer Service has to be in version 3.1 at least. The installation process will be aborted with an error message, if the Windows Installer version is lower than 3.1. As following you can check, which version of Windows Installer is installed in your operating system. Go to Start -> Run and type msiexec /help into the command line input. A window appears which is showing some information about the Windows Installer. You will find the recent version number in the first line. 6
Usually the Windows Installer is updated by the automatic Windows Update service. Java Runtime Environment (JRE) The Java Runtime Environment (JRE) is essential for the functionality of the datango collaborator. It should be installed at least in version 6 update 1.6. You can check as follows, whether Java Runtime Environment (JRE) has been installed on your operating system before and, if so, in which version it has been installed: Go to Start -> Settings -> Control Panel Choose Add or Remove Programs Choose Programs and Features in Windows Vista. Search in the list of installed programs for the entry Java(TM) 6 Update x. If there is no such entry, you have to install it. You can download the installation file by using the following link: http://www.java.com/en/download/ 7
Installing MS SQL Server Express Edition With MS SQL Server Express Edition Microsoft offers a free version of the database server. This version almost fulfils the requirements for using the datango collaborator in small up to middle-sized productive environments. If your plan is to use the collaborator in an environment with a high number of user accesses it may happen that Microsoft s limitations will negatively occur to the performance of the application. According to that case we recommend the use of a fully fledged MS SQL Server version without limitations. Note: Please read necessary settings in following subchapter Settings if you will use an already existing installation of MS SQL Server. Start the installation process of Microsoft SQL Server Express Edition by a double-click on the file SQLEXPR_ADV_EN.EXE. The installation dialog appears. Agree to the license agreement and click the button Install in the following Installing Prerequisites dialog. After finishing the installation of the prerequisites the dialog window System Configuration Check appears. Clicking the button Next, an automatic system check verifies that all requirements for a successful installation are given. If there are components or applications missing, the summary of the check will contain warnings for the specific errors. The installation process will be aborted afterwards. Note: The Warning IIS Feature Requirement is not essential for a successful installation. The feature Internet Information Services (IIS) Feature is not necessary for the functionality of the datango collaborator. 8
Click the button Next. After showing the installation progress the window for the Registration Information appears. Enter your personal data and click the button Next. In the Feature Selection dialog you can add the component Management Studio Express, provided there is a need for the administration of the database. Otherwise you have not to change anything on the given standards. Click the button Next. In the dialog for the Authentification Mode you have to choose the option Mixed Mode. Insert a password for the super administration user sa. In the dialog for the Configuration Options you should activate the option add user to the SQL Server Administrator role. This option adds your recent user account as a SQL administrator. Note: Please leave the checkbox Hide advanced configuration options selected. You should configure advanced options only if you have the knowledge according to. The description of the advanced configuration options will not be part of this manual. In the dialog Error and Usage Report Settings is no need for changes. Just click the button Next. Start the final installation process by clicking the button Install. 9
Settings After finalizing the installation process, please start the SQL Server Configuration Manager by choosing the menu item SQL Server Configuration Manager in Start - > Programs -> Configuration Tools. Note: Using an already existing installation of MS SQL Server please check that you have the SQL Native Client installed and the protocol for Named Pipes enabled. Expand the item SQL Server 2005 Network Configuration in the left frame of the SQL Server Configuration Manager. Choose the sub item Protocols for SQLEXPRESS. Enable the protocols for Named Pipes and TCP/IP by selecting the item Enable in the context menu of each one. 10
Now choose the item TCP/IP again and call the Properties item in the context menu. Insert the number 1433 in every line where a TCP-Port is requested. Click on the button Apply and close the window with the Ok button. Note: These settings won t work until you have restarted the server. When the Server was restarted, you can close the SQL Server Configuration Manager. 11
Installing the Tomcat server Note: You can download the most recent setup file for tomcat server here: http://tomcat.apache.org/ Start the installation of the Tomcat server by a double click on the installation file, i.e. apache-tomcat-6.0.xx.exe. The installation dialog appears. Just accept the license agreement by a click on the button I agree. In the Choose Components dialog expand the item Tomcat in the tree view. Enable the item Native and click the button Next. In the next dialog you may customize the target directory for your installation. Afterwards click the button Next.
In the Configuration dialog you may customize your administrative user name with a specific password. Port number 8080 should not be customized, unless you have other needs and the experience to do so. In the Java Virtual Machine dialog the path to the designated java installation is set. Usually the path is recognized automatically. If there is no path recognized or if you have some other needs for choosing another java installation, choose the path by your own. Usually a standard java installation should be installed in C:\Program Files\java\. Click the button Finish. This will finalize the installation process.
Configure a secure connection (SSL) Apache Tomcat provides the creation of self-signed certificates as even as the import of TTP certificates (Trusted Third Party, for example by VeriSign, TC TrustCenter, Signtrust, TeleSec, Thawte Consulting). By using an SSL certificate you are able to encrypt all communication with the server, thus the communication with datango collaborator. Using an SSL connection you will have to call the datango collaborator with https:// as prefix of address. Please read the Tomcat documentation for detailed information about configuring SSL within a Tomcat environment: http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html
Change of memory allocation The performance of Apache Tomcat depends on the size of the memory available for java applications, since it will be necessary for executing actions as fast as possible even by a large amount of connections. After installation the default value is 64 MB, which is not suitable for high server performance. Change the value as following: 1) Start the tomcat management by using Start -> Programs -> Apache Tomcat x.x -> Configure Tomcat. Alternatively you may start it by using the file Tomcat6w.exe, which is located inside the bin folder in Tomcat installation directory. 2) Choose the tab Java (1) and insert an accordant value into the field Maximum memory pool (2). Note: Windows restricts the memory allocation of java within a 32bit environment. Insert 1380 at maximum as value. Otherwise the tomcat service won t work. This restriction does not apply within a 64bit environment.
3) Choose tab General (1). Start the service by clicking on Start (2). If tomcat service is running already, you have to stop it before by clicking Stop (3). Warning: If Service Status shows Stopped after trying to start the service, the value for memory allocation might be overvalued. Enter a lower value and try again.
Installing the datango collaborator For the installation of the datango collaborator just open your favourite browser application and type in the following address: http://localhost:8080/manager/html An authentication window appears. Insert the username and password as defined in the installation process of the Tomcat server. The Tomcat Manager will open in the browser window. Scroll to the section Deploy and click the button Browse. Go to the file collaborator_xx.war, select it and click the button Open. Now click on the button Deploy and wait for a little moment. The browser window refreshes automatically after the file was integrated successfully. You will find a new entry in the list of applications. It should have the same title as the file you have deployed. Click on the path entry in the column Path. This will open the datango collaborator. Again an authentication window appears. Please insert the login data you have obtained separately. Server Install Page With the server install page you got a wizard to define all settings for the datango collaborator. You can define all values individually in just 4 steps. In the following parts you will get an overview of the values you may define in those 4 steps by your own.
Step 1 SQL Server Connection: Server address: Specify the address of the server, which is allocating the Microsoft SQL Express Server. If the SQL Server is located on your own workstation, please don t use the IP address 127.0.0.1, which is normally used for a localhost. Instead you should use the status dialog of your network connection to determine the IP address, which is given to your workstation by the network host. Otherwise it might be that the collaborator becomes inaccessible for other network participants. Use the appendix :1433 for the IP address you have specified. This is the port definition, which is necessary for a successful connection to the Microsoft SQL Server. Schematic Example: 192.168.100.132:1433 Authentication user: Insert username sa. This username is used for the super administrator of the SQL-Server. Authentication password: Insert the password you have defined for the super administrator in the installation process of the Microsoft SQL Express Server. Repeat password: Repeat password as you have entered in field authentication password.
Step 2 Database Initialization You have the opportunity to choose between selecting an existing database, for example one from a previous installation, or creating a new one. Choose your option by selecting one of the radio buttons shown for every opportunity. Select existing database: Within this option you will get a list of all existing databases in a dropdown menu. Choose the database of your choice and click the button Next Step. Create new database: Insert a name for the database, which will be created, and define a database path, where the created database files will be stored. Take care for the correct permission rights of the defined folder. In Windows Vista it might be advisable to create the folder before, defining the specific folder permissions inside the folder properties dialog manually. After entering the data click the button Next Step.
Step 3 Various settings File storage: In the field base directory enter the path to the directory, where the objects and contents of the collaborator will be stored. Ensure that this directory is having the correct access permissions. Note: The base directory is usually automatically created as entered by path statement. Since Windows Vista works restricted by user access control it is not possible to create that directory automatically. You have to create the directory manually with the windows explorer before. As created, please check folder permission for operating smoothly. Mail server: Specify the address of the mail server to use in field SMTP Server. Usually this address is composed of server name and domain name, like servername.domainname.de. Enter a sender address registered on the mail server. This address is used for the mails which were generated by collaborator. This address is to be shown as sender of every automatic generated email.
Step 4 collaborator initialization Initial user: Specify login data for the first user profile in collaborator by entering the fields username and password. This user profile will get administrator permissions by default. Attention: Please note this data since the datango collaborator will become inaccessible without it. Initial Workarea: Specify the display name which will be shown in initial arranged Workarea. You should define a clear allocable short variant of that name, without spaces, in the field name (used in URLs), for example wa for Workarea. Specify the name of the root group in initial arranged Workarea by entering the field root group (display name).
Finish installation process The window Finished informs you about completion of the install process. Now you have the possibility to import existing user data or to configure the user authentification by single sign-on method. Please read the according chapters Import of user structures and Configuration of Single sign-on for further information. By clicking the button License Manager you will be forwarded to the license management. If you decide to do one of those optional configurations the License Manager will appear after first login.
License Manager The License Manager enables you to import your according license file to activate your specific components of the datango collaborator. Note: Without the implementation of a valid license file you are not able to access the datango collaborator. The License Manager will be loaded with every page request until you import a valid license file. Please do following steps to import your license file: 1. Click on button Add License.... 2. Click on now appearing button Choose file to open an explorer window for choosing file location and file itself. The license file has to be in format <filename>.licensedfeatures. 3. Choose specific file and click on button Open. 4. After short delay the page will be reloaded, now showing various informations as saved in the license file.
Note: If the information of the license file won t fit to your installation environment, the license will be shown in red letters, declared as invalid. Choose the invalid license in the dropdown in heading area to get all specifications listed in detail. At the top of the list you will get that specifications listed, which are not compatible with your environment. Please contact the datango support team with this information. 5. Click the button collaborator to get back to main interface of datango collaborator. Now the login view of the datango collaborator will appear. Please enter the username and password as set in section Initial User of installation step 4 to logon as administrator. After confirmation of entered data you will now initially see the interface of the datango collaborator.
Single sign-on Interacting with a network inbound Active Directory server the datango collaborator gives you the possibilty to enable Single sign-on login for your users. Thus your users don t have to enter login data when they request the datango collaborator but will have direct access to their specific areas as they are logged in automatically at request. Attention: The start of navigations (*.dnt) located on datango collaborator will not operate by use of Single sign-on and Internet Explorer 6 due to technical restrictions of the browser. Setup To setup server sided Single sign-on in your datango collaborator installation please do as described in following steps: 1. Create an user account in Active Directory (LDAP). The account should be created at the top level domain server which contains the global catalog and has to be named different than the hostname of the server which will be used for datango collaborator installation. 2. Open command panel of the Active Directory server and enter command strings as following, whereas you have to replace the red highlighted placeholders with your specific values. This command will create the keytab file as necessary for functionality. To specify an output path please enter path additionally to the filename at parameter /out. Without specification of an output path the file will be created in recent directory of command panel. ktpass /pass <password> /mapuser <username> /princ HTTP/<coll_hostname>@<DOMAIN> /ptype KRB5_NT_PRINCIPAL /Target <DOMAIN> ktpass /out <coll.http.keytab> /princ HTTP/<username>@<DOMAIN> /ptype KRB5_NT_PRINCIPAL /Target <DOMAIN> /pass <password> /mapuser <username> *placeholders shown uppercase have to be defined uppercase as well
Note: Kerberos ktpass is not native part of Windows Server 2000 and Enduser Operating Systems like XP or Vista. You will have to install additionally the ktpass utilities from installation medium. 3. Store the keytab file in an arbitrary location on your collaborator server (e.g.: C:\collaborator\collaboratorpc.HTTP.keytab). Please avoid to store the file in webapps folder, since it will be deleted there while updating the application. 4. Now enter specific values to the Single sign-on configuration in the installation wizard of datango collaborator. These will be explained in following table. 1 If you are already running a Kerberos service in your network, controlled by a config file, please enter the path to the config file. In this case you won t have to enter values in fields 5 and 6. Read more about using krb5.config file here: http://java.sun.com/j2se/1.5.0/docs/guide/security/jgss/tutorials/k erberosreq.html 2* Enter service authentification with complete server and domain name of the collaborator servers, e.g. http/collaboratorpc.mycompany.com@mycompany.com 3* Enter path to keytab file as stored in step 3. Please use / as path
separator. 4 Specify if client tickets, as they will be created at user logon, shall be stored in server cache. 5* Enter the host name of the Active Directory server, e.g. master. 6* Enter your domain, e.g. mydomain.com 5. Now click on button <Save and go on> to save entered data and switch to configuration of the LDAP server. Please read chapter Import from a LDAP structure for further information. Note: Kerberos based Single sign-on doesn t work by requesting localhost. You have to request your instance of datango collaborator from another workstation to get Single sign-on functionality. Settings for Mozilla Firefox Enter about:config in the address bar to call the advanced browser configuration. Filter for the option network.negotiate-auth.trusted-uris and enter the name of server or server domain as value. Settings for Internet Explorer Open browser settings dialog by Tools > Internet Options and configure options as following: 1. Go to tab Advanced. Turn on the option Enable Integrated Windows Authentification* in section Security. 2. Go to tab Security and click on Local intranet. Click on button Custom level and set option Automatic logon in Intranet zone which is located in section User Authentication > Logon. Close window by clicking the button OK. 3. Click on button Sites and in next step on button Advanced in appearing dialog. Enter IP address or hostname of datango collaborator server into the field on top and click Add. If there is some network policy preventing you to enter any data please contact your network administrator to ensure that IP address or hostname of server will be added to list.
Import of user structures With the datango collaborator you have the opportunity to import existing userdata. Just click on Administration in the menu of the datango collaborator and choose Server Import in the dropdown menu. The window for data import appears.
Import from an excel file To avoid the creation of users one by one, you have the option to import userlists by an excel file. You only have to take care of the correct syntax of the column identifiers, which have to be placed within the first row of the excel sheet. The order of the columns is irrelevant for that procedure. Use the identifiers in same syntax as follows: Identifier username password first name last name email position department parentdepartment country Description The username to login. Mandatory identifier. The password to login. The first name of the user. Mandatory identifier. The last Name of the user. Mandatory identifier. The mail address of the user. Mandatory identifier. This specifies the role of the user. It must be a toplevel role. It will be created automatically, if it is not existent by now. This defines the organizational unit, the user will be integrated into. The organizational unit will be created automatically, if it is not existent by now. This defines the parent organizational unit, the user will be integrated into. The organizational unit will be created automatically, if it is not existent by now. This defines the major organizational unit, the user will be integrated into. The organizational unit will be created automatically, if it is not existent by now. For the import of an excel file please click the button Browse. Choose your excel file in the explorer window, mark it and click Open.
The path to the excel file is now shown inside of the field location of file. Click the button Import. You can close the window as soon as the site has reloaded and the text loading has disappeared. Just click the button Close in the subnode return to collaborator.
Import from a LDAP structure Import LDAP Data enables you to import your existing data structure from a LADP server, displaying your whole organizational structure in the datango collaborator compliant to LDAP standards. Afterwards you just have to add the specific permissions for each unit. Read more in the online help of the datango collaborator. Enter the specific access data of your LDAP server into the fields and click the button Select. Note: The request for the LDAP server is done automatically on port 389. If you have defined another port for connecting your LDAP server, you have to specify this by adding a port appendix in field ldap server (myserver:123) After clicking Select a data structure mapping of the specified LDAP server will appear below the input fields. This mapping enables you to view all levels of the data structure by expanding specific entries by clicking on the arrow in front of the entry. Choose the entries to be imported by clicking onto. While holding the CTRL key you can do a multiple choice. Note: The root entry is not able to be choosen. Doing so will cause the button for processing to stay inactive. Note: Relating to the logic of LDAP it is not possible to choose ancillary entries as well as the superior entry of those. Doing so will cause the button for processing to stay inactive as well.
After choosing your data set(s) just click the button Import. The process is finished when the site has reloaded. The mask Import LDAP data is invisible now. Click the button Close in section return to collaborator to go back to the datango collaborator. You can update your data with that method at any time. To do so just click on the button Update (appears instead of Import after having done one import before) without selecting anything. Deletions within the LDAP structure are not adopted. Note: Adding further LDAP branches to the collaborator, take care to select the already imported branches as well. Otherwise the already imported user structures will become disabled.
Working with collaborator and producer With the datango collaborator you will have a worldwide accessible central Workarea, in which contents could be edited and updated with the datango producer easily. Read now, how you connect the datango producer with the datango collaborator. How to connect To connect the datango producer with the datango collaborator go to the project explorer view in the datango producer and choose Workarea -> Administration -> Connect with collaborator. The connection wizard appears, allowing you to input connection data necessary to connect to the server, which is running datango collaborator.
Step 1: Select Server Edit settings in dialog select server as following: URL: Enter the address of the server and the installation path of datango collaborator. It could be specified as an IP address or as a string, for example http://192.168.0.1 or http://www.domain.com. Extend the server address for the port as specified within installation process of tomcat. If you haven t done an extra specification, port number is 8080. User: Enter your user name. Password: Enter your password. Save password: Specifies, if your password should be saved locally. Click on Establish connection to check your entered data for validity. Note, that the button Next will stay inactive as long as haven t got a valid response from server.
If connection has been established successfully, you will get served informations about workarea, users and existing status shown in notification area below the button Establish connection. Click on button Next to go to next step. Step 2: Select workarea Click on dropdown button Workarea paths to get the list of existing workareas. Select your according workarea. After selection of workarea you will get informations about existing resources and tags listed in notification area. Based on this informations the connection wizard
is preselecting the option right below the notification area. Manipulate this options depending on your needs. 1. Use server root This option sets datango producer to use the root group of the collaborator even in your local workarea. Existing contents of your local workarea will be moved to group of Unreferenced entities. 2. Download resources If your are connecting to an already equipped collaborator, this option will download and use the resources existing on server. Existing resources of your local workarea will be overwritten. 3. Upload resources If you are connecting to a collaborator, which is not already equipped with resources or with elder resources, this option will upload your existing resources of your local workarea to the server. Click on button Next to go to next step.
Step 3: Personal group Within this step you can specify a personal group for your local workarea. This group will be uploaded to server while connecting and will be usable for editing contents directly after connection process. Click on Finish to finish process of connecting with collaborator. A dialog appears, showing you the status of content synchronization.
The progress dialog shows you informations and options as following: 1. Progress of entities Shows the particular entity with its informations and result of synchronization. 2. Show details Click on Show details to get detailed information on current marked entity, for example if the synchronization result shows an error. 3. Auto-close on success Select this option to make the dialog closing itself after succesful data transfer. If there are errors in transferring data the dialog will stay opened to show you the errors in transfer of entities. Click on the button Ok. The connection between the datango producer and the datango collaborator is ready now.
First Steps After having set the connection to the datango collaborator for first time, you are able to fill the central Workarea with content now or, if there are existing contents on the server yet, to download them into your local Workarea. For keeping overview even inside of very large structures, you are able to use a group inside your local structure as root. This root group enables you to load just that part from the central Workarea which is important to you. So the root group is to be understand as an entry point to the data structure on the server. In cause of that use the definition of a root group is essential for working together with datango collaborator. Select a group inside the tree view of the project explorer (in case you have a complete new generated Workarea this might be the group Content) and call the context menu by the right mouse button. Choose Group ops -> Set root. Load the preferred part of the central Workarea by choosing Central Workarea -> Check out Objects. A dialog appears, in which you can choose your preferred part by using checkboxes. Confirm your choice with the Ok button. A progress window will show you the status of the check out. After finalizing the check out procedure, you will find the downloaded part inside of the item Unreferenced Entities right at the bottom of the tree. Select the highest level object and drag it with the mouse onto the group, you had defined as root before. Now you may work with your projects as habitual.
Updating the datango collaborator In the event of a server installation file update being available for the datango collaborator you can install it using the settings and records of an already existing installation of the datango collaborator. Note: Please backup your database and the file structure of datango collaborator before processing the update. This enables you to rebuild your data in case of having trouble while updating. Proceed as follows to update an already existing installation: 1. In the already existing installation of the datango collaborator call the Server Install Page and note the following values: File Storage: The path specified in the Base directory. Database: The name specified under database name. 2. Launch the Tomcat server environment application manager by entering the following path in your browser's address bar: http://<server>:8080/manager/html 3. In the application list look for the entry corresponding to the existing installation of the datango collaborator. 4. Name the current installation file you have with the string shown in the path name (without the forward slash "/" at the beginning). 5. Return to the Tomcat manager application list and select the menu item Undeploy in the Commands column of the installation to be replaced. 6. Once you have reloaded the page, click on the Browse button from Deploy -> WAR file to deploy. 7. Select the installation file of the updated version of the datango collaborator and confirm the Open button. The path to the file is displayed in the input field. 8. Click on the Deploy button. The installation file is incorporated into the server environment. 9. Then click in the application list on the path of the incorporated file and enter in the authentication interrogation the user data you have for the Server Install Page. 10. Amend the server address under SQL Server Connection and input in File Storage -> base directory and in Database -> database name the values you noted down from the previous installation.
11. After successful loading of a licence key the database updater appears, since an older version of database structure was recognized. 12. Click on Update Database for initializing the database update. To verify your upcoming changes once again you will be informed about changes to do. Confirm the start of the update process by clicking Update Database once again. 13. After successful update you will read the version number as it is now valid for database. Click on Collaborator to call for the interface of datango collaborator. The updated version of the datango collaborator is now available to you under the same path and with the same volume of data as the previous installation. Attention: You have to restart the tomcat server after update has finished since some functions are still in server cache. This might produce malfunctions in updated collaborator.
Note for LDAP based user structures Up to datango collaborator 2010 version 8.0.0 build 865 Based on file structure the LDAP access data, as defined in previous version, will be deleted while updating to next version of datango collaborator. Although no imported users or relating structure dependencies will get lost, this will occur in unsuccesful login procedures for every user imported by LDAP caused by the missing connection data to the LDAP server for checking password validity. To solve this, the LDAP access data has to be specified again. Do as following to redefine the LDAP access data: 1. Choose entry Server Import in menu item Administration. 2. Enter authentification data as specified for Server Install Page into appearing authentification popup and proceed with clicking Ok button or ENTER key. 3. Enter your connection data to the LDAP server into the appearing form Import LDAP Data. 4. Click on button Save LDAP Access. 5. Click on button Close to return to datango collaborator. Validation of login information based by LDAP is now restored. Note: Due to a changed saving method there will be no more necessety do do this step when updating at least datango collaborator 2010 build 865 with a future version.
With datango collaborator 2010 and above version 8+ Based on structure reengineering the update of datango collaborator it s needed to import all LDAP structure data again. Please proceed the according steps as written in chapter Import from a LDAP structure. Note: Please consider that you will import all datasets from LDAP server that have been imported in previous installation. Otherwise those users from old structure not existing in new import will be deactivated.