User Manual

Manuals Brands HP Manuals Computer Hardware Integrity NonStop J-Series

Open Source Java Frameworks on NonStop

User's Guide (Spring 3.0.2, Hibernate

3.5.1, MyFaces 2.0.2, Axis2/Java 1.5.2)

HP Part Number: 641664-002

Published: February 2012

Edition: J06.03 and subsequent J-series RVUs and H06.06 and subsequent H-series RVUs.

Summary of content (470 pages)

PAGE 1

Open Source Java Frameworks on NonStop User's Guide (Spring 3.0.2, Hibernate 3.5.1, MyFaces 2.0.2, Axis2/Java 1.5.2) HP Part Number: 641664-002 Published: February 2012 Edition: J06.03 and subsequent J-series RVUs and H06.06 and subsequent H-series RVUs.
PAGE 2

© Copyright 2011 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.....................................................................................8 Supported Release Version Updates (RVUs)..................................................................................8 Intended Audience....................................................................................................................8 New and Changed Information in This Edition..............................................................................
PAGE 4

5 Getting Started with Spring....................................................................75 Prerequisites......................................................................................................................75 NonStop System...........................................................................................................75 Windows System...........................................................................................................75 Overview of EmpInfo...........
PAGE 5

Modifying the Hibernate Application.............................................................................191 Enabling Browse Access...................................................................................................191 Hibernate Applications................................................................................................191 Spring and Hibernate Applications................................................................................
PAGE 6

H Installing MyFaces Trinidad Framework Libraries on NonStop...................285 Downloading MyFaces Trinidad Distribution........................................................................285 Copying MyFaces Trinidad Runtime Libraries from Windows to NonStop.................................285 I Installing MyFaces Tomahawk Framework Libraries on NonStop.................286 Downloading MyFaces Tomahawk Distribution on Windows..................................................
PAGE 7

Contract-First approach................................................................................................336 V Integrating Frameworks...........................................................................346 18 Using Spring Transaction Manager......................................................348 Why Transaction Management is required..........................................................................348 Spring Transaction Management...............................................
PAGE 8

About This Document This manual provides information on how Spring, Hibernate, MyFaces, and Axis2/Java frameworks can be used to develop applications that can run on the HP NonStop™ platform. The frameworks are described with respect to their installation, configuration, and use on NonStop systems. For detailed information about a framework, see the links to online and public resources provided in the relevant sections.
PAGE 9

prerequisite software and hardware required to install and configure Hibernate and Spring on NonStop systems.
PAGE 10

Appendix E: Customizing Sample Applications This appendix details the customizations made in the Hibernate sample applications: Caveat Emptor and EventManager. Appendix F: JDBC Configuration This appendix describes the consolidated JDBC Type 2 driver configuration and the JDBC Type 4 driver configuration in the hibernate.cfg.xml and hibernate.properties files. Appendix G: Hibernate Environment Setup Script This appendix contains the ei_setenv script.
PAGE 11

Notation Conventions 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: MAXATTACH Italic Letters Italic letters, regardless of font, indicate variable items that you supply. Items not enclosed in brackets are required.
PAGE 12

{ } Braces A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list can be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces.
PAGE 13

!i,o In procedure calls, the !i,o notation follows an input/output parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ; !i,o !i:i In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes.
PAGE 14

process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } | Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK | Failed } % Percent Sign A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number.
PAGE 15

Computer Type Computer type letters within text indicate case-sensitive keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.sh Bold Text Bold text in an example indicates user input typed at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. [ ] Brackets Brackets enclose optional syntax items.
PAGE 16

"{" module-name [, module-name]... "}" Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: DAY (datetime-expression) DAY(datetime-expression) If there is no space between two items, spaces are not permitted. In this example, no spaces are permitted between the period and any other items: myfile.
PAGE 17

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 18

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 19

• JDBC Type 2 Driver for NonStop SQL/MX - enables Java applications to use HP NonStop SQL/MX to access NonStop SQL databases. • NonStop Server for Java (NSJ) - is a Java environment that supports compact, concurrent, dynamic, and portable programs for NonStop systems. NonStop iTP WebServer • You must have either of the following versions of iTP WebServer installed on the NonStop system: ◦ non-secure: version T8996H02 or later ◦ secure: version T8997H02 or later To verify the version: 1.
PAGE 20

If you do not have iTP WebServer deployed on the NonStop system, create your own iTP WebServer deployment: 1. Go to the /usr/tandem/webserver/ directory on OSS: OSS> cd /usr/tandem/webserver 2. 3. Select the iTP WebServer version you want to deploy. Go to the version-specific iTP WebServer installation directory on OSS: OSS> cd where, is the version of the iTP WebServer you want to deploy.
PAGE 21

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. • NSJSP must be deployed on the NonStop system. ◦ ◦ If you have NSJSP deployed on the NonStop system, you should know: – Location of the iTP WebServer deployment directory under which NSJSP is setup. This location will be referred to as .
PAGE 22

2.
PAGE 23

For information on installing NSJ on a NonStop system, see the NonStop Server for Java 6.1 Programmer's Reference Manual. Windows System The following software must be installed on the Windows™ system: • Java Development Kit (JDK) - is a Java development tool kit, which includes the Java Runtime Environment (JRE) that enables you to run Java applications and applets. • Ant - is a Java library and command-line tool used to build Java projects. This tool is required to build Axis2/Java applications.
PAGE 24

3. Click Environment Variables. A list of environment variables appears. 4. If the PATH and JAVA_HOME variables are listed in the User Variables dialog box, verify that: • The PATH variable includes the bin directory of . • The JAVA_HOME variable is set to . If the PATH and JAVA_HOME variables exist, but do not contain the respective directories, do the following: 1.
PAGE 25

4. If the PATH and ANT_HOME variables are listed in the User Variables dialog box, verify that: • The PATH variable includes the bin directory of • The ANT_HOME variable is set to If the PATH and ANT_HOME variables exist but do not contain the respective directories, do the following: 1. Add \bin to PATH, separated by semicolon, and to ANT_HOME. For example: Add C:\ant1.7.
PAGE 26

If the PATH and MAVEN_HOME variables exist but do not contain the respective directories, do the following: 1. Add \bin to PATH, separated by semicolon, and to MAVEN_HOME. For example: Add C:\apache-maven-2.2.1\bin to PATH and C:\apache-maven-2.2.1 to MAVEN_HOME. 2. 3. Click OK. Click Apply Changes. If the PATH and MAVEN_HOME variables do not exist, follow these steps: 1. Click New on the User Variables dialog box. 2.
PAGE 27

1. Go to the \lib directory on the Windows system. command prompt> cd \lib For example: command prompt> cd C:\JDBCT4\lib 2. Verify that the version of JDBC Type 4 driver is T1249V11 or later: command prompt> java -jar t4sqlmx.jar Version procedure: T1249_V11_15MAY05_HP_NONSTOP(TM)_JDBCT4_2005_04_28 For information on installing JDBC Type 4 driver on a Windows system, see the HP NonStop JDBC Type 4 Driver Programmer's Reference Manual.
PAGE 28

1. Add \bin to PATH, separated by semicolon, and to ACE_HOME. For example: Add C:\svn-win32-1.5.4\bin to PATH and C:\svn-win32-1.5.4 to ACE_HOME. 2. 3. Click OK. Click Apply Changes. If the PATH and ACE_HOME variables do not exist, follow these steps: 1. Click New on the User Variables dialog box. 2. Enter the variable name as PATH and variable value as \bin. 3.
PAGE 29

8. Start the SVN server: command prompt> net start svnserver SVN 1.5.4 is now installed and running on the Windows system. NOTE: If want to use the Eclipse Galileo IDE, download the SVN plugin for Eclipse from http:// www.eclipse.org/subversive/downloads.php. Eclipse Galileo IDE You must have Eclipse Galileo IDE version 3.3.1.1 or a later installed on the Windows system. If you do not have the Eclipse Galileo IDE installed on your Windows system, download it from: http://archive.eclipse.
PAGE 30

Part I Spring Framework Part I includes the following chapters: • “Spring Overview” (page 33) This chapter provides an overview of the following: • ◦ Spring projects certified for use on NonStop ◦ Deployment environment for a web application that is written using Spring and accesses data from the SQL/MX database. “Installing the Spring Framework” (page 36) This chapter helps you to install Spring framework libraries and enables you to deploy and run sample Spring applications on your NonStop system.
PAGE 31

Contents 2 Spring Overview......................................................................................33 Spring Projects.......................................................................................................................33 Spring Framework..............................................................................................................33 Spring Web Flow...............................................................................................................
PAGE 32

C JDBC Configuration................................................................................144 D Installing Spring Web Flow......................................................................146 Downloading Spring Web Flow Distribution on Windows..........................................................146 Copying Spring Web Flow Runtime Libraries from Windows to NonStop......................................
PAGE 33

2 Spring Overview Spring is an open source framework that can be used to develop enterprise applications. Its features and functions are packaged in different modules, which facilitate Java application development. It includes a lightweight container that provides a centralized, automated configuration and wiring of your application objects. Spring includes the following: • A flexible MVC web application framework, built on core Spring functionality.
PAGE 34

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 MVC platform to provide a flow definition language. For information about downloading and installing the Spring Web Flow, see Appendix D: Installing Spring Web Flow.
PAGE 35

instances listening on the port in a round-robin manner. If the RMI servers are distributed across all the processors it leads to RMI calls getting distributed across all the processors. NOTE: NonStop TCPIPv6 limits one process per processor to listen on any given port, while IP-CIP does not have any such restriction. 2. Spring applications accessing SQL/MX database. Spring web applications can be configured to access a SQL/MX database through the JDBC drivers (JDBC Type 2 or JDBC type 4 drivers).
PAGE 36

3 Installing the Spring Framework This chapter describes the procedure to install Spring framework libraries on a Nonstop system. It also describes the steps required to deploy and run sample Spring applications, which help you to verify if you have successfully installed Spring on the NonStop system. The following tasks are described in this chapter: 1. “Installing Spring Framework Libraries on NonStop” (page 36) 2.
PAGE 37

3. 4. “Downloading Sample Spring Applications on Windows” (page 38) “Copying Spring Runtime Libraries from Windows to NonStop” (page 39) NOTE: Throughout the chapter, 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 38

\src includes the source of the Spring framework. Downloading Spring Dependency JAR Files on Windows To download the Spring dependency JAR files on the Windows system, complete the following steps: 1. Go to http://www.springsource.com/download/community?project=Spring%20Framework. The Spring Community Downloads web page appears. 2. Do one of the following: 1. Register yourself. 2. Click I'd rather not fill in the form. Just take me to the download page. The Spring frameworks available for download appear.
PAGE 39

Copying Spring Runtime Libraries from Windows to NonStop To copy the Spring runtime libraries from a Windows system to a NonStop system, complete the following steps: 1. Go to and create JAR files of \dist and directories on the Windows system: command command command command prompt> prompt> prompt> prompt> cd jar -cvf spring_dist.jar dist cd jar -cvf spring_dependency.
PAGE 40

NOTE: The SAMPLES.zip file is distributed as a part of the NS Samples for Java Frameworks - T0874. SAMPLES.zip is present in the T0874AAB.BIN file in Scout for NonStop Servers. 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.zip file from Scout for NonStop servers. 2. Add the .zip extension to it. The file is renamed as SAMPLES.zip. 3.
PAGE 41

2. Modify the jdbc.properties file to update the JDBC configuration. You can use either the JDBC Type 2 driver or the JDBC Type 4 driver. The SQL/MX settings for each of them is as follows: • To use the JDBC Type 2 driver, uncomment the SQL/MX settings for the JDBC Type 2 driver in the jdbc.properties file, so that the SQL/MX settings for JDBC Type 2 driver appear as: # Properties that control the population of schema and data for a new data source # SQL/MX Settings for JDBC Type 2 Driver jdbc.
PAGE 42

