skype manager 3 b2b -technical_architecture_v01

7/28/2019 Skype Manager 3 B2B -Technical_Architecture_v01

1/26

Skype Manager

Project

PRJ001

B2B System Technical Architecture

Version Issued Author/Reviser Amended Sections

0.1 10 March 2011 John T Boyd


2/26

CHAMP Cargo Systems PD-PRJ001-Documentation Standard

PRJ001 page 2 of 26 Version 1.0

Contents

1 INTRODUCTION ........................................................................................................................................ 4 1.1 I NTENT ...................................................................................................................................................... 4 1.2 CONTENT .................................................................................................................................................. 4 1.3 OUT OF SCOPE ........................................................................................................................................... 4

2 BACKGROUND ........................................................................................................................................... 4 2.1 PROJECT DESCRIPTION .............................................................................................................................. 4 2.2 PROJECT FUNDING : ................................................................................................................................... 4 2.3 K EY OBJECTIVES ....................................................................................................................................... 4 2.4 APPLICATION PROFILE .............................................................................................................................. 5 2.5 ARCHITECTURAL CONSTRAINTS : .............................................................................................................. 6 2.6 COMPOSITION OF END USER POPULATION .................................................................................................. 6 2.7 ESTIMATED NUMBER OF PRODUCTION TABLES AND SPACE REQUIREMENTS .............................................. 6 2.8 SOURCES OF DATA AND CONTACTS ( E XTERNAL SYSTEMS ) .......................................................................... 6 2.9 DATA EXCHANGE : .................................................................................................................................... 7

2.9.1 Ex change Requirements ................................................................................................................ 7 2.10 ADDITIONAL STORAGE AND BACKUP R EQUIREMENTS ......................................................................... 8

2.10.1 Space Requi rements ....................................................................................................................... 8

3 TECHNICAL VISION AND STRATEGY ................................................................................................ 9 3.1 APPLIED PATTERNS ................................................................................................................................... 9 3.2 E NVIRONMENTS ........................................................................................................................................ 9 3.3 SUN JAVA SYSTEM APPLICATION SERVER (SJSAS) 8.1 ............................................................................ 9 3.4 DEPLOY AND R UN ..................................................................................................................................... 9 3.5 TECHNICAL LIFECYCLE AND STATUS ...................................................................................................... 10

3.5.1 Curr ent Status .............................................................................................................................. 10 3.5.2 F utur e Packages .......................................................................................................................... 10

3.6 CURRENT STATUS AND FUTURE TIMETABLE OF THE PROJECT . ................................................................. 11 3.6.1 Curr ent Status .............................................................................................................................. 11 3.6.2 F utu re Release ............................................................................................................................. 11

3.7 APPROACH AND ARCHITECTURE ............................................................................................................. 11 3.7.1 Standards and Pattern s ................................................................................................................ 11

3.8 ARCHITECTURE FRAMEWORK OF PROJECT .............................................................................................. 12 3.8.1 I nformation L ayer ........................................................................................................................ 12 3.8.2 Application L ayer ......................................................................................................................... 12 3.8.3 I nfr astructur e Layer .................................................................................................................... 13 3.8.4 All business logic will be run under Sun Java Application Server. All interfaces will be in SeeBeyond. ................................................................................................................................................... 13 3.8.5 I nfr astructur e Layer .................................................................................................................... 14

4 IMPLEMENTATION AND OPERATIONAL DETAILS...................................................................... 15 4.1 GENERAL DETAILS .................................................................................................................................. 15

4.1.1 Database Detail s .......................................................................................................................... 15 4.1.2 Web Hosting Details .................................................................................................................... 15

5 ENVIRONMENTS ..................................................................................................................................... 16 5.1 I NTRODUCTION ....................................................................................................................................... 16 5.2 I NTEGRATION .......................................................................................................................................... 17

5.2.1 I ntegration Configuration ........................................................................................................... 17 5.3 PRODUCTION ........................................................................................................................................... 17

5.3.1 Overview ....................................................................................................................................... 17 5.3.2 Production Configur ation ........................................................................................................... 18

5.4 DEVELOPMENT ........................................................................................................................................ 19


3/26



5.4.1 Overview ....................................................................................................................................... 19 5.4.2 Workstation D evelopment Envir onment ..................................................................................... 20

