Point and click display file import
ASNA Wings provides a simple point-and-click dialog box for important IBM i display files from DDS display file source members. Wings reads the DDS and then generates a browser-based equivalent.
The ASNA Wings' user interface can be customized an infinite number of ways. The Wings presentation layer is an ASP.NET Web site and can therefore be extended with virtually any ASP.NET custom control. Wings also includes several controls with which you can provide user interface elements such as pie and bar charts, images, and maps. You can enhance your Wings displays with features such as business partner Web services, Ajax, and MS Office integration. The look and feel of your Wings displays can be easily tailored to use your corporate colors and logos.
The Wings Open Access handler passes a semantic buffer of data to the Wings presentation layer. For basic use of Wings, this doesn't matter much to you. But, when you want to customize a Wings display, it will mean a lot to you! As you add functionality to the presentation layer you're able to naturally use the display file data addressing it by field name. Wings doesn't use a 5250 data stream, therefore it lifts you from the positional nature of field values in the 5250 data stream that screen scrapers use. The data that Wings brings to the presentation includes all of the field values, all of the indicator values, and any hidden or system field values.
With Wings, you're able to add functionality to the presentation layer (using VB.NET, C#, or ASNA Visual RPG) and these enhancements can be completely transparent to the underlying RPG program. It continues to run as though it were communicating with a traditional green-screen display file.
100% of your existing RPG remains unchanged
Wings' underlying enabler is IBM's Rational Open Access for RPG edition. This API empowers Wings to intercept RPG workstation data at a very low level. Prior to the introduction of the Open Access (OA) API, it was virtually impossible to intercept workstation data like this. Thanks to the OA API, Wings's displays are performant and secure and require no changes to your RPG programming logic. Read more about IBM's Open Access.
High fidelity with DDS-based rules
Wings creates browser-based displays derived from DDS display file specifications. The indicator-driven DDS rules that govern how your program behaves are faithfully implemented by Wings. For example, if your RPG program positions the cursor to a field conditionally based on an indicator value, Wings will also obey that rule.
Wings comes with the ASNA Browser Terminal emulator
Wings is packaged with ASNA's browser-based terminal emulator, Browser Terminal (BTerm). Wings uses BTerm to render display files that you haven't yet modernized with Wings. This gives you the flexibility to cherry-pick the displays you want to modernize first, while the others are rendered in BTerm. BTerm is also important because you may also have end-user workflows that use displays that can't be modernized by Wings. For example, you may have some users who frequently need to use the IBM i WRKSPLF command. With Wings, those kinds of screens are displayed in BTerm. Read more about BTerm.
Bulk screen import available with Wings Flight Plans
Wings includes a feature called Flight Plans which imposes a more formal display file import work flow. This helps you plan for, and execute, the import of a large number of displays at once.