4. Go to \spring\samples\petclinic\target and run the following commands: command prompt> cd \spring\samples\petclinic\target command prompt> jar uf petclinic.war WEB-INF\lib\hibernate3sqlmx.jar The hibernate3sqlmx.jar is copied to \spring\samples\petclinic\target\petclinic.war\WEB-INF\lib. • To use JDBC Type 4 driver: 1. Enter the following command: command prompt> mvn clean package The application WAR file (petclinic.
PAGE 43

3. Copy the following scripts from the \spring\samples\petclinic\ src\main\resources\db\mxci\Windows directory to the /spring/samples/petclinic/dbconfig OSS directory: • petclinic_tables_script.sql • petclinic_dataload_script.sql NOTE: 4. • The petclinic_tables_script.sql script creates the SQL/MX database catalog, schema, and tables for PetClinic. • The petclinic_dataload_script.sql script loads the database with sample data.
PAGE 44

Figure 2 NSJSP Manager Login Screen 2. Enter the User name: and Password: and click OK. The NSJSP Manager screen appears. Figure 3 shows the NSJSP Manager screen.
PAGE 45

3. Select SERVLETS for the Server Class and click Set. The Host (in server.xml) tab is enabled and populated with localhost. Click Set, which enables the Deployment tab on the NSJSP Manager screen. Figure 4 shows the Deployment tab of NSJSP Manager. Figure 4 NSJSP Manager Screen - Deployment tab 4. In the Deployment tab, complete the following steps in the Web Application Deployment from Desktop section: 1. In the Select a .war file to upload field, click Browse... and locate the petclinic.
PAGE 46

• 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. This section describes the following steps for the JPetStore sample application.
PAGE 47

jdbc.username= jdbc.password= jdbc.catalog=jpetstorecat jdbc.schema=jpetstoresch NOTE: must have access to the schema created for JPetstore. 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.
PAGE 48

• : specify the location of the metadata tables for the catalog. For example: \NSK01.$data01. • : specify the designated subvolume name for the schema. For example: SASH2. NOTE: The subvolume name is always prefixed by ZSD and must have eight characters (including ZSD). 2.
PAGE 49

1. Go to http://:/. The NSJSP Manager Login screen appears. Figure 5 shows the NSJSP Manager Login screen. Figure 5 NSJSP Manager Login Screen 2. Enter the User name: and Password: and click OK. The NSJSP Manager screen appears. Figure 6 shows the NSJSP Manager screen.
PAGE 50

Figure 6 NSJSP Manager Screen 3. Select SERVLETS for the Server Class and click Set. The Host (in server.xml) tab is enabled and populated with localhost. Click Set, which enables the Deployment tab on the NSJSP Manager screen. Figure 4 shows the Deployment tab of NSJSP Manager.
PAGE 51

4. In the Deployment tab, complete the following steps in the Web Application Deployment from Desktop section: 1. In the Select a .war file to upload field, click Browse... and locate the org.springframework.samples.jpetstore-1.0.0-SNAPSHOT.war file on the Windows system. 2. (Optional) In the Context name field, enter a name for the application context. 3. Click Deploy. JPetStore is deployed on NSJSP and is listed under Applications tab of the NSJSP Manager screen.
PAGE 52

4 Configuring Spring Applications on NonStop Systems This chapter provides information about configuring Spring applications on NonStop systems and includes the following sections: • “NonStop Platform Configurations” (page 52) • “Spring Framework Configurations” (page 62) • “Module File Caching Configurations” (page 73) NonStop Platform Configurations On a NonStop system, an application developed using the Spring framework is deployed as a web application under the NSJSP container.
PAGE 53

3. 4. 5. Set the value of Maxlinks to 250. This is the maximum number of links to the server process (NSJSP process). This means that the server process must be capable of processing 250 requests simultaneously. Set the value of TANDEM_RECEIVE_DEPTH to 250 (because the values of Maxlinks and TANDEM_RECEIVE_DEPTH should be equal). A value of 250 means that the NSJSP process is able to read a maximum of 250 messages simultaneously from its $RECEIVE file.
PAGE 54

Configuring httpd Processes to Handle Maximum Load The httpd processes are configured using the Server configuration directive in the /conf/httpd.config file on OSS. The Server directive controls the creation of the PATHMON environment, where the webserver runs.
PAGE 55

each of the five static processes can handle 100 requests. In this example, the capacity of the iTP WebServer environment can be summarized as follows: ◦ The static capacity of iTP WebServer is [Numstatic X TANDEM_RECEIVE_DEPTH]= 500. ◦ The dynamic capacity is [(Maxservers - Numstatic) X TANDEM_RECEIVE_DEPTH]= 4500. ◦ The total capacity of iTP WebServer is [Maxservers X TANDEM_RECEIVE_DEPTH]= 5000. Using this configuration, the iTP WebServer can handle 500 simultaneous requests statically.
PAGE 56

After determining the values, you can use any the following approaches to make necessary configurations for the TS/MP parameters of the httpd processes: ◦ Using the default value of TANDEM_RECEIVE_DEPTH ◦ Modifying the value of TANDEM_RECEIVE_DEPTH Using the default value of TANDEM_RECEIVE_DEPTH With TANDEM_RECEIVE_DEPTH set to the default value of 50, the static processes can be configured on the basis of Average Load and dynamic processes can be configured on the basis of Peak Load on your system.
PAGE 57

In this case, the iTP WebServer serves 105 requests (higher multiple of Numstatic nearest to the count value). Here, the 106th request displays the following error message: Maximum connections reached: The server reached its maximum configured capacity. with HTTP response code: 200 OK To customize the error message, create a new message ID error-maximum-connection. This customized message is displayed if the message configuration directive is used in the /conf/httpd.
PAGE 58

NOTE: • The default value of -DSaveSessionOnCreation is false. -DSessionBasedLoadBalancing Enables or disables SessionBasedLoadBalancing. Syntax: -DSessionBasedLoadBalancing=[ true | false ] NOTE: The default value of -DSessionBasedLoadBalancing is set to true.
PAGE 59

that can be processed simultaneously can be controlled by limiting the number of threads that NSJSP Connector can spawn. NOTE: A single connector can service multiple instances of the container. The connector must be configured such that it can spawn threads sufficient for all the container instances. In terms of configuration, the Host element in the server.xml configuration file represents a container that is serviced by the connector.
PAGE 60

1. 2. 3. 4. 5. Numstatic – Determines the number of static NSJSP processes. Maxservers – Determines the total number of NSJSP processes. TANDEM_RECEIVE_DEPTH – Determines the handling capacity of each instance of NSJSP. Maxlinks – Determines the maximum number of TS/MP links. The number of simultaneous messages that can be delivered to an instance of NSJSP is determined by Maxlinks. NSJSP reads these many number of messages from the $RECEIVE file simultaneously. Number of Connector threads.
PAGE 61

processing the timeout requests could still be busy. Therefore, the number of threads that must be configured is (25+25 = 50). NSJSP Configured with SessionBasedLoadBalancing Turned ON • The value of Numstatic must be [(Peak Load)/(Max load one instance of NSJSP can handle)]. • The value of Maxservers must be [(Peak Load)/(Max load one instance of NSJSP can handle)]. This ensures that no dynamic process is created, so that the session object is not lost when there are many File System calls.
PAGE 62

Some of the important Java runtime arguments that you must consider during the deployment of your Spring applications are: • “-Xmx” (page 62) • “-Xss” (page 62) • “-Xnoclassgc” (page 62) There are other Java runtime arguments supported by NSJSP. For more information, see the NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator's Guide. -Xmx Sets the maximum size of the memory allocation pool, which is the garbage collected heap.
PAGE 63

Configuring JDBC Driver for SQL/MX Database The JDBC driver to be used when a Spring application (using Spring DAO) connects to the SQL/MX database needs to be specified in the applicationContext.xml and jdbc.properties file provided by the Spring framework.
PAGE 64

Defining the placeholder for JDBC Type 2 Driver Class Modify the applicationContext.xml file to define a placeholder for the JDBC Type 2 driver class name com.tandem.sqlmx.SQLMXDriver from the jdbc.properties file as shown below. ${jdbc.driver} NOTE: It is recommended to use com.mchange.v2.c3p0.
PAGE 65

Configuring JDBC Type 4 Driver for SQL/MX Database To configure JDBC Type 4 driver for connecting a Spring application with SQL/MX database, complete the following configurations: 1. “Configurations in the jdbc.properties File” (page 65) 2. “Configurations in the applicationContext.xml File” (page 65) NOTE: Verify and install JDBC Type 4 driver version T1249V11 by following the steps discussed in the “Installing the Spring Framework” (page 36) chapter. Configurations in the jdbc.
PAGE 66

${jdbc.driver} NOTE: It is recommended that you use com.mchange.v2.c3p0.ComboPooledDataSource as the datasource class because it provides various parameters for connection pooling. Other available datasource classes are org.apache.commons.dbcp.BasicDataSource provided by Apache DBCP and org.springframework.jdbc.datasource.DriverManagerDataSource provided by Spring framework. Defining the Placeholder for Connection URL Modify the applicationContext.
PAGE 67

Declarative Transaction Management This section describes the following steps to configure transactions in Spring applications using declarative approach: • “Defining the Transactional Object” (page 67) • “Defining the Transactional Advice” (page 68) • “Defining the Transactional Execution Point” (page 68) • “Defining the Transaction Datasource” (page 69) • “Defining the PlatformTransactionManager” (page 69) • “Defining the Transaction Rollback (Optional)” (page 70) NOTE: In a typical Spring app
PAGE 68

Defining the Transactional Advice The next step is to add the transactional advice to the transactional object. The transaction semantics that must be applied are encapsulated in the definition.
PAGE 69

In this case, the definition ensures that the transactional advice defined by the txAdvice bean actually executes at the appropriate points in the program. Define a pointcut that matches the execution of any operation defined in the MyService interface (myServiceOperation). Associate the pointcut with the txAdvice using an advisor. The result indicates that at the execution of a myServiceOperation, the advice defined by txAdvice will be run.
PAGE 70

Defining the Transaction Rollback (Optional) This section describes the steps to control the rollback of transactions in a simple declarative fashion. The recommended way to indicate to the Spring framework transaction infrastructure that a transaction work must be rolled back is to throw an Exception from the code that is currently executing in the context of a transaction.
PAGE 71

// use constructor-injection to supply the PlatformTransactionManager public SimpleService(PlatformTransactionManager transactionManager) { Assert.notNull(transactionManager, "The 'transactionManager' argument must not be null."); this.transactionTemplate = new TransactionTemplate(transactionManager); } public Object someServiceMethod() { return transactionTemplate.
PAGE 72

2. might be a good approach. Being able to set the transaction name explicitly is also something that can only be done using the programmatic approach to transaction management. If your application has numerous transactional operations, declarative transaction management is usually worthwhile. It keeps transaction management out of business logic, and is not difficult to configure.
PAGE 73

Minimum Pool Size The correct minimum value for the pool can be determined by examining the applications that are using the pool. If it is determined, for example, that at least four connections are needed at any point in time, the minimum number of connections should be set to 4 to ensure that all requests can be fulfilled without connection wait timeout exceptions. At off-peak times, the pool shrinks back to this minimum number of connections.
PAGE 74

NOTE: You can configure any number of servers based on your requirement. If you do not specify the number of servers, the default value (maxserver=5, initserver=1, and idleserver=1) is assumed. 3. Stop the datasource: mxci>> stop ds MFC_datasource, reason 'test'; NOTE: status. 4. This step must be performed only if you have a configured datasource in the started To enable the MFC feature, add the statement_module_caching environment variable to the datasource: mxci>> add evar $mcbs."MFC_datasource".
PAGE 75

5 Getting Started with Spring This chapter explains how to develop a web application using Spring. It describes the steps to build a basic employee management system on the Windows system and deploy it on the NonStop system.
PAGE 76

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 an IDE that supports Java. • The screen captures in this section are based on Eclipse Galileo IDE version 3.3.1.1. The screen captures might look different if you use a different version of Eclipse Galileo. The following activities are required to develop the EmpInfo application using the Eclipse Galileo IDE: 1. “Developing a Basic EmpInfo Application” (page 77) 2.
PAGE 77

2. Click OK. To create a new workspace, click Browse and select the folder you want to use as the workspace. The Eclipse SDK Welcome screen appears. NOTE: D:\sash_usr\spring is the sample workspace used to develop the EmpInfo application. Figure 9 Eclipse SDK Welcome Screen Close the welcome screen. The workspace is created. NOTE: The source code for the EmpInfo application is in the SAMPLES.zip file.
PAGE 78

Creating a Dynamic Web Project To create a new Eclipse project for the EmpInfo application, complete the following steps: 1. Click File> New> Project. The New Project dialog box appears. 2. From the list of folders, select Web > Dynamic Web Project and click Next. Figure 10 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: 78 The other fields in the New Dynamic Web Project dialog box are selected by default.
PAGE 79

Figure 11 New Dynamic Web Project Dialog Box When prompted, change the perspective to Java EE and click Yes to open the new perspective. NOTE: The perspective should 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, confirm that the JRE System Library is set to JRE version 1.6 or later, as shown in Figure 12. If the JRE version is not set to 1.6, right-click JRE System Library to select JRE 1.6.
PAGE 80

Figure 12 Project Explorer View Creating the index.jsp File Create the index.jsp file in the EmpInfo/WebContent directory. This JSP page is the entry point EmpInfo. To create the index.jsp file, complete the following steps: 1. On the Project Explorer frame, right-click EmpInfo and select New > Other. The New File dialog box appears. 2. 80 From the list of folders, select Web > JSP and click Next.
PAGE 81

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

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

Figure 15 New JavaServer Page: JSP Template Dialog Box The template for the index.jsp file is generated. Modifying the index.jsp File To modify the index.jsp file, complete the following step: • Modify the EmpInfo/WebContent/index.jsp file to add a header item. Add as the title tag, as the header item and within the body tag of the EmpInfo/WebContent/index.
PAGE 84

Spring Getting Started with EmpInfo Application
Welcome to the EmpInfo Application

This is EmpInfo Test Page.
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 85

1. Double-click the EmpInfo/WebContent/WEB-INF/web.xml file in the Project Explorer frame to open it. NOTE: By default, XML files open in the XML Editor. The XML Editor has two views: Design and Source view. Select the Source view. 2. Open the EmpInfo/WebContent/WEB-INF/web.xml file. The template for the default web.xml file generated during project creation is: PAGE 86
org.springframework.web.servlet.DispatcherServlet 1 EmpInfo *.htm Creating the EmpInfo-servlet.xml File Create a WebApplicationContext file, which contains references to all the web-related components. The name of this file is determined by the value of the element in the web.
PAGE 87

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. Figure 18 New XML File Dialog Box The New XML File: Options dialog box with XML template options appears. 4. Select Create XML file from an XML template and click Finish.
PAGE 88

Figure 19 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 89

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 1 Spring Dependency JAR Files Dependency JAR Files Source Location com.springsource.org.
PAGE 90

Figure 20 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. On the Project Explorer frame, right-click EmpInfo and select Properties. The Project Properties dialog box appears. 2. 3. 90 From the type filter text, select J2EE Module dependencies. Select all the dependency JAR files.
PAGE 91

Figure 21 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 91) 2.
PAGE 92

