1. Implementation - Deployment Methods of deployment –User PC –Network shared (workstation install) –Terminal server –Web Deployment (ActiveX) (Note: this section is covered in detail in the next presentation) –lookserver deployment (Note: this is covered in the lookserver training module)

2. 0. Approach Options Available –Program files are installed on the PC. –Program files are installed on the PC with updates ‘pushed’ out. –Program files are installed on the PC with SID on server. Deployment – Local Installation

3. 0. Approach All Program files on the PC Deployment – Local Installation

4. 0. Approach Program files on the PC (cont.) –Pros All the files are executed locally therefore eliminating the reliance on a third- party server. Network traffic is minimized as communication will be via 5250 data streams to the iSeries. –Cons Any updates to program or data files will have to be applied manually. * Can still use nlupdate Deployment – Local Installation

5. 0. Approach Program files on the PC with updates ‘pushed’ –Use ‘images’ with third party products from Microsoft and Novell. Deployment – Local Installation

6. 0. Approach Program files on the PC with updates ‘pushed’ (Cont.) –Pros Files are executed locally. Network traffic is minimized. newlook maintenance is centralized for easier updates. updates can be scheduled for quiet times. End-user operating systems, drivers, virus definitions and third-party programs can also be installed and updated ‘silently’. –Cons There is an implementation overhead associated with the initial loading of files on end-user PCs. Not every company has access to these tools or infrastructure. Deployment – Local Installation

7. 0. Approach All Program files on the PC (except SID) Deployment – Local Installation

8. 0. Approach All Program files on the PC (except SID) –Pros All the files are executed locally therefore eliminating the reliance on a third- party server. Updates to the definition file can be applied centrally. –Cons The screen ID records within the SID file are loaded every time newlook is started. This could create an increase in network traffic if a large number of users try and log on at the same time. Any updates to program or data files will have to be applied manually. –Variations Custom Installation Scripted Installation Deployment – Local Installation

9. 0. Approach Options Available –Program files are stored and executed from file server (workstation/server install). –Citrix (or Windows Terminal Server). Deployment – Network Installation

10. 0. Approach Program files are stored and executed from file server (workstation/server install) Deployment – Network Installation

11. 0. Approach Program files are stored and executed from file server (workstation/server install) (Cont.) –Pros All the files are centrally located and therefore easily updated. –Cons The program and SID files are loaded every time newlook is started. This will create a noticeable increase in network traffic if several users try and log on at the same time. End-User PCs are reliant on access to the third-party server to execute newlook. Deployment – Network Installation

12. 0. Approach Citrix (or Windows Terminal Server) Deployment – Network Installation

13. 0. Approach Citrix (or Windows Terminal Server) (Cont.) –Pros All the files are centrally located and therefore easily updated. Support via Citrix for Mac, Java, PDA, Thin Client and Web delivery. –Cons The communications from the server will be full GUI frames and not 5250 data streams. As the GUI frames will be of a greater size than the 5250 data stream bandwidth requirements will increase. End-user PCs are reliant on the Citrix server and therefore if it is unavailable users will not be able to access the iSeries. Deployment – Network Installation

14. Web Deployment –Activated via the Internet browser, users download, install, and run newlook by simply pointing their browser at a nominated web page. –The files required to run the ActiveX control are packaged into CAB files & are stored on the web server. Program CAB Web Server Custom CAB Deployment –Web Deployment

15. Web Deployment –Pros Installation can be unattended. Users click on the web page and the download of the necessary files takes place automatically Updates are automated. Each time a user starts the web page a check for newer files takes place. All the installation (CAB) files are centrally located and therefore easily updated. If the application has been downloaded previously then locally cached files will be used. Only updates that are made to the server will be downloaded. –Cons A browser supporting ActiveX controls is required.

16. Deployment using lookserver –HTTP traffic between client and web server –Telnet traffic between web server and iSeries Deployment –lookserver Firewall/Proxy Server IBM iSeries Application server Internet HTTP/HTTPS TN5250 Web Server (IIS) thinclient (IE, FireFox etc)mobileclient – PDA (Pocket IE) HTTP/HTTPS

17. Deployment using lookserver –Pros Zero footprint so no download of program files is required Will work across multiple desktop platforms. Only requires a browser with XML support. Will support mobile/PDA devices natively. Updates are easy to deploy. –Cons Desktop integration not supported Full rich client interface only available with smartclient. Deployment –lookserver

18. newlook 8 Training Deployment