5.5 PUBLIC I NTERNET ACCESS TO SKYPE MANAGER .................................................................................... 20 5.5.1 Design Details: ............................................................................................................................. 21 5.5.2 Production View ........................................................................................................................... 22 5.5.3 I ntegration View .......................................................................................................................... 22 5.5.4 Authentication .............................................................................................................................. 22 5.5.5 Build ............................................................................................................................................. 22 5.5.6 I ntegration (QA) .......................................................................................................................... 22 5.5.7 Deployment ................................................................................................................................... 22 5.5.8 F ail Over ...................................................................................................................................... 22 5.5.9 Di saster Recovery ......................................................................................................................... 23

6 CONTACTS ................................................................................................................................................ 24 6.1 TECHNICAL CONTACTS ........................................................................................................................... 24 6.2 PROJECT CONTACTS ................................................................................................................................ 24

7 ISSUES AND IMPERATIVES .................................................................................................................. 25

8 APPROVAL AND SIGNOFF .................................................................................................................... 26 8.1 ARCHITECTURE STANDARD CHECK ........................................................................................................ 26 8.2 SIGN OFF OF TECHNICAL ARCHITECTURE ............................................................................................... 26


4/26



1 INTRODUCTION This Technical Architecture document describes the architecture and environments used to buildthe application, train users, execute the application in production and maintain the applicationfrom an operational perspective. The document describes the required hardware, software,packaged products, middleware, and infrastructure components such as security and notificationservices.

1.1 Intent

This document is intended as a framework; early in the systems life cycle most of the informationwill be at a high level, while later in the life cycle, physical details may be added to the document(software versions, network details, etc. as appropriate).

Besides its purpose of describing the proposed technical architecture, another use/benefit of thisdocument is to help other Skype B2B System architects/organizations understand the project'sproposed use (reuse) of Skype B2B System standard patterns and exceptions to thosearchitectures. This will help the project (by facilitating it's alignment with supported technologies)and the company (by providing a vehicle to help manage the standards).

1.2 Content

Chapter 2 of this document comprises the Application Background; which is intended to be usedas a subset of non-functional requirements which will help drive the architectural design. Theremainder of the document describes the proposed architecture; including not only platformproducts, versions, network topology (technical architecture) but also other infrastructureservices (middleware, security service, directory service) upon which the application will be built.

1.3 Out of Scope

This document does not include diagrams/documentation of the application ("functional/process")architecture for the proposed system. A Database server is required; the technology architecturemight include an PrePay and Post Pay Systems as well as the SecureWeb Platform.

2 B ACKGROUND

Project Name: Skype Manager Initiative Name: Skype Manager

2.1 Project Description

The Skype Manager System is a web based management tool for managing Skype accountsacross a business of any size. It allows for the creation of accounts, the allocation of credits andfeatures and the tracking of expenditures across a business or department.

2.2 Project Funding:

Internal:

2.3 Key Objectives

In this initial phase, Skype Manager Release 1 (R1), we intend to provide the followingfunctionality:

Implementation of airline scheduling for all airlines.

Implementation of Unit Load Device management.

Why This Project is Important to Skype B2B System (Business Value)

Each application is currently extensively utilised throughout the Air B2B System industry however neither application could be considered to utilise new and open technologies.

The goal is to create a new application with a new technology that will provide customers with anapplication that will meet all of their business requirements for today and in the future. The new


5/26



application environment should allow for any necessary enhancements to be developed quicklyand easily and allow ultimate flexibility to SITA and its customers

2.4 Application Profile

Skype Manager is an application which will replace the existing Skype Manager.

Transaction Title Average UsageInformation

Current maximum number of users 4250Lowest estimated number of concurrent users 1275Highest estimated maximum number of concurrent users 2975Annual Total Number of AWB's 13,000,000Annual Estimated Total Number of AWB updates 195,000,000Average Number of Daily Updates 534,247Estimated max number of daily updates 667,808Estimated min number of daily updates 400,685

Percentage number of all transactions that are shipment related. No EDI or keepalive messages included.

20

Annual estimated number of transactions 975,000,000Average Number of daily transactions 2,671,233Estimated max number of daily transactions 3,339,041Estimated min number of daily transactions 2,003,425Average hourly updates 22,260Estimated max number of hourly updates 33,390Estimated min number of hourly updates 11,130