Figure 22 New Java Package Dialog Box 3. Click Finish. The com.hp.empinfo.web package is created. Create the Controller Class To create the Controller class, complete the following steps: 1. On the Project Explorer frame, right-click EmpInfo and select New >Class. 2. In the Package field, type com.hp.empinfo.web. In the Name field, type EmployeeController. 3. In the Superclass field, type org.springframework.web.servlet.mvc.SimpleFormController and click Finish.
PAGE 93

Figure 23 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 94

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 95

Figure 24 EmpInfo: Employee Details Screen Developing and Configuring Views and the Controller This section describes the process to develop and configure Views and the Controller. Views are provided by JSP pages and the controller has the intelligence to recognize the business logic based on the input provided in the JSP pages. This 1. 2. 3. 4.
PAGE 96

Figure 25 New Folder Dialog Box 3. Click Finish. The jsp folder is created. Creating the include.jsp File To create the include.jsp file, complete the following steps: 1. Create the include.jsp file in the EmpInfo/WebContent/WEB-INF/jsp directory as described in “Creating the index.jsp File” (page 80).
PAGE 97

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 98

After modification, the insert.jsp file appears as: <%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%> <%@ include file="/WEB-INF/jsp/include.
PAGE 99

import org.springframework.web.servlet.ModelAndView; import javax.servlet.ServletException; import javax.servlet.http.HttpServletRequest; 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.
PAGE 100

Figure 27 EmpInfo: Employee Details Screen Decoupling View from the Controller So far, the controller is specifying full path of the view, thereby creating unnecessary dependency between the controller and the view. Ideally, the view must be mapped using a logical name, so that the view can be switched without changing the controller. To decouple the view from the controller, complete the following steps: 1. Modify the EmpInfo-servlet.
PAGE 101

return new ModelAndView("WEB-INF/jsp/insert.jsp", "now", now); After modification: return new ModelAndView("insert", "now", now); After modification, the EmployeeController.java file appears as: package com.hp.empinfo.web; import import import import import import import import import org.springframework.web.servlet.mvc.SimpleFormController; org.springframework.web.servlet.ModelAndView; javax.servlet.ServletException; javax.servlet.http.HttpServletRequest; javax.servlet.http.HttpServletResponse; org.
PAGE 102

Figure 28 EmpInfo: Employee Details Screen Developing Business Logic and Providing the Web Interface This 1. 2. 3. 4. section describes the following tasks: “Creating a Simple POJO” (page 102) “Creating Data Access Object Implementation for JDBC” (page 103) “Creating and Modifying Supporting Views to Display Business Data” (page 103) “Adding Dependency JAR Files” (page 105) Creating a Simple POJO To create a simple POJO, complete the following steps: 1. Create a com.hp.empinfo.
PAGE 103

} public void setFirstname (String firstname) { this. firstname= firstname; } 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.
PAGE 104

"http://www.w3.org/TR/html4/loose.dtd"> <%@ include file="/WEB-INF/jsp/include.jsp"%> Spring Getting Started with EmpInfo Application
Insert Operation Successfully Executed

${model.add}

>Insert Employee
3. Modify the insert.jsp file in the EmpInfo/WebContent/Web-INF/jsp/insert.
PAGE 105

path="firstname"/> width="20%">Last Name : path="lastname"/> width="20%">Age : path="age"/> width="20%">Email : path="email"/> align="left" value="Insert"> Adding Dependency JAR Files Add the following JAR file required for XML parsing: Table 3
PAGE 106

Figure 29 Project Explorer View Integrating the Web-tier of EmpInfo with NonStop SQL/MX Database This 1. 2. 3. 4. 5. 6. 7. section describes the following tasks: “Creating the applicationContext.xml File” (page 106) “Creating the jdbc.properties File” (page 107) “Modifying the EmpInfo-servlet.xml File” (page 109) “Improving the Controller” (page 110) “Modifying the web.
PAGE 107

${jdbc.driver} ${jdbc.
PAGE 108

Figure 30 New File Dialog Box The jdbc.properties file is created.
PAGE 109

3. Modify the jdbc.properties file based on the JDBC driver type you plan to use: • If you plan to 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 110

xmlns:jee="http://www.springframework.org/schema/jee" xmlns:tx="http://www.springframework.org/schema/tx" xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd 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.
PAGE 111

.put("add", "Transaction Complete - One Employee Added to Employee Database"); return new ModelAndView("insertresult", "model", model); } 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.
PAGE 112

org.springframework.web.context.ContextLoaderListener contextConfigLocation /WEB-INF/applicationContext.xml 2. Increase the startup load to 2 after adding the ContextLoaderListener to make DispatcherServlet as the secondary servlet class. The ContextLoaderListener servlet class becomes the primary servlet class. After modification, the web.
PAGE 113

If you plan to use the JDBC Type 4 driver, you must add the JAR file of the JDBC Type 4 driver to the EmpInfo project library. Table 5 JDBC Type 4 Dependency JAR File Dependency JAR File t4sqlmx.jar Source Location \lib 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 89).
PAGE 114

Figure 31 Project Explorer View 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 116) section. NOTE: The code for the EmpInfo application developed so far is located in \spring\getting-started\EmpInfo-InParts\Part-6 To verify the EmpInfo application developed so far, complete the following steps: 1.
PAGE 115

Figure 32 EmpInfo: Insert Employee Screen 3. On the EmpInfo: Insert Employee screen, click Insert Employee . The EmpInfo: Employee Details screen appears. 4. Type the employee details and click Insert. Figure 33 EmpInfo: Employee Details Screen The Insert Operation Successfully Executed message is displayed.
PAGE 116

Figure 34 EmpInfo: Message Screen Enabling EmpInfo to Delete and Retrieve Employee Details This 1. 2. 3. 4. 5. 6. 7. 8. section describes the following activities: “Creating JSPs to Delete and Retrieve Employee Details” (page 116) “Creating the RowMapper Class” (page 118) “Modifying the EmployeeDao.java Class File” (page 119) “Modifying the Employee.java File” (page 119) “Modifying the EmployeeController.java File” (page 120) “Modifying the EmpInfo-servlet.xml File” (page 121) “Modifying the index.
PAGE 117

Welcome to the EmpInfo Application

Enter Employee Id

Employee Id :

Action to Perform (Retrieve/Delete) :

PAGE 118
5. 6. Create the deleteresult.jsp file in the EmpInfo/WebContent/WEB-INF/jsp directory, as described in “Creating the index.jsp File” (page 80). Modify the deleteresult.jsp file to remove the details of an employee record from the JSP page. After modification, the deleteresult.jsp file appears as: <%@ include file="/WEB-INF/jsp/include.jsp"%> <%@ taglib prefix="form" uri="http://www.springframework.
PAGE 119

