User Manual

Manuals Brands HP Manuals Computer Hardware Integrity NonStop J-Series

Open Source Java Frameworks on NonStop

User's Guide (Spring 3.1.0, Hibernate

4.1.1, MyFaces 2.0.2, Axis2/Java 1.5.2)

HP Part Number: 698927-002

Published: December 2012

Edition: J06.11 and subsequent J-series RVUs and H06.22 and subsequent H-series RVUs.

Summary of content (351 pages)

PAGE 1

Open Source Java Frameworks on NonStop User's Guide (Spring 3.1.0, Hibernate 4.1.1, MyFaces 2.0.2, Axis2/Java 1.5.2) HP Part Number: 698927-002 Published: December 2012 Edition: J06.11 and subsequent J-series RVUs and H06.22 and subsequent H-series RVUs.
PAGE 2

© Copyright 2012 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
PAGE 3

Contents About This Document.....................................................................................6 Supported Release Version Updates (RVUs)..................................................................................6 Intended Audience....................................................................................................................6 New and Changed Information in This Edition..............................................................................
PAGE 4

Installing MyFaces Framework................................................................................................146 Prerequisites....................................................................................................................147 Downloading MyFaces Framework Libraries on Windows......................................................147 Deploying and Running Sample MyFaces Application on NonStop........................................
PAGE 5

C Deploying Sample Applications on NonStop.............................................331 D Sample JDBC Configuration for Spring......................................................334 E Installing Spring Web Flow......................................................................336 Downloading Spring Web Flow Distribution on Windows..........................................................336 Copying Spring Web Flow Runtime Libraries from Windows to NonStop......................................
PAGE 6

About This Document This manual provides information on how Spring, Hibernate, MyFaces, and Axis2/Java frameworks, referred to as SASH, can be used to develop applications that can run on the HP NonStop™ system.
PAGE 7

• Updated the Hibernate distribution version in the “Downloading the Hibernate Distribution on Windows” (page 93) section. • Added the “Downloading Hibernate Dependency JAR Files using Gradle” (page 93) section. • Added the “Customizing the Hibernate Dialect for NonStop” (page 95) section. • Added a note and the Prerequisites for the Hibernate sample applications in the “Setting up Sample Hibernate Applications on NonStop” (page 98) section. • Updated “Connection Pooling” (page 112).
PAGE 8

Appendix D: Sample JDBC Configuration for Spring This appendix describes the JDBC configuration for the Spring framework using NonStop JDBC Type 2 and JDBC Type 4 drivers. Appendix E: Installing Spring Web Flow This appendix describes the steps required to install Spring Web Flow on your NonStop system. Appendix F: Sample JDBC Configuration for Hibernate This appendix describes the JDBC configuration for the Hibernate framework using NonStop JDBC Type 2 and JDBC Type 4 drivers.
PAGE 9

[ ] Brackets Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines.
PAGE 10

Line Spacing If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections.
PAGE 11

A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list can be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines.
PAGE 12

General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: SELECT Italic Letters Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in brackets are required.
PAGE 13

{, sql-expression}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: expression-n… Punctuation Parentheses, commas, semicolons, and other symbols not previously described must be typed as shown. For example: DAY (datetime-expression) @script-file Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown.
PAGE 14

1 Introduction Java-based web application development has been inundated by frameworks of every kind. There is a framework available for almost every application development requirement. The effort for developing an application using the framework approach is significantly less as compared to developing an application afresh. The efficiency of Java-based Web development can be increased by using the appropriate framework.
PAGE 15

NonStop provides a highly scalable servlet/JSP container to host the web applications developed using the frameworks. Because the applications are deployed on NSJSP, the Java frameworks can leverage the following advantages of NonStop: • Scalability Scalability in NSJSP refers to its ability to increase its capacity to process a large number of requests simultaneously, by adding resources, such as additional processes and logical processors, to a system.
PAGE 16

2 Spring Framework Spring Overview Spring is an open source framework that you can use to develop enterprise applications. Its features and functions are packaged in different modules. It includes a lightweight container that provides a centralized, automated configuration and wiring of your application objects. NOTE: Throughout this document, Spring refers to Spring version 3.1.0. Spring includes the following: • A flexible MVC web application framework, built on core Spring functionality.
PAGE 17

Spring Web Flow At times, web applications need to execute the same sequence of steps in different contexts. The Spring Web Flow can be used to implement such repetitive steps or flows because it integrates with the Spring Web Model View Control (MVC) platform to provide a flow definition language. For information about downloading and installing the Spring Web Flow, see Appendix E: Installing Spring Web Flow.
PAGE 18

NOTE: NonStop TCP/IPv6 limits one process per processor to listen on any given port, while IP-CIP does not have any such restriction. However, in the RMI Service Exporter configuration the following property must be defined: 2. Spring applications accessing an SQL/MX database. Spring web applications can be configured to access an SQL/MX database through the JDBC drivers (JDBC Type 2 or JDBC Type 4 drivers). 3.
PAGE 19

1. 2. “Downloading the Spring Distribution on Windows” (page 19) “Copying Spring Runtime Libraries from Windows to NonStop” (page 19) NOTE: Throughout the section, references are made to the following directories: • : The directory on the Windows system where the Spring distribution files are extracted. • : The OSS directory on the NonStop system where the Spring runtime JAR files are located.
PAGE 20

