EGL Online Seminar Series What’s New in V7.1 Jon Sayles – [email_address] All statements regarding IBM's plans, directions, and intent are subject to change or withdrawal without notice. The content of this presentation does not constitute IBM commitment to deliver products and functions. IBM Warranties are delivered exclusively as indicated in products availability Terms and Conditions
Consistent with EGL philosophy, hides all Ajax complexities with a higher level abstraction
Includes WYSIWIG and scripted composition tools, and libraries of Rich UI widgets (EGL rendering of DOJO, YUI, EXT, etc)
Easily integrate/consume any service (REST or SOAP, external or created in EGL)
Single language end-to-end, simple and productive to deliver RIA-to-mainframe solutions
Combined with EGL legacy interoperability easily extends legacy to Web 2.0
EGL notation and tools to support development of Rich Internet Applications (RIA)
When the linkage has remotePgmType=EGL or EXTERNALLYDEFINED
The EGL catcher program is used so the EGL iSeries COBOL runtime must be installed
If the linkage includes luwControl=CLIENT, the caller can use SysLib.commit() and SysLib.rollback() on the work done by the called program
Connections are pooled. On the first call a connection and host job are created based on the host and user name provided. The host job stays active until the JVM runs to completion. Subsequent calls will use the existing connection. In a web environment there is no guarantee that calls will get the same connection.
The EGL catcher program is not used so the EGL iSeries COBOL runtime is not needed
luwControl=CLIENT is not supported. Commits and rollbacks must be coded on the host.
Currently only available for JSFHandlers. A connection and host job is created for each web session. Each time that session makes a call to the host it uses the same connection. This is especially useful when calling a stateful program on the host. A stateful host program can keep resources open (SQL connections, files, queues, etc.)
The connection will be disconnected when the HTTP session goes times out. The user can also use ExternalTypes to gain access to the HTTPSession and invalidate it (make it timeout).