Average hourly transactions 111,301Estimated max number of hourly transactions 166,952Estimated min number of hourly transactions 55,651Average updates per second 6.18Estimated max updates per second 9.28Estimated max number of transactions per second 46.38Estimated min number of transactions per second 15.46


6/26



The following diagram shows the interaction between existing systems.

Availability (Critical transaction timing requirements or large volume processing windows, uptimerequirements, allowable recovery time):

Acceptable amount of downtime (not including maintenance):

X Non-Stop __4 Hours __ 8 hours __ 1 day

__ 3 days __ 7 days __ 14 days __ 30 days

Performance Requirements (Peaks in transaction volumes/response times?): ? days per weekwhen orders are place by the Airlines

2.5 Architectural Constraints:

The system will need to use the Sita and B2B System Luxs mainframe infrastructure located atSkype B2B System s Londongate and Luxembourg Data Centres.

Skype Manager will interface with the existing architecture ex- Sitas and ex -B2B System Luxsarchitecture.

Capacity Projections (planned increases in number of users, space requirements): Currentproduction capacity in Skype Manager is 16 GB on the database, it s not expected that this willchange in the near future.

For the purpose of initial sizing of the application the figures are based upon Skype B2B Systemof Europe. The application itself is intended to be brand independent.

2.6 Composition of end user population

Population Total

Current maximum number of users 4250Lowest estimated number of concurrent users 1275Highest estimated maximum number of concurrent users 2975

2.7 Estimated number of Production tables and space requirements

We now need to have 2 full size environments on XXXX, calculations show that only 2 full sizesare now possible so we need more space added to XXXX. I propose that we ask for another XXGB. Production also will require another XX GB added for extra archive log space when SkypeManager R3 is launched.

Space Req

Large Tablespaces

Medium Tablespaces

Small Tablespaces

Archive Logs

2.8 Sources of data and contacts ( Externa l sys tems)

Source Platform Contact

Master Flight Schedules(SSIM)

Flight Schedules (SSM)

Flight Schedules (ASM)

UCM Handling

LUC Handling


7/26



SCM Handling

URI/O Handling

MUC Handling

2.9 Data Exchange:

2.9.1 Exchange Requirements

In order to facilitate workflow and a move toward a Service Oriented Architecture (SOA), we willtransforms all flat file messages internally into XML messages and only produce flat filemessages when sending messages. We are looking to facilitate our partners move towards aService Oriented Architecture in the future. This will also allow for more complex businessprocess handling of the message than is presently possible.

Data for Exchange External or Internal Format (XML, EDI, etc.)

Master Flight Schedules(SSIM)

External Flat File

Flight Schedules (SSM) External Flat File

Flight Schedules (ASM) External Flat File

UCM Handling External Flat File

LUC Handling External Flat File

SCM Handling External Flat File

URI/O Handling External Flat File

MUC Handling External Flat File


8/26



2.10 Additional Storage and Backup Requirements

2.10.1 Space Requirements

We are now needed to have 3 full size environments on XXX, calculations show that only 2 fullsizes are now possible so we need more space added to XXX. I propose that we ask for another XX GB. Production also will require another XX GB added for extra archive log space whenSkype Manager R1 is launched.

Environment Server Description Platform Capacity

Dev Development

Int UAT

Production Production

Data backup and archival requirements:

The data backup requires a hot backup implementation to support a 24 by 7 application. Archival requirements are being identified consistent with Skype B2B System requirements.

(One-time) Data conversion requirements:

There will be one time data conversion requirements due to data that presently exists on exSita and ex B2B SystemLux systems.

Frequency/volume of ongoing data loads/refreshes:

Data refreshes will happen on a constant ongoing basis at indeterminate frequencies. Thevolume expected is the 2KB 1MB range. Complete data refreshes will need to plannedwith application support team to ensure that the disk space on the server is sufficient andthe SeeBeyond application is up and running.


9/26



3 T ECHNICAL VISION AND S TRATEGY 3.1 Applied Patterns

Below describes Skype Manager's non-compliance with Skype B2B System s Enterprise Architecture (EA) Standards v2006. The page numbers in brackets to the ArchitectureManagement Document 'Guide to Enterprise Architecture Standards v200 6.

