Open Source Java Frameworks on NonStop User's Guide (Spring 2.5.0, Hibernate 3.2.6, MyFaces 1.2.5, Axis2/Java 1.4.1)

Manuals Brands HP Manuals Server HP Integrity NonStop H-Series

Open Source Java Frameworks on NonStop

User's Guide

HP Part Number: 576269-001

Published: August 2009

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

Summary of content (492 pages)

PAGE 1

Open Source Java Frameworks on NonStop User's Guide HP Part Number: 576269-001 Published: August 2009 Edition: J06.03 and subsequent J-series RVUs and H06.
PAGE 2

© Copyright 2009 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

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

Windows System........................................................................................................................45 Installing Spring Framework Libraries on NonStop.......................................................................45 Downloading Spring Distribution on Windows........................................................................45 Copying Spring Runtime Libraries from Windows to NonStop...............................................
PAGE 5

Defining the PlatformTransactionManager...........................................................83 Defining the Transaction Rollback (Optional).................................................................83 Programmatic Transaction Management..............................................................................84 Using the TransactionTemplate...............................................................................84 Using a PlatformTransactionManager......................................
PAGE 6

Modifying the index.jsp File.....................................................................................137 Deploying EmpInfo on NonStop.............................................................................................142 Creating the Application WAR File on Windows...............................................................142 Deploying the EmpInfo WAR File in NSJSP on NonStop..................................................143 Running EmpInfo on NonStop.............................
PAGE 7

6 Axis2/Java Overview...........................................................................................173 Axis2/Java Architecture.................................................................................................................173 Key Features of Axis2/Java............................................................................................................174 Components in an Axis2/Java Application on NonStop...............................................................
PAGE 8

Module Configuration..............................................................................................................200 9 Getting Started with Axis2/Java.........................................................................201 Prerequisites..................................................................................................................................201 NonStop System..........................................................................................................
PAGE 9

12 Configuring MyFaces Applications on NonStop Systems..............................239 NonStop Platform Configurations.................................................................................................239 Determining the Application Parameters................................................................................239 Determining the Maximum Capacity of NSJSP Instance.........................................................239 Configuring iTP WebServer for MyFaces Applications.........
PAGE 10

F Installing MyFaces Tomahawk Framework Libraries on NonStop....................285 Downloading MyFaces Tomahawk Distribution on Windows.....................................................285 Copying MyFaces Tomahawk Runtime Libraries from Windows to NonStop............................285 IV Hibernate Framework...............................................................................................287 14 Hibernate Overview..............................................................................
PAGE 11

Configuring httpd Processes to Handle Maximum Load................................................309 Limiting the Maximum Number of Incoming Requests....................................................311 Configuring NSJSP for Hibernate Applications.......................................................................312 Configuring SessionBasedLoadBalancing..........................................................................312 Configuring Connector Threads...........................................
PAGE 12

G Customizing Sample Application.......................................................................355 Customizing Caveat Emptor.........................................................................................................355 Modified File............................................................................................................................355 Main.java ........................................................................................................................
PAGE 13

Creating the Employee.hbm.xml File.................................................................................392 Removing the EmployeeRowMapper.java File...................................................................394 Adding Dependency JAR Files...........................................................................................394 Deploying EmpInfo on NonStop.............................................................................................
PAGE 14

Creating the IEmployeeDao.java File..................................................................................443 Modifying the EmployeeDao.java File.........................................................................444 Creating the ServiceFinder.java File....................................................................................445 Creating the EmpBean.java File.......................................................................................445 Creating the MessageFactory.
PAGE 15

About This Document This manual is a user manual and a reference manual. It provides information on using OpenSource Java Frameworks on a NonStop system, and contains instructions and guidelines on install, configure, and use the following frameworks on an HP NonStop™ system: • • • • Spring Axis2/Java MyFaces Hibernate Supported Release Version Updates (RVUs) This manual supports J06.03 and all subsequent J-series RVUs, and H06.
PAGE 16

Appendix D: Installing Spring Web Flow This appendix describes the steps required to install Spring Web Flow on your NonStop system. Part II: Axis2/Java Framework Part II describes the procedure to customize the Axis2/Java framework to work on a NonStop system. Chapter 6: Axis2/Java Overview This chapter provides an overview of the Axis2/Java framework, its architecture, key features, advantages, and message flow.
PAGE 17

Appendix I: Hibernate Environment Setup Script This appendix contains the ei_setenv script. Appendix J: Installing Hibernate Annotations Libraries on NonStop This appendix describes the steps required to install Hibernate Annotations Libraries on your NonStop system. Appendix K: Installing Hibernate EntityManager Libraries This appendix describes the steps required to install on NonStop Hibernate EntityManager Libraries on your NonStop system.
PAGE 18

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. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none.
PAGE 19

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: CALL STEPMOM ( process-id ) ; 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: $process-name.
PAGE 20

Italic Text Italic text indicates variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed.
PAGE 21

!r The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING. !r !o The !o notation following a token or field name indicates that the token or field is optional. For example: ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32. !o General Syntax Notation This list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS Uppercase letters indicate keywords and reserved words.
PAGE 22

| Vertical Line A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: {expression | NULL} … Ellipsis An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: ATTRIBUTE[S] attribute [, attribute]... {, sql-expression}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times.
PAGE 23

HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to docsfeedback@hp.com. Include the document title, part number, and any comment, error found, or suggestion for improvement you have concerning this document.
PAGE 24
PAGE 25

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. Hence, the need for OpenSource frameworks arises.
PAGE 26

Prerequisites Before getting started, make sure that you have the requisite software installed on your NonStop and Windows system.
PAGE 27

is the version procedure of the iTP Secure WebServer release installed (for example, T8997H02_09FEB09_ADE_H028_01). For example: OSS> cd /usr/tandem/webserver/T8997H02_09FEB09_ADE_H028_01/bin NOTE: You may have more than one version of iTP Secure WebServer available on your NonStop system. Ensure that you select iTP WebServer version T8997H02 or later. 2.
PAGE 28

NonStop Servlets for Java Server Pages (NSJSP) • The version of NSJSP installed on your system must be T1222H60 or later. — If you already have NSJSP installed on your system, check its version by following these instructions: 1. Go to the /usr/tandem/nsjsp//lib directory on OSS. where, is the version procedure of the NSJSP release installed (for example, T1222H60_27JUN2008_V600_AAH_1).
PAGE 29

The setup script guides you through the deployment of NSJSP. For more information on setup, see the NonStop Servlets for JavaServerPages (NSJSP) 6.0 System Administrator's Guide. • Ensure the following settings in NSJSP: — The unpackWARs and autoDeploy parameters must be set to true in the /conf/server.xml file on your NonStop system. NOTE: — By default, unpackWARs and autoDeploy is set to false. The /conf/jdbc.
PAGE 30

The version of JDBC Type 2 driver must be T1275H50 or later. To install JDBC Type 2 driver on your NonStop system, see the JDBC Driver for SQL/MX Programmer's Reference Manual. NonStop SQL/MX The version of SQL/MX installed on your system must be T1050H23 or later. If you already have SQL/MX installed on your NonStop system, check its version by following these instructions: 1. Go to the /bin directory on OSS.
PAGE 31

Windows System The following software must be installed on your Windows system: • Java Development Kit (JDK) • Ant • JDBC Type 4 Driver for NonStop SQL/MX • Eclipse IDE Java Development Kit (JDK) The version of JDK installed on your system must be 1.5 or later. If you already have JDK installed on your Windows system, check its version using the following command: Command Prompt> java –version java version "1.5.0_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.
PAGE 32

3. Enter the variable name as JAVA_HOME and variable value as . For example: Enter C:\Program Files\Java\jdk1.5.0_05\bin as the value of PATH and C:\Program Files\Java\jdk1.5.0_05 as the value of JAVA_HOME. 4. 5. Click OK. Click Apply Changes. If you do not have JDK installed on your Windows system, download it from the website: http://java.sun.com/javase/downloads/index.jsp NOTE: All applications have been verified using JDK version 1.5.
PAGE 33

3. Enter the variable name as ANT_HOME and variable value as . For example: Enter C:\ant1.7.0RC1\bin as the value of PATH and C:\ant1.7.0RC1 as the value of ANT_HOME. 4. 5. Click OK. Click Apply Changes. If you do not have Ant 1.7.0 installed on your Windows system, download the apache-ant-1.7.0-bin.zip file from the website: http://archive.apache.
PAGE 34
PAGE 35

Part I Spring Framework Part I describes how a Spring framework can be customized to work on a NonStop system. It includes the following chapters: • Chapter 2: Spring Overview This chapter provides an overview of the Spring framework, its architecture, key features, advantages, and message flow. • Chapter 3: Installing Spring Framework This chapter helps you to install the Spring framework libraries and enables you to deploy and run sample Spring applications on your NonStop system.
PAGE 36
PAGE 37

2 Spring Overview The HP NonStop system provides a platform that makes it easy to integrate open source frameworks and build enterprise applications to cater to the ever-changing business requirements. A range of frameworks are available to build modern-day enterprise applications. One such framework is the Spring framework, which enables users to quickly and easily create high-quality enterprise applications that can be deployed on NonStop servers.
PAGE 38

Figure 2-1 Core Spring Components The functionality of each component is as follows: • Spring Core The Spring Core provides the Inversion of Control (IoC) and Dependency Injection feature and is a fundamental part of the Spring framework. It is based on the concept of BeanFactory. The BeanFactory implements factory patterns, which separates the implementation of actual business logic from the dependencies configuration and specifications.
PAGE 39

• Spring ORM The Spring Object Relational Mapping (ORM) module enables you to integrate several popular ORM tools, such as Hibernate and Java Persistence API (JPA). These ORM tools are conformant with the generic transaction and DAO exception hierarchies in Spring. • Java Enterprise Edition The Java Enterprise Edition (JEE) Context Package includes APIs that can be leveraged by a Spring context file.
PAGE 40

For more information on PATHMON processes, see the HP NonStop Pathway/iTS System Management Manual. iTP WebServer An iTP WebServer is a NonStop web server, which provides a range of services for running an online commercial or informational enterprise on the Web. The core process of the iTP WebServer is httpd, which acts as a File server and a Message-switching facility. For more information on iTP WebServer, see the iTP Secure WebServer System Administrator's Guide.
PAGE 41

Figure 2-2 Message Flow in a Spring Application A Spring message flows through all the components in the following sequence: 1. 2. 3. Web client sends Spring application request to the NonStop TCP/IP subsystem through a web browser. The NonStop TCP/IP subsystem sends the request to the httpd process of the iTP WebServer. If you are using the conventional TCP/IP, request is sent to the Distributor process of the iTP WebServer.
PAGE 42

NOTE: Because JDBC Type 2 is a dynamic-link library (DLL), it is loaded as a part of the Spring application process. However, when the JDBC Type 4 driver is used, the JDBC process runs as a separate process external to the Spring application process.
PAGE 43

Following are additional advantages of using the Spring Web Flow: • • • The UI flow in a web application is clearly visible by examining the corresponding web flow definition (typically in an XML file). Web Flows can be designed to be self-contained; you can view a part of your application as a module and reuse it in multiple situations. Web Flows can define any reasonable UI flow in a web application using the same consistent technique.
PAGE 44
PAGE 45

3 Installing Spring Framework This chapter discusses the steps required to complete the following activities: 1. 2. Installing Spring Framework Libraries on NonStop Deploying and Running Sample Spring Applications on NonStop Prerequisites Before getting started, make sure that you have the requisite software installed on your NonStop and Windows system.
PAGE 46

1. 2. Register yourself. Click No thanks, take me to the download. The Spring frameworks available for download are displayed. 3. Download the spring-framework 2.5.5-with-dependencies.zip file. NOTE: • The spring-framework 2.5.5-with-dependencies.zip file includes the Spring sample applications, the Spring framework libraries, and third party libraries that are required to build the sample applications. The other distributions, spring-framework-2.5.5-with-docs.zip and spring-framework-2.5.5.
PAGE 47

OSS> jar –xvf spring_dist.jar OSS> jar –xvf spring_lib.jar After extraction, must have two sub-directories: /dist and /lib. NOTE: The sub-directories on your NonStop system must contain the same list of files as those in the \dist and \lib directories on your Windows system. This completes the installation of Spring runtime libraries on a NonStop system.
PAGE 48

NOTE: There are four sample applications distributed with the Spring distribution, of which three (PetClinic, JPetStore, and ImageDB) are discussed here. The modifications made in these three sample applications are discussed in the Customizing Sample Applications section. PetClinic The PetClinic sample application is an information system that is accessible using a web browser.
PAGE 49

For example, if your is C:\spring-framework-2.5.5, modify spring.root to: 3. Configure the JDBC driver settings for the NonStop SQL/MX database. 1.
PAGE 50

Command Prompt> ant –buildfile build_jdbct2.xml all • If you plan to use the JDBC Type 4 driver, build the PetClinic web archive using the command: Command Prompt> ant –buildfile build_jdbct4.xml all 3. If the PetClinic build is successful, a new directory named dist is created in the \spring\samples\petclinic directory. The application WAR file (petclinic.war) is created in the dist directory.
PAGE 51

NOTE: By default, the petclinic_tables_script.sql file creates the database catalog name as petcliniccat and schema name as petclinicsch. If these names conflict with any of the existing catalog and schema names, modify the database catalog and schema names in the petclinic_tables_script.sql script file. If you modify the database catalog and schema names, edit the jdbc.properties file present in the \spring\samples\petclinic\src directory, present in SAMPLES.zip file. 6.
PAGE 52

Figure 3-1 NSJSP Web Application Manager Login Screen 2. Enter the User name and Password and click OK. The NSJSP Web Application Manager screen appears. Figure 3-2 shows the NSJSP Web Application Manager screen.
PAGE 53

3. 4. In the WAR file to deploy section, click Browse and locate the petclinic.war file on your Windows system. Click Deploy. PetClinic is listed under Applications. NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can deploy PetClinic on your NonStop system by completing the following steps: 1. Ensure that you have WRITE permissions to the webapps directory in your .
PAGE 54

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 how to build, setup, deploy, and run the JPetStore sample application.
PAGE 55

2. Modify the jdbc.properties file to update the JDBC configuration. You can use either the JDBC/MX Type 2 driver or the JDBC/MX Type 4 driver. The SQL/MX settings for each of them is as follows. • If you plan to use the JDBC/MX 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 the JDBC Type 2 driver appear as: #------------------------------------------------------------# SQL/MX Settings for JDBC Type 2 Driver jdbc.
PAGE 56

1. Edit the jpetstore_tables_script.sql file to add the following: • <$datavol>: specify the Guardian volume for the primary partition of the table. For example: $data01 • : specify the owner of the schema. For example: super.sashusr • : 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: 2. The subvolume name must only be five characters long.
PAGE 57

Deploying JPetStore on NonStop To deploy JPetStore on your NonStop system, complete the following steps: 1. Go to http://:/servlet_jsp /manager/html. The NSJSP Web Application Manager Login screen appears. Figure 3-3 shows the NSJSP Web Application Manager Login screen. Figure 3-3 NSJSP Web Application Manager: Login Screen 2. Enter the User name and Password and click OK. The NSJSP Web Application Manager screen appears.
PAGE 58

