Changing the wheels on a running train - PowerPoint PPT Presentation

1 / 15
About This Presentation
Title:

Changing the wheels on a running train

Description:

Lessons learned. Vopak is a logistics service provider for storage and handling of liquid and ... PS 3 (10 servers in farm) AIX 5.3. Oracle 9.2.0.7. Windows ... – PowerPoint PPT presentation

Number of Views:66
Avg rating:3.0/5.0
Slides: 16
Provided by: lambert1
Category:

less

Transcript and Presenter's Notes

Title: Changing the wheels on a running train


1
Changing the wheels on a running train
  • Replacing Vopaks JDEdwards enterprise servers
    and storage

Session 20470 L.J.J. Caljouw
2
Agenda
  • Vopak
  • JDEdwards EnterpriseOne at Vopak
  • The CDC2006 project
  • Approach
  • Tools and techniques
  • End result
  • Lessons learned

3
  • Vopak is a logistics service provider for storage
    and handling of liquid and gaseous chemical and
    oil products.
  • Vopak operates 75 tank terminals in 30 countries,
    with 3,442 employees, providing a total of over
    20 million cbm storage
  • Revenue Around 1 B, ROCE 19,4

Vopak information services
  • Operations 11
  • Development and support 13
  • Business consultancy 8
  • IT Architects 4
  • Management 7

4
JDEdwards EnterpriseOne at Vopak
  • PEPI Package Enabled Process Improvement
  • Number of Tank terminals (sites) live 40
  • Concurrent users 350
  • Named users 1,000
  • Number of batch jobs / prints 225,000
  • Data Volume 340 GB
  • True 24/7 business
  • Maintenance windows
  • Technical maintenance once a month, 4 hours max.
  • Software deployment once a month, 4 hours max.

5
JDEdwards EnterpriseOne at Vopak
  • JDEdwards version Xe, SP22
  • Citrix PS 3 (10 servers in farm)
  • AIX 5.3
  • Oracle 9.2.0.7
  • Windows 2000 AS
  • XPI/WebMethods

6
The CDC2006 project
  • Goals
  • Support growth strategy for Vopak
  • Increase short term storage capacity
  • Reduce complexity
  • Control operational costs P-series
  • Results
  • Selection and acquisition of new hardware
  • Installation of new hardware
  • Migration of software
  • Removal of old hardware

7
The CDC2006 project
Old situation
Target situation
Data center Amsterdam
Data center Amsterdam
P570
S85
S85
PRD ORA
PRD JDE
PRD ORA
PRD JDE
Dell 136T
PRD BCK
IBM N5200
NetApp F810C
PRD Data
PRD Data
Data center Rotterdam
Data center Rotterdam
S7A
P570
S80
S7A
CRP/DR ORA
CRP/DR ORA
DVL ORA/JDE
DR ORA
DR JDE
CRP ORA
CRP JDE
DVL ORA
DVL JDE
Dell 136T
IBM 3310
CRP/DR BCK
DAS
NetApp F810C
IBM N5200
CRP/DR Data
DVL Data
DR/CRP/DVL data
8
Approach key success factors
  • Commitment from supplier
  • Prince-2 Project Management Approach
  • Instance-by-instance migration
  • Preparation
  • Trial migration
  • Actual migration
  • Verification
  • Work with alternative go-live dates from the
    start
  • End-user communication
  • Avoid concurrent changes
  • Provide fallback possibilities at all times
  • Design for flip the switch migration approach

9
Service Names (DNS Aliases)
  • DNS-entries
  • NLAMSDS103 gt 10.1.23.45
  • PRDORA00 gt NLAMSDS103

JDE.ini DB SYSTEM SETTINGS . ServerPRDJDE00
.
tnsnames.ora PEPIP (DESCRIPTION
(ADDRESS_LIST (ADDRESS (PROTOCOL
TCP)(HOST PRDORA00)(PORT 1234))
Doesnt work for everything. Script for exceptions
10
Replication techniques
  • Ontap SnapMirror replication
  • Block-size data replication (Band Width
    regulation)
  • Used to replicate all non-Oracle data
  • Oracle DataGuard
  • Oracle log-files gt ship and apply
  • Used to replicate all Oracle data
  • Introduction of OEM 10 makes this EASY!

Dont use service names!!
11
Provide fallback possibilities
  • Shut down JDE Oracle on old servers
  • Switch replication directions
  • Adjust DNS settings
  • Start Oracle and JDE on new servers
  • Actual Migration
  • Stop replication
  • Decommission old servers
  • Test Migrations
  • Migrate backwards
  • Using actual data from new
  • Using a snapshot just prior to migration

12
Partitioning
  • One LPAR per JDE Oracle instance
  • Virtualisation of CPU and Memory
  • AIX parameters optimised for purpose
  • P570 resource (re-)allocation / prioritisation
  • Overhead LPARs
  • VIO brings Virtualisation of I/O
  • For even more failover, two VIO LPARs
  • NIM LPAR

13
End Result
  • Planned go-live for PRD on schedule
  • Migration process executed in 2 hours
  • No issues after go-live
  • Performance increase after go-live (30)
  • Floor space reduction of over 50
  • Opportunities for new techniques
  • Additional LPARs
  • SnapCopy

14
Lessons Learned
  • Using operational staff requires close(r) project
    management
  • Priority for operational issues
  • Creative solutions / additions
  • One physical box creates additional risk/impact
    for HW maintenance
  • Plan for documentation separately
  • Avoid latest technology from supplier
  • Risks (Nseries is almost equal to NetApp)
  • Learning curve supplier

15
Questions
  • ?
Write a Comment
User Comments (0)
About PowerShow.com