Modifying the EmployeeDao.java Class File To modify the EmployeeDao.java in com.hp.empinfo.service package, complete the following steps: 1. Add two new methods getDetail and deleteEmployee in the EmployeeDao.java class file to add the retrieve and delete functionality in the application. 2. Add two import statements that are being used in the modified EmployeeDao.java file: import com.hp.empinfo.domain.Employee; import com.hp.empinfo.domain.EmployeeRowMapper; After modification, the EmployeeDao.
PAGE 120

} public int getEmpid() { return empid; } public void setEmpid(int empid) { this.empid = empid; } public String getFirstname() { return firstname; } public void setFirstname (String firstname) { this. firstname= firstname; } public String getLastname () { return lastname; } public void setLastname (String lastname) { this. lastname= lastname; } public int getAge () { return age; } public void setAge (int age) { this.
PAGE 121

String firstname = ((Employee) command).getFirstname(); String lastname = ((Employee) command).getLastname(); int age = ((Employee) command).getAge(); String email = ((Employee) command).getEmail(); String rord = ((Employee) command).getRord(); if (rord!=null && rord.equalsIgnoreCase("Retrieve")) { Employee emp1 = empdao.getDetail(empid); Map model = new HashMap(); model.put("empid", "" + emp1.getEmpid()); model.put("empfn", emp1.getFirstname()); model.put("empln", emp1.
PAGE 122

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.domain.Employee emp PAGE 123
Figure 35 Project Explorer View Implementing the RMI Service in EmpInfo To implement the RMI service in the EmpInfo, complete the following steps: 1. Creating RMI Service Interface. 2. Creating Implementation Class of RMI service. 3. Modify applicationContext.xml file. 4. Creating Test class to Test the RMI service. 5. Creating the clientContext.xml file 6. Creating the client.properties file 7.
PAGE 124

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 To create an implementation class of RMI service, complete the following steps: 1. Create a com.hp.empinfo.
PAGE 125

Creating Test class to Test the RMI service To create the test class that can be used to test the RMI Service, complete the following steps: 1. Create a com.hp.empinfo.domain package and an RmiClientTest class under the com.hp.empinfo.domain package, as described in “Creating the Controller for EmpInfo” (page 91). 2.
PAGE 126

2. Modify the client.properties file to add the NonStop System IP address (where your RMI service is running) and the RMI port number. serverName= rmiPort= Adding Dependency JARs Add the following dependency jars to the EmpInfo project library: Table 6 Aopalliance Dependency JAR Files Dependency JAR Files aopalliance-1.0.jar Source Location \org.aopalliance\ com.springsource.org.aopalliance\1.0.
PAGE 127

The EmpInfo application is complete now. You can now deploy and verify the EmpInfo application on a NonStop system, by following the steps described in “Deploying EmpInfo on NonStop” (page 129). NOTE: The complete code of the EmpInfo application is located in \spring\getting-started\EmpInfo. To verify if the application is working, complete the following steps: 1.
PAGE 128

3. To retrieve an employee record, in the Action to Perform field, type Retrieve. Click Retrieve/Delete. The employee record details are displayed. Figure 39 EmpInfo: Employee Details Screen 4. Click Back to return to the EmpInfo: Delete screen. Figure 40 EmpInfo: Delete Screen 5. To delete an employee record, in the Action to Perform field, type Delete. Click Retrieve/Delete. The employee record is deleted.
PAGE 129

Figure 41 EmpInfo: Deleted Screen Deploying EmpInfo on NonStop This section describes the following tasks: 1. “Creating the Application WAR File on Windows” (page 129) 2. “Deploying the EmpInfo WAR File in NSJSP on NonStop” (page 131) 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, complete the following steps: 1.
PAGE 130

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

Figure 43 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, complete the following steps: 1. Go to http://:/.
PAGE 132

Figure 44 NSJSP Manager Login Screen 2. Enter the User name: and Password: and click OK. The NSJSP Manager screen appears. Figure 45 shows the NSJSP Manager screen.
PAGE 133

3. Select SERVLETS for the Server Class and click Set. The Host (in server.xml) tab is enabled and populated with localhost. Click Set, which enables the Deployment tab on the NSJSP Manager screen. Figure 46 shows the Deployment tab of NSJSP Manager. Figure 46 NSJSP Manager Screen - Deployment tab 4. In the Deployment tab, complete the following steps in the Web Application Deployment from Desktop section: 1. In the Select a .war file to upload field, click Browse... and locate the EmpInfo.
PAGE 134

A EmpInfo Database Script The empinfo_tables_script.sql script file is used to create the SQL/MX database for the EmpInfo application. The content of this file is as follows: Log EmpInfo.log; drop schema empinfocat.empinfosch cascade; drop catalog empinfocat; create catalog empinfocat LOCATION ; create schema empinfocat.empinfosch AUTHORIZATION "" LOCATION ZSD; set schema empinfocat.
PAGE 135

B Customizing Sample Applications This appendix provides information about how PetClinic and JPetStore sample applications were customized to run on NonStop systems. You can download the Spring sample applications from http://src.springframework.org/ svn/ spring-samples. Customizing PetClinic To customize the PetClinic sample application to run on NonStop systems, two directories and one file were added, and four files were modified. Added Directories: • /mxci • /etc Added File: • SetDatabase.
PAGE 136

this.catalog=catalog; addConnectionProperty("catalog",this.catalog); } public void setSchema(String schema) { this.schema=schema; addConnectionProperty("schema",this.schema); } } Modified Files The following files were modified to customize PetClinic. web.xml (\spring\samples\petclinic\src\main\webapp\WEB-INF\web.xml) This is the deployment descriptor configuration file for PetClinic.
PAGE 137

To use the JPA variant above, you will need to enable Spring load-time weaving in your server environment. See PetClinic's readme and/or Spring's JPA documentation for information on how to do this. --> petclinic.hbm.xml (\spring\samples\petclinic\src\main\resources\petclinic.hbm.xml) This Hibernate mapping file is used to map database tables with the corresponding Java objects.
PAGE 138

jdbc.properties (\spring\samples\petclinic\src\main\resources\ jdbc.properties) This configuration file is used for connecting to the SQL/MX database, and was modified to add the SQL/MX JDBC properties to override the default HSQL JDBC properties used by PetClinic. Changes to the jdbc.
PAGE 139

Customizing JPetStore To customize the JPetStore sample application to run on NonStop systems, one file was added and five files were modified. Added File: • SetDatabase.java Modified Files: • Item.xml • dataAccessContext-local.xml • jdbc.properties • Order.xml • Pom.xml Added File The following file was added to customize JPetStore: SetDatabase.java (\spring\samples\jpetstore\src\main\java\org\ springframework\samples\jpetstore\property\SetDatabase.java) The SetDatabase.
PAGE 140

Changes to the Item.xml file Before the change: After the change: dataAccessContext-local.
PAGE 141

jdbc.username=sa jdbc.password= After the change: # Properties file with JDBC-related settings. # Applied by PropertyPlaceholderConfigurer from "dataAccessContext-local.xml". # Targeted at system administrators, to avoid touching the context XML files. #jdbc.driverClassName=org.hsqldb.jdbcDriver #jdbc.url=jdbc:hsqldb:hsql://localhost:9002 #jdbc.username=sa #jdbc.password= #------------------------------------------------------------------------------# SQL/MX Settings for JDBC Type 2 Driver #jdbc.
PAGE 142

Changes to the Pom.xml file The following modifications were made to the POM.xml file: • The Spring-version property in the properties section of the pom.xml file was modified to 3.0.3. Before the change: 3.0.0.BUILD-SNAPSHOT 2.2.0 1.8.0.7 . . . After the change: 3.0.3.RELEASE 2.2.0 1.8.0.
PAGE 143

2.0.7.RELEASE 2.3.4.726 3.2.1 1.4.0 1.6.1 1.2 1.6.5 2.5 2.1 After the change: 3.0.3.RELEASE 2.2.0 1.8.0.
PAGE 144

C JDBC Configuration This appendix describes the consolidated JDBC Type 2 driver configuration and the JDBC Type 4 driver configuration in the applicationContext.xml and jdbc.properties files. • JDBC Type 2 driver configurations The consolidated JDBC Type 2 driver configuration in applicationContext.xml is as follows: PAGE 145
The SQL/MX settings for JDBC Type 4 driver in jdbc.properties appear as follows: #----------------------------------------------------------------------# SQL/MX Settings for JDBC Type 4 Driver jdbc.driverClassName=com.tandem.t4jdbc.SQLMXDriver jdbc.url=jdbc:t4sqlmx://: jdbc.username= jdbc.
PAGE 146

D Installing Spring Web Flow To use Spring Web Flow for developing your application, you need to install the Spring Web Flow distribution on the NonStop system.
PAGE 147

After extraction, must have a sub-directory: /dist. This completes the installation of the Spring Web Flow runtime libraries on a NonStop system. You can use these libraries when developing and running Spring Web Flow applications on a NonStop system, using the steps similar to those for the Spring framework.
PAGE 148

Part II Hibernate Framework Part II includes the following chapters: • “Hibernate Overview” (page 151) This chapter provides an overview of the following: • ◦ Hibernate projects certified for use on NonStop ◦ Message flow in an application that uses Hibernate on NonStop “Installing the Hibernate Framework” (page 153) This chapter helps you to install Hibernate framework libraries, and enables you to deploy and run sample Hibernate applications on your NonStop system.
PAGE 149

Contents 6 Hibernate Overview...............................................................................151 Hibernate Projects.................................................................................................................151 Hibernate Annotations......................................................................................................151 Hibernate EntityManager..................................................................................................
PAGE 150

F JDBC Configuration.................................................................................227 G Hibernate Environment Setup Script..........................................................
PAGE 151

6 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 152

• 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. Hibernate Applications on NonStop Hibernate can be used in a standalone Java application or in a Java web application using servlets or EJB session beans.
PAGE 153

7 Installing the Hibernate Framework This chapter describes the procedure to install Hibernate framework libraries on a Nonstop system. It also describes the steps required to deploy and run sample Hibernate applications, which help you to verify if you have successfully installed Hibernate on the NonStop system. The following tasks are described in this chapter: 1. “Installing Hibernate Framework Libraries on NonStop” (page 153) 2.
PAGE 154

NOTE: • Before you start installing the Hibernate framework, extract the contents of the SAMPLES.zip file (containing OpenSource Java Frameworks for NonStop) to a directory on the Windows system. • Throughout the chapter, references are made to the following directories: ◦ : The directory on the Windows system where the Hibernate distribution files are extracted. ◦ : The OSS directory on the NonStop system where the Hibernate runtime JAR files are located.
PAGE 155

6. Extract the hibernate-distribution-3.5.1-Final-dist.zip file into a directory on the Windows system. This directory will be referred as . Among other directories and files, includes the following sub-directories: \project includes the Hibernate source code. \project\annotations includes the source code of Hibernate Annotations. \project\entitymanager includes the source code of Hibernate EntityManager. \lib includes libraries required to build Hibernate applications.
PAGE 156

NOTE: • The C:\Documents and Settings\\.m2\repository location will be referred as . • You can run Hibernate 3.5.1 with JDK 1.6. However, Hibernate 3.5.1 distribution cannot be complied with JDK 1.6 . Therefore, you need to compile Hibernate 3.5.1 with JDK1.5. • Update \conf\settings.xml with the section below. org.jboss.maven.
PAGE 157

jboss-plugins https://repository.jboss.org/nexus/content/groups/public true never true never This includes axis2-codegen*.jar in the WAR file. Building the Axis2/Java Web Archive with Sandesha2 Build the Axis2/Java web archive with Sandesha2 using the steps described in “Building the Axis2/Java Web Archive using Standard Binary Distribution” (page 293). Deploying the Axis2/Java Web Archive with Sandesha2 Before you deploy the web archive (axis2.war), remove the axis2.
PAGE 300

3. Extract the Standard Binary Distribution (rampart-dist-1.5-bin.zip) into a directory on your Windows system. This directory will be referred as . Among other directories, contains the following sub-directories: \samples includes sample applications demonstrating Rampart features. \lib includes the Rampart binaries. \modu les includes the module archive files. \docs includes the Rampart documentation in HTML format.
PAGE 301

FaultHandling FaultHandling demonstrates Exception Handling using the WSDL faults and invokes BankService webservice when it is run. The intended users of this application are bank customers. This section describes the following steps for FaultHandling: • “Building FaultHandling on Windows” (page 301) • “Deploying FaultHandling on NonStop” (page 301) • “Running FaultHandling” (page 303) Building FaultHandling on Windows To build FaultHandling on your Windows system, complete the following steps: 1.
PAGE 302

1. Go to the Axis2/Java admin login page using the following URL: http://://axis2/axis2-admin/. Figure 105 Axis2/Java Administration Login Page 2. 3. Enter the username and password for the admin login to Axis2/Java. The default password for username admin is axis2. In the Tools section, click Upload Service. In the Service Archive field, enter the complete address for the BankService.aar file or click Browse... to locate and select the file.
PAGE 303

Running FaultHandling To run FaultHandling, the BankService webservice on your NonStop system must be invoked through a client on your Windows system. To do so, perform the following steps: 1. Go to \samples\faulthandling, using the command: command prompt> cd \samples\faulthandling For example: cd C:\axis2-1.5.2-bin\samples\faulthanding 2. You can use the following sample runs to check if BankService is successfully invoked. • command prompt> ant run.
PAGE 304

command prompt > cd C:\axis2-1.5.2-bin\samples\mtom 2. Generate the service using the command: command prompt> ant generate.service This command creates the service archive file (sample-mtom.aar) in \samples\mtom\build\service directory on your Windows system. MTOM is now ready to be deployed under the Axis2/Java web application on NonStop system. Deploying MTOM on NonStop To deploy the MTOMSample webservice under Axis2/Java web application, complete the following steps: 1.
PAGE 305

Figure 108 Axis2/Java Administration Upload Page 4. Click Upload to upload the service in Axis2/Java. This completes deploying the MTOMSample and it is listed in http://://axis2/services/listServices . Configuring the client for running MTOM Before running MTOM, modify the MTOM Sample WSDL file, using the following steps: 1. Go to the \samples\mtom\resources directory on your Windows system. 2.
PAGE 306

command prompt> ant clean 3. Run the client, using the command: command prompt> ant run.client -Dfile "" -Ddest Destination-file-name For example: command prompt> ant run.client -Dfile "C:\testfile.txt" -Ddest testfile.txt Confirm the following: a. The message File saved successfully appears on the command prompt. b. The Destination-file-name file is present in .
PAGE 307

16 Configuring Axis2/Java Applications on NonStop Systems This chapter provides information about configuring Axis2/Java applications on NonStop systems. This chapter includes the following sections: • “NonStop Platform Configurations” (page 307) • “Axis2/Java Framework Configurations for NonStop Systems” (page 317) NonStop Platform Configurations On a NonStop system, an application developed using the Axis2/Java framework is deployed as a web application under the NSJSP container.
PAGE 308

3. 4. 5. Set the value of Maxlinks to 250. This is the maximum number of links to the server process (NSJSP process). This means that the server process must be capable of processing 250 requests simultaneously. Set the value of TANDEM_RECEIVE_DEPTH to 250 (because the values of Maxlinks and TANDEM_RECEIVE_DEPTH should be equal). A value of 250 means that the NSJSP process is able to read a maximum of 250 messages simultaneously from its $RECEIVE file.
PAGE 309

Configuring httpd Processes to Handle Maximum Load The httpd processes are configured using the Server configuration directive in the /conf/httpd.config file on OSS. The Server directive controls the creation of the PATHMON environment, where the webserver runs.
PAGE 310

each of the five static processes can handle 100 requests. In this example, the capacity of the iTP WebServer environment can be summarized as follows: ◦ The static capacity of iTP WebServer is [Numstatic X TANDEM_RECEIVE_DEPTH]= 500. ◦ The dynamic capacity is [(Maxservers – Numstatic) X TANDEM_RECEIVE_DEPTH]= 4500. ◦ The total capacity of iTP WebServer is [Maxservers X TANDEM_RECEIVE_DEPTH]= 5000. Using this configuration, the iTP WebServer can handle 500 simultaneous requests statically.
PAGE 311

After determining the values, you can use any the following approaches to make necessary configurations for the TS/MP parameters of the httpd processes: ◦ Using the default value of TANDEM_RECEIVE_DEPTH ◦ Modifying the value of TANDEM_RECEIVE_DEPTH Using the default value of TANDEM_RECEIVE_DEPTH With TANDEM_RECEIVE_DEPTH set to the default value of 50, the static processes can be configured on the basis of Average Load and dynamic processes can be configured on the basis of Peak Load on your system.
PAGE 312

In this case, the iTP WebServer serves 105 requests (higher multiple of Numstatic nearest to the count value). Here, the 106th request displays the following error message: Maximum connections reached: The server reached its maximum configured capacity. with HTTP response code: 200 OK To customize the error message, create a new message ID error-maximum-connection. This customized message is displayed if the Message configuration directive is used in the /conf/httpd.
PAGE 313

NOTE: • The default value of -DSaveSessionOnCreation is false. -DSessionBasedLoadBalancing Enables or disables session-based load balancing. Syntax: -DSessionBasedLoadBalancing=[ true | false ] NOTE: The default value of -DSessionBasedLoadBalancing is set to true.
PAGE 314

that can be processed simultaneously can be controlled by limiting the number of threads the NSJSP Connector can spawn. NOTE: A single connector can service multiple instances of the container. The connector must be configured such that it can spawn threads sufficient for all the container instances. In terms of configuration, the Host element in the server.xml configuration file represents a container that is serviced by the connector.
PAGE 315

4. 5. Maxlinks – Determines the maximum number of TS/MP links. The number of simultaneous messages that can be delivered to an instance of NSJSP is determined by Maxlinks. NSJSP reads these many number of messages from the $RECEIVE file simultaneously. Number of Connector threads. The configurations for Numstatic, Maxservers, TANDEM_RECEIVE_DEPTH, and Maxlinks can be set under the Server directive in the /conf/servlet.config file on OSS.
PAGE 316

NSJSP is configured with SessionBasedLoadBalancing turned ON • The value of Numstatic must be [(Peak Load)/(Max load one instance of NSJSP can handle)]. • The value of Maxservers must be [(Peak Load)/(Max load one instance of NSJSP can handle)]. This ensures that no dynamic process is created, so that the session object is not lost when there are numerous file system calls. • The value of Maxlinks must be set to the peak load that one instance of NSJSP is expected to handle.
PAGE 317

important Java runtime arguments that you must consider during the deployment of your Axis2/Java applications are: • -Xmx • -Xss • -Xnoclassgc There are other Java runtime arguments supported by NSJSP. For more information, see the NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator's Guide. -Xmx Sets the maximum size of the memory allocation pool, which is the garbage collected heap.
PAGE 318

For more information about the various options available for global configuration, see: http:// ws.apache.org/axis2/1_2/axis2config.html#Global_Configuration Service Configuration Service configurations are used to configure various services on Axis2/Java. The description of these services is specified in the services.xml file. Each service archive file (.aar) must have a services.xml file to be a valid service and it must be available in the META-INF directory of the archive file.
PAGE 319

17 Getting Started with Axis2/Java This chapter explains how to develop a web service using the Axis2/Java framework. It describes the steps required to build a basic TemperatureConverter system on your Windows system and deploy it on your NonStop system. Prerequisites Before getting started, make sure that you have the requisite software installed on your NonStop and Windows system.
PAGE 320

Developing TemperatureConverter Web Service on Windows Developing the TemperatureConverter web service on a Windows system involves the following activities: 1. “Creating the Web Service Implementation Class” (page 320) 2. “Creating the Deployment Descriptor” (page 320) 3. “Creating an Axis2/Java AAR File” (page 321) Creating the Web Service Implementation Class To create the Web Service implementation class, complete the following steps: 1.
PAGE 321

Axis2/Java has a set of built-in MessageReceivers. Some of them can handle only the XML-In and XML-Out scenario, and these are called RawXML MessageReceivers. There are other message receivers called RPC MessageReceivers that can handle JavaBeans, simple Java types, and XML. The RPC MessageReceivers message receiver is used for the sample TemperatureConverter web service. To create the deployment descriptor, complete the following steps: 1.
PAGE 322

1. Go to the Axis2/Java admin login page using the following URL: http://://axis2/axis2-admin/. Figure 109 Axis2/Java Administration Login Page 2. 3. Enter the username and password for the admin login to Axis2/Java. The default password for username admin is axis2. In the Tools section, click Upload Service. In the Service Archive field, enter the complete address for the TemperatureConverter.aar file or click Browse...
PAGE 323

This completes deploying TemperatureConverter and it is listed in http://://axis2/services/listServices . Running TemperatureConverter Web Service on NonStop To run the TemperatureConverter web service on your NonStop system, complete the following steps: 1. If iTP WebServer is already running, the TemperatureConverter web service must be listed in http://://axis2/services/listServices 2.
PAGE 324

Figure 112 TemperatureConverter Web Service WSDL The WSDL file is required to create the TemperatureConverter web service client that invokes the TemperatureConverter as a web service. Developing TemperatureConverter Client on Windows using the Eclipse Galileo IDE To invoke the TemperatureConverter service running on your NonStop system, you need to create an Axis2/Java client on your Windows system. The APIs of the client application will be used to invoke the web service.
PAGE 325

1. Double-click the eclipse.exe file in to open the Eclipse IDE. The Workspace Launcher dialog box appears. By default, the workspace is set to your existing workspace, if already created. NOTE: D:\sash_usr\axis2 is the sample workspace that is used to develop the AxisClient client application for the TemperatureConverter web service. Figure 113 shows the Workspace Launcher dialog box. Figure 113 Workspace Launcher Dialog Box 2. Click OK.
PAGE 326

Figure 115 New Project Dialog Box The New Java Project dialog box appears. 5. In the Project name field, enter the name of the project you want to create. Ensure that the directory for this project is created inside the workspace that you have selected or created. NOTE: • In this sample, AxisClient is the name of the Java project and all the references for the project are made to TemperatureConverterClient. • The options in the JRE and Project layout sections are selected by default.
PAGE 327

Figure 116 New Java Project Dialog Box 6. Confirm that the JRE System Library is set to JRE version 1.5 or later. NOTE: The JRE version used in this example is 1.6. If JRE version is not 1.5 or later, complete the following steps to select JRE 1.5 or later: a. Select Windows→Preferences. b. From the left pane of the Preferences page, select Java→Installed JREs option. The list of JREs that are exposed to the Eclipse IDE appears. c. Select JRE 1.5 or later and click OK.
PAGE 328

Figure 117 JRE Options - Preferences Screen 7. Click Finish (in Figure 116) to create the Java project. Figure 118 shows the structure of the newly created Java Project AxisClient. Figure 118 Java Project AxisClient Creating the Java Package for Client Project To create the Java Package for client project, complete the following steps: 1. On the Project Explorer frame, right-click AxisClient and select New→Package. The New Java Package dialog box appears. 2. In the Name field, enter com.hp.
PAGE 329

Figure 119 New Java Package Dialog Box The Java Package for Client Project is created. Creating the Class Files under the Java Package To create the class files under the Java package, complete the following steps: 1. On the Project Explorer frame, right-click the com.hp.client package and select New→Class. The New Java Class dialog box appears. 2. In the Name field, enter TemperatureConverterClient. 3. Select public static void main(String[ ] args).
PAGE 330

Figure 120 New Java Package Dialog Box 4. Click Finish. The class files under the Java package are created. Modifying the Class File of the Client To modify the newly created TemperatureConverterClient.java class file, complete the following steps: 1. Create an instance of the ServiceClient under the main() method. ServiceClient client = new ServiceClient(); 2.
PAGE 331

return method; } public static OMElement createPayLoad2() { OMFactory fac = OMAbstractFactory.getOMFactory(); OMNamespace omNs = fac.createOMNamespace( "http://ws.apache.org/axis2", "axis2"); OMElement method = fac.createOMElement("f2cConversion", omNs); OMElement element = fac.createOMElement("value", omNs); element.setText("4"); method.addChild(element); return method; 3. Create a metadata object called Options under the main() method and set it to ServiceClient.
PAGE 332

public class TemperatureConverterClient { public static void main(String[] args) throws AxisFault { ServiceClient client = new ServiceClient(); // create option object Options opts = new Options(); // setting target EPR opts .setTo(new EndpointReference( "http://: //axis2/services/TemperatureConverter")); // Setting action ,and which can be found from the wsdl of the service opts.setAction("urn:c2fConversion"); opts.setProperty(Constants.Configuration.
PAGE 333

Table 9 Axis2/Java Dependency JAR Files Dependency JAR Files Source Location activation-1.1.jar /lib antlr-2.7.7.jar /lib axiom-api-1.2.9.jar /lib axiom-impl-1.2.9.jar /lib axis2-adb-codegen-1.5.2.jar /lib axis2-kernel-1.5.2.jar /lib axis2-transport-http-1.5.2.jar /lib axis2-transport-local-1.5.2.jar /lib bcel-5.1.
PAGE 334

Figure 121 Properties for AxisClient Dialog Box This completes the development of the AxisClient project on the Windows system. The AxisClient project structure appears as shown. Figure 122 shows the AxisClient project structure in the project explorer window.
PAGE 335

Figure 122 AxisClient Project Structure Dialog Box Running TemperatureConverter Client on Windows To run the TemperatueConverter Client on a Windows system: On the Project Explorer frame, right-click the TemperatureConverterClient.java file in the AxisClient Java Project and select Run As→Java Application. Figure 123 shows the Java Eclipse SDK -Options.
PAGE 336

The following output is displayed on the console. 39.2 -15.555555555555555 Figure 124 shows the output in the console. Figure 124 Console Accessing a REST Web Service using HTTP GET You can access the Axis2/Java based web services using HTTP GET.
PAGE 337

Developing the TemperatureConverter Web Service on Windows Developing the TemperatureConverter web service on a Windows system involves the following activities: 1. Generating the web service skeleton file using WSDL2Java 2. Update service skeleton with business logic 3. Creating an Axis2/Java AAR File Generating the web service skeleton file using WSDL2Java To generate the web service skeleton file, complete the following steps: 1.
PAGE 338

The service skeleton file for your web service is created and you need to implement the required business logic. Update the service skeleton file with the business logic To update the business logic in the service skeleton file, complete the following steps: 1. Modify the \axis2\gettingstarted\TemperatureConverter-Contract-First\src\org\apache\ws\axis2\ TemperatureConverterSkeleton.
PAGE 339

Deploying the TemperatureConverter Web Service on NonStop To deploy the TemperatureConverter.aar) file on your NonStop system, complete the following steps: 1. Go to the Axis2/Java admin login page using the following URL: http://://axis2/axis2-admin/. Figure 126 Axis2/Java Administration Login Page 2. 3. Enter the username and password for the admin login to Axis2/Java. The default password for username admin is axis2.
PAGE 340

Figure 127 Axis2/Java Administration Upload Page 4. Click Upload to upload the service in Axis2/Java. This completes deploying TemperatureConverter and it is listed in http://://axis2/services/listServices . Running the TemperatureConverter Web Service on NonStop To run the TemperatureConverter web service on your NonStop system, complete the following steps: 1.
PAGE 341

Figure 128 TemperatureConverter List Services Screen You can view the auto-generated WSDL file for the TemperatureConverter application by clicking the TemperatureConverter in Figure 111. Figure 129 shows the WSDL file for the TemperatureConverter web service.
PAGE 342

Figure 129 TemperatureConverter Web Service WSDL File You use the WSDL file to create the TemperatureConverter web service client so that the TemperatureConverter is invoked as a web service. Developing the TemperatureConverter Client on Windows using the Eclipse Galileo IDE To invoke the TemperatureConverter service running on your NonStop system, you need to create an Axis2/Java client on your Windows system. The APIs of the client application will be used to invoke the web service.
PAGE 343

Adding Dependency JAR Files Add all the Axis2/Java dependency JAR files in the Java Build Path of the AxisClientStub project to compile and link the project. These JAR files are located in the /lib directory. To add the dependency JAR files to the projects library path, complete the steps described in “Adding Dependency JAR Files” (page 332). Creating the Client stub file using WSDL2Java To create the Client stub, complete the following steps: 1.
PAGE 344

4. Click the Arguments tab on the Run Configuration dialog and enter the following argument in the Program arguments: field: -uri TemperatureConverter.wsdl -d adb -s 5. Click Apply and then click Run. The client stub file is created in the following location: AxisClientStub\src\org\apache\ws\axis2. Modifying the Client Stub File Add the following code in the AxisClientStub\src\org\apache\ws\axis2\TemperatureConverterStub.
PAGE 345

public static void main(String[] args) throws RemoteException { TemperatureConverterStub stub = new TemperatureConverterStub(); F2CConversion f2CConversion = new F2CConversion(); double param = 1; f2CConversion.setArgs0(param); stub.f2CConversion(f2CConversion); C2FConversion conversion = new C2FConversion(); double param2 = 2; conversion.setArgs0(param2); stub.
PAGE 346

Part V Integrating Frameworks Part III includes the following chapters: • “Using Spring Transaction Manager” (page 348) This chapter helps you to use the Spring Transaction Manager. • “Integrating Hibernate into Spring” (page 367) This chapter helps you to integrate Hibernate with the Spring framework. • “Integrating JPA with Hibernate into Spring” (page 383) This chapter helps you to integrate JPA with Hibernate with the Spring framework.
PAGE 347

Contents 18 Using Spring Transaction Manager.........................................................348 Why Transaction Management is required...............................................................................348 Spring Transaction Management............................................................................................348 Declarative Transaction Management.................................................................................348 Programmatic Transaction Management.......
PAGE 348

18 Using Spring Transaction Manager This chapter describes how a Spring application can manage its database transactions using a Spring Transaction Manager. This is demonstrated by modifying the EmpInfo application (developed in “Getting Started with Spring” (page 75) chapter) using the Eclipse Galileo IDE.
PAGE 349

Prerequisites The prerequisites for using the Spring Transaction Manager are: • Basic knowledge of the Spring framework and transactions. • EmpInfo application (explained in the “Getting Started with Spring” (page 75) chapter) developed on the Windows system.
PAGE 350

Figure 130 Project Explorer View 350 Using Spring Transaction Manager
PAGE 351

Modifying the EmpInfo application involves the following tasks: 1. “Modifying EmpInfo based on the Type of Transaction” (page 351) • • 2. “For Declarative Transaction” (page 351) ◦ “Creating the IEmployeeDao.java File” (page 351) ◦ “Modifying the EmployeeController.java File” (page 353) ◦ “Modifying the applicationContext.xml File” (page 354) “For Programmatic Transaction” (page 356) ◦ “Modifying the applicationContext.xml File” (page 356) ◦ “Modifying the EmployeeController.
PAGE 352

Figure 131 New Java Interface Dialog Box The IEmployeeDao.java file is created. 4. Modify the IEmployeeDao.java file to declare the methods implemented in the EmployeeDao.java file. After modification, the IEmployeeDao.java file must appear as: package com.hp.empinfo.service; import java.sql.SQLException; import com.hp.empinfo.domain.
PAGE 353

Modifying the EmployeeController.java File Modify EmployeeController.java to replace the instance of the EmployeeDao.java class with the instance of the IEmployeeDao.java interface. To modify the EmployeeController.java file, complete the following steps: 1. Change an import statement to import the IEmployeeDao.java interface instead of EmployeeDao.java. import com.hp.empinfo.service.IEmployeeDao; 2.
PAGE 354

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.insertDetail(empid, firstname, lastname, age, email); Map model = new HashMap(); model .
PAGE 355

com.hp.empinfo.service.IEmployeeDao 5. Bean Instance for the implementation class: It creates a bean for the implementation class and contains a reference to the data source. 6.
PAGE 356

${jdbc.driver} ${jdbc.url} ${jdbc.
PAGE 357

${jdbc.password} ${jdbc.catalog} ${jdbc.schema} PAGE 358
private EmployeeDao empdao; PlatformTransactionManager txManager; public ModelAndView onSubmit(Object command) throws Exception { WebApplicationContext wac = WebApplicationContextUtils .getRequiredWebApplicationContext(getServletContext()); empdao = (EmployeeDao) wac.getBean("empdao"); txManager = (PlatformTransactionManager) wac.getBean("txManager"); int empid = ((Employee) command).getEmpid(); String firstname = ((Employee) command).getFirstname(); String lastname = ((Employee) command).
PAGE 359

"Transaction Complete - One Employee Added to Employee Database"); return new ModelAndView("insertresult", "model", model); } } } Adding Dependency JAR Files Add the dependency JAR files to the build path of EmpInfo, based on the type of transaction as explained below: For Declarative Transaction To incorporate the features of Declarative Transaction in the EmpInfo application, the following JAR files, other than the ones added while developing the EmpInfo application, must be added to the EmpInfo project
PAGE 360

Figure 132 Project Explorer View: Declarative Transaction 360 Using Spring Transaction Manager
PAGE 361

For Programmatic Transaction To incorporate the features of Programmatic Transaction in the EmpInfo application, no additional JAR files, other than the ones added while developing the EmpInfo application, are required. This completes the modifications in the EmpInfo application to incorporate Programmatic Transaction.
PAGE 362

Figure 133 Project Explorer View: Programmatic Transaction Deploying EmpInfo on NonStop This section describes the following tasks: 362 Using Spring Transaction Manager
PAGE 363

1. 2. “Creating the Application WAR File on Windows” (page 363) “Deploying the EmpInfo WAR File in NSJSP on NonStop” (page 364) Creating the Application WAR File on Windows A WAR file is essential to deploy the web application. It includes the property and configuration files, Java class file,and JSPs of the web application. To create the application WAR file, complete the following steps: 1. On the Project Explorer frame, right-click EmpInfo and select Export > Export. The Export dialog box appears. 2.
PAGE 364

Figure 135 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, complete the following steps: 1.
PAGE 365

Figure 136 NSJSP Manager Login Screen 2. Enter the User name: and Password: and click OK. The NSJSP Manager screen appears. Figure 137 shows the NSJSP Manager screen.
PAGE 366

3. Select SERVLETS for the Server Class and click Set. The Host (in server.xml) tab is enabled and populated with localhost. Click Set, which enables the Deployment tab on the NSJSP Manager screen. Figure 138 shows the Deployment tab of NSJSP Manager. Figure 138 NSJSP Manager Screen - Deployment tab 4. In the Deployment tab, complete the following steps in the Web Application Deployment from Desktop section: 1. In the Select a .war file to upload field, click Browse... and locate the EmpInfo.
PAGE 367

19 Integrating Hibernate into Spring This chapter describes how a Spring application can use Hibernate for its database operation. This is demonstrated by modifying the EmpInfo application (developed in the “Getting Started with Spring” (page 75) chapter) using the Eclipse Galileo IDE.
PAGE 368

• • Following software installed on the NonStop system: ◦ NonStop iTP WebServer version T8996H02 or later ◦ NSJSP version T1222H60 or later ◦ JDBC Type 2 driver version T1275H50 or later, or JDBC Type 4 driver version T1249V11 or later ◦ NonStop SQL/MX version T1050H23 or later ◦ NSJ version T2766H50 or later Following software installed on the Windows system: ◦ JDK version 1.5 or later ◦ JDBC Type 4 driver version T1249V11 or later ◦ Eclipse Galileo IDE version 3.3.1.
PAGE 369

Figure 139 Project Explorer View Example of Integrating Hibernate into Spring 369
PAGE 370

Modifying the EmpInfo application involves the following tasks: • “Modifying the applicationContext.xml File” (page 370) • “Modifying the EmployeeDao.java File” (page 371) • “Creating the Employee.hbm.xml File” (page 372) • “Removing the EmployeeRowMapper.java File” (page 375) • “Adding Dependency JAR Files” (page 376) Modifying the applicationContext.xml File Modify the EmpInfo/WebContent/WEB-INF/applicationContext.
PAGE 371

${jdbc.password} ${jdbc.catalog} ${jdbc.schema} Employee.hbm.xml PAGE 372
public class EmployeeDao { private SessionFactory sessionFactory; public void setSessionFactory(SessionFactory sessionFactory) { this.sessionFactory = sessionFactory; } public Employee getDetail(int empid) throws SQLException { Session session = sessionFactory.openSession(); List l = session.createQuery( "from Employee where emp_id=" + empid).list(); Iterator i = l.iterator(); Employee employee = i.next(); session.
PAGE 373

Figure 140 New File Dialog Box The New XML File dialog box appears. 3. In the File name field, type Employee.hbm.xml and ensure that the parent folder is set to EmpInfo/src. Click Next.
PAGE 374

Figure 141 New XML File Dialog Box The New XML File: Create XML dialog box appears. 4.
PAGE 375

Figure 142 New XML File: Create XML Dialog Box The Employee.hbm.xml file is created in the EmpInfo/src directory. 5. Modify the Employee.hbm.xml file to add the mapping details. The Employee.hbm.xml file must appear as: PAGE 376
(.hbm file), the EmpInfo application will no longer use the EmployeeRowMapper.java file for mapping purposes. Therefore, you must delete the EmployeeRowMapper.java file from the com.hp.empinfo.domain package.
PAGE 377

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 in the Adding Dependency JAR Files in the Project Library Path section of the “Getting Started with Spring” (page 75) chapter. The EmpInfo application is now modified to integrate Hibernate into a Spring application (EmpInfo) to handle database operations.
PAGE 378

Figure 143 EmpInfo: Project Explorer View 378 Integrating Hibernate into Spring
PAGE 379

Deploying EmpInfo on NonStop This section describes the following tasks: 1. “Creating the EmpInfo WAR File on Windows” (page 379) 2. “Deploying the EmpInfo WAR File in NSJSP on NonStop” (page 380) Creating the EmpInfo 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, complete the following steps: 1.
PAGE 380

Figure 145 The 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, complete the following steps: 1.
PAGE 381

Figure 146 NSJSP Manager Login Screen 2. Enter the User name: and Password: and click OK. The NSJSP Manager screen appears. Figure 147 shows the NSJSP Manager screen.
PAGE 382

3. Select SERVLETS for the Server Class and click Set. The Host (in server.xml) tab is enabled and populated with localhost. Click Set, which enables the Deployment tab on the NSJSP Manager screen. Figure 148 shows the Deployment tab of NSJSP Manager. Figure 148 NSJSP Manager Screen - Deployment tab 4. In the Deployment tab, complete the following steps in the Web Application Deployment from Desktop section: 1. In the Select a .war file to upload field, click Browse... and locate the EmpInfo.
PAGE 383

20 Integrating JPA with Hibernate into Spring This chapter describes how a Spring application can use the Java Persistence API (JPA) with Hibernate for its database operation. This is demonstrated by modifying the EmpInfo application (developed in “Getting Started with Spring” (page 75) chapter) using the Eclipse Galileo IDE.
PAGE 384

• ◦ NonStop SQL/MX version T1050H23 or later ◦ NSJ version T2766H60 or later Following software installed on the Windows system: ◦ JDK version 1.5 or later ◦ JDBC Type 4 driver version T1249V11 or later ◦ Eclipse Galileo IDE version 3.3.1.
PAGE 385

Figure 149 Project Explorer View Modifying the EmpInfo application involves the following activities: Example of Integrating JPA with Hibernate into Spring 385
PAGE 386

1. 2. 3. 4. 5. 6. “Creating the persistence.xml File” (page 386) “Creating the EntityEmployee.java File” (page 386) “Modifying the applicationContext.xml File” (page 388) “Modifying the EmployeeDao.java File” (page 389) “Removing the Employee.hbm.xml File” (page 391) “Adding Dependency JAR Files” (page 391) Creating the persistence.xml File Create the persistence.xml file to define a persistence unit called Empinfo to define a set of classes and their mapping characteristics. To create persistence.
PAGE 387

import javax.persistence.Table; @Entity @Table(name = "Employee") public class EntityEmployee { @Id private int emp_id; @Basic private String first_name; @Basic private String last_name; @Basic private int age; @Basic private String email; public EntityEmployee() { super(); } public EntityEmployee(int emp_id, String first_name, String last_name, int age, String email) { this.emp_id = emp_id; this.first_name = first_name; this.last_name = last_name; this.age = age; this.
PAGE 388

} } Modifying the applicationContext.xml File Modify the EmpInfo/WebContent/WEB-INF/applicationContext.xml file, so that it uses JPA EntityManagerFactory to connect to the employee SQL/MX database table, in place of Hibernate SessionFactory. To modify the applicationContext.xml file, complete the following steps: 1. Specify the EntityManagerFactory in the applicationContext.xml file as shown: PAGE 389
${jdbc.user} ${jdbc.password} ${jdbc.catalog} ${jdbc.schema} PAGE 390
a. b. c. public Employee getDetail(int empid) throws SQLException public void insertDetail(int empid, String firstname, String lastname, int age, String email) throws SQLException public String deleteEmployee(int empid) After modification, the EmployeeDao.java file should appear as: package com.hp.empinfo.service; import import import import import import import import java.sql.SQLException; java.util.Iterator; java.util.List; javax.persistence.EntityManager; javax.persistence.
PAGE 391

EntityEmployee entityEmployee = em.find(EntityEmployee.class, new Integer(empid)); em.remove(entityEmployee); em.flush(); t.commit(); return "Employee deleted"; } } Removing the Employee.hbm.xml File JPA annotations (EntityEmployee.java class) have been used to map the database entities. Hence, the Hibernate Mapping file (Employee.hbm.xml) is no longer needed and is removed. Adding Dependency JAR Files Adding the dependency JAR files involves the following tasks: 1.
PAGE 392

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 in the “Adding Dependency JAR Files in the Project Library Path” (page 89) section in the “Getting Started with Spring” (page 75) chapter. The EmpInfo application is now modified to integrate JPA with Hibernate into a Spring application.
PAGE 393

Figure 150 Project Explorer View Example of Integrating JPA with Hibernate into Spring 393
PAGE 394

Deploying EmpInfo on NonStop This section describes the following tasks: 1. “Creating the EmpInfo WAR File on Windows” (page 394) 2. “Deploying the EmpInfo WAR File in NSJSP on NonStop” (page 395) Creating the EmpInfo 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, complete the following steps: 1.
PAGE 395

Figure 152 The 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, complete the following steps: 1.
PAGE 396

Figure 153 NSJSP Manager Login Screen 2. Enter the User name: and Password: and click OK. The NSJSP Manager screen appears. Figure 154 shows the NSJSP Manager screen.
PAGE 397

3. Select SERVLETS for the Server Class and click Set. The Host (in server.xml) tab is enabled and populated with localhost. Click Set, which enables the Deployment tab on the NSJSP Manager screen. Figure 155 shows the Deployment tab of NSJSP Manager. Figure 155 NSJSP Manager Screen - Deployment tab 4. In the Deployment tab, complete the following steps in the Web Application Deployment from Desktop section: 1. In the Select a .war file to upload field, click Browse... and locate the EmpInfo.
PAGE 398

21 Integrating Axis2/Java into Spring This section describes how a Spring application can use Axis2/Java for exposing itself as a web service. This is demonstrated by modifying the EmpInfo application (developed in the Getting Started with Spring chapter) using the Eclipse Galileo IDE.
PAGE 399

Activities involved Integrating the EmpInfo application with Axis2/Java, involves the following activities: • Modifying EmpInfo on Windows using Eclipse Galileo IDE • Deploying EmpInfo on NonStop • Running EmpInfo Web Service on NonStop • Developing EmpInfoClient on Windows • Running EmployeeInfo on NonStop Modifying EmpInfo on Windows using Eclipse Galileo IDE The EmpInfo application, developed in the Getting Started with Spring chapter, is the starting point to demonstrate the integration of Axi
PAGE 400

4. 5. Creating the build.xml File Adding Dependency JAR Files Creating the SpringInit.java File Create a Java class (SpringInit.java) to initialize the EmpInfo application context when the application is exposed under Axis2/Java. NOTE: The SpringInit.java is a ServiceLifeCycle class and its startUp method gets called when it is being loaded. This is required to expose EmpInfo as a webservice under Axis2/Java. To create SpringInit.java , complete the following steps: 1. Create SpringInit.java in the com.
PAGE 401

Creating the services.xml File Create the Axis2/Java Deployment Descriptor file (services.xml) to instantiate the SpringInit and EmpInfo services. To create the services.xml file, complete the following steps: 1. Create the services.xml file in the EmpInfo/WebContent/META-INF directory, as explained in the Creating the EmpInfo-servlet.xml File section in the Getting Started with Spring chapter. 2. Modify the services.xml file to include the instances SpringInit and EmpInfo services.
PAGE 402

${jdbc.url} ${jdbc.username} ${jdbc.password} ${jdbc.catalog} ${jdbc.schema} PAGE 403
PAGE 404
Figure 157 Project Explorer View Deploying EmpInfo on NonStop This section describes the following tasks: 1. Creating the EmpInfo AAR File on Windows 2. Deploying the EmpInfo AAR File in Axis2/Java on NonStop Creating the EmpInfo AAR File on Windows To create the EmpInfo AAR (EmpInfoService.aar) file, complete the following steps: 1. On the Project Explorer frame, right-click the EmpInfo/build.xml file and select Run As > Ant Build. Figure 158 shows the Project Explorer Frame.
PAGE 405

Figure 158 Project Explorer Frame On selecting Ant Build, the following output appears on the console and target directory under EmpInfo is created. NOTE: The EmpInfoService.aar file is created inside the target directory. Figure 159 shows the Console dialog box.
PAGE 406

Figure 159 Console Dialog Box 2. Refresh the EmpInfo Project and locate the EmpInfoService.aar under EmpInfo/target directory. Deploying the EmpInfo AAR File in Axis2/Java on NonStop To deploy the EmpInfo AAR (EmpInfoService.aar) file on your NonStop system, complete the following steps: 1. Go to the Axis2/Java admin login page using the following URL: http://://axis2/axis2-admin/.
PAGE 407

2. 3. Enter the username and password for the admin login to Axis2/Java. The default password for username admin is axis2. In the Tools section, click Upload Service. In the Service Archive field, enter the complete address for the EmpInfoService.aar file or click Browse... to locate and select the file. Figure 161 Axis2/Java Administration Upload Page 4. Click Upload to upload the service in Axis2/Java.
PAGE 408

Running EmpInfo Web Service on NonStop To run the EmpInfo web service on your NonStop system, complete the following steps: 1. Access the EmpInfo web service using the following URL: http://://axis2/services/listServices. Details such as EPR, Service Description, Service Status, and Available Operations are also shown for the EmpInfo web service. The SpringInit service initializes the EmpInfo application context on startup.
PAGE 409

3. 4. 5. Creating the EmpInfoClient.java File Modifying the EmpInfoClient.java File Adding Dependency JAR Files Creating the EmpInfoClient Project in Eclipse To create the client project in Eclipse, complete the following steps: 1. Click File > New > Java Project. The New Project dialog box appears. 2. From the list of folders, select Java > Java Project and click Next. Figure 163 shows the New Project dialog box. Figure 163 New Project Dialog Box The New Java Project dialog box appears. 3.
PAGE 410

Figure 164 New Java Project Dialog Box 4. Confirm that the JRE System Library is set to JRE version 1.5 or later. If JRE version is not 1.5 or later, complete the following steps to select JRE 1.5 or later: a. Click Windows > Preferences. b. From the type filter text, select Java > Installed JREs. The JRE Options: Preferences dialog box appears. c. Select JRE 1.5 or later and click OK. NOTE: In this section, JRE 1.6 version is used to create the client project.
PAGE 411

Figure 165 JRE Options: Preferences Dialog Box d. Click Finish in Figure 164 to create the Java project. Figure 166 shows the Java: Project Explorer View. Figure 166 Java: Project Explorer View Creating the Package for EmpInfoClient To create the package for client project, complete the following steps: 1. On the Project Explorer frame, right-click the EmpInfoClient and select New > Package. The New Java Package dialog box appears. 2. In the Name field, enter com.hp.
PAGE 412

Figure 167 New Java Package Dialog Box The package for client project is created. Creating the EmpInfoClient.java File To create the EmpInfoClient.java class file under the EmpInfoClient package, complete the following steps: 1. On the Project Explorer frame, right-click the com.hp.client package and select New > Class. The New Java Class dialog box appears. 2. In the Name field, enter EmpInfoClient and click Finish. Figure 168 shows the New Java Class dialog box.
PAGE 413

Figure 168 New Java Class Dialog Box The EmpInfoClient.java class file under the EmpInfoClient package is created. Modifying the EmpInfoClient.java File Modify the newly created class file EmpInfoClient.java file so that it appears as: package com.hp.client; import java.util.Scanner; import import import import import import import import org.apache.axiom.om.OMAbstractFactory; org.apache.axiom.om.OMElement; org.apache.axiom.om.OMFactory; org.apache.axiom.om.OMNamespace; org.apache.axis2.AxisFault; org.
PAGE 414

int choice=scan.nextInt(); if (choice==1 ) { opts.setAction("urn:insertDetail"); client.setOptions(opts); client.sendRobust(createPayLoad1()); System.out.println("Request Sent Successfully"); } else if (choice==2 ) { opts.setAction("urn:getDetail"); client.setOptions(opts); OMElement res2 = client.sendReceive(createPayLoad2()); System.out.println(res2); } else if (choice==3) { opts.setAction("urn:deleteEmployee"); client.setOptions(opts); OMElement res3 = client.sendReceive(createPayLoad3()); System.out.
PAGE 415

Adding Dependency JAR Files Add the following Axis2/Java dependency JAR files to the location /lib in the Java Build Path of the EmpInfoClient project to compile and link the project: • commons-codec-1.3.jar • commons-httpclient-3.1.jar • commons-logging-1.1.1.jar • antlr-2.7.7.jar • activation-1.1.jar • axiom-api-1.2.9.jar • axiom-impl-1.2.9.jar • axis2-adb-1.5.2.jar • axis2-kernel-1.5.2.jar • wstx-asl-3.2.9.jar • geronimo-stax-api_1.0_spec-1.0.1.jar • neethi-2.0.4.
PAGE 416

Figure 169 Project Explorer View Running EmpInfoClient on Windows To run the EmpInfoClient on windows, complete the following steps: 1. On the Project Explorer frame, right-click the EmpInfoClient.java file and select Run As > Java Application. Figure 170 shows the Java Eclipse Platform.
PAGE 417

Figure 170 Java Eclipse Platform The Console is displayed. 2. Press 1 to insert Employee. Specify the employee details as prompted. Figure 171 shows the Console: Insert Employee.
PAGE 418

Figure 171 Console: Insert Employee The message Request Sent Successfully is displayed. 3. 4. Press Y to continue. Press 2 to retrieve Employee details. Specify the Employee ID of the employee whose details you wish to retrieve. Figure 172 shows the Console: Employee Details.
PAGE 419

Figure 172 Console: Employee Details 5. 6. Press Y to continue. Press 3 to delete Employee. Specify the Employee Id of the employee you wish to delete. Figure 173 shows the Console: Delete Employee.
PAGE 420

Figure 173 Console: Delete Employee 420 Integrating Axis2/Java into Spring
PAGE 421

22 Integrating MyFaces into Spring This section describes how a Spring application can use MyFaces to create Views. This is demonstrated by modifying the EmpInfo application (developed in Getting Started with Spring chapter) using the Eclipse Galileo IDE. The following topics are discussed in this section: • Why Integrate MyFaces into Spring • Example of Integrating Axis2/Java with Spring Why Integrate MyFaces into Spring MyFaces and Spring have their individual usefulness and capabilities.
PAGE 422

Modifying EmpInfo on Windows using Eclipse Galileo IDE The EmpInfo application developed in the Getting Started with Spring chapter is the starting point to demonstrate the integration of MyFaces with Spring applications. Following is the screen shot of the final structure of the EmpInfo application that was developed in the Getting Started with Spring chapter. Figure 174 shows the Project Explorer View. Figure 174 Project Explorer View Modifying the EmpInfo application involves the following tasks: 1.
PAGE 423

Removing the Folders and Files from the EmpInfo Application Remove the following folders and files from the EmpInfo application: • jsp folder in EmpInfo/WebContent/WEB-INF. • EmpInfo-servlet.xml file in EmpInfo/WebContent/WEB-INF. • EmployeeController.java in EmpInfo/src/com/hp/empinfo/web. Modifying the web.xml File Modify the web.xml file to set the Faces servlet and its mapping. To modify the web.xml file, complete the following steps: 1.
PAGE 424

5. Set the filter mapping as shown below: extensionsFilter *.jsf extensionsFilter /faces/* After modification, the web.xml file appears as: PAGE 425
Creating the IEmployeeDao.java File Create a Java interface named IEmployeeDao.java to implement the EmployeeDao.java class. The IEmployeeDao.java is placed with its implementation class in the com.hp.empinfo.service package. To create the IEmployeeDao.java file, complete the following steps: 1. On the Project Explorer frame, right-click EmpInfo and select New > Interface. The New Java Interface dialog box appears. 2. 3.
PAGE 426

int age, String email) throws SQLException ; /**Deleting Employee corresponding to given employeeId**/ public String deleteEmployee(int empid) throws SQLException; /**Checking whether the employee corresponding to provided employeeId already exists in the database**/ public Employee checkEmp(int empid)throws SQLException; } Modifying the EmployeeDao.java File Modify the EmployeeDao.java file in com.hp.empinfo.
PAGE 427

} Creating the ServiceFinder.java File The ServiceFinder.java file is a Business Services class that contains the code to interact with the data tier. The ServiceFinder service is used to get the Spring managed beans from WebApplicationContext. To create the ServiceFinder.java file in the com.hp.empinfo.web package, complete the following steps: 1. Create the ServiceFinder.java file under the com.hp.empinfo.
PAGE 428

