PureApplication and IBM Sterling Order Management pattern by Icon Solutions.

1. Exploiting Hybrid Cloud to Better
Manage Retail Workloads and Lower
Management Costs
BIN-4237
Thursday 26th February 2015
BIN-4237

2. Icon and PureApplication
Skilled
PureAppllication
Practice
•Focused on the
needs of current
and prospective
customers
•Includes ex IBM
Hursley Lab
contacts
Leader in
PureApplication
Patterns
•First Internet
Banking pattern
(award winning)
•First MQ Broker
plugin
•First WS
Commerce &
Sterling Order
management
pattern
•First Software AG
webMethods
pattern
Specialist in
DevOps
•UrbanCode and
PureApp
integrators
•SDLC enablers
•Practical
experience with
large global
insurer
Owners of the
European Pure
User Group
•An independent
community for
PureApplication
customers to
share user
experiences,
exchange best
practices and help
shape future plans
2

3. 3
Retail topologies are complicated…

4. 4
Users

5. 5
The technology can be even
more confusing!

6. 6
The development lifecycle challenges
are all too familiar….

7. 1 It takes too long to deploy test and dev
environments
2 Errors creep in between development, test
and production environments.
3 Too much IT resource and budget is spent on
low-level, routine tasks
Just some of the challenges
7

8. 8
PureApplication creates a transformation

9. Simplifying the IT project
lifecycle
Transforms provisioning, speeds up application
deployment and reduces IT costs
Uses ‘Patterns’ to lock in the knowledge of
installing and configuring an entire solution
Enables you to deploy new instances of the
solution in hours not weeks
9

10. PureApplication Patterns
Building blocks which can be used
to configure the software you want
to deploy onto a hardware topology
You can create repeatable solution
infrastructure designs which can be
deployed as many times as needed
More time is available to work on
higher value solutions
10

11. 11

12. 12

13. 13
What’s in a Pattern

14. Your
Topology
Product
Suites
Software
components
The 3 Pattern
Levels
Installs &
configures a
single
product
Captures multiple
software
components into
potentially complex
suite installs
Bespoke pattern
which potentially uses
product suites &
always uses Software
Components
14

15. PATTERNS, PATTERNS EVERYWHERE
15

16. 16

17. 17

18. 18
Delivering Deployment Benefits

19. 19
CLEAR ROUTE-TO-LIVE

20. Clear-Route-To-Live: A Definition
Ensuring consistency between:
Why?
If applications haven’t been developed and tested on the same
configuration errors creep in…
20
Dev Test Prod

21. Clear-Route-To-Live: A Definition
21
Dev Test Prod
True customer story:
Bug in system took 6 months to surface and
took down complete production
environment.
Why?
Different environments between Test and
Production !

22. Route-to-Live
22A Developer uses one instance of a pattern

23. Route-to-Live
23A Tester can use the exact same pattern but adds on a test client

24. She then adds on a scaling policy for performance testing

25. A production administrator then takes the testers pattern, removes the
test client and alters the DB to point to the production DB

26. We can see how there is now a very clear route from the dev pattern to
the prod pattern

27. 27
Extending applications to Hybrid Cloud

28. Scenario 1: Clear route-to-live
28
This scenario is using the cloud for development and the on-premise for
production. But Patterns maintain the same clear-route-to-live.

29. Scenario 2: Cloud-Bursting
29
When the on-premise solution needs temporarily expanding the cloud
can be used for those peak times.

30. 30
Scenario 3: Global reach
I no longer need data centres cross the world. Softlayer has them for
me and deals with the specific data protection policies in those regions.

31. STERLING OMS & WS COMMERCE
31
PureApp and Hybrid Cloud in practice

32. KEY CHALLENGE
Deploy environments quickly, reduce the risk of errors
and deliver faster time to value
The client: Leading UK retailer
The challenge: Needed to get their
Commerce & OMS website up and
running for the Christmas period - it was
already March.
32
Didn’t have the skills and services available to meet this timeline.
Commerce & OMS projects already running
Taken 6 weeks+ to deploy new environments

35. 35
OMS + WebSphere Commerce
(a HUGE retail product suite!)

36. 36

37. 37
That’s 1000+ pages of
configuration
This is the Commerce pattern – which already saves you weeks of work.

38. Combining Commerce and OMS takes the best of both products

39. Commerce & OMS Topology
39Prior to patterns: users found commerce/OMS so complex they shared
resources between dev/test/prod because they found it so hard to build

40. 40
Icon Commerce/OMS enablement
With our pattern you can just add in a script to commerce and be up
and running!

41. KEY CHALLENGE
The need to faster deploy environments, reduce the risk
of errors and deliver faster time to value.
The results:
• Cut deploy times of Commerce/OMS
topology from
6 weeks+ to under 3 hours.
41
• Self-service development environments now an
option
• Systems can be upgraded in hours not days.

42. 42
Questions?

43. 43