CmapServer Release Notes

CmapServer v6.04.01 - July 24, 2015
  • Minor update to provide support for installation under Windows 10.
CmapServer v6.04 - June 22, 2015
  • Added LDAP debug logging, enabled via config parameter "ldap.user.directory.debug=true" in serverconfig.txt.
  • On OS X, the “CmapServer.app” and “AdminTool.app” are used for launching the CmapServer. “LaunchCmapServer” and “LaunchAdminTool” are not used anymore.
  • For CmapServers using an LDAP server, fixed a bug where userDN lookups would fail after the LDAP server became unavailable due to high demand; now continues to try userDN lookups if they ever succeeded in the past.
  • Fixed bug where renaming files would fail if only changing the case.
  • Many additional bug fixes...
CmapServer v6.00.07 - January 7, 2015
  • All CmapServers now include Java 7 as part of the Install program.
  • Many fixes to better support SSL mode.
  • The HTTP-protocol for client interaction has been completed, allowing a client to perform all transactions with the CmapServer through HTTP.
  • SLP now supports setting "secureMode" via the property "net.slp.secureMode" in slp.conf.
  • HTTP-sockets protocol now works when the CmapServer is configured to use HTTPS (secure sockets).
  • The CmapServer now supports interaction with the Cmap Cloud (not available in downloadable version).
