Setting up the the licensing for RPE Web Services 2.0


One of the most common problems I’ve seen reported for RPE 2.0 is setting up the shared license library required for RPE WebService 2.0 to function. You access http://server:8080/rpeng/, login and you are greeted by the following error

Error 400: Cannot obtain a RPE License. Please contact the system administrator.

For the RPE WebServices 2.0 to work properly you need to configure a shared library in the application container you are using. The procedure is described in the Infocenter in detail for all supported application containers but there are a couple of errors that can cause the deployment to fail.  For this I have listed the key missing/incorrect points in our docs.

NOTE: we are working to simplify this procedure considerably in the next RPE release.

Common

For all supported deployments make sure you pick the appropriate  version of the native library for your system ( dll for Windows and so for Linux) and bitness of the server.

You also need to have the RPE_HOME system environment variable or Java property pointing to the RCL license server that has RPE licenses.

WebSphere

The RPE Infocenter documentation is here.  The corrections to the documented procedure are described below:

  • Classpath – you only need to list the jar file
  • Native Library Path – you need to list the path to the library folder not to the dll/so itself.

NOTE: with this change you do not need to alter the PATH system variable on Windows or the LD_LIBRARY_PATH on Linux

rpe_license_websphere

Liberty

The RPE Infocenter documentation is here. The corrections to the documented procedure are described below:

  • the fileset for the RCL library must include both  *.jar and *.dll/*.so files. See attached the version for my Windows liberty deployment. Replace *.dll with *.so for Linux deployments

NOTE: with this change you do not need to alter the PATH system variable on Windows or the LD_LIBRARY_PATH on Linux

rpe_license_liberty

Tomcat

The RPE Infocenter documentation is here.  The corrections to the documented procedure are described below:

  1. copy rcl_telelogic.jar in Tomcat’s lib folder. This is a must regardless of the option  you use for the next step
  2. for Tomcat to find the DLL you have 3 options
    1. copy rcl_telelogic.dll/librcl_telelogic.so in Tomcat’s bin folder
    2. add the library folder containing the dll/so in the PATH  (Windows) or LD_LIBRARY_PATH (Linux) system variable for the Tomcat process
    3. add the library path to the java.library.path Java property in the catalina.bat/catalina.sh file as shown below.

NOTE: if you go with options 2.1 or 2.3 you do not need to alter the PATH system variable on Windows or the LD_LIBRARY_PATH on Linux

rpe_license_tomcat

Advertisements

Author: Dragos Cojocari

Architect for Rational Publishing Engine

3 thoughts on “Setting up the the licensing for RPE Web Services 2.0”

  1. Hi, I think you may have a typo in your instructions for Tomcat setup. The file name appears to be rcl_telelogic.jar (not rlc_telelogic.jar). Thanks for the notes!

  2. Hi Dragos.. Thanks for your page here.

    I am still having problems connecting to the license server.

    Can you elaborate on your Common section above? There is mention of the RPE_HOME system environment variable or Java property.

    If I change my RPE_HOME variable to point to my license server, my local installation of Document Studio will not work, and the RPE web app still cannot find the license server.

    Can you explain more about the Java property? Where/how do I find, create, or change it? What exactly should the variable name be and the value be set to?

    Thanks very much!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s