Resolution:

This general error indicates that the ORB needed a product license but could not find a valid one. To resolve the problem check

• If the application needs a license
• If a license for the ORB core was properly installed and enabled
• If the application configuration points to the right license folders
• If the user running the application has access to the license folders
• If the examples packaged with VisiBroker run without showing the error

Check if a license was installed and enabled

Run the license administration tool and verify the installed license(s) by running "lmadm -i console" and select the option "[2] List all licenses". There should be one enabled license for the ORB core. Dependent on the license type and the VisiBroker version the output should look similar to

[0] Visibroker 8.5 CORE PROD - Enable
     |---Visibroker 8.5 CORE PROD Visibroker 8.5 CORE PROD
              Serial number = XXXX-XXXXXX-XXXXXX-XXXX
              Platform = All
              Term/Trial = No

For some license types and registration modes they are delivered as a .txt or a .slip file. This file needs to be copied into the /license sub-folder of the VisiBroker installation. After that lmadm should list the license.

Licenses which are distributed as a combination of serial and key number need to be registered and activated through lmadm. The tool offers several options, for example a direct registration if the server has internet access.

Check the application configuration

The VisiBroker ORB needs to know where the /var and /license folders are located. By default they are sub-folders of the VisiBroker installation, but for some deployments - especially when applications are packaged with VisiBroker dependencies - these folders may be in a different location.

VisiBroker for C needs the environment variables

• BES_LIC_DIR pointing to the /var folder
• BES_LIC_DEFAULT_DIR pointing to the /license folder

Your application may use the /bin/vbroker.sh or /bin/vbroker.bat script files included in VisiBroker, or any application specific means to set these environment variables. Locate where they are set and verify the values.

VisiBroker for Java needs the Java System properties

• borland.enterprise.licenseDir pointing to the /var folder
• borland.enterprise.licenseDefaultDir pointing to the /license folder

If your application uses the /bin/vbj starter included in VisiBroker, these properties are configures in /bin/vbj.config. But the application may also set them through parameters passed to Java or in source code. Locate the properties and verify the values.

Verify also that the lmadm configuration points to the same folders, else the information shown in lmadm is not consistent with what the application reads.

• The configuration is stored in /bin/lmadm.config
• It sets the Java System Properties for lmadm

Check access rights to the folders

The user running the VisiBroker based application needs read and write access to the /var and /license folders. Verify the access rights and modify them if needed.

Run a VisiBroker example

If all above checks do not indicate any cause, try to run one of the examples shipped with VisiBroker. This helps you to determine if there is anything wrong with the VisiBroker installation, or with the application configuration.

• Navigate to the /examples/vbroker/basic/bank_agent sub-folder of your VisiBroker installation
• Read the included html files to build and run the Server

For the C example, make sure you run /bin/vbroker.sh or /bin/vbroker.bat before you build and run it. For the Java example use the vbj starter as described in the html documentation of the example.