Skype Manager Project

PRJ001 B2B System Technical Architecture

Version 0.1

Issued 10 March 2011

Author/Reviser John T Boyd

Amended Sections

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

Contents
1 INTRODUCTION ........................................................................................................................................ 4 1.1 1.2 1.3 2 INTENT ...................................................................................................................................................... 4 CONTENT .................................................................................................................................................. 4 OUT OF SCOPE........................................................................................................................................... 4

BACKGROUND ........................................................................................................................................... 4 2.1 PROJECT DESCRIPTION .............................................................................................................................. 4 2.2 PROJECT FUNDING: ................................................................................................................................... 4 2.3 KEY 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 (EXTERNAL SYSTEMS) .......................................................................... 6 2.9 DATA EXCHANGE: .................................................................................................................................... 7 2.9.1 Exchange Requirements ................................................................................................................ 7 2.10 ADDITIONAL STORAGE AND BACKUP REQUIREMENTS ......................................................................... 8 2.10.1 Space Requirements ....................................................................................................................... 8

TECHNICAL VISION AND STRATEGY ................................................................................................ 9 3.1 APPLIED PATTERNS ................................................................................................................................... 9 3.2 ENVIRONMENTS ........................................................................................................................................ 9 3.3 SUN JAVA SYSTEM APPLICATION SERVER (SJSAS) 8.1 ............................................................................ 9 3.4 DEPLOY AND RUN ..................................................................................................................................... 9 3.5 TECHNICAL LIFECYCLE AND STATUS ...................................................................................................... 10 3.5.1 Current Status .............................................................................................................................. 10 3.5.2 Future Packages .......................................................................................................................... 10 3.6 CURRENT STATUS AND FUTURE TIMETABLE OF THE PROJECT. ................................................................. 11 3.6.1 Current Status .............................................................................................................................. 11 3.6.2 Future Release ............................................................................................................................. 11 3.7 APPROACH AND ARCHITECTURE ............................................................................................................. 11 3.7.1 Standards and Patterns ................................................................................................................ 11 3.8 ARCHITECTURE FRAMEWORK OF PROJECT.............................................................................................. 12 3.8.1 Information Layer........................................................................................................................ 12 3.8.2 Application Layer ......................................................................................................................... 12 3.8.3 Infrastructure 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 Infrastructure Layer .................................................................................................................... 14

IMPLEMENTATION AND OPERATIONAL DETAILS...................................................................... 15 4.1 GENERAL DETAILS .................................................................................................................................. 15 4.1.1 Database Details .......................................................................................................................... 15 4.1.2 Web Hosting Details .................................................................................................................... 15

ENVIRONMENTS ..................................................................................................................................... 16 5.1 INTRODUCTION ....................................................................................................................................... 16 5.2 INTEGRATION .......................................................................................................................................... 17 5.2.1 Integration Configuration ........................................................................................................... 17 5.3 PRODUCTION ........................................................................................................................................... 17 5.3.1 Overview ....................................................................................................................................... 17 5.3.2 Production Configuration ........................................................................................................... 18 5.4 DEVELOPMENT........................................................................................................................................ 19
page 2 of

PRJ001

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

5.4.1 Overview ....................................................................................................................................... 19 5.4.2 Workstation Development Environment ..................................................................................... 20 5.5 PUBLIC INTERNET ACCESS TO SKYPE MANAGER .................................................................................... 20 5.5.1 Design Details: ............................................................................................................................. 21 5.5.2 Production View ........................................................................................................................... 22 5.5.3 Integration View .......................................................................................................................... 22 5.5.4 Authentication .............................................................................................................................. 22 5.5.5 Build ............................................................................................................................................. 22 5.5.6 Integration (QA) .......................................................................................................................... 22 5.5.7 Deployment................................................................................................................................... 22 5.5.8 Fail Over ...................................................................................................................................... 22 5.5.9 Disaster Recovery ......................................................................................................................... 23 6 CONTACTS ................................................................................................................................................ 24 6.1 6.2 7 8 TECHNICAL CONTACTS ........................................................................................................................... 24 PROJECT CONTACTS ................................................................................................................................ 24

