Solved Problems in OnePoint Diagnostics 3.3.0001

1. When a proxy server was defined and active for the browser, remote server handling could fail due to internal OnePoint Diagnostics configuraton settings or due to firewall settings. All requests to and from a remote server are now handled internally by OnePoint Diagnostics not requiring any longer the proxy setting of the browser.
   
   
2. When a new portingset of ERP LN (formerly Baan) was installed, the associated OnePoint Diagnostics connector failed to connect which has been resolved.
   
   
3. The OnePoint Diagsnostics Informix connector would fail if the informixserver and informix client software would have been installed in different directories. It is now possible to define two different directories in the profile of the Informix connector.
   
   
4. The OnePoint Diagsnostics service on Windows systems could timeout during startup phase of the OnePoint Diagsnostics Portal; this was most likely to happen on slow systems. The service startup method has been changed in such a way that this timeout should no longer occur.
   
   
5. On slow systems, the internal test connection timeout value of 45 second has proven to be to low to finish completing the connection test. The internal timeout has been increased to a value of 120 seconds to solve this problem.
   
   
6. The digital signature for the Java classes will expire on May 27, 2006. A new digital signature will be available in the near future.