Server API for Release 2.

7
Product Overview
August 25, 2006
Version 1.0

This Bloomberg Server API documentation is a reference guide for Bloomberg customers and
authorized developers, and is provided for such informational purposes only. The documentation
cannot be released to anyone who is not licensed to receive it from Bloomberg. The documentation
is governed by the Bloomberg Agreement and other agreements with Bloomberg.

BLOOMBERG is a registered trademark of Bloomberg, L.P. in the United States and other countries.

All other trademarks and registered trademarks are the property of their respective owners.

© 2006 Bloomberg, L.P. All rights reserved.

 Table of Contents ii

Table of Contents
Table of Contents........................................................................................................................ ii
Customer Support Information.................................................................................................. 4
1 Product Description................................................................................................................ 5
1.1 Overview .......................................................................................................................... 5
1.2 Authorized Users of Server API ....................................................................................... 5
1.3 Server API Product Features ........................................................................................... 7
1.4 Technical Overview.......................................................................................................... 7
1.5 Network Requirements .................................................................................................... 8
1.6 Supported Platforms ...................................................................................................... 10
1.7 Supported Programming Languages ............................................................................. 10
1.8 64-bit Support ................................................................................................................ 11
2 Application Development..................................................................................................... 12
2.1 Client Library.................................................................................................................. 12
2.2 Test Environment........................................................................................................... 12
2.3 Server API Usage Model ............................................................................................... 12
2.4 Building Your Application ............................................................................................... 14
2.5 Preparing Applications for Production............................................................................ 14
3 Implementing your Application ........................................................................................... 15
3.1 User Account Requirements and Recommendations .................................................... 15
3.2 Server API Requirements .............................................................................................. 16
3.3 Multi-User Model ............................................................................................................ 16
3.4 Server Model.................................................................................................................. 18
Appendix A: Security Plan ...................................................................................................... 21
General Questions Related to Your Application ................................................................... 21
Integration of Bloomberg Server API .................................................................................... 21

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service. i
i
 Customer Support Information 4

Customer Support Information

Sales Support
Call your Bloomberg sales representative.

Americas: +1 212 318 2000

Europe: +44 20 7330 7500

Pacific Rim: +81 3 3201 8900

+65 6212 1000

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service. 4
1 Product Description 5

1 Product Description
1.1 Overview
The Bloomberg Server API is a data product that delivers Bloomberg data and third party
data in real-time and static form, plus unparalleled analytical capabilities to drive targeted
business applications. The Server API leverages the Bloomberg Professional API for its core
functionality, with additional features that make it a true server solution. The Server API is
intended to run independently and autonomously, 24x7, with scalable configurations to
support small or large business requirements. Server API is intended to support business
applications for Bloomberg Users only.

1.2 Authorized Users of Server API

1.2.1 Background
The Server API is a technical extension of the Bloomberg Professional terminal API, but
carries its own licensing agreement with Bloomberg. The desktop API that accompanies the
terminal is intended for that user only and is not meant to act as a server based API
connection supporting groups of users. The Server API is specifically intended for that
purpose and differentiates itself from the terminal API at this point. Because the Server API
allows for data distribution, certain control features must be in place within the client's
application to control the flow of data to Bloomberg BBA users only.

1.2.2 Standard Use of Server API

The standard contractual terms for Server API require that you implement specific measures
in your application that control the flow of Bloomberg data to very strongly defined
“Authorized Users”. The Server API offers a toolset that lets you validate for Bloomberg users
and their data entitlements through your application to ensure they are authorized to receive
data from your application and Server API. These tools must be integrated into your
application prior to use to control the flow of data to authorized users only.

1.2.3 Authorized Users

All users must be Bloomberg BBA users actively logged in to their Bloomberg when receiving
Bloomberg data from your application. The user's data entitlements must be checked using
the Server API permissioning toolset prior to use. The user cannot be receiving Bloomberg
data at multiple locations simultaneously and no two users can share your applications logon
credentials or Bloomberg logon credentials.

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
1 Product Description 6

1.2.4 Connecting to Bloomberg via Server API

The Server API is intended to nourish server based applications and can be implemented in
two ways depending on your application needs and how your users interact with the data.

1.2.4.1 Server Model

