Download - 4.2 BigHand Enterprise Core Product Technical Requirements

Transcript
  • 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):As for BigHand Server service

    Storage

    requirement:As for BigHand Server service

    OperatingSystem:

    Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64 bitversions supported)*

    .NET

    Framework:.NET Framework version 3.5

    Connection

    info:WCF web services, file system access, MSDTC

    Co-exist with

    other servicesYes

    Other

    information:

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

    are installed on the operating system before installing this component.Network DTC (Distributed Transaction Co-ordinator) must be enabled. The BigHand

    database host server must also have network DTC enabled.

    The device drivers for the portables must be installed to convert web submissions to

    BigHand format (if web submission is required).

    Requires a service account that is a db_owner of the BigHand database. This account

    must have read/write/delete permissions to the BigHand filestore(s).

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

    running on the same machine.

    The windows service 'Port Sharing' must be enabled and started.

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

    12/21

    ore Components

    2

    BigHand External Workflow Server

    Description

    This Windows service checks for voice files that users have sent to Speech Recognition.

    The service monitors the database to provide email notifications to users and escalate

    workflows. The service also monitors directories for Grundig LAN Docking files and files

    for the automatic import of data for practice builder and profiling.

    Component

    of:

    Speech Recognition, Email Notifications, Session Import (Profiling and Practice

    Builder), Grundig LAN Docking, Workflow Escalation

    Connects to: BigHand Services Host and BigHand Transcription Server.

    Target of: Transcription Server*

    Processor: As for BigHand Services

    Memory

    (RAM):As for BigHand Services

    Storage

    requirement:

    As for BigHand Services

    Operating

    System:

    Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64 bit

    versions supported)

    .NET

    Framework:.NET Framework version 3.0

    Connection

    info:WCF

    Co-exist

    with other

    services

    Yes

    Other

    information:

    * The service independently polls the BigHand database, taking action as necessary. It is

    not explicitly the target of any component other than the Transcription Server, which

    notifies External Workflow Server when a transcription is complete.

    BigHand recommends that the latest relevant Service Packs and Windows Updates

    are installed on the Operating System before installing this component.

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

    running on the same machine.

    This component may need to be located on a separate server if there is a high usage of

    Speech Recognition. This is because of the additional processor requirements for

    conversion of the audio files.

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

    13/21

    Core Components

    13

    Active Directory Users & Computers

    Description:

    When BigHand is integrated with Active Directory, user management is performed in

    Active Directory, and is disabled in BigHand. Users are authenticated in BigHand by

    virtue of their Windows authentication (Single sign-on).

    Component

    of: Windows Server operating system

    Connects to: Active Directory

    Target of: BigHand Active Directory Services

    Processor: N/A*

    Memory

    (RAM):N/A

    Storage

    requirement:N/A

    OperatingSystem:

    Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 (64 bitversions supported)

    .NET

    Framework:N/A

    Connection

    info:Ethernet

    Other

    information:

    * The specification of your domain controller(s) is beyond the scope of this document. A

    dedicated security group must be set up for BigHand users. This group may contain

    nested groups. Some BigHand components must run under Windows 'service

    accounts'. These accounts are created and authorised in Active Directory.

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

    14/21

    ore Components

    4

    BigHand Active Directory Services

    Description:

    BigHand Active Directory Services synchronises BigHand with Active Directory to

    simplify user management and provide 'single sign on' for users (Windows

    authentication) .

    Component

    of: BigHand core

    Connects to: BigHand Services Host

    Target of: BigHand System Administration

    Processor: N/A*

    Memory

    (RAM):N/A*

    Storage

    requirement:N/A

    OperatingSystem:

    N/A*

    .NET

    Framework:N/A*

    Connection

    info:TCP/IP

    Co-exist

    with other

    services

    Yes

    Other

    information:

    * This component should reside on the BigHand Services Host server. If the DirectoryService will synchronise users from multiple domains, the BigHand Directory Services

    should be installed on a BigHand Services Host in each domain. You will need to set up

    trust relationships. Requires a service account if you do not co-locate this service with the

    BigHand Services Host.

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

    15/21

    Core Components

    15

    BigHand System Administration

    Description: A client application for carrying out BigHand system administration tasks.

    Component

    of:BigHand core

    Connects to: BigHand Services Host

    Target of: User

    Processor: As per operating system

    Memory

    (RAM):As per operating system

    Storage

    requirement:Minimum: 100 MB; Recommended: 200 MB

    Operating

    System:Windows XP (SP2), Windows Vista, or Windows 7 (64-bit versions supported)

    .NET

    Framework:.NET Framework version 3.0

    Connection

    info:Web services connections (WCF)

    Other

    information:

    BigHand recommends that the latest relevant Service Packs and Windows Updates

    are installed on the Operating System before installing this component.

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

    16/21

    ore Components

    6

    BigHand Windows Client

    Description:The BigHand Windows Client is most commonly used for creating and transcribing

    BigHand voice files on the user's PC.

    Component

    of:BigHand core

    Connects to: BigHand Server, BigHand Services

    Target of: User

    Processor: Minimum: Pentium IV; Recommended: Core 2 duo

    Memory

    (RAM):Minimum: As per operating system requirements

    Storage

    requirement:Minimum: 100 MB; Recommended: 200 MB

    Operating

    System: Windows XP, Windows Vista, or Windows 7 (64-bit versions supported)

    .NET

    Framework:Minimum: .NET Framework version 3.0

    Connection

    info:TCP/IP. Minimum 128 kbps for VPN.

    Other

    information:

    MSI installer version 4.5 on client machines and any terminal servers that will serve the

    BigHand Windows Client.

    * .NET Framework version 3.0 is the minimum requirement.

    Soundcard required if using analogue / serial (non-USB) devices. Powered USB port

    required for USB microphone or portable recording device.

    Additional requirements for Speech Recognition support:

    Windows XP with SP2 (or later OS)

    Microsoft Word 2003, 2007, 2010, 2010x64

    Additional requirements for Word Playback Tools:

    Dragon Correction Object

    Additional requirements for Client Side Speech Recognition:

    Dragon NaturallySpeaking SDK Client Edition

    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

    17/21

    Core Components

    17

    BigHand Standalone

    Description:

    This module is installed by default with the BigHand Windows Client. A client-side

    module that simply records or plays voice files. Provides business continuity if the

    BigHand database or server components are unavailable for an extended period.

    Component

    of: BigHand core

    Connects to: N/A

    Target of: User

    Processor: As for BigHand Windows Client

    Memory

    (RAM):As for BigHand Windows Client

    Storage

    requirement:As for BigHand Windows Client

    OperatingSystem:

    As for BigHand Windows Client

    .NET

    Framework:.NET Framework version 3.0

    Connection

    info:N/A*

    Otherinformation:

    * This application does not require a network connection; however, you may wish to

    transport voice files by email or to a network share. The application shares components

    with the BigHand Windows Client and must therefore be installed alongside the BigHand

    Windows Client.

    BigHand Standalone is installed with the client, by default, but you can choose not to

    install it.

    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

    18/21

    ore Components

    8

    Terminal server (Citrix)

    Description:The BigHand Windows client application runs on the Citrix terminal server. The client is

    installed on the server and ICA plug-in users connect to the terminal server.

    Component

    of:Optional module

    Connects to: BigHand Server, BigHand Services

    Target of: BigHand thin client plug-in

    Processor: Depends on shared application environment

    Memory

    (RAM):Depends on shared application environment

    Storage

    requirement:Depends on shared application environment

    Operating

    System:

    Minimum: MetaFrame Presentation Server 4.0

    Recommended: XenApp 5 (32-bit)

    .NET

    Framework:Minimum: .NET Framework version 3.0

    Connection

    info:ICA

    Other

    information:

    Recommended additional bandwidth per active user = 40 kbps (with optimisations off).

    Note: With optimisations on the bandwidth is reduced. Additional bandwidth will be

    required for multiple users or if other applications outside of BigHand are also being used

    on the Citrix or Terminal Server.

    Minimum specification may increase if other applications outside of BigHand are alsorunning on the same machine.

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

    19/21

    Core Components

    19

    Terminal Server (Windows)

    Description:The BigHand client application runs on the Windows terminal server. The client is

    installed on the terminal server and plug-in users connect to the terminal server.

    Component

    of:Optional module

    Connects to: BigHand Server, BigHand Services

    Target of: BigHand thin client plug-in

    Processor: Depends on shared application environment

    Memory

    (RAM):Depends on shared application environment

    Storage

    requirement:Depends on shared application environment

    Operating

    System:

    Recommended: Windows Server 2003, Windows Server 2008, Windows Server 2008

    R2 (64-bit versions supported)

    .NET

    Framework:Minimum: .NET Framework version 3.0

    Connection

    info:RDP

    Other

    information:

    Recommended additional bandwidth per active user = 60 kbps (with optimisations off).

    Note: With optimisations on the bandwidth required is reduced. Additional bandwidth will

    be required for multiple users or if other applications outside of BigHand are also being

    used on the Citrix or Terminal Server.

    Minimum specification may increase if other applications outside of BigHand are alsorunning on the same machine.

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

    20/21

    ore Components

    0

    Thin client (PC)

    Description:

    In a centralised computing environment, BigHand can run on PCs acting as Citrix or

    Windows thin client terminals. The BigHand plug-in works via either protocol (ICA /

    RDP).

    Component

    of: Optional module

    Connects to: Terminal server

    Target of: User

    Processor: Minimum: Pentium IV; Recommended: Core 2 duo

    Memory

    (RAM):Minimum: 128 MB; Recommended: 256 MB

    Storage

    requirement:Minimum: 5 MB; Recommended: 10 MB

    OperatingSystem:

    Windows XP, Windows Vista, Windows 7 (64 bit versions supported*)

    .NET

    Framework:.NET Framework version 2.0

    Connection

    info:ICA / RDP

    Other

    information:

    USB, or RS232 serial port required for hardware connection (Analogue sound card

    required if using serial port device)

    Connection speed minimum: 128 kbps; recommended: 128 kbps or more Internet

    Explorer 6 or later. RDP5 or ICA32 Version 6.01 or above or ICAWEB version 6.3 orabove required.

    * 64-bit Windows Vista is not supported as a terminal services client.

    .NET Framework version 2.0 is the minimum requirement.

    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

    21/21

    Core Components

    Thin client (Terminal)

    Description:In a centralised computing environment, BigHand can run on Citrix or Windows thin

    client terminals. The BigHand plug-in works via either protocol (ICA / RDP).

    Component

    of:Optional module

    Connects to: Citrix server or Windows Terminal Server

    Target of: User

    Processor: Requirement as for Windows 7 Embedded*.

    Memory

    (RAM):

    (Flash memory) Minimum: 128 MB

    Recommended: 256 MB

    Storage

    requirement:

    Minimum: 5 MB

    Recommended: 10 MB

    Operating

    System:

    Windows XP Embedded with SP2

    Windows 7 Embedded

    .NET

    Framework:.NET Framework version 2.0

    Connection

    info:ICA or RDP

    Other

    information:

    * If using portable recorders (and DeviceSync) with terminals, BigHand recommends at

    least a 1 GHz processor because the processing power of the terminal affects

    DeviceSync speed.

    USB, or RS232 serial port required for hardware connection (Analogue sound card

    required if using serial port device)Connection speed minimum: 56 kbps; recommended: 128 kbps or more

    Internet Explorer 6 or later.

    RDP5 or ICA32 Version 6.01 or above or ICAWEB version 6.3 or above required.

    .NET Framework version 2.0 is the minimum requirement.

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

    running on the same machine.