XGMS_Deploymentx - About ftp.heanet.ie

lifeguardknowledgeInternet και Εφαρμογές Web

30 Ιουλ 2012 (πριν από 5 χρόνια και 2 μήνες)

352 εμφανίσεις

XGMS: Deployment description

Upon closer examination of the available packages, you will see

that the system consists of
three

distinct parts:



A web package, in the form of a WAR file, to be loaded within IBM Websphere

Community
Edition. This package contains the web application.



A standalone package, in the form of a JAR file. It consists of an Administrative Application in
the form of a Thick Client.



A specific DLL, used to allow communication of third party programs
with the Belgian eID
middleware.

The following part will describe how to set up these packages in to working order.

1)

The
eID DLL

The DLL file, in this case “beid35libJava_Wrapper.dll”, should be dropped somewhere within the
CLASS path within the OS. By d
efault these are areas such as C:
\
windows
\
system32, but it is
recommended to drop it in the eID middleware folder, by default “
C:
\
Program Files
\
Belgium Identity
Card
”.

2) The Web application

The WAR might seem quite heavy, but it contains al the libraries
and the applet too. Load it within
Websphere (dropping it in the appropriate folder and having auto
-
mount enabled should do the
trick) and let it do its work.

Next, go in the web.xml of the web application

where you will find 3 init parameters that you nee
d to
fill in:



DB username



DB password



DB url

These need to be entered in order to allow a connection to the database.

The URL usually has this
form:

jdbc:db2://<IP>:<PORT>/<DBNAME>
:retrieveMessagesFromServerOnGetMessage=true;

An example:

jdb
c:db2://127.0.0.1:50000/XGMS
:retrieveMessagesFromServerOnGetMessage=true;

3) The Administrative Application

The administrative application comes packed in a single JAR file. Just run it with java

jar <archive
filename> from the command prompt, or double c
lick on the JAR file if your Java is thus configured
for direct launch of runnable JAR files, to launch the application.

As with the web application, you will need to fill in the DB username, DB password and DB URL within
the appropriate fields, followed b
y pressing the “connect” button. Only when a successful connection
is made will the other functions become available.

4) Preparing the database

The program expects a database with the following table configurations:

Please note that the table names

obviously do not have the quote marks. If the name within the
table here is noted as having quote marks, then it needs to be this way.

Table “Account”

Name

Type

Length

ID

INTEGER


USERID

VARCHAR

50

“TYPE”

VARCHAR

30

PERSONID

INTEGER



ID is the
primary key

Table “Clusters”

Name

Type

Length

ID

INTEGER


NAME

VARCHAR

50

CLUSTERDOC

XML



ID is the primary key

Table “Course”

Name

Type

Length

ID

INTEGER


NAME

VARCHAR

50

SP

VARCHAR

5

WP

VARCHAR

5

COURSEDOC

XML



ID is the primary key

Table
“Grade”

Name

Type

Length

ID

INTEGER


“RESULT”

VARCHAR

20


ID is the primary key

Table “Person”

Name

Type

Length

SSN

INTEGER


FIRSTNAME

VARCHAR

50

LASTNAME

VARCHAR

50

ADDRESS

VARCHAR

50

TELEPHONENUMBER

VARCHAR

50

EMAIL

VARCHAR

50

GSMNUMBER

VARCHAR

50

DOCUMENT

XML



SSN is the primary key


When these 5 tables are in the database, it should work together with the program.