Problem:
- Product Name: VisiBroker
- Product Version: 5.2
- Product Component: Licenses
- JDK Version: 1.3.1
- Platform/OS Version: All
Q1:
What is the difference between deployment license from only development license in VisiBroker 5.2? It is only run 72 hours in the BES AppServer, then AppServer will be down and need to be restarted.
Q2:
Describe what cause our server down after run 72 hours in All Edition. What is the principle behind it?
Q3:
How do to register only install VisiBroker Edition with the deployment license? After installing the BES AppServer, the Console can be started and perform the registration. However, when installing the VisiBroker Edition, the AppServer Console can not be found but only the VisiBroker Console, and the registration function is not there in the VisiBroker Console.
Resolution:
Ans1:
The 72-consecutive-hour development license constraint is the same across all four editions: Web, VisiBroker, Team, and AppServer.
Ans2:
Regarding on the licenses principal,
Development License: Development versions are restricted. Services shutdown after 72 hours of continuous work so that no production operation can be performed with development licenses.This is because we want customers to contact Borland so we can assist them and follow up on the sale opportunity.
Deployment License: Licenses are unique. A server will not start if there is another server using the same s/n and a/k in the network (osagent domain).
The intent of the deployment licenses is to have customers pay for the right to deploy the server components of applications. We do not attempt to make customers "count" clients or count web based users. For VisiBroker for Java and C , deployment licenses are required only for machines running server-side components ( including the infrastructure components). Distribution of client-side deployment is without charge.
With the deployment license, the files included in the "deployment" package are those that are installed by the Visibroker install program on a machine that executes "server" logic or are running the infrastructure component(osagent, locserv, irep,etc...). Those infrastructure pieces are considered server-side functionality and require a deployment license for those pieces to be installed in a production environment.
Ans3:
Borland VisiBroker (standalone). Installs VisiBroker for C and Java ONLY. Note: The VisiBroker standalone option is not the VisiBroker Edition. The VisiBroker standalone installation does not include the Web Edition; the VisiBroker Edition installation does. First method is to key in the deployment license in the beginning of the installation. Second method - Please refer to the installation guide(pg5-1). Basically, the concept is to created the text properties file, save it as properties_file.txt and then execute it on the command prompt like this:
>BES52_Windows.exe -f c:\\properties_file.txt
In the properties_file.txt, you could specify the BES_SERIAL and BES_KEY whereby here you can use your deployment license key.
#Security
#VisiBroker