3.2 Environments

Development/Integration/Production - This pattern specifies that the platforms should be EAwhich includes as its web and application server Sun Java Web Server, SJSAS 5.0.x and Oracle10i release 1. Skype Manager will be deployed to Skype B2B System s EA platforms for theRelease 1. The Skype B2B System s EA Standard for Development, Integration and Productionwill be used in order to better manage and anticipate the cost of development, deployment,migration and support going forward.

Public Internet Access In order to provide public internet access to Airlines in various marketswe have rolled out a solution involving EA web servers, Sun Java Web Server in the DMZconnecting through the firewall to the SJSAS 5.0.x instances running on EA application servers.The design is consistent with the Skype B2B System s EA Standard v2006 .

3.3 Sun Java System Application Server (SJSAS) 8.1

Application Layer/ Application Servers Consistent with Skype B2B System s EA Standardv2006 we will be using Sun Java System Application Server version 8.1.

Application Layer/ Reusable Services We are using SeeBeyond and will continue using it for Skype Manager Release 3 Package 2. In the interest of being as compliant with the TransactionPattern for 2006, we are evaluating moving the SeeBeyond core code within SJSAS in order thatwe don't have any java code running outside of SJSAS's jvm. Beyond these measures, we prefer that any major migration be towards the Information Bus architecture when it is available.

Application Layer/ Managed Asynchronous Messaging The pattern indicates that for theseservices we should use the SeeBeyond for point to point and publish subscribe messagingservices. We need to confirm whether SeeBeyond requires using EJBs and our architecture andservices are intended to be developed using plain old java objects (POJOs).

Application Layer/ Personalization and Customization Due to the user requirements of SkypeManager in different brand market combinations we are obliged to develop a customization layer around extensions to Tiles and Java Server Faces. We intend to use portal functionality in order to facilitate customisation of the user interface.

Application Layer/ Information Services It is stated in the pattern, that for Reporting we areaware that there is a Skype B2B System Standard tool, Oracle Reports, for reporting. As our requirements expand beyond a simple query of a database table, we will move to that tool.

3.4 Deploy and Run

Infrastructure Layer/ Point-to-Point Message Broker SeeBeyond

Technology Usage Guidelines/ Load Balancing - See note about High Availability Architectureabove.

Technology Usage Guidelines/ High Availability - See note about High Availability Architectureabove.

Technology Usage Guidelines/ High Availability For extranet and public internet access, highavailability support is provided via Skype B2B System Support.

It should be noted that all business logic, including any scheduled processing, will be run under SJSAS.

The vision and strategy of Skype Manager are highlighted below:

Support Closer Relationship with Customers & Partners

Cost Reduction


10/26



Introduction of New Product and Services

Exploit New Business Opportunities

Shorter Time to Market

In addition to this we have identified areas that need to be addressed in order to provide thefunctionality and architecture for the application to meet its requirements in this release and inthe future. These areas are:

Profiling and Customization of the web site by user role and brand.

Rule based client side validation to improve the performance and manageability.

Rule based server side validation to improve the performance and manageability.

Rich web application interface via Asynchronous Javascript + XML (AJAX) technologieseven in low bandwidth markets.

Improve the scalability, performance and manageability for Enterprise Integration Architecture using the message broker SeeBeyond.

Improve the overall manageability of the application by applying Object Oriented Design

principles including GOF Patterns.Eliminate the increased complexity of the application by layering services (such assecurity, transaction management, logging, etc)

Improve the scalability of the application through use of a service layer to manage globaltransactions

Along with eliminating complexity, provide common services used by different tiers of theapplication so that it is easy to test and promotes re-use.

Improve the extensibility of the application for future evolution.

3.5 Technical Lifecycle and Status

Release 1 Release 2 Release 3

Project Start Date Jan 2006 January 2007 January 2008

PlannedInfrastructureReadiness

Skype EAStandard Platformv2006

Skype EAStandard Platformv2007

Skype EAStandardPlatform

Planned LaunchDate:

December 2006 December 2007 Not Known

3.5.1 Current Status

Inception phase for Release 1

3.5.2 Future Packages

