Click on the button below to download a tar-ball that contains all the client scripts. You will then need to untar it in a location of your choice. Please make sure you follow the instructions on this page to learn how to setup and configure these scripts.Download the DB2PRO Client Scripts (21 KB)
Setup Instructions - High Level
Free,Personal, Premium Plan Users
Business in AWS Cloud Plan
Business in-house Plan
|Install Cygwin||If you are running the scripts on Windows platform|
|Receive AWS Keys|
|Step 1: Un-tar download package|
|Step 2: Verify DB2 Client|
|Step 3: Setup DatabaseList.ini|
|Step 4: Setup Data Collection Scripts|
|Step 5: Setup Data Shipping Scripts|
|Step 6: Do a Test Run of Data Collection Scripts|
|Step 7: Launch Everything in Background|
|Step 8: Upload files manually|
All of our scripts are coded in bash and in order to run them in a Windows environment (for instance Windows 7) you will need to install Cygwin to emulate the script.
The installation is straight forward, the default selection will be good enough, but you also need to add the openssh module.
Business in AWS Cloud Plans
If you have a Business in AWS Cloud subscription, you can upload files manually via the upload page or automatically via a private key file. In this case, please contact us so that we can provide you with:
- A private key file that is used for sending files to AWS server, usually it will be called [your-company]_datacopyuser.pem
- The address of your AWS server, usually it will be in the form of [your-company].db2pro.com
You will need this in step 5.
If you are using our services on the Free Tier, you can only upload files manually via our upload page.
Step 1: Un-tar the download file
You will need to download the client package and un-tar it in your $HOME directory.
Note: the package will create these directories:
Step 2: Verify DB2 Client
Since you will be collecting data (from SYSIBMADM and SYSCAT schemas) via a database connection, you will need to make sure that your DB2 Client is properly configured with all the catalog entries to the databases from which you intent to connect to.
You can do this trivial test as follows.
Windows Users: Please use DB2 Command Window to do this test
This would insure not only you have the catalog entry properly configured, but also the userid that you are using to connect has enough privileges.
Step 3: Setup DatabaseList.ini (in db2pro/DataCollection Folder)
Edit a file called DatabaseList.ini and add your database information:
This file is used by the Data Collection Scripts to connect to the database and retrieve stats and meta data.
The <Hostname> and <DB2 Instance> don't serve any technical functionality, but they are used in the file names that are produced - and these are the values you will see in your dashboard on the db2pro site.
As well, <Hostname> cannot have dots. You can simply put an alias name or replace the dots with dashes.
Step 4: Setup Data Collection Scripts
You will see three Data Collection scripts which you can optionally edit and adjust what you like to collect.
For your reference, here is the content of these scripts:
Step 5: Setup the Data Shipping script
You will need to place the private key file in your db2pro/DataCollection folder.
Then you will need to edit the data shipping script and adjust two important parameters.
You MUST adjust these two lines:
Step 6 - Do a Test Run of Data Collection Scripts
At this point you, you need to make sure that all your .sh files have the execute bit turned on (chmod 755) and just execute it.
We suggest you start with Collect.DB2.Stats.hourly.sh first in foreground, and verify in the db2pro/DataCollection/data folder you see a file(s) created. These scripts are self scheduling so after they go through doing their work, they calculate how long they need to go to sleep so that they can run at a perfect interval. After your first test run, simply press Ctrl-C to stop the script.
You then try Collect.DB2.Stats.daily.sh and Collect.DB2.Stats.weekly.sh and verify some files have been created.
Last step is to try the Ship.DB2.Stats.to.db2pro.sh script which should send those files to AWS and remove them from your local directory.
Step 7 - Launch everything in background
Congratulations, all you have to do is to fire off these scripts in the background as follows:
Note: you can set
Step 8 - Upload files manually
At this point you will start seeing DB2PRO Packages on your machine. If you are using the Free, Personal or Premium plan, you can log in to our site, and upload these files using the "Upload Files" page.