License Key Installation for Evaluations
Note: There is a known bug with SGI evaluations of Builder Xcessory that is fixed in the next release. For now, if you are evaluating Builder Xcessory on SGI, please see the question: Why does my BX Evaluation on SGI always start up in Demo mode? and then proceed with step #3 below.

Full operation of a BX PRO evaluation requires the installation of two evaluation license keys: one for Builder Xcessory and one for the bundled libraries (EPak and ViewKit). You should have received a separate email with both keys. If you did not, you can request another evaluation key at . The following instructions will help you properly install the keys.

Start BX by typing the following at the shell prompt:
% bx
BX will startup and ask you for a license key. Open up the email containing the key and copy-paste it into the text entry field. If you do not yet have your key, you can click Cancel and continue in "Demo Mode" (i.e., you cannot save any user interfaces). BX will keep asking you for the Key on every startup until you install a Key.
Note: The evaluation key format differs between Linux and UNIX. If you are installing a Linux evaluation key, it should look like (it is a single line, ignore any line breaks):

LICENSE BuilderXcessory (key)

And a UNIX evaluation key should look like (again a single line, ignore any line breaks):

FEATURE BuilderXcessory ICSBX 6.000 (Date) (#licenses) (key) "ICS Builder Xcessory" DEMO

Where (key), (Date), and (#licenses) are replaced by values appropriate for your environment. When asked to enter the Evaluation Key, enter the whole line starting with "LICENSE" for Linux and "FEATURE" for UNIX. It is highly recommended that you copy and paste the appropriate line from the email containing the key to avoid re-typing mistakes.

Note: The Builder Xcessory evaluation key is stored in a subdirectory of ~/.builderXcessory6. This means that every person evaluating Builder Xcessory must install this key through the dialog box mentioned above. You do not need to request additional evaluation keys. The one that you used will work for them too.

The EnhancementPak and ViewKit libraries included with the BX PRO eval, also require a key to run applications. You can build an application using EnhancementPak widgets or the ViewKit Library, and you can even generate code, compile it and link it. However, when you try to run your application, a Dialog Box will appear and a Key will be requested (both EnhancementPak and ViewKit are enabled by the same Key). If you don't enter a key, the application will be terminated.
Note: If you wish to avoid entering the EnhancementPak/ViewKit evaluation license key every time your run your test application, then simply make sure that the following commands are executed in the shell (or shell script) that runs your application:

For csh (and its variants):
% setenv ICS_EVAL_KEY (widget libraries evaluation key)

For sh (and its variants):
% export ICS_EVAL_KEY=(widget libraries evaluation key)

License Key Installation for Purchased Products
Since there is no license key for the bundled libraries (EnhancementPak and ViewKit), installing the license key for a purchased version of BX PRO can be easier than an evaluation version. Once you've installed the key for BX PRO, you're immediately operational. Before you start your installation, request your license key by visiting: BROKEN PAGE.

License key installation varies slightly depending on whether you are installing a Linux single user, a Linux server license, or a UNIX version of BX PRO:

Linux (single user): If you are the only user of the license, the installation of a permament license key for Linux is exactly the same process as that of the evaluation version. Start BX up and copy/paste key you received via email. If you have any questions, please review the prior section.
Linux (server install) You can share a license of BX PRO installed on a server among multiple users providing you do not have more simultaneous users than you have licenses. The recommended procedure in this case is to install a license in a common directory that is readable by all users and then have each user set the environment variable ICS_LICENSE_FILE to that directory (perhaps in their shell startup file.) If you have any questions, please review the question How can I put the license file somewhere else?.
UNIX: To receive the full benefit of the floating license for BX PRO, you will need to install the FlexLM license server. Please read Appendix C of the BX Reference Manual. This information is also available at: http://www.ics.com/files/docs/bx/6/BX60RefManual.pdf.
NOTE: It is important that you install BX PRO from the distribution media you received as the result of your purchase. The evaluation versions of BX PRO have a variety of limitations, the most obvious of which is that EPak and ViewKit require a license key. Simply delete the BX PRO home directory (typically under /opt) and reinstall the production version of BX PRO.

I installed the key as suggested, but upon startup BX tells me that the key it found is invalid. Did you send me a bad key?
Possibly, but not likely. Typically, a key is not recognized for one of the following reasons:

On UNIX, you have installed a BX 6 key and a BX 5 key is still in the FlexLM database. (See next question)
A UNIX key is used for Linux (or the opposite). Linux keys start off with the word "LICENSE" while UNIX keys start off with the word"FEATURE".
Some email readers wrap lines and only half the line gets pasted into the text field.
People try to rearrange a Linux key to look like the example UNIX key that the dialog box requests (This is a bug in BX 6.0. In BX 6.1, the example used for Linux will be a Linux key, and the example used for UNIX will be a UNIX key).
You have put the License file in a non-default location and have set the wrong environment variable. UNIX and Linux use different environment variables to specify the location of the license file. See the question How can I put the license file somewhere else? for details.
If all else fails, remove the .builderXcessory6 directory in the user's home directory and try starting bx again. (It stores the license key in a file in the .builderXcessory6 directory and if you have a bad key, it will generate the error message you received.)
I am upgrading from BX 3.5.1 for VMS/VAX to BX 5.0 on OpenVMS running on the Alpha hardware platform. How do I get the license loaded under OpenVMS?
I am able to register the license. However, when I try to load the license using the following command:
LIC LOAD BUILDERXCESSORY

I get the error
%LICENSE-W-WRGARCH, BUILDERXCESSORY license is not valid on this architecture

When you install BX5.0 VMS license key on a previously installed BX3.5.1 VMS license key, the above error message is generated. This is because it has the same product name as the earlier one. You need to delete BX3.5.1 license key completely before installing BX5.0 license key.

I'm using Solaris and I've just upgraded to BX 6 from BX 5. After installing BX 6, I've installed the corresponding new BX 6 keys into the FlexLM license server. Whenever I try to start BX 6, it runs in "Demo Mode" but BX 5 runs in "Full Use Mode". Why?
On UNIX platforms, ICS uses the FlexLM license server to manage the floating licenses to BX. When you purchase a new license or an upgrade license, you use commands provided by FlexLM to add these licenses to the database of the license server. This process can be confusing, and we highly recommend that new users carefully read Appendix C: License Manager, before adding attempting to add new or upgrade licenses.

In the situation described, the most likely problem is that you forgot to remove the BX 5 licenses from the FlexLM license server. A BX 6 license key will enable both BX 6 and all prior releases of BX (e.g., BX 5, 4, 3.5.1, etc.) to function in "Full Use Mode". However, when BX 6 checks out a BX 5 key, it rejects it and goes into "Demo Mode". This explains the observed situation where BX 5 works, and BX 6 does not.

Why does my BX Evaluation on SGI always start up in Demo mode? It never asked me to install a key. How do I provide BX with my evaluation key so that I can get full use of the product?
There is a known problem with Builder Xcessory evaluations on SGI/IRIX that is fixed in the next release. If you are using IRIX, you should create a license file that contains the license key and then set the environment variable LM_LICENSE_FILE to point to it. Let's assume that you've put your evaluation license for BX in the file /some_path/mylicensefile.dat. Then depending on which UNIX shell family you are using, you would do one of the following:

For csh (and its variants):
% setenv LM_LICENSE_FILE /some_path/mylicensefile.dat

For sh (and its variants)
% export LM_LICENSE_FILE=/some_path/mylicensefile.dat

When BX PRO requests my evaluation key, the dialog box that appears specifies a format that is different than the key I was sent. Do I mangle my Linux key into that format?
No. Cut the line from the email that delivered the key and paste the exact line into the entry field. The example license line is accurate for UNIX evaluation licenses.

Do I enter the whole line or just the "key" portion when BX PRO requests a key?
Enter the whole line starting with "LICENSE" for Linux evaluations and "FEATURE" for UNIX evaluations.

How can I put the license file somewhere else?
The environment variables ICS_LICENSE_FILE (on Linux platforms) and LM_LICENSE_FILE (on UNIX platforms) are used to specify the location of the BX PRO license file. To set the environment variable

Linux:
For csh (and its variants):
% setenv ICS_LICENSE_FILE /some_path/mylicensefile.dat

For sh (and its variants)
% export ICS_LICENSE_FILE=/some_path/mylicensefile.dat
UNIX:

For csh (and its variants):
% setenv LM_LICENSE_FILE /some_path/mylicensefile.dat

For sh (and its variants)
% export LM_LICENSE_FILE=/some_path/mylicensefile.dat

My system administrator installed the evaluation and the corresponding evaluation key. However, when I start up BX, it requests a key from me and when I don't provide it, it goes into demo mode. How do I fix this?
Everybody that will be using BX must install the evaluation key or set the proper environment variable (see question above) to point to a common location for the evaluation license key.

Can I evaluate Linux and Solaris simultaneously?
BX 6.1: Yes, just cut and paste the appropriate key into the key request dialog box as BX starts on the platform. Alternatively, if your startup file detects which system type you are using, just set the environment variable above to the appropriate location for that system. EPak and ViewKit share the same evaluation key on both Linux and UNIX, so you can just set it once.

BX 6.0: If you need to evaluate both a UNIX and Linux version of BX PRO with BX 6.0, do the following:

Linux: Copy your license into a file called icslicense.dat and save this file into your home directory.

UNIX: Start BX on your UNIX system and copy and paste the UNIX evaluation key into text box when it requests a license.

I'm confused, I thought that BX used the FlexLM license server?
When you install a full, permanent license for BX PRO on UNIX systems, you will use FlexLM. Detailed instructions for installing FlexLM are provided in Appendix C of the BX Reference Manual. If you are installing a permament key, we urge you to read this section in detail to maximize your benefit from using floating licenses.

To reduce the amount of time spent installing keys, we have developed a simpler scheme for evaluation licenses. This section talks about how you install an enable an evaluation of BX PRO.

I am using Solaris 8 and having a problem time starting the ICSBX daemon and the lmgrd program.
You need to manually set the number of file descriptors in the shell that starts the lmgrd daemon to something less than 4096. Our suggestion is to use 1024 since that was the default on Solaris 7 systems. To do so:

For csh (and its variants):
% limit descriptors 1024

For sh (and its variants)
% ulimit -H -n 1024

Restart the lmgrd and do a:
% ps -ef

You should see the ICSBX daemon running.

I have FlexLM 7.0 running on my Solaris 8 system and I've added my BX PRO license to its database. When I run ./lmstat, it claims I am checked in. However, when I start BX up, I'm told that no license exists. How can I get BX to checkout that license?
You need to manually set the number of file descriptors in the shell that starts the lmgrd daemon to something less than 4096. Our suggestion is to use 1024 since that was the default on Solaris 7 systems. To do so:

For csh (and its variants):
% limit descriptors 1024

For sh (and its variants)
% ulimit -H -n 1024

Restart the lmgrd and do a:
% ps -ef

You should see the ICSBX daemon running.