Replace of existing ex-Sita and ex-Skype B2B System systems as part of the Skype Manager application rollout


11/26



3.6 Current status and future timetable of the project.

3.6.1 Current Status

The Project is now in the Requirements Gathering (phase 1). Subsequently we will have theElaboration (phase 2) was completed on July 22. For the design phase we have used a use-casedriven UML based approach where we have transformed the scenarios into use-cases,associated the use cases with the requirements, developed a use case model for the differentmodules that are designed, and then broke out all relevant entities, processes, and boundaries

and combined this with Skype B2B System Architecture Standard patterns and existingapplication components to design the overall application architecture and then the realization(Class Diagrams, State Diagrams, Sequence Diagrams, Collaboration Diagrams) for eachrelevant use case.

3.6.2 Future Release

The releases of Skype Manager program have been broken down to package level. There iscurrently Skype Manager Release 1 in the inception phase. It is intended that under SkypeManager, the end of Release 3 the project will have had a global rollout using service orientedarchitecture. This is consistent with the strategic direction of Skype B2B System for itsinformation architecture.

3.7 Approach and Architecture

3.7.1 Standards and Patterns

Skype B2B System IT is driving to an increasingly disciplined approach in the application of technology to the customer's business solution needs. This discipline is founded on theestablishment of technology standards and patterns, and a governance process to managethem.

The project will follow the Skype B2B System s Enterprise Architecture Standard for theinfrastructure in the development of Skype Manager.

Field Code Changed


12/26



3.8 Architecture Framework of Project

The following table describes the functionality to be provided on various framework layers, andthe components that will be used to provide the required functionality. It should provide a basis

for understanding how the application maps to Skype B2B System "standard" products andarchitectures, and highlight exceptions to those architectures (denoted with asterisks). Refer tothe above Standards and Patterns sections for additional details concerning frameworkstandards. All applications should be based on one of the existing predefined patterns. It isstrongly suggested that architecture framework components from the selected pattern be copiedinto this document and modified as required.

3.8.1 Information Layer

Minor Layer Service/Functionality How Implemented is this Architecture / Comments

Interoperability Managed AsynchronousMessaging

SeeBeyond

Interoperability Point-to-PointMessaging Queue

SeeBeyond

Interoperability Workflow BPEL Tool?

Interoperability Service InterfaceRegistry

SeeBeyond

Interoperability Connector Toolkit SeeBeyond

3.8.2 Application Layer


Presentation Portal / Presentation Access throughExtranet/Internet

Presentation Web Browser /InputValidation

Internet Explorer 6.x

Presentation Terminal Emulation N/A

Presentation Content Management N/A

Presentation Email N/A

Presentation Instant Messaging ?

Presentation Collaboration ?

Application Platforms Application Server Sun Java System ApplicationServer 5.0.2

Application Platforms Web Server Sun Java Web Server/SunJava Web Server

Information Services Database Server Oracle 10i

Information Services Data WarehouseRelational Engine

TBD

Information Services Extract Transform andLoad

SeeBeyond

Information Services Reporting Eclipse BIRT

Information Services Business IntelligenceTools

Business Objects (Atlanta)


13/26



Information Services DocumentManagement

N/A

Information Services Information/

Knowledge Retrieval

N/A

Information Services Data Access Services Hibernate

Application Platform Reusable Services JSF

Application Platform Workflow BPEL

Application DevelopmentTools

IDE Eclipse + MyEclipse pluginProfessional Edition


Testing Tools Test Director


Source Control, Build,Deploy

CVS, Maven, Cruise Control

3.8.3 Infrastructure Layer


Security Authentication Sun Access Manager

Security Authorization Sun Access Manager

Security Encryption ?

Security Audit/Compliance ?

Systems Management Monitoring ?

Systems Management Software Distribution Skype B2B System BuildSystem

Network Extranet ?

Network Load Balancing ? Content Switching Manager (CSM)

Computing Platforms Windows / Servers Solaris

Computing Platforms Operating System Solaris

3.8.4 All business logic will be run under Sun Java Application Server. All interfaces willbe in SeeBeyond.


14/26



3.8.5 Infrastructure Layer


15/26



4 IMPLEMENTATION AND OPERATIONAL DETAILS 4.1 General Details

