Go Thin Transitioning to EnterpriseOne Web Client

1
Go Thin! - Transitioning to EnterpriseOne Web
Client

• Session 28650
• Presented by
• Alex Rodriguez Premier Group
• Andrew Ritting Penn Engineering

www.premierway.com
2
Agenda

• Overview of EnterpriseOne Web Client
• Why use the Web Client?
• Preparing for the Transition
• Demonstration of Key Web Client Features
• Comparison of Web Client vs. Traditional Client
• Migration Paths to Web Client
• Web Client Administration Tools
• Next Steps
• Questions and Answers

3
History of EnterpriseOne Web Client First
Generation (Service Packs 11-14)

• J.D. Edwards first established the web client
  with the release of OneWorld B733 in 1998
• Designed to expand connectivity outside of the
  LAN and support Inquiry only type users
• Mixed mode connectivity was supported allowing
  customers to have standard Windows clients and
  web clients
• Technical architecture from first generation
  still remains in use today
• First version supported a Java Client

4
History of EnterpriseOne Web ClientSecond
Generation (Service Packs 15-20)

• With the release of OneWorld Xe new features were
  added to increase the usability of the web client
• New enhancements such as Import/Export, Column
  Movement and Grid Tabs expanded the user base of
  the web client to include some data entry users
• Mixed mode connectivity still supported allowing
  customers to have standard Windows clients and
  web clients
• Began support of Websphere 4.0

5
History of EnterpriseOne Web ClientTodays
Generation

• Currently two versions exist Tools Release 8.9x
  for 8.9-8.12 customers and Service Pack 23 for Xe
  and ERP 8 customers
• Current version can serve as a replacement for
  the standard Windows-based client (8.11 supports
  only the web client)
• Mixed mode connectivity is still supported for
  all releases except 8.11 allowing customers to
  have standard Windows clients and web clients
• Technical architecture from first generation
  still remains in use today
• Java Client no longer supported

6
Tools Release vs. Service Pack

• Tools release is the new term for the foundation
  code for 8.x versions (replaces Service Pack)

7
JAS Server
Enterprise Server
HTTP Service
Business Functions
Servlet Engine
HTML Pages
JDENET
JAS
UBEs
JVM
Web Browser
Applications
JDBC
Operating System
Java Serialized Objects
JDB
JDBC
Database Platforms
DB2
SQL Server
UDB
Oracle
8
Why use the Web Client?

• Reduces Deployment Costs
• Centralizes Server Administration
• Effective Replacement for Windows Client
• Highly Scalable
• Access is available from most popular browsers
• Enable Self-Service functionality for end users
  and customers
• Improve System Availability for 24x7 operations

9
Preparing for the Transition Configuration Changes

• Web Server is now required
• Browser now required for each client
• Possible upgrade to current enterprise server
  more processing on back end
• Additional generation step is required (post
  package build) to create java serialized objects
  (F989998 and F989999 in Central Objects) 8.12
  Automatic Generation
• Refer to Customer Connection for latest MTRs

10
Preparing for the Transition Training

• EnterpriseOne Web Server Installation
  Administration (5 Days)
• IBM WebSphere/Oracle Application Server
  Administration (5 Days)
• Version Net Change Training (if upgrading
  releases)

11
Go Thin! - Transitioning to EnterpriseOne Web
Client

• Demonstration ofWeb Client Software
• Tools Release 8.96 Update 1 (8.12)

www.premierway.com
12
Demonstration Architecture
13
Web Client Feature Comparison Service Pack 23
vs. Tools Release 8.96
14
Windows Only Applications 8.11

• All Design Tools (FDA, RDA, TDA)
• Data Dictionary
• Object Management Workbench (OMW)
• Security Workbench (8.12 Only)
• Package Build / Deployment
• Product Packaging
• Software Updates
• Solution Explorer for launching administrative
  and design applications only
• Table Conversion

15
Web Client vs. Traditional Client

