Number: TB0011

Availability: As of BuildPro 8.00, all users.

Introduction

Access to BuildProfessional is controlled through a series of licenses. The licenses determine features like the number of users allowed to access BuildPro, expiry dates, platform, interfaces to databases etc. This document describes how to license or re-license you BuildPro installation.

About BuildPro Licenses

There are three different license types used in BuildProfessional; Repository, Extension and Developer. Each license consists of a 12-character License Key and 8-character Activation Key. All characters in the license are upper case and must be entered in upper case. There are no zero's in a license or activation key.

The License Key consists of 3 sets of four characters (letters and numbers) separated by a hyphen (-). Example: FEAF-TYED-GVXT

The Activation Key consists of 8 characters (letters and numbers). Example: DFELSWRE

The three license types are:

1. Repository (or Base). The Repository License is the main license and determines the platform and number of run time users allowed to access the BuildPro installation. The Repository License may contain an expiry date. The License Key portion of the Repository License is displayed under the About BuildPro screen accessible from the Help pulldown menu.
    
2. Extension. Extension licenses control access to BuildPro features like database interfaces, client/server options etc. Before installing a license, make sure you have the correct extension features.
    
3. Developer. The Developer license controls access to the development environment and determines the numbers of developer users.

A runtime (end-user) site will receive a Repository and an Extension License. A developer site will receive Repository, Extension and Developer licenses. If you are licensed to use BuildPro on several platforms, you will receive licenses for each platform.

Licenses are "targeted" together and cannot be interchanged.

Licensing BuildProfessional

Licenses are applied to both the BuildPro Repository (sfiles) and the executable files. Depending on your configuration you may be required to re-license BuildPro after your initial installation. The licensing procedure is slightly different on Windows and Linux platforms. The below examples show you how to quickly re-license a BuildPro installation.

Licensing BuildPro under Windows

The simplest way to license or re-license your BuildPro installation under Windows is to use the License Manager in the BuildPro Server short-cuts directory.

If you have to re-license many different installations it can be useful to embed the licenses into the License Manager command line. This way you can store your licenses. Create a short using the following command line:

C:\BuildPro\bin\brandv3.exe -f "c:\buildpro\BIN\wintdyx.exe" -b AAAA-AAAA-AAAA/AAAAAAAA -e BBBB-BBBB-BBBB/BBBBBBBB -d DDDD-DDDD-DDDD-DDDD

where:

C:\BuildPro is your installation directory

AAAA-AAAA-AAAA/AAAAAAAA is your Repository license and activation key

BBBB-BBBB-BBBB/BBBBBBBB is your Extension license and activation key

DDDD-DDDD-DDDD/DDDDDDDD is your Developer license and activation key

After creating the short-cut with embedded licenses, you can re-license your installation by simply clicking on the new shortcut.
 

Licensing BuildPro under Linux

Under Linux it is neccessary to re-license executable files after re-linking or moving to a different database. It is therefore very convenient to store your licenses in a shell script.

To license a BuildProfessional installation, create a shell script file as follows:

#Brand the executables:
../install/brandv3c -a todayx -b AAAA-AAAA-AAAA/AAAAAAAA -e BBBB-BBBB-BBBB/BBBBBBBB

../install/brandv3c -a todays -b AAAA-AAAA-AAAA/AAAAAAAA -e BBBB-BBBB-BBBB/BBBBBBBB
../install/brandv3c -a sessmgr -b AAAA-AAAA-AAAA/AAAAAAAA -e BBBB-BBBB-BBBB/BBBBBBBB
../install/brandv3c -a fbuild -b AAAA-AAAA-AAAA/AAAAAAAA -e BBBB-BBBB-BBBB/BBBBBBBB

#License the Repository (sfiles)
./userinit -lDDDD-DDDD-DDDD/DDDDDDDD
./userinit -avision -lDDDD-DDDD-DDDD/DDDDDDDD

Run the script from your BuildPro bin directory.

Before re-licensing make sure no users are running BuildProfessional and the Session Manager is killed.