ePatha License Manager
FAQ's
and Bugs
Updated for Version 3.0




Q. The key provided is too long. How do I create a long value in my code with this key ?
A.
 You must assign it using the static method parseLong in the Long class. Example:
    long key = Long.parseLong("1234567890123456789");




Q. What are the basic differences between the Standard and Enterprise editions ?
A.
The Enterprise Edition (EE) provides many features the Standard Edition (SE) does not. Here are a few:

Q. Can I get a trial version of the Standard Edition ?
A.
Sure, just click here

Q. Can I get a trial version of the Enterprise Edition ? How ?
A.
Yes. Just request one.

Q. What version of Java is required to run it ?
A.
 You must have at least a Java Runtime Environment (JRE) version 1.3 or later  installed on your computer and your client's computer.



Q. On temporary licenses, when does the countdown start ?
A.
On 2.x licenses, the countdown always started at the time the license was created. This is also true on 3.x licenses, unless the "Start on First Use" indicator has been selected.

Q. How does the "Start On First Use" indicator work ?
A.
This depends on whether you're using the Enterprise or Standard Edition.
If you're using the Standard edition, the first time a license is used, a date file is created on the client's platform using that platform's system date. Thereafter, the client's system date is always compared to that date file.
If you're using the Enterprise edition and the client's license was specified with "Use Date Server", then the first time the license is used, the date will be recorded on your eLM Server. Thereafter, the server's system date is compared to the recorded date. If the client cannot access the internet, or your eLM server, the original creation date is checked against the client platform's system date.

Q. Can I create a temporary license that's already expired ?
A.
Yes. You can do this from any of the interfaces, by prefixing a minus sign (-) to the number of days to expiration.
Note, do not use a zero in the days field unless you intend to create a permanent license.



Q. How can I be sure customers just don't copy the license for their friends ?
A.
You can't in the Standard Edition, but in the Enterprise Edition an internet verification option allows you to do platform verification whenever the license is accessed.

Q. Can I embed my licenses in my application jar files ?
A.
Yes. We do that with the eLM itself. However, in this version, you cannot direct the server to update/rewrite these licenses, as you can with license files not in a jar.
In the next revision (3.1), however, this feature will be provided.

Q. Can I license an applet with the License Manager ?
A.
The eLM is designed as an application tool, so it contains no hooks specific to applets. However, if you follow the general rules of applet design, there is no reason the license verification methods shouldn't work. If you discover any such conflicts, please let us know.

Q. Can my License Server be hacked ?
A.
Not likely. There are a number of precautions built into the server to thwart invalid users, including encryption and bad command limits. Even if they did, there is route available for them to damage your server or data.

Q. How secure are the communications between the license client and the server ?
A.
All requests and responses are encrypted with a 64 bit proprietry methodology.

  • Can I issue licenses from Tomcat or Websphere ?

  • A. Yes. Just be sure to include your License.jar file in a place it can be found.
    e.g. with Tomcat, place in CATALINA_HOME/common/lib

    Q. Can I redistribute the License GUI with my application, so my customers can use it ?
    A. NO.
    This is a violation of the License Agreement.

    Q. Can I resell the License Manager to my customers ?
    A. Not without special permission from us. Otherwise, this is a violation of the License Agreement.

    Q. What does License.getExpirationDate() return for a license that never expires ?
    A.
    The String "none".

    Q. Will the number of options be expanded above 8 ?
    A.
    Probably not, but if you use the new Categorized Data field properly, you can extend your effective options significantly.



    Q. How do I upgrade my 2.x licenses to version 3 ?
    A.
    While there is no specific tool to do this, the easy way is just to go to History -> View/Edit, then select all the licenses you want to upgrade to 3.0 and click Reissue.

    Q. Why isn't this version obfuscated ?
    A.
    There are a significant number of API tags which we can't really obscure, plus reverse engineering is forbidden under the License Agreement. That not withstanding, version 3.1 will be obfuscated.



    Q. I run VMS and the java install didn't move my files, although it said it did. What's wrong ?
    A. Java install
    moves files, which in the VMS world means renames them. As you know in VMS you can't rename your files to a different disk. Try copying your LICENSE.ZIP file to a location on your system disk and rerun it from there.

    Q. During the Generic installation process, I need to run java install, but I have no access to a shell. How can I do it ?
    A.
    Install the product on a platform that does have shell access, then copy everything in the target directory to the machine in question.

    Q. During the Generic installation process, I run java install, but I get the following error:
        Exception in thread "main" java.lang.InternalError: Can't connect to X11 window
    this is a Solaris server and no windowing is installed. What can I do
    ?
    A.
    Run the install with the target directory as the first parameter to java install. For example:
    java install "/root/usr/bin/jlm"
    It will install as normal except, of course, you won't be able to use the GUI features. All the API and CLI features will still work fine.



    Q.  Any reported bugs ?
    A. All reported bugs will be listed here :

     
    Bug List
    Bug Version Affected Description Workaround Resolution
    1
    2.0
    The API call to verifyLicenseFile() will not set the LicenseVal public variable to -5 as stated in the documentation. Instead LicenseVal will be zero for valid, but expired, licenses.
    Call the isExpired() API to determine if a valid license has expired. Functions and documentation made consistant in 2.0.1 released 13-Mar-2004
    2




    3




    4




    5




    6




    7





     

     Return to Product Announcement

    © ePatha Software, LLC. All rights reserved.

    Last updated  May 19, 2005