work guide for tgmc1

7/31/2019 Work Guide for Tgmc1

1/157


2/157

First, installation of IBM Java

1.4.2

--TGMC workshop team, SOC.


3/157


4/157


5/157


6/157


7/157


8/157


9/157


10/157


11/157


12/157

Second, an easy installation of

Eclipse 3.1.2 with WAS CE patched

plug-in



13/157


14/157


15/157


16/157


17/157

Third, Installation of WAS CE



18/157


19/157


20/157


21/157


22/157


23/157


24/157


25/157


26/157


27/157


28/157

Last in installation, DB2 Express

c 9.0

--Rajaraman Srinivasan


29/157

Choose Install a

Product


30/157

Choose Install New


31/157


32/157


33/157

Choose Typical, since

only basic features are

included in the CD


34/157

Remember thispath


35/157


36/157

Remember this

password


37/157


38/157


39/157

Remember thispath


40/157


41/157


42/157


43/157


44/157


45/157


46/157

If you need, you could create a sample

database. Or, you could create your own

database from First Steps (this window)

Or you could launch Control Center and

create your own database from there


47/157

Control Center could be launched either

from Taskbar (Right Corner) or from

ProgramsIBM DB2 DB2COPY1

General Administration Tools

ControlCenter


48/157


49/157


50/157

Enter the name of the database here


51/157

No Input needed in this page Just click

Next


52/157

Choose IBM-1252

(default option) if

you are using the

database to storeonly English If you

want localization

choose UTF-8

Click Next


53/157

Click on Show

Command to see the

database creation

command generated

by Control Center

Click Finish to create

database


54/157

Click on Show

Command to see the

database creation

command generated

by Control Center


database


55/157


56/157


57/157


58/157


59/157

No Inputs needed

on this page Click

Next


60/157

No Inputs needed

on this page Click

Next


61/157

Click on Add Primary

to add a primary key

for the table.

Similarly for Add

Unique and Add

Foreign (if needed)


62/157

No Inputs needed

on this page Click

Next


63/157

Click on Add to

impose a check

constraint (if

needed)

Click on Next to

proceed


64/157

Click on Show SQL to

see the table

creation command

generated by

Control Center


table


65/157

Click on Query to run

queries insert, select,

update or delete


66/157


67/157

Configuration of Installed Softwares

and a deep introduction to J2EE



68/157

Give a suitable workspace here, where all your work will be

Stored!


69/157

Click the arrow like icon


70/157

Click window option in the menu bar


71/157


72/157


73/157


74/157

Right click here


75/157


76/157

Click next after selections are made as shown


77/157

Click next


78/157

Click browse button, to choose the home directory where WAS CE is installed

i.e., the parent-directory for the bin folder of WAS CE

The error symbol

should disappear to a

warning symbol after

choosing the correctlocation


79/157

Choose the home directory and press OK


80/157

As the correct path is

given, the symbolchanges as shown


81/157

Click next. Please note the user id and password for

WAS CE


82/157

Click finish!


83/157

Right click the Dynamic

web project as shown


84/157

Make similar selections and it will

Guide you to the project creation

Wizard


85/157

Give an

appropriate

name for yourproject and click

next


86/157


87/157

Click next!


88/157

Click finish


89/157


90/157

You should have such hierarchy

Of files inside your dynamic web

Projects node in the tree shown in

Project Explorer Pane


91/157

Right click the server


92/157

Click start


93/157

Wait until the server finishes starting

You can see a message in the console!

[it happens sometimes that the server

Has some problems due to internet connection(wi-fi). So, disable wi-fi, if your server throws

Exceptions at startup.]


94/157

Now server is ready to work


95/157

In the server pane also, the status will be started


96/157

Click this button, to

open web browser


97/157

Type the address as

shown


98/157


99/157

Click the database

pools link


100/157

Click this link(first one)

This is for creating a link

with the Database created

at DB2


101/157

Give a name(and remember it) for the database pool you are creating.

FYI: a pool is a set of connections with the database. It avoids the program

To communicate with the database directly for accessing it each time.

Instead, by creating this pool, it gets a set of connections from the database

so that they can be used one-at-a-time basis, whenever needed.

This not only saves time for the program, but also for the database!


102/157

Select DB2 for database type, as shown, and click next


103/157

This page requires all

fields to be filled

correctly.


104/157

From the drivers

list, choose

com.ibm.db2/db2j

cc/8.2/jar

The name of the database is

testdb in our case, and a snapshot

f h l l h


105/157

This is

50000

bydefault

Give the database name correctly as itis the one you are going to make

transactions through the program. The

database should already exist and

should be running(at least before

testing the connection)

of the control center is also shown


106/157

If you see this

message, leave

the fields as such

and click theTest

Connection

button


107/157

Now, the server is connected with

the database and we can deploy

the pool permanently.

Click Deploy


108/157


109/157

The pool we created should appear in the list shown.


110/157

Also, the message of successful deployment should be seen on the

console.


111/157

Now, to connect the pool with our application,

Click usage link to the right of the pool, which

has connections with the needed database

The next page has a picture, which is the screen shot of the page that appears after

li ki th li k f th d t b l


