Skip to main content

Problem:

  • Product Name: BES App Server
  • Product Version: 6.5
  • Product Component: License Manager & JBuilder 2005 Plugin
  • Platform/OS Version: All
  • JDK/Compiler Version: Same versions bundled with BES


As a matter of fact, JBuilder 2005 license package includes BES 6.0 license which enables both BES 6.0.x and BES 6.5 versions.

Please remember that BES 6.0.x does not support Networked Named User Licensing, but supports Concurrent Network Licensing, whereas BES 6.5 does endorse both Named and Concurrent Licensing.

Hence, when you try to use JBuilder 2005 with BES 6.5 using JBuilder"s Named License file (*.slip), you would see that BES Management Agent (scu) starts up with the following message at the top:

"Starting UNLICENSED management agent"

And also you would not be able to start your BES Partition and hence you would fail deploying from JBuilder.

Resolution:

You can follow the steps below to make BES 6.5 working with the same Named Network License (*.slip) file from your JBuilder 2005 License package.


1. Stop your BES server (if currently running - say, with the temp license)
2. Use BES License Manager to remove all the licenses applied in your BES deployment.
   (Please refer BES User Guide regarding License Manager options)
3. Copy the named network license file (the same *.slip file from your JBuilder) into /license folder.
4. Modify your "license.ini" file under /var folder to have "USER" as the license mode, instead of "NODE".
   i.e., LICENSE_MODE=USER
5. Ensure that your BLS (License Host) server started up successfully
   (Hint: JBuilder should work for the same user who tries to run BES)
6. Now, try to start "SCU" from BES Command Prompt. You should not see any "UNLICENSED" message while starting up.


#namedlicense
#VisiBroker
#Security
#concurrent