Figure 3-4 NSJSP Web Application Manager Screen 3. 4. In the WAR file to deploy section, click Browse and locate the jpetstore.war file on your Windows system. Click Deploy. JPetStore is listed under Applications. NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can deploy JPetStore on your NonStop system by completing the following steps: 1. Ensure that you have WRITE permissions to the webapps directory in your .
PAGE 59

NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can run JPetStore on your NonStop system by completing the following steps: 1. Go to the /conf directory using the command: OSS> cd /conf For example: OSS> cd /home/sash_usr/webserver/conf 2. Start your iTP WebServer using the command: OSS> ./start 3.
PAGE 60

\src includes the customized source for ImageDB. \war includes all the necessary configuration files required to build the application WAR file. 2. Modify the ImageDB build file. • If you plan to use the JDBC Type 2 driver, set the spring.root property in the \spring\samples\imagedb\build_jdbct2.xml file as:
PAGE 61

NOTE: Because JDBC Type 2 driver resides on the NonStop system, you need not mention the username and password in the jdbc.username and jdbc.password fields. • If you plan to use the JDBC/MX Type 4 driver, uncomment the SQL/MX settings for the JDBC Type 4 driver in the jdbc.properties file and enter the values of the JDBC URL (NonStop system IP Address and port number of JDBC data source), NonStop system username, and password. The SQL/MX settings for the JDBC Type 4 driver in the jdbc.
PAGE 62

NOTE: 2. The subvolume name must only be five characters long. Create a directory in OSS to place the database script files, using the command: OSS> mkdir –p /spring/samples/imagedb/dbconfig For example: OSS> mkdir –p /home/sash_usr/sash/spring/samples/imagedb/dbconfig NOTE: can be any working directory. It is suggested that you create the spring/samples/imagedb/dbconfig directory structure in . 3. Copy the imagedb_tables_script.
PAGE 63

Figure 3-5 NSJSP Web Application Manager Login Screen 2. Enter the User name and Password and click OK. The NSJSP Web Application Manager screen appears. Figure 3-6 shows the NSJSP Web Application Manager screen.
PAGE 64

3. 4. In the WAR file to deploy section, click Browse and locate the ImageDB.war file on your Windows system. Click Deploy. ImageDB is listed under Applications. NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can run ImageDB on your NonStop system by completing the following steps: 1. Go to the /conf directory using the command: OSS> cd /conf For example: OSS> cd /home/sash_usr/webserver/conf 2.
PAGE 65

4 Configuring Spring Applications on NonStop Systems This chapter provides information about configuring Spring applications on NonStop systems. This chapter includes the following sections: • • • NonStop Platform Configurations Spring Framework Configurations Module File Caching Configurations 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 66

4. 5. 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. Configure the Executor element in the /conf/server.xml file on OSS. The Executor is used by the Connector as a thread pool. Set maxThreads = 300, minSpareThreads = 10 and maxIdleTime = 30000.
PAGE 67

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 68

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 69

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 70

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.config file with the new message ID.
PAGE 71

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 72

NOTE: When the SessionBasedLoadBalancing feature is turned ON, messages are delivered to NSJSP not only through TS/MP but also through file system calls. Hence, there could be a situation that all messages delivered to a particular dynamic process are through file system calls and none through TS/MP. Therefore, TS/MP might assume that a particular dynamic process is not required any more and will shut down the process.
PAGE 73

connectionTimeout="0" acceptCount="25" maxThreads="75"/> … … Configuring the Executor Element You can configure the Executor element as a child element of the Service element in the /conf/server.xml file on OSS. The following snippet of the server.xml configuration file shows the configuration of the Executor element and how a Connector element can be configured to use an Executor element: … …
PAGE 74

• • TANDEM_RECEIVE_DEPTH must be twice the value of Maxlinks. Normally, to handle n number of messages, you need n number of threads. In extreme cases, all the n requests may timeout. While the same number of threads processing the timeout requests could still be busy, you need the same n number of threads to process the new incoming requests. Therefore, the number of threads that must be configured is (n + n = 2n).
PAGE 75

to NSJSP through TS/MP and there will not be any file system call. After the 25 requests are serviced, subsequent requests on those 25 web dialogs are delivered to NSJSP through file system I/O operations. At this stage, all 25 links to the NSJSP instance are free to process more incoming requests delivered through TS/MP. Therefore, the NSJSP instance should now be able to handle 25 more concurrent requests all being the first requests of web dialogs.
PAGE 76

-Xnoclassgc Is an optional argument to stop the Java class garbage collection. Syntax: -Xnoclassgc By default, the Java runtime reclaims space for unused Java classes. Including this optional argument may prevent any memory-leak problems.
PAGE 77

the connection URL, specify the connection URL as jdbc:sqlmx:// for the SQL/MX database in the jdbc.properties file: jdbc.properties file: jdbc.url=jdbc:sqlmx:// Establishing the Connection Specify the username and password with no values in the jdbc.properties file: jdbc.username= jdbc.password= Configurations in the applicationContext.xml File For making necessary JDBC configurations, complete the following activities: 1. 2. 3. 4.
PAGE 78

PropertyPlaceholderConfigurer class provided by the Spring framework substitutes all the database properties specified in the applicationContext.xml file with the values specified in the jdbc.properties file during runtime. Modify the applicationContext.xml file for wiring the jdbc.properties file as shown below: classpath:jdbc.
PAGE 79

jdbc.username= jdbc.password= Configurations in the applicationContext.xml File For making necessary JDBC configurations, you need to create the applicationContext.xml file and complete the following activities: 1. 2. 3. 4.
PAGE 80

classpath:jdbc.properties NOTE: For information on the complete configuration snippet of the applicationContext.xml file and the jdbc.properties file, see JDBC Configuration.
PAGE 81

} public MyObject getMyObject(String myObjectName, String myObjectDesc) { throw new UnsupportedOperationException(); } public void insertMyObject(MyObject myobject) { throw new UnsupportedOperationException(); } public void updateMyObject(MyObject myobject) { throw new UnsupportedOperationException(); } To make the DefaultMyService service object as transactional, the configuration in the applicationContext.
PAGE 82

Defining the Transactional Execution Point To ensure that the transactional advice defined in the above step is executed at the appropriate point in the program, you must define the transactional execution point. This is done using the definition in the applicationContext.xml file. Define a pointcut that matches the execution of any operation defined in the Transactional Service interface. Associate the pointcut with the advisor.
PAGE 83

NOTE: Here org.apache.commons.dbcp.BasicDataSource is used as the datasource. Defining the PlatformTransactionManager The PlatformTransactionManager is an interface; it is not tied to a lookup strategy such as JNDI, thereby making it abstract while working with JTA. The PlatformTransactionManager interface implementations normally require knowledge of the environment in which they work, such as JDBC, or JTA or Hibernate and so on. For JDBC, the implementation of PlatformTransactionManager is org.
PAGE 84

Programmatic Transaction Management The Spring framework provides two means of programmatic transaction management: • • Using the TransactionTemplate Using a PlatformTransactionManager Using the TransactionTemplate The TransactionTemplate handles the transaction lifecycle and possible exceptions so that the calling code does not explicitly handle transactions.
PAGE 85

2. Use the TransactionDefinition and TransactionStatus objects to initiate transactions, rollback, and commit. DefaultTransactionDefinition def = new DefaultTransactionDefinition(); // explicitly setting the transaction name is something that can only be done programmatically def.setName("SomeTxName"); def.setPropagationBehavior(TransactionDefinition.PROPAGATION_REQUIRED); TransactionStatus status = txManager.
PAGE 86

NOTE: C3P0 is tunable and offers a number of configuration parameters. For more information on C3P0 configuration, see http://sourceforge.net/projects/c3p0. For the complete list of parameters, see http://www.mchange.com/projects/c3p0/ index.html#appendix_a Recommendations Connection Pooling mechanism should be used when your application: • • • Cannot handle the overhead of obtaining and releasing connections frequently.
PAGE 87

Module File Caching Configurations The Module File Caching (MFC) feature shares the prepared statement plans among the NonStop SQL/MX database connections and helps in reducing resource consumption. MFC is disabled by default; therefore, it must be configured to enable it. To use the MFC feature, you must perform the following activities: • • Configuring NonStop SQL/MX DataSource for MFC Modifying the Spring Application NOTE: JDBC Type 4 driver offers MFC feature.
PAGE 88

Modifying the Spring Application NOTE: If the default datasource is configured for MFC, do not modify the Spring application. To use the MFC feature, modify the Spring application by using the following steps: 1. Modify the applicationContext.xml file as follows: • To set serverDataSource to the datasource name on which MFC is configured, add the following under connectionProperties tag.
PAGE 89

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 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 90

Developing EmpInfo on Windows using the Eclipse IDE NOTE: • This section describes the steps to develop EmpInfo using the Eclipse Integrated Development Environment (IDE). It is not mandatory to use the Eclipse IDE; you can choose any IDE that supports Java. • The Eclipse version used in this example is 3.3.1.1. The sample screen shots provided in this section are based on Eclipse IDE version 3.3.1.1. If you are using a different version of Eclipse, the screen shots may look different.
PAGE 91

Figure 5-2 Eclipse SDK Welcome Screen Close the welcome screen. The workspace is created. After the workspace is created, complete the following activities to develop the EmpInfo application using the Eclipse IDE: 1. 2. 3. 4. 5.
PAGE 92

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 5-3 shows the New Project Wizard dialog box. Figure 5-3 New Project Wizard Dialog Box The New Dynamic Web Project dialog box appears. 3. In the Project name field, enter EmpInfo and click Next. NOTE: The other fields in the New Dynamic Web Project dialog box are selected by default. Figure 5-4 shows the New Dynamic Web Project dialog box.
PAGE 93

Figure 5-4 New Dynamic Web Project Dialog Box 4. Confirm that the Java version set for your project is 5.0 or later. If the version is not set to 5.0 or later, select Java from the Project Facet list. Then select 5.0 or later from the version list and click Finish. NOTE: The Java version used in this example is 5.0. Figure 5-5 shows the New Dynamic Web Project: Project Facets.
PAGE 94

Figure 5-5 New Dynamic Web: Project Facets 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. 5. In the Project Structure, confirm that the JRE System Library is set to JRE version 1.5 or later, as shown in Figure 5-6. If the JRE version is not set to 1.5, right-click JRE System Library to select JRE 1.
PAGE 95

Figure 5-6 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. From the list of folders, select Web > JSP and click Next. Figure 5-7 shows the New File dialog box.
PAGE 96

Figure 5-7 New File Dialog Box The New JavaServer Page dialog box appears. 3. In the File name field, enter index and ensure that the parent folder is set to EmpInfo/WebContent. Click Next. Figure 5-8 shows the New JavaServer Page dialog box.
PAGE 97

Figure 5-8 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: The Use JSP Template check box is selected by default. Figure 5-9 shows the New JavaServer Page: JSP Template dialog box.
PAGE 98

Figure 5-9 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 99

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

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 101
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 102

The New XML File dialog box appears. 3. In the File name field, enter EmpInfo-servlet.xml and ensure that the parent folder is set to EmpInfo/WebContent/WEB-INF. Click Next. Figure 5-12 shows the New XML File dialog box. Figure 5-12 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. Figure 5-13 shows the New XML File: Options dialog box.
PAGE 103

Figure 5-13 New XML File: Options Dialog Box The EmpInfo-servlet.xml file is created in the EmpInfo/WebContent/WEB-INF directory. NOTE: By default, XML files open in the XML Editor. The XML Editor has two views: Design and Source view. Select the Source view. 5. Modify the EmpInfo-servlet.xml file by adding a bean entry named /insert.htm and entering com.hp.empinfo.web.EmployeeController as its class. NOTE: The com.hp.empinfo.web.
PAGE 104

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 5-1 Spring Dependency JAR Files Dependency JAR Files Source Location commons-logging.
PAGE 105

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

Figure 5-15 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. 2.
PAGE 107

Figure 5-16 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. 2. 3. On the Project Explorer frame, right-click EmpInfo and select New >Class. In the Package field, enter com.hp.empinfo.web. In the Name field, enter EmployeeController. In the Superclass field, enter org.springframework.web.servlet.mvc.SimpleFormController and click Finish.
PAGE 108

Figure 5-17 New Java Class Dialog Box The EmployeeController.java 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 109

Creating the View After completing the controller implementation for EmpInfo, complete the following steps to create the first view of the EmpInfo application: 1. 2. Create a new JSP page insert.jsp in EmpInfo/WebContent by following steps as explained in the Creating the index.jsp File section. Add as the title tag, as the header item and within the body tag of EmpInfo/WebContent/insert.
PAGE 110

Figure 5-18 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 section describes the following activities: 1. 2. 3. 4.
PAGE 111

2. In the Folder name field, enter jsp and select EmpInfo/WebContent/WEB-INF as the parent folder. Figure 5-19 shows the New Folder dialog box. Figure 5-19 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 the Creating the index.jsp File section.
PAGE 112

2. Add the tag extensions (taglibs) to include the .jsp file so that your 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 113

3. Add the tag to display the current date and time retrieved from the model passed to the view, which will be rendered using the JSTL. For example:
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 114

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 115

Figure 5-20 EmpInfo: Insert Employee Screen 3. Click Insert Employee. The EmpInfo: Employee Details screen appears. Figure 5-21 shows the EmpInfo: Employee Details screen.
PAGE 116

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.xml file in the EmpInfo/WebContent/WEB-INF directory to add the following bean to declare a new ViewResolver entry.
PAGE 117

public ModelAndView handleRequest(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { String now = (new Date()).toString(); logger.info("Returning hello view with " + now); return new ModelAndView("insert", "now", now); } } At this point, you can either deploy and verify the EmpInfo application you have developed so far on your NonStop system, or you can continue with the steps described in the Developing Business Logic and Providing the Web Interface section.
PAGE 118

1. 2. 3. 4. Creating a Simple POJO Creating Data Access Object Implementation for JDBC Creating and Modifying Supporting Views to Display Business Data Adding Dependency JAR Files Creating a Simple POJO To create a simple POJO, complete the following steps: 1. 2. Create a com.hp.empinfo.domain package and an Employee class in the com.hp.empinfo.domain package, as described in the Creating the Controller for EmpInfo section. Modify the Employee.
PAGE 119

1. 2. Create a com.hp.empinfo.service package and an EmployeeDao class under the com.hp.empinfo.service package, as described in the Creating the Controller for EmpInfo section. This will contain the logic for handling Employee Database Transactions. Modify the EmployeeDao.java class file to add the function for inserting employee details. After modification, the EmployeeDao.java file must appear as: package com.hp.empinfo.service; import java.sql.SQLException; import org.springframework.jdbc.core.
PAGE 120

PAGE 121

To add the dependency JAR file in the project library path and to resolve the J2EE module dependency on it, follow the instructions described in the Adding Dependency JAR Files in the Project Library Path section. NOTE: The code of the EmpInfo application developed so far is present in \spring\getting-started\EmpInfo-InParts\Part-5 Your project directory structure for the EmpInfo application must appear as follows: Figure 5-23 shows the Project Explorer View.

