TEMPLATE DESIGN © 2008
www.PosterPresentations.com
JAVA SERVER FACES (JSF) Upgrade from
Version 1.1 to 2.0 for two Major Apps
Implemented by Vishwanarayan Sriganesh
under the Guidance of John C Richard
Research
• Java Server Faces version and usage with J2EE
application information
• Compatibility check for JSF with WebSphere
Application Server 8.5
• Agile Methodology and Environment – Sprints,
Work items, Story Points, Retrospective and other
Agile Terminologies
• Pros and Cons for using JSF 2.0 and JSF 2.2 with
WAS 8.5
• Application and Application Libraries compatibility
and usage with JSF 2.0
• Rational Software Architect (RSA) and Rational
Team Concert (RTC) coexistence
• Configuration and Setup of Development
Environment with WebSphere Application Server
for Developers integrated with RSA
Procedure
Problems
Compatibility issues for two of the major applications
(MFCTableManagement and NewCCOVSearch)post
upgrade of WebSphere Application Server from
version 7.0 to 8.5
•Full Page Refresh on page action
•Drop down loads and refresh for fields
•JIBX compilation with new JAVA Version (8.0)
•No progress intimation to user regarding loading on
search
•Usage of IBM extended Libraries for the Front end
styles(Not supported for JSF 2.0)
Hypothesis
JAVA Server Faces (JSF) version 2.0 is assumed to be the latest
version that is compatible with the WebSphere Application
Server version 8.5
Conclusion
Both the Major two applications
(MFCTableManagement and NewCCOVSearch) have
been updated for the Java Server Faces from version
1.1 to 2.0 in order to have their web pages user friendly
and compatible with the existing current WebSphere
Application Server which is version 8.5
Data
• JAR files required for the upload functionality on the
install page for MFCTableManagement application
• Plugin files required for the Development
Environment setup for the Rational Software
Architect and Rational Team Concert
• JIBX Binding files (JAR files) required as part of
MFCTablemanagement application development
• Information regarding JSF compatibility with
WebSphere Application Server 8.5
• JSP version of the application and server files were
required for performing a diff with the new updated
ones
Software and Tools used
• FileZilla
• Putty
• Winscp
• Rational Software Architect
• Rational Team Concert
• Snipping Tool
• Microsoft Word
• Beyond Compare
• Notepad++
• WebSphere Application Server
References and Sources
Observation
Contact information
* Several sources and websites have come handy
and useful throughout the implementation of this
project. Few of the important ones are highlighted
below.
•www.stackoverflow.com
•www.oracle.com
•https://www.ibm.com/developerworks/community
•www.w3schools.com
•www.quirksmode.org
•http://www.javaserverfaces.org/
* Also, my Team Lead John C Richard was very much
helpful in guiding and assisting me with the project
research and implementation processes
• Component refresh instead of full page refresh for
the web pages
• Drop Down refresh and updates as per the user
click actions
• Additional feature of loading spinning wheel image
and information added to show the progress on
user action like search
• Replacing the additional IBM extended
components by the JSF specific library files
• ANT Build Compilation for JIBX was successful
post reference to older JAVA Version (7.0)
Vishwanarayan Sriganesh (Software Developer
Intern)
Manufacturing Configuration Tools Services –
Supply Chain Domain
Email: vsrigan@us.ibm.com/svishwa91@gmail.com
Phone: +19803493852
• Development Environment setup for the
MFCTableManagement and NewCCOVSearch applications for
working on with the JSF upgrade
• Configuration and set up of WebSphere Application Server to
the Rational Software Architect and documenting the reference
steps
• Getting to know the compatibility of JSF version with the
existing WebSphere Application Server 8.5
• Downloading necessary JAR files and additional libraries that
are required to support some of the features like upload and
install and to avoid IBM’s extension libraries on the web pages
• Conversion of the front end web pages from a .jsp to a .faces
format(XHTML) files
• Conversion of the Deployment descriptors version for the war
portion from 2.4 to 3.0 and ear portion of the application from
1.6 to 6.0
• Update to the faces-config.xml and the JAVA class files as
required to bring the application working to the newest format
• Making changes to the application’s properties file as required
• Removal of IBM extensions for the JSF
• Running and debugging the application on the Development
environment to verify that all the changes looks good
• Performing a diff with the existing project and system files to
ensure that we didn’t miss any of the changes or contents
required for the applications and reverting the changes for the
properties file
• Cleaning the project, compiling and running an ANT build for
the project for generating a new ear file for the project
• Taking back up of the existing ear file for the application via
the admin console for the DEV system
• Update the application with the new ear via the admin console
for the changes to take effect
• Restart the application and the server for the changes to take
place and pushing the applications to the other environments
accordingly post validation
• Getting User Acceptance Testing Performed on the apps post
deployment
Definition and Purpose
• JavaServer™ Faces (JSF) is the standard component-oriented
user interface (UI) framework for the Java EE platform. It is also
referred to as a Java based Web Framework
• JSF is included in the Java EE platform, so you can create
applications that use JSF without adding any extra libraries in
your project
• JSF is often used together with Ajax, a Rich Internet application
technology. Ajax is a combination of technologies that make it
possible to create rich user interfaces
• JSF is a component based MVC framework which is built on
top of the Servlet API, and provides components via taglibs
which can be used in Java based view technologies such as
JSP’s and Face lets
• RSA works well with JSF that helps users to use the built in
palettes and other components as drag and drop on the user
interface with built in Code and Graphical layouts rather than
manual coding

