430 likes | 755 Views
Wondering about WebFacing?. September 2 2009 Host Access Transformation Services (HATS) Team. Agenda. IBM WebFacing Tool. AS/400- iSeries Only Solution Bundled with IBM WebSphere Development Studio Client (WDSc)
E N D
Wondering about WebFacing? September 2 2009 Host Access Transformation Services (HATS) Team
IBM WebFacing Tool • AS/400- iSeries Only Solution • Bundled with IBM WebSphere Development Studio Client (WDSc) • No Additional Deployment Cost - ran on AS/400-iSeries Internal Application Server • Ran on cheaper AS/400 Batch models IBM WebSphere HATS • Addressed both 3270 and 5250 re-facing requirements • Required IBM WebSphere Application Server (WAS) for Deployment • Required more expensive AS/400-iSeries Interactive hardware Before 2006 Introduction: A Little History
IBM WebFacing Tool • AS/400- iSeries Only Solution • Bundled with IBM WebSphere Development Studio Client (WDSc) • No Additional Deployment Cost - ran on AS/400-iSeries Internal Application Server • Ran on cheaper AS/400 Batch models IBM WebFacing Tool with HATS Technology (WDHT) V6.0.1 • Lower Tier Pricing for eServer iSeries • "Out-of-the-box" integration of WebFaced and non-WebFaced applications in a browser • Eliminated expensive HATS Interactive charge (Workload) IBM WebSphere HATS • Addressed both 3270 and 5250 re-facing requirements • Required IBM WebSphere Application Server (WAS) for Deployment • Required more expensive AS/400-iSeries Interactive hardware Jan 2006 Before 2006 Introduction: A Little History
IBM WebFacing Tool • AS/400- iSeries Only Solution • Bundled with IBM WebSphere Development Studio Client (WDSc) • No Additional Deployment Cost - ran on AS/400-iSeries Internal Application Server • Ran on cheaper AS/400 Batch models IBM WebFacing Tool with HATS Technology (WDHT) V6.0.1 IBM WDHT v7.0 • IBM WebFacing and HATS projects can be deployed as one project (ear file). • Rich Client Platform support introduced. • Lower Tier Pricing for eServer iSeries • "Out-of-the-box" integration of WebFaced and non-WebFaced applications in a browser • Eliminated expensive HATS Interactive charge (Workload) IBM WebSphere HATS • Addressed both 3270 and 5250 re-facing requirements • Required IBM WebSphere Application Server (WAS) for Deployment • Required more expensive AS/400-iSeries Interactive hardware Jan 2006 Feb 2007 Before 2006 Introduction: A Little History
IBM WebFacing Tool • AS/400- iSeries Only Solution • Bundled with IBM WebSphere Development Studio Client (WDSc) • No Additional Deployment Cost - ran on AS/400-iSeries Internal Application Server • Ran on cheaper AS/400 Batch models IBM WebFacing Tool with HATS Technology (WDHT) V6.0.1 IBM WDHT v7.0 IBM Rational HATS v7.1+ • IBM WebFacing and HATS projects can be deployed as one project (ear file). • Rich Client Platform support introduced. • Lower Tier Pricing for eServer iSeries • "Out-of-the-box" integration of WebFaced and non-WebFaced applications in a browser • Eliminated expensive HATS Interactive charge (Workload) • Now one product for HATS and IBM WebFacing projects • WDHT Withdrawn from Marketing, • IBM WebFacing Tool Enhancements: • WebFacing Tools now part of HATS toolkit • WebFacing Application Bridge —WebFacing applications can exchange host data with other Web applications • Support for Firefox • HATS Specific Enhancements: • Mobile Device Support Introduced • Industry JSR 168 portlet support • Visual Macro Editor introduced— Now much easier method of updating HATS Web services IBM WebSphere HATS • Addressed both 3270 and 5250 re-facing requirements • Required IBM WebSphere Application Server (WAS) for Deployment • Required more expensive AS/400-iSeries Interactive hardware Jan 2006 Feb 2007 March 2008 and Beyond Before 2006 Introduction: A Little History
Agenda • Introduction • Packaging • Deployment • New features of WebFacing • HATS: current state and hot features • Going forward
Packaging • IBM WebFacing Tool was part of WDSC1 up to Version 7.0 • WebFacing Tool became a part of HATS2 toolkit in Version 7.1 • IBM i application development portion of WDSC was repackaged into RDi3 • WebFacing Tool users need to install a supported Rational software development tool such as RAD4, and then install RDi and HATS in the same package as RAD • IBM provides a bundle named RDi SOA5, which contains the HATS toolkit and includes all the prerequisites for the IBM WebFacing Tool except WebSphere Portal support 1 WebSphere Development Studio Client for iSeries 2 Host Access Transformation Service 3 Rational Developer for i 4 Rational Application Developer 5 Rational Developer for i with SOA construction *
Packaging • WebFacing Tool is an optionally installable feature of the HATS toolkit • Advanced features of WebFacing Tool once part of WDSC AE1 are now part of HATS • Portal feature of WebFacing Tool requires either RAD or a flavor of RAD with base WebSphere Portal tooling 1 Advanced Edition *
Packaging, a Picture Speaks a Thousand Words WebFacing Tool part of WDSC HATS Toolkit WDSC 7.0 WDSC AE 7.0 WebFacing Tool WebFacing Tool HATS Toolkit 7.1 WebFacing Tool HATS Toolkit 7.0 RBD1 7.1 RAD-based IDEs 7.1 RDz2 7.1 RDi 7.1 RDi 7.1 RDi 7.1 RAD-based IDEs 7.0 WDz3 7.0 WDSC AE 7.0 WDSC 7.0 WebFacing Tool WebFacing Tool RDi SOA 7.1 RDi is only needed for WebFacing Tool HATS Toolkit 1 Rational Business Developer 2 Rational developer for z 3 WebSphere Developer for System z V7.0 V7.1
Agenda • Introduction • Packaging • Deployment • New features of WebFacing • HATS: current state and hot features • Going forward
The IBM WebFacing Tool HATS Toolkit What Can Be Re-Faced? IBM i Only Solution Requires RPG/COBOL Screen Data Definitions (DDS) Can Transform any 3270 or 5250 Screen
The IBM WebFacing Tool HATS Toolkit Screen Transformation One to One One to One or Many to One
The IBM WebFacing Tool HATS Toolkit Web Service GUI Portal Requires RAD Rich Client Mobile Screen Deployment Options GUI Portal Requires RAD
Agenda • Introduction • Packaging • Deployment • New features of WebFacing • HATS: current state and hot features • Going forward
WebFacing New Features (1) • Dynamic Data Stream Transformation • Your WebFacing application will continue working even when it encounters • Unconverted DDS-based application screens • Unconverted DDS-based system screens • UIM-based application screens • UIM-based system screens • HATS default rendering engine used for this feature • Available for both Web and portlet projects • Works on V5R4 and later Your WebFacing application works with NO “DDS not converted” runtime errors!
Combined Enterprise Application (EAR) HTML over HTTP (non-persistent) Shared connection to WF server (persistent) Internet, Intranet, or VPN WebSphere Application Server Client Web Browser IBM i (V5R4 or later) WebFacing Server WebFacing New Features (2) • Interoperability with HATS • WebFacing application and HATS application can be linked and deployed as one enterprise application (EAR), with a single runtime license • Allows DDS source-based application transformed by WebFacing to interact with application transformed by HATS • Benefits to WebFacing developers • No source for part of host application • HATS features desired
WebFacing New Features (2) • Customize each as separate projects • HATS project • Use HATS macros to automate application execution, control application flow, combine data from multiple IBM i systems, etc. • Improve the usability and attractiveness of screens by using transformations and different rendering patterns • WebFacing Project • Customize pre-converted screen artifacts • Convert the display files for the screens that are to be rendered by WebFacing Seamless interoperability between WebFacing and HATS applications!
Green Screen WebFacing Web/EGL Composite Web/EGL, HATS, WebFacing Applications Application Bridge HATS WebFacing New Features (3) • Application Bridge • Enables you to seamlessly interconnect new Web applications (written with EGL for example) with WebFacing or HATS • Allows you to quickly modernize using WebFacing/HATS at low cost • Can iteratively add new function taking advantage of the latest Web technologies • Use the Application Bridge feature to pass data between Web applications such as EGL and WebFacing applications • EGL or Web services allow you to access IBM i batch services or data from a Web application • The application bridge allows you to link your new Web application to an interactive IBM i application and share data
WebFacing New Features (3) • Application Bridge Scenarios • From WebFacing, call another Web application with data; the Web application does the necessary processing and then returns control to WebFacing with the data updates. • Other Web application can also invoke a WebFacing application with data and get the data updates back from WebFacing after it does the processing. • When used with the HATS/WebFacing Interoperability feature, you can make HATS and Web applications interoperate through the application bridge or make WebFacing, HATS and Web applications all work together. Cost-effectively modernize existing applications to the Web, take advantage of the latest Web technologies to build your new applications, and have those existing and new applications seamlessly work together!
WebFacing New Features (4) • Firefox Support • WebFacing Web, portlet, HATS interoperability applications can now run on Mozilla Firefox • Information about Firefox: • Estimated market share is 20%-30% worldwide • Available on Windows, Mac OS X, and Linux platforms • Provides a lot of useful add-ons, e.g., Firebug, Web Developer toolbar • Tips • For a project migrated to V7.5, do a reconversion so the project can run properly in Firefox • Write cross-browser code in your customizations • Want to test with an unsupported browser? • WebFacing issues a WF0095 error stating that WebFacing requires Internet Explorer 5.5 or greater, or Firefox V2.0 or greater • To avoid the above error, set the web.xml variable WFIgnoreBrowserTypeCheck to true WebFacing supports multiple browsers (Internet Explorer 5.5 and greater, and Firefox V2.0 and greater), covering 90% of the global browser market!
WebFacing New Features (5) • Limited Capabilities Users Support • Limited capabilities users: user profile has the LIMIT CAPABILITIES (LMTCPB) parameter set to *YES or *PARTIAL • LMTCPB is used to prevent the user from running programs outside of the menus • Works on V6R1 and later WebFacing supports limited capabilities users on V6R1 and later!
Agenda • Introduction • Packaging • Deployment • New features of WebFacing • HATS: current state and hot features • Going forward
Rich Client Browser Portal Host Access Transformation Services Summary Mobile Web Services • Integration at the desktop with other Eclipse-based applications • Client side processing • Rich set of user interface widgets • Supports Lotus Expeditor deployment • Zero footprint • Pure HTML • Access through your favorite browser, including Internet Explorer and Firefox. • Integration at the glass • Cooperative portlet support • JSR 168 compliant • Access host applications from mobile devices • Build self-service transactions • Expose host business processes as Web Services • Provide controlled access to vital host applications and host data. • Quick ROI : Host applications can be quickly deployed with a new user interface • Low cost : No need to rewrite application • Low risk : Leverage open, proven platforms and technologies • Increase productivity and reduce training costs • Improving work flow from multiple applications • Provides integration of host business processes and data with other Web, portal, and rich client applications 24
What’s Different About HATS Now? • IBM Rational Host Access Transformation Services is the strategic offering from IBM to transform 3270 and 5250 green screen applications. • The IBM WebFacing Tool development and deployment are now all part of HATS. • Reasons that had impacted HATS adoption in the past have been negated: • Operating System Interactive workload requirement • Higher cost Hardware requirement • High deployment costs on IBM i
Host Access Transformation Services (HATS) • What can you do with HATS? • Quickly and easily create Web, portal or rich client applications that provide an easy-to-use GUI for your green-screen applications • Low skills requirement • Highly customizable • Iterative development process • Transformation “on the fly” • Extend terminal application tasks as Web services • Benefits • Extend host application to new users • Improve the navigation of your host application • Reuse your existing assets in a Service Oriented Architecture • Avoid rewriting applications (no impact to code)
Improve Navigation & Productivity • Macros & Global Variables • Skip unnecessary screens; combine screens; split screens, enter data on behalf of the end user • Store end user input as global variables to use again; pre-fill text entry fields • Improve User Interface with Screen Customization • Add buttons, hot links, drop-down menus, valid value lists, etc. • Modify graphics, fonts, colors, and layout • Add business logic • Local print support • Native keyboard support • Security – HTTPs, SSL • Performance – HTTP Compression, Contention Resolution • Supports iterative development • Default Transformation rules - fully functional HATS application on the web quickly • Customize Default Transformation rules • Customize screens
Achieving a Green Screen Look with HATS • HATS supports host colors and extended field attributes, including: • Numeric only, alphabetic only, signed numeric, reverse image, column separator, underline, and blink fields • Supports automatic field advance • Host keypad and OIA can be displayed (and positioned anywhere) • Native keyboard support (i.e. pressing F12 in the browser sends F12 to the host application).
Extends host applications to the desktop. Applications run on: Eclipse RCP 3.2 or 3.3 IBM Lotus Expeditor Client 6.1.x Provide a modern GUI interface to mission critical green screen applications. Processing occurs on the desktop (WebSphere Application Server is not required) Provides the capability to integrate host access applications with other applications on the desktop. Alternative to traditional terminal emulator products. Targeted at internal users in a controlled environment. HATS Rich Client Overview
What is HATS mobile device support? • HATS transformation applications can now be accessed by pervasive devices such as cellular phones, data collection terminals, and Personal Digital Assistants • This allows for the HATS developer to: • Customize and transform individual screens • Add business logic to screen interactions • Enhance the presentation, layout, and flow of the original host systems • Supported browser: Internet Explorer Mobile 5.0 or later • Reminder: HATS Integration Object or Web service data can also be used in conjunction with mobile devices
The Value of HATS SOA • HATS is an important part of the IBM SOA strategy! • IBM SOA Foundation helps to extend the value of the applications and business processes that currently run your business, not replace them. • HATS does not require application reengineering or rewriting • Rewriting can consume significant amounts of time and resources. • Rewriting requires access to and understanding of application source code. • Rewriting inherently introduces new bugs that must be found and fixed. • Simply put - rewriting is not an option for some customers! • HATS is unique • HATS is the only IBM product that Web Service-enables 3270, including CICS and IMS, 5250, and VT terminal applications – great for customers with a mix of applications (one tool can be used to enable all of them). • HATS generates standard Web Service interfaces • HATS services can be integrated into an existing SOA.
SOA with the HATS Visual Macro Editor Web services are generated from macros. Macros can drive navigation, enter data, and retrieve data from VT, 3270, and 5250 (and WebFacing Server) applications.
Other HATS SOA Capabilities • Connection pooling • Automatically connects a specified number of connections at application startup. Connections can be reused (this decreases connect/disconnect activity on the system). • Connect / disconnect macros • Automatically signs on sessions at startup and signs them out when no longer needed. • User lists • Signs on sessions using a set of predefined credentials. • User list information can be encrypted. • Stateful or stateless interaction (even for Web services) • Enables clients to have stateful interactions (i.e. the host session stays active between interactions) with host applications using Web Services.
Summary of HATS Features and Value Propositions • Host screens are converted to GUIs on the fly, in real time • Improved navigation of host application • Zero footprint on the desktop with Web deployment • Support deployment to Rich Client • Access host assets from mobile devices • Combine screens and data from multiple applications • Eliminates need to customize every screen • Generate Web services from host transactions • Exploits security & scalability of WebSphere Application Server and WebSphere Portal • Extensible through IBM Rational Software Delivery Platform • Supports iterative development
Agenda • Introduction • Packaging • Deployment • New features of WebFacing • HATS: current state and hot features • Going forward
IBM WebFacing Tool Costs - Standard Retail Prices - Prices are subject to change without notice
Going forward • Resources: • Official HATS Web site: www.ibm.com/software/awdtools/hats • Hotspot: http://www-949.ibm.com/software/rational/cafe/community/hats • Blogs • Various self-help documents • Forums • Find help from an IBM partner • Sandbox: www.ibm.com/developerworks/downloads/emsandbox/systemi.html • Play with the HATS without installing • Trial download software: http://www-949.ibm.com/software/rational/cafe/docs/DOC-2952 • Recent articles on WebFacing Tool • “Wondering about WebFacing?” Published in Extra e-newsletter of IBM Systems Magazine, IBM i edition August 2009 (http://www.ibmsystemsmag.com/ibmi/enewsletterexclusive/26105p1.aspx) • “New WebFacing Features” Due to publish in IBM Systems Magazine, IBM i edition September 2009