import com.hp.empinfo.web.ServiceFinder; public class EmpBean { private int empid; private String firstname; private String lastname; private int age; private String email; private String rord; boolean exist = false; boolean state = false; boolean state1 = false; boolean ntexist = false; public boolean isExist() { return exist; } public void setExist(boolean exist) { this.exist = exist; } public int getEmpid() { return empid; } public void setEmpid(int empid) { this.
PAGE 429

com.hp.empinfo.domain.Employee employee = new com.hp.empinfo.domain.Employee(); // Set employee id employee.setEmpid(getEmpid()); // Set employee Firstname employee.setFirstname(getFirstname()); // Set employee Lastname employee.setLastname(getLastname()); // Set employee age employee.setAge(getAge()); // Set employee email employee.setEmail(getEmail()); /** Inserting Employee Details* */ dao.insertDetail(employee.getEmpid(), employee.getFirstname(), employee.getLastname(), employee.getAge(), employee .
PAGE 430

exist = true; s1 = getRord(); if (s1.equals("Delete")) { /** Deleting employee Details* */ dao.deleteEmployee(getEmpid()); state = true; } else if (s1.equals("Retrieve")) { /** Retrieving employee Details* */ com.hp.empinfo.domain.Employee employee = dao .getDetail(getEmpid()); setEmpid(employee.getEmpid()); setAge(employee.getAge()); setEmail(employee.getEmail()); setFirstname(employee.getFirstname()); setLastname(employee.
PAGE 431

To create the MessageFactory.java file in the com.hp.empinfo.web package, complete the following steps: 1. Create the MessageFactory.java file under the com.hp.empinfo.web package, as explained in the Creating the Controller for EmpInfo section in the Getting Started with Spring chapter. 2. Modify the MessageFactory.java file to include the method for receiving messages from the message bundle. After modification, the MessageFactory.java file must appear as shown: package com.hp.empinfo.web; import java.
PAGE 432

3. 4. Modifying JSPs Creating the mycss.css File Creating Pages folder Create a new folder pages under EmpInfo/WebContent as explained in the Creating a folder to store JSPs section in the Getting Started with Spring chapter. Creating JSPs Create the following JSP files under EmpInfo/WebContent/pages as explained in the Creating the index.jsp File section in the Getting Started with Spring chapter. • welcome.jsp • insert.jsp • empUpdate.jsp • empDetail.jsp • success.
PAGE 433

PAGE 434
PAGE 435

PAGE 436
PAGE 437

<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%> <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%> <%@ taglib uri="http://myfaces.apache.org/tomahawk" prefix="t"%> Detail PAGE 438

PAGE 439

Creating the mycss.
PAGE 440

Figure 176 New File Dialog Box 3. Click Finish. The mycss.css file is created. 4. Add the following code to the mycss.css file: body{ background-color:#fff2f2; margin-left:0; margin-right:0; margin-top:0; margin-bottom:0; } .TableRow1 { background-color: #D0E6E0; } .TableRow2 { background-color: #E8F7F1; } .TableColumn { text-align: center } .TableClass { font-family : verdana, Geneva, Arial, Helvetica, sans-serif; font-size: 13px; color: #000000; padding: 2; border-style: solid; border-width: 2px; } .
PAGE 441

.style1 { font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold; font-size: 16px; color: green; font-weight:bold; } .style2 { font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10px; font-weight: bold; } .style3 {font-size: 13px; font-family: Verdana, Arial, Helvetica, sans-serif;} .style4 { font-family: Verdana, Arial, Helvetica, sans-serif; font-weight:bold; color: #FF0000; } .errors { font-style: italic; color: green; } Modifying the index.jsp File Modify EmpInfo/index.
PAGE 442

/pages/insert.jsp success /pages/success.jsp failure /pages/insert.jsp home /pages/welcome.jsp /pages/welcome.
PAGE 443

home /pages/welcome.jsp back /pages/insert.jsp Adding Dependency JAR Files Download the following JAR files from http://archive.apache.org/dist/commons/: • commons-el.jar • commons-fileupload-1.0.jar • commons-validator-1.3.1.jar • tomahawk-1.1.8.
PAGE 444

Figure 177 shows the Project Explorer View. Figure 177 Project Explorer View Deploying EmpInfo on NonStop This section describes the following tasks: 1. Creating the EmpInfo WAR File on Windows 2.
PAGE 445

Creating the EmpInfo 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, complete the following steps: 1. On the Project Explorer frame, right-click EmpInfo and select Export > Export. The Export dialog box appears. 2. From the list of folders, select Web > WAR file and click Next. Figure 178 shows the Export dialog box.
PAGE 446

Figure 179 The 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 your NonStop system, complete the following steps: 1.
PAGE 447

Figure 180 NSJSP Manager Login Screen 2. Enter the User name: and Password: and click OK. The NSJSP Manager screen appears. Figure 181 shows the NSJSP Manager screen.
PAGE 448

3. Select SERVLETS for the Server Class and click Set. The Host (in server.xml) tab is enabled and populated with localhost. Click Set, which enables the Deployment tab on the NSJSP Manager screen. Figure 182 shows the Deployment tab of NSJSP Manager. Figure 182 NSJSP Manager Screen - Deployment tab 4. In the Deployment tab, complete the following steps in the Web Application Deployment from Desktop section: 1. In the Select a .war file to upload field, click Browse... and locate the EmpInfo.
PAGE 449

Figure 183 Welcome to Employee Management Service Screen To insert new employee details, complete the following steps: 1. On the Welcome to Employee Management Service screen, click Insert New Employee Details. The Insert Employee Details screen appears. Figure 184 shows the Insert Employee Details screen.
PAGE 450

Figure 184 Insert Employee Details Screen 2. Enter the required Employee details and click Submit. Figure 185 shows an example of valid employee details.
PAGE 451

If the values in each field are valid, Database is successfully updated message appears. Figure 186 shows the Success screen. Figure 186 Success Screen If you enter an existing Employee ID, the Insert Employee Details screen shows Employee already exists message. Figure 187 shows the message in the Insert screen.
PAGE 452

Figure 187 Message Screen If you enter invalid field values, the corresponding error messages appear on the Insert Employee Details screen. Figure 188 shows the Error Message screen.
PAGE 453

Figure 188 Error Message Screen To update the existing employee details, complete the following steps: 1. Click Update the existing employee details on the Welcome screen. The Record Update screen appears. Figure 189 shows the Record Update screen appears.
PAGE 454

Figure 189 Record Update Screen 2. Enter the required Employee ID and Action to be performed (Retrieve/Delete) and click Retrieve/Delete. If you enter Retrieve, the Employee Information screen appears. Figure 190 shows the Employee Information screen. Figure 190 Employee Information Screen If you enter a non-existing Employee ID, the Record Update screen appears with the message Employee does not exist. Figure 191 shows the Record Update: Message Screen.
PAGE 455

Figure 191 Record Update: Message Screen If you enter invalid field values, the corresponding error messages appears on the Record Update screen. Figure 192 shows the Record Update: Error Message screen.
PAGE 456

Figure 192 Record Update: Error Message Screen 3.
PAGE 457

• In the Employee ID field, enter the employee ID you want to delete and in the Action to perform field, enter Delete. Click Retrieve/Delete. Figure 193 shows the Record Update: Delete Employee screen. Figure 193 Record Update: Delete Employee Screen The Employee ID is deleted.
PAGE 458

23 Frequently Asked Questions 23.23.1.1 Why do I get "blobTableName property is not set or set to null value or set to invalid value OR clobTableName property is not set or set to null value or set to invalid value error(s)" while running a JDBC application on NonStop system? BLOB and CLOB are not native data types in SQL/MX database. But, database administrators can create SQL/MX tables that have BLOB or CLOB columns by using the JDBC drivers for SQL/MX database or special SQL syntax in MXCI.
PAGE 459

23.23.1.7 One of the most common reasons for this error is the use of "Reserved Words". There are a set of words reserved to be used by NonStop SQL/MX. To prevent syntax errors, avoid using these words as identifiers in NonStop SQL/MX SQL statements. In case you intend to use a reserved word as a column or table name, you must enclose the reserved word in double quotes (") to access that column or object. I see "org.apache.axis2.
PAGE 460

If the application is a web application developed on Windows using Eclipse Galileo IDE, then you should add all the dependency JAR files in the project library path and resolve the J2EE module dependency on these JAR files using the steps described in the “Adding Dependency JAR Files in the Project Library Path” (page 89) of the “Getting Started with Spring” (page 75) chapter. However, if the application is not a web application, you need to add the dependency JAR files into the CLASSPATH. 23.23.2.
PAGE 461

Glossary A Arglist Specifies the argument list passed to an object at the start time or at the runtime. AXIOM AXIOM (AXIs2 Object Model) is the base of Axis2, where any incoming SOAP message is represented as an object model called AXIOM inside Axis2. The advantage of AXIOM over other XML inforset representations is that it is based on PULL parser technique, while most others are based on PUSH parser technique.
PAGE 462

In traditional programming the flow is controlled by a central piece of code. Using Inversion of Control this central control as a design principle is left behind. Although the caller will eventually get its answer, how and when is out of control of the caller. It is the callee who decides to answer how and when. J J2EE Environments J2EE Environment consist of J2EE platform that represents a single standard for implementing and deploying multi-tier enterprise applications.
PAGE 463

addition, you can use it to view Hotstuff messages, Support Notes, SPRs for special consideration, contents of available RVUs, and to review what software products are licensed for the systems. SessionBasedLoadBalancing A feature of NSJSP by virtue of which NSJSP Container maintains sessions for load balancing purposes. SOAP SOAP,Simple Object Access Protocol, is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks.
PAGE 464

Index Symbols $datavol, 42 $RECEIVE, 53, 171, 241, 308 -DSaveSessionOnCreation, 57, 175, 245, 312 -DSessionBasedLoadBalancing, 58, 176, 246, 313 -Xmx, 62, 180, 250, 317 -Xmx maximum-stack-size, 62, 180, 250, 317 -Xnoclassgc, 62, 180, 250, 317 -Xss, 62, 180, 250, 317 //EmpInfo, 382 /dbconfig, 223 /etc, 135, 223 /insert.
PAGE 465

Installing Axis2/Java, 292 Building, 293 Deploying, 294 Downloading, 292 Running, 296 TemperatureConverter, 319 AxisClient, 324, 342 AxisClient/src, 328 B BankService, 301 BankService.aar, 301 Bean Instance, 355 Bid.hbm.xml, 184 build.xml, 402 Business Layer, 421 Business Logic, 102 C c2fConversion, 320 c3p0-0.9.1.2.jar, 72 c3p0-0.9.1.jar, 190 Caching, 190 Caveat Emptor, 159 Building, 159 Customizing, 221 Added Files, 221 Modified File, 223 Deploying, 163 Running, 163 Setting, 161 Caveatemptor.
PAGE 466

employeeinfocat, 215 employeeinfosch, 215 EmployeeRowMapper, 118, 375 empUpdate.jsp, 435 EntityEmployee.java, 386 Environment.HBM2DDL_AUTO, 223 error-maximum-connection, 57, 175, 245, 312 eventcat, 165 EventManager Customizing, 223 Added Directories, 223 Added Files, 224 Modified File, 225 eventmanager_script.sql, 224 Eventmgr, 163 eventsch, 165 Executor, 53, 171, 241, 308 Executor Element, 59, 177, 247, 314 F f2cConversion, 320 faces-config.
PAGE 467

jpetstore.war, 47 jpetstore_dataload_script.sql, 48 jpetstore_tables_script.sql, 47 jpetstorecat, 48 jpetstoresch, 48 JSESSIONID, 57, 175, 245, 312 JSP pages, 95 JSP Standard Tag Library (JSTL), 95 jstl.jar, 263 JTAFactory, 189 kilobytes, 62, 180, 250, 317 Downloading, 286 Installing MyFaces Trinidad Copying, 285, 286 Downloading, 285 MyFaces distribution, 234 MyFaces Getting Started, 252 myfaces-components, 234 Building, 235 Deploying, 235 Running, 237 myfaces-components.war, 235 myfaces-impl-2.0.2.
PAGE 468

Modified Files, 136 Deploying, 43 Running, 45 Setting, 42 petclinic.hbm.xml, 137 Changes to petclinic.hbm.xml, 137 petclinic.war, 41 petclinic_dataload_script.sql, 43 petclinic_tables_script.sql, 43 placeholder, 64 Plain Old Java Object (POJO), 421 platform-independent, 367 PlatformTransactionManager, 356 PlatformTransactionManagerImplementation, 348 Pom.xml, 141 Changes to Pom.
PAGE 469

taglibs, 97 TANDEM_RECEIVE_DEPTH, 53, 54, 171, 172, 241, 242, 308, 309 target, 161 TemperatureConverter, 320 TemperatureConverter Client Developing, 324, 342 Adding Dependency JAR Files, 332, 343 Creating Class Files, 329 Creating Client Project, 324, 342 Creating Java Package, 328 Creating the Client stub, 343 Modifying Class File, 330 Running, 335 TemperatureConverter Web Service Deploying, 321, 339 Developing, 320 Creating Axis2/Java AAR File, 321 Creating Deployment Descriptor, 320 Creating Web Service
PAGE 470

Employee Id :
Action to Perform (Retrieve/Delete) :