New Features in OnePoint Diagnostics 3.3

1. Unicode Support
   This version of OnePoint Diagnostics is Unicode enabled; it now supports storage of multi-byte data (like Japanese and Chinese texts) in the output containers. The XML output generated by the portal is now in UTF-8 format. Whenever possible the conversion to UTF-8 format is done by the application/database. This is most likely the case for the newer versions of the application/database. If the application/database is not capable of converting the data to UTF-8 format, the portal will try to perform the conversion to UTF-8 format.
   
   
2. Additional Questions
   
   • Many questions for Infor ERP LX (aka BPCS) are added. These questions are primarily relevant to OnePoint Diagnostics on an OS/400 server.
   • 42 compatible BaanERP 5.0c questions are now also activated for BaanERP 5.2a and ERP LN 6.1.
   
   
3. Migrate Run-time Files during Installation
   It is now possible during installation of a new OnePoint Diagnostics kit to include the configuration and run-time files of an older installation. When this old installation directory is specified, all relevant files are copied to the new installation directory as final step. The big advantage is that an already existing view will be available directly when using the new installation without additional effort.
   
   
4. Saved Tree View
   The tree view of each user always was saved in a binary (Java dictated) format. A drawback of this method was that the tree view had to be reconstructed manually when a (major) change in one of the internal Java classes was necessary.
   Starting with OnePoint Diagnostics 3.3 the tree view is also saved in XML format which allows reconstructing the tree view even when the Java classes are changed.



5. Dump Server Files for Debug
   In order to simplify the procedure to collect debug information (as sometimes requested by OnePoint Diagnostics experts) to understand and solve a problem, a new feature is prepared. This feature is available from the File menu in the portal when specific objects in the tree are selected being:
   
   
   • The top of the tree i.e., the OnePoint Diagnostics node
   • Each remote server (i.e., a Remote Server node in folder Remote Servers) provided the selected remote server is in the connected state.
   
   When one of these nodes is selected, the File menu will show the option “Dump Server Files”. When this option is chosen, files on the involved server are collected and stored in a container on the selected server. When ready, you will be prompted to download this container. Finally, when requested by a OnePoint Diagnostics expert, the downloaded file can be mailed possibly after compressing it. The server files are selected according to the following pattern:
   
   
   • If the file profiles//dumpfiles.txt on the target server is existing, it is used as input. This file is user specific and hence the content can vary per user.
   • When the above mentioned file is not existing or empty, the file dumpfiles.txt on the target server will be used instead. This file is common to all users.
   • When according to the above rules no file is found or only empty files, a minimum set of interesting files is selected by default on the target server being config.txt, enabled.txt and version.txt.
   
   The file profiles//dumpfiles.txt or dumpfiles.txt is not installed as part of a regular installation. Either the file needs to be manually created upon request or is sent to you by a OnePoint Diagnostics expert. Simply install this file according the instructions and execute the “Dump Server Files” command. The content of the input file for the debug feature is a text file containing one file name per line. When a file name is specified that doesn’t exist, the non-existing file is silently ignored. When an input line specifies a directory, all regular files in that directory are selected as target. Note that this procedure is only single level. In other words: when a directory search finds another directory, this next level directory is skipped. When Java logging is active, the skipped files or directories are listed in the Java logging.