ISSUES AND IMPERATIVES .................................................................................................................. 25 APPROVAL AND SIGNOFF .................................................................................................................... 26 8.1 8.2 ARCHITECTURE STANDARD CHECK ........................................................................................................ 26 SIGN OFF OF TECHNICAL ARCHITECTURE ............................................................................................... 26

PRJ001

page 3 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

1 INTRODUCTION
This Technical Architecture document describes the architecture and environments used to build the application, train users, execute the application in production and maintain the application from an operational perspective. The document describes the required hardware, software, packaged products, middleware, and infrastructure components such as security and notification services. 1.1 Intent This document is intended as a framework; early in the systems life cycle most of the information will 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 this document is to help other Skype B2B System architects/organizations understand the project's proposed use (reuse) of Skype B2B System standard patterns and exceptions to those architectures. 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 used as a subset of non-functional requirements which will help drive the architectural design. The remainder of the document describes the proposed architecture; including not only platform products, versions, network topology (technical architecture) but also other infrastructure services (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 architecture might include an PrePay and Post Pay Systems as well as the SecureWeb Platform.

2 BACKGROUND
Project Name: Initiative Name: Skype Manager Skype Manager

2.1 Project Description The Skype Manager System is a web based management tool for managing Skype accounts across a business of any size. It allows for the creation of accounts, the allocation of credits and features 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 following functionality: 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 an application that will meet all of their business requirements for today and in the future. The new
page 4 of

PRJ001

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

application environment should allow for any necessary enhancements to be developed quickly and 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 Current maximum number of users Lowest estimated number of concurrent users Highest estimated maximum number of concurrent users Annual Total Number of AWB's Annual Estimated Total Number of AWB updates Average Number of Daily Updates Estimated max number of daily updates Estimated min number of daily updates Percentage number of all transactions that are shipment related. No EDI or keepalive messages included. Annual estimated number of transactions Average Number of daily transactions Estimated max number of daily transactions Estimated min number of daily transactions Average hourly updates Estimated max number of hourly updates Estimated min number of hourly updates Average hourly transactions Estimated max number of hourly transactions Estimated min number of hourly transactions Average updates per second Estimated max updates per second Estimated max number of transactions per second Estimated min number of transactions per second Average Usage Information 4250 1275 2975 13,000,000 195,000,000 534,247 667,808 400,685 20 975,000,000 2,671,233 3,339,041 2,003,425 22,260 33,390 11,130 111,301 166,952 55,651 6.18 9.28 46.38 15.46

PRJ001

page 5 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

The following diagram shows the interaction between existing systems.

Availability (Critical transaction timing requirements or large volume processing windows, uptime requirements, allowable recovery time): Acceptable amount of downtime (not including maintenance): X Non-Stop __ 3 days __4 Hours __ 7 days __ 8 hours __ 14 days __ 1 day __ 30 days ? days per week

Performance Requirements (Peaks in transaction volumes/response times?): when orders are place by the Airlines 2.5 Architectural Constraints:

The system will need to use the Sita and B2B SystemLuxs mainframe infrastructure located at Skype B2B Systems Londongate and Luxembourg Data Centres. Skype Manager will interface with the existing architecture ex-Sitas and ex-B2B SystemLuxs architecture. Capacity Projections (planned increases in number of users, space requirements): Current production capacity in Skype Manager is 16 GB on the database, it s not expected that this will change in the near future. For the purpose of initial sizing of the application the figures are based upon Skype B2B System of Europe. The application itself is intended to be brand independent. 2.6 Composition of end user population Population Current maximum number of users Lowest estimated number of concurrent users Highest estimated maximum number of concurrent users 4250 1275 2975 Total

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 sizes are now possible so we need more space added to XXXX. I propose that we ask for another XX GB. Production also will require another XX GB added for extra archive log space when Skype Manager R3 is launched. Space Req Large Tablespaces Medium Tablespaces Small Tablespaces Archive Logs 2.8 Sources of data and contacts (External systems) Source Master Flight Schedules (SSIM) Flight Schedules (SSM) Flight Schedules (ASM) UCM Handling LUC Handling Platform Contact

PRJ001

page 6 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

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 will transforms all flat file messages internally into XML messages and only produce flat file messages when sending messages. We are looking to facilitate our partners move towards a Service Oriented Architecture in the future. This will also allow for more complex business process handling of the message than is presently possible.