PAGE 122

2. Create a new XML file in the EmpInfo/WebContent/WEB-INF directory and enter the name of the XML file as applicationContext. NOTE: By default, XML files open in the XML Editor. The XML Editor has two views: Design and Source view. Select the Source view. 3. Modify the applicationContext.xml file to add a bean definition of the EmployeeDao class. After modification, the applicationContext.xml file must appear as: PAGE 123
Figure 5-24 New File Dialog Box The jdbc.properties file is created.

PAGE 124

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 125

PAGE 126
int age = ((Employee) command).getAge(); String email = ((Employee) command).getEmail(); empdao.insertDetail(empid, firstname, lastname, age, email); Map model = new HashMap(); model .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.

PAGE 127

Modifying the web.xml File To modify the web.xml in the EmpInfo/WebContent/ directory, complete the following steps: NOTE: By default, XML files open in the XML Editor. The XML Editor has two views: Design and Source view. Select the Source view. 1. Add ContextLoaderListener to load the applicationContext.xml file under the tag: org.springframework.web.context.

PAGE 128

Table 5-4 Jakarta Commons Dependency JAR Files Dependency JAR Files Source Location commons-collections.jar /lib/jakarta-commons commons-lang.jar /lib/jakarta-commons 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-5 JDBC Type 4 Dependency JAR File Dependency JAR File t4sqlmx.

PAGE 129

Figure 5-25 Project Explorer View At this point, you can either deploy and verify the EmpInfo application you have developed so far on your NonStop system, or you can proceed to the Enabling EmpInfo to Delete and Retrieve Employee Details section. NOTE: The code for the EmpInfo application developed so far is present in \spring\getting-started\EmpInfo-InParts\Part-6 To verify your EmpInfo application developed so far, complete the following steps: 1. 2.

PAGE 130

Figure 5-26 EmpInfo: Insert Employee Screen 3. On the EmpInfo: Insert Employee screen, click Insert Employee . The EmpInfo: Employee Details screen appears. 4. Enter the employee details and click Insert. Figure 5-27 shows the EmpInfo: Employee Details screen.

PAGE 131

The message Insert Operation Successfully Executed is displayed. Figure 5-28 shows the EmpInfo: Message screen. Figure 5-28 EmpInfo: Message Screen Enabling EmpInfo to Delete and Retrieve Employee Details This section describes the following activities: 1. 2. 3. 4. 5. 6. 7. Creating JSPs to Delete and Retrieve Employee Details Creating the RowMapper Class Modifying the EmployeeDao.java Class File Modifying the Employee.java File Modifying the EmployeeController.java File Modifying the EmpInfo-servlet.

PAGE 132

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

PAGE 133

Employee Id :

First Name :

Last Name :

Age :

Employee Email Id :

">Back 5. 6. Create the deleteresult.jsp file in the EmpInfo/WebContent/WEB-INF/jsp directory, as described in the Creating the index.jsp File section. Modify the deleteresult.jsp file to remove the details of an employee record from the JSP page. After modification, the deleteresult.
PAGE 134

employee.setEmail(rs.getString(5)); return employee; } } Modifying the EmployeeDao.java Class File To modify the EmployeeDao.java in com.hp.empinfo.service package, complete the following steps: 1. 2. Add two new methods getDetail and deleteEmployee in the EmployeeDao.java class file to add the retrieve and delete functionality in the application. 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.
PAGE 135

private String rord; public String getRord() { return rord; } public void setRord(String rord) { this.rord = rord; } 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.
PAGE 136