OSS> jar -xvf spring_dist.jar NOTE: The sub-directories on the NonStop system must contain the same list of files as those in the \dist directory on the Windows system. The Spring runtime libraries are installed on the NonStop system. You can use these libraries to develop and run Spring applications on a NonStop system. Setting up Sample Spring Applications on NonStop The sample Spring applications (PetClinic and JPetStore) are included in the SAMPLES.zip file.
PAGE 21

• For Windows system: Table 4 Softwares to be installed on the Windows system Software Download JDK version 1.6 Download from http://www.oracle.com/technetwork/java/javase/downloads/index.html and set the PATH and JAVA_HOME environment variables. Maven version 2.2.1 Download from http://maven.apache.org/download.html and set the PATH and MAVEN_HOME environment variables.
PAGE 22

#------------------------------------------------------------# Properties that control the population of schema and data for a new data source # SQL/MX Settings for JDBC Type 4 Driver jdbc.driverClassName= com.tandem.t4jdbc.SQLMXDriver jdbc.url= jdbc:t4sqlmx://: jdbc.username= jdbc.password= jdbc.catalog=petcliniccat jdbc.schema=petclinicsch hibernate.dialect=org.hibernate.dialect.SqlmxDialect 3.
PAGE 23

OSS> mkdir -p /spring/samples/petclinic/dbconfig For example: OSS> mkdir -p /home/sash_usr/sash/spring/samples/petclinic/dbconfig NOTE: can be any working directory. It is suggested that you create spring/samples/petclinic/dbconfig directory structure in . 3. Copy the following scripts from the \spring\samples\petclinic\src\main\resources\db\mxci\ Windows directory to the OSS directory created in Step 2: • petclinic_tables_script.
PAGE 24

• Add a new pet to the system • View information about the pet's visit to the clinic JPetStore The intended users of the JPetStore sample application are Visitors and Shoppers. A Visitor is anyone who visits the site. A Shopper is an authenticated visitor who is signed in to the site. Visitors can browse the site for items of their interest. Shoppers can purchase items of their interest. NOTE: The JPetStore sample application described here uses Spring 3.0.2 version.
PAGE 25

