SX.enterprise Architecture & Deployment

Session #24

Duc Chu & Perry Jager

Session Overview

• SX.e & Progress software architecture

• Computer (Servers and PC) communications & layouts

• Network considerations• Topology alternatives

“Good Old” UNIX Days

• Trend 8, SX 2.x, & Progress v8

• Single database data-store

• All database processes on one UNIX system

• All user processes on one systemUNIX Server

SharedMemory

Database

ASCII DumbTerminal

ASCII DumbTerminal

ASCII DumbTerminal

DatabaseServer

UNIX (Full) Client/Server

• Large user configurations

• Single database data-store

• CHUI clients on application-store

• Separate LAN for data traffic

UNIX Data Store

Database

UNIX Application Store

ASCII DumbTerminal

ASCII DumbTerminal

ASCII DumbTerminal

ProgressCharacter

Client

SharedMemory

DatabaseServer

Switch

SX 3.X and Progress 9

• SX 3.x requires 9.1– 9.1B currently– 9.1D soon

• Progress 9.1B requires Java 1.1.8 – Java 1.1.7 on HP & Unixware– Java 1.1.7 on DG

• Progress 9.1D will require Java 1.3

SX 3.X and Progress 9

• Java require specific OS levels• Progress 9 features

– Performance enhancements– Large file enabled (>2GB)– Single db with Storage Areas– Administration enhancements– New networking requirements– Slightly more overhead

SX.e 3.XDatabase Server

• Progress Database Server

• Progress Application Server

• Progress Admin Server

• Progress Name Server

UNIX Server

SharedMemory

DatabaseAdminServer

NameServer

Appserver

DatabaseServer

SX.e Staging Server

UNIX Server

SharedMemory

DatabaseAdminServer

NameServer

Appserver

DatabaseServer

SX.e Staging Server

CompiledCode

Bundle

• GUI code compile• Centralized Client

install mechanism• Centralized Client

update mechanism• Code Test

mechanism• AppServer Library

SX.e GUI Clients

• Full Push Client• Full Progress install• Full SX code install

• Code Server• Full Progress install• Full SX code install• Code Bundle

• Network Client• Little Progress code• No SX code

UNIX Server

SharedMemory

DatabaseAdminServer

NameServer

Appserver

DatabaseServer

Full Push PC

Code Server

SX.e Staging Server

CompiledCode

Bundle

Terminal Server

SX Network Client

SX Network Client

SX.e Client considerations

• Full Push Client• Independent• High bandwidth

update• Higher Admin

overhead• Recommended for

all Terminal Server installsUNIX Server

SharedMemory

DatabaseAdminServer

NameServer

Appserver

DatabaseServer

Full Push PC

Terminal Server

SX.e Client considerations

UNIX Server

SharedMemory

DatabaseAdminServer

NameServer

Appserver

DatabaseServer

Code Server

SX Network Client

SX Network Client

• Code Server• Independent• Fewer high

bandwidth updates• Less admin

overhead

• Network Client• Dependent on

Code Server• No updates• Little Admin

overhead

Network Hardware

• Hubs/Switches• Routers/Firewalls• CSU/DSU Devices• Domain Server• Mail Server• Print Server• Terminal Server

Network Hardware - Branch

• Hubs/Switches• Routers/Firewalls• CSU/DSU Devices• Backup Domain

Server (optional)• Code Server

(depending on configuration)

SX.e Thin Clients

• Windows Terminal Server– Full Push Client– Host based model– Virtual Computers

for multiple users– No extended

deployment issues

WAN

SX.e Thin Clients

• Windows Terminal Server and Citrix– Runs directly on

the Terminal Server

– Improves WAN performance with ICA Protocol

– Web based access– ICA Client access

WAN

SX.e Thin Clients

• Windows Terminal Server and Tarantella– Web based access– Tarantella Client– Java client

required on client PC

– Separate Tarantella Server

WAN

Other SX.e Clients

• ODBC– SX.intelligence– SX2G0

• FTP– Clippership– RXLaser

Other SX.e Clients

• Webspeed/ Appserver– Esales– Ecatalog

• Sonic MQ/XQ– Commerce

Connect

Networking Considerations

• DNS – Internal DNS

Required– Reverse lookups– Dynamic DNS

issues (DHCP)– DNS forward

lookups

Special Considerations

• TWL– Separate

Database– Shared Admin &

Name Server– Separate

Appservers

Test Environments

• Test Company– Same files on disk– Access to other

company data

• Test Environment– Full copy of files

on disk– Snapshot in time

Support Architecture

• Points of access– UNIX– Windows

• Staging Server • Code Server• Client

• Network access– Telnet– FTP– PCAnywhere– Dial up

Internet

Support Architecture

• Points of access– UNIX– Windows

• Staging Server • Code Server• Client

• Network access– Telnet– FTP– PCAnywhere– Dial up

Internet

Questions?PLEASE, don’t forget to fill out the survey sheet.

SX.e Architecture & Deployment

Session #24

Thank you!

PLEASE, don’t forget to fill out the survey sheet.

SX.e Architecture & Deployment

Session #24

Thank you!