Export (0) Print
Expand All

Setting Up Digital Broadcast Manager

Published: February 01, 2000

Microsoft Digital Media Division

On This Page

Abstract Abstract
Introduction Introduction
Setting up the Digital Broadcast Manager system Setting up the Digital Broadcast Manager system
For more information For more information

Abstract

Microsoft® Digital Broadcast Manager for Windows Media™ is a complete solution for creating a pay-per-view Web site built around Microsoft Windows Media Technologies. This document guides you through the process of setting up a Digital Broadcast Manager system from scratch: it shows you what hardware and software is required and how to set up and install all the pieces. No programming experience is required, just a basic knowledge of the Microsoft Windows NT® operating system, databases, and networking.

Introduction

Microsoft® Digital Broadcast Manager for Windows Media™ combines Windows Media Technologies with Microsoft Site Server, Commerce Edition and Microsoft SQL Server™ to create an end-to-end commerce solution for creating and selling media content on the Internet. Digital Broadcast Manager provides a simple way for you to develop pay-per-view solutions for live events and recorded streams and pay-per-download solutions for downloadable media content.

This document lists the hardware and software requirements and shows you how to set up and configure the three types of servers that you will use to deploy your pay-per-view or pay-per-download solution. It is important that you follow the procedures exactly and in the sequence given.

This document contains the following topics:

  • Setting up the Digital Broadcast Manager system. Provides an overview and diagram of the system.

    • Digital Broadcast Manager hardware requirements. Lists the recommended minimum hardware specifications of the three servers.

    • Digital Broadcast Manager software requirements. Lists the software required to run Digital Broadcast Manager, and shows you how to install and configure it.

    • Installing Digital Broadcast Manager. Shows you how to install the Digital Broadcast Manager software.

    • Installing the credit card software. Shows you how to install the third party credit card processing software.

  • For more information.

Setting up the Digital Broadcast Manager system

A Digital Broadcast Manager system requires three servers: a server running Microsoft SQL Server version 7.0, a Web server with Microsoft Site Server version 3.0, and a server running Microsoft Windows Media Services version 4.1. In addition, Windows Media Encoder is required for live events. The following illustration shows the Digital Broadcast Manager system architecture for a three-server configuration.

You can create a Digital Broadcast Manager system with multiple Windows Media servers and/or Web servers. For more information, see the Capacity Planning for Digital Broadcast Manager white paper on the Microsoft Web site. This white paper will be available approximately mid February.

Digital Broadcast Manager hardware requirements

This section describes the hardware requirements for each configuration in the three-server configuration that makes up a Digital Broadcast Manager system.

SQL Server hardware

The following table shows the recommended minimum hardware configuration for the SQL Server.

Category

Recommended configuration

Processor

Dual Pentium II 400 megahertz (MHz) or better

Memory

256 megabytes (MB) minimum (512 MB recommended)

Disk space

Two 18-gigabyte (GB) SCSI 7,200 drives

Disk configuration

RAID-1 (redundant array of independent disks, level 1)

Network connection

100BaseT network adapter

Note: It is recommended that you implement RAID-1 (disk mirroring) for best fault tolerance. However, you can implement RAID-0 (disk striping) if you prefer performance to fault-tolerance. RAID-0 provides the best I/O performance.

Web server hardware

The following table shows the recommended minimum hardware configuration for the Web server.

Category

Recommended configuration

Processor

Single Pentium II 400 MHz or better

Memory

256 MB minimum

Disk space

One 9-GB SCSI 7,200 drive

Disk configuration

One 2-GB primary NTFS partition (system) and one 7-GB secondary NTFS partition (Inetpub root)

Network connection

100BaseT network adapter

Windows Media server hardware

The following table shows the recommended minimum hardware configuration for the Windows Media server.

Category

Recommended configuration

Processor

Dual Pentium II 400 MHz or better

Memory

256 MB or more

Disk space

One 9-GB SCSI 7,200 drive

Disk configuration

One 2-GB primary NTFS partition (system) and one 7-GB secondary NTFS partition (ASFRoot)

Network connection

100BaseT network adapter

Digital Broadcast Manager software requirements

This section describes the general software installation procedures for the three-server configuration that makes up a Digital Broadcast Manager system. This section is only an overview of the installation procedures and is designed for someone who is familiar with installing Microsoft Windows NT® Server and other Microsoft applications. It is not a complete installation guide. Products are installed using default installation procedures unless otherwise noted.

Setting up the software on the SQL Server