Skype B2B System Classification:Disaster recovery classification:

4.1.1 Database Details

Environment (Development,QA, Production, etc.)

Database Type No. of Instances

Amount of Storage per instance

Development Oracle 10i 1 ? GB

QA Oracle 10i 1 ? GB

Production Oracle 10i 1 ? GB

4.1.2 Web Hosting Details

URLs:

URL Environment URL Name

Production

Integration

Multi-tier with web, app, and DB objects: Yes

Software Requirements

Indicate the specific software products the project intends to use:

_X Java _X SeeBeyond _X Sun Java Web Server __ JSP

_X HTML _X XML _X SSL _X XSLT

_X SOAP _X Sun Java System Application Server

Software Name Server Type(app, web, etc.)

Version Description

Application


16/26



5 E NVIRONMENTS 5.1 Introduction

Model (Service Layer)

Model (Service) A

Model (Service)B

Persistance Layer

Oracle SeeBeyond

External Systems

View

J SP Pa ge A J SP Pa ge B

Java Server Faces

J SF Be an A J SF Be an B

SOAP/HTTP(WebService)

JDBCMQ/HTTP/SOAP

Service Facade

FusionWebServiceSubscriber

SOAP/HTTP(WebService)

HTTP HTTP


17/26



5.2 Integration

5.2.1 Integration Configuration

5.3 Production

5.3.1 Overview

Web Server

HTTP

Sun XXX

Sun XXX

Web Server

ApplicationServer

HTTP

Sun XXX

TPF/MVS

SeeBeyond

MQ

MQ

MQ

Web serverWeb server

Webcontainer

Java WebServer

Java WebServer

Sun Java Application Server

SQL Net

Remote

Remote

XSLT

JCAInterface

AirlinesXML/MQ

Database Server

ApplicationDatabase

Oracle10i

Remote

SQL Net

MQ

Web ServiceInterface

CDMP

MQ

SQL Net

MQ

Company HQ

HKG

Airports

Sun XXX

XML/MQSOAP/HTTP

SOAP/HTTP

SOPA/HTTP

Client

Workstation

WebBrowser

ApplicationServer

Sun Java Application

Server

Sun XXX

Webcontainer

JCAInterface

WebServiceInteface

HTTP/HTTPSHTTP/HTTPS

London

Mapper

CargoLux

CargoLux

ClientWeb

Browser

PDA

RFID

HTTP/HTTPS

HTTP/HTTPS

HTTP/HTTPS

HTTP/HTTPS


18/26



5.3.2 Production Configuration


19/26



5.4 Development

5.4.1 Overview

Web/Application Server box

Web Server

WebContainer

ApplicationDatabase

SQL*NET

HTTP

SJSWS

SJSAS 8.1

ApplicationServer

Oracle 9i


20/26



5.4.2 Workstation Development Environment

The Skype Manager application is making use of Eclipse and MyEclipse for development.MyEclipse provides the design environment for the system; Eclipse provides a developmentenvironment on the PC. MyEclipse has built-in web and links with an application server for deploying and testing of functionality.

5.5 Public Internet Access to Skype Manager

VCC Airlines access Skype Manager via the public internet in remote markets. This is describedin this section. For more information about application servers, see EPIC Configuration for Production (section 8.3.2)


21/26



5.5.1 Design Details:

The purpose is to provide access to provide access via web servers that will reside in the DMZbetween the public internet and Skype B2B System's Safe zone. Shown below is a diagramhighlighting the new infrastructure required (shown in red). This is the diagram for our proposedfinal solution for connecting to the existing Skype Manager Production environment. A ContentSwitch fronts this with Airlines connecting via https. We will also have the same solution in placefor our QA environment.

Instance Details:

Sun Box running Solaris

1.5 GHz CPU

1GB RAM

36 GB External storage for OS and Application (Sun Java Web Server)

https connectivity, requiring X.509 certificates


22/26



Load Balancing is consistent with existing Skype Manager platform i.e. Load Balancingvia a Content Switch

Fail over is consistent with existing Skype Manager platform i.e. Fail over to

Londongate or to LuxembourgBackup will be required as static content Build, Deploy and Monitor Tool

Sun Java System Application Server plug-in connecting over 62040 (http: SOAP)

