For a JSF web application team project you need a web application server that is shared by all members of the team. That is, it is a stand-alone server run on a machine that is up 24/7. The GlassFish server works well when driven by NetBeans but it has some serious problems with database setup when run as a stand-alone server.

Fortunately, the British C2B2 Consulting company has a team that develops Payara, a web application server derived from GlassFish sources. This server fixes the database problems in GlassFish.

In this lab exercise your team will set up a shared Payara server on the UMD CS Department's server machine ukko.d.umn.edu. You will also create a database on Payara's embedded Derby database server and create a JDBC resource for its use in your team project. Finally, all team members will create a NetBeans project for the CS 4531 team project and connect their NetBeans to the shared Derby database.

The NetBeans project for your team will be constructed from sources for a modified version of the database JSF web application. This application will be used for testing the project setup. Its sources and database table can be removed after the set up is tested. This will leave you with a web application server, a database server, and a NetBeans project that will are properly configured for your team project efforts.

Preparation

The steps for this lab exercise are outlined in the section "Lab Exercise Overview" and detail are given in the following sections. Before you begin your team should decide on some passwords:

• A password for administering Payara from its administrative console.
• A password for the database.

These passwords should be reasonably secure. They can be the same.

• One team member sets up a shared Payara server for your team project work and sets up its embedded Derby database server. This is involves UNIX commands executed on ukko.d.umn.edu. Other team members can assist and observe.
• All team members log in to the Payara admin console.
• All team members create a new project from the provided sources. The sources are a modified version of the database application sources.
• All team members establish a connection from their local NetBeans IDEs to the Derby database server.
• One team member runs a SQL file from the new project to create the table for the database project.
• One team member creates a Payara JDBC resource.
• One team member deploys the modified database application to the team server. All team members should observe. You all may need to redeploy after you make modifications to the project sources.
• All team members create a NetBeans JDBC resource for their project.
• All team members remove files that are not needed for the project.

All team members should log in to the Payara admin Console. Later in this exercise one team member will use it to create a JDBC resource for the project. Later yet, one team member will use the admin console to deploy the project application. During project work other team members may need to to this.

The admin console is a JSF web application. It can be run by pointing your browser to the following url:

https://ukko.d.umn.edu:admin-port/common/index.jsf

Here admin-port is the administrative port reported by the asadmin command when the domain was started. The login name is admin. You will need your team's Payara admin password to log in.

The first time you log in you will get a warning about an insecure connection. You can add a security exception to get past this warning and prevent future warnings.

Click on the "Add Exception..." button to get past the exception and prevent future warnings. This brings up an "Add Security Exception" to confirm the exception.

Click on the "Confirm Security Exception". This will finally bring up the Payara admin console.

The Payara admin console is shown below. After this lab exercise, you will only need it to redeploy your project application after modifications.

Everything you need to do can be started from the left pane by clicking on its tree nodes:

• Clicking on the "Applications" node brings up a list of deployed applications in the right pane. From there you can deploy or redeploy an application.
• Clicking on the "JDBC Connection Pools" node brings up a list of connection pools in the right pane. From there you can create a new connection pool or test or modify an existing one.
• Clicking on the "JDBC Resources" node brings up a list of JDBC resources pools in the right pane. From there you can create a new resource or modify an existing one.

Most team members should log out by clicking on the "Logout" button at the upper right. One team member can stay logged on for upcoming lab exercise steps.

All team members should do the steps below. This will give you the starting point for your team project.

• Download a modified version of the database project here.
• Unzip it.
• Rename it to Teamn, where n is your team number.
• Start a new project in NetBeans from its source files.

Only one team member should create the database project table.

The database can only be created when the database server is running and NetBeans has a connection to it.

The "Web Pages/misc" folder of the project contains a customers.sql file. Running this file in NetBeans will create the table and insert rows into it.

Be sure to select the new NetBeans connection for your team database!

Only one team member should create a JDBC resource on the Payara server.

Setting up a JDBC resource makes it available to managed beans using resource injection. To create the resource you need to log in to the Payara admin console. Its url is https://ukko.d.umn.edu:admin-port/common/index.jsf, where admin-port is the administrative port reported by the asadmin command when the domain was started. You will also need the Payara admin password.

There are two parts to Payara resource creation:

• Create a connection pool on the Payara server
• Register a JDBC resource on the Payara server

One team members should deploy the application.

All team members should view the application with their web browser. It can be run by pointing your browser to the following url:

https://ukko.d.umn.edu:admin-port/common/index.jsf

Here admin-port is the administrative port reported by the asadmin command when the domain was started.

To deploy the application you need to first clean and build the application in NetBeans. Then bring up the Payara admin console and click on the "Applications" node in the left pane. You should get the screenshot below. Click on the "Deploy" button. This brings up the "Deploy Applications or Modules" dialog.

All you need to do here is use the "Browse" button to locate the project WAR file in your project's dist folder. Then click on the "OK" button. After a short delay the application should appear in the console's application list.

All team members should remove the Web Pages/misc/customers.sql file. You may later want to add your own file for recreating database tables here.

One team member should remove the customers table from the database. You can do this in the NetBeans "Services" pane by connecting to the project connection, expanding its node, then the "APP" subnode, then the "Tables" subnode. Right-click on the table and select "Delete" from the popup menu.