4.2 BigHand Enterprise Core Product Technical Requirements

download 4.2 BigHand Enterprise Core Product Technical Requirements

of 21

  • date post

    04-Apr-2018
  • Category

    Documents

  • view

    214
  • download

    0

Embed Size (px)

Transcript of 4.2 BigHand Enterprise Core Product Technical Requirements

  • 7/31/2019 4.2 BigHand Enterprise Core Product Technical Requirements

    1/21

    B IG H A N D C O R E P R O D U C T T E CH N IC AL R E Q U IR E M E N T S

    BIGHANDENTERPRISE

    Software version: 4.2

    Last edited date: 26 October 2011

  • 7/31/2019 4.2 BigHand Enterprise Core Product Technical Requirements

    2/21

    ontents

    Contents

    Contents 2

    BigHand Core Topology 3

    Introduction 3

    Centralised Computing Environment 4

    Distributed 5

    Hybrid 6

    Core Components 7

    BigHand Database 8

    BigHand Workflow Server 9

    Filestore(s) 10

    BigHand Services Host 11

    BigHand External Workflow Server 12

    Active Directory Users & Computers 13

    BigHand Active Directory Services 14

    BigHand System Administration 15

    BigHand Windows Client 16

    BigHand Standalone 17

    Terminal server (Citrix) 18

    TerminalServer (Windows) 19

    Thin client (PC) 20

    Thin client (Terminal) 21

  • 7/31/2019 4.2 BigHand Enterprise Core Product Technical Requirements

    3/21

    BigHandCore Topology

    3

    BigHand Core Topology

    Introduction

    BigHand is a future-proof technology which can be implemented in a variety of ways, allowing the

    application to remain flexible to your organisation's requirements. The implementation scenarios are:

    1) Centralised

    2) Distributed

    3) Hybrid

    Components can be installed on the same physical / virtual server or on separate servers with the

    exception of BigHand Telephony and Speech Recognition.

  • 7/31/2019 4.2 BigHand Enterprise Core Product Technical Requirements

    4/21

    4

    Centralised Computing Environment

    BigHand can be implemented in a centralised environment where all server components are located

    in a main site or data centre while client connections are made over the LAN/WAN.

    The above diagram represents an implementation based on centralised server side components. The

    main server hosts the global master database, which stores all voice file metadata. The voice files are

    not stored in the database - to ensure optimum database performance - but in a separate filestore.

    All the server side software is hosted in the main site, with clients connecting to the server(s) via LAN,

    WAN and VPN.

  • 7/31/2019 4.2 BigHand Enterprise Core Product Technical Requirements

    5/21

    5

    Distributed

    BigHand can be implemented in a distributed environment where BigHand services and filestores are

    installed in each geographic site to support the users within each location.

    The above diagram represents an implementation based on more autonomous offices, having their

    own server side components. The master database is still located in the main site, but each site hosts

    its own BigHand services and filestore.

    The BigHand services in each site refers to the master database to store and retrieve voice file

    metadata. The servers store files locally to reduce WAN traffic, but the central database keeps track

    of where all the systems files are located, allowing work to be shared.

    This model lends itself to sites with greater autonomy, and assumes that a large share of the voice file

    created in a site will be transcribed in the same site. The majority of this models WAN traffic is

    metadata, and most file transfer is confined to the site LANs.

  • 7/31/2019 4.2 BigHand Enterprise Core Product Technical Requirements

    6/21

    6

    Hybrid

    Alternatively BigHand can be implemented in a hybrid environment where you have a mix of both

    centralised and distributed, with large remote sites being supported by their own BigHand services

    and filestores whilst smaller satellite sites/offices connect to BigHand using Terminal Server

    (Citrix/Terminal Services).

    Users connect to their local server through LAN, WAN, VPN or Terminal Server, making use of

    potentially better network links within the regions. This limits the amount of bandwidth used by

    BigHand on network links, assuming voice files rarely move between regions.

  • 7/31/2019 4.2 BigHand Enterprise Core Product Technical Requirements

    7/21

    Core Components

    7

    Core Components

    BigHand is based on three-tier, service-oriented architecture with the following core components:

    l BigHand Database

    l BigHand Workflow Server

    l BigHand Filestore

    l BigHand Services Host

    l BigHand External Workflow Server

    l BigHand System Administration

    l BigHand Windows Client

    l Terminal Server

    l Terminal Client

    The technical requirements for each core component is detailed in the following sections.

  • 7/31/2019 4.2 BigHand Enterprise Core Product Technical Requirements

    8/21

    ore Components

    BigHand Database

    Description:The BigHand database stores records of all the voice files submitted to BigHand, such

    as the author, workflow destination and user data, as well as the system configuration.

    Component

    of:BigHand core

    Connects to: None

    Target of: BigHand Server, BigHand Services

    Processor:Minimum: Pentium IV

    Recommended: Dual Xeon 3.6GHz 800MHz FSB or higher

    Memory

    (RAM):

    Minimum: 1 GB

    Recommended: 2 GB

    Storage

    requirement:

    Minimum: 1 GB

    Recommended: 4 GB

    Operating

    System*:

    Minimum: Windows Server 2003Recommended: Windows Server 2008, Windows Server 2008 R2 (64-bit versions

    supported)

    .NET

    Framework:Not required

    Connection

    info:TCP/IP Ethernet. Recommended: 1 Gbps

    Co-exist with

    other

    services

    Yes

    Other

    information:

    Minimum database platform: MSDE 2000 or MSSQL Server Express Edition with latest

    service patches.

    Recommended database platform: MSSQL Server 2005 or MSSQL Server 2008 with

    latest service packs.

    * BigHand recommends that the latest relevant Service Packs and Windows Updates

    are installed on the Operating System before installing this component.

    Recommended: 10/100/1000 Mbps

    Network DTC must be enabled on the database server.

    Memory is dependent on the size of the database.

  • 7/31/2019 4.2 BigHand Enterprise Core Product Technical Requirements

    9/21

    Core Components

    9

    BigHand Workflow Server

    Description:A Windows service that manages file transfer and database updates on behalf of the

    applications that it serves.

    Component

    of:BigHand core

    Connects to: Database, filestore(s).

    Target of: BigHand Windows Client, Telephony, Outsourcing module.

    Processor:Minimum: Pentium IV

    Recommended: Dual Xeon 3.6GHz 800MHz FSB or higher

    Memory

    (RAM):

    Minimum: 1 GB

    Recommended: 2 GB

    Storage

    requirement:Minimum: 200 MB*

    Operating

    System:

    Minimum: Windows Server 2003Recommended: Windows Server 2003, Windows Server 2008, or Windows Server

    2008 R2 (64-bit versions supported)

    .NET

    Framework:Minimum: .NET Framework version 2.0.

    Connection

    info:

    TCP/IP Ethernet. Client TCP port range 5114-5118, connects to SQL Server on

    TCP 1433. Recommended Ethernet connection speed: 1 Gbps

    Other

    information:

    * For application purposes (see filestore for storage requirements)

    BigHand recommends that the latest relevant Service Packs and Windows Updates

    are installed on the Operating System before installing this component.In a distributed environment, it requires a service account that is a db_owner of the

    BigHand database, and has read/write/delete permissions to the filestore(s).

    Minimum specification may increase if other applications outside of BigHand are also

    running on the same machine.

  • 7/31/2019 4.2 BigHand Enterprise Core Product Technical Requirements

    10/21

    ore Components

    0

    Filestore(s)

    Description:

    The BigHand system uses one or more filestores to keep voice files. Often the filestores

    are co-located with BigHand Server services. The filestores must be accessible, for read

    / write / delete operations, by all BigHand Server services and all BigHand Services Host

    services, to enable multi-site work sharing.

    Component

    of:BigHand core

    Connects to: None

    Target of: BigHand Server services, BigHand Services

    Processor: N/A

    Memory

    (RAM):N/A

    Storage

    requirement:

    Approx 1.4 MB per 10 minutes of recording

    Operating

    System:N/A

    .NET

    Framework:N/A

    Connection

    info:TCP/IP

    Otherinformation:

    Must be shared with the service accounts that run BigHand Server and BigHand

    Services.

    Storage requirement (MB) = 7 x 0.14 x number of users x avg. recording duration peruser per day (minutes)

    (Approx. 0.14 MB per minute - with GSM codec) (7 days default time to store completed

    voice files)

  • 7/31/2019 4.2 BigHand Enterprise Core Product Technical Requirements

    11/21

    Core Components

    11

    BigHand Services Host

    Description:A Windows service that hosts a collection of WCF web services enabling

    communication between BigHand software components and the BigHand database.

    Component

    of:BigHand core

    Connects to: Database, filestore(s)

    Target of:System Administration, BigHand Windows Client, Web Client, BigHand Active

    Directory Services, BigHand Gateway, External Workflow Server, Security Faade

    Processor: As for BigHand Server service

    Memory

    (RAM):