Showcase_Intern

  • 1.
    TEMPLATE DESIGN ©2008 www.PosterPresentations.com JAVA SERVER FACES (JSF) Upgrade from Version 1.1 to 2.0 for two Major Apps Implemented by Vishwanarayan Sriganesh under the Guidance of John C Richard Research • Java Server Faces version and usage with J2EE application information • Compatibility check for JSF with WebSphere Application Server 8.5 • Agile Methodology and Environment – Sprints, Work items, Story Points, Retrospective and other Agile Terminologies • Pros and Cons for using JSF 2.0 and JSF 2.2 with WAS 8.5 • Application and Application Libraries compatibility and usage with JSF 2.0 • Rational Software Architect (RSA) and Rational Team Concert (RTC) coexistence • Configuration and Setup of Development Environment with WebSphere Application Server for Developers integrated with RSA Procedure Problems Compatibility issues for two of the major applications (MFCTableManagement and NewCCOVSearch)post upgrade of WebSphere Application Server from version 7.0 to 8.5 •Full Page Refresh on page action •Drop down loads and refresh for fields •JIBX compilation with new JAVA Version (8.0) •No progress intimation to user regarding loading on search •Usage of IBM extended Libraries for the Front end styles(Not supported for JSF 2.0) Hypothesis JAVA Server Faces (JSF) version 2.0 is assumed to be the latest version that is compatible with the WebSphere Application Server version 8.5 Conclusion Both the Major two applications (MFCTableManagement and NewCCOVSearch) have been updated for the Java Server Faces from version 1.1 to 2.0 in order to have their web pages user friendly and compatible with the existing current WebSphere Application Server which is version 8.5 Data • JAR files required for the upload functionality on the install page for MFCTableManagement application • Plugin files required for the Development Environment setup for the Rational Software Architect and Rational Team Concert • JIBX Binding files (JAR files) required as part of MFCTablemanagement application development • Information regarding JSF compatibility with WebSphere Application Server 8.5 • JSP version of the application and server files were required for performing a diff with the new updated ones Software and Tools used • FileZilla • Putty • Winscp • Rational Software Architect • Rational Team Concert • Snipping Tool • Microsoft Word • Beyond Compare • Notepad++ • WebSphere Application Server References and Sources Observation Contact information * Several sources and websites have come handy and useful throughout the implementation of this project. Few of the important ones are highlighted below. •www.stackoverflow.com •www.oracle.com •https://www.ibm.com/developerworks/community •www.w3schools.com •www.quirksmode.org •http://www.javaserverfaces.org/ * Also, my Team Lead John C Richard was very much helpful in guiding and assisting me with the project research and implementation processes • Component refresh instead of full page refresh for the web pages • Drop Down refresh and updates as per the user click actions • Additional feature of loading spinning wheel image and information added to show the progress on user action like search • Replacing the additional IBM extended components by the JSF specific library files • ANT Build Compilation for JIBX was successful post reference to older JAVA Version (7.0) Vishwanarayan Sriganesh (Software Developer Intern) Manufacturing Configuration Tools Services – Supply Chain Domain Email: vsrigan@us.ibm.com/svishwa91@gmail.com Phone: +19803493852 • Development Environment setup for the MFCTableManagement and NewCCOVSearch applications for working on with the JSF upgrade • Configuration and set up of WebSphere Application Server to the Rational Software Architect and documenting the reference steps • Getting to know the compatibility of JSF version with the existing WebSphere Application Server 8.5 • Downloading necessary JAR files and additional libraries that are required to support some of the features like upload and install and to avoid IBM’s extension libraries on the web pages • Conversion of the front end web pages from a .jsp to a .faces format(XHTML) files • Conversion of the Deployment descriptors version for the war portion from 2.4 to 3.0 and ear portion of the application from 1.6 to 6.0 • Update to the faces-config.xml and the JAVA class files as required to bring the application working to the newest format • Making changes to the application’s properties file as required • Removal of IBM extensions for the JSF • Running and debugging the application on the Development environment to verify that all the changes looks good • Performing a diff with the existing project and system files to ensure that we didn’t miss any of the changes or contents required for the applications and reverting the changes for the properties file • Cleaning the project, compiling and running an ANT build for the project for generating a new ear file for the project • Taking back up of the existing ear file for the application via the admin console for the DEV system • Update the application with the new ear via the admin console for the changes to take effect • Restart the application and the server for the changes to take place and pushing the applications to the other environments accordingly post validation • Getting User Acceptance Testing Performed on the apps post deployment Definition and Purpose • JavaServer™ Faces (JSF) is the standard component-oriented user interface (UI) framework for the Java EE platform. It is also referred to as a Java based Web Framework • JSF is included in the Java EE platform, so you can create applications that use JSF without adding any extra libraries in your project • JSF is often used together with Ajax, a Rich Internet application technology. Ajax is a combination of technologies that make it possible to create rich user interfaces • JSF is a component based MVC framework which is built on top of the Servlet API, and provides components via taglibs which can be used in Java based view technologies such as JSP’s and Face lets • RSA works well with JSF that helps users to use the built in palettes and other components as drag and drop on the user interface with built in Code and Graphical layouts rather than manual coding