Data for Exchange Master Flight Schedules (SSIM) Flight Schedules (SSM) Flight Schedules (ASM) UCM Handling LUC Handling SCM Handling URI/O Handling MUC Handling

External or Internal External External External External External External External External

Format (XML, EDI, etc.) Flat File Flat File Flat File Flat File Flat File Flat File Flat File Flat File

PRJ001

page 7 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

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 full sizes 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 when Skype Manager R1 is launched. Environment Dev Int Production Server Description Platform Development UAT Production Capacity

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 ex Sita and ex B2B SystemLux systems. Frequency/volume of ongoing data loads/refreshes: Data refreshes will happen on a constant ongoing basis at indeterminate frequencies. The volume expected is the 2KB 1MB range. Complete data refreshes will need to planned with application support team to ensure that the disk space on the server is sufficient and the SeeBeyond application is up and running.

PRJ001

page 8 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

3 TECHNICAL VISION AND STRATEGY

3.1 Applied Patterns Below describes Skype Manager's non-compliance with Skype B2B Systems Enterprise Architecture (EA) Standards v2006. The page numbers in brackets to the Architecture Management Document 'Guide to Enterprise Architecture Standards v2006. 3.2 Environments Development/Integration/Production - This pattern specifies that the platforms should be EA which includes as its web and application server Sun Java Web Server, SJSAS 5.0.x and Oracle 10i release 1. Skype Manager will be deployed to Skype B2B Systems EA platforms for the Release 1. The Skype B2B Systems EA Standard for Development, Integration and Production will 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 markets we have rolled out a solution involving EA web servers, Sun Java Web Server in the DMZ connecting through the firewall to the SJSAS 5.0.x instances running on EA application servers. The design is consistent with the Skype B2B Systems EA Standard v2006. 3.3 Sun Java System Application Server (SJSAS) 8.1 Application Layer/ Application Servers Consistent with Skype B2B Systems EA Standard v2006 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 Transaction Pattern for 2006, we are evaluating moving the SeeBeyond core code within SJSAS in order that we 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 these services we should use the SeeBeyond for point to point and publish subscribe messaging services. We need to confirm whether SeeBeyond requires using EJBs and our architecture and services are intended to be developed using plain old java objects (POJOs). Application Layer/ Personalization and Customization Due to the user requirements of Skype Manager 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 are aware 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 Architecture above. Technology Usage Guidelines/ High Availability - See note about High Availability Architecture above. Technology Usage Guidelines/ High Availability For extranet and public internet access, high availability 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:
PRJ001

Support Closer Relationship with Customers & Partners Cost Reduction

page 9 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

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 the functionality and architecture for the application to meet its requirements in this release and in the 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) technologies even 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 as security, transaction management, logging, etc) Improve the scalability of the application through use of a service layer to manage global transactions Along with eliminating complexity, provide common services used by different tiers of the application 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 Project Start Date Planned Infrastructure Readiness Planned Launch Date: 3.5.1 Current Status Jan 2006 Skype EA Standard Platform v2006 December 2006 Release 2 January 2007 Skype EA Standard Platform v2007 December 2007 Release 3 January 2008 Skype EA Standard Platform Not Known

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

PRJ001

page 10 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

3.6 Current status and future timetable of the project.

Field Code Changed

3.6.1

Current Status

The Project is now in the Requirements Gathering (phase 1). Subsequently we will have the Elaboration (phase 2) was completed on July 22. For the design phase we have used a use-case driven 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 different modules that are designed, and then broke out all relevant entities, processes, and boundaries and combined this with Skype B2B System Architecture Standard patterns and existing application components to design the overall application architecture and then the realization (Class Diagrams, State Diagrams, Sequence Diagrams, Collaboration Diagrams) for each relevant use case. 3.6.2 Future Release

The releases of Skype Manager program have been broken down to package level. There is currently Skype Manager Release 1 in the inception phase. It is intended that under Skype Manager, the end of Release 3 the project will have had a global rollout using service oriented architecture. This is consistent with the strategic direction of Skype B2B System for its information 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 the establishment of technology standards and patterns, and a governance process to manage them. The project will follow the Skype B2B Systems Enterprise Architecture Standard for the infrastructure in the development of Skype Manager.

PRJ001

page 11 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