Server mode is used when you implement an application that runs autonomously on the
server and supports client users that request data from your application and not Bloomberg
directly. Your application may request data on behalf of a group of users, and may do caching
or server side processing prior to dissemination to an “authorized user”. In Server Mode, the
connection with Bloomberg is established on behalf of the server itself. The server carries its
own identity and all data retrieved is based on that identity. This identity is created when the
Server API is installed by using a Bloomberg BBA license that accompanies the Server API
service. This Bloomberg BBA login should be retained by the Server API administrator for
future use.

1.2.4.2 Multi-User model

This implementation allows each authorized user to connect using their personal Bloomberg
BBA license credentials (UUID, SID, SID Instance, etc.). The connection is established
through the Server API session but specifically for the individual user. This mode is designed
for applications that do NO caching, but pass all requests directly back to the authorized user
that initiated the request.

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
1 Product Description 7

1.3 Server API Product Features

Table 1-1 summarizes the Server API features.

Table 1-1: Server API Product Features

Features Server API

Data Types z Streaming data: Trades, Quotes, etc.
z Static data: Security master, derived data, historical data,
snapshot pricing data

Approximately 11,000 data fields

Instrument Types All instruments and data sources offered in Bloomberg desktop API
and Data Sources
Data Distribution Targeted applications with user permissioning. All users must have a
Bloomberg License.
Development z Used for initial and ongoing application development
License z Limited data (5000 hits daily)
z Limited Function Bloomberg Terminal
z Documentation and support access
Production Server Prior to use, Bloomberg verifies each application’s permissioning
API system.
Pricing There is a monthly fee for:
z Server API
z Development License

See your Bloomberg Sales Representative for current pricing

Product Description The Server API requires the customer application to permission users
and control data distribution to Bloomberg Anywhere users only.

1.4 Technical Overview

The Server API product consists of:
z A user-managed process that runs on the customer's machines and communicates
with Bloomberg; and
z Libraries for writing local applications that communicate with this process:
 C APIs
See “C Function Library” on page 10 for more information.
 .NET and COM APIs
See “Microsoft .NET Interface” on page 11 and “COM Data Control” on
page 11 for information about these APIs.

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
1 Product Description 8

z An installation program facilitates a simple installation and registration procedure.

z Help programs and samples
z Documentation

The Server API process is not intended to be installed on an Open Bloomberg Terminal and
does not require any additional middleware products. The product is available for Windows
Server and a variety of UNIX-like platforms.

All customer or vendor applications that communicate directly with a Server API instance
(that is, they link in the Bloomberg Server API Client Library) must be digitally signed. The
Bloomberg API Software Signing tool offers a simple and fast process for signing
applications. The signing tool takes as inputs, the customer's compiled programs (binaries),
any supporting libraries (.dll or .so), and a Bloomberg supplied vendor-signing certificate.

1.5 Network Requirements

The Server API process resides on a Solaris, Linux, or Windows server. That machine must
have connectivity to Bloomberg’s API network in one of the following ways:
z Bloomberg Network
Server machines connect through leased lines and a Bloomberg router. Bloomberg
provides two gateways to the API Network. The server machines should be able to
connect to both hosts.
z Through the internet
Bloomberg provides two IP addresses for the API network. The server machines
should be able to connect to both addresses.

Bloomberg highly recommends that production servers connect through Bloomberg’s

dedicated network.

The Server API process establishes multiple (currently two to four) TCP/IP connections to
Bloomberg API Network from the client's network to Bloomberg's network (i.e., outbound
connections) to ports 8194 and 8195 on published IP addresses in the Bloomberg domain. All
data except for real-time, outbound streaming tick data is encrypted using a mutually
authenticated SSL session.

Server API listens for TCP/IP connections from internal client applications on ports 8194 and
8195. Unlike the connections to the Bloomberg network, these connections are not
encrypted. Figure 1-1 provides a high level illustration of the connectivity surrounding a
Server API instance.

Although your company can have multiple Server APIs, Bloomberg requires
that only one Server API process be running per licensed installation.

Each Server API process has its own serial number and registration key and
Bloomberg only allows one connection for each registration key.

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
1 Product Description 9

Figure 1-1: Server API High-Level Network View

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
1 Product Description 10

1.6 Supported Platforms

Server API is installed by Bloomberg customers on their own servers using an installation
application that is downloaded from Bloomberg. Multiple platforms, made up of standard
operating systems and hardware, are supported. Table 1-2 lists the supported platforms.

Table 1-2: Supported Platforms

Platform Operating System Architecture

Windows Server 2000 X86
Server 2003
Linux Kernel 2.4† 686

