Installation
From SQLBWiki
Contents |
[edit] Prerequisites
SQLBrowser runs on a Windows XP Client connecting to Sybase ASE 12.5 to 15 data servers with Java 1.6_07+ installed.
Important For best results, we generally recommend to upgrade to the latest JRE
[edit] Installation
Although this will come some day, SQLBrowser currently does not have an installer. The distribution is a zip file that you have to unzip. Please follow the current instructions for installation:
Important If you want to install a shared version of SQLBrowser (recommended, please go this section)
- Install JRE 1.6 or JDK 1.6 which you can find here
- Download the zip file and unzip it in a directory, e.g. 'c:\Program Files'. We will further refer to this installation directory as the <installdir>
- This will create a version specific directory, e.g. 'C:\Program Files\sqlbrowser_Jun08_222_Official'
- You can create a cmd file launching <installdir>\bin\sqlbrowser.exe, sqlbrowser.cmd is in the bin directory as an example
- In case of JDK version problems (this can happen depending on order of JDK/JRE installations or if an older JDK is installed after the 1.6), add an argument to the command line to specify the jdkhome like for example:
<installdir>\bin\sqlbrowser.exe --jdkhome "C:\Program Files\Java\jre1.6.0"
- To add more memory (for batch analysis for instance), add -J-Xmx400m -J-Xms64m to the command line
- For more informatin, go to the Command Line section.
- For the first start, please read the Getting Started section.
[edit] Sybase ini File
- The Sybase ini file is necessary To SQLBrowser.
- The Sybase ini file is part of your Sybase open-client software.
- It is normally located in C:\sybase\ini.
- It contains the definitions (host port) of your servers.
- Generally, people interested in using SQLBrowser have Sybase Open Client installed.
- Please install Sybase Open Client software to get this file or get a copy an ini file describing the servers you wish to analyze.
- SQLBrowser does not otherwise require any other Sybase file than the Sybase ini file.
- Set up the path to the ini File in SQLBrowser Options.
[edit] Network Installation and Preferences
- It is advised to install SQLBrowser in a directory located on a network drive shared by users:
- All users use the same version of SQLBrowser. Version upgrades are done only in one place
- User can share preferences, such as the registration key. Make sure your organisation is registered for the effective number of users.
- Create a sqlbrowser.cmd file in a network drive as described above with the desired amount of memory and possibly the correct JDK shared path
- Have people using shortcuts pointing to this cmd file
- To share preferences simply supply an argument file containing these preferences. See the Command Line section for the argument file description
- This is the comments section extracted from the file <sqlbrowser>\bin\sqlbrowser_shared.cmd. It is always more accurate in this file but is copied here for reference
REM ********************************** REM NETWORK INSTALLATION OF SQLBROWSER REM ********************************** REM REM *** PRINCIPLE ************************************************************** REM The idea is that end-user just have to copy paste a shortcut on their desktop REM End-users only have to make sure they have the correct version of JAVA installed REM REM Centralizing the installation allows the sqlbrowser administrator to: REM * upgrade the version for all users in one go REM * share the license REM * share other common setup (server definitions, defects,..) REM REM When a new version of sqlbrowser is available, the sqlbrowser admin just has to: REM * unpack in the shared drive REM * edit the sqlbrowser_version.cmd script REM REM When willing to change some common setup: REM * edit the arguments.xml file REM REM *** INSTALLATION INSTRUCTIONS (please follow carefully) ******************** REM 1) choose a shared drive which will contain the sqlbrowser distributions. REM we will assume that for example this directory is: REM S:\SQLBROWSER REM REM 2) download and unpack an sqlbrowser zip file directly to this shared drive REM for example <SD> will now contain the directory: REM S:\SQLBROWSER\sqlbrowser_Dev_592_Beta REM REM 3) copy the 3 following files 2 levels up (ie in the S:\SQLBROWSER directory): REM S:\SQLBROWSER\sqlbrowser_Dev_592_Beta\bin\sqlbrowser_version.cmd REM S:\SQLBROWSER\sqlbrowser_Dev_592_Beta\bin\sqlbrowser_shared.cmd REM S:\SQLBROWSER\sqlbrowser_Dev_592_Beta\bin\sb32.ico REM S:\SQLBROWSER will now contain: REM S:\SQLBROWSER\sqlbrowser_Dev_592_Beta REM S:\SQLBROWSER\sb32.ico REM S:\SQLBROWSER\sqlbrowser_shared.cmd REM S:\SQLBROWSER\sqlbrowser_version.cmd REM REM 4) create the PROD shortcut with windows menu REM - click on S:\SQLBROWSER\sqlbrowser_shared.cmd REM - right click and choose 'Create Shortcut' REM - rename this shortcut to 'sqlbrowser_shared_prod.cmd' REM - right click the shortcut and choose 'Properties' REM - add the parameter PROD at the end of the target field REM - click enter to validate REM - when you edit the properties, the shortcut target should now contain: REM S:\SQLBROWSER\sqlbrowser_shared.cmd PROD REM REM 5) repeat step 4) but use BETA instead of PROD REM S:\SQLBROWSER will now contain: REM S:\SQLBROWSER\sqlbrowser_shared_beta.cmd.lnk REM S:\SQLBROWSER\sqlbrowser_Dev_592_Beta REM S:\SQLBROWSER\sb32.ico REM S:\SQLBROWSER\sqlbrowser_shared.cmd REM S:\SQLBROWSER\sqlbrowser_version.cmd REM S:\SQLBROWSER\sqlbrowser_shared_prod.cmd.lnk REM REM 6) SQLBROWSER ICON REM point the icon of the shotrcut(s) to sb32.ico REM REM 7) edit the sqlbrowser_version.cmd file REM open the sqlbrowser_version.cmd and change the BETA & PROD version REM to point to the pure name of the distribution dirctory (not the fullname) REM for example: REM set SQLBROWSER_VERSION=sqlbrowser_Feb10_515_Release REM or REM set SQLBROWSER_VERSION=sqlbrowser_Dev_593_Beta REM both BETA & PROD versions can point to the same name REM REM 8) Users just have to copy one (or the 2) link(s) to their desktop REM REM *** USER DIR *************************************************************** REM it is assumed that the user directory is in C:\temp\SqlbrowserUserDir REM this setting is very convenient because it is the same for every user. REM (to reclaim settings from a previous installation, REM copy the old user dir in this directory when sqlbrowser is not running) REM REM *** DESCRIPTION OF THIS CMD ************************************************ REM * copies sqlbrowser directory on the C: drive (the first time) REM * always copies latest version of arguments.xml REM * starts sqlbrowser REM * the arg to this script is either PROC or BETA which allows for certain REM users to test a beta version of sqlbrowser while regular users REM still use the PRODversion REM REM *** RATIONALE FOR COPYING TO THE LOCAL DRIVE ******************************* REM launching a java program from a local drive is always faster than launching REM from a shared drive because of java expensive class loading mechanism REM REM *** LOCAL ACCESS *********************************************************** REM When in need to run sqlbrowser when access to shared drive is impossible REM just have the user create shortcut(s) to the command(s) located REM in the C:\TEMP directory. This will bypass the test on the shared drive
[edit] Internet Proxy
- SQLBrowser can check for updates on the internet. To switch this option on or off do the following:
- Go in "Tools" / "Plugins" / "Settings" and Select the Check Interval you need. Select "Never" to bypass update checks
- Go in "Options" / "SQLBrowser" / "Proxy" / "Check For Updates At Startup" and tick or untick the checkbox
- If you turn update checks on and your require a proxy, please set up the proxy accordingly in "Options" / "General". If your proxy requires authentication, you can provide the credentials in this panel