112/157

clicking the usage link of the database pool.

It also has a clipped image of the project explorer pane of eclipse with the web content

folder of the project expanded

You can find two sub folders within it. Among which WEB-INF has two files.Those two files are needed to be modified, in order to make our application communicate

with the pools, which in turn communicate with the database.

Let us look at the changes to be made.


113/157


114/157

Copy this

selection and

paste it into the

source of

Geronimo-

web.xml


115/157

Pasting alone will leadto error at the

tag


116/157

To rectify the error, change the nam shown in the highlight to naming


117/157

And change MyDataSource to yourpool name, as shown


118/157


119/157


120/157

Similar changes are to be

made for web.xml also


121/157


122/157


123/157


124/157


125/157

Now, we shall see, how to code in eclipse, retrieve data from DB2 and

test-and-run it in WAS CE.


126/157

FYI: All packages needed should be placed inside the src folder

for its usage as beans or as importable classes.All jsp,html pages should be placed inside the WebContent

folder. In order to make a html page, right click WebContent

and make selections as shown.


127/157

Give a name and click next


128/157

Click finish


129/157

You can type the html codes here, save it.

The sample, we are having has the following objectives:

1. Gets the user id and password from user through a html page

2. Verifies it with the data stored in the database and3. Finally direct the right user to welcome screen and others back to

Login

The values of

i t i thi f


130/157

inputs in this form

will lead the page

mentioned in its

action property. If

the page

mentioned is not

found, WAS CE

reports error


131/157

Now, to run the page,

right click the file on the project

explorer pane and select the

options as shown.


132/157

Click next. After

selecting this


133/157

Make sure that the project

in which the file to run

exist in the list of

configured projects and

click finish


134/157


135/157


136/157

As we dont have any log.jsp, this error is reported!


137/157

Now, create a jsp page.


138/157


139/157


140/157

The following two slides shows the codes in this page as snapshots.

To understand it, the forthcoming pages at the last will consist of

Explanations to each necessary statement.


141/157


142/157


143/157

// // //

Hai!

Here, the first few lines are taken. tag needs attention for the last import

property. As value(s) for the property you can give any number of valid java packages,separated by commas. The pageEncoding field can be changed to any encoding schemes

like UTF-8,UTF-16 etc.

tag plays importance only in case of using XML. We can apply particular style for

custom tags using XSLs in XML. It can be ignored right now.

Next is the tag, within which the is used to display the text at the title bar of

the browser.

function fun()

{


144/157

{

alert("welcome user!your details are found in the database!!");

}

function foon()

{

alert("Sorry! you are not a valid user!! click here to go back to login!!!");

history.back(1);

}

The power of J2EE lies in the use of HTML, java, JavaScript, XML etc. in a single source file.

This shows two javascript functions with the output of fun() as shown in (i) and foon()

produces the message as shown in(ii) and leads to the page visited before.

(i) (ii)


145/157


146/157

boolean flag=false;

InitialContext ic=new InitialContext();

DataSource ds=(DataSource)ic.lookup("java:comp/env/jdbc/testpool");Connection con=ds.getConnection();

Statement stmt=con.createStatement();

For simplicity, it is not necessary to understand ever line of this jdbc block.These are the statements for making connection with the pool. These statements need

Javax.naming.*, javax.sql.*, java.sql.* ;

boolean flag=false;

is a statement to be used to indicate the validity of the users login.

In the 5 th line, the testpool should be replaced by the appropriate pool names given in

the WEB-INF/web.xml and WEB_INF/geronimo-web.xml files.Statement is a class, which has methods for executing queries and it cannot be directly

instantiated.

The first statement try{ will be referred in slide 82.

ResultSet rs=stmt.executeQuery("select * from log_table");

while(rs.next())

{


147/157

{

String temp=rs.getString(1);

String temp1=rs.getString("pass");

if(temp.equals(user)&&temp1.equals(pas))

{

flag=true;

break;

}

}

To execute select queries, we use stmt.executeQuery() whose result is returned in a ResultSet

object. Insert, update & delete queries should be executed as stmt.executeUpdate(query);

From the ResultSet object , we should know about 2 general functions. next() function takes

the cursor to the next row of the result and returns true on success and if it is already in the

last row, returns false. get() method returns the cell value specified by the column namas String or column index as integer with the specified type.

The logic involves checking the user id and password entered with those retrieved from the

log_table in the database.

if(flag)

{

out.println("hai!!!"+user);

%>


148/157

%>

fun();

document.write("Invalid parameters");

foon();


149/157

{

e.printStackTrace();

}%>

Every try{} block should have a catch(){} block or finally{} block or both. As java is very cryptic

In errors and exceptions it is necessary to use them. However J2EE has a choice.

But to keep track of errors, it is advised to use try blocks wherever needed.

The statement e.printStackTrace(); will have references to the line in which the error occurred

by showing a lengthy stack trace at the servers console, which will help in debugging.

Finally, the code is to be tested and run.

As seen, this page needs the sample.html page to be run, in order to check for bugs.

So, run sample.html.


150/157


151/157


152/157


153/157


154/157


155/157


156/157


157/157

work guide for tgmc1

Documents