3.8 Architecture Framework of Project The following table describes the functionality to be provided on various framework layers, and the 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 and architectures, and highlight exceptions to those architectures (denoted with asterisks). Refer to the above Standards and Patterns sections for additional details concerning framework standards. All applications should be based on one of the existing predefined patterns. It is strongly suggested that architecture framework components from the selected pattern be copied into this document and modified as required. 3.8.1 Information Layer Minor Layer Interoperability Service/Functionality Managed Asynchronous Messaging Point-to-Point Messaging Queue Workflow Service Interface Registry Connector Toolkit How Implemented is this Architecture / Comments SeeBeyond

Interoperability Interoperability Interoperability Interoperability 3.8.2 Application Layer Minor Layer Presentation Presentation Presentation Presentation Presentation Presentation Presentation Application Platforms Application Platforms Information Services Information Services Information Services Information Services Information Services

SeeBeyond BPEL Tool? SeeBeyond SeeBeyond

Service/Functionality Portal / Presentation Web Browser /Input Validation Terminal Emulation Content Management Email Instant Messaging Collaboration Application Server Web Server Database Server Data Warehouse Relational Engine Extract Transform and Load Reporting Business Intelligence Tools

How Implemented is this Architecture / Comments Access through Extranet/Internet Internet Explorer 6.x N/A N/A N/A ? ? Sun Java System Application Server 5.0.2 Sun Java Web Server/Sun Java Web Server Oracle 10i TBD SeeBeyond Eclipse BIRT Business Objects (Atlanta)

PRJ001

page 12 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

Information Services Information Services Information Services Application Platform Application Platform Application Development Tools Application Development Tools Application Development Tools 3.8.3 Infrastructure Layer Minor Layer Security Security Security Security Systems Management Systems Management Network Network Computing Platforms Computing Platforms

Document Management Information/ Knowledge Retrieval Data Access Services Reusable Services Workflow IDE Testing Tools Source Control, Build, Deploy

N/A N/A Hibernate JSF BPEL Eclipse + MyEclipse plugin Professional Edition Test Director CVS, Maven, Cruise Control

Service/Functionality Authentication Authorization Encryption Audit/Compliance Monitoring Software Distribution Extranet Load Balancing Windows / Servers Operating System

How Implemented is this Architecture / Comments Sun Access Manager Sun Access Manager ? ? ? Skype B2B System Build System ? ? Content Switching Manager (CSM) Solaris Solaris

3.8.4

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

PRJ001

page 13 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

3.8.5

Infrastructure Layer

PRJ001

page 14 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

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.) Development QA Production 4.1.2 URLs: URL Environment Production Integration URL Name Web Hosting Details Database Type No. of Instances 1 1 1 Amount of Storage per instance ? GB ? GB ? GB

Oracle 10i Oracle 10i Oracle 10i

Multi-tier with web, app, and DB objects: Software Requirements

Yes

Indicate the specific software products the project intends to use: _X Java _X HTML _X SOAP _X SeeBeyond _X XML _X Sun Java Web Server _X SSL __ JSP _X XSLT

_X Sun Java System Application Server

Software Name

Server Type (app, web, etc.) Application

Version

Description

PRJ001

page 15 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

5 ENVIRONMENTS
5.1 Introduction
Fusion WebService Subscriber JSP Page A View JSP Page B

HTTP

HTTP

SOAP/HTTP (WebService)

JSF Bean A

JSF Bean B

Java Server Faces

Service Facade

Model (Service) A

Model (Service) B

Model (Service Layer)

SOAP/HTTP (WebService) MQ/HTTP/SOAP

External Systems

JDBC

Oracle Persistance Layer

SeeBeyond

PRJ001

page 16 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

5.2 Integration 5.2.1 Integration Configuration

5.3 Production 5.3.1 Overview

Client
Web Browser

HTTP/HTTPS Client
Web Browser

Workstation

HTTP/HTTPS

Sun XXX Web Server

Web server

Sun XXX
HTTP/HTTPS PDA HTTP/HTTPS

Web Server
Web server

HTTP/HTTPS

HTTP/HTTPS

Java Web Server

HTTP

RFID

Java Web Server

HTTP

Sun XXX Database Server

Sun XXX Application Server

Sun Java Application Server
Web container JCA Interface Web Service Inteface

SQL Net

Oracle 10i

Application Database

SQL Net

Application Server
Web container