In the three-server configuration that makes up a Digital Broadcast Manager system, the following software must be installed on the computer running SQL Server:

  • Windows NT Server 4.0

  • Windows NT 4.0 Service Pack 4 (SP4)

  • Microsoft Internet Explorer 5

  • SQL Server 7.0

  • SQL Server 7.0 SP1

  • Microsoft Data Access Components (MDAC) 2.1 SP2

  • Windows NT 4.0 SP6

This section describes the procedure for installing the software. Each software product must be installed with default settings unless otherwise noted.

To install the software on the SQL Server

Install Windows NT Server 4.0. The following custom settings are required:

  • Format the partition for the operating system using the NTFS file system so you can use the advanced security features.

  • On the Server Type screen, click Stand-Alone Server.

  • (Optional) Type the following server name: WMSSQL01. If you choose a different server name, choose a server name that contains only alphanumeric characters. Do not use a server name that has more than 12 characters.

  • Do not install Internet Information Server (IIS).

  • On the Networking Protocol screen, select only TCP/IP Protocol.

  • On the TCP/IP Setup message screen that asks you if you wish to use DHCP, click No. You must specify an IP address.

Note: After installing Windows NT Server 4.0, run Disk Administrator and format any remaining unformatted partitions as NTFS.

  1. Install Windows NT 4.0 SP4.

  2. Install Internet Explorer 5.

    Install the full version of SQL Server 7.0. The following custom setting is required:

    • On the Services Accounts screen, under Service Settings, click Use the Local System account.

    Install SQL Server 7.0 SP1. The following custom setting is required:

    • On the Connect to Server screen, click SQL Server authentication.

  3. Install Microsoft Data Access Components (MDAC) version 2.1 SP2.

    Download the MDAC 2.1 SP2 software from the Microsoft Universal Data Access page at the Microsoft Web site ( http://www.Microsoft.com/Data/ ).

  4. Install Windows NT 4.0 SP6.

To configure the software on the SQL Server

  • In SQL Server 7.0 Enterprise Manager, create the following databases.

    Name

    Initial size (General tab)

    Initial size (Transaction Log tab)

    SSAnalysis

    100 MB

    50 MB

    SSCommerce

    500 MB

    250 MB

    SSMembership

    250 MB

    125 MB

    Change the default network library from Named Pipes to TCP/IP.

    • In the SQL Server Client Network Utility, select TCP/IP in the Default network library list, and then click Add.

    • Type the fully qualified domain name for the SQL Server in Server alias, and then click OK.

  • Enable DNS for Windows® name resolution.

    The Enable DNS for Windows Resolution setting allows Domain Name System (DNS) in addition to network basic input/output system (NetBIOS) name resolution on Windows networks. DNS is the name resolution method used on the Internet. If you plan to deploy your Digital Broadcast Manager system on the Internet, perform the following steps:

    • In Control Panel, double-click Network.

    • In the Network dialog box, on the Protocols tab, click TCP/IP Protocol in the Network Protocols list, and then click Properties.

    • In the Microsoft TCP/IP Properties dialog box, on the WINS Address tab, click Enable DNS for Windows Resolution.

    Optimize SQL Server performance:

    • In SQL Server 7.0 Enterprise Manager, increase the size of the tempdb database to 25 MB.

    • Set the MSDTC (Microsoft Distributed Transaction Coordinator) Service to start automatically when the system starts.

    • Maximize throughput for network applications for the server network service.

    Note: For more information about optimizing tempdb performance, see Optimizing tempdb performance in SQL Server Books Online. For detailed instructions on how to maximize throughput for network applications for the server network service, see To specify settings for a network service in Windows NT Help.

Setting up the software on the Web server

In the three-server configuration that makes up a Digital Broadcast Manager system, the following software must be installed on the Web server computer:

  • Windows NT Server 4.0

  • Windows NT 4.0 SP3

  • Internet Explorer 4.01 SP2

  • Windows NT 4.0 Option Pack

  • Microsoft FrontPage® 98 Server Extensions 3.0.2.1706

  • Site Server 3.0

  • Site Server 3.0, Commerce Edition

  • Windows NT 4.0 SP4

  • Internet Explorer 5

  • MDAC 2.1 SP 2

  • Active Directory Service Interfaces (ADSI) 2.5

  • Site Server 3.0 SP3

  • Windows Media Tools 4.1

  • Microsoft Windows Media Rights Manager version 1.0

  • Windows NT 4.0 SP6

This section describes the procedure for installing the software. Each software product must be installed with default settings unless otherwise noted.

To install the software on the Web server

Install Microsoft Windows NT Server 4.0. The following custom settings are required:

  • Format the partition for the operating system using the NTFS file system so you can use the advanced security features.

  • On the Server Type screen, click Stand-Alone Server.

  • (Optional) For a server name, type WMSIIS01. If you choose a different server name, choose a server name that contains only alphanumeric characters. Do not use a server name that has more than 12 characters.

  • Do not install Internet Information Server (IIS).

  • On the Networking Protocol screen, select only TCP/IP Protocol.

  • On the TCP/IP Setup message screen that asks you if you wish to use DHCP, click No. You must specify an IP address.

Note: After installing Windows NT Server 4.0, run Disk Administrator and format any remaining unformatted partitions as NTFS.

  1. Install Windows NT 4.0 SP3.

  2. Install Internet Explorer 4.01 SP2. Skip the Windows Desktop Update installation.

    Install Windows NT 4.0 Option Pack. The following custom setting is required:

    • On the Select Components screen, clear the FrontPage 98 Server Extensions and Microsoft Script Debugger components.

  3. Install Microsoft FrontPage 98 Server Extensions version 3.0.2.1706.

    Download the FrontPage 98 Server Extensions from the Microsoft FrontPage 98 Server Extensions v. 3.0.2.1706 for Windows Platforms Update page at the MSDN Online Web Workshop Web site ( http://msdn.microsoft.com/workshop/languages/fp/98exts/1706update_Windows.asp ).

    Install Site Server 3.0. The following custom settings are required:

    • When you select features during Site Server 3.0 installation, clear the Access Database Support feature of Analysis. Digital Broadcast Manager contains a separate analysis tool.

    • When you set a user account for selected features, type Administrator in User name and Password. Type the computer name in Domain.

    Notes: The next time you restart the Web server computer, wait for approximately 3 minutes for Index Server to finish indexing before logging back on to the Web server. After you log on, monitor Task Manager until the System Idle Process is greater than 95 percent.

    The default settings in Site Server 3.0 balance security, performance, and administrative convenience. Changing settings to strengthen security can weaken performance and/or administrative convenience. It is recommended that you review the Microsoft Site Server documentation before you make security decisions.

    Install Site Server 3.0, Commerce Edition. The following custom setting is required:

    • On the components screen, clear all components in the Components list. Then, when you are prompted to install the Commerce Server core components, click Yes.

  4. Install Windows NT 4.0 SP4.

  5. Install Internet Explorer 5.

  6. Install MDAC version 2.1 SP2.

    Download the MDAC 2.1 SP2 software from the Microsoft Universal Data Access page at the Microsoft Web site ( http://www.Microsoft.com/Data/ ) or from the Microsoft TechNet CD subscription.

  7. Install Active Directory Service Interfaces (ADSI) version 2.5.

    Download the ADSI 2.5 software from the Active Directory Service Interfaces 2.5 page at the Microsoft Web site ( http://www.microsoft.com/NTServer/nts/downloads/other/ADSI25/ ) or from the Microsoft TechNet CD subscription.

  8. Install Site Server 3.0 SP3.

  9. Install Windows Media Tools version 4.1.

    Install Windows Media Rights Manager version 1.0. The following custom setting is required:

    • On the Create or Select Database screen, in Database Name, type SSContent, and in SQL Server, type SQL_Server_name .

  10. Install Windows NT 4.0 SP6.

To configure the software on the Web server

  • Configure IIS to use TCP/IP sockets when it connects to the SQL Server computer in the Digital Broadcast Manager system.

    1. Run the SQL Client Configuration Utility (Windbver.exe).

    2. In the SQL Server Client Configuration Utility dialog box, on the Net Library tab, select TCP/IP Sockets in the Default Network list.

  • Enable DNS for Windows name resolution.

    The Enable DNS for Windows Resolution setting allows DNS in addition to NetBIOS name resolution on Windows networks. DNS is the name resolution method used on the Internet. If you plan to deploy your Digital Broadcast Manager system on the Internet, perform the following steps:

    • In Control Panel, double-click Network.

    • In the Network dialog box, on the Protocols tab, click TCP/IP Protocol in the Network Protocols list, and then click Properties.

    • In the Microsoft TCP/IP Properties dialog box, on the WINS Address tab, click Enable DNS for Windows Resolution.

  • Change the User Rights policy so that the account used to log on to the Web server has the advanced user right Log on as a service. The account must be a local or domain account with administrative rights on the server.

  • Configure the SMTP Service.

    Identify the mail server, such as Microsoft Exchange Server, that processes the mail. Then, perform the following steps to configure the Default SMTP Site on the Web server.

    • In Internet Service Manager, expand the Internet Information Server folder and Web_server_name, right-click Default SMTP Site, and then click Properties.

    • On the Delivery tab, type the name or IP address of the mail server in Smart host.

  • Maximize throughput for network applications for the server network service.

    Notes: The Log on as a service advanced user right allows the Digital Broadcast Manager service on the Web server to log on to remote machines in the Digital Broadcast Manager system. For more information about changing the User Rights policy, see To manage the User Rights policy in the User Manager Help. To improve SMTP Service performance, specify an IP address in Smart host instead of a name. To use the IP address, enter the address for the smart host in square brackets to indicate that this value is an IP address. When you use the IP address, IIS skips parsing the address string to identify it. For detailed instructions on how to maximize throughput for network applications for the server network service, see To specify settings for a network service in the Windows NT Help.

Setting up the software on the Windows Media server

In the three-server configuration that makes up a Digital Broadcast Manager system, the following software must be installed on the computer running Windows Media Services:

  • Windows NT Server 4.0

  • Windows NT 4.0 SP4

  • Internet Explorer 5

  • MDAC 2.1 SP2

  • ADSI 2.5

  • Windows NT 4.0 SP6

  • Windows Media Services 4.1

This section describes the procedure for installing the software. Each software product must be installed with default settings unless otherwise noted.

To install the software on the Windows Media server

Install Windows NT Server 4.0. The following custom settings are required:

  • Format the partition for the operating system using the NTFS file system so you can use the advanced security features.

  • On the Server Type screen, click Stand-Alone Server.

  • (Optional) Type the following server name: WMSSERVER01. If you choose a different server name, choose a server name that contains only alphanumeric characters. Do not use a server name that has more than 12 characters.

  • Do not install Internet Information Server (IIS).

  • On the Networking Protocol screen, select only TCP/IP Protocol.

  • On the TCP/IP Setup message screen that asks you if you wish to use DHCP, click No. You must specify an IP address.

Note: After installing Windows NT Server 4.0, run Disk Administrator and format any remaining unformatted partitions as NTFS.

  1. Install Windows NT 4.0 SP4.

  2. Install Internet Explorer 5.

  3. Install MDAC version 2.1 SP2.

    Download the MDAC 2.1 SP2 software from the Microsoft Universal Data Access page at the Microsoft Web site ( http://www.microsoft.com/Data/ ) or from the Microsoft TechNet CD subscription.

  4. Install ADSI version 2.5.

    Download the ADSI 2.5 software from the Active Directory Service Interfaces 2.5 page at the Microsoft Web site ( http://www.microsoft.com/NTServer/nts/downloads/other/ADSI25/ ) or from the Microsoft TechNet CD subscription.

  5. Install Windows NT 4.0 SP6.

    Install Windows Media Services 4.1. The following custom setting is required:

    • On the Enable HTTP streaming and distribution screen, click Enable HTTP streaming for the Windows Media unicast service.

To configure the software on the Windows Media server

  • Change the User Rights policy so that the account used to log onto the Windows Media server has the advanced user right Log on as a service. The account must be a local or domain account with administrative rights on the server.

  • Enable DNS for Windows name resolution.

    The Enable DNS for Windows Resolution setting allows DNS in addition to NetBIOS name resolution on Windows networks. DNS is the name resolution method used on the Internet. If you plan to deploy your Digital Broadcast Manager system on the Internet, perform the following steps:

    • In Control Panel, double-click Network.

    • In the Network dialog box, on the Protocols tab, click TCP/IP Protocol in the Network Protocols list, and then click Properties.

    • In the Microsoft TCP/IP Properties dialog box, on the WINS Address tab, click Enable DNS for Windows Resolution.

    Enable logging for unicast client information.

    • In Windows Media Administrator, click Server Properties.

    • Click the Publishing Point Logging tab.

    • Click Enable Logging, and accept the default period (Daily) and folder location (SystemRoot\System32\Logfiles).

    • Click Apply.

  • Maximize throughput for network applications for the server network service.

    Note: For more information about changing the User Rights policy, see To manage the User Rights policy in the User Manager Help. For detailed instructions on how to maximize throughput for network applications for the server network service, see To specify settings for a network service in the Windows NT Help.

Installing Digital Broadcast Manager

This section describes the installation procedures for Digital Broadcast Manager. All required software must already be installed on each of the three servers in the Digital Broadcast Manager configuration.

Important: Uninstall is not supported in this beta version of Digital Broadcast Manager.

To install Digital Broadcast Manager

  • Run Microsoft Digital Broadcast Manager for Windows Media Setup, first on the Web server and then on the Windows Media server. Do not run Setup on the SQL Server.

    If you install Digital Broadcast Manager on the Windows Media server first, you must stop and restart the Windows Media Unicast Service on the Windows Media server so that it can acquire the Lightweight Directory Access Protocol (LDAP) service that runs on the Web server.

    Note: After you install Digital Broadcast Manager on the servers in your system, open Digital Broadcast Manager Administrator on the primary Web Server (type http:// primary_Web_server_name:8080/ ) and confirm that the each Web server and Windows Media server in the system appear on the Servers page in Site Manager. For more information, see Servers in the Digital Broadcast Manager online Help documentation.

Installing the credit card software

Digital Broadcast Manager contains credit card processing software, called the CyberSource Commerce Component for Microsoft Site Server, Commerce Edition, provided by Cybersource Corporation ( http://www.cybersource.com/ ). You can use the CyberSource Commerce Component to simulate credit card transactions on the Digital Broadcast Manager sample store (Southridge Video Store) and perform actual credit card transactions when you activate the store on the Internet. CyberSource Commerce Component for Site Server, Commerce Edition Setup is stored on the Web server (SystemDrive\Program Files\Windows Media Components\Microsoft Digital Broadcast Manager\Components\CyberSource) in the Digital Broadcast Manager system.

The Digital Broadcast Manager sample store is pre-registered with test status at the CyberSource data center; therefore, you can install the CyberSource Commerce Component and run test credit card transactions, using a preinstalled test-merchant ID and the following test credit card numbers, before activating your store. Test credit card transactions never reach a bank for authorization or billing.

Credit card

Test credit card number

American Express

3111-1111-1111-1117

Visa

4111-1111-1111-1111

MasterCard

5111-1111-1111-1118

Discover

6111-1111-1111-1116

If you choose to continue using the CyberSource Commerce Component to process credit card payments after activating your store, you must contact a CyberSource customer service representative to register and obtain a CyberSource-assigned merchant ID.

Note: If you do not install the CyberSource Commerce Component, you can still simulate a test credit card transaction on the store. The transaction proceeds as if a credit card payment is made; however, credit card processing is skipped.

To implement the CyberSource Commerce Component

This procedure outlines the process required to install the CyberSource Commerce Component on the Web server and run a test credit card transaction against the CyberSource data center.

  1. On the Web server, run CyberSource Commerce Component for Site Server, Commerce Edition Setup (SystemDrive\Program Files\Windows Media Components\Microsoft Digital Broadcast Manager\Components\CyberSource\Setup.exe).

  2. Register the CyberSource Commerce Component.

    Click Start, point to Programs, point to CyberSource Commerce Component, and then click Register Component.

  3. In Pipeline Editor, open the order processing pipeline configuration files credits.pcf and purchase.pcf located in SystemDrive\Inetpub\Wwwroot\Srvs\Config, and add the CyberSource Commerce Component to the payment stage in the pipeline. For more information about adding components to a pipeline, see The Pipeline Editor in the Microsoft Site Server, Commerce Edition documentation.

  4. On the Web server, run a test credit card transaction between the Digital Broadcast Manager sample store and the CyberSource data center.

    Click Start, point to Programs, point to CyberSource Commerce Component, and then click Test a SCMP Transaction. A Simple Commerce Messaging Protocol (SCMP) test transaction is conducted using a preinstalled Merchant Key and a test credit card number. The CyberSource Commerce Component in the payment stage of the OrderPipeline initiates a connection to the CyberSource data center as part of the test. Test failures are likely due to network connection problems, for example, your corporate LAN's firewall may block the test transaction.

    Note: Complete documentation support is installed with the CyberSource credit card software. On the Web server, click Start, point to Programs, point to CyberSource Commerce Component, and then click CyberSource Component Doc. An updated version of the documentation is also available from the Cybersource Web site ( http://apps.cybersource.com/library/documentation/dev_guides/Microsoft_Site_Server/html/ch03.html ).

For more information

To learn more, see the Digital Broadcast Manager online Help documentation.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft