Portlet Development Workbook
Return back to the Data source page by selecting that tab. With the JDBC provider that we just
created being selected, click on Add… to create a Data source. On the first page of that wizard
select DB2 Legacy CLI-based Type 2 JDBC Driver and a Version 5.0 data source. Then on the
next page specify a name of your choice, I used Portlet Development Workshop Data Source.
For the JNDI name you can also specify a name of your choice. This value will be used in our
portlet code to look up this data source using the JNDI naming service. I used jdbc/pdwDS. For
the Description enter Portlet Development Workshop Data Source. Next, associate the
authentication credentials for this data source to connect to the database successfully. For
Component-managed authentication alias select the security alias that we just created.
Deselect the checkbox identified as “Use this data source in container managed persistence
(CMP)”. Select Finish completing the data source creation.
Return back to the Data source page by selecting that tab. With the JDBC provider that we just
created being selected, click on Add… to create a Data source. On the first page of that wizard
select DB2 Legacy CLI-based Type 2 JDBC Driver and a Version 5.0 data source. Then on the
next page specify a name of your choice, I used Portlet Development Workshop Data Source.
For the JNDI name you can also specify a name of your choice. This value will be used in our
portlet code to look up this data source using the JNDI naming service. I used jdbc/pdwDS. For
the Description enter Portlet Development Workshop Data Source. Next, associate the
authentication credentials for this data source to connect to the database successfully. For
Component-managed authentication alias select the security alias that we just created.
Deselect the checkbox identified as “Use this data source in container managed persistence
(CMP)”. Select Finish completing the data source creation.
A final step is to actually associate our database, by name, to this
data source. With the data source we just created selected edit
the databaseName Resource property. Change the value of this
property to the name of our database (the database, not the table).
The name we used was pdwdb. With this done, we have
completed the creation of the data source in our application server
configuration. Unlike the application server console we cannot test
this connection. So, hopefully you have followed these instructions
carefully so we don’t have to debug data source definition errors!
A final step is to actually associate our database, by name, to this
data source. With the data source we just created selected edit
the databaseName Resource property. Change the value of this
property to the name of our database (the database, not the table).
The name we used was pdwdb. With this done, we have
completed the creation of the data source in our application server
configuration. Unlike the application server console we cannot test
this connection. So, hopefully you have followed these instructions
carefully so we don’t have to debug data source definition errors!
Create a Contact bean in Application Developer Create a Contact bean in Application Developer
Next we will create a bean (a class that follows standard naming conventions and is serializable)
that will represent a entry in our contact list. Select the JavaSource folder in our Contacts –
Standard portlet project and add a new package called com.ibm.sample.standard.beans. In
that package create a class called Contact that implements Serializable as defines the following
fields
Next we will create a bean (a class that follows standard naming conventions and is serializable)
that will represent a entry in our contact list. Select the JavaSource folder in our Contacts –
Standard portlet project and add a new package called com.ibm.sample.standard.beans. In
that package create a class called Contact that implements Serializable as defines the following
fields
protected String oid = "";
protected String userid = "";
protected String firstName = "";
protected String lastName = "";
protected String email = "";
protected String company = "";
protected String businessPhone = "";
protected String mobilePhone = "";
Generate the getter and setter methods for these fields (in Application Developer select Contact
from the outline or explorer view and from the context menu and select Source…. Generate
Getters and Setters. Save the file when the access methods are defined.
Create a database access class
Next we will create a database access class with a public method that will return a list of Contact
instances that represent the contacts of the logged in user. Select the JavaSource folder in our
Page 11 of 65