Kernel 2.6†
Solaris Solaris 8 SPARC
Solaris 9
Solaris 10
† Server API has been tested against a variety of Red Hat and SUSE Linux
distributions based on Linux Kernel 2.4 and 2.6. Only Red Hat and SUSE
distributions are supported. The minimum supported version of GLIBC is 2.3.2.

The optimal hardware requirements for a customer vary depending on the expected usage.
An application that makes infrequent data calls or subscribes to a small number of real-time
tick streams can run on minimal hardware. An application that makes high volume data
requests or subscribes to a large number of real-time tick streams will benefit from more
CPUs, faster clock rates, and more memory. Table 1-3 specifies the minimum hardware
configurations that Server API is supported on.

Table 1-3: Minimum Hardware Requirements

Architecture CPU Memory Disk

X86 Single 2.4 GHz 512 Mb Ram 20 Gb
686 Single 2.4 GHz 512 Mb Ram 20 Gb
SPARC UltraSPARC II 1 Gb Ram 20 Gb

1.7 Supported Programming Languages

Server API comes with a library of functions that enable communication between custom
applications and the Server API process.

1.7.1 C Function Library

These functions are written in the C language, which in theory means that there are
potentially many programming languages to select from when developing Server API-
enabled applications, including C, C++, and Java. In practice, however, Bloomberg requires
For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
1 Product Description 11

that applications are provided as either ELF (Solaris/Linux) or PE COFF (Windows) formatted
executable files. Microsoft Visual Studio, Visual Studio .NET and all UNIX linkers generate
files in these formats, and therefore any programming language that is both supported by
these products and supports calling external C functions is in turn supported by Server API.
Therefore, languages like Java and Perl, while they provide mechanisms for calling C
functions, are not supported because they do not provide binaries in one of the above
formats.

1.7.2 Microsoft .NET Interface

This interface provides the same functionality as the C library but as a .NET interface,
meaning that developers can use any language supported by CLR, including C#, C++, and
VB.NET to develop their Server API-based applications. Bloomberg does not support its
.NET interface on the Mono platform.

The Server API for .NET can be downloaded from {WAPI<GO>} on your Bloomberg terminal.

1.7.3 COM Data Control

The COM Data Control for Server API is a solution for those clients who want to have the
benefit of using the Bloomberg Server API, but want to have backward compatibility with
existing applications that were developed with the Bloomberg ActiveX Data Control and/or
Excel spreadsheets.

The COM Data Control for Server API exposes the same programming interface as the
Bloomberg Data Control plus an additional programming interface specific to Server API. See
{WAPI<GO>} for details.

The COM Data Control for Server API can be downloaded from {WAPI<GO>} on your
Bloomberg terminal.

1.8 64-bit Support

The Server API library uses a 32-bit programming model. Currently, Bloomberg does not
support calling Server API library functions from within 64-bit applications.

To integrate Bloomberg data into 64-bit applications, you should consider

writing a 32-bit server application that takes requests for Bloomberg data and
forwards them to Bloomberg via Server API.

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
2 Application Development 12

2 Application Development
This section summarizes aspects of the Server API development environment. For additional
details and a step-by-step guide to developing Server API-based applications, see the Server
API Developer's Guide.

2.1 Client Library

The Server API installation program installs a set of C header files and a C function library
that customers use to program their application in order to access Bloomberg data. These
libraries are the same as the ones provided with the Desktop API with some additions
specifically for Server API that are described in detail in the Server API Developer's Guide.

A user's guide, with examples and a reference manual detailing the function-level interface in
the Bloomberg API C library is provided on the Bloomberg terminal at WAPI<GO>.

2.2 Test Environment

In order to develop Server API-enabled applications, you will need access to a Server API
test environment. In some development environments, it may be feasible for developers to
connect directly to a production backup (or even primary) Server API process.

Bloomberg recommends that developers work with a separate development installation that
is covered by a Server API Developer license agreement. The recommended process is to
develop your application on a development machine, then move the application to your
production machine.

2.3 Server API Usage Model

There are two distinct logical models for using the Server API. The difference between the
two is motivated primarily by permissions and data preferences and the model you choose
will affect how you program your application. The decision to use one model over the other is
also influenced by how the resulting data is distributed to users and who these users are. See
“Implementing your Application” on page 15 or contact your Bloomberg Sales
Representative for more information on data permissions.

2.3.1 Server Model