Deployment of static web content (web.jar) file Build, Deploy and Monitor Tool

5.5.2 Production View

5.5.3 Integration View

5.5.4 Authentication

Authentication is done via XXXX. The Skype Manager web servers and content switches are part

of the dealer connection domain. When a user first tries to access the URL, if they don't have thedealer connection domain cookie, they are redirected to the authentication server. Theyauthenticate themselves and once authenticated, are redirected back to the Skype Manager webservers.

5.5.5 Build

The build of static content required by the JSPs on the Skype Manager EA web servers is doneby using the Skype B2B System Build System. The file produced by the build for the SkypeManager web servers, web.jar will then be pushed to the Skype Manager EA web server in theDMZ via a Gateway?

5.5.6 Integration (QA)

The integration environment will have the same layout as the Production Environment. There willbe one Skype Manager EA web server in the DMZ. It is accessed also via a Gateway server incase of deployment and the web server in the DMZ will link back with the two application servers

(Sun Java System Application Server on EPIC) in QA via the Sun Java System ApplicationServer plugin for Sun Java Web Server.

5.5.7 Deployment

The Skype B2B System build manager handles the deployment of static content required by theJSPs to the Skype Manager web servers. At the end of the build process, the build scriptlaunches a SSH to a Gateway Server in the SafeZone that gives access to the Skype Manager EA web servers. The build manager will need to enter a temporary password provided by theSkype B2B System Support team. The password is only valid for 24 hours before expiring. Oncethe SSH session is established the build script connects to the Skype Manager EA web serversand unjars the web.jar file into the appropriate directory. Once completed, the build script closesall connections and exits.

5.5.8 Fail Over

In the case of fail over of one of the Skype Manager EA web servers, the Content Switch will

direct traffic to the other Skype Manager web server in either Londongate or Luxembourg. Incase of fail over on the Sun Java Application Server, the Sun Java System Application Server plugin for Sun Java Web Server (SJWS) will note that the particular instance of Sun Java System

Application Server is no longer active and route traffic to another instance of Sun Java System Application Server that is active. We will configure the Sun Java System Application Server plugin for SJWS will the IP addresses for all the Sun Java System Application Server instancesincluding those located in Londongate or Luxembourg. If for at any time we require to launchanother instance of Sun Java System Application Server for increase loads or fail over, the pluginwill automatically notice that another instance of Sun Java System Application Server is activeand begin to forward traffic to it. It also has the ability to provide sticky session functionality to


23/26



ensure that a user will continue to be forwarded to the same server once their session has beenstarted with a particular instance of Sun Java Application Server. The process of determiningwhich instance of Sun Java System Application Server a user starts their session is done in around robin manner.

5.5.9 Disaster Recovery

The disaster recovery for the Skype Manager EA web servers are handled automatically via theContent Switches. The Content Switches have a communications link between them to ensurethat they are active. In a disaster, if the Londongate or Luxembourg Content Switches areknocked offline, traffic would automatically be redirected to the Londongate or LuxembourgContent Switches that would forward traffic to the Skype Manager EA web servers located inLondongate or Luxembourg. The Skype B2B System Disaster recovery plan still applies inrelation to all the EA elements of the Skype Manager architecture. This means that the web andapplication servers are started manually in Londongate or Luxembourg.


24/26



6 C ONTACTS 6.1 Technical Contacts

In the table below, provide technical contact information:Role Name Skype Id

Web Hosting Support ? ?

DBA ? ?

6.2 Project Contacts

In the table below, provide project contact information, e.g., Business Customer, Business Analyst, Project Manager, and Lead Developer

Role Name Skype Id

Lead Developer

Project Manager Jamie Fitzgerald [email protected] Analyst Keith Sedge [email protected]

Program Manager

Technical Co-ordinator


25/26



7 ISSUES AND IMPERATIVES Discuss current issues and imperatives of the project and the status of each:

Issue ID Description Status


26/26



8 A PPROVAL AND S IGNOFF 8.1 Architecture Standard Check

Description Yes No Application is hosted within Skype B2B System

Is this using Skype B2B System standard architecture?

8.2 Sign Off of Technical Architecture

Name Dept. Role Date Signature Comments

John Boyd TechArch

skype manager 3 b2b -technical_architecture_v01

Documents