Web Service Interface

Sun Java Application Server

JCA Interface

SQL Net XML/MQ SOAP/HTTP

SOAP/HTTP XML/MQ

Airlines

Sun XXX
MQ SOPA/HTTP MQ Remote

SeeBeyond
XSLT MQ

Remote MQ MQ Remote MQ

Airports

Mapper
CargoLux Company HQ

CDMP
CargoLux

TPF/MVS HKG London

PRJ001

page 17 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

5.3.2

Production Configuration

PRJ001

page 18 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

5.4 Development 5.4.1 Overview

Web/Application Server box Web Server

SJSWS

HTTP

Web Container

Application Server SJSAS 8.1

SQL*NET

Application Database

Oracle 9i

PRJ001

page 19 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

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 development environment 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 described in this section. For more information about application servers, see EPIC Configuration for Production (section 8.3.2)

PRJ001

page 20 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

5.5.1

Design Details:

The purpose is to provide access to provide access via web servers that will reside in the DMZ between the public internet and Skype B2B System's Safe zone. Shown below is a diagram highlighting the new infrastructure required (shown in red). This is the diagram for our proposed final solution for connecting to the existing Skype Manager Production environment. A Content Switch fronts this with Airlines connecting via https. We will also have the same solution in place for 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

PRJ001

page 21 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

Load Balancing is consistent with existing Skype Manager platform i.e. Load Balancing via a Content Switch Fail over is consistent with existing Skype Manager platform i.e. Fail over to Londongate or to Luxembourg Backup 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 5.5.4

Integration View 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 the dealer connection domain cookie, they are redirected to the authentication server. They authenticate themselves and once authenticated, are redirected back to the Skype Manager web servers. 5.5.5 Build

The build of static content required by the JSPs on the Skype Manager EA web servers is done by using the Skype B2B System Build System. The file produced by the build for the Skype Manager web servers, web.jar will then be pushed to the Skype Manager EA web server in the DMZ via a Gateway? 5.5.6 Integration (QA)

The integration environment will have the same layout as the Production Environment. There will be one Skype Manager EA web server in the DMZ. It is accessed also via a Gateway server in case 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 Application Server plugin for Sun Java Web Server. 5.5.7 Deployment

The Skype B2B System build manager handles the deployment of static content required by the JSPs to the Skype Manager web servers. At the end of the build process, the build script launches 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 the Skype B2B System Support team. The password is only valid for 24 hours before expiring. Once the SSH session is established the build script connects to the Skype Manager EA web servers and unjars the web.jar file into the appropriate directory. Once completed, the build script closes all 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. In case 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 instances including those located in Londongate or Luxembourg. If for at any time we require to launch another instance of Sun Java System Application Server for increase loads or fail over, the plugin will automatically notice that another instance of Sun Java System Application Server is active and begin to forward traffic to it. It also has the ability to provide sticky session functionality to
PRJ001 page 22 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

ensure that a user will continue to be forwarded to the same server once their session has been started with a particular instance of Sun Java Application Server. The process of determining which instance of Sun Java System Application Server a user starts their session is done in a round robin manner. 5.5.9 Disaster Recovery

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

PRJ001

page 23 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

6 CONTACTS
6.1 Technical Contacts In the table below, provide technical contact information: Role Web Hosting Support DBA Name ? ? Skype Id ? ?

6.2 Project Contacts In the table below, provide project contact information, e.g., Business Customer, Business Analyst, Project Manager, and Lead Developer Role Lead Developer Project Manager Business Analyst Program Manager Technical Co-ordinator Jamie Fitzgerald Keith Sedge James.Fitzgerald@sita.aero Keith.Sedge@sita.aero Name Skype Id

PRJ001

page 24 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

ISSUES AND IMPERATIVES

Discuss current issues and imperatives of the project and the status of each:

Issue ID

Description

Status

PRJ001

page 25 of

26

Version 1.0

CHAMP Cargo Systems

PD-PRJ001-Documentation Standard

8 APPROVAL AND SIGNOFF

8.1 Architecture Standard Check Description Application is hosted within Skype B2B System Is this using Skype B2B System standard architecture? 8.2 Sign Off of Technical Architecture Name John Boyd Dept. Role TechArch Date Signature Comments Yes No

PRJ001

page 26 of

26

Version 1.0