Browse Prior Art Database

System for Verifying Library Dependencies and Configuring Runtime Parameters for a Thick Client Application

IP.com Disclosure Number: IPCOM000206419D
Publication Date: 2011-Apr-25
Document File: 5 page(s) / 45K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a system comprised of both a program and a script which verify library dependencies and configure runtime parameters for a thick client application. The system automatically generates Classpath and Java Virtual Machine (JVM) options based on the information supplied; the only configuration settings required are those specific to the client being run.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 30% of the total text.

Page 01 of 5

System for Verifying Library Dependencies and Configuring Runtime Parameters for a

Thick Client Application

Configuring standalone Java* EE thick client applications can be challenging, especially when clients are intended to support several application servers from different vendors. The client generally requires several libraries to be added to the Java classpath and several vendor-specific Java Virtual Machine (JVM) properties to be set. Missing a single client library or required setting will cause the application to fail, generally with a fairly opaque stack trace rather than any guidance as to what might have gone wrong.

This is a particular problem for products and platforms which are built on top of Java EE, thus adding their own requirements in addition to those of the application server and the client application. For example, thick clients for the FileNet P8 Platform require additional Java Archive (JAR) files for the Content Engine and Process Engine Application Programming Interfaces (APIs), and result in commands similar to the following to launch:

set CLASSPATH=cesample.

j

ar;C:

\Program

Files\IBM\FileNet\CEClient\lib\Jace.

j

ar;C:

\Program

Files\IBM\FileNet\CEClient\lib\log4

j-1.2.14.

j

ar;C:

\Program

Files\IBM\FileNet\BPMClient\files

\

pe.

j

ar;C:

\Program

Files\IBM\FileNet\BPMClient\files

\pe3pt.

j

ar;C:

\Program

Files\IBM\FileNet\BPMClient\files

\peResources.

jar

"C:\Program Files\IBM\WebSphere

\AppServer

\

java

\bin

\

java" -cp

"-Djava.naming.provider.url=iiop://cm-cfgsvr69vm1:2809 -Dfilenet.pe.bootstrap.ceuri=iiop://cm-cfgsvr69vm1:2809/FileNet/Engine -Djava.security.auth.login.config="C:

\Program

Files\IBM\FileNet\CEClient\config

\samples

\

jaas.conf.WebSphere"

-Dcom.ibm.CORBA.ConfigURL="file:C:

\Program

Files\IBM\WebSphere\AppServer

\properties

\sas.client.props"

-Djava.ext.dirs="C:\Program Files\IBM\WebSphere\AppServer

\

java

jre

\lib

\

ext;C:

\Program

Files\IBM\WebSphere\AppServer

\lib;C:

\\Program

Files\IBM\WebSphere\AppServer

\plugins"

-Djava.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory -DtraceSettingsFile="C:\Program Files\IBM\WebSphere\AppClient\properties

\TraceSettings.properties"

-Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Djava.util.logging.configureByServer=true cesample.MainFrame

The complexity is compounded by the requirement to support multiple application servers and operating systems. There are other options as well. In the case of FileNet P8, clients can choose to connect to Content Engine using either the native Enterprise JavaBeans (EJB) transport protocol provided by the application server (e.g., RMI-IIOP, WebLogic T3, or JNP), or a Simple Object Access Protocol (SOAP) Web Services

1


Page 02 of 5

interface. The result is that while a sample program like the CE Folder Browser consists of a single JAR file, it also ships with 12 different scripts to start the program, one for each combination of application server, operating system family, and...