CmapServer v5.05 - January 24, 2014
  • Added support for instalation in the latest platforms: Windows 8.1, Windows Server 2012 R2 , Mac OS X Mavericks (10.9), Red Hat Enterprise Linux 6.4 (desktop and server editions; x86 and x64), SUSE Linux 10 (x86), OpenSUSE Linux 11.2, 11.3, 11.4, 12.1, 12.2, and 12.3 (x86 and x64), SUSE Linux Enterprise 11 SP2 (x64), Ubuntu 13.04 (desktop and server editions; x86 and x64), Fedora 18 and 19 (desktop and server editions; x86 and x64).
  • Fixed a bug that would cause the CmapServerer to deny synchronous collaboration on a Cmap.
  • Added the parameter: "collaboration.max.clients" in the CmapServer configuration file, and code to limit number of collaboration clients (defaults to 80% max number of server's concurrent client limit).
  • Increased the default value of “concurrent.client.limit" from 30 to 100 in the CmapServer configuration file.
  • Fixed a Cmap backward compatibility problem by adding code for handling the reading of ImageIcon objects that were serialized with Java 1.5 and cannot be read with Java 1.6. 
  • Upgraded Embedded Tomcat webserver to Tomcat 6.
  • Fixed a bug that prevented mp3 files from being played in Chrome.
  • Fixed drag & drop of URLs from Chrome and IE9 onto concepts.
  • To fix the limited memory available to the Windows version, the installers for Windows (32/64 bits) are now using Oracle JRockit 160_31 R28 VM instead of JVM SE. 1.5.0_17.
  • Fixed a bug when renaming resources.
  • Fixed a bug that deleted the last commit to a Discussion Thread.
  • Signifcantly improved the speed of reading and saving of Cmaps.
  • Overall improvement in the handling of CXL versions of Cmaps.
CmapServer v5.04.03 - May 14, 2011
  • New configuration parameters to send email notifications to the CmapSever administrators and to users requesting their password on a folder.
  • Fixed the email notifications problem that prevented emails to be sent by the CmapServer.
  • Fixed problems when saving Cmaps in the CXL format when the CmapServer is configured to save Cmaps as CXL by default.
  • Updated the Installer for the Mac version, now the CmapServer will run as a 64-bit application and does not require Rosetta to install.
  • Updated and extended the http-based API for communications of other programs with the CmapServer.
CmapServer v5.04.02 - November 4, 2010
  • Fixed a problem where some earlier releases of CmapServers would not be accessible by CmapTools clients because of a problem with scopes (groups).
CmapServer v5.04.01 - November 3, 2010
  • Fixed the problem that caused some CmapServers to not register with the Directory of Places, and therefore not appear in the Views in CmapTools.
  • Fixed the problem whereby connections to an LDAP server were kept open indefinitely.
  • Fixed the problem when handling anonymous users with Active Directory that cased the error code DSID-0C0906DD.
  • Fixed the problem where the log files were truncated when running a CmapServer under Java 1.6 (which is the case for updated Mac OS X machines).
  • Fixed the "Check for Update" incompatibility caused by recent update of OS X from Apple.
CmapServer v5.04 - July 16, 2010
  • Fixed the problem where, on a server with more than one ethernet port, if the CmapServer is configured to bind to one port in particular, the http-sockets protocol (which is used if port 4447 or whatever is used to communicate between client and server is not accessible) will fail.
  • Updated and extended the http-based API for communications of other programs with the CmapServer.
  • If a Cmap is saved on a CmapServer, and it doesn't include an HTML component (the Web version of the Cmap), the html is now generated by the CmapServer. This allows for the automatic generation of HTML when a program other than CmapTools stores Cmaps in a CmapServer.
  • Fixed a problem with Thumbnails being generated with "noise" when using OS X Snow Leopard in its latet releases.
CmapServer v5.03.03 – Oct 15, 2009
  • This version fixes the bad webserver (Tomcat) configuration file web.xml which was distributed in the previous version.
CmapServer v5.03.02 – July 29, 2009
  • This version fixes the Silent Installation Mode. Now you can install a CmapServer in Silent Mode using the properties file: CmapServerv5.03.02.properties.
  • Now when you install a CmapServer and select Connection Mode: SSL, you can specify the SSL keystore and SSL Keystore password.
  • Fixed a bug that allwows the specification of the CA cerftificate from a File when installing the CmapServer in Console Mode.
  • WebServices now fully supports the xml version of alias-resource and acl-info.
CmapServer v5.03.01 - June 5, 2009
  • This version fixes a bug in the Webservices whereby when creating a folder in the CmapServer, the folder was being created with a duplicate name.
  • Fixed bug where DoP log files could not be retrieved using the AdminTool.
CmapServer v5.03- May 19, 2009
  • A new URL format for Cmaps has been implemented. The new short URL format provides at least two benefits over the previous URL format, which produced URLs that were quite a bit longer than the new ones:
    1. The new URLs will fit more easily into an email message.
    2. The URL now contains the name of the resource to which it refers.
  • Now CmapServer automatically generates the Thumbnails view for all the resources stored in the server.
  • Now the CmapServer is a Proxy DoP, which means that clients in the same network can now detect the Proxy DoP by broadcast allowing them to know what other Places are available in the world, without having to contact the DoP directly.
  • The WebServices have been improved: it is now possible to change or add permissions to existing folders.
  • A 64-bit architecture of the CmapServer distribution is now available for Windows and Linux operating systems.
  • The Concept Map search mechanism makes use of the topological taxonomy of the Cmaps to rank the search results.
CmapServer v4.18 June 09, 2008
  • Fixed the problem with the Internet Explorer not being able to handle the no-cache parameter of the CmapServer servlet.
Note: CmapServer v4.17 was an internal version that was not publicly released.
CmapServer v4.16 - March 11, 2007
  • Fixed a bug in the LDAP implementation. CmapServer now allows a null value for the groupBaseDN parameter, since it is no longer required by LDAPUserDirectory.
Note: CmapServer v4.15 was an internal version that was not publicly released.
CmapServer v4.14 January 10, 2008
  • Added support to Create directory structures in a CmapServer using web services.
Note: CmapServer v4.13 was an internal version that was not publicly released.
CmapServer v4.12 - October 18, 2007
  • Multiple instances of the CmapServer can no longer run simultaneously on the same folder.
CmapServer v4.11 – July 06, 2007
  • Those server admins who have installed the CmapServer on a newer version of Linux such as Kubuntu 7.04 or Fedora Core 5 will now no longer experience C library errors due to an incompatibility with a third-party launch script when trying to update their server to a future version using the “update” application.
  • When performing a “reinstall” of the v4.10 CmapServer on top of an existing installation of the CmapServer on Windows, the new “serverconfig.txt” and “slp.conf” files that get created no longer have the possibility of disappearing after rebooting the machine.  This would rarely occur in v4.10 and earlier servers.
  • Now soups will appear as expected in the “Select Soup to Join” search window, regardless of whether or not the CmapServer that is storing a particular soup is registered with the IndexServer.
  • Now when a CmapServer is configured to use an Active Directory server for use with the LDAP permissions scheme, binding and authentication works as expected for users.  CmapServer compliance with Active Directory LDAP groups is still being developed.
  • Now third-party SSL certificates may be used in conjunction with the CmapServer's bundled Web server.  For more information on how to make use of this new feature, please visit the following entry in the FAQs (http://cmap.ihmc.us/Support/FAQs.php): "Q. Can I install a third-party SSL certificate, such as one by Thawte or Verisign, into the bundled Web server that comes with the CmapServer..."
  • Now the bundled Web server that comes with the CmapServer is set to enable Web clients to cache elements of the pages served up by the Web server that do not change when browsing the table of contents, Cmaps, etc., so long as the Web client is configured to handle caching.
CmapServer v4.10 – May 09, 2007
  • Now using any version of CmapTools, when clicking a resource link to a Cmap or resource stored in a folder that is either no longer present in it's original location or no longer exists after the time the resource link was made, the server sends the client an "Error Opening Resource" dialog instead of being prompted for credentials.  Consequently when viewing the web version of the Cmap users also now get a 404 "Page Not Found" error, as expected.
  • Now when you choose to make use of audit mode and adjust some of the audit mode parameters during installation, the configuration for audit mode that you supplied will be present in the serverconfig.txt file as expected.
  • Now the audit mode on the CmapServer will record read requests for Cmaps that are viewed as a Web page in a browser.
  • Now when the CmapServer is launched using any of the three permission schemes: Standard, LDAP-only, and "both" ...the values for "admin.password=", "root.folder.password=", and "ldap.root.folder.password=" will all be encrypted.
  • Now the CmapServer will install and run on Windows Vista as expected.
  • Now Safari on Mac OS X prompts the user for credentials for the Web version of Cmaps and resources stored in a locked-down folder in a Place, as expected.
  • When a non-root user tries to run the CmapServer on Linux and the bundled Web server is set to run on port 80, the CmapServer will now fail to launch and instead it will inform the admin via email that the server failed to launch due to insufficient privileges in accessing port 80 prohibiting the launch of the Web server.
CmapServer v4.09 – January 02, 2007
  • Now when CmapTools users access folders that are stored in a v4.09 CmapServer, if a folder contains anything and the user refreshes the list of contents of the parent folder or the server root, the ‘+’ symbol that is next to the folder will still be present.
  • Now when the network becomes disconnected for a CmapTools user before or during a move to/from a CmapServer, the Java Bug Report form no longer appears and instead an informative error dialog is displayed to the user.
CmapServer v4.08 – November 30, 2006:
  • The CmapServer is now able to make use of the LDAP permissions scheme in LDAP-only mode or LDAP plus standard permissions (mixed mode).  Now when authorized CmapTools users access an LDAP-enabled CmapServer, they can add LDAP “Users” and “Groups” to the permissions lists of folders that they create either manually or by searching the LDAP directory.  For more information on how to install and configure the CmapServer to use LDAP, please visit the LDAP documentation for both CmapTools and the CmapServer here:

    Managing Users Through LDAP

  • Now the CmapServer comes bundled with the Tomcat web server to serve up Cmaps and resources to users who browse a CmapServer via their web browser.  Opening very large Cmaps and resources stored in a CmapServer no longer fail to open in a browser due to socket timeouts on the web server.
  • Now when a user wishes to display a Cmap or resource by browsing a CmapServer via a web browser, resource allocation has been improved in the CmapServer's web servlet to handle these requests more efficiently.
  • The CmapServer admin may now choose whether or not the serverRootFolder Table of Contents (TOC) should be cached as a user browses their CmapServer via the web by specifying a value for the "cache.root.folder.toc=" parameter in the serverconfig.txt file.  Caching is recommended, especially for servers with a large serverRootFolder TOC.  The value for the parameter is set to "true" by default.
  • When a user has a lock on a Cmap stored in a CmapServer and the connection was severed between the user's CmapTools client and the CmapServer, the behavior of the CmapServer in the following scenario has been improved:
  • The user closes out of the Cmap without saving.
  • The connection between the user's client and the server is reestablished.
  • The user opens the same Cmap back up and obtains lock on it.

Now the CmapServer is informed that the previous user has reestablished a lock on the Cmap.  As a result, any other user who has priviledges to modify the Cmap and attempts to do so will be prompted for synchronous collaboration as expected.

  • If an unfortunate incident arises and a Cmap that is stored in a CmapServer somehow becomes corrupted, the user now has the ability to immediately delete the Cmap whereas before if the corrupted Cmap was able to be deleted, one would have to wait at least four minutes to delete the corrupted Cmap.
  • The CmapServer has a new improvement that speeds up a CmapTools user's access time of CmapServers containing many folders, Cmaps, and resources, given that the user has a reliable Internet connection.
  • An enhancement was implemented to make indexing that the CmapServer regularly performs on its folders, Cmaps, and resources more efficient.
  • For those v4.08 CmapServers that register with the public IndexServer, an enhancement was implemented that extends the caching ability of the IndexServer, thus improving the speed that CmapTools users will receive search results with v4.08 CmapServers.
  • If the serverconfig.txt file is missing from a v4.08 CmapServer installation, the server will now report a meaningful error message in the cmapserver0.log that includes the absolute path where the CmapServer is trying to locate the file, then the server will fail to launch.
CmapServer v4.07 – October 10, 2006:

  • The CmapServer’s program now uses the "My Places/All Places" model for the Places view. Added the server's version as a column in the main table. Fixed tooltip messages for the status icon.  Added a popup menu for the Places and DoPs table.
  • Now the CmapServer’s AdminTool table sorting defaults to alphabetizing Places names, and hostnames for DoPs, in ascending order.
  • When a user shuts down a CmapServer via the AdminTool, the list of Places in the AdminTool now refresh to indicate the server has been shut down.
  • Now the HTML Charset has been changed from ISO-8859-1 to UTF-8 to allow the proper display of Asian characters for the titles of Cmaps, resources, and folders when viewing the contents of a Place in a web browser.
  • Fixed a bug where a PKI-enabled CmapServer could not talk to another PKI enabled server (such as the IndexServer).
  • Made changes in order to enable/disable the webserver's logger via the CmapServer's configuration.  Added the configurable parameter: webserver.logging.enabled=false …to the serverconfig.txt file.
  • Now when a non-admin of a folder or Place has only “view” and “annotate” permissions, Cmaps may be safely saved and reopened without becoming corrupt.
  • Fixed the "move resource" functionality.  Now the permissions scheme clearly handles the "move a folder" and "move a resource" actions separately.