3. Build the JPetStore WAR file (org.springframework.samples.jpetstore-1.0.0-SNAPSHOT.war). 1. Go to the \spring\samples\jpetstore directory: command prompt> cd \spring\samples\jpetstore 2. Build the JPetStore web archive using the JDBC Type 2 driver or JDBC Type 4 driver. 1. Enter the following command: command prompt> mvn clean package The application WAR file (org.springframework.samples.jpetstore-1.0.0-SNAPSHOT.
PAGE 26

3. Copy the following scripts from the \spring\samples\jpetstore\db\mxci Windows directory to the OSS directory created in Step 2: • jpetstore_tables_script.sql • jpetstore_dataload_script.sql NOTE: 4. • The jpetstore_tables_script.sql script creates the SQL/MX database catalog, schema, and tables for JPetStore. • The jpetstore_dataload_script.sql script loads the database with sample data. Go to the OSS directory where the jpetstore_tables_script.sql and jpetstore_dataload_script.
PAGE 27

As a shopper, you can perform the following activities (including those performed by a visitor): • Enter a username and password to access your account. • Store shipping information and preferences for your use at future sessions. • Purchase the items collected in a Cart. • Provide payment information.
PAGE 28

6. 7. PROPAGATION_NEVER: Does not support a current transaction; throws an exception if a current transaction exists. PROPAGATION_NESTED: If a current transaction exists, it executes within a nested transaction: otherwise, the behavior is similar to PROPAGATION_REQUIRED. This behavior is not supported on NonStop. Setting up the Sample SpringTMFAdapter on NonStop The sample SpringTMFAdapter is included along with the Spring application. springtmf.
PAGE 29

Table 6 Softwares to be installed on the Windows system Software Download JDK version 1.6 Download from http://www.oracle.com/technetwork/java/javase/downloads/index.html and set the PATH and JAVA_HOME environment variables. JDBC Type 4 driver version For information on installing JDBC Type 4 driver on a Windows system, see JDBC Type 4 Driver Programmer's Reference for SQL/MX. Ant 1.8.2 Download from http://archive.apache.org/dist/ant/binaries/ and set the PATH and ANT_HOME environment variables.
PAGE 30

Dependent Libraries for the Sample TMFAdapter Before executing the sample TMFAdapter application, get the following libraries to the \Samples\TMF_Adapter_Sample\lib directory on Windows. Then transfer these files (via FTP) to the /spring/samples/TMFAdapter/lib/ directory on the NonStop system. Table 7 TMFAdapter Dependent Libraries Dependency JAR Files antlr-2.7.6.jar Source Location \lib\required com.springsource.org.aopalliance-1.0. 0.
PAGE 31

Table 7 TMFAdapter Dependent Libraries (continued) Dependency JAR Files Source Location slf4j-api-1.6.1.jar \lib\required springtmf.jar \SpringTMFAdapter t4sqlmx.jar tmf.jar /jre/lib/ext util.jar jdbcMx.jar /lib Running TMFAdapter on NonStop To run the TMFAdapter application, you can use either JDBC Type 2 driver or JDBC Type 4 driver.
PAGE 32

-Djava.library.path= -Djdbcmx.transactionMode=external com.hp.programmatic.MainProgrammatic where is the location where the JDBC T2 driver is installed. For example, java -cp "/home/sash_usr/spring/samples/TMFAdapter/TMFAdapter_Sample_Programmatic.jar: /home/sash_usr/spring/samples/TMFAdapter/lib/*" -Djava.library.path=/usr/tandem/jdbcMx/current/lib -Djdbcmx.transactionMode=external com.hp.programmatic.
PAGE 33

For example, java -cp "/home/sash_usr/spring/samples/TMFAdapter/TMFAdapter_Sample_Programmatic.jar: /home/sash_usr/spring/samples/TMFAdapter/lib/*" com.hp.programmatic.MainProgrammatic Annotation: java -cp "/spring/samples/TMFAdapter/TMFAdapter_Sample_Annotation.jar:/spring/samples/TMFAdapter/lib/*" com.hp.annotation.MainAnnotation AOP: java -cp "/spring/samples/TMFAdapter/TMFAdapter_Sample_AOP.
PAGE 34

Configuring Spring Applications on NonStop Systems This section provides information about configuring Spring applications on NonStop systems.
PAGE 35

For Type 4 Driver: Specify the username and password of your NonStop system. jdbc.username= jdbc.password= Configurations in the applicationContext.xml File Defining the Placeholder for JDBC Driver Class For JDBC Type 2 driver: HP recommends to use com.tandem.sqlmx.SQLMXDataSource as the datasource class. This datasource can be configured as follows: PAGE 36
database properties specified in the applicationContext.xml file with the values specified in the jdbc.properties file during runtime. Modify the applicationContext.xml file for wiring the jdbc.properties file as shown below: classpath:jdbc.
PAGE 37

The POJO Class SimpleService can use @Transactional annotation on its methods. The SimpleService class using the @Transactional annotation is as shown: public class SimpleService { @Transactional public void addRecord(SimpleBean b){ // } public SimpleBean[] getRecords(){ // return null; } } In this case, when the addRecord transaction is invoked, it is invoked under a TMF transaction.
PAGE 38

Configuring Using the Transaction Template The following configuration shows how TmfTransactionManager can be used in a Spring Transaction Template: ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(“txbean.xml"); transactionTemplate = new TransactionTemplate(transactionManager); transactionTemplate.
PAGE 39

Prerequisites • For NonStop system: Table 8 Softwares to be installed on the NonStop system Software For more information: NonStop iTP WebServer version 7.x or later For information on installing and setting up iTP WebServer (secure and non-secure) on a NonStop system, see the iTP Secure WebServer System Administrator's Guide. NSJSP version 6.1 For information on installing and setting up NSJSP on a NonStop system, see the NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator's Guide.
PAGE 40

The following sections describe the steps required to develop, deploy, and run the EmpInfo application. • “Developing EmpInfo on Windows using the Eclipse Galileo IDE” (page 40) • “Deploying EmpInfo on NonStop” (page 87) • “Running EmpInfo on NonStop” (page 89) Developing EmpInfo on Windows using the Eclipse Galileo IDE NOTE: • It is not mandatory for you to use the Eclipse Galileo IDE. You can use any IDE that supports Java.
PAGE 41

2. Click OK. The Eclipse SDK Welcome screen appears. NOTE: D:\sash_usr\spring is the sample workspace used to develop the EmpInfo application. Figure 3 Eclipse SDK Welcome Screen Developing a Basic EmpInfo Application Developing the EmpInfo application using Eclipse Galileo IDE involves the following activities: 1. “Creating a Dynamic Web Project” (page 41) 2. “Creating the index.jsp File” (page 43) 3. “Modifying the index.jsp File” (page 46) 4. “Modifying the web.xml File” (page 47) 5.
PAGE 42

Figure 4 New Project Wizard Dialog Box The New Dynamic Web Project dialog box appears. 3. In the Project name field, type EmpInfo and click Finish. NOTE: The other fields in the New Dynamic Web Project dialog box are selected by default.
PAGE 43

When prompted, change the perspective to Java EE and click Yes to open the new perspective. NOTE: The perspective must be changed to Java EE because the Dynamic Web Project is associated with the Java EE perspective. The Project Structure appears. 4. In the Project Structure, ensure that the JRE System Library is set to JRE version 1.6 or later, as shown in Figure 6. If the JRE version is not set to 1.6, right-click JRE System Library to select JRE 1.6. NOTE: The JRE version used in this example is 1.6.
PAGE 44

Figure 7 New File Dialog Box The New JavaServer Page dialog box appears. 3. 44 In the File name field, type index and ensure that the parent folder is set to EmpInfo/WebContent. Click Next.
PAGE 45

Figure 8 New JavaServer Page Dialog Box The New JavaServer Page: Select JSP Template dialog box appears. 4. From the Select JSP Template dialog box, select New JSP File (html) and click Finish. NOTE: The Use JSP Template check box is selected by default.
PAGE 46

Figure 9 New JavaServer Page: JSP Template Dialog Box The template for the index.jsp file is generated. Modifying the index.jsp File Add the header item and body content in the JSP file as shown: <%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%>
PAGE 47

Welcome to the EmpInfo Application

This is EmpInfo Test Page.
The code of the EmpInfo application developed so far is located in \spring\getting-started\EmpInfo-InParts\Part-1. At this point, you can either deploy and verify the EmpInfo application you have developed so far on the NonStop system, or you can proceed with the steps for modifying the web.xml file.
PAGE 48

EmpInfo *.htm NOTE: This servlet definition maps to the application patterns. Any URL with the .htm extension is routed to the EmpInfo servlet (the DispatcherServlet). After modification, the web.xml file appears as: PAGE 49
2. From the list of folders, select XML > XML and click Next. Figure 10 New File Wizard Dialog Box The New XML File dialog box appears. 3. In the File name field, type EmpInfo-servlet.xml and ensure that the parent folder is set to EmpInfo/WebContent/WEB-INF. Click Next.
PAGE 50

Figure 11 New XML File Dialog Box The New XML File: Options dialog box appears. 4. 50 Select Create XML file from an XML template and click Finish.
PAGE 51

Figure 12 New XML File: Options Dialog Box The EmpInfo-servlet.xml file is created in the EmpInfo/WebContent/WEB-INF directory. 5. Modify the EmpInfo-servlet.xml file by adding a bean entry named insert.htm and com.hp.empinfo.web.EmployeeController as its class. NOTE: The com.hp.empinfo.web.EmployeeController class provides controller for the EmpInfo application to service a request according to its corresponding URL mapping in /insert.htm.
PAGE 52

http://www.springframework.org/schema/jee/spring-jee-2.5.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd"> Adding Dependency JAR Files in the Project Library Path Because the EmpInfo application uses the Spring framework, it requires the following dependency JAR files. Table 10 Spring Dependency JAR Files Dependency JAR Files com.springsource.org.apache.commons.
PAGE 53

Figure 13 Java Build Path Dialog Box 5. Click OK. The dependency JAR files are added in the EmpInfo project library path. To resolve the J2EE module dependency on these JAR files, complete the following steps on the Eclipse Galileo IDE: 1. In the Project Explorer frame, right-click EmpInfo and select Properties. The Project Properties dialog box appears. 2. 3. From the type filter text, select J2EE Module dependencies. Select all the dependency JAR files.
PAGE 54

Figure 14 J2EE Module Dependencies Dialog Box 4. Click OK. The J2EE module dependency on the JAR files is resolved. Creating the Controller for EmpInfo In the Spring Web MVC framework, the controller handles the request and returns a ModelAndView . Create the Controller to handle the navigation logic and to interact with the service tier of the business logic. To create the Controller, complete the following steps: 1. “Create the Package for the Controller Class” (page 54) 2.
PAGE 55

Figure 15 New Java Package Dialog Box 3. Click Finish. The com.hp.empinfo.web package is created. Create the Controller Class 1. 2. 3. In the Project Explorer frame, right-click EmpInfo and select New >Class. In the Package field, type com.hp.empinfo.web. In the Name field, type EmployeeController. In the Superclass field, type org.springframework.web.servlet.mvc.SimpleFormController and click Finish. NOTE: The Controller class EmployeeController extends the SimpleFormController class in the org.
PAGE 56

Figure 16 New Java Class Dialog Box The EmployeeController.java class file is created. 4. Modify the EmployeeController.java class file to create a basic controller. After modification, the EmployeeController.java file appears as: package com.hp.empinfo.web; import org.springframework.web.servlet.mvc.SimpleFormController; import org.springframework.web.servlet.ModelAndView; import javax.servlet.ServletException; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.
PAGE 57

logger.info("Returning hello view"); return new ModelAndView("insert.jsp"); } } Your basic controller implementation is ready. This controller is expanded further to add more functionality to the EmpInfo application. Creating the View After completing the controller implementation for EmpInfo, complete the following steps to create the first view of the EmpInfo application: 1. Create a new JSP page insert.jsp in EmpInfo/WebContent by completing the steps explained in “Creating the index.
PAGE 58

Configuring the JSP Standard Tag Library (JSTL) This 1. 2. 3. 4. section involves the following activities: “Creating a folder to store JSPs” (page 58) “Creating the include.jsp File” (page 58) “Modifying the index.jsp File” (page 59) “Modifying the insert.jsp File” (page 59) To configure the JSTL, complete the following steps: Creating a folder to store JSPs 1. In the Project Explorer frame, right-click EmpInfo and select New > Folder. A New Folder dialog box appears. 2.
PAGE 59

2. Add the tag extensions (taglibs) to include the.jsp file so that the include.jsp file appears as: <%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%> <%@ page session="false"%> <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %> <%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %> <%@ taglib prefix="form" uri="http://www.
PAGE 60

<%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%> <%@ include file="/WEB-INF/jsp/include.
PAGE 61

import javax.servlet.http.HttpServletResponse; import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; import java.io.IOException; import java.util.Date; public class EmployeeController extends SimpleFormController { protected final Log logger = LogFactory.getLog(getClass()); public ModelAndView handleRequest(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { String now = (new Date()).toString(); logger.
PAGE 62

http://://EmpInfo. Developing Business Logic and Providing the Web Interface This 1. 2. 3. 4. section describes the following tasks: “Creating a Simple POJO” (page 62) “Creating Data Access Object Implementation for JDBC” (page 63) “Creating and Modifying Supporting Views to Display Business Data” (page 63) “Adding Dependency JAR Files” (page 64) Creating a Simple POJO 1. 2. Create a com.hp.empinfo.
PAGE 63

Creating Data Access Object Implementation for JDBC 1. 2. Create a com.hp.empinfo.service package and an EmployeeDao class under the com.hp.empinfo.service package, as described in “Creating the Controller for EmpInfo” (page 54). This will contain the logic for handling Employee Database Transactions. Modify the EmployeeDao.java class file to add the function for inserting employee details. After modification, the EmployeeDao.java file must appear as: package com.hp.empinfo.service; import java.sql.
PAGE 64

PAGE 65

NOTE: The jar file mentioned in the above table can be found in the following spring repository: http://ebr.springsource.com/repository/app/. To add the dependency JAR file in the project library path and to resolve the J2EE module dependency on it, follow the instructions described in “Adding Dependency JAR Files in the Project Library Path” (page 52).

PAGE 66

6. 7. “Adding Dependency JAR Files” (page 71) “Creating Database Catalog, Schema, and Tables on NonStop” (page 71) Creating the applicationContext.xml File 1. 2. 3. Create the applicationContext.xml file in the EmpInfo/WebContent/WEB-INF/ directory, as described in “Creating the EmpInfo-servlet.xml File” (page 48). Create a new XML file in the EmpInfo/WebContent/WEB-INF directory and type the name of the XML file as applicationContext. Modify the applicationContext.

PAGE 67

Figure 19 New File Dialog Box The jdbc.properties file is created.

PAGE 68

3. Modify the jdbc.properties file based on the JDBC driver type you use: • If you use the JDBC Type 2 driver, the SQL/MX settings for JDBC Type 2 driver in the jdbc.properties file must appear as: #---------------------------------------------------------------------------# SQL/MX Settings for JDBC Type 2 Driver jdbc.url=jdbc:sqlmx:// jdbc.driver=com.tandem.sqlmx.SQLMXDriver jdbc.user= jdbc.password= jdbc.catalog=empinfocat jdbc.

PAGE 69

http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-2.5.xsd http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-2.5.xsd http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd"> insert com.hp.empinfo.

PAGE 70

3. Add the following import statements to include the classes used in the controller. import import import import import import import com.hp.empinfo.domain.Employee; com.hp.empinfo.service.EmployeeDao; org.springframework.web.context.WebApplicationContext; org.springframework.web.context.support.WebApplicationContextUtils; java.sql.SQLException; java.util.HashMap; java.util.Map; After incorporating the above modifications, the EmployeeController.java controller class must appear as: package com.hp.

PAGE 71

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"> EmpInfo index.jsp EmpInfo org.springframework.web.servlet.

PAGE 72

NOTE: The database catalog, schema, and table creation script empinfo_tables_script.sql is included in the SAMPLES.zip file. For information on the empinfo_tables_script.sql, see “EmpInfo Database Script” (page 319). To create a database catalog, schema, and table on NonStop, complete the following steps: 1. Copy the empinfo_tables_script.sql script from the \spring\getting-started\dbconfig Windows directory to the /spring/my_samples/empinfo/dbconfig OSS directory. 2.

PAGE 73

Figure 20 Project Explorer View The code of the EmpInfo application developed so far is located in \spring\getting-started\EmpInfo-InParts\Part-6. At this point, you can either deploy and verify the EmpInfo application you have developed so far on the NonStop system, or you can proceed to the “Enabling EmpInfo to Delete and Retrieve Employee Details” (page 73) section. For deployment, see the steps described in “Deploying EmpInfo on NonStop” (page 87).

PAGE 74

6. 7. 8. “Modifying the EmpInfo-servlet.xml File” (page 78) “Modifying the index.jsp File” (page 79) “Implementing the RMI Service in EmpInfo” (page 80) Creating JSPs to Delete and Retrieve Employee Details To delete or retrieve any employee details in the EmpInfo application, you must create and modify the following files: • retrieveordelete.jsp • retrieveresult.jsp • 1. deleteresult.jsp Create the files in the EmpInfo/WebContent/WEB-INF/jsp directory, as described in “Creating the index.

PAGE 75

">Back 4. Modify the deleteresult.jsp file to remove the details of an employee record from the JSP page as follows: <%@ include file="/WEB-INF/jsp/include.jsp"%> <%@ taglib prefix="form" uri="http://www.springframework.

PAGE 76

After modification, the EmployeeDao.java file appears as: package com.hp.empinfo.service; import import import import java.sql.SQLException; org.springframework.jdbc.core.support.JdbcDaoSupport; com.hp.empinfo.domain.Employee; com.hp.empinfo.domain.EmployeeRowMapper; public class EmployeeDao extends JdbcDaoSupport { public Employee getDetail(int empid) throws SQLException { Employee employee; employee = (Employee) getJdbcTemplate().

PAGE 77

} public String getLastname () { return lastname; } public void setLastname (String lastname) { this. lastname= lastname; } public int getAge () { return age; } public void setAge (int age) { this. age= age; } public String getEmail () { return email; } public void setEmail (String email) { this. email= email; } } Modifying the EmployeeController.java File The EmployeeController.java file in the com.hp.empinfo.

PAGE 78

model.put("empln", emp1.getLastname()); model.put("empage", "" + emp1.getAge()); model.put("empemail", emp1.getEmail()); return new ModelAndView("retrieveresult", "model", model); } if (rord!=null && rord.equalsIgnoreCase("Delete")) { String str = empdao.deleteEmployee(empid); Map model = new HashMap(); model.put("del", str); return new ModelAndView("deleteresult", "model", model); } else { empdao.

PAGE 79

retrieveordelete com.hp.empinfo.domain.Employee emprord PAGE 80
Figure 21 Project Explorer View Implementing the RMI Service in EmpInfo This 1. 2. 3. 4. 5. 6. 7. contains the following activities: Creating RMI Service Interface Creating Implementation Class of RMI service Modify applicationContext.xml file Creating Test class to Test the RMI service Creating the clientContext.xml file Creating the client.properties file Adding Dependency JARs Creating RMI Service Interface 1. 80 Create a com.hp.empinfo.

PAGE 81

2. Modify the EmployeeInfo.java file as follows: package com.hp.empinfo.service; import com.hp.empinfo.domain.Employee; public interface EmployeeInfo { public Employee getEmployee(int empId); }. This creates the RMI service interface which you must implement as described in the subsequent section. Creating Implementation Class of RMI service Interface 1. 2. Create a com.hp.empinfo.service package and an EmployeeInfoImpl class under it, as described in “Creating the Controller for EmpInfo” (page 54).

PAGE 82

Creating Test class to Test the RMI service 1. 2. Create a com.hp.empinfo.domain package and an RmiClientTest class under it, as described in “Creating the Controller for EmpInfo” (page 54). Modify the RmiClientTest.java file to invoke the RMI service by adding the following code: package com.hp.empinfo.domain; import org.springframework.context.ApplicationContext; import org.springframework.context.support.ClassPathXmlApplicationContext; import com.hp.empinfo.service.

PAGE 83

Table 15 Aopalliance Dependency JAR Files Dependency JAR Files com.springsource.org.aopalliance-1.0.0.jar NOTE: The jar file mentioned in the above table can be found in the following spring repository: http://ebr.springsource.com/repository/app/. To add the dependency JAR files in the project library path and to resolve the J2EE module dependency on these JAR files, follow the instructions described in “Adding Dependency JAR Files in the Project Library Path” (page 52).

PAGE 84

To insert an employee record: 1. Start the iTP WebServer and access the index page: http://>:<//EmpInfo. Figure 23 EmpInfo: Insert, Retrieve or Delete Employee Details 2. 3. Click Insert Employee. The Enter Employee Details screen appears. Type the employee details and click Insert. Figure 24 EmpInfo: Employee Details Screen The Insert Operation Successfully Executed message is displayed.

PAGE 85

Figure 25 EmpInfo: Message Screen 4. To retrieve or delete an employee record: Click Retrieve or Delete in the index page. Figure 26 EmpInfo: Retrieve Screen 5. To retrieve an employee record, in the Action to Perform field, type Retrieve. Click Retrieve/Delete. The employee record details are displayed.

PAGE 86

Figure 27 EmpInfo: Employee Details Screen 6. Click Back to return to the EmpInfo: Delete screen. Figure 28 EmpInfo: Delete Screen 7. To delete an employee record, in the Action to Perform field, type Delete. Click Retrieve/Delete. The employee record is deleted.

PAGE 87

Figure 29 EmpInfo: Deleted Screen Deploying EmpInfo on NonStop This section describes the following tasks: 1. “Creating the Application WAR File on Windows” (page 87) 2. “Deploying the EmpInfo WAR File in NSJSP on NonStop” (page 89) Creating the Application WAR File on Windows A WAR file is essential to deploy the web application. It contains property and configuration files, Java class file, and JSPs of the web application. To create the application WAR file: 1.

PAGE 88

Figure 30 Export Dialog Box The WAR Export dialog box appears. 3. 88 In the Web project field, type EmpInfo and browse to the destination where you want to save the WAR file.

PAGE 89

Figure 31 WAR Export Dialog Box 4. Click Finish. The WAR file is created. NOTE: If you have specified an existing name for the WAR file, the Finish button is disabled. In this case, change the name of the WAR file. If you want use the existing name, select the Overwrite existing file check box. Deploying the EmpInfo WAR File in NSJSP on NonStop To deploy the EmpInfo WAR file on the NonStop system, see “Deploying Sample Applications on NonStop” (page 331).

PAGE 90

3 Hibernate Framework Hibernate Overview Hibernate is an object-relational mapping (ORM) tool for Java environments that provides a framework for mapping a data representation from an object model to a relational data model with an SQL-based schema. Hibernate provides configuration files to map Java classes with database tables, and to configure database connectivity properties, such as the database URL, database credentials, connection pooling configuration parameters, and so on.

PAGE 91

The Hibernate EntityManager implements the following: • Standard Java Persistence management API • Standard Java Persistence Query Language • Standard Java Persistence object lifecycle rules • Standard Java Persistence configuration and packaging You can implement a complete EJB3 persistence solution using Hibernate Annotations and the Hibernate EntityManager with the Hibernate package. NOTE: The EJB3 specification is supported on Java 5.0 and above versions.

PAGE 92

3. The Application layer passes the request to the persistence layer (that is, Hibernate). Hibernate establishes connection with the database, performs database operations (such as create, update, retrieve, and delete), and then returns persistent object to the application. NOTE: Persistent objects are the Java classes, which are mapped with database tables. Installing the Hibernate Framework This section describes the procedure to install Hibernate framework libraries on a Nonstop system.

PAGE 93

Downloading the Hibernate Distribution on Windows NOTE: 1. 2. The Hibernate distribution described here is for Hibernate version 4.1.1. Go to http://www.hibernate.org/downloads.html. Click on the release bundles hyperlink under Release bundle section. A web page from sourceforge.net,showing various Hibernate packages that can be downloaded, appears. 3. Click hibernate4, and then click on 4.1.1.Final. The links to the following files appear: 4. • hibernate-release-4.1.1.Final.

PAGE 94

The DIALECT file (which includes hibernate4sqlmx.jar) is distributed as a part of the SQL/MX Hibernate Dialect - T0873AAD and can be downloaded from Scout. To obtain the hibernate4sqlmx.jar file, complete the following steps: 1. Download the DIALECT file from Scout. For information on how to download from Scout, see https://h20453.www2.hp.com/scout/download_help.htm. 2. Add the .zip extension to it. 3. Extract the DIALECT.zip file to a location on the Windows system.

PAGE 95

5. 6. Transfer the hibernate_Dependency.jar files from C:\Documents and Settings\ to the OSS root directory. Extract hibernate_Dependency.jar: OSS> cd OSS> jar -xvf hibernate_Dependency.jar The Hibernate framework libraries are installed on the NonStop system. You can use these libraries to develop and run Hibernate applications on a NonStop system.

PAGE 96

All generators implement the interface org.hibernate.id.IdentifierGenerator. Some applications may have their own specialized implementations; however, Hibernate provides a range of built-in implementations, such as increment, identity, sequence, hilo, Seqhilo, uuid, guid, native, assigned, select, foreign, and sequence-identity. You can use any of the built-in implementations except sequence, guid, native, and sequence-identity.

PAGE 97

When the SQL/MX table contains the identity column and the mapping does not specify the generator class as “identity or "org.hibernate.dialect.SqlMxIdentityGenerator “, then the dialect returns the following errors which are captured in the log: Exception in thread "main" org.hibernate.exception.GenericJDBCException: could not insert: Caused by: com.tandem.t4jdbc.SQLMXException: *** ERROR[3428] IDENTITY column ID defined as GENERATED ALWAYS cannot accept values specified by the user.

PAGE 98

Session s = sf.openSession(); Query q = s.createSQLQuery("select * frm address"); try { List s2 = q.list(); } catch (HibernateException e) { // Customers must get the corresponding SQL Exception using getCause(). If they want to build recovery mechanism, then the Customer must have SQLMX specific error codes compared with error code in the SQLException object embedded in HibernateException which will make the hibernate code SQLMX specific. } When the converter is implemented then, try { List s2 = q.

PAGE 99

NOTE: The SAMPLES.zip file is distributed as a part of the NonStop Samples for Java frameworks - T0874. SAMPLES.zip is present in the T0874AAB.BIN file in Scout. For information on how to install the T0874AAB.BIN file from Scout, see https://h20453.www2.hp.com/scout/download_help.htm. Before you deploy the sample applications, complete the following steps: 1. Download the SAMPLES file from Scout. 2. Add the .zip extension to it. The file is renamed as SAMPLES.zip. 3. Extract the SAMPLES.

PAGE 100

Caveat Emptor The Caveat Emptor sample application is an auction system. The intended users of the application are bidders and the sellers of various items. NOTE: The Caveat Emptor sample application described here uses Hibernate 3.5.1 version.

PAGE 101

NOTE: The hibernate.properties file, located in \hibernate\samples\eg\src\main\resources, has the database catalog name set toauctioncat and schema name set to auctionsch. If the database catalog name auctioncat and schema name auctionsch already exists, or if you want to use a different database catalog and schema name, modify the following: 3. ◦ values for the hibernate.connection.catalog and hibernate.connection.schema property in the hibernate.properties file.

PAGE 102

NOTE: can be any working directory. It is suggested that you create the hibernate/samples/eg/dbconfig directory structure in . 3. 4. Copy the caveatemptor_script.sql script from the \hibernate\samples\eg\dbconfig Windows directory to the OSS directory created in Step 2. Go to the OSS directory where the caveatemptor_script.sql script is copied, and create the Caveat Emptor database catalog, schema, and tables: OSS> obey caveatemptor_script.

PAGE 103

3. 4. Copy the setenv script file from \hibernate\samples\eg\setup to /hibernate/samples/eg/setup. Set the execute permissions of the setenv script file: OSS> chmod +x setenv 5. Run the setenv script file: • To use the JDBC Type 2 driver, type: OSS> . ./setenv T2 • To use the JDBC Type 4 driver, type: OSS> . ./setenv T4 Deploying Caveat Emptor on NonStop To deploy Caveat Emptor on a NonStop system, transfer the application JAR file (caveatemptor.

PAGE 104

1. 2. Go to the \hibernate\samples\web\src\main\resources directory on the Windows system. Modify the hibernate.properties file to update the JDBC configuration.

PAGE 105

The hibernate-tutorial-web-3.5.0-CR-2.war file is created in the \hibernate\samples\web\target directory. 2. 3. 4. Create the WEB-INF\lib folder in the \hibernate\samples\web\target directory. Copy the hibernate35sqlmx.jar file to the \hibernate\samples\web\target\WEB-INF\lib directory.

PAGE 106

3. 4. Copy the eventmanager_script.sql script from the \hibernate\samples\web\dbconfig Windows directory to the OSS directory created in step 2. Go to the OSS directory where the eventmanager_script.sql script is copied, and create the EventManager database catalog, schema, and tables: OSS> obey eventmanager_script.sql; NOTE: By default, the eventmanager_script.sql script file creates the database catalog eventcat and schema eventsch.

PAGE 107

Configuring the JDBC Type 2 or Type 4 Driver for SQL/MX Database In a typical Hibernate application, you can configure the JDBC Type 2 or Type 4 driver for the SQL/MX database by configuring either the hibernate.cfg.xml file or the hibernate.properties file. • “Configuring the JDBC Type 2 or Type 4 Driver for the SQL/MX Database using hibernate.cfg.xml” (page 107) • “Configuring JDBC Type 2 or Type 4 Driver for SQL/MX Database using hibernate.

PAGE 108

... ... NOTE: The significance of the tag is explained in “Opening a Session for Database Operation” (page 109). Defining the Connection URL After you have specified the JDBC driver, enter the location of the SQL/MX server. URLs referring to SQL/MX use the jdbc: protocol and have the server host, port number embedded within the URL.

PAGE 109

The basic configuration is ready for you to perform database operation using Hibernate. Opening a Session for Database Operation Opening a new session for database transaction involves: 1. “Configuring SessionFactory in the hibernate.cfg.xml File” (page 109) 2. “Creating a New Session from the SessionFactory in your Java Program” (page 109) Configuring SessionFactory in the hibernate.cfg.xml File Add the following lines to configure the Hibernate SessionFactory.

PAGE 110

Specifying the JDBC Driver Class for SQL/MX Database For Type 2 Driver: Specify com.tandem.sqlmx.SQLMXDriver as the JDBC Type 2 driver class for the SQL/MX database as shown: hibernate.connection.driver_class_com.tandem.sqlmx.SQLMXDriver For Type 4 Driver: Specify com.tandem.t4jdbc.SQLMXDriver as the JDBC Type 4 driver class for the SQL/MX database as shown: hibernate.connection.driver_class com.tandem.t4jdbc.

PAGE 111

public void databaseCon() { Configuration cfg = new Configuration(); factory = cfg.buildSessionFactory(); ... ... ... } Creating a New Session from the SessionFactory in Java Add the following lines to your Java program to create a new session from the SessionFactory: Session s = factory.openSession(); This will create the session which will be used further in your application to perform database operation. NOTE: To view the complete configuration snippet of the hibernate.

PAGE 112

1. Define a JTA user transaction. javax.transaction.UserTransaction tx = null; 2. Initialize the user transaction. tx = com.tandem.jta.JTAFactory.getUserTransaction(); 3. Begin the transaction. tx.begin(); 4. Commit or rollback the transaction depending upon the status of the operations performed. tx.commit(); or tx.rollback(); Configurations using JDBC To use JDBC Transaction Manager, complete the following steps: 1. Open the session. Session session = factory.openSession(); 2.

PAGE 113

Connection pooling using C3P0 Table 20 Property settings for C3P0 connection pooling Property meaning Property Example value Maximum number of database connections to open hibernate.c3p0.max_size 15 Initial number of database connections hibernate.c3p0.min_size 3 Maximum idle time for a connection (in seconds) hibernate.c3p0.timeout 5000 Maximum size of c3p0 statement cache (0 to turn off) hibernate.c3p0.

PAGE 114

jdbc-0.proxool.alias=property jdbc-0.proxool.driver-url=jdbc:t4sqlmx://: jdbc-0.proxool.driver-class=com.tandem.t4jdbc.SQLMXDriver jdbc-0.user= jdbc-0.password= jdbc-0.proxool.maximum-connection-count=15 jdbc-0.proxool.minimum-connection-count=5 For a list of Proxool properties, see http://proxool.sourceforge.net/properties.html. Using JNDI datasource with C3P0 connection pooling Steps to use JNDI datasource with C3P0 connection pooling are as follows: 1.

PAGE 115

false org.hibernate.dialect.SqlmxDialect 1000 update true NOTE: com.mchange.v2.c3p0.ComboPooledDataSource is part of jar file located in < Hibernate Home>\lib\optional\c3p0 The jar file is c3p0-0.9.1.

PAGE 116

2. Include Regex Patterns by creating the BrowseAccessIncludeExcludeList.xml file, and add it to the CLASSPATH (place this file with hibernate.properties/ hibernate.cfg.xml files). Copy the following into BrowseAccessIncludeExcludeList.xml file.

Employee Id :

First Name :

Last Name :

Age :

Employee Id :
First Name :
Last Name :
Age :