SmartVista CI Ready and NonStop
Architectures
BPC and HP NonStop seminar
Athens, 12th October,2011
Oleg Patsiansky, Senior Solutions Architect
SmartVista CI Ready
HP and BPC Banking
Technologies consider
SmartVista NonStop
solution as a strategic
one for payments
2
SmartVista as BASE24 Upgrade Option
3
Porting Project Goals

Port SmartVista FrontEnd switching component on
HP Integrity NonStop platform

Keep NonStop version of SmartVista FrontEnd as
close as possible to common UNIX version

Use proprietary NonStop features if required

Develop source code translation procedures to keep
NonStop version up-to-date

4
Suggest a NonStop-based hardware environment
Porting Target – SmartVista FrontEnd
Interface Tier
Authorization Switch
Card & Merchant
Management
Interface Component
Integration Tier
Communication
Component
Kernel
Integration Component
Dynamic Link Interface
Communication Component
Communication
Protocol
Business Logic Tier
ATM Scenario
Builder
Card
Management
Component
Merchant
Management
Component
Authorization
Kernel
Formatters
Component
Kernel
POS
Management
Dynamic Link Interface
Formatters Component
ATM
Management
Loyalty
Formatter
Chip Cards
HSM Component
HSM
Kernel
Auth Engine Component
Specific HSM
Interface
l
Authorization
Engine Kernel
Dynamic Link Interface
MagStripe
Cards
Billing
Management
Component
Dynamic Link Interface
Card Production
Component
Authorization
Procedure
Database Tier
Database
5
Fault Tolerant Message Flow
1st stage
2nd stage
3rd stage
TCP
CROUTER
ATMint
SVFE
ATMint
ATMint
Queue
Through crouter
and tcpcomms or
x25comms
TXROUTER
TXROUTER
TXROUTER
$
NWint
ON-THEM
HSMcomms
Host Security Module
6
ON_US
HOSTint
STDAUTH
CBS
$
Prerequisites

Stateless components

Multiple instances for every process type (similar to
NonStop Server Class concept)
7

Single-threaded processes

Message prioritizing

GUI is not a critical component
NonStop Infrastructure Example
Terminals
Host connections
Users
Firewall
Firewall
Firewall
RDF replication
PRODUCTION
SITE
Ethernet
Ethernet
Hardware:
DR SITE
Ethernet
EXPAND
Catalyst
29xx29xx
Catalyst
HP Integrity NonStop NS2004
16GB RAM Per CPU
Catalyst 29xx
HP Integrity NonStop NS2002
16GB RAM Per CPU
UID
UID
INIT
INIT
1
3
5
2
1
4
3
5
2
1
4
2
1
8
3
7
2
6
1
4
6
8
3
5
8
7
2
6
1
Front End Active
Thales 8xxx 220 TPS
5
2
8
7
7
4
6
Front End Passive
Thales 8xxx 220 TPS
Thales 8xxx 220 TPS
Oracle DataGuard
Ethernet
Ethernet
Ethernet
Catalyst
29xx29xx
Catalyst
HP Integrity rx6600
4 cores 16GB RAM
UID
UID
INIT
3
5
2
INIT
2
1
8
3
7
2
5
8
7
1
4
6
1
4
6
3
5
8
3
5
8
7
2
6
1
2
1
4
7
4
6
HP FC LTO
Ready
Web Access Active
Clean
Attention
Error
Cancel Enter
HP
StorageWorks
1/8 G2 Tape
Autoloader
Previous Next
Tape Library
Back Office Active
HP Integrity NonStop NS2004
Server (Production), including:
· 4 logical CPU
· 2 cores per logical CPU
· 16GB of RAM
· 10 x 146 GB Hard Disks
·
6 x 72 GB Hard Disks
· Rack Mount Console with DVD/
ROM drive
· 1 LTO 3 Tape Drive
Catalyst 29xx
HP Integrity rx6600
4 cores 16GB RAM
1
2 HP Integrity rx6600 Servers,
including:
· 4 cores
· 16GB of RAM
· 16 x 300GB SFF Hard Disks in
RAID1
· DVD/ROM drive
Web Access
Passive
Back Office
Passive
2
HP Integrity NonStop NS2002
Server (DR), including:
· 2 logical CPU
· 2 cores per logical CPU
· 16GB of RAM
· 10 x 146 GB Hard Disks
·
6 x 72 GB Hard Disks
· Rack Mount Console with DVD/
ROM drive
· 1 LTO 3 Tape Drive
6 Cisco Catalyst 2911 K9 Routers
3 Thales 8xxx HSMs high-speed
8
Hardware Infrastructure Features

HA-enabled environment with better availability
compared to UNIX

Less hardware compared to all-UNIX environment

Expand option available for distributed database

No SAN and hardware mirroring required up to midsize requirement

9
Scalability on request
Availability Features

Uses native RDF/GoldenGate/DRnet features for
replication

Both Active-Passive and Active-Active modes ready

Expand option available for distributed database

ServerNet feature used for clustering

Remote DR/Second Production Site installation
capability
10
Target Implementation Environments
11

“Pure Switching” installations

ATM/Device Controller installations

Horizontally scaled environments

Active-Active installations with non-equal nodes

Where RTO = 0 is a must

Retention of the Nonstop platform is a priority
Project Goals Achieved

SmartVista FrontEnd ported on HP Integrity NonStop
platform

NonStop version of SmartVista FrontEnd inherits all
the functionality of UNIX version

Runs on top of proprietary layers of NonStop

Automatic procedures available for source code
translation from UNIX version

12
Suggested NonStop based hardware environment
Important To Know

Functionality (including operational) identical to common
UNIX-based solution

OSS used instead of Guardian to manage SmartVista
processes

It is possible to control the processes from Guardian as
well

Uses native NonStop TS/MP features for queues and
message priorities

13
Process types are registered as Server Classes
Benchmark Experiences





14
Two benchmarks conducted – Bangalore and Cupertino
Solution tested for compatibility on H-, G- and J-Series
platforms
Benchmarked on G- and J-Series including NonStop
BladeSystem
180TPS /2-way, 240TPS/4-way with less than 50% CPU
load
Fault tolerance tests passed - CPU shutdown while
system running
Technical Environment
Platforms
OS
IBM Power Systems
(System p, System i)
HP Proliant Systems
(ML, DL, BL … all
x86)
HP Integrity rx Systems
SUN SPARC Systems (M,
T … all x86)
Stratus ftServer
x86_64 systems
VMWare EX
HP Integrity
Nonstop
HP HPUX 11
IBM AIX 5.3, 6.1
RedHat Linux 5
SuSe Linux 11
OEL Linux 5
Sun Solaris 10
IBM I (i5/OS)
HP Nonstop OS J06
(OSS)
RDBMS
Oracle 9i, 10gR2,
11gR1, 11gR2
SQL/MX and DB2 9.7
(Cobra)
Other soft
C compiler
( GCC, CC )
Perl
Shell
Oracle Client
TACL and OSS shell
SmartVista remains an Open System application on Nonstop
15
www.bpcbt.com
Seminar
The SmartVista alternative on NonStop
16