Web Enabling AllFusion 2E Applications - CA Communities

coordinatedcapableSoftware and s/w Development

Nov 4, 2013 (3 years and 11 months ago)

122 views

Web Enabling
AllFusion
®

2E
Applications

Rory Hewitt


Software Architect

Computer Associates

San Francisco, CA USA

Session: 2B (10:00am Thursday April 28
th

2005)

Session Abstract


AllFusion 2E Web Option enables organizations
to bring existing key iSeries applications to the
Web with
no

reprogramming and
no

changes to
the underlying business logic, which can help
reduce development costs by accelerating time
-
to
-
market.


This session will provide an overview of Web
Option, key features and development tips.

Speaker Bio


Rory has been using 2E
since 1994 and has been
part of the 2E Development
Team since 1997


Rory is now the Software
Architect for the 2E
Development Team


Rory likes snowboarding

Lola Hewitt


born February 12
th

2005

Agenda


Background


Installation & Setup


Running Web Option


Using the HTML Generator


New features in r8.1 and beyond


Q&A

Background

Background to Web Option


Web
-
enablement for the iSeries

-
“Screen
-
scrapers” vs. “Application
-
changers”


IBM’s offerings

-
WebFacing, HATS, HATS LE etc.


Features of Web Option

-
Best of both worlds

-
Simple and easy to learn and use

-
Extremely flexible

-
Pure HTML

SCREEN

JOB

iSeries

WEB OPTION ROUTER

HTTP SERVER

WEB OPTION SERVER

…001001001001…

SCREEN

JOB

Web Option concepts


Runs on top of your existing interactive jobs

-
Requires
no

change to existing applications

-
Similar performance to green
-
screen use


Uses the standard OS/400 HTTP server

-
No need to install an app. server like WebSphere


Runtime requires
no license

-
Can be used on multiple production boxes


Includes Just
-
In
-
Time support by default

-
Automatically caters for ‘unidentified’ screens

Installation and Setup

Installing Web Option


Install zipped save file from CD or FTP site


Restore Web Option libraries from save file


Initialize Web Option


Start Web Option server



er…



…that’s it

Running Web Option

Running Web Option


Start HTTP server (if not started)


Start Web Option server (if not started)


Access iSeries from connected browser, e.g.:

-
http://my
-
iseries:4100/web2e


Sign on to iSeries using displayed sign
-
on
screen


Navigate through screens
exactly

as you would
in a green
-
screen session

Running Web Option


Screens identified and screen data merged with
pre
-
generated HTML ‘skeleton’ page


Just
-
In
-
Time (JIT) processor invoked when no
skeleton exists

-
Uses Web Option defaults to create basic page


No need to identify every screen or create link
reference table

Generating HTML skeletons

Generating HTML skeletons


Set up 2E model to use Web Option



Generate and compile 2E function

-
Screen includes hidden *SCREEN ID field



Command
-
based front
-
end (YGENMLS)

-
Can run over 2E model list

-
Can process individual function/DDS member

-
Can be run directly from within model screens

Generating HTML skeletons


Processes 2E display file DDS

-
Includes model/function information

-
Parses text and variables to HTML

-
Can use message ID’s for variable text etc.



Data
-
driven HTML generator

-
Controlled by syntax/formatting/data files

-
Can be edited to provide customer
-
specific data

Generating HTML skeletons


Generates HTML ‘skeleton’ pages

-
Reside on iSeries as source members

-
Contain encoded control information


HTML tags


Output text


Web Option control tags

Example skeleton code

<td align="left" height="20" colspan="34">


<span class="atr3A">


account balance .


</span>

</td>

<td height="20" colspan="6">

</td>

<td align="right" height="20" colspan="24">


<span class="atr20">


(_f0422)


</span>

</td>


Output text

Web Option tags

HTML tags

Screen Identification

Session Summary


Hidden identifier generated into display file DDS
when screen generated in 2E

-
Record added to screen cross
-
reference file

-
Used at runtime to identify screen

Session Summary


Hidden identifier generated into display file DDS
when screen generated in 2E

-
Record added to screen cross
-
reference file

-
Used at runtime to identify screen


Skeleton generated using YGENMLS

-
Record added to MLS cross
-
reference file

-
Used at runtime to identify skeleton to display


Session Summary


Hidden identifier generated into display file DDS
when screen generated in 2E

-
Record added to screen cross
-
reference file

-
Used at runtime to identify screen


Skeleton generated using YGENMLS

-
Record added to MLS cross
-
reference file

-
Used at runtime to identify skeleton to display


At runtime, Web Option merges run
-
time data
with skeleton to give HTML web page

Skeleton customization


Global Customisation

-
Web Option control values

-
MLS Syntax file


YEDTMLSSYN command


Model
-
level Customisation

-
Customisation Data added to Model Elements

-
Retained when skeleton is regenerated


Specific Customisation

-
Using HTML editing tool or Notepad

-
Lost when skeleton is regenerated

Command keys as hyperlinks

Pop
-
up date picker window

Scripting


Web Option
-
specific scripting language

-
Similar to Client Access macro language


Behind
-
the
-
scenes functionality

-
No visible screen transfer


Scripts created/stored as source members


Can be edited for immediate change


Saves data between screens


Can loop through screens

Scripting

Main

Menu

Display

Customers

Edit

Customer

Edit

Accounts

Display

Orders

Edit

Order

Edit

Details

Typical iSeries

Application

New features in r8.1

New features


Improved multiple
-
language support


Use cascading style sheets


Further increase flexibility of generator


Drop down list based on condition values


Enhanced scripting support


Enhanced model integration


Improved multiple
-
language support


Data elements can be externalized

-
Screen constants

-
Values List data (for drop
-
down lists)

-
Prompt messages (e.g. screen constants)


Can switch languages ‘on the fly’

-
No change to underlying job library list

Cascading style sheets


Externalization of web page style elements


Shipped default style pages


Industry standard


Allows for ‘on the fly’ style changes

Enhanced model integration


Can invoke MLS generator from many model
screens

-
EDIT FUNCTIONS

-
EDIT ALL FUNCTIONS

-
OPEN FUNCTIONS

-
EDIT MODEL OBJECT LIST


Can invoke MLS editor from inside model

-
EDIT FUNCTION DETAILS

-
EDIT MODEL OBJECT LIST

Enhanced model integration


More information retrieved from model

-
Command key strings

-
Prompt messages


Values List Data now used for DDL’s


Prompt Messages used where defined


Enhanced scripting support


Additional script commands

-
IFNOT


inverse of IF

-
MSG


send message to user

-
TAB


tab to fields

-
Counter commands


INZ/ADD/SUB/MLT/DIV

-
SCAN


scan for data

-
SET


set a local variable

-
CAT


concatenate screen values

General enhancements


60K skeleton size limit removed


Tags now usable within JIT pages


Max sessions increased from 1000 to 10000


Improved debugging support


F4 prompting for window fields enabled


Function key ignoring enhanced


Web Option comments


Enhanced script processing

Questions & Answers