• Web
• Visually engaging
• Supports most browsers
• Small Footprint on PC
• Limited Hardware Requirements
• Excellent Performance
• Table Browser (8.94)
• No Development Client
• Task Explorer

• Traditional Client
• Familiar Interface
• Strong Desktop Integration
• High Resource
• Requirements on PC
• Can be Network Intensive
• Full Development Client
• Support
• Solution Explorer
• Only supported on
• Microsoft Windows

16
Migration Paths to Web Client

• Staged Transition
• Applicable to customers not running the web
  client that would like to perform a controlled
  and staged transition
• Version Upgrade to 8.12
• Applicable to customers running older releases
  that would like to migrate to web only all at
  once and also receive all the benefits of 8.12

17
Staged Transition to Web Client
Update EnterpriseOne Service Pack
Hardware and Software Preparation, Training
Define Users for Web Client Pilot
Build and Tune Web Server
Conduct Web Client Pilot
Web Client Go-Live
Months 1
2
3 4
Service Pack 23 or Tools Release 8.96
Follow User Guides and Best Practices
Repeat cycle until all user have been migrated to
Web Client
Select Platform for Web Server and acquire
hardware and software
18
Complete Web Client MigrationVersion Upgrade to
8.12
8.12 Upgrade Planning Phase
Hardware and Software Preparation, Training
Build 8.12 Servers and Perform Upgrade
Conduct 8.12 Retrofitting and Testing
8.12 Go-Live
Months 1 2
3
Variable
Analyze Current Environment and Modifications
Follow User Guides and Best Practices
Timing is variable depending on modification
level and testing times
Since a complete version upgrade is being
performed significant testing and training needs
to be done
Update Hardware and Software to Support 8.12
19
Migration Considerations

• Possibly reutilize Citrix or Application Servers
  as Web Servers
• Choosing your browser (IE Preferred)
• Load Balancing (Hardware vs. Software)
• Compression (Recommended for WAN)
• Security (Firewalls, SSL, DMZ)
• Enterprise Server sizing

20
Customer Profile Penn Engineering

• PennEngineering serves as a single source for
  fastening solutions, offering the hardware,
  equipment, and technical services and support to
  satisfy assembly needs from design through
  production.
• October 2001 Go-Live on OneWorld Xe with IBM
  xSeries Hardware
• March 2004 Move to IBM iSeries Hardware and
  added Xe Web Client (Service Pack 22) to support
  some remote users (USA, England, Ireland,
  Singapore and China)
• December 2005 - In order to provide support for
  multiple languages and locations more effectively
  Penn began plans to upgrade from Xe to 8.11SP1.
• June 2006 Premier Group chosen to assist with
  8.11SP1 Upgrade
• With support from Premier Group, Penn
  successfully upgraded from EnterpriseOne Xe to
  8.11SP1 completing the web-only migration for all
  users in all worldwide sites. The upgrade was
  completed in 3 months.
• September 2006 - Go-Live on 8.11SP1
• Operations have been streamlined and Penn can now
  support their 24x7 multi-site, multi-language
  operations more effectively

21
Go Thin! - Transitioning to EnterpriseOne Web
Client
Demonstration ofWeb Client Administration Tools
www.premierway.com
22
Administration Tools Review

• Browser-based Administration of any EnterpriseOne
  Servers
• Gather data for performance tuning and
  troubleshooting
• Monitor Real-Time User Activity
• Clear key caches without need for server reset
• Make configuration changes on the fly

23
Next Steps

• Assess current EnterpriseOne environment to
  determine best scenario to select
• Prepare budget and cost justification for the Web
  Client Project
• Build an action plan to ensure successful
  migration to the web client
• Implement your action plan
• Begin enjoying the benefits of the web client

24
Questions and Answers
Premier Group Alex Rodriguez, Technical Services
Manager 305-567-3188 x223 alex_rodriguez_at_premierw
ay.com Penn Engineering Andrew
Ritting 215-766-8853 x1863  aritting_at_penn-eng.c
om
Updated Copy of Presentation Available _at_
www.premierway.com