Digital Dashboard Resource Kit 2.0 Readme
July 2000 - CD Refresh
© 2000 Microsoft Corporation. All rights reserved.
includes updated information for the Digital Dashboard Resource Kit 2.0.
- What's New in this CD Refresh
- Before You Install
- SQL Server Digital Dashboard Sample
- Microsoft Windows File System Digital
- Digital Dashboard Services Component (DDSC)
- Web Part Builder
What's New in this CD Refresh
- Digital Dashboard Service Component (DDSC)
- The ItemCollection object is
a new collection added to the object model. It provides programmatic
access to items that are contained by a parent item.
- Administration Sample Dashboards
- DDSC support is now
available on Administration sample dashboards, making the Administration
samples even better examples of how to build digital dashboards.
- Double Byte Characters
(DBCS) are now supported. You now have the ability to develop parts and
dashboards using multi-language character sets.
- Minimize and Remove
functionality that is included in the HTML files generated by the
dashboard factory is now provided by the DDSC.
- Web Part Catalog server in SQL Server Digital
- Security enforcement now
supports inherited security rights. For more information about inherited
security, see Windows 2000 online help.
- Setup Program for SQL Server Digital Dashboard
- Database creation is now
supported during installation. You no longer have to create a database
before running Setup, or interrupt installation to create a database for
storing dashboard data.
- Web Part Catalog database upgrades are now supported for
an existing installations. Existing dashboard and part definitions are
automatically migrated to new database formats when you install newer
versions of the SQL Server Digital Dashboard.
Before You Install
- You should always back up your IIS Metabase
before running an install. The metabase can be found in the
WINNT\System32\INETSRV directory and is called metabase.bin. If there is a
problem with setup and the metabase corrupts, you can restore it with this
- The digital dashboard samples of the DDRK 2.0
use the XMLHttpRequest object to process certain requests for content on
the server. The XMLHttpRequest object uses Wininet to process the request
on the server, however, Wininet was designed to be run in a client side
process. When run in a protected server service, certain functions of
WinInet can be degraded including access to http sites. This object is used to get content for a
web part with the following settings: a ContentLink with RequiresIsolation
- The Administration dashboard requires IE5.01
on windows 98 to be viewed correctly.
- Setup should not
be run when a machine is offline. Setup requires that 1) a user be properly
authenticated and 2) that IP resolution is available. If you receive an
error during setup, and the welcome dashboard does not render properly,
rerun setup when you have network connectivity.
SQL Server Digital Dashboard
- After performing an upgrade from previous
versions make sure to check all security settings. In certain cases the
security settings may change.
- Installing SQL Server Digital Dashboard to any
Web site that is not on port 80 returns error "403: Forbidden"
when you subsequently retrieve and save parts to the Web site after
installation completes. If you want to use a nondefault Web site, be sure
to assign it to port number 80.
- Setup fails on standalone PCs running
Microsoft Windows 2000 Professional that are isolated from the network. To
continue, add 127.0.0.1 MyComputerName to the following file:
- SQL Server Web Part catalog requires a user
login with special privileges to support a database connection. If login
permission is insufficient, the following error occurs: "Internal
server error 500". Before you install, create a database, then define
a user login for that database that has Administrator privileges. During
installation, you must specify the user login values. Setup provides a
page for specifying the SQL Server name, the authentication mode, and the
Username, Domain, and Password. The Username, Domain, and Password values
must be those of the user login you created for the database. The values
that you enter are not validated or verified during Setup. The
values that you enter are used at run time only. If you enter an incorrect
login value during Setup, it will not be detected until run time, at which
point access will be denied. To correct for this, rerun Setup and enter
the correct login values.
- HTTP 1.1 is required. You can enable HTTP 1.1
in Internet Explorer by clicking Internet Options on the Tools menu, and
then clicking Advanced. Scroll to HTTP 1.1 Settings, then select "Use
- Web Parts with embedded or non-isolated linked
content cannot contain relative links to support files such as GIFs.
- Do not use the % character in Dashboard or Web
Part names. Manipulating a dashboard or part that includes this character
in the name can affect other dashboards that reside at an equal or lower
level in the hierarchy.
- The masterPart link must be in the following
Microsoft Windows 2000 File System Web Store
- The masterPart link must be in the following
form WebPartID=http://myserver/dashboards/mydashboard/my part.htm
- There are a number of important notes to the
MasterPart behavior on the file system digital dashboard sample
- The Master Web Part MUST be
a Web Part in the store, it cannot be a .dwp file.
- A child Web Part can only
link to a master Web Part residing on the same store.
- A master Web Part and its
child Web Part cannot reside on the same dashboard
- There are a variety of caching strategies for
IIS. Your caching strategy for the dashboard factory can have a significant
effect on the behavior of the dashboard. Because the dashboard is so
dynamic, it is recommended that you use a minimalist caching strategy.
- Web Parts with embedded or non-isolated
linked content cannot contain relative links to support files such as Gifs.
- Notes on using Double Byte Character Systems.
- Whenever possible, you should
match your client and server operating server languages
- Non-Unicode servers (such as US
English) will not accept a new dashboard or Web Part name with Double Byte
Digital Dashboard Services
- The DDSC does not work with IFrames. If you
create an isolated Web Part, you cannot use the DDSC on the dashboard that
contains that Web Part.
The Web Part Builder Add-in for Visual
- You cannot use the Web Part builder when
Visual InterDev is in local mode
- Visual InterDev could experience difficulties
with the following actions. These difficulties are NOT effects from the
Web Part Builder.
- Frequent refreshes of the
- Connecting to a local server
and then to a remote server in the same session can cause Visual InterDev
- Visual InterDev uses the UCS2 encoding for Unicode and cannot properly
process Unicode in the UTF-8 format. The dashboard will read UCS2 encoded
files but saves its files as UTF-8. For this reason, you my see some
instances when Visual InterDev improperly interprets the content element
of a Web Part Created in the dashboard.