A server-based permission scheme is used in cases where your server-based application will
retrieve data from a Server API instance on behalf of many users, instead of making
individual requests on behalf of each user. An individual user's real-time permissions will
normally be checked after your application has started receiving real-time data. The
verification of permissions for each user must take place during the client's user
authentication process.
For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service. 1
2
2 Application Development 13

If you are using the Server Model, the Bloomberg Server API product provides two
permissioning models for controlling access to data. These models are outlined below. For
more details see the Server API Developer's Guide.

2.3.1.1 All or None Model

The All or None model for controlling access to data is intended for use by firms where the
majority of the server users are trading similar instruments. In this model, Bloomberg verifies
that the user requesting security data is entitled to receive all of the data that is available via
their Server API. If the user is not entitled to data available via their Server API, Bloomberg
will recommend that the user not receive data and return the entitlement IDs for the data
available on the server that a user is not entitled to.

For more information on the All or None Model, see the Server API Developers Guide.

2.3.1.2 Product Level Model

The Product Level model for controlling access to data is intended to provide the granularity
and flexibility required by firms where users of the same Server API trade a variety of
instruments. With this model, clients will be able to submit requests to Bloomberg to
determine:
z The set of entitlements for a security for which the user is enabled.
z The set of entitlements for a security for which the Server API installation is enabled.

It is then expected that the client will verify that a specific user has the necessary
entitlements to receive data when a user requests information for a specific security.

For more information on the Product Level Model, see the Server API Developers Guide.

2.3.2 Multi-User Model

A multi-user permission scheme is used in cases where the permissions of each individual
user should be used to retrieve data from a Server API independently from any other user.
That is, a server application would have multiple sessions with the Server API, one for each
user, in order to make independent data requests.

Independent data requests may be desirable if each user is performing some unrelated work
with respect to other users or if each user wants to use their own preferences and set of
privileges to retrieve data. The downside of this approach is that redundant data requests
may be sent resulting in higher network and processing demands. This also means that
individual sessions would make their own real-time data subscriptions. The permissions
assigned to the Server API process are not used in this model, instead each individual's
permissions are checked when a request is validated.

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
2 Application Development 14

2.4 Building Your Application

API library functions depend only on standard language and operating system libraries. The
example directory created during installation contains a sample program that resolves API
library references on your chosen platform.

2.5 Preparing Applications for Production

Bloomberg requires that applications that connect to production Server API instances are
digitally signed with a valid Bloomberg-issued ISV certificate and registered with Bloomberg.
See “Digital Signature Requirements” on page 19 for more information.

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
3 Implementing your Application 15

3 Implementing your Application

The following section highlights, but is not limited to, criteria that is examined during the
course of Bloomberg's Server API evaluation and approval process. This list does not contain
an exclusive list of all areas under review and is subject to change based on the actually
deployment solution selected and implemented by the organization using Server API.

Implementing a secure permissioning scheme protects both your firm and Bloomberg from
unauthorized use of data.

Bloomberg requires that you adhere to the data permissioning requirements described in this
section to ensure that data is distributed only to authorized users, computers, and servers, as
described in your contract. Additionally, Bloomberg reserves the right to audit and test your
application to verify that these requirements are being met.

There are two general types of requirements that Bloomberg will need to verify in order to
approve the Server API permissioning system:
z 3.1 User Account Requirements and Recommendations
z 3.2 Server API Requirements

3.1 User Account Requirements and

Recommendations
The following requirements and recommendations refer to the Server API accounts. If the
customer chooses to use an existing account management system (for example, a Windows
domain), then these requirements still apply to accounts that are used to access Server API.
z There must be no sharing of accounts or passwords.
z No two user accounts may be mapped to the same UUID or SID.
z It must be possible to produce, on demand, a report showing the mapping of user
accounts to UUIDs and SIDs and a login history, including both successful and failed
login attempts.
z It is recommended that accounts be disabled after a maximum of 90 days of
inactivity.
z It is recommended that passwords must be at least 8 characters long.
z It is recommended that passwords not be transmitted over the network in clear text.

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service. 1
5
3 Implementing your Application 16

3.2 Server API Requirements

As described in “Server API Usage Model” on page 12, the Server API is available in two
different models for permissioning.

Permissioning requirements are different for Server Model and Multi-User Model
applications. In general, Multi-User Model applications must always preserve the separation
between users, while Server Model applications may allow common access to data among
authorized users. In cases where database storage is permitted, permissioning requirements
for accessing data from a database are the same as for accessing the data directly from
Bloomberg.

The Server API Developers Guides provides information on the functions that Bloomberg
provides to facilitate meeting these permissioning requirements.

3.3 Multi-User Model

In the Multi-User Model, the permissions of each individual user should be used to retrieve
data from a Server API independently.
z A Multi-User Model Server API has no identity of its own.
z Every request made by a Multi-User Model server is made on behalf of some client
application. The server should receive no data when no clients are connected to the
server.
z Each user's data stream must be strictly separated from all others - there must be no
mingling of one user's data with another's.
z The server may not store Bloomberg data in a central database. If data will be stored
in a local database for a user, it must be secure for that user only.
z A Multi-User Model server maintains a separate logical connection from the Server
API client application to Bloomberg for each user.
z All users must be Bloomberg BBA users actively logged in to their Bloomberg when
receiving Bloomberg data from your application.
z Bloomberg determines a user’s data entitlements on a per data request basis.

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
3 Implementing your Application 17

Figure 3-1: Simple Multi-User Model

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
3 Implementing your Application 18

3.4 Server Model

The Server API has its own set of permissions, determined by your contract with Bloomberg.
z A Server Model server has its own UUID and SID and is created when the Server
API is installed.
z A Server Model server may run autonomously, receiving and processing data when
no users are logged in.
z There is only one logical connection between Bloomberg and the server. The server
itself manages connections to the client applications.
z Data may be stored in a central database, but must be strongly controlled. Data may
also be stored in local databases on the workstations.
z All users must be Bloomberg BBA users actively logged in to their Bloomberg when
receiving Bloomberg data from your application.
z A Server Model server can use either of two permissioning models to control user
access to data, the All or None Permissioning Model or the Product Level
Permissioning Model. See “Server Model” on page 12 for more information.

Your application must control user’s data entitlements using the Server API tool set. Two
methods are offerered:
z All or None
z Product Level Permissioning

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
3 Implementing your Application 19

Figure 3-2: Simple Server Model - All or None Permissioning

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
3 Implementing your Application 20

Figure 3-3: Simple Server Model - Product Level Permissioning

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.
A: Security Plan 21

A: Security Plan
This section provides a sample of the Security Plan that is included with the Server API
contract.

Please respond per unique application

Firm Name:

Date:

Responder Name:

Responder Email:

The following questions apply to customers using Server API for Bloomberg Terminal Users.
Please read the Permissioning section of the Server API Product Overview before answering
these questions.

General Questions Related to Your Application

What is the name of your applications?

These questions refer to the Server API application's user accounts, not to the underlying
Bloomberg user accounts.

1. Which type of application will you run? (Refer to the application types in the
Permissioning chapter of the Server API Product Overview, (check only one):

‰ Simple Multi-User Model

‰ Multi-User Model with Database

‰ Simple Server Model

‰ Server Model with Database

Integration of Bloomberg Server API

User Management

1. Are any two of your application's user accounts mapped to the ‰ Yes ‰ No
same UUID or SID?

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service. 2
1
A: Security Plan 22

2. Can you produce a report showing the mapping of your ‰ Yes ‰ No

application's user accounts to Bloomberg UUIDs and SIDs and the
login history for user each account, including both successful and
failed login attempts?

User Validation

1. Using the Server API Tool Set, are all users validated as ‰ Yes ‰ No
Bloomberg Users that are logged in to Bloomberg on the same
device where they are running or viewing your application?

2. If user validation fails does your application block access to ‰ Yes ‰ No

Bloomberg Data from Server API?

User Entitlements
The Bloomberg Server API provides two methods for accessing data: Server Mode and Multi-
User Mode. (See the Server API Product Overview.)

Server Mode

The following questions should be answered if you are implementing this method for
retrieving data, otherwise check “Not Applicable”

1. Using the Server API Tool Set, will your application verify each ‰ Yes ‰ No
“Bloomberg User's” data entitlements prior to receiving data from
the Server API? ‰ Not Applicable

2. If user entitlements are inadequate will your application block that ‰ Yes ‰ No
user from receiving data from the Server API?

Multi-User Mode

The following question should be answered if you are implementing this method for retrieving
data, otherwise check “Not Applicable”.

1. Will each user connect to Bloomberg and receive data from ‰ Yes ‰ No
Bloomberg individually, with no data sharing or storage in a central
database? ‰ Not Applicable

For 24 hour global customer support call +1 212 318 2000, +44 20 7330 7500, +65 6212 1000,
+81 3 3201 8900 or press the HELP key twice on the BLOOMBERG PROFESSIONAL® service.