SQLException { WebApplicationContext wac = WebApplicationContextUtils. getRequiredWebApplicationContext(getServletContext ()); empdao = (EmployeeDao) wac.getBean("empdao"); int empid = ((Employee) command).getEmpid(); 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.
PAGE 137

xmlns:aop="http://www.springframework.org/schema/aop" xmlns:p="http://www.springframework.org/schema/p" xmlns:context="http://www.springframework.org/schema/context" 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.
PAGE 138

>Insert Employee

> Retrieve or Delete

Figure 5-29 shows what your EmpInfo application directory structure must look like after creating the requisite files on your system. Figure 5-29 shows the Project Explorer View. Figure 5-29 Project Explorer View Your EmpInfo application is complete now.
PAGE 139

Figure 5-30 EmpInfo: Retrieve or Delete Employee Details 2. Click Retrieve or Delete to access the following URL: http://:/servlet_jsp/EmpInfo/retrieveordelete.htm Figure 5-31 shows the EmpInfo: Retrieve screen.
PAGE 140

3. To retrieve an employee record, in the Action to Perform field, enter Retrieve. Click Retrieve/Delete. The employee record details are displayed. Figure 5-32 shows the Employee Details screen. Figure 5-32 EmpInfo: Employee Details Screen 4. Click Back to return to the EmpInfo: Delete screen. Figure 5-33 shows the EmpInfo: Delete screen.
PAGE 141

Figure 5-33 EmpInfo: Delete Screen 5. To delete an employee record, in the Action to Perform field, enter Delete. Click Retrieve/Delete. The employee record is deleted. Figure 5-34 shows the EmpInfo: Deleted screen.
PAGE 142

Deploying EmpInfo on NonStop This section describes the following tasks: 1. 2. Creating the Application WAR File on Windows Deploying the EmpInfo WAR File in NSJSP on NonStop 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 143

Figure 5-36 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 144

Figure 5-37 NSJSP Web Application Manager Login Screen 2. Enter the User name and Password and click OK. The NSJSP Web Application Manager screen appears. Figure 5-38 shows the NSJSP Web Application Manager screen.
PAGE 145

3. 4. In the WAR file to deploy section, click Browse and locate the EmpInfo.war file on your Windows system. Click Deploy. EmpInfo is listed under Applications. NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can deploy EmpInfo on your NonStop system by completing the following steps: 1. Ensure that you have WRITE permissions to the webapps directory in your .
PAGE 146
PAGE 147

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 148
PAGE 149

B Customizing Sample Applications Customizing PetClinic To customize the PetClinic sample application to run on NonStop systems, six files were modified and a directory and file were added. Added Directory: • /etc Added File: • SetDatabase.java Modified Files: • build_jdbct2.xml • build_jdbct4.xml • web.xml • petclinic.hbm.xml • applicationContext-hibernate.xml • jdbc.properties Added Directory /etc (\samples\petclinic\etc) This directory is included in the SAMPLES.
PAGE 150

Modified Files The following files were modified to customize PetClinic. build_jdbct2.xml (\samples\petclinic\build_jdbct2.xml) This is the build file for PetClinic when using the JDBC Type 2 driver for database connectivity. The build_jdbct2.xml file was modified to: • Update the Spring Root Location (property:spring.root) • Include the Hibernate SQL/MX dialect file (hibernate3sqlmx.jar) • Include the Commons DBCP JAR file (commons-dbcp.
PAGE 151

NOTE: The build.xml file in the Spring distribution has been customized for the JDBC Type 2 driver and is provided as the build_jdbct2.xml file in the SAMPLES.zip file. Changes to the build_jdbct2.xml file The changes to the build_jdbct2.xml file are as follows: • For JDBC Type 2 driver, the following modifications were made: 1. The spring.root property with the directory was updated. For example: Before updating, the spring.root property in the build_jdbct2.
PAGE 152

• • Include the Hibernate SQL/MX dialect file (hibernate3sqlmx.jar) Include the Commons DBCP JAR file (commons-dbcp.jar) NOTE: The build.xml file in the Spring distribution has been customized for JDBC Type 2 driver and is provided as the build_jdbct4.xml file in the SAMPLES.zip file. Changes to the build_jdbc4.xml file The changes to the build_jdbct4.xml file are as follows: 1. The spring.root property was updated with the directory. For example: Before updating, the spring.
PAGE 153

…. …. 5. The path of the Commons DBCP JAR file (commons-dbcp.jar) was set. A new tag was added to specify the path of the Commons DBCP JAR file location under the tag: …. …. web.
PAGE 154

/WEB-INF/applicationContext-jdbc.xml /WEB-INF/applicationContext-jpa.xml --> petclinic.hbm.xml (\samples\petclinic\src\petclinic.hbm.
PAGE 155

> jdbc.properties (\samples\petclinic\src\jdbc.properties) This configuration file is used for connecting to the SQL/MX database and was modified to add the SQL/MX JDBC properties instead of the default HSQL JDBC properties used by PetClinic. Changes to the jdbc.
PAGE 156

# - This is the IP address of your NonStop system # - This is the Port Number of JDBC Data Source # - This is the HP NonStop system UserName # - This is the HP NonStop system Password Customizing JPetStore To customize the JPetStore sample application to run on NonStop systems, one file was added and six files were modified: Added File: • SetDatabase.java Modified Files: • build_jdbct2.xml • build_jdbct4.xml • Item.
PAGE 157

The build_jdbct2.xml file was modified to: • Update the Spring Root Location (property:spring.root) • Include the Commons DBCP JAR file (commons-dbcp.jar) NOTE: The build.xml file in the Spring distribution has been customized for the JDBC Type 2 driver and is provided as build_jdbct2.xml in the SAMPLES.zip file. Changes to the build_jdbct2.xml file The build_jdbct2.xml file was modified as follows: 1. The spring.root property was updated with the directory.
PAGE 158

…. …. 4. The path of the Commons DBCP JAR file (commons-dbcp.jar) was set.
PAGE 159

After the change: PAGE 160
#For JDBC Type 4 Driver: # # - This is the IP address of your NonStop system # - This is the Port Number of JDBC Data Source # - This is the HP NonStop system UserName # - This is the HP NonStop system Password Order.xml (\jpetstore\src\org\springframework\samples\jpetstore\dao\ ibatis\Order.xml): Order.xml is the ibatis mapping file that maps the Order.java class to the order table.
PAGE 161

NOTE: The build.xml file in the Spring distribution has been customized for the JDBC Type 2 driver and is provided as build_jdbct2.xml in the SAMPLES.zip file. Changes to the build_jdbct2.xml file The following modification was made in the build_jdbct2.xml file: The spring.root property was updated with the directory. For example: Before updating, the spring.root property in the build_jdbct2.xml file appeared as: After updating, the spring.
PAGE 162

applicationContext.xml (\samples\imagedb\war\WEB-INF\applicationContext.xml): The applicationContext.xml file contains all the configuration metadata for ImageDB. This file is modified to set the following properties: • catalog • schema • blobTableName Changes to the applicationContext.xml file The dataSource bean is modified to set the catalog, schema, and blobTableName properties. Before the change: PAGE 163
• Increased the time interval for which the application invokes the checkImages method in the org.springframework.samples.imagedb.DefaultImageDatabase class. Before the change : PAGE 164
#jdbc.url=jdbc:sqlmx:// #jdbc.username= #jdbc.password= #------------------------------------------------------------------------------# SQL/MX Settings for JDBC Type 4 Driver #jdbc.driverClassName=com.tandem.t4jdbc.SQLMXDriver #jdbc.url=jdbc:t4sqlmx://: #jdbc.username= #jdbc.password= #For JDBC Type 4 Driver: # - This is the IP address of your NonStop system #
PAGE 165

void storeImage(String name, InputStream is, int contentLength, String description)throws DataAccessException; After the change: void storeImage(String name, byte[] fl, String description); DefaultImageDatabase.java (\samples\imagedb\src\org\springframework\samples\ imagedb\ web\DefaultImageDatabase.java): This Java file includes implementations of the central image database business interface.
PAGE 166

); } • The storeImage function (final String name, final InputStream contentStream, final int contentLength, final String description) was modified to enable the data entry to the BLOB table. Before the change: @Transactional public void storeImage( final String name, final InputStream contentStream, final int contentLength, final String description) throws DataAccessException { getJdbcTemplate().
PAGE 167

C JDBC Configuration This section 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 168
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 169

D Installing Spring Web Flow To use Spring Web Flow for your application development, install the Spring Web Flow distribution on your NonStop system.
PAGE 170

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 171

Part II Axis2/Java Framework Part II describes how an Axis2/Java framework can be customized to work on a NonStop system. It includes the following chapters: • Chapter 6: Axis2/Java Overview This chapter provides an overview of the Axis2/Java framework, its architecture, key features, advantages, and message flow.
PAGE 172
PAGE 173

6 Axis2/Java Overview Simple Object Access Protocal (SOAP) is an XML based messaging protocol that is used to communicate with webservices. SOAP provides a standard mechanism to exchange information over a distributed environment. The Axis2/Java framework implements the SOAP protocol, which enables you to expose applications on the NonStop platform as webservices. This feature enables you to integrate your NonStop applications into Service Oriented Architecture (SOA) implementation.
PAGE 174

Axis2/Java has a modular architecture and consists of the following modules: • Information Processing The Message Receiver/Sender model contains all the information about the state of objects and their hierarchy. • XML Parser The XML Parser provides a simple API for the SOAP and XML information set to handle SOAP messages. • SOAP Engine The SOAP Engine controls the execution of the SOAP processing.
PAGE 175

• Message exchange support Axis2/Java supports the request-response message exchange pattern and the one-way message exchange pattern. Both these patterns are defined in the by defined in the WSDL file. • Extensible architecture The Axis2/Java architecture enables you to add custom header processing and system management features, thereby making it an extensible architecture.
PAGE 176

NonStop Servlets for JavaServer Pages The NonStop Servlets for JavaServer Pages (NSJSP) 6.0 implementation is a multi-thread, out-of-process servlet container, and a Java web container that runs on a Java Virtual Machine (JVM) outside the iTP WebServer httpd process. NSJSP includes the following components: • • NSJSP Connector NSJSP Container For more information on NSJSP, see the NonStop Servlets for JavaServer Pages (NSJSP) 6.0 System Administrator's Guide.
PAGE 177

calls. The first request is always routed to an NSJSP instance through TS/MP using Pathsend calls. TS/MP determines the least loaded instance of NSJSP and routes the request to it. Subsequent requests from the web client are either routed to a particular instance of NSJSP through file system calls or are sent to an instance of NSJSP through TS/MP using Pathsend calls. For more information on Pathsend calls, see the HP NonStop TS/MP Pathsend and Server Programming Manual. 4. 5. 6.
PAGE 178
PAGE 179

7 Installing Axis2/Java Framework This chapter discusses the steps required to complete the following activities: 1. 2. Installing Axis2/Java on NonStop Deploying and Running Axis2/Java Sample Applications on NonStop Prerequisites Before getting started, make sure that you have the requisite software installed on your NonStop and Windows system.
PAGE 180

NOTE: The following distributions are available for download: • Standard Binary Distribution: includes the Axis2/Java binaries and sample applications. • Source Distribution: includes the source of the Axis2 standard distribution. • Web Archive (WAR) Distribution: includes the web application to be deployed on servlet containers. • Documents Distribution: includes the documentation for Axis2/Java. 2. Download the Standard Binary Distribution in the zip format.
PAGE 181

Deploying Axis2/Java as a Web Application on NonStop To deploy Axis2/Java on your NonStop system, complete the following steps: 1. Go to http://:/servlet_jsp /manager/html. The NSJSP Web Application Manager Login screen appears. Figure 7-1 shows the NSJSP Web Application Manager Login screen. Figure 7-1 NSJSP Web Application Manager Login Screen 2. Enter the User name and Password and click OK. The NSJSP Web Application Manager screen appears.
PAGE 182

Figure 7-2 NSJSP Web Application Manager Screen 3. 4. In the WAR file to deploy section, click Browse and locate the axis2.war file on your Windows system. Click Deploy. Axis2/Java is listed under Applications. NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can deploy Axis2/Java on your NonStop system by completing the following steps: a. Ensure that you have WRITE permissions to the webapps directory in your .
PAGE 183

1. Click the /servlet_jsp/axis2 path under Applications in the NSJSP Web Application Manager screen. NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can run Axis2/Java on your NonStop system by completing the following steps: a. Go to the /conf directory using the command: OSS> cd /conf For example: OSS> cd /home/sash_usr/webserver/conf b. Start your iTP WebServer using the command: OSS> ./start c.
PAGE 184

Figure 7-4 Axis2/Java Validate Screen Deploying and Running Axis2/Java Sample Applications on NonStop This section discusses the steps to deploy the following sample applications distributed along with the Axis2/Java binary distribution: • • FaultHandling MTOM NOTE: The Axis2/Java distribution contains several sample applications. Among all these sample applications, only FaultHandling and MTOM are discussed here for demonstration purposes.
PAGE 185

Building FaultHandling on Windows To build FaultHandling on your Windows system, complete the following steps: 1. Go to the \samples\faulthandling directory on your Windows system, using the command: command prompt> cd \samples\faulthandling For example: command prompt> cd C:\axis2-1.4.1-bin\samples\faulthandling 2. Generate the service. To do so, complete the following steps: a. Clean the output directory (if already present) using the command: command prompt> ant clean b.
PAGE 186

cd C:\axis2-1.4.1-bin\samples\faulthanding 2. You can use the following sample runs to check if BankService is successfully invoked. • command prompt> ant run.client -Durl=http://:/servlet_jsp/axis2/services/ BankService -Daccount=13 -Damt=400 The output must include the following: Account#13 does not exist • command prompt> ant run.
PAGE 187

Deploying MTOM on NonStop To deploy the MTOMSample webservice under Axis2/Java web application, complete the following steps: 1. 2. Copy the sample-mtom.aar file from the \samples\mtom\build\service directory on Windows system to /webapps/axis2/WEB-INF/services OSS directory on your NonStop system.
PAGE 188

command prompt> ant run.client -Dfile "C:\testfile.txt” –Ddest testfile.txt Confirm the following: a. b. The message File saved successfully appears on the command prompt. The Destination-file-name file is present in . You can thus use MTOM to transfer any file from a Windows system to a NonStop system.
PAGE 189

8 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 Axis2/Java Framework Configurations for NonStop Systems 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 190

4. 5. 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. Configure the Executor element in the /conf/server.xml file on OSS. The Executor is used by the Connector as a thread pool. Set maxThreads = 300, minSpareThreads = 10 and maxIdleTime = 30000.
PAGE 191

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 192

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 193

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 194

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.config file with the new message ID.
PAGE 195

Syntax: -DSessionBasedLoadBalancing=[ true | false ] NOTE: The default value of -DSessionBasedLoadBalancing is set to true. For example, if you want to enable the SessionBasedLoadBalancing feature for your Axis2/Java application and save the application sessions in a persistent store, set the Arglist as: Server … … … … $server_objectcode { Arglist -DSessionBasedLoadBalancing=true \ -DSaveSessionOnCreation=true \ … … … … } where, server_objectcode is mapped to the servlet.
PAGE 196

For more information on the SessionBasedLoadBalancing and SessionBasedLoadBalancing configuration directives, see the NonStop Servlets for JavaServer Pages (NSJSP) 6.0 System Administrator's Guide. Configuring Connector Threads The Connector is responsible for creating and maintaining the threads that are used for message processing.
PAGE 197

NOTE: All executors that are configured in NSJSP must implement the java interface org.apache.catalina.Executor. NSJSP provides a standard implementation of this interface in the class org.apache.catalina.core.StandardThreadExecutor. Configuring TS/MP Specific Parameters This section describes the following TS/MP specific configuration parameters: 1. 2. 3. 4. 5. Numstatic – Determines the number of static NSJSP processes. Maxservers - Determines the total number of NSJSP processes.
PAGE 198

TANDEM_RECEIVE_DEPTH) of (25+25). Thus, you must set the value of TANDEM_RECEIVE_DEPTH to 50. The reason for setting TANDEM_RECEIVE_DEPTH to a value of 50 can be explained as: To handle 25 messages, you need 25 threads. In an extreme case where all the 25 requests time out, you need another 25 threads to process the new incoming 25 requests because the threads processing the timeout requests could still be busy. Therefore, the number of threads that need to be configured is (25+25 = 50).
PAGE 199

Configuring Java Runtime Arguments The configurations for Java runtime arguments can be done in the /conf/servlet.config file on OSS. The sscaux object is configured under the Server directive. The Java runtime arguments are populated in the Arglist. Some of the 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.
PAGE 200

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 201

9 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 202

1. 2. 3. Creating the Web Service Implementation Class Creating the Deployment Descriptor Creating an Axis2/Java AAR File Creating the Web Service Implementation Class To create the Web Service implementation class, complete the following steps: 1. 2. 3. Create the TemperatureConverter sub-directory in \axis2\gettingstarted directory on your Windows system. Create a Java class TemperatureConverter.java in the TemperatureConverter directory using any text editor.
PAGE 203

/** * Temperature Converter Implementation Class */ public class TemperatureConverter { /** * util method to convert celsius to fahrenheit * @param cValue : double value of celsius * @return calculated value of fahrenheit */ public double c2fConversion(double cValue) { return ((cValue * 9.0)/5.0 )+ 32.0; } /** * util method to convert fahrenheit to celsius * @param fValue : double value of fahrenheit * @return calculated value of celsius */ public double f2cConversion(double fValue) { return ((fValue - 32.
PAGE 204

TemperatureConverter false true PAGE 205
must display WRITE permissions to the services directories. If these directories do not have WRITE permission set, run the following commands: OSS> chmod +w /webapps/axis2/WEB-INF/services For example: OSS> chmod +w 3. /home/sash_usr/webserver/servlet_jsp/webapps/axis2/WEB-INF/services After verifying the permissions, copy TemperatureConverter.aar to /webapps/axis2/WEB-INF/services directory.
PAGE 206

Figure 9-1 TemperatureConverter List Services Screen You can view the auto-generated WSDL file for the TemperatureConverter application by clicking the TemperatureConverter in Figure 9-1. Figure 9-2 shows the WSDL file for the TemperatureConverter Web Service WSDL.
PAGE 207

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 IDE To invoke the TemperatureConverter service running on your NonStop system, you need to create a Axis2/Java client on your Windows system. The APIs of the client application will be used to invoke the web service.
PAGE 208

Figure 9-4 Eclipse SDK Welcome Screen Close the Welcome screen. The Workspace is created. 3. 4. Click File > New > Java Project to open the New Project dialog box. From the list of folders, select Java > Java Project and click Next. Figure 9-5 shows the New Project dialog box.
PAGE 209

The New Java Project dialog box appears. 5. In the Project name field, enter the name of the project you want to create and 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. Figure 9-6 shows the New Java Project dialog box.
PAGE 210

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

Figure 9-9 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. 2. 3. On the Project Explorer frame, right-click the com.hp.client package and select New > Class. The New Java Class dialog box appears. In the Name field, enter TemperatureConverterClient. Select public static void main(String[ ] args).
PAGE 212

Figure 9-10 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 213

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 214

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://: /servlet_jsp/axis2/services/TemperatureConverter")); // Setting action ,and which can be found from the wsdl of the service opts.setAction("urn:c2fConversion"); // setting created option into service client client.
PAGE 215

Table 9-1 Axis2/Java Dependency JAR Files (continued) Dependency JAR Files Source Location axiom-api-1.2.7.jar /lib axiom-impl-1.2.7.jar /lib axis2-adb-1.4.1.jar /lib axis2-kernel-1.4.1.jar /lib backport-util-concurrent-3.1.jar /lib commons-logging-1.1.1.jar /lib commons-httpclient-3.1.jar /lib commons-codec-1.3.jar /lib geronimo-stax-api_1.0_spec-1.0.1.
PAGE 216

Figure 9-11 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 9-12 shows the AxisClient Project Structure in the project explorer window.
PAGE 217

Figure 9-12 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 9-13 shows the Java Eclipse SDK -Options.
PAGE 218

Figure 9-13 Java Eclipse SDK - Options The following output is displayed on the console. 39.2 -15.555555555555555 Figure 9-14 shows the output in the console.
PAGE 219

Figure 9-14 Console Overview of TemperatureConverter 219
PAGE 220
PAGE 221

Part III MyFaces Framework Part III describes how a MyFaces framework can be customized to work on a NonStop system. It includes the following chapters: • Chapter 10: MyFaces Overview This chapter provides an overview of the MyFaces framework, its architecture, key features, advantages and message flow. • Chapter 11: Installing MyFaces Framework This chapter helps you to install the MyFaces framework libraries and enables you to deploy and run sample MyFaces applications on your NonStop system.
PAGE 222
PAGE 223

10 MyFaces Overview JavaServer Faces (JSF) is based on the Model-View-Controller (MVC) architecture, which provides a rich and comprehensive set of components that help you create and maintain the Graphical User Interface (GUI) for any web application. Among many JSF implementations, the Apache MyFaces implementation is the most popular because it provides all the necessary components required for creating the commonly used web forms.
PAGE 224

The basic architecture of JSF is based on the Model-View-Controller (MVC) design pattern. The key components of this design pattern are: • Model This block contains the business logic of the application and handles the corresponding data. • View This is the presentation layer that contains the user-interface code and comprises JSF pages. • Controller This block handles all user interactions with the application and constitutes Faces servlets.
PAGE 225

NonStop Servlets for JavaServer Pages The NonStop Servlets for JavaServer Pages (NSJSP) 6.0 implementation is a multi-thread, out-of-process servlet container, and a Java web container that runs on a Java Virtual Machine (JVM) outside the iTP WebServer httpd process. NSJSP includes the following components: • • NSJSP Connector NSJSP Container For more information on NSJSP, see the NonStop Servlets for JavaServer Pages (NSJSP) 6.0 System Administrator's Guide.
PAGE 226

3. The httpd processes of the iTP WebServer communicate with the NSJSP processes either using Pathsend calls through TS/MP or directly with an NSJSP process using File System calls. The first request is always routed to an NSJSP instance through TS/MP using Pathsend calls. TS/MP determines the least loaded instance of NSJSP and routes the request to it.
PAGE 227

• Support for multiple customer requirements Because of the extensible architecture of JSF, you can generate your own component tag libraries by extending the component classes. This feature enables you to support customer-specific requirements. • Flexible display model The rendering feature in MyFaces enables you to separate the functionality and display of the application. Therefore, you can create multiple displays and provide a different appearance for the same component.
PAGE 228
PAGE 229

11 Installing MyFaces Framework This chapter discusses the steps required to complete the following activities: 1. 2. Installing MyFaces Framework Libraries on NonStop Deploying and Running Sample MyFaces Application on NonStop Prerequisites Before getting started, make sure that you have the requisite software installed on your NonStop and Windows system.
PAGE 230

NOTE: • The myfaces-core-1.2.5-bin.zip and myfaces-core-1.2.5-bin.tar.gz files include the MyFaces framework libraries and third party libraries that are required to build MyFaces applications. These files only differ in their compression formats. • The sample application (Tomahawk) discussed in this section has been verified using MyFaces version 1.2.5 only. 3. Extract the myfaces-core-1.2.5-bin.zip or myfaces-core-1.2.5-bin.tar.gz file into a directory on your Windows system.
PAGE 231

NOTE: The SAMPLES file is distributed as a part of the NS Samples for Java Frameworks - T0874 and can be downloaded from Scout for NonStop Servers. Before you start deploying the sample applications, complete the following steps: 1. 2. 3. Download SAMPLES file from Scout for NonStop Servers. Add .zip extension to it. The file is now named as SAMPLES. zip. Extract SAMPLES. zip file to a location on your Windows system. The NS-Samples-for-Java-Frameworks folder appears.
PAGE 232

NOTE: Besides commons-fileupload-1.0.zip and commons-fileupload-1.0.tar.gz , you will also find links to their respective signature files, commons-fileupload-1.0.zip.asc and commons-fileupload-1.0.tar.gz.asc. You need not download the signature files. • commons-el.jar Download commons-el-1.0.zip or commons-el-1.0.tar.gz from: http:// archive.apache.org/dist/commons/el/binaries/. Both the files contain the binary distributions. The only difference is in their compression format.
PAGE 233

NOTE: Besides the jakarta-taglibs-standard-1.1.2.zip and jakarta-taglibs-standard-1.1.2.tar.gz files, you will also find the links to their respective signature files, jakarta-taglibs-standard-1.1.2.zip.asc and jakarta-taglibs-standard-1.1.2.tar.gz.asc. You need not download the signature files. • oro-2.0.8.jar Download jakarta-oro-2.0.8.zip or jakarta-oro-2.0.8.tar.gz from http:// archive.apache.org/dist/jakarta/oro/binaries/. Both the files contain the binary distributions.
PAGE 234

This completes the building of myfaces-components application WAR file on your Windows system. Deploying myfaces-components on NonStop To deploy myfaces-components on your NonStop system, complete the following steps: 1. Go to http://:/servlet_jsp /manager/html. The NSJSP Web Application Manager Login screen appears. Figure 11-1 shows the NSJSP Web Application Manager Login screen. Figure 11-1 NSJSP Web Application Manager Login Screen 2.
PAGE 235

Figure 11-2 NSJSP Web Application Manager Screen 3. 4. In the WAR file to deploy section, click Browse and locate the myfaces-components.war file on your Windows system. Click Deploy. myfaces-components is listed under Applications. NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can deploy myfaces-components on your NonStop system by completing the following steps: 1. Ensure that you have WRITE permissions to the webapps directory in your .
PAGE 236

NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can run myfaces-components on your NonStop system by completing the following steps: 1. Go to the /conf directory using the command: OSS> cd /conf For example: OSS> cd /home/sash_usr/webserver/conf 2. Start your iTP WebServer using the command: OSS> ./start 3.
PAGE 237

— — • t:validateCreditCard: This tag allows you to validate various credit cards, including Amex, Visa, Mastercard, and Discover, using the Jakarta Commons validation library. t:validateEqual: This tag allows you to validate user input by comparing it with another backing bean property. This is useful, for example, when validating a password or an e-mail address twice. http://:/servlet_jsp/myfaces-components/tabbedPanes.
PAGE 238
PAGE 239

12 Configuring MyFaces Applications on NonStop Systems This chapter provides information about configuring JavaServer Faces (MyFaces) applications on NonStop systems. This chapter includes the following section: • NonStop Platform Configurations NonStop Platform Configurations On a NonStop system, an application developed using the MyFaces framework is deployed as a web application in the NSJSP container.
PAGE 240

4. 5. 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 NSJSP process is able to read a maximum of 250 messages simultaneously from its $RECEIVE file. Configure the Executor element in the /conf/server.xml file on OSS. The Executor element is used by the Connector as a thread pool. Set maxThreads = 300, minSpareThreads = 10 and maxIdleTime = 30000.
PAGE 241

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 242

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 243

After determining the values, you can use any the following approaches to configure 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 244

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.config file with the new message ID.
PAGE 245

Syntax: -DSessionBasedLoadBalancing=[ true | false ] NOTE: The default value of -DSessionBasedLoadBalancing is set to true. For example, if you want to enable the SessionBasedLoadBalancing feature for your MyFaces application and save the application sessions in a persistent store, set the Arglist as: Server … … … … $server_objectcode { Arglist -DSessionBasedLoadBalancing=true \ -DSaveSessionOnCreation=true \ … … … … } where, server_objectcode is mapped to the servlet.
PAGE 246

For more information on the SessionBasedLoadBalancing and SessionBasedLoadBalancing configuration directives, see the NonStop Servlets for JavaServer Pages (NSJSP) 6.0 System Administrator's Guide. Configuring Connector Threads The Connector is responsible for creating and maintaining the threads that are used for message processing.
PAGE 247

NOTE: All Executor elements that are configured in NSJSP must implement the Java interface org.apache.catalina.Executor. NSJSP provides a standard implementation of this interface in the class org.apache.catalina.core.StandardThreadExecutor. Configuring TS/MP Specific Parameters This section describes the following TS/MP specific configuration parameters: 1. 2. 3. 4. 5. Numstatic – Determines the number of static NSJSP processes. Maxservers - Determines the total number of NSJSP processes.
PAGE 248

by TANDEM_RECEIVE_DEPTH) of (25+25). Thus, you must set the value of TANDEM_RECEIVE_DEPTH to 50. The reason for setting TANDEM_RECEIVE_DEPTH to a value of 50 can be explained as: To handle 25 messages, you need 25 threads. In an extreme case where all the 25 requests time out, you need another 25 threads to process the new incoming 25 requests because the threads processing the timeout requests could still be busy. Therefore, the number of threads that need to be configured is (25+25 = 50).
PAGE 249

Configuring Java Runtime Arguments The configurations for Java runtime arguments can be done in the /conf/servlet.config file on OSS. The sscaux object is configured under the Server directive. Java runtime arguments are populated in the Arglist. Some of the important Java runtime arguments that you must consider during the deployment of your MyFaces application are: • • • -Xmx -Xss -Xnoclassgc There are other Java runtime arguments supported by NSJSP.
PAGE 250

4. 5. 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. Configure the Executor element in /conf/server.xml file on OSS. The Executor element is used by the Connector element as a thread pool. Set maxThreads = 300, minSpareThreads = 10 and maxIdleTime = 30000.
PAGE 251

13 Getting Started with MyFaces This chapter explains how to develop a web application using the MyFaces framework. It describes the steps required to build a basic MyFaces sample called SkinSelector 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 252

1. Open the Eclipse IDE by double-clicking the eclipse.exe file in . The Workspace Launcher dialog box appears. By default, the workspace is set to your existing workspace, if already created. Figure 13-1 shows the Workspace Launcher dialog box. Figure 13-1 Workspace Launcher Dialog Box 2. Click OK. If you wish to create a new workspace, click Browse and select the folder you want to use as your workspace. The Eclipse SDK Welcome screen appears.
PAGE 253

Figure 13-2 Eclipse SDK Welcome Screen Close the welcome screen. The workspace is created. NOTE: file. You can find the source code for the SkinSelector application in the SAMPLES.zip Developing the SkinSelector application using Eclipse IDE requires the following activities: • • • • • • • Creating a Dynamic Web Project Creating the index.jsp File Modifying the web.
PAGE 254

Figure 13-3 New Project Dialog Box The New Dynamic Web Project dialog box appears. 3. In the Project name field, enter SkinSelector and click Next. NOTE: The other fields in the New Dynamic Web Project screen are selected by default. Figure 13-4 shows the New Dynamic Web Project dialog box.
PAGE 255

Figure 13-4 New Dynamic Web Project Dialog Box The New Dynamic Web Project: Project Facets screen appears. 4. Confirm that the Java version set for your project is 5.0 or later. If the version is not 5.0 or later, select Java from the Project Facet list. Select 5.0 or a later version from the version list and click Finish. NOTE: The Java version used in this example is 5.0. Figure 13-5 shows the New Dynamic Web Project: Project Facets.
PAGE 256

Figure 13-5 New Dynamic Web Project: Project Facets When prompted, change the perspective to Java EE and click Yes to open the new perspective. This step is required because the Dynamic Web Project is associated with the Java EE perspective. The Project Structure appears. 5. In the Project Structure, confirm that the JRE System Library is set to JRE version 1.5 or later. If the JRE version is not set to 1.5, right-click JRE System Library to select JRE 1.5 or later.
PAGE 257

Figure 13-6 Project Explorer View Creating the index.jsp File Create the index.jsp file in the SkinSelector/WebContent directory. This JSP page is the entry point for your application. To create the index.jsp file, complete the following steps: 1. On the Project Explorer view, right-click SkinSelector and select New > Other. The New File dialog box appears. 2. From the list of folders, select Web > JSP and click Next. Figure 13-7 shows the New JSP File Selection dialog box.
PAGE 258

Figure 13-7 New JSP File Selection Dialog Box The New JavaServer Page dialog box appears. 3. In the File name field, enter index.jsp and ensure that the parent folder is set to SkinSelector/WebContent. Click Next. Figure 13-8 shows the New JavaServer Page dialog box.
PAGE 259

The New JavaServer Page: JSP Template dialog box appears. 4. Select New JSP File (html) and click Finish. The template for the index.jsp file is generated. Figure 13-9 shows the New JavaServer Page: JSP Template dialog box. Figure 13-9 New JavaServer Page: JSP Template Dialog Box 5. 6. Delete the default code present in the index.jsp file. Add a redirection tag for faces-enabled page customize.jsp. NOTE: The Creating the customize.jsp File section describes how to create the customize.jsp file.
PAGE 260

SkinSelector index.html index.htm index.jsp default.
PAGE 261

Adding Dependency JAR Files to the Project Library Apart from the core MyFaces runtime JAR files, SkinSelector requires some dependency JAR files. Download the following distributions of all the dependency JAR files on your Windows system: NOTE: If you have already downloaded the servlet-api.jar, commons-el.jar, commons-lang-2.1.jar, standard.jar, and jstl.jar dependency JARs, as described in Deploying and Running Sample MyFaces Application on NonStop section, you need not download them again.
PAGE 262

Because the SkinSelector application uses the MyFaces framework, it requires the following dependency JAR files. Table 13-1 MyFaces Dependency JAR Files Dependency JAR Files Source Location commons-beanutils-1.7.0.jar \lib commons-codec-1.3.jar \lib commons-collections-3.2.jar \lib commons-digester-1.8.jar \lib commons-discovery-0.4.jar \lib commons-logging-1.1.1.jar \lib commons-el-1.0.
PAGE 263

Figure 13-10 SkinSelector Project Libraries - Java Build Path Dialog Box 5. Click OK. The dependency JAR files are added in the SkinSelector project library path. To resolve the J2EE module dependency on these JARs, complete the following steps on the Eclipse IDE: 1. On the Project Explorer frame, right-click SkinSelector and select Properties. The SkinSelector Project Libraries - J2EE Module Dependencies dialog box appears. 2. From the type filter text, select J2EE Module Dependencies.
PAGE 264

Figure 13-11 SkinSelector Project Libraries - J2EE Module Dependencies Dialog Box 4. Click OK. The J2EE module dependency on these JARs is resolved. Creating Views for SkinSelector Creating Views for SkinSelector involves the following activities: 1. 2. 3. 4. 5. 6. 7. 8. Creating the css and results Folder Creating the style.css File Modifying the style.css File Creating the customize.jsp File Modifying the customize.jsp File Creating the same-color.jsp and show-preview.
PAGE 265

Figure 13-12 New Folder Dialog Box 3. Click Finish. The css folder is created. Similarly, create the results folder with SkinSelector/WebContent/WEB-INF as its parent folder. Creating the style.css File Create a new file style.css to describe the presentation of JSP page. To create the style.css file, complete the following steps: 1. On the Project Explorer frame, right-click SkinSelector and select New > File. The New File dialog box appears. 2.
PAGE 266

Figure 13-13 New File Dialog Box 3. Click Finish. The style.css file is created. Modifying the style.css File To modify the style.css file, complete the following steps: 1. 2. 266 Double-click the style.css file in the Project Explorer frame to open it. Add the following code in the style.
PAGE 267

BODY { background-color: #FDF5E6 } A:hover { color: red } H2 { color: #440000; text-align: center; font-family: Arial, Helvetica, sans-serif } TH.TITLE { background-color: #EF8429; font-size: 28px; font-family: Arial, Helvetica, sans-serif; } .WHITE { color: white; font-family: Arial, Helvetica, sans-serif; font-size: 80%; font-weight: bold; text-decoration : none; } .DARK { background-color: black; } Creating the customize.jsp File Create a new JSP file named customize.
PAGE 268

Name:
Job Title:
PAGE 269
Color Error
You chose "" as both the foreground and background color.
try again. Modifying the show-preview.jsp File To modify the show-preview.jsp file, complete the following steps: 1. 2. Double-click the show-preview.jsp file in the Project Explorer frame to open it. Replace the default content of the show-preview.
PAGE 270

Figure 13-14 Project Explorer View Creating the Managed Beans A managed bean is a Java class for JSF applications. It is a Plain-Old Java Object (POJO) that conforms to Java Beans naming conventions. For a JSF application to refer to its Java classes, their methods and properties, it has to be available in the Java classpath and registered in the faces-config.xml (). NOTE: faces-config.xml is described in the Creating the Configuration File section.
PAGE 271

Figure 13-15 New Java Package Dialog Box 3. Click Finish. The coreservlets package is created. Creating a New Java Class File To create a new Java class file in the coreservlets package, complete the following steps: 1. On the Project Explorer frame, right-click coreservlets package, and select New > class. The New Java Class dialog box appears. 2. Ensure that the Source folder is SkinSelector/src and the parent Package is coreservlets. In the class Name field, enter ResumeBean.
PAGE 272

Figure 13-16 New Java Class Dialog Box 3. Click Finish The ResumeBean Java class is created. Modifying the Java Class File To modify the ResumeBean.java file, complete the following steps: 1. 2. 272 Double-click the ResumeBean.java file in the Project Explorer frame to open it. Replace the default contents of the ResumeBean.
PAGE 273

package coreservlets; import javax.faces.model.*; import javax.faces.event.*; import java.io.
PAGE 274

public String getColorSupportLabel() { if (isColorSupported) { return("Disable Color Customization"); } else { return("Enable Colors Customization"); } } public boolean isUsingColorNames() { return(isUsingColorNames); } public void setUsingColorNames(boolean isUsingColorNames) { this.isUsingColorNames = isUsingColorNames; } public void changeColorMode(ValueChangeEvent event) { boolean flag = ((Boolean)event.getNewValue()).
PAGE 275

Figure 13-17 New File Dialog Box The faces-config.xml file is created. 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. Add the following XML content in the faces-config.xml file to describe the navigation model of the application:
PAGE 276

NOTE: The resumeBean is registered as a managed bean in the faces-config.xml, which is described in the following part of the faces-config.xml: resumeBean coreservlets.ResumeBean session The navigation rules in the faces-config.
PAGE 277

Figure 13-18 Project Explorer View Deploying SkinSelector on NonStop This section describes the following activities: 1. 2. Creating the SkinSelector Application WAR File on Windows Deploying the SkinSelector WAR File in NSJSP on NonStop Creating the SkinSelector Application WAR File on Windows A WAR file is essential to deploy the web application. This file contains the Java class file, JSPs, and entire configuration XMLs.
PAGE 278

Figure 13-19 Export Dialog Box The WAR Export dialog box appears. 3. In the Web module field, enter SkinSelector and browse to the destination file to save the WAR file. Figure 13-20 shows the WAR Export dialog box.
PAGE 279

4. Click Finish. The WAR file is created. NOTE: If you have specified an existing name for the WAR file, Finish will be disabled. In this case, change the name of the WAR file or select the Overwrite existing file check box. Deploying the SkinSelector WAR File in NSJSP on NonStop To deploy the SkinSelector WAR file on your NonStop system, complete the following steps: 1. Go to http://:/servlet_jsp /manager/html.
PAGE 280

Figure 13-22 NSJSP Web Application Manager Screen 3. 4. In the WAR file to deploy section, click Browse and locate the SkinSelector.war file on your Windows system. Click Deploy. SkinSelector is listed under Applications. NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can deploy SkinSelector on your NonStop system by completing the following steps: 1. Ensure that you have WRITE permissions to the webapps directory in your .
PAGE 281

NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can run SkinSelector on your NonStop system by completing the following steps: 1. Go to the /conf directory using the command: OSS> cd /conf For example: OSS> cd /home/sash_usr/webserver/conf 2. Start your iTP WebServer using the command: OSS> ./start 3.
PAGE 282

Figure 13-24 Employee Resume Screen • If you select the same Foreground and Background color, the Color Error page (same-color.jsp) showing the try-again option appears. Figure 13-25 shows the Color Error Screen.
PAGE 283

E Installing MyFaces Trinidad Framework Libraries on NonStop Installing MyFaces Trinidad framework libraries on a NonStop system requires the following : • Downloading MyFaces Trinidad Distribution • Copying MyFaces Trinidad Runtime Libraries from Windows to NonStop Downloading MyFaces Trinidad Distribution To download the MyFaces Trinidad distribution on your Windows system, complete the following steps: 1. Go to http://www.apache.org/dist/myfaces/binaries/.
PAGE 284
PAGE 285

F Installing MyFaces Tomahawk Framework Libraries on NonStop Installing the MyFaces Tomahawk framework libraries on a NonStop system requires the following: • Downloading MyFaces Tomahawk Distribution on Windows • Copying MyFaces Tomahawk Runtime Libraries from Windows to NonStop Downloading MyFaces Tomahawk Distribution on Windows To download the MyFaces Tomahawk distribution on your Windows system, complete the following steps: 1. Go to http://www.apache.org/dist/myfaces/binaries/.
PAGE 286
PAGE 287

Part IV Hibernate Framework Part IV describes how a Hibernate framework can be customized to work on a NonStop system. It includes the following chapters: • Chapter 14: Hibernate Overview This chapter provides an overview of the Hibernate framework, its architecture, key features, advantages, and message flow.
PAGE 288
PAGE 289

14 Hibernate Overview Developing object-oriented applications using relational database can prove to be a cumbersome process because of the increasing size and complexity of enterprise applications. Hibernate is an object-relational mapping (ORM) library that helps in simplifying this task by providing a methodology to map data representation in an object-oriented model. Hibernate enables you to develop persistent Java objects for most of the traditional relational databases.
PAGE 290

The Hibernate architecture includes the following key components: • ConnectionProvider The ConnectionProvider (org.hibernate.connection.ConnectionProvider) module contains a pool of Java Database Connectivity (JDBC) or Java Transaction API (JTA) connections, which abstract applications from the underlying Datasource or DriverManager. It is an optional module. • TransactionFactory The TransactionFactory (org.hibernate.
PAGE 291

Clients Clients are Java programs that provide input parameters and can communicate directly with the Hibernate layer. JDBC Drivers for NonStop SQL/MX Java Database Connectivity (JDBC) is an API for the Java programming language that defines how a client may access a database. It provides methods for querying and updating data in a database. JDBC is oriented towards relational databases.
PAGE 292

TS/MP PATHMON Process The PATHMON process provides centralized monitoring and control of a TS/MP environment comprising server classes and objects types. For more information on conventional TS/MP PATHMON process, see the HP NonStop Pathway/iTS System Management Manual. iTP WebServer An iTP WebServer is a NonStop web server, which provides a range of services for running an online commercial or informational enterprise on the Web.
PAGE 293

Figure 14-2 Hibernate Application: Message Flow in a Standalone Application A Hibernate message flows through all the components in the following sequence: 1. 2. 3. 4. 5. A Java client program makes a function call and passes the input parameter(s) to the Hibernate application. The Hibernate application, which is deployed on a NonStop system, processes the request and performs the business validations. The Hibernate application passes the request to the JDBC layer.
PAGE 294

Figure 14-3 Hibernate Application: Message Flow in a Web Application A Hibernate message flows through all the components in the following sequence: 1. 2. 3. A Hibernate-specific request is sent to the TCP/IP subsystem through a web browser. The TCP/IP subsystem sends the request to the httpd process of the iTP WebServer. If you are using conventional TCP/IP, the request is sent to the Distributor process of iTP WebServer.
PAGE 295

5. 6. 7. The Hibernate layer processes the request and performs the business validation. It also performs the database operations (create, update, retrieve, and delete) and passes the instruction to the JDBC layer. JDBC establishes the database connection with the NonStop SQL/MX database for retrieval or manipulation of data. NonStop SQL/MX retrieves the data from the data repository.
PAGE 296

Hibernate Annotations In Hibernate, the application metadata is commonly provided to the Java Virtual Machine (JVM) through XML files. You can also use Annotations to provide the application metadata. Annotations enable you to provide the metadata for the Object and Relational Table mapping by including the metadata information in the Plain Old Java Objects (POJO) file along with the code. This helps you to understand the table structure and POJO simultaneously during application development.
PAGE 297

15 Installing Hibernate Framework This chapter discusses the steps required to complete the following activities: 1. 2. Installing Hibernate Framework Libraries on NonStop Deploying and Running Sample Hibernate Application on NonStop Prerequisites Before getting started, make sure that you have the requisite software installed on your NonStop and Windows system.
PAGE 298

1. 2. Go to http://hibernate.org/6.html. Click Browse all Hibernate downloads under Binary Releases. A web page from SOURCEFORCE.NET,showing various Hibernate packages that can be downloaded, is displayed. 3. Click hibernate3 under Package. A web page, with links to download different Hibernate3 release versions, is displayed. 4. Click 3.2.6.ga. The links to the following files are displayed: • • • • hibernate-3.2.6.ga.tar.gz hibernate-3.2.6.ga.tar.gz.md5.txt hibernate-3.2.6.ga.zip hibernate-3.2.6.ga.
PAGE 299

1. 2. 3. Download DIALECT file from Scout for NonStop Servers. Add .zip extension to it. Extract DIALECT.zip file to a location on your Windows system. The SQL/MX-Hibernate-Dialect folder containing hibernate3sqlmx.jar appears. NOTE: If you have already extracted the SAMPLE file from Scout for NonStop Servers, you can get the hibernate3sqlmx.jar file at \hibernate\sqlmxdialect. Your Hibernate distribution is now ready to be transferred to your NonStop system. NOTE: hibernate3sqlmx.
PAGE 300

The sample application distributed with the Hibernate distribution requires modifications to make it compatible with NonStop systems. For convenience, the modified sample application is included in the SAMPLES file. NOTE: The SAMPLES file is distributed as a part of the NS Samples for Java Frameworks - T0874 and can be downloaded from Scout for NonStop Servers. Before you start deploying the sample applications, complete the following steps: 1. 2. 3. Download SAMPLES file from Scout for NonStop Servers.
PAGE 301

\org includes the java source files and mapping files of Caveat Emptor. 2. Modify the build file of Caveat Emptor. • If you plan to use the JDBC Type 2 driver, set the hibernate.root property in \hibernate\samples\eg\build_jdbct2.xml as: PAGE 302
hibernate.connection.driver_class com.tandem.t4jdbc.SQLMXDriver hibernate.connection.url jdbc:t4sqlmx://: hibernate.connection.username hibernate.connection.password hibernate.connection.catalog auctioncat hibernate.connection.schema auctionsch NOTE: The hibernate.properties file, present in \hibernate\samples\eg, has the database catalog name set to auctioncat and schema name set to auctionsch.
PAGE 303

NOTE: 2. The subvolume name must only be five characters long. Create a directory in OSS to place the database script files, using the command: OSS> mkdir –p /hibernate/samples/eg/dbconfig For example: OSS> mkdir –p /home/sash_usr/sash/hibernate/samples/eg/dbconfig NOTE: can be any working directory. It is suggested that you create the hibernate/samples/eg/dbconfig directory structure in . 3. 4. Copy the caveatemptor_script.
PAGE 304

the hibernatehome variable must be set to hibernatehome=/usr/tandem/sash/hibernate-3.2.6 b. Set the value of JDBC/MX driver locations. • If you plan to use the JDBC/MX Type 2 driver, set the value of t2jdbc variable to the OSS directory.
PAGE 305

When org.hibernate.auction.
PAGE 306
PAGE 307

16 Configuring Hibernate Applications on NonStop Systems This chapter provides information about configuring Hibernate applications on NonStop systems. This chapter includes the following sections: • • • NonStop Platform Configurations Hibernate Framework Configurations for NonStop Systems Module File Caching Configurations NonStop Platform Configurations On a NonStop system, an application developed using the Hibernate framework is deployed as a web application in the NSJSP container.
PAGE 308

4. 5. 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. Configure the Executor element in the /conf/server.xml file on OSS. The Executor element is used by the Connector element as a thread pool. Set maxThreads = 300, minSpareThreads = 10 and maxIdleTime = 30000.
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 web server runs.
PAGE 310

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 configure 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

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.config file with the new message ID.
PAGE 313

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 314

NOTE: When the SessionBasedLoadBalancing feature is turned ON, messages are delivered to NSJSP not only through TS/MP but also through file system calls. Hence, there could be a situation that all the messages delivered to a particular dynamic process are through file system calls and none through TS/MP. Therefore, TS/MP may assume that a particular dynamic process is not required any more and will shut down the process.
PAGE 315

acceptCount="25" maxThreads="75"/> … … Configuring the Executor Element You can configure the Executor element as child elements of the Service element in the /conf/server.xml file on OSS. The following snippet of the server.xml configuration file shows the configuration of the Executor element and how a Connector element can be configured to use an Executor element: … …
PAGE 316

• • TANDEM_RECEIVE_DEPTH must be twice the value of Maxlinks. Normally, to handle n number of messages, you need n number of threads. In extreme cases, all the n requests may timeout. While the same number of threads processing the timeout requests could still be busy, you need the same n number of threads to process the new incoming requests. Therefore, the number of threads that must be configured is (n + n = 2n).
PAGE 317

to NSJSP through TS/MP and there will not be any file system call. After the 25 requests are serviced, subsequent requests on those 25 web dialogs are delivered to NSJSP through file system I/O operations. At this stage, all 25 links to the NSJSP instance are free to process more incoming requests delivered through TS/MP. Therefore, the NSJSP instance must be able to handle 25 more concurrent requests, all being the first requests of web dialogs.
PAGE 318

-Xnoclassgc Is an optional argument to stop the Java class garbage collection. Syntax: -Xnoclassgc By default, the Java runtime reclaims space for unused Java classes. Including this optional argument might prevent any memory-leak problems.
PAGE 319

com.tandem.sqlmx.SQLMXDriver ... ... ... ... NOTE: The significance of the tag is explained in Opening a Session for Database Operation section.
PAGE 320

Configuring SessionFactory in the hibernate.cfg.xml File Add the following lines in the hibernate.cfg.xml file to configure the Hibernate SessionFactory. ... ... ... ... ...
PAGE 321

Defining the Connection URL After you have specified the JDBC Type 2 driver, enter the location of the SQL/MX server. URLs referring to SQL/MX use the jdbc: protocol embedded within the URL. To define the connection URL, enter jdbc:sqlmx:// as the connection URL for the SQL/MX database in the hibernate.properties file as shown: hibernate.connection.url jdbc:sqlmx:// Establishing the Connection If you plan to use the JDBC Type 2 driver, do not specify the username and password.
PAGE 322

Configuration cfg = new Configuration() .addResource("Name of mapping file#1") .addResource("Name of mapping file#2"); For example, If the mapping file used in your application is Item.hbm.xml and Bid.hbm.xml, specify it as shown. Configuration cfg = new Configuration() .addResource("Item.hbm.xml") .addResource("Bid.hbm.xml"); The basic configuration is ready for you to perform database operation using Hibernate.
PAGE 323

NOTE: The significance of the tag is discussed in the Opening a Session for Database Operation section. Defining the Connection URL After you have specify the JDBC Type 4 driver, enter the location of the SQL/MX server. URLs referring to SQL/MX use the jdbc: protocol and have the server host, port number embedded within the URL. To define the connection URL, enter jdbc:t4sqlmx://:
PAGE 324

... ... ... ... ... NOTE: The above configuration uses the hibernate-configuration-3.0.dtd file. Creating a New Session from the SessionFactory in Java Add the following to create a new session from the SessionFactory: SessionFactory sessionFactory; Configuration cfg = new Configuration().configure(); sessionFactory = cfg.buildSessionFactory(); Session session = sessionFactory.
PAGE 325

Establishing the Connection To establish the connection, specify the username and password of your NonStop system in the hibernate.properties as shown. hibernate.connection.username hibernate.connection.password Defining the Hibernate Dialect for SQL/MX Database Enter org.hibernate.dialect.SqlmxDialect as the class name of a Hibernate dialect file in the hibernate.properties file as shown below. hibernate.dialect org.hibernate.dialect.
PAGE 326

Closing the Session Once the database operation is complete, close the session to deallocate the memory. Add the following line of code when you complete the database operation. session.close(); Database Transaction Management Hibernate works in any environment that uses JTA, in fact, we recommend to use JTA whenever possible as it is the standard Java transaction interface.
PAGE 327

tx.rollback(); Connection Pooling Connection Pooling is a cache of database connections maintained in the database memory so that the database connections can be reused when the database receives any future requests for data. In this case, whenever a database operation needs to be performed, a request for an existing database connection is made to a pool or any object that holds the existing database connections. Once that particular database operation is completed, the connection is returned to the pool.
PAGE 328

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 329

17 Getting Started with Hibernate This chapter explains how to develop an application using the Hibernate framework. It describes the steps required to build a basic employee management system (using Hibernate) on your Windows system and run 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 330

Developing EmployeeInfo on Windows using the Eclipse IDE NOTE: • This section describes the steps to develop the EmployeeInfo application using the Eclipse Integrated Development Environment (IDE). However, using the Eclipse IDE is not mandatory. You can choose any other IDE that supports Java. • The sample screen shots provided in this section are based on Eclipse IDE version 3.3.1.1. If you are using a different version of Eclipse, the screen shots might look different.
PAGE 331

Figure 17-2 Eclipse SDK Welcome Screen Close the welcome screen. The workspace is created. NOTE: You can find the source code for the EmplopyeeInfo application in the SAMPLES.zip file.
PAGE 332

Figure 17-3 New Project Dialog Box The New Java Project dialog box appears. 3. In the Project name field, enter EmployeeInfo. Ensure that the directory for this project is created inside the workspace that you have selected or created. NOTE: • In this application, EmployeeInfo is the name of the Java project. • The options in the JRE and Project layout sections are selected by default. Figure 17-4 shows the New Java Project dialog box.
PAGE 333

Figure 17-4 New Java Project Dialog Box 4. 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.5. If JRE version is not 1.5 or later, complete the following steps to select JRE 1.5 or later: 1. Click Configure default in the JRE dialog box. The Preferences screen appears. 2. Under the type filter text, select Java > Installed JREs. A list of JREs that are exposed to the Eclipse IDE is displayed as shown in JRE Options Dialog Box. 3.
PAGE 334

Figure 17-5 JRE Options Dialog Box 5. Click Finish in Figure 17-4 to create the Java project. The Java Project Structure, displaying the structure of the newly created EmployeeInfo Java project, is created. Figure 17-6 shows the Java Project Structure dialog box. Figure 17-6 Java Project Structure Dialog Box Adding Dependency JAR Files to the Project Library Add the following Hibernate dependency JAR files in the Java Build Path of the EmployeeInfo project to compile and link the project.
PAGE 335

Table 17-1 Hibernate Dependency JAR Files (continued) Dependency JAR Files Source Location cglib-2.1.3.jar \lib commons-collections-2.1.1.jar \lib commons-logging-1.0.4.jar \lib dom4j-1.6.1.jar \lib hibernate3.jar hibernate3sqlmx.jar \lib jta.jar \lib log4j-1.2.11.
PAGE 336

Figure 17-8 EmployeeInfo Project Structure Dialog Box Creating the Package for the EmployeeInfo Application To create the package for the EmployeeInfo application, complete the following steps: 1. On the Project Explorer frame, right-click EmployeeInfo and select New > Package. The New Java Package dialog box appears.
PAGE 337

2. In the Name field, enter com.hp.domain and click Finish. Figure 17-9 shows the New Java Package dialog box. Figure 17-9 New Java Package Dialog Box Creating the Class File To create the Employee.java class file, complete the following steps: 1. On the Project Explorer frame, right-click the com.hp.domain package and select New > Class. The New Java Class dialog box appears. 2. In the Name field, enter Employee and click Finish and ensure that the Source folder is EmployeeInfo/src.
PAGE 338

Figure 17-10 New Java Class Dialog Box The Class file is created. 3. 338 Modify the Employee.
PAGE 339

package com.hp.domain; public class Employee { private int id; private String fname; private String lname; private int age; public int getId() { return id; } public void setId(int id) { this.id = id; } public String getFname() { return fname; } public void setFname(String fname) { this.fname = fname; } public String getLname() { return lname; } public void setLname(String lname) { this.lname = lname; } public int getAge() { return age; } public void setAge(int age) { this.
PAGE 340

+ "\to_id=" + emp.getId()); } public void createEmp(TestManager manager) { manager.createEmpl(); } public static void main(String[] args) { Test client = new Test(); Session session = client.openSession(); TestManager manager = new TestManager(session); client.createEmp(manager); client.testFindByHQL(manager); session.close(); } } The Test.java main class file is created. Implementing the Business Logic The business logic for the EmpIoyeeInfo application is implemented in the TestManager.java class file.
PAGE 341

Employee emp = null; do { if (emps.hasNext()) { emp = (Employee) emps.next(); System.out.println("----------" + emp.getId()); System.out.println("----------" + emp.getFname()); } } while (emps.hasNext()); return (emp); } public void createEmpl() { try { tx = session.beginTransaction(); Employee emp = new Employee(); emp.setAge(23); emp.setFname("Test"); emp.setLname("Data"); session.save(emp); tx.commit(); } catch (HibernateException e) { if (tx != null) try { tx.
PAGE 342

Figure 17-11 EmployeeInfo Project Dialog Box Creating the Hibernate Mapping File The Hibernate mapping file (.hbm) maps the employee objects to their respective columns in the SQL/MX database tables. To create the Employee.hbm.xml file in the EmployeeInfo/src directory, complete the following steps: 1. On the Project Explorer frame, right-click EmployeeInfo and select New > Other. The New dialog box appears. 2. From the list of folders, select XML > XML and click Next.
PAGE 343

Figure 17-12 New Dialog Box The New XML File: Create XML dialog box appears. 3. In the File name field, enter Employee.hbm.xml and ensure that the parent folder is set to EmployeeInfo/src. Click Next. The New XML File: Create XML dialog box appears again. Figure 17-13 shows the New XML File dialog box.
PAGE 344

Figure 17-13 New XML File: Create XML Dialog Box 4. Select Create XML from an XML template and click Finish. The Employee.hbm.xml file is created in the EmployeeInfo/src directory. NOTE: By default, XML files open in the XML Editor. The XML Editor has two views: Design and Source view. Select the Source view. 5. Modify the Employee.hbm.xml file by adding a Hibernate mapping for the Employee.java class. After modification, the Employee.hbm.xml file appears as follows:
PAGE 345

NOTE: The generator class for tag is mentioned as increment. This is to use the auto-increment feature of Hibernate. Setting Hibernate Configurations To set up Hibernate configurations, create the following files: • • hibernate.cfg.xml hibernate.properties hibernate.cfg.xml Hibernate uses the hibernate.cfg.xml file to set up the environment. To create and modify hibernate.cfg.
PAGE 346

1. Create the hibernate.cfg.xml file in the EmployeeInfo/src directory, as explained in the Creating the Hibernate Mapping File section. 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. To modify the hibernate.cfg.xml file, complete the following steps: • Add reference for the Hibernate mapping file under tag. PAGE 347
Figure 17-14 New File Dialog Box Overview of EmpIoyeeInfo 347
PAGE 348

3. Modify the hibernate.properties file depending 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 hibernate.properties file must appear as: #---------------------------------------------------------------------------# SQL/MX Settings for JDBC Type 2 Driver hibernate.connection.driver_class=com.tandem.sqlmx.SQLMXDriver hibernate.connection.url=jdbc:sqlmx:// hibernate.connection.username= hibernate.connection.
PAGE 349

Figure 17-15 EmployeeInfo Project Structure Dialog Box Creating the EmployeeInfo Application JAR File To create the JAR file of the EmployeeInfo application, complete the following steps: 1. On the Project Explorer frame, right-click EmployeeInfo and select Export. The Export dialog box appears. 2. From the list of folders, select Java > JAR file. Figure 17-16 shows the Export dialog box.
PAGE 350

Figure 17-16 Export Dialog Box 3. Click Next. The JAR Export dialog box appears. Browse to the location where you want to save the JAR file on your Windows system. Figure 17-17 shows the JAR Export dialog box.
PAGE 351

Figure 17-17 The JAR Export Dialog Box 4. Click Finish. The EmployeeInfo application JAR file (EmployeeInfo.jar) is created. Setting Up NonStop Environment To set up NonStop environment, complete the following steps: 1. Create the SQL/MX database catalog and schema on your NonStop system with the same names as specified in the hibernate.properties file. The MXCI commands to create the database catalog and schema are as follows: mxci>> create catalog employeeinfocat LOCATION
PAGE 352

NOTE: To view the contents of the ei_setenv script, see the Hibernate Environment Setup Script section. 4. Edit the ei_setenv script as follows: 1. Set the value of the hibernatehome variable to the OSS directory. For example, if is /usr/tandem/sash/ hibernate-3.2.6, the hibernatehome variable must be set to hibernatehome=/ usr/tandem/sash/hibernate-3.2.6 2. Set the value of the JDBC/MX driver locations. a.
PAGE 353

3. Run the EmployeeInfo application by executing the command: OSS> java com.hp.imp.Test The following output appears: Hibernate: select max(id) from Emp Hibernate: insert into Emp (fname, lname, age, id) values (?, ?, ?, ?) 1237276999876 Hibernate: select employee0_.id as id0_, employee0_.fname as fname0_, employee0_ .lname as lname0_, employee0_.
PAGE 354
PAGE 355

G Customizing Sample Application Customizing Caveat Emptor To customize Caveat Emptor, one file was modified and five files were added. Modified File • Main.java Added Files • hibernate.properties • setenv • build_jdbct2.xml • build_jdbct4.xml • Caveatemptor_script.sql Modified File Main.java (\eg\org\hibernate\auction\Main.java) This is the class file that performs all database operations and is an entry point for the Caveat Emptor application. • Changes in the Main.
PAGE 356

This file provides hibernate configuration to Caveat Emptor. • The content of the hibernate.properties file is: ##-----------------------------------------------------------------------------# SQL/MX Settings for JDBC Type 2 Driver #hibernate.dialect org.hibernate.dialect.SqlmxDialect #hibernate.connection.driver_class com.tandem.sqlmx.SQLMXDriver #hibernate.connection.url jdbc:sqlmx:// #hibernate.connection.username #hibernate.connection.password #hibernate.connection.catalog auctioncat #hibernate.
PAGE 357

################################################################################ #CLASSPATHs for JDBC/MX Type 4 Drivers if [ $1 = T4 ]; then export CLASSPATH=$CLASSPATH:$t4jdbc/hibernate/samples/eg/t4sqlmx.
PAGE 358

build_jdbct4.
PAGE 359

Caveatemptor_script.sql (\hibernate\samples\eg\dbconfig\caveatemptor_script.sql) This is the script file used to create database catalog, schema, and database tables for Caveat Emptor application.
PAGE 360
PAGE 361

H JDBC Configuration This section describes the consolidated JDBC Type 2 driver configuration and the JDBC Type 4 driver configuration in hibernate.cfg.xml and hibernate.properties files. • JDBC Type 2 driver configurations The consolidated JDBC Type 2 driver configuration in hibernate.cfg.xml is as follows:
PAGE 362
PAGE 363

I Hibernate Environment Setup Script The ei_setenv script file is used for setting up the Hibernate CLASSPATH and JDBC environments. The content of the file is as follows: #!/bin/ksh hibernatehome=”” t4jdbc=”” t2jdbc=”” Usage="\n Usage: .
PAGE 364
PAGE 365

J Installing Hibernate Annotations Libraries on NonStop Installing Hibernate Annotations framework libraries on a NonStop system requires the following actions: • Downloading Hibernate Distribution on Windows • Copying Hibernate Distribution from Windows to NonStop Downloading Hibernate Distribution on Windows To download the Hibernate Annotations distribution on your Windows system, complete the following steps: 1. Go to http://hibernate.org/6.html. 2.
PAGE 366

This completes the installation of the Hibernate Annotations framework libraries on your NonStop system. You can use these libraries when developing and running Hibernate applications using Hibernate Annotations on a NonStop system, using the steps similar to those for the Hibernate framework.
PAGE 367

K Installing Hibernate EntityManager Libraries on NonStop Installing the Hibernate EntityManager framework libraries on a NonStop system requires the following: • Downloading Hibernate Distribution on Windows • Copying Hibernate Distribution from Windows to NonStop Downloading Hibernate Distribution on Windows To download the Hibernate EntityManager distribution on your Windows system, complete the following steps: 1. Go to http://hibernate.org/6.html. 2.
PAGE 368

OSS> cd OSS> jar –xvf hibernate-entitymanager_lib.jar This completes the installation of Hibernate EntityManager framework libraries on your NonStop system. You can use these libraries when developing and running Hibernate applications using Hibernate EntityManager on a NonStop system, using the steps similar to those for Hibernate framework.
PAGE 369

Part V Integrating Frameworks Part V helps you to use the Spring Transaction Manager and integrate Spring with Hibernate, Axis2/Java, and MyFaces. It includes the following chapters: • Chapter 18: Using Spring Transaction Manager This chapter helps you to use the Spring Transaction Manager. • Chapter 19: Integrating Hibernate into Spring This chapter helps you to integrate Hibernate with the Spring framework.
PAGE 370
PAGE 371

18 Using Spring Transaction Manager This section 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 chapter) using the Eclipse IDE.
PAGE 372

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 chapter) developed on your Windows system.
PAGE 373

Figure 18-1 Project Explorer View Modifying the EmpInfo application involves the following tasks: 1. Modifying EmpInfo based on the Type of Transaction • For Declarative Transaction — Creating IEmployeeDao.java — Modifying EmployeeController.java File — Modifying applicationContext.xml File • 2. For Programmatic Transaction — Modifying applicationContext.xml File — Modify the EmployeeController.
PAGE 374

For Declarative Transaction The following activities are involved in the declarative transactions. Creating IEmployeeDao.java 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.
PAGE 375

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)throws SQLException; Modifying 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.
PAGE 376

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

4. AOP Proxy Factory Bean: It creates an AOP proxy factory bean that contains the business interface and the implementation class as the target. com.hp.empinfo.service.IEmployeeDao 5.
PAGE 378

${jdbc.driver} ${jdbc.url} ${jdbc.user} ${jdbc.password} ${jdbc.catalog} ${jdbc.
PAGE 379

Modify the EmployeeController.java File This file is modified to use the PlatformTransactionManager implementation as follows: 1.
PAGE 380

String rord = ((Employee) command).getRord(); if (rord != null && rord.equalsIgnoreCase("Retrieve")) { DefaultTransactionDefinition def = new DefaultTransactionDefinition(); def .setPropagationBehavior(TransactionDefinition.PROPAGATION_REQUIRED); TransactionStatus status = txManager.getTransaction(def); Employee emp1; try { emp1 = empdao.getDetail(empid); } catch (Exception e) { // TODO: handle exception txManager.rollback(status); throw e; } txManager.
PAGE 381

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 library path: Table 18-1 Dependency JAR Files Dependency JAR Files Source Location aspectjweaver.jar \lib\aspectj cglib-nodep-2.1_3.
PAGE 382

Figure 18-4 Project Explorer View: Programmatic Transaction Deploying EmpInfo on NonStop This section describes the following tasks: 1. 2. Creating the Application WAR File on Windows Deploying the EmpInfo WAR File in NSJSP on NonStop 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.
PAGE 383

Figure 18-5 Export Dialog Box The WAR Export dialog box appears. 3. In the Web module field, enter EmpInfo and browse to the destination where you want to save the WAR file. Figure 18-6 shows the WAR Export dialog box.
PAGE 384

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. Go to http://:/servlet_jsp /manager/html.
PAGE 385

Figure 18-8 NSJSP Web Application Manager Screen 3. 4. In the WAR file to deploy section, click Browse and locate the EmpInfo.war file on your Windows system. Click Deploy. EmpInfo gets listed under Applications. NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can deploy EmpInfo on your NonStop system by completing the following steps: 1. Ensure that you have WRITE permissions to the webapps directory in your .
PAGE 386

NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can run EmpInfo on your NonStop system by completing the following steps: 1. Go to the /conf directory using the command: OSS> cd /conf For example: OSS> cd /home/sash_usr/webserver/conf 2. Start your iTP WebServer using the command: OSS> ./start 3.
PAGE 387

19 Integrating Hibernate into Spring This section 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 chapter) using the Eclipse IDE.
PAGE 388

• Following software installed on your NonStop system: — NonStop iTP WebServer — NonStop Servlets for Java Server Pages (NSJSP) — JDBC Type 2 Driver for NonStop SQL/MX — NonStop SQL/MX — NonStop Server for Java (NSJ) • Following software installed on your Windows system: — Java Development Kit (JDK) — JDBC Type 4 Driver for NonStop SQL/MX — Eclipse IDE Activities involved Integrating the EmpInfo application with Hibernate involves the following tasks: • • • Modifying EmpInfo on Windows using Eclipse ID
PAGE 389

Figure 19-1 Project Explorer View Modifying the EmpInfo application involves the following tasks: • Modifying the applicationContext.xml File • Modifying the EmployeeDao.java File • Creating the Employee.hbm.xml File • Removing the EmployeeRowMapper.java File • Adding Dependency JAR Files Modifying the applicationContext.xml File Modify the EmpInfo/WebContent/WEB-INF/applicationContext.
PAGE 390

Example of Integrating Hibernate into Spring 9 true 2. Modify the bean instance of the EmployeeDao class to add the reference of the Hibernate SessionFactory, as shown: After modification, the applicationContext.
PAGE 391

Modifying the EmployeeDao.java File Modify the EmployeeDao.java file (under the com.hp.empinfo.service package), to change the JDBC queries to Hibernate queries for the insert, delete, and retrieve operations, using the following steps: 1. Instantiate the Hibernate SessionFactory as shown: private SessionFactory sessionFactory; public void setSessionFactory(SessionFactory sessionFactory) { this.sessionFactory = sessionFactory; } 2.
PAGE 392

Session session = sessionFactory.openSession(); Employee employee = new Employee(); employee.setEmpid(empid); session.delete(employee); session.flush(); return "Employee deleted"; Creating the Employee.hbm.xml File Create the Employee.hbm.xml (Hibernate Mapping) file in EmpInfo/src directory to map Java class with the database entities. To create the Employee.hbm.xml file in the EmpInfo/src directory, complete the following steps: 1.
PAGE 393

Figure 19-3 New XML File Dialog Box The New XML File: Create XML dialog box appears. 4. Select Create XML file from an XML template and click Finish Figure 19-4 shows the New XML File: Create XML dialog box. Figure 19-4 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.
PAGE 394

PAGE 395
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 chapter. The EmpInfo application is now modified to integrate Hibernate into a Spring application (EmpInfo) to handle database operations. Figure 19-5 shows the EmpInfo: Project Explorer View.
PAGE 396

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 19-6 shows the Export dialog box.
PAGE 397

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

Figure 19-8 NSJSP Web Application Manager Login Screen 2. Enter the User name and Password and click OK. The NSJSP Web Application Manager screen appears.
PAGE 399

3. 4. In the WAR file to deploy section, click Browse and locate the EmpInfo.war file on your Windows system. Click Deploy. EmpInfo gets listed under Applications. NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can deploy EmpInfo on your NonStop system by completing the following steps: 1. Ensure that you have WRITE permissions to the webapps directory in your .
PAGE 400
PAGE 401

20 Integrating JPA with Hibernate into Spring This section 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 chapter) using the Eclipse IDE.
PAGE 402

Activities involved Integrating the EmpInfo spring application with JPA and Hibernate, involves the following tasks: • • • Modifying EmpInfo on Windows using Eclipse IDE Deploying EmpInfo on NonStop Running EmpInfo on NonStop Modifying EmpInfo on Windows using Eclipse IDE The EmpInfo application developed in the Integrating Hibernate into Spring chapter is the starting point to demonstrate the integration of JPA with Hibernate in Spring.
PAGE 403

Modifying the EmpInfo application involves the following activities: 1. 2. 3. 4. 5. 6. Creating the persistence.xml File Creating the EntityEmployee.java File Modifying the applicationContext.xml File Modifying the EmployeeDao.java File Removing the Employee.hbm.xml File Adding Dependency JAR Files 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 404

import javax.persistence.Id; 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 405

this.email = email; } } 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 406
${jdbc.schema} PAGE 407
public class EmployeeDao { private EntityManagerFactory entityManagerFactory; public void setEntityManagerFactory( EntityManagerFactory entityManagerFactory) { this.entityManagerFactory = entityManagerFactory; } public Employee getDetail(int empid) throws SQLException { EntityManager em = entityManagerFactory.createEntityManager(); EntityTransaction t = em.getTransaction(); t.begin(); List l = em.createQuery( "from EntityEmployee where emp_id=" + empid).
PAGE 408

Adding Dependency JAR Files Adding the dependency JAR files involves the following tasks: 1. 2. Downloading Hibernate Entity Manager Adding Dependency JAR Files Downloading Hibernate Entity Manager To use JPA with Hibernate, the javassist.jar and ejb3-persistence.jar dependency JAR files present in the Hibernate Entity Manager package must be downloaded. To download the Hibernate Entity Manger, complete the following steps: 1. Go to http://sourceforge.net/project/showfiles.
PAGE 409

Figure 20-2 Project Explorer View Deploying EmpInfo on NonStop This section describes the following tasks: 1. 2. Creating the EmpInfo WAR File on Windows Deploying the EmpInfo WAR File in NSJSP on NonStop 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 410

2. From the list of folders, select Web > WAR file and click Next. Figure 20-3 shows the Export dialog box. Figure 20-3 Export Dialog Box The WAR Export dialog box appears. 3. In the Web module field, enter EmpInfo and browse to the destination where you want to save the WAR file. Figure 20-4 shows the WAR Export dialog box.
PAGE 411

Figure 20-4 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 412

Figure 20-5 NSJSP Web Application Manager Login screen 2. Enter the User name and Password and click OK. The NSJSP Web Application Manager screen appears.
PAGE 413

3. 4. In the WAR file to deploy section, click Browse and locate the EmpInfo.war file on your Windows system. Click Deploy. EmpInfo gets listed under Applications. NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can deploy EmpInfo on your NonStop system by completing the following steps: 1. Ensure that you have WRITE permissions to the webapps directory in your .
PAGE 414
PAGE 415

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 IDE.
PAGE 416

Activities involved Integrating the EmpInfo application with Axis2/Java, involves the following activities: • • • • • Modifying EmpInfo on Windows using Eclipse 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 IDE The EmpInfo application, developed in the Getting Started with Spring chapter, is the starting point to demonstrate the integration of Axis2/Java with Spring appl
PAGE 417

1. 2. 3. 4. 5. Creating the SpringInit.java File Creating the services.xml File Modifying the applicationContext.xml File 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.
PAGE 418

} } 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. 2. 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. Modify the services.xml file to include the instances SpringInit and EmpInfo services.
PAGE 419

${jdbc.driver} ${jdbc.url} ${jdbc.username} ${jdbc.password} ${jdbc.catalog} ${jdbc.
PAGE 420

PAGE 421
Figure 21-2 Project Explorer View Deploying EmpInfo on NonStop This section describes the following tasks: 1. 2. Creating the EmpInfo AAR File on Windows 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 21-3 shows the Project Explorer Frame.
PAGE 422

Figure 21-3 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 21-4 shows the Console dialog box.
PAGE 423

Figure 21-4 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. Make sure you have the Axis2/Java web application deployed in NSJSP. NOTE: For information on deploying the Axis2/Java web application in NSJSP, see the Installing Axis2/Java Framework chapter. 2.
PAGE 424

3. 4. After verifying the permissions, copy spring.jar from /dist to /webapps/axis2/WEB-INF/lib directory on OSS. Copy t4sqlmx.jar from on your Windows directory to /webapps/axis2/WEB-INF/lib directory on OSS. NOTE: 5. This step is required only if you plan to use JDBC Type 4 driver. Copy EmpInfoService.aar to /webapps/axis2/ WEB-INF/services directory on OSS.
PAGE 425

Figure 21-5 List Services Dialog Box Developing EmpInfoClient on Windows To invoke the EmpInfo web service on your NonStop system, you need to create Axis2/Java client on your Windows system. The APIs of the client are used to invoke the service. To create an Axis2/Java client for EmpInfo web service, we will be using Eclipse IDE. Developing the Axis2/Java client (EmpInfoClient) for EmpInfo web service involves the following steps: 1. 2. 3. 4. 5.
PAGE 426

Figure 21-6 New Project Dialog Box The New Java Project dialog box appears. 3. In the Project name field, enter EmpInfoClient (or specify the name of the project that you wish to create) and ensure that the directory for this project is created inside the workspace that you have selected or created. Figure 21-7 shows the New Java Project dialog box.
PAGE 427

Figure 21-7 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.5 version is used to create the client project.
PAGE 428

Figure 21-8 JRE Options: Preferences Dialog Box d. Click Finish in Figure 21-7 to create the Java project. Figure 21-9 shows the Java: Project Explorer View.
PAGE 429

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.client and ensure that the Source folder is set to EmpInfoClient/src and click Finish. Figure 21-10 shows the New Java Package dialog box Figure 21-10 New Java Package Dialog Box The package for client project is created. Creating the EmpInfoClient.java File To create the EmpInfoClient.
PAGE 430

Figure 21-11 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 431

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 432

NOTE: Remember to replace with the IP address and of the iTP WebServer with the port number of the iTP WebServer under which your EmpInfo webserver is running. 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: • • • • • • • • • • • • • • • • • • • activation-1.1.jar annogen-0.1.0.jar axiom-api-1.2.7.jar axiom-impl-1.2.
PAGE 433

Figure 21-12 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 21-13 shows the Java Eclipse Platform.
PAGE 434

Figure 21-13 Java Eclipse Platform The Console is displayed. 2. Press 1 to insert Employee. Specify the employee details as prompted. Figure 21-14 shows the Console: Insert Employee.
PAGE 435

Figure 21-14 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 21-15 shows the Console: Employee Details.
PAGE 436

Figure 21-15 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 21-16 shows the Console: Delete Employee.
PAGE 437

Figure 21-16 Console: Delete Employee Example of Integrating Axis2/Java with Spring 437
PAGE 438
PAGE 439

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 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 440

Modifying EmpInfo on Windows using Eclipse 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 22-1 shows the Project Explorer View. Figure 22-1 Project Explorer View Modifying the EmpInfo application involves the following tasks: 1. 2. 3. 4.
PAGE 441

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 442

5. Set the filter mapping as shown below: extensionsFilter *.jsf extensionsFilter /faces/* After modification, the web.xml file appears as: PAGE 443
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 444

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 445

} 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. 2. Create the ServiceFinder.java file under the com.hp.empinfo.
PAGE 446

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 447

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 448

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 449

To create the MessageFactory.java file in the com.hp.empinfo.web package, complete the following steps: 1. 2. 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. 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 450

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 451

PAGE 452
PAGE 453

PAGE 454
PAGE 455

<%@ taglib uri="http://myfaces.apache.org/tomahawk" prefix="t"%> Detail PAGE 456

PAGE 457

Creating the mycss.
PAGE 458

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 459

Creating the faces-config.xml File This file contains configuration details for the MyFaces implementation. To create the faces-config.xml file, complete the following steps 1. 2. Create the faces-config.xml file in the EmpInfo/WebContent/WEB-INF directory as explained in the Creating the EmpInfo-servlet.xml File section in the Getting Started with Spring chapter. Modify the faces-config.xml file to include information about message bundle, backing bean, and navigation rules.
PAGE 460

/pages/empUpdate.jsp Retrieve /pages/empDetail.jsp Delete /pages/empUpdate.jsp Incorrect /pages/empUpdate.
PAGE 461

NOTE: If you have already downloaded and installed these JAR files, you need not download them again. Download and extract the zip files of the above-mentioned JAR files to a location on your Windows system. Assume this location to be .
PAGE 462

Figure 22-4 Project Explorer View Deploying EmpInfo on NonStop This section describes the following tasks: 1. 2. Creating the EmpInfo WAR File on Windows Deploying the EmpInfo WAR File in NSJSP on NonStop 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 463

Figure 22-5 Export Dialog Box The WAR Export dialog box appears. 3. In the Web module field, enter EmpInfo and browse to the destination where you want to save the WAR file. Figure 22-6 shows the WAR Export dialog box.
PAGE 464

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. Go to http://:/servlet_jsp /manager/html.
PAGE 465

Figure 22-8 NSJSP Web Application Manager Screen 3. 4. In the WAR file to deploy section, click Browse and locate the EmpInfo.war file on your Windows system. Click Deploy. EmpInfo gets listed under Applications. NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can deploy EmpInfo on your NonStop system by completing the following steps: 1. Ensure that you have WRITE permissions to the webapps directory in your .
PAGE 466

NOTE: If you do not have access to the NSJSP Web Application Manager screen, you can run EmpInfo on your NonStop system by completing the following steps: 1. Go to the /conf directory using the command: OSS> cd /conf For example: OSS> cd /home/sash_usr/webserver/conf 2. Start your iTP WebServer using the command: OSS> ./start 3.
PAGE 467

Figure 22-10 Insert Employee Details Screen 2. Enter the required Employee details and click Submit. Figure 22-11 shows an example of valid employee details.
PAGE 468

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

Figure 22-13 Message Screen If you enter invalid field values, the corresponding error messages appear on the Insert Employee Details screen. Figure 22-14 shows the Error Message screen.
PAGE 470

Figure 22-14 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 22-15 shows the Record Update screen appears.
PAGE 471

Figure 22-15 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 22-16 shows the Employee Information screen.
PAGE 472

Figure 22-16 Employee Information Screen If you enter a non-existing Employee ID, the Record Update screen appears with the message Employee does not exist. Figure 22-17 shows the Record Update: Message Screen.
PAGE 473

If you enter invalid field values, the corresponding error messages appears on the Record Update screen. Figure 22-18 shows the Record Update: Error Message screen.
PAGE 474

Figure 22-18 Record Update: Error Message Screen 3.
PAGE 475

• 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 22-19 shows the Record Update: Delete Employee screen. Figure 22-19 Record Update: Delete Employee Screen The Employee ID is deleted.
PAGE 476
PAGE 477

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 478

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 479

Your application uses classes which are defined in one or more JAR files. This error appears when any of these dependency JAR files is not added into the CLASSPATH.
PAGE 480
PAGE 481

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 482

I Inversion of Control Inversion of control, or IoC, is an abstract principle describing an aspect of some software architecture designs in which the flow of control of a system is inverted in comparison to procedural programming. 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.
PAGE 483

(SPRs) as well as to request Site Update Tapes (SUTs) and Independent Product (IP) CDs for your systems. In 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 your systems. SessionBasedLoadBalancing A feature of NSJSP by virtue of which NSJSP Container maintains sessions for load balancing purposes.
PAGE 484
PAGE 485

Index Symbols $datavol, 50 $RECEIVE, 66, 190, 240, 308 -DSaveSessionOnCreation, 70, 194, 244, 312 -DSessionBasedLoadBalancing, 71, 194, 244, 313 -Xmx, 75, 199, 249, 317 -Xmx maximum-stack-size, 75, 199, 249, 317 -Xnoclassgc, 76, 199, 249, 318 -Xss, 75, 199, 249, 317 /etc, 149 /insert.
PAGE 486

Configuring NSJSP for Axis2/Java, 194 Determining Application Parameters, 189 Determining Maximum Capacity of NSJSP Instance, 189 Installing Axis2/Java, 179 Building, 180 Deploying, 181 Downloading, 179 Running, 182 TemperatureConverter, 201 Axis2/Java Architecture, 173 AxisClient, 207 AxisClient/src, 210 B BankService, 184 BankService.aar, 185 Bean Instance, 377 Bid.hbm.xml, 322 blobTableName, 62 build.xml, 152, 419 build_jdbct2.xml, 150, 156, 160, 301, 357 Changes to build_jdbct2.
PAGE 487

empinfocat, 124 EmpInfoClient, 425 EmpInfoClient.java, 429 empinfosch, 124 EmpInfoService.aar, 421, 423 Employee.hbm.xml, 319, 342, 392, 407 Employee.java, 118, 338 EmployeeController, 107 EmployeeController.java, 108, 373, 375 EmployeeDao, 390 EmployeeDao class, 122 EmployeeDao.
PAGE 488

iTP WebServer, 40, 175, 292 J Java Data Objects (JDO), 387, 401 Java Development Kit (JDK), 31 Java Enterprise Edition (JEE), 39 Java Persistence API (JPA), 401 Java Runtime Arguments, 75, 199, 249, 317 JavaServer Faces (JSF), 223 javassist.jar, 408 javax.faces.webapp.FacesServlet, 441 javax.transaction, 326 JDBC Configuration, 167 JDBC Type 2 Driver, 318 JDBC Type 2 Driver Class, 76 JDBC Type 2 Driver for NonStop SQL/MX, 29 JDBC Type 4 Driver, 78, 322 JDBC Type 4 Driver for NonStop SQL/MX, 33 jdbc.
PAGE 489

New Package, 270 coreservlets, 270 node.$vol, 50 NonStop iTP WebServer, 26 NonStop Platform, 65, 189, 239, 307 NonStop Server for Java (NSJ), 30 NonStop Servlets for Java Server Pages (NSJSP), 28 NonStop Servlets for JavaServer Pages (NSJSP), 40, 176, 292 NonStop SQL/MX, 30 NonStop system, 26, 45, 89, 179, 201, 229, 251, 297 Numstatic, 65, 67, 189, 191, 239, 241, 307, 309 O OMElement, 212 onSubmit, 125 Order.xml, 160 Changes to Order.xml, 160 org.apache.catalina.core.
PAGE 490

Configuring Configuring iTP WebServer for Spring, 66 Configuring NSJSP for Spring, 70 Determining Application Parameters, 65 Determining Maximum Capacity of NSJSP Instance, 65 Installing Spring, 45 Copying, 46 Downloading, 45 Spring Beans, 387 Spring Core, 38 Spring Framework Architecture, 37 Spring Getting Started, 89 Spring JDBC API, 89 Spring Transaction Management, 371 Declarative Transaction Management, 371 Programmatic Transaction Management, 371 Spring Transaction Manager, 371 Spring-MVC framework, 8
PAGE 491

Windows system, 31, 45, 89, 179, 201, 229, 251, 297, 329 WSDL, 184, 415 X XML namespace, 377 XML Parser, 174 491
PAGE 492

Employee Id :
First Name :
Last Name :
Age :
Employee Email Id :