User manual BUSINESS OBJECTS BUSINESSOBJECTS ENTERPRISE 6.5 FOR WINDOWS AND UNIX DIAGNOSTIC TOOLS GUIDE

[. . . ] Diagnostic Tools Guide BusinessObjects Enterprise 6. 5 Business Intelligence UNIX and Windows 2 Diagnostic Tools Guide Copyright Copyright © 2004 Business Objects. If you find any problems with this documentation, please report them to Business Objects S. A. Printed in France. Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners. [. . . ] Another way to check license files, on both UNIX and Windows platforms, is to read the readable XML files located in the license directory set during installation. Do not edit these files: as they are signed, any modification might corrupt them. When should I check my licensed Business Objects products? If you are unable to launch a Business Objects product, your license may have expired. Run wlicense in this case to see all the products for which you have a currently valid license. wlicense reference !Launching wlicense from the prompt wlicense is stored in the $INSTALLDIR/setup directory. However, you should log in as a user with rights to the web server and application server directories. Although they are not necessary for the installer, you need these rights when you run the Configuration Tool. You can run wlicense directly from the command line, by simply entering the command: wlicense There are no parameters. The screen displays the products for which you have a license, and expiry dates if applicable. Checking your license files with wlicense 32 Diagnostic Tools Guide Checking Business Objects software with WICheckInstall After installation, it's a good idea to verify that the installation was complete, and that your Business Objects system has all the elements it requires to run properly. Even once you're using the system, remember that all systems are subject to modifications from time to time. File systems and directories can be added or renamed, operating systems can be updated with patches, and files can be corrupted or accidentally deleted. Checking the version and availability of system libraries, the validity of the directory paths defined at the initial setup, and the integrity of the libraries and executables used by the Business Objects setup may help resolve some of the issues that occur at runtime. WICheckInstall verifies the contents of a Business Objects installation. During installation, winstall creates reference files that contain a list of all files that are installed. After scanning the installed files, WICheckInstall: · compares the installed files with the reference files and checks that no files are missing · checks that you have at least read access to all files and directories · checks that all files and directories belong to the user who is carrying out the installation · checks the size of each file At the end of the output, a summary section returns all the error messages displayed. By default, WICheckInstall generates a log file in the $INSTALLDIR/tools/log directory called WICheckInstall_<date>. log When should you use WICheckInstall? The main reason for running this tool is to make sure all critical files, such as executables and libraries, are in fact present on the machine. Therefore, run this tool in the following circumstances: · after installation, to make sure the installation was complete · after an update of either the operating system or a Business Objects product · if you receive error messages indicating that required files are missing Checking Installation and System Settings Diagnostic Tools Guide 33 WICheckInstall reference !Launching WICheckInstall from the prompt WICheckInstall is stored in the $INSTALLDIR/tools/bin directory. You can run WICheckInstall directly from the command line, using the following syntax: WICheckInstall [-help] [[-log <logFile>] | [-nolog]] Parameter Value -help -log Description Display online help. By default, WICheckInstall generates a log file in the $INSTALLDIR/tools/log directory called WICheckInstall_<date>. log N/A <logFile> -nolog N/A Do not generate log file. By default, this option is not active and a log file is created. Checking Business Objects software with WICheckInstall 34 Diagnostic Tools Guide Checking system settings with WICheckConfig WICheckConfig retrieves critical information about your system's setup, analyzes this information, and tells you whether its findings indicate there's a problem. · If its findings concerning a particular facet of your system's configuration are positive, it registers a message beginning with + Great!· If it discovers a problem with a particular part of your configuration, it produces an error message beginning with # Oops! [. . . ] Its default name is WIGetConfDmp_<Date>. tar. Z TIP If you decompress this tar file on a Windows machine using the WinZip facility, make sure you use the default options (it doesn't matter whether the Use folder names option is checked or not -- if it is and the folders do not exist, they will be created). Retrieving Information Diagnostic Tools Guide 63 WIGetConfDmp reference !Launching WIGetConfDmp from the prompt WIGetConfDmp is stored in the $INSTALLDIR/tools/bin directory. You can run WIGetConfDmp directly from the command line, using the following syntax: WIGetConfDmp [-help] [-all] [-tar <archiveFile>] Parameters Values -help -all Description Display online help. Include Business Objects temporary and log directories, and the log directories for your web and application servers. [. . . ]