|
With the IBM WebFacing Tool, you can quickly convert your DDS display file source members so that the user interface of your System i programs can run in a browser. The WebFacing Tool facilitates the conversion process through user-friendly wizards for selecting the 5250 application's DDS source, converting it, and deploying the new Web-based interface to your program as a Web application. JavaServer Pages and XML files are generated at development time and take the place of your DDS code, allowing for flexibility in customizing the appearance of your new interface prior to run time. Customization
Using the provided tools, you can further enhance the graphics, fonts, colors, and layouts of your Web pages. For example, you can use Web Settings to customize how your application renders and functions when accessed through a Web browser. Cascading Style Sheet Positioning (CSS-P) is one of the Web Settings available to you. It allows the DDS fields on the Web-enabled interface to be repositioned, unconstrained by the boundaries of the original 5250 area, and offers an almost unlimited ability to customize the Web-enabled interface. Zero OLTP
Your WebFacing application can be run without requiring Online Transaction Processing (OLTP) capacity. System screens and unconverted parts of your application can also be displayed by WebFacing through dynamic transformation of the screens. Portal
The WebFacing Tool can generate a portlet application that can be deployed to a WebSphere Portal server and added to the portal pages served by that server. This allows multiple applications to run in the same browser window. Portlet applications can also take advantage of the features available to a WebFacing Web project. Single sign-on
Single sign-on enables users to access more than one application and multiple platforms using one user ID and password. For example, you can integrate secured WebFacing and other Web applications which a user can access without requiring separate IDs and passwords for each, or you can access a WebFacing portlet without signing on again after you have signed on to the portal. WebFacing and HATS interoperability
The WebFacing and HATS interoperability feature enables you to easily integrate your WebFacing and HATS Web applications when running on the Web. You can create a HATS/WebFacing enabled project with the WebFacing Tool and link it with a HATS project. This linked HATS/WebFacing application operates seamlessly and provides a unified, Web-enabled interface, which can be deployed to a WebSphere Application Server. It utilizes the capabilities of both HATS and the WebFacing Tool. Application bridge
The application bridge is of great value when enhancing your i5/OS application by allowing you to implement part of it as a Web application, such as Enterprise Generation Language (EGL), and modernizing other parts of your application with WebFacing or HATS. It allows WebFacing to transfer control and data to and from other Web applications, such as EGL, giving you the ability to combine HATS, WebFacing, and other Web applications into a single application. i5/OS integrated Web application server
WebFacing applications can be deployed to the i5/OS integrated Web application server. You can use the i5/OS integrated Web application server if you are deploying WebFacing Web applications and have limited i5/OS system resources that cannot optimally run the WebSphere Application Server. Note that this configuration does not support high availability and failover. High availability and failover
WebFacing provides cluster support on a WebSphere Application Server Network Deployment (ND) to meet the high availability and server failure bypass needs of your application, allowing for better response times, scalability, and failover safety. You can also configure additional interactive subsystems on i5/OS to handle a greater number of concurrent users of your WebFacing application.
| 
