TWS InstallationGuide

Team Workspace Desktop TM
Installation Guide
2006 Landmark Graphics Corporation
Part No. 160549 R2003.18.1.0 January 2006

2006 Landmark Graphics Corporation
All Rights Reserved Worldwide
This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also protected by
Federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system,
or translated into any human or computer language, in any form or by any means, electronic, magnetic, manual, or otherwise, or
disclosed to third parties without the express written permission of:
Halliburton Digital and Consulting Solutions

Landmark Graphics Corporation
Building 1, Suite 200, 2101 CityWest, Houston, Texas 77042, USA
P.O. Box 42806, Houston, Texas 77242, USA
Phone: 713-839-2000
Fax: 713-839-2401 Web: www.lgc.com
Trademark Notice
3DFS, 3D Drill View, 3D Drill View KM, 3DView, 3D Surveillance, Active Field Surveillance, Active Reservoir Surveillance,
ADC, Advanced Data Transfer, ARIES, Asset Development Center, AssetJournal, Asset Performance, AssetView, Atomic
Meshing, Automate, BLITZ, BLITZPAK, CasingSeat, COMPASS, Contouring Assistant, Corporate Data Archiver, Corporate
Data Store, DataManager, DataStar, DBPlot, DecisionSuite, Decisionarium, DecisionSpace, DecisionSpace AssetPlanner,
DecisionSpace AssetView, DecisionSpace Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace
Nexus, DecisionSpace PowerGrid, DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace Reservoir,
DecisionSpace TracPlanner, DecisionSpace Well Seismic Fusion, DepthTeam, DepthTeam Explorer, DepthTeam Express,
DepthTeam Extreme, DepthTeam Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery,
Discovery Asset, Drill-to-the-Earth Model, Drillability Suite, Drilling Desktop, DrillModel, DrillVision, DSS, Dynamic Reservoir
Management, Dynamic Surveillance System, EarthCube, EDM, eLandmark, Engineers Data Model, The Engineer's Desktop,
Engineers Link, Executive Assistant, ezFault, ezSurface, ezTracker, FG+, FastTrack, FieldWorks, FZAP!, GeoDataLoad,
GeoGraphix (stylized), GeoGraphix Exploration System, GeoLink, GeoProbe, GeoProbe GF DataServer, GES, GESXplorer,
GMAplus, GRIDGENR, Handheld Field Operator, I2 Enterprise, iDIMS, IsoMap, iWellFile, Landmark, Landmark & Design,
Landmark Logo & Design, Landmark Decision Center, Landscape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep,
Magic Earth, MagicDesk, Make Great Decisions, MathPack, MIMIC, MIMIC+, MIRA, Model Builder, MyLandmark, Nexus,
Object MP, OpenBooks, Open Explorer, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWorks, OpenWorks
Well File, PAL, Parallel-VIP, PetroBank, PetroWorks, PetroWorks ULTRA, PlotView, Point Gridding Plus, Pointing Dispatcher,
PostStack, PostStack ESP, PowerCalculator, PowerExplorer, PowerHub, Power Interpretation, PowerJournal, PowerModel,
PowerView, Presgraf, PRIZM, PROFILE, Project Administrator, ProMAGIC, ProMAGIC Connect, ProMAGIC Server, ProMAX,
ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP, pSTAx, Query Builder, Quick, Quick+,
QUICKDIF, QUIKCDP, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP, Quickwell, Quickwell+, RAVE, RayMap, RayMap+,
RTOC, Real Time Asset Management Center, Real Time Asset Management Centre, Real Time Knowledge Company, Real Time
Operations Center, Real Time Production Surveillance, Real Time Surveillance, Reference Data Manager, Reservoir Framework
Builder, RESev, ResMap, RightTime, RMS, SCAN, SeisCube, SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks,
SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerSection, SeisXchange, Sierra, Sierra (design),
SigmaView, SimResults, SIVA, SIVA+, smartSECTION, Spatializer, SpecDecomp, StrataAmp, StrataMap, StrataModel,
StrataSim, StratWorks, StressCheck, STRUCT, Surf & Connect, SynTool, SystemStart for Servers, SystemStart, SystemStart for
Clients, SystemStart for Storage, Tanks & Tubes, TDQ, Team Workspace, TERAS, Total Drilling Performance, TOW/cs, TOW/cs
Revenue Interface, TracPlanner, Trend Form Gridding, Turbo Synthetics, VESPA, VESPA+, VIP, VIP-COMP, VIP-CORE, VIP-
DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, Well Seismic Fusion,
Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN, WellXchange, WOW, Xsection, You're in
Control. Experience the difference, ZAP!, and Z-MAP Plus are trademarks, registered trademarks or service marks of Landmark
Graphics Corporation.
All other trademarks are the property of their respective owners.
Note
The information contained in this document is subject to change without notice and should not be construed as a commitment by
Landmark Graphics Corporation. Landmark Graphics Corporation assumes no responsibility for any error that may appear in this
manual. Some states or jurisdictions do not allow disclaimer of expressed or implied warranties in certain transactions; therefore,
this statement may not apply to you.
Landmark Graphics Corporation Team Workspace Desktop Installation Guide
Contents
Welcome ................................................................................................................................... 1
Team Workspace Desktop ....................................................................................................... 1
Documentation ................................................................................................................... 1
Code ................................................................................................................................... 1
Team Workspace Site Preparation ............................................................................. 3

The Team Workspace Site ....................................................................................................... 3
Windows Server 2003 ........................................................................................................ 3
General Site Requirements .......................................................................................... 3
Database Server Requirements .................................................................................... 4
Web Server Requirements ........................................................................................... 4
Citrix MetaFrame Server Requirements ...................................................................... 6
Windows 2000 Server ........................................................................................................ 6
General Site Requirements .......................................................................................... 6
Database Server Requirements .................................................................................... 7
Web Server Requirements ........................................................................................... 8
Citrix MetaFrame Server Requirements .................................................................... 10
Preparing to Install a Site........................................................................................................ 11
Active Directory .............................................................................................................. 11
Microsoft SQL Server Databases .................................................................................... 11
Shared Resources ............................................................................................................. 11
Internet Information Service Web Servers ...................................................................... 12
Installation Team ............................................................................................................. 12
Preview and Order Data from a Databank.............................................................................. 13
Bank Requirements .......................................................................................................... 13
Administration Tasks Before Installing ................................................................. 15

Enterprise Administrator Tasks ............................................................................................. 15
Skills Required ................................................................................................................. 15
Active Directory ........................................................................................................ 15
SQL Server ................................................................................................................ 15
Internet Information Server (IIS) ............................................................................... 15
Citrix MetaFrame (if used) ........................................................................................ 16
Install the Site Servers ............................................................................................................ 17
Create a Group for the Site Administrators ..................................................................... 18
Delegate Permissions to Site Administrators ................................................................... 18
Create the Team Workspace Site Organizational Unit .................................................... 19
Citrix Administrative Permissions ................................................................................... 20
R 2003.18.1.0 Contents iii

Team Workspace Desktop Installation Guide Landmark Graphics Corporation
Site Administrator Tasks ........................................................................................................ 21

Required Skills ................................................................................................................. 21
Check Information From Enterprise Administrator ......................................................... 21
Install Team Workspace ................................................................................................. 23

Installation Overview ............................................................................................................. 23
Database Server ............................................................................................................... 23
Administration Tool ................................................................................................... 24
Web Server ...................................................................................................................... 24
Installation Prerequisites......................................................................................................... 25
Create File Shares ............................................................................................................ 25
Microsoft .NET Framework and MDAC on a Web Server ............................................. 26
Install MDAC and .NET Framework (Windows 2000) ........................................... 26
Configure .NET Framework the Servers (Windows 2000 and Windows Server 2003) .
27
Install Web Services Enhancements for Microsoft .NET (Windows 2000 and Windows
Server 2003) - Team Workspace Web Server Only ........................................................ 30
Windows Registry Changes for Windows 2000 .............................................................. 31
Change the Registry ................................................................................................... 31
Install Landmarks License Application Manager.................................................................. 33
Obtain a Server License File ...................................................................................... 33
Install LAM Server .................................................................................................... 34
LAM Server Initial Startup ........................................................................................ 35
LAM Technical Notes ............................................................................................... 37
Using LAM Server Without NT Service ............................................................. 37
If Applications Cannot Find License File ............................................................ 37
Install Team Workspace ......................................................................................................... 38
Prerequisites ..................................................................................................................... 38
Installation Steps .............................................................................................................. 38
Install the Team Workspace Site (or Database Server) ............................................. 39
Create the Team Workspace Site ......................................................................... 42
Install the Team Workspace Web Server .................................................................. 43
Finish the Web Server Installation ....................................................................... 44
Team Workspace Settings ............................................................................................... 46
The Variables for a Site ............................................................................................. 46
Notes on Editing ixSiteVariables.JS .......................................................................... 51
Editing the File ........................................................................................................... 52
Changing Site Variables After Creating a Site ................................................................ 53
Upgrade Team Workspace 2003.13.3..................................................................................... 55
Prerequisite for Version 2003.18.1 .................................................................................. 55
Upgrade from Version 2003.13.3 to 2003.18.1 ............................................................... 56
Before Upgrading ...................................................................................................... 57
Upgrade the Team Workspace Site (or Database Server) ......................................... 58
Upgrade the Team Workspace Web Server ............................................................... 65
After Upgrading the Site .................................................................................................. 69
iv Contents R 2003.18.1.0
GIS Map Configuration ............................................................................................. 69

Adding An Additional Web Server to a Site .......................................................................... 70
Prerequisites ..................................................................................................................... 70
Installation Procedure for An Additional Web Server ..................................................... 70
Other Administration Tasks ......................................................................................... 73

Uninstalling Release 2003.18.1.0 .......................................................................................... 73
Web Server Uninstallation ............................................................................................... 73
Database/File Server Uninstallation ................................................................................ 75
R 2003.18.1.0 Contents v
vi Contents R 2003.18.1.0
Welcome
Team Workspace Desktop is a light-weight technical portal that allows

you to access the data and information you need. With it, separate
workspaces or projects can be created for the various tasks assigned to
you or a team. Each project can be configured to contain only the data
and information pertinent to a task.
This Installation Guide will help you install a Team Workspace site in
your computing environment.
Team Workspace Desktop
Documentation
The documentation is available on the Team Workspace installation CD
in the Documentation folder at the root of the CD.
Team Workspace Release Notes (TWS_ReleaseNotes.PDF)
Team Workspace Installation Guide

(TWS_InstallationGuide.PDF)
Team Workspace Online Help (OnlineHelp.HTM)
Code
Pre-requisites which must be installed before Team Workspace
will function correctly. These files are in
CD_DriveLetter:\TWprereq on the Team Workspace
installation CD-ROM.
Team Workspace files.
Third Party Software for Team Workspace.
R 2003.18.1.0 Welcome: Team Workspace Desktop 1

2 Welcome: Team Workspace Desktop R 2003.18.1.0

Team Workspace Site Preparation
The Team Workspace Site
A Team Workspace site is a collection of servers on which the Team

Workspace web site and its underlying components reside. Some of
those components are databases and shared resources, such as folders
and files. A server in a Team Workspace site can have the
Windows 2000 Server (Service Pack 4) operating system or the
Windows Server 2003 (Service Pack 1) operation system. The
components of the basic Team Workspace site vary depending on the
operating system. The requirements for each operating system are
delineated in the following subsections.
Windows Server 2003
General Site Requirements

Microsoft Windows Server 2003 Standard Edition (Service
Pack 1) operating system. If clustered servers or load balanced
web farms are required, Microsoft Windows Server 2003
Enterprise (Service Pack 1) operating system is required.
Active Directory domain installed and running in Native mode.
Active Directory organizational unit (OU) created for the Team

Workspace site, and Full Control permissions on the OU delegated
to the account that Team Workspace Site Administrators use.
All servers must use English (United States) as the default

language in the regional and language options. The language can
be set on the Region Options and Language tabs in the Regional
And Language Options control panel.
Landmark License Application Manager 2003 (LAM) server with

a valid license from Landmark Graphics Corporation.
R 2003.18.1.0 Team Workspace Site Preparation: The Team Workspace Site 3

Database Server Requirements

The Team Workspace database server requires Microsoft SQL
Server 2000 Service Pack 3a, running in Integrated Security mode
(recommend using only TCP/IP, not Named Pipes, to
communicate with clients).
The IIS Common Files component must be installed on the system

where SQL Server is installed. These files are required by the
TWAdmin tool.
In Windows Server 2003, the Common Files component is not

installed as a default, and it is a subcomponent of the Internet
Information Services (IIS) component. It is available through the
Add Or Remove Programs control panel and its Add/Remove
Windows Component Wizard.
For example, to add the Common Files, in the Windows

Component Wizard dialog, double-click the Application Server
component to display the Application Server dialog, double-click
the Internet Information Services (IIS) component to display the
Internet Information Services (IIS) dialog, and then check the
Common Files component. Click OK in each dialog to save your
change.
Shared folder for the system files Team Workspace (twsource),

workspace data (twdata), and third-party applications
(tw3rdparty) used by Team Workspace. These shared folders
are usually located on a Team Workspace file server, usually the
server with the Microsoft SQL database.
Web Server Requirements

Microsoft Internet Information Service (IIS) 6.0 web server
installed with the ASP.NET component.
In Windows Server 2003, the ASP.NET component is not installed

as a default. The ASP.NET component is a subcomponent of the
Application Server component. The component is available
through the Add Or Remove Programs control panel and its Add/
Remove Windows Component Wizard.
For example, to add the ASP.NET component, in the Windows

Components Wizard dialog, double-click the Application Server
component to display the Application Server dialog. In the
4 Team Workspace Site Preparation: The Team Workspace Site R 2003.18.1.0

Application Server dialog, check ASP.NET. Click OK in each

dialog to save your changes.
If workspaces will send email notifications, the Simple Mail

Transfer Protocol (SMTP) service must be installed with the web
server of the Microsoft Internet Information Services.
Team Workspace requires that valid SSL certificates be installed

on each web server. If you have a certificate server installed, you
are able to create your own SSL certificates. Otherwise SSL
certificates must be purchased from a Certificate Authority
(namely, Verisign or Thawte).
A Machine Code Group in the Runtime Security Policy branch of

the .NET Framework Configuration console for the Team
Workspace twsource share name. For more information,
see Configure .NET Framework the Servers (Windows 2000 and
Windows Server 2003) on page 27.
The WebServerName\Users group should have Full Control

permissions over the Temporary ASP.NET Files folder in the .NET
Framework installation folder. For more information,
Web Services Enhancements for Microsoft .NET (WSE) 2.0,

Service Pack 1. If you need to install version 2.0, Service Pack 1,
the installation file, Microsoft WSE 2.0 SP1.MSI, is
located in CD_DriveLetter:\twprereq\W2K3\dotnet .
If workspaces will access an Oracle database, Oracle Client 9.2.0.x

installed. The client is available from Oracle.
Oracle Client Included with OpenWorks
If you have purchased OpenWorks and received Oracle software with your
purchase, your license with Landmark Graphics Corporation, and through
Landmark, your license for the Oracle software, does not allow you to use
that Oracle Client with Team Workspace. You must purchase a license for
the Oracle software separately from your OpenWorks purchase in order to
use the Oracle Client with Team Workspace.
If workspaces will access an Oracle database, Oracle Provider for

OLE DB installed. The version of the Oracle Provider should be of
the same release as the Oracle Client. The Oracle Provider is
available from Oracle.

If workspaces will use a Citrix MetaFrame server, the ASP.NET

component must be installed, and then Microsoft Visual J# .NET
Redistributable Package, version 1.1 (vjredist1.1.EXE) must
be installed.
The ASP.NET component is available through the Add Or Remove

Programs control panel and its Add/Remove Windows Component
Wizard.
The installation program for Visual J# .NET is located in

CD_DriveLetter:\twprereq\W2K3\citrix .
Installation Order
The ASP.NET component must be installed before Microsoft Visual

J# .NET Redistributable Package is installed.
If a workspace has the Team Workspace export application

configured in order to export data from a catalog, Crystal
Reports XI, Developer Edition, from Business Objects SA
(www.businessobjects.com) must be installed.
Also, the local Users group on the web server must be granted the
Modify permission over the Temp folder in the root of the
system folder. The path name of this folder is contained in
the %SystemRoot% environment variable (typically,
c:\Windows).
Citrix MetaFrame Server Requirements

If Team Workspace will access applications from a Citrix
MetaFrame Server, Citrix MetaFrame XP (Feature Release 3), or
higher is required. For further information, see Citrix Systems, Inc.
Windows 2000 Server
General Site Requirements

Microsoft Windows 2000 Server operating system (Service
Pack 4). If clustered servers or load balanced web farms are
required, Microsoft Windows 2000 Advanced Server operating
system (Service Pack 4) is required.

Active Directory domain installed and running in Native mode.
Active Directory organizational unit (OU) created for the Team

Workspace site, and permissions on the OU delegated to the
account that Team Workspace Site Administrators use.
The OU must be configured to allow the Team Workspace

Administrator to have the Full Control permission over the OU.
All servers must use English (United States) as the default

language in the regional options. The language can be set on the
General and Input Locales tabs in the Regional Options control
panel.
Microsoft .NET Framework 1.1, Service Pack 1. If you need to

install version 1.1, the installation file, DotNetFx1.1.EXE, is
located in CD_DriveLetter:\twprereq\W2K\dotnet . The
folder also contains the installation file for the service pack,
DotNet1.1SP1.exe .
Microsoft XML Parser version 3.0, Service Pack 2, or later

installed. If you need to install this version, the installation file,
msxml3sp2Setup.exe, is located in
CD_DriveLetter:\twprereq\W2K\msxml . A version of the
XML Parser is included in a number of Microsoft products (such
as MDAC and Internet Explorer) and security patches.
Windows Scripting Engine version 5.6, or later, installed. If you

need to install this version, the installation file, ScriptEn56.EXE,
is located in CD_DriveLetter:\twprereq\W2K\scripten .
Microsoft Data Access Components (MDAC) 2.7, Service Pack 1,

installed. If you need to install this version, the installation file,
Mdac_Typ_2.7SP1.EXE, is located in
CD_DriveLetter:\twprereq\W2K\mdac . This version is
included with the installation of Service Pack 3a for Microsoft
SQL Server 2000.
Landmark License Application Manager 2003 (LAM) server with

a valid license from Landmark Graphics Corporation.
Database Server Requirements

The Team Workspace database server requires Microsoft SQL
Server 2000 Service Pack 3a, running in Integrated Security mode

(recommend using only TCP/IP, not Named Pipes, to

communicate with clients).
Shared folder for the system files Team Workspace (twsource),

workspace data (twdata), and third-party applications
(tw3rdparty) used by Team Workspace. These shared folders
are usually located on a Team Workspace file server, usually the
server with the Microsoft SQL database.
The TWAdmin console requires the Windows Administration

Tools (AdminPak.MSI).

Web Server Requirements

installed.
If workspaces will send email notifications, the Simple Mail

Transfer Protocol (SMTP) service must be installed with the web
server of the Microsoft Internet Information Services.
Team Workspace requires that valid SSL certificates be installed

on each web server. If the customer has their own certificate server
installed, they can create their own SSL certificates. Otherwise
SSL certificates must be purchased from a Certificate Authority
(namely, Verisign or Thawte).

The WebServerName\Users group should have Full Control

permissions over the Temporary ASP.NET Files folder in the .NET
Framework installation folder. For more information,

Web Services Enhancements for Microsoft .NET (WSE) 2.0,

Service Pack 1. If you need to install version 2.0, Service Pack 1,
the installation file, Microsoft WSE 2.0 SP1.MSI, is
located in CD_DriveLetter:\twprereq\W2K\dotnet .
If workspaces will access an Oracle database, Oracle Client 8.1.7

or 9.2.0.x installed. The client is available from Oracle.
Oracle Databases with Data Encoded as Unicode Characters
If the data in the Oracle database is encoded as Unicode characters (not

encodings such as ISO/IEC 8859-x or ASCII characters), Oracle
Client 9.2.0.x must be installed.
Oracle Client Included with OpenWorks
If you have purchased OpenWorks and received Oracle software with your
purchase, your license with Landmark Graphics Corporation, and through
Landmark, your license for the Oracle software, does not allow you to use
that Oracle Client with Team Workspace. You must purchase a license for
the Oracle software separately from your OpenWorks purchase in order to
use the Oracle Client with Team Workspace.
If workspaces will access an Oracle database, Oracle Provider for

OLE DB must be installed. The version of the Oracle Provider
should be of the same release as the Oracle Client. The Oracle
Provider is available from Oracle.
If workspaces will use a Citrix MetaFrame server, Microsoft

Visual J# .NET Redistributable Package, version 1.1
(vjredist1.1.EXE) must be installed after Microsoft .NET
Framework 1.1.
The installation program for Visual J# .NET is located in

CD_DriveLetter:\twprereq\W2K\citrix .
Installation Order
Microsoft .NET Framework 1.1 must be installed before Microsoft Visual

J# .NET Redistributable Package is installed.
If a workspace has the export application configured in it in order

to export data from a catalog, Crystal Reports XI, Developer

Edition, from Business Objects SA

(www.businessobjects.com) must be installed.
Also, the local Users group on the web server must be granted
Modify permission over the Temp folder in c:\Documents
and Settings\WebServerName\ASPNET\Local
Settings .
Citrix MetaFrame Server Requirements

If Team Workspace will access applications from a Citrix
MetaFrame Server, Citrix MetaFrame XP (Feature Release 3), or
higher is required. For further information, see Citrix Systems, Inc.

Preparing to Install a Site
Active Directory
Team Workspace web, file, and database servers must be members of
an Active Directory domain. This domain must be in Native mode (not
Mixed mode), since Team Workspace takes advantage of the ability to
nest Domain Local groups, which is only available once your domain
has been moved to Native mode. Only users in the same Active
Directory forest as the domain in which Team Workspace is installed
can have their user accounts added to Team Workspace.
An organizational unit (OU) must be created for the Team Workspace

site in the same domain as the Team Workspace servers, and full
permissions of this unit must be delegated to the Team Workspace site
administrators. Team Workspace will create other OUs and Domain
Local groups within the main organizational unit, and will use these
groups to control access to the Team Workspace infrastructure
components.
Microsoft SQL Server Databases

Team Workspace uses Microsoft SQL Server for its databases. Team
Workspace will create one database for the site, and an additional
database per workspace.
Team Workspace accesses the database using Windows NT Integrated

Security. For security reasons, Landmark recommends Microsoft SQL
Server be installed in Integrated Security mode only, and that it should
only use TCP/IP, not Named Pipes, to communicate with clients.
For scalability and availability, the Team Workspace SQL Server

databases can be installed on a Windows 2000 Advanced Server cluster
or a Windows Server 2003, Enterprise Edition, cluster.
Shared Resources
Team Workspace requires file shares for the Team Workspace code, for
some additional components, and for storing Team Workspace data.
Team Workspace secures all data at the file system level.
R 2003.18.1.0 Team Workspace Site Preparation: Preparing to Install a Site 11

The shared Team Workspace data (shared in the twdata folder)

should be set up so that all users have full access. Team Workspace sets
NTFS permissions; therefore, the Full Control permission, rather than
the Change permission, should be used on the shared folder. The Team
Workspace shared files can be stored on network attached storage
(NAS) devices, if desired.
Internet Information Service Web Servers

Team Workspace uses Microsoft Internet Information Service (IIS)
web server, version 5.0, in Windows 2000 Server or uses version 6.0 of
IIS web server in Windows Server 2003. Users log into the web server
with an Active Directory user account, using Basic Authentication over
Secured Sockets Layer (SSL).
Installation Team
Installing a Team Workspace site requires steps to be performed by two
types of administrator, which shall be referred to as the Site
Administrator and the Enterprise Administrator.
The Enterprise Administrator is a user with administrative

permissions to the Enterprise IT infrastructure. The central IT
department usually retains this role.
The Site Administrator is a user with administrative permissions to

the servers within the Team Workspace site, and also full permissions
to the Active Directory organizational unit of the Team Workspace Site.
In some organizations, a single group or user will carry out both of

these tasks. However, in most cases, two distinct groups will be
involved in a Team Workspace site installation.
12 Team Workspace Site Preparation: Preparing to Install a Site R 2003.18.1.0

Preview and Order Data from a Databank
Team Workspace 2003.18.1.0 allows you to preview and order data

from a data bank. The data bank must run Landmarks PetroBank
Master Data Store (MDS) with PowerHub and Power Explorer. Team
Workspace can view and order log curves, seismic sections, and archive
object documents.
Bank Requirements
Team Workspace 2003.18.1.0 requires the following components and
versions of components at the data bank to be able to preview or order
data:
PetroBank Master Data Store 2003.18.0
Refer to the MDS documentation for more information about

patches to MDS and other requirements.
MDS RMI server 2003.18.0 must be installed and started by a

Unix user with access to all the directories containing the data
available to a user in Team Workspace.
For a client to preview log curves, the MDS RMI server must
mount the directory where RECALL data is stored on the
RECALL server.
For a client to preview archive object documents, the MDS

RMI server must mount the file system where the document
files are stored.
For a client to preview sections in a seismic project, an MDS

administrator must create a graphic file (usually in JPEG
format) for each seismic section. The MDS RMI server must
mount the base directory where the graphic files are stored.
The default location is /data/images on the MDS
server. Typically, with 3D seismic projects, seismic images
are generated for only a subset of the sections.
Power Explorer 2003.18.1
PowerHub 2003.18.1 (both its server and web services)
R 2003.18.1.0 Team Workspace Site Preparation: Preview and Order Data from a Databank 13
14 Team Workspace Site Preparation: Preview and Order Data from a Databank R 2003.18.1.0
Administration Tasks Before Installing
Enterprise Administrator Tasks
Skills Required
The Enterprise Administrator should have high-level infrastructure
skills, including but not limited to:
Active Directory
High-level of experience and knowledge working with Active
Directory.
Ability to identify the mode of a domain, Mixed or Native; to

understand the difference between the two; and, if necessary,
change a domain to Native mode.
Ability to create and manage organizational units (OUs), including

the delegation of administrative rights on OUs.
Ability to manage group policies.
SQL Server
Ability to install and configure Microsoft SQL Server.
Ability to configure authentication and connection settings.
Internet Information Server (IIS)

Experience and knowledge of Internet Services Manager.
Ability to install and configure SSL certificates.
If workspaces will send email notifications, experience and

knowledge of the Simple Mail Transfer Protocol (SMTP) service.
R 2003.18.1.0 Administration Tasks Before Installing: Enterprise Administrator Tasks 15

Citrix MetaFrame (if used)

Experience and knowledge of the Citrix Management console. In
particular, the delegation of permissions.
16 Administration Tasks Before Installing: Enterprise Administrator Tasks R 2003.18.1.0

Install the Site Servers
Team Workspace can be installed on a single computer (server) if

required, but such a configuration is not recommended. Normally,
Team Workspace should be installed over a number of computers
(servers).
1. Determine the number of computers required and their

configuration. Minimally for Team Workspace, the following
computers are normally required loaded with various server
applications:
At least one server running Internet Information Service (IIS).

IIS must have a valid Secured Sockets Layer (SSL) certificate
installed as well as other configurations. For more information
about the other configurations, see Microsoft .NET
Framework and MDAC on a Web Server on page 26.
At least one server running Microsoft SQL Database Server.
Database with the Name tw__site
When installing Team Workspace for the first time in a site, the SQL
database must not have a database with the name tw__site (that is
tw followed by two underscore characters and the word site).
If tw__site exists as a database, the installation will fail.
At least one server containing the shared folders for Team

Workspace. For more information about the shared folders,
see Create File Shares on page 25.
At least one Active Directory domain controller must exist in

the domain in which the Team Workspace site (web, database,
and file servers) exists. The domain must be running in Native
Mode.
R 2003.18.1.0 Administration Tasks Before Installing: Install the Site Servers 17

2. Install the required servers and join them to the domain.
Information for the Site Administrator of Team Workspace
The Enterprise Administrator should pass the following information to the

Site Administrator of Team Workspace:
Provide the name of the server running the SQL Server; or if the SQL
Server is running on a cluster, provide the SQL Server cluster name.
Provide the name of the server on which the shared folders should be
located. If the server is a network attached storage device (NAS), the
device must support the Common Internet File System (CIFS)
protocol and must be a member of the Active Directory Domain.
Provide the names of each web server.
Provide the web site number or ID (for example, 1 ) of the web

server that will run the Team Workspace web site on the computer.
The Windows script, FindWeb.VBS, can help you retrieve
information about your web site. It is typically located in
C:\Inetpub\AdminScripts. The script provides the following
information about the web site: web site number (or server number),
web site description (or server description), server host name, its port
number, and its IP address. For more information, see
http://localhost/iisHelp/ .
Create a Group for the Site Administrators

The Site Administrators, who will be creating the Team Workspace site
and subsequent workspaces, will require administrative permissions to
the servers in the Team Workspace site and to an organizational unit,
which you create and delegate to them.
Landmark recommends that you create a group to delegate these

permissions. All Site Administrators should be members of this group.
The Enterprise Administrator should pass to the Site Administrator of Team

Workspace the name of the group that grants Site Administrator access to the site.
Delegate Permissions to Site Administrators

Use the group created in the previous section to grant administrative
privileges to the Team Workspace Site Administrators on all of the
18 Administration Tasks Before Installing: Install the Site Servers R 2003.18.1.0

following servers. The Site Administrators will require administrative

permissions to the following:
Microsoft SQL Servers

Web Servers
Shared folders on the file server
Create the Team Workspace Site Organizational Unit

Team Workspace requires an organizational unit (OU) to be created in
the domain that the Team Workspace servers are in. This organizational
unit can be named whatever you want, but something descriptive is a
good practice. If many Team Workspace sites are to be installed in this
domain, you may choose to make a new application OU to function as a
container for the OUs of all of the Team Workspace sites. For example,
the name of the application OU may be TeamWorkspace . Then,
each of the Team Workspace sites would be given an OU, which may
be the city where the site is located (for example, Aberdeen).
Team Workspace Site Administrators will need permissions to:
Create OUs under the Team Workspace Site OU. One OU per
Workspace.
Set permissions on the Workspace OUs as required by Team

Workspace.
Delete OUs, when deleting workspaces.
Delegate full administrative rights to the Team Workspace OUs to the

group you created for Site Administrators.
The Enterprise Administrator should pass to the Site Administrator of Team Workspace,
the LDAP distinguished name (not the canonical name) of the organizational unit created
for the Team Workspace site. For example, given a container OU of TeamWorkspace,
a Team Workspace site in Aberdeen would have a name similar to the following:
ou=Aberdeen,ou=TeamWorkspace,dc=MyDomain,dc=com
R 2003.18.1.0 Administration Tasks Before Installing: Install the Site Servers 19

Citrix Administrative Permissions

If Team Workspace will publish Citrix MetaFrame applications, the
Site Administrators will require permissions to update the list of users
who can run the Citrix applications. Using the Citrix Management
console, assign Citrix Administrator permissions to the group you
created for the Team Workspace Site Administrators.
20 Administration Tasks Before Installing: Install the Site Servers R 2003.18.1.0

Site Administrator Tasks
Required Skills
Site Administrators do not require the same detailed technical
knowledge of the Team Workspace infrastructure components as the
Enterprise Administrators; however, Site Administrators should have
the following knowledge:
Basic knowledge of Active Directory; Microsoft SQL Server;

Internet Information Service (IIS); and Citrix MetaFrame, if used.
Ability to manage file and share permissions on CIFS and NTFS

volumes.
Ability to create and delete Active Directory OUs.
Familiarity with the Active Directory Users & Computers console.
Familiarity with the Internet Services Manager console.
Familiarity with the SQL Server Enterprise Manager console.
Check Information From Enterprise Administrator

The Enterprise Administrator should have passed the following
information to the Site Administrator:
Name of the server running SQL Server; or if running the SQL

Server is on a cluster, the SQL Server cluster name.
Name of the server, or of a network attached storage device, on

which the file shares should be located.
Name of each of the web servers that will run the Team Workspace
website.
The web site ID of the web server that will run the Team
Workspace web site.
Name of the group that grants Site Administrator access to the site.
R 2003.18.1.0 Administration Tasks Before Installing: Site Administrator Tasks 21

The LDAP distinguished name (not the canonical name) of the

organizational unit for the Team Workspace site.
To check that the above information is valid:
1. Log on with your administrative account.
2. Use the Active Directory Users and Computers console to confirm

that you have full permissions to the organizational unit for the
Team Workspace site. For instance, try creating an OU under it,
and then delete it.
3. Note the Pre-Windows 2000 name of the domain that the site OU
is in.
4. Note the Pre-Windows 2000 name of the group that grants Site
Administrator access.
5. Check that you have administrative rights on all web servers, and
that all have IIS installed with a valid SSL Certificate.
6. Check that you have administrative rights on the SQL Server and
that SQL Server is installed and running.
7. Check that you have access to the file shares that Team Workspace
requires, and that you have full control of these. For instance, try
creating a file or folder and setting its permissions.
22 Administration Tasks Before Installing: Site Administrator Tasks R 2003.18.1.0

Install Team Workspace
The procedures in this chapter guide you through the installation of

Team Workspace 2003.18.1 as a new Team Workspace site or as an
upgrade of an existing site (version 2003.13.3 to 2003.18.1).
This chapter contains the following:
Installation Overview (page 23)
Installation Prerequisites (page 25)
Install Landmarks License Application Manager (page 33)
Install Team Workspace (page 38)
Upgrade Team Workspace 2003.13.3 (page 55)
Adding An Additional Web Server to a Site, if needed (page 70)
Installation Overview
The site of Team Workspace 2003.18.1 consists of:
Team Workspace Database Server
Team Workspace Web Server
Database Server
The Team Workspace files are typically copied to a computer where
Microsoft SQL Server is running; however, if you desire, the file server
and the database server can be separate computers. After registering
some components and configuring the contents of
ixSiteVariables.JS, you run a script which creates the Team
Workspace database. SQL Server must be running when the script is
executed. Besides creating the Team Workspace database, the script
configures Active Directory for the site.
R 2003.18.1.0 Install Team Workspace: Installation Overview 23

A Team Workspace database server must also have Microsoft .NET

Framework 1.1.
Administration Tool
The Team Workspace Administration Tool (TWAdmin console) is a
Microsoft Management Console (MMC) snap-in. It allows a Team
Workspace site administrator to administer workspaces and the users of
workspaces. With workspaces, the administrator can create and delete
them. With users, the administrator can add and remove users from a
workspace and set the users default role in the workspace.
As a part of the installation of Team Workspace, the TWAdmin console

files are copied to the computer and then registered.
The TWAdmin console in the Windows 2000 operating system requires

the Windows Administration Tools (AdminPak.MSI). For more
information, see the Microsoft Knowledge Base Article 269483
or 314978. In the Windows Server 2003 operating system, the
TWAdmin console requires the Common Files component. This
component is a part of the Internet Information Services component,
which is a part of the Application Server component of the operating
system.
Web Server
The Team Workspace web server should only be created after the Team
Workspace file server and database have been created. If the Team
Workspace site uses more than one web server, you must create the
Team Workspace web server on each web server. A Team Workspace
web server must also have Microsoft .NET Framework 1.1 and Web
Services Enhancements for Microsoft .NET 2.0 installed.
When the Team Workspace web server is created, custom error files,
password changer files, and program files are copied to the computer.
24 Install Team Workspace: Installation Overview R 2003.18.1.0

Installation Prerequisites
Whether you are upgrading a Team Workspace site or are creating a

new site, these installation procedures presume all required Team
Workspace site servers have been configured by the Enterprise
Administrator as indicated in the previous chapter, Administration
Tasks Before Installing on page 15. It also presumes that you have
validated the information from the Enterprise Administrator, as
specified in the section, Site Administrator Tasks on page 21.
A Team Workspace site requires a number of servers (database, file,

and web servers). The requirements for a server differ depending on the
operating system and its purpose. See the following for more
information:
For a Windows Server 2003, see Windows Server 2003 on

page 3.
For a Windows 2000 server, see Windows 2000 Server on

page 6.
Create File Shares

On the file server, create the following folders with the following share
names and permissions:
Folder Name Share Name Share Permissions

twsource twsource Local Users: Check the Allow box for
only the Read permission.
tw3rdparty tw3rdparty
Local Administrators: Check the Allow
box for the Full Control permission.
Checking that box also checks the boxes
for the Change and Read permissions.
twdata twdata Everyone: Check the Allow box for the
Full Control permission. Checking that
box also checks the boxes for the Change
and Read permissions.
twdata\workspaces Do not share This subfolder should not need be
specifically shared.It should inherit the
configurations of the twdata folder.
dbs Do not share The dbs folder should not be shared.
This folder contains the files for the
Team Workspace database site and
workspace files (MDF and LDF files).
R 2003.18.1.0 Install Team Workspace: Installation Prerequisites 25

Microsoft .NET Framework and MDAC on a Web Server

The Team Workspace database and web servers must have
Microsoft .NET Framework 1.1 installed. On the web servers, .NET
Framework must also include Microsofts Web Service Enhancements
(WSE).
Microsoft Data Access Components (MDAC), .NET Framework, and

WSE are available from Microsoft, but for your convenience, they are
included on the Team Workspace installation CD.
Each web server in a Team Workspace installation must have the

following:
Installed MDAC. Unnecessary in Windows Server 2003.
Install .NET Framework 1.1. Unnecessary in Windows

Server 2003, but the ASP.NET component must be installed.
Configure .NET Framework for Team Workspace.
Install Microsoft Web Service Enhancements 2.0.
Install MDAC and .NET Framework (Windows 2000)

To install MDAC and .NET Framework in Windows 2000, do the
following on each web server:
1. Make sure that the latest security updates to Internet Information

Services version 5.0 have been installed. Microsofts Windows
Update web page can assist you in acquiring the latest updates. To
display the page, select Start > Windows Update, or enter
microsoft.com/WindowsUpdate in the Address text box
of the browser window to display the web page.
2. If the version of Microsoft Data Access Components (MDAC) is

older than version 2.7, Service Pack 1, install a newer version of
the components by installing MDAC_Typ_2.7SP1.EXE. The
installation program is located on the Team Workspace CD in
\TWprereq\W2K\mdac .
Follow the instructions of Microsofts installation program. Some

services, such as SQL Server, SQL Service Manager, and SNMP,
may need to be halted temporarily, or the system may need to be
rebooted after MDAC is installed.
26 Install Team Workspace: Installation Prerequisites R 2003.18.1.0

3. Again, check that the latest security patches for Microsoft Internet
Information Services (IIS) have been installed, and install them
before installing Microsoft .NET Framework 1.1.
4. Install .NET Framework 1.1 (DotNetFx1.1.EXE), following

the instructions of the installation program. The installation
program is located on the Team Workspace CD in
\TWprereq\W2K\dotnet.
5. Install Service Pack 1 for .NET Framework 1.1

(DotNet1.1SP1.EXE), following the instructions of the
installation program. The installation program is located on the
Team Workspace CD in \TWprereq\W2K\dotnet.
6. Follow the steps in Configure .NET Framework the Servers

(Windows 2000 and Windows Server 2003) to prepare .NET
Framework for Team Workspace.
7. Install Web Service Enhancements 2.0 Service Pack 1. Follow the

steps in Install Web Services Enhancements for Microsoft .NET
(Windows 2000 and Windows Server 2003) - Team Workspace
Web Server Only on page 30.
Configure .NET Framework the Servers (Windows 2000 and Windows

Server 2003)
After the Microsoft .NET Framework is installed, it must be configured
for Team Workspace to be able use it components. The .NET
Framework must be configured on each Team Workspace server:
database or web.
If Upgrading from 2003.13.3.0
On a web server, this procedure is only necessary if you are configuring Team
Workspace Release 2003.18.1 (and configuring .NET Framework for Team
Workspace) for the first time. If you are upgrading Team Workspace, the
configuration in this procedure should have already been done on the web server.
On a database server, this procedure must be done, since in Release 2003.18.1

this configuration is necessary for the TWAdmin tool. This procedure was not
required in the previous releases of Team Workspace.

To configure .NET Framework, do the following:
1. Create a security code group within .NET Framework to allow it to

execute ASPX files from shared folders.
Start the Microsoft .NET Framework 1.1 Configuration

console. The console is located in the Administrative Tools of
the Control Panel.
In the tree of the console, expand the tree to show the All_Code
branch (My Computer > Runtime Security Policy > Machine >
Code Groups).
Right-click All_Code to display a shortcut menu.
Select New in the shortcut menu to display the Create Code

Group dialog.
In the dialog, select the Create A New Code Group radio

button.
In the Name text box, type TWWebApps_Zone .
Click Next to display the Choose A Condition Type panel in

the dialog.
In the Choose The Condition Type drop-down list box, select

URL . A URL text box appears in the dialog.
Type the following in the URL text box:
file://FileServerName/twsource/*
where FileServerName is the host name or IP address of the

Team Workspace file server as indicated in the Internet
Services Manager console on the web server. The name used in
the URL should match the server name included in the path in
the Network Directory text box on the Home Directory tab in
the properties dialog for the Team Workspace web site (usually
the Default Web Site).
And, where the URL element twsource is the share name

of the folder created and configured previously in Create File
Shares on page 25.

Click Next. The Assign A Permission Set panel appears in the

dialog.
Select the Use Existing Permission Set radio button.
In the drop-down box, select FullTrust .
Click Next.
Click Finish.
Close the .NET Framework Configuration console.
2. If the server is a web server, change the security setting on

the .NET Framework folder as indicated below.
Navigate to the contents of the v1.1.4322 folder. For

example, the folder is located in the following path:
SystemRoot\Microsoft.NET\Framework\v1.1.4322
where SystemRoot is a path usually similar to c:\winnt or

c:\windows .
Right-click the Temporary ASP.NET Files folder to

display a shortcut menu. This folder is the output folder used
by the Just-In-Time compiler.
Select Properties in the shortcut menu.
Select the Security tab.
If the users group of the local web server

(WebServerName\Users) does not exist in the Name list box:
Click Add in the Properties dialog to display the Select

Users, Computers, Or Groups dialog.
Double-click Users in the Name list box of the Select

Users dialog.
Click OK to return to the Properties dialog.
Select Users (WebServerName\Users) in the Name list

box.

Check the Full Control check box
Click Apply in the Properties dialog.
Click OK to close the dialog.
Install Web Services Enhancements for Microsoft .NET (Windows 2000

and Windows Server 2003) - Team Workspace Web Server Only
To install Web Services Enhancements for Microsoft .NET (WSE) on a
Team Workspace web server, .NET Framework 1.1 must be installed in
Windows 2000 and Windows Server 2003.
During the installation of WSE, select the Runtime setup type. For
example, to install WSE, do the following:
1. Run the Microsoft installer package on the Team Workspace CD.

For example, for Windows 2000:
CD_DriveLetter:\twprereq\W2K\dotnet\Microsoft WSE 2.0 SP1.MSI
or for Windows Server 2003
CD_DriveLetter:\twprereq\W2K3\dotnet\Microsoft WSE 2.0 SP1.MSI
The Microsoft WSE 2.0 SP1 Install Shield Wizard dialog displays
with the Welcome panel.
2. Click Next. The License Agreement panel displays in the dialog.
3. Select I Accept ... .
4. Click Next. The Setup Type panel displays in the dialog.
5. Select Runtime.
6. Click Next. The Ready To Install panel displays in the dialog.
7. Click Install. The Installing Microsoft WSE 2.0 SP1 panel

displays in the dialog.
8. When InstallShield Wizard Completed panel displays, click

Finish.

The Web Service Enhancements are now installed on the web

server.
Windows Registry Changes for Windows 2000

When both the file and web servers use Windows 2000 as the operating
system, the web server may incur a problem when you change
workspaces. The cause of this problem is described in the Microsoft
Knowledge Base article, KB221790, on the Microsoft web site.
http://support.microsoft.com/default.aspx?scid=kb;en-us;221790&sd=tech
To prevent the problem, you must make changes to the Windows

Registry on the file and web servers in the Team Workspace site.
Problems When Editing the Windows Registry
Improper registry editing can damage the operating system of the computer and
can make the computer unbootable.
For information about the Windows Registry and how to edit it, see:
http://support.microsoft.com/kb/256986/EN-US/
Change the Registry

The procedure below is taken from the Microsoft Knowledge Base
article, KB221790. For more information, see the article on the
Microsoft web site.
To change the registry, do the following:
1. Use Windows Update on the file and web servers to make sure
they have the latest system fixes and updates.
2. Create a text file with the file name Client.reg .
3. Enter the following lines in Client.reg, and save the file.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters]
"MaxCmds"=dword:00000800
4. Run it on each web server.

5. Create a text file with the file name Server.reg .
6. Enter the following lines in Server.reg, and save the file.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters]
"MaxMpxCT"=dword:00000800
"MaxWorkItems"=dword:00002000
7. Run it on the file server.
8. Restart all of the servers for the changes to take effect.
Effects of These Registry Changes
Increasing these values consumes additional non-paged pool memory on the file
and web servers. Non-paged pool memory has an upper limit of 256 megabytes.
A large number of web servers with a large number of connections can consume
all of the non-paged pool memory on the file server. Use Performance Monitor to
watch this counter and to make sure that it is not approaching the limit.

Install Landmarks License Application Manager
License Application Manager (LAM) has a server component and a

client component. For Release 2003.18.1.0 of the Team Workspace to
accept the login of users, the LAM server must be accessible by Team
Workspace, and the LAM server must be running with a valid license
file, containing the licenses for the applications you will be running
(namely Team Workspace). A license file is available from Landmark
Graphics Corporation as a part of your purchase of this product.
The license server can be on practically any computer; however, the

following must be true:
The computer must have at least one Ethernet port that is always
accessible.
The license server must always be accessible by the web and site
servers of Team Workspace over the TCP/IP protocol.
The installation program for LAM is available on Volume 3 of the

Landmark CD installation package.
Obtain a Server License File

Before you begin, check LAM Technical Notes on page 37.
A license file must be obtained from Landmark Graphics Corporation

before you can start the license server and provide license information
to Landmark applications. To obtain the information required for a
license:
1. As an administrator of the computer where the license server will

run, log on to the computer.
2. Make sure at least one Ethernet port is active which will always
remain accessible. This requirement is usually not a problem with
desktop computers, but can be a concern with portable computers
with docking stations.
3. Enter the following command in a Command Prompt window:
ipconfig /all
4. Note the Host Name: ______________________________
R 2003.18.1.0 Install Team Workspace: Install Landmarks License Application Manager 33

5. Note the Physical Address: _________________________
On Windows 2000 systems, the address has twelve digits. For

example, an address might be similar to the following: 00-C0-
3D-68-F9-2B . If that were the address, the digits without the
dashes (00C03D68F92B) should be noted and will be provided
to Landmark. The address is not an IP address.
On computers with multiple adapters (such as a physical Ethernet

adapter, a logical or virtual adapter, or a wireless connection), it
may take some trial-and-effort to decide which is the correct
address of an adapter which is always accessible by other servers
over the network.
6. Request the license file from the following address:
http://www.lgc.com/support/licensing
You will be asked for the Host Name and Physical Address, as
well as the type of license, number of users for the license,
platform, model, and operating system version.
7. Place the license file in the LAM 2003 destination folder specified
during the LAM installation. For example, the default is
C:\Landmark\LAM .
If you do not place the license file on the server you cannot use the
NT Service that automatically starts the license server upon reboot
of the computer. See Using LAM Server Without NT Service on
page 37.
Install LAM Server

To install the LAM server, do the following:
1. Log on to the server as an administrator.
2. Put the LAM CD (volume 3) in the CD-ROM drive. The

installation will automatically start if your computer allows CDs to
load automatically.
3. If it does not start automatically, use the following steps:
Select Start > Run. The Run dialog box opens.
34 Install Team Workspace: Install Landmarks License Application Manager R 2003.18.1.0

In the Open text box, type:
CD-ROM_DriveLettter:\Install.exe
Click OK.
The LAM R2003 splash screen appears.
4. Click OK on the Copyrights panel. The Landmark Graphics panel

appears.
5. Click FLEXlm License Application Manager. The FLEXlm

panel appears.
6. Click Install. The Landmark LAM 2003 Setup dialog appears.
7. Click LAM Server in the dialog. The LAM Server Destination

Location panel appears in the dialog.
8. Click Next to accept the default location (C:\Landmark\LAM);

or click Browse to choose another location, and then click Next.
The installation program displays a status panel during

installation, and then displays the LAM Configuration panel in the
Landmark LAM 2003 Setup dialog.
9. Click Finish to restart the computer and to allow the installation to

complete.
The license server should start automatically when the machine

reboots if a valid license file is in the LAM folder.
10. Remove the LAM CD from the CD-ROM drive.
LAM Server Initial Startup

The license server is configured during LAM installation to become an
NT Service that starts automatically. However, you may need to
perform a few customization steps.
If you did not place the license file on the server you cannot use the NT
Service described in this section. See Using LAM Server Without NT
Service on page 37.

If the license file is on the server, make sure the file is placed in the
correct folder. To verify this:
1. Select Start > Programs > LAM2003 > License Tool Manager.
2. Click the Configuration Using Services radio button labelled.

The list box contains LGC License Application
Manager listed and selected. If it is not selected, select it now.
3. Click on the Configure Services tab.
4. Note the location of the license file (for example,

C:\Landmark\Lam\license.dat, which is the default).
Your license file should have been copied to this location.
5. During the installation, the LAM Server was set to automatically

start when Windows starts up. Verify this by looking at the Start
Server At Power Up check box. If it is not checked, check it, click
Save Service, then click Yes to confirm.
6. If you installed a new license file after rebooting, and after the
LAM server started, LAM must reread the license file to make the
server aware of the new file.
To reread the license file, go to step 7. Otherwise, skip to step 8.
7. To reread the license file, do the following:
Select the Start/Stop/Reread tab.
Select LGC License Application Manager.
Click the ReRead License File button.
If you receive an error message, click Stop Server, and then

click Start Server. A Server Starting message should appear
in the status bar at the bottom of the window.
8. Exit the License Tool Manager.
36 Install Team Workspace: Install Landmarks License Application Manager R 2003.18.1.0

LAM Technical Notes
Using LAM Server Without NT Service

In order to use LAM Server on a PC as an NT Service, the license file
must reside on the computer where LAM is run, not across the network
on another computer.
If the license file resides across the network, the server can still be
launched, but not as an NT Service. It must be run in a Command
Prompt window as follows:
lmgrd.exe -c LicenseFilePath
If Applications Cannot Find License File

Environment variables locating the license are normally set up by the
applications installation program. The variable can contain either the
full path to the license file including the machine name on which it
resides, or it can contain the port number and machine name or IP
address of the license server that serves that license file. For example:
LM_LICENSE_FILE 2013@NameOfHostRunningLAM
LM_LICENSE_FILE \\NameOfHostRunningLAM\Landmark\Lam\license.dat
FLEXlm performs background operations to optimize access time to

the license file when it is run from an application for the first time.

Install Team Workspace
This installation procedure presumes all required Team Workspace site

servers have been configured by the Enterprise Administrator as
indicated in the previous chapter, Administration Tasks Before
Installing on page 15. It also presumes that you have validated the
information from the Enterprise Administrator, as specified in the
section, Site Administrator Tasks on page 21.
Prerequisites
Refer to Installation Prerequisites on page 25.
Installation Steps
Review the section, Site Administrator Tasks on page 21, and make
sure you have the information required for the installation.
To install a new Team Workspace site you must have logged in as a Site
Administrator with sufficient administrative privileges to all the site
servers of Team Workspace and to the Team Workspace site
organizational unit in Active Directory.
Default Locations of Files
This procedure assumes the following default locations or folders:
The system drive (%SYSTEMDRIVE%) is the C-drive (or C: ).
The system root (%SYSTEMROOT%) is C:\WINNT or c:\windows .
The default drive for the files of Team Workspace is the system drive,
unless otherwise noted.
Except for the files that must go in a location in the system root folder or in
special Windows folders (like Documents and Settings and
Program Files), you can install the files of Team Workspace in locations
other than the ones indicated in this procedure.
38 Install Team Workspace: Install Team Workspace R 2003.18.1.0

Install the Team Workspace Site (or Database Server)

The installation program for installing the site must be executed on the
server running Microsoft SQL Server and must be installed first.
Do the following on the Team Workspace database server:
1. Insert the Team Workspace installation CD in the CD drive of the

computer where the database server runs.
2. Copy the following folders from the \DBServer folder on the

installation CD to the C-drive. If a Confirm Folder Replace dialog
displays, click Yes To All to overwrite the files in the folders.
Documents and Settings
Program Files
These folders contain libraries that Team Workspace uses as well

as the Team Workspace Administration console.
3. Copy the contents of the \tw3rdparty folder on the

installation CD to the folder shared as tw3rdparty .
4. Copy the contents of the \twsource folder on the installation

CD to the folder shared as twsource .
5. Install the Team Workspace .NET files.
Navigate to the AppSetup subfolder in the folder shared as

twsource.
DriveLetter:\twsource\AppSetup
Double-click TWSSetup.MSI to install the Team

Workspace .NET files. The TWSSetup dialog displays with the
Welcome To The TWSSetup Setup Wizard screen.
Click Next. The Select Installation Folder screen displays in

the dialog.
In the Folder text box, enter the path to the www subfolder in
the folder shared as twsource. For the path, use the syntax
defined by the Universal Naming Convention syntax for
network resources. For example:
\\FileServerName\twsource\www
R 2003.18.1.0 Install Team Workspace: Install Team Workspace 39

Select the Everyone radio button.
Click Next in the Select Installation Folder panel. The Confirm

Installation panel appears in the dialog.
Click Next to continue the installation. A progress panel

displays in the dialog until the Installation Complete panel
displays.
Click Close in the Installation Complete panel.
6. If a workspace will have the export facility of Team Workspace

configured in it, and if a license and the installation of Crystal
Reports XI Developer Edition are installed on the server, install
the Crystal Reports Export Application of Team Workspace.
Crystal Reports XI Developer Edition
This product must be purchased separately and my be purchased from

Business Objects SA (www.businessobjects.com).
To install the Crystal Reports Export Application, do the

following:

twsource.
Double-click TWSExportCRAppSetup.MSI to install the

export application. The TWSExportCRAppSetup dialog
displays with the Welcome To The TWSExportCRAppSetup
Setup Wizard screen.

the dialog.



displays.
7. Register the Dynamic Link Libraries (DLLs) associated with Team

Workspace. Do the following in a Command Prompt window:
Set the default scripting host with the following command:
cscript //h:cscript
Navigate to the DBServer folder on the installation CD. For

example:
cd CD_DriveLetter:\DBServer
Type the following command with the /A option to register

all Team Workspace DLLs:
Tw3rdparty Shared Folder and Reg.WSF
The registration script, Reg.WSF, assumes the shared folder for the
third-party applications is shared as tw3rdparty .
If the folder is not shared as tw3rdparty, modify the assignment of

to the path name in RegFiles.XML . This file is located in the
same folder as the script, Reg.WSF .Below is the section where the
path name is located. Edit only the value between the double-quotes.
<dllpath>


<const name="TW3rdPARTY" path="tw3rdparty" />
</dllpath>
reg.wsf \\FileServerName\ShareNameOfTwsource /A
For example:
reg.wsf \\myFileServer\twsource /A

8. Edit the ixSiteVariables.JS file in the bin subfolder in

the folder shared as twsource . For more information,
see Team Workspace Settings on page 46.
Create the Team Workspace Site

9. If the file server and web server are on the same computer, perform
steps 1 through 4 in the Install the Team Workspace Web Server
section below.
10. In the Command Prompt window, set the default scripting host
with the following command:
cscript //h:cscript
11. Navigate to the bin folder inside the folder shared as

twsource .
12. Enter the following commands:
twadmin site create
13. Verify whether the site creation was successful.
twadmin site status DatabaseServerName
If the site creation was successful, the command will display the
configuration of the Team Workspace site database. Verify the
value of sVersion is set to 2003.18.1.0 .
14. Create the LM_LICENSE_FILE environment variable to refer

to the license server installed in Install Landmarks License
Application Manager on page 33. Run the TWAdmin.WSF
script with the following syntax:
twadmin site licadd PortNumber@HostName
Where PortNumber is the TCP port number through which the

Team Workspace servers communicate to the license server.
The port number usually defaults to 2013. The value is
contained in the Server line in the license file. For example:
SERVER HostName PhysicalAddress PortNumber
Where HostName is the name or IP address of the computer on

which the license server runs.

15. If the file server and web server are on the same computer, return
to the Install the Team Workspace Web Server section below
(step on page 44) to complete the web server installation.
Install the Team Workspace Web Server

Install the Team Workspace web server only after the Team Workspace
site has been installed successfully on the server where SQL Server is
running. However, if the Team Workspace site has the database server
and web server on the same computer, steps 1 through 4 of this
procedure will need to be performed before the Team Workspace site
has been created (in the Create the Team Workspace Site section
above).
Also this procedure assumes, the procedure outlined

in Microsoft .NET Framework and MDAC on a Web Server on
page 26 has been performed on the computer as well as other
prerequisites for web servers indicated in previous sections.
Do the following on each Team Workspace web server:

computer where the web server runs.
2. Log in as a site administrator.
3. Copy the following folders from the \WebServer folder on the

installation CD to the C-drive. If the Confirm Folder Replace
dialog displays, click Yes to All when it ask you to overwrite the
files in the folders.
iisadmpwd
Program Files
twerrors

Workspace. Do the following in a Command Prompt window:
cscript //h:cscript

Navigate to the WebServer folder on the installation CD.

For example:
cd CD_DriveLetter:\WebServer
Run the following script with the /W option to register all

Team Workspace DLLs:

same folder as the script, Reg.WSF . Below is the section where the
<dllpath>
different -->
share name -->
</dllpath>
reg.wsf \\FileServerName\ShareNameOfTwsource /W
For example:
reg.wsf \\myFileServer\twsource /W
5. If the file server and web server are on the same computer, and if
you performed step 9 in the Install the Team Workspace Site (or
Database Server) section above, return to step 10 on page 42 of
that procedure.
Finish the Web Server Installation

In the Command Prompt window, set the default scripting host
with the following command:
cscript //h:cscript

6. Navigate to the C:\Program Files\Landmark\Team

Workspace\Main\bin folder.
c:
cd \Program Files\Landmark\Team Workspace\Main\bin
7. Enter the following to create Team Workspace entries in the

Windows Registry:
twweb web addreg DatabaseServerName

Application Manager on page 33. Run the TWWeb.WSF script
in a Command Prompt window with the following syntax
(assuming the location, c:\Program
Files\Landmark\Team Workspace\Main\bin):
twweb web licadd PortNumber@HostName


9. If the operating system is Windows Server 2003, allow active

server pages for the Web Services Extensions. Do the following:
Select Start > Control Panel >Administrative Tools >

Internet Information Services (IIS) Manager. The Internet
Information Services (IIS) Manager console displays.
In the left pane, display the branches of the WebServerName

branch.
Select the Web Service Extensions branch. The Web Service

Extensions screen displays in the right pane.
If Prohibited is displaying in the Status column for the

Active Server Pages item in the Web Service
Extension column, do the following:

Select the Active Server Pages row.
Click the Allow button.
Close the Internet Information Services (IIS) Manager console.
10. Restart the computer.
Team Workspace Settings

Team Workspace uses a configuration file (ixSiteVariables.JS)
to store the initial configuration information for the Team Workspace
site. This file is only used during the installation. You may want to
retain the version of the file edited for your site for informational
purposes during future upgrades of Team Workspace.
This file should be edited for step 8 on page 42 in the Install the Team
Workspace Site (or Database Server) section. After editing the file,
return to step 9 on page 42 in that section.
The Variables for a Site
Variable Name Sample value Explanation

Site Variables
sSiteOU "ou=tw-site1,dc=twdh,dc=com" This information is
received from the
Enterprise Administrator.
sSiteID "site1" The ID (or OU name) can
not exceed ten
alphanumeric characters.
All site IDs must be
unique within a domain.
sNTDomain "TWDH" The NetBIOS or pre-
Windows 2000 name of
the domain in which the
Team Workspace site
resides.


sAdminGroup "TWS Site Administrators" The name of the group
granting site administrator
rights to the
administrators of the
Team Workspace servers
and site organizational
unit. This information is
received from the
This value must be in pre-
Windows 2000 format.
Database Variables
sDbServer "twsqlserver1" The name of the server
where SQL Server is
installed. This information
is received from the
sDBFileServer "twsqlserver1" The server, where the
database files (MDF and
LDF files) are stored.
Normally, it is the same as
the value of
sDbServer.
sSiteDBPath "c:\\dbs" The path on
sDBFileServer
where the site database
files are placed. This
information is received
from the Enterprise
Administrator.
sSiteDBLogPath "c:\\dbs" The path on the
sDBFileServer
where the log files for the
site database are placed.
If this variable were not
specified, the location
would default to
sSiteDBPath.
sWSDBPath "c:\\dbs" The path on
sDBFileServer
where the workspace
database files are placed.
This path is received from
the Enterprise
Administrator.


sWSDBLogPath "c:\\dbs" The path on the
sDBFileServer
where the log files for the
workspaces are placed.
If this variable were not
specified, the location
would default to
sWSDBPath.
nSiteDBInitSize 10 The initial size in
megabytes of the site
database.
nSiteDBMaxSize 50 The maximum size in
megabytes of the site
database.
nSiteDBincSize 10 The size in megabytes of
increments for growing
the site database.
nWSDBInitSize 10 The initial size in
megabytes for the
workspace database.
nWSDBMaxSize 500 The maximum size in
megabytes for the
workspace database.
nWSDBincSize 50 The size in megabytes of
increments for growing
the workspace database.
Data Location Variables
sFileServer "twfileserver1" The name of the server
that will contain the user
data. This information is
received from the
sWSFilePath "twdata\\workspaces" The path where Team
Workspace will put user
data. This path is the name
of the user data share
(twdata) followed by
\\workspaces .
Normally, you do not need
to change this path.


Source Code Variables
sSystemServer "twfileserver1" The name of the server
that has the Team
Workspace source code on
it. This name is received
from the Enterprise
Administrator. This name
is normally the same as
the value of
sFileServer.
sSystemPath "twsource" The name of the shared
folder where the Team
Workspace code is
located. Normally, you do
not need to change this
name.
sSiteDBObjPath "twsource\\bin\\dbscripts\\ You never need to change
site" this setting, unless you
named the folder
containing the source
code something other than
twsource . This path
contains the scripts that
create the site database.
sWSDBObjPath "twsource\\bin\\dbscripts\\ You never need to change
workspace" this path, unless you
named the folder
containing the source
code something other than
twsource . This path
contains the scripts that
create the workspace
database.
Other Shared Folder Variables
STW3rdParty "tw3rdparty" The share name of the
folder where the third
party components are
stored on the computer
identified in the
sSystemServer
variable.


MetaFrame Variables
sMFPrimary "twmetaframe1" The name of the primary
Citrix MetaFrame server.
If you are using Citrix,
you should receive this
name from the Enterprise
Administrator
sMFSecondary "" The name of secondary
Citrix MetaFrame server.
If you are using Citrix,
you should receive this
name from the Enterprise
Administrator. Leave this
value blank if you do not
have a secondary
MetaFrame server.
nMFPrimaryPort 81 The XML port number for
the primary Citrix
MetaFrame server. If you
are using Citrix, you
should receive this
number from the
nMFSecondaryPort 0 The XML port number for
the secondary Citrix
MetaFrame server. If you
are using Citrix, you
should receive this
number from the
Web Site Variables
bPwdChanger True Set this variable to True
if you want users to be
able to change their
password in the Team
Workspace web interface.
Set it to False if not.
sIisadmpwdPath "c:\\iisadmpwd" The location on the web
servers where the
password changer will be
copied. You do not need to
change this path.
sCustomErrorsDir "C:\\twerrors" Location on the web
servers where the custom
errors files are copied.
Normally, you do not need
to change this path.


gSiteAdmin.arWebServers ["twwebserver1",twwebserver2] List of all the web server
names in the Team
Workspace site. These
name are received from
the Enterprise
Administrator.
gSiteAdmin.arWebSites [1,1] List of each web site
number of each Team
Workspace web server
listed in the
....arWebServers
variable. The web site
numbers should be in the
order listed in the
....arWebServers
variable. These numbers
are received from the
Notes on Editing ixSiteVariables.JS

The TWAdmin.WSF script uses this file. The script is located in
\\FileServerName\twsource\bin . Any syntax errors will cause
the installation to fail.
A string variable must have its value in double quotation marks, as

follows:
sSiteID = "Aberdeen"
If the string value is null, or blank, the double quotation marks have no
character between them, as follows:
sMFSecondary = ""
A number variable does not have quotation marks, as follows:
nSiteDBMaxSize = 50
An array variable is contained within square brackets with the values

separated by a comma. An array of strings is represented, as follows:
gSiteAdmin.arWebServers = ["twwebserver1",twwebserver2]

An array of numbers is represented, as follows:
gSiteAdmin.arWebSites = [1,3]
A comment is represented by two forward slashes, as follows:
gSiteAdmin.arWebSites = [1,3]// This is a comment
A back slash is a special character and therefore when it is used within

a file path, you must add an additional back slash to tell the interpreter
that you really do want a back slash. So to represent c:\dbs , you
would use the following:
sSiteDBPath = "c:\\dbs"
Editing the File

1. Change folders to:
\\FileServerName\twsource\bin
2. Using a text editor, such as Notepad, edit

ixSiteVariable.JS to include information about the Team
Workspace site.
Be careful to maintain the syntax of the file.
Below is a sample of the file.
//globals
var gSiteAdmin = new ixTWSiteWrap()

with (gSiteAdmin.oTWSite)
{
// site specific variables
sSiteOU = "ou=tw-site1,dc=twdh,dc=com"
sSiteID = "site1"//CAN NOT BE MORE THAN 10 CHARACTERS!!!!!
sNTDomain = "TWDH" //NETBIOS domain name
sAdminGroup = "Domain Admins"//group name in AD containing
//domain accts
// database locations
sDbServer = "twdh-sw-rl" //sql server host
sDBFileServer = "twdh-sw-rl" //db file host
sSiteDBPath = "D:\\dbs" //site database path
sSiteDBLogPath = "d:\\dbs" //site database logfile path
sWSDBPath = "D:\\dbs" //workspace database path

sWSDBLogPath = "D:\\dbs" //workspace database logfile path
nSiteDBInitSize = 10 //site db initsize

nSiteDBMaxSize = 50
nSiteDBincSize = 10
nWSDBInitSize = 10
nWSDBMaxSize = 500
nWSDBincSize = 50
// file data locations

sFileServer = "twdh-sw-rl" //file data host
sWSFilePath = "twdata\\workspaces"//workspace file data
//path e.g twdata\\workspaces
// source code locations

sSystemServer = "twdh-sw-rl" //system code host
sSystemPath = "twsource" //share path to the system code
sSiteDBObjPath = "twsource\\bin\\dbscripts\\site"
//path to the sql src for site db
//objects
sWSDBObjPath = "twsource\\bin\\dbscripts\\workspace"
//path to the sql src for the ws
//db objects
// other shares
sTW3rdParty = "tw3rdparty" // tw3rdparty share - on
//sSystemServer box
// metaframe settings
sMFPrimary = "twih-m-01" //name of primary
//metaframe data collector
sMFSecondary = "twih-m-02" //name of secondary
//metaframe data collector
nMFPrimaryPort = 81
nMFSecondaryPort = 81
// web site info
bPwdChanger = true
sIisadmpwdPath = "c:\\iisadmpwd"
sCustomErrorsDir = "c:\\twerrors"
gSiteAdmin.arWebServers = ["web01","web02"]
//webserver list, separated by commas
gSiteAdmin.arWebSites = [1,1]
//website list, separated by commas
}
Changing Site Variables After Creating a Site

After you have created a Team Workspace site, the site configuration
(and the configuration variables) can be updated using the twadmin

script, which is located in the bin subfolder located in the folder

shared as twsource. The syntax of the command line is the
following:
twadmin site update DatabaseServerName VariableName="ValueOfVariable"

Upgrade Team Workspace 2003.13.3
This procedure will upgrade a Team Workspace 2003.13.3 installation

to 2003.18.1. If you have an older version of Team Workspace, you
should upgrade to 2003.13.3.0 before using the procedures in this
section.
Prerequisite for Version 2003.18.1

Since the previous release, the following prerequisites, requirements,
and features were added to Team Workspace:
If you will be using Team Workspaces new data export facility,

Crystal Reports XI Developer Edition must be installed on the web
servers. For more information about Crystal Reports, see Business
Objects SA (www.businessobjects.com).
If a workspace will be using the Crystal Reports product with the

data export facility, grant the Modify permission to the Users
group on each web server of the following folder:
Windows Server 2003
%SystemRoot%\Temp
Windows 2000
c:\Documents and Settings\WebServerName\ASPNET\Local Settings\Temp
For Window 2000, the service pack level has been updated to
Service Pack 4 and the latest security patches.
If the workspaces will access an Oracle database with Unicode

encoding of the characters in the database, use Oracle
Client 9.2.0.x, and use the Oracle Provider for OLE DB apropos to
that client, on the web server.
A Team Workspace server can now be on the Windows

Server 2003 operating system. If a Team Workspace server is on
Windows Server 2003, the following must be installed.
Install the Common Files of Internet Information Services on

the database server. These files are not installed by default
and are needed by the site creation script. Check that they are
R 2003.18.1.0 Install Team Workspace: Upgrade Team Workspace 2003.13.3 55

installed by opening the Add/Remove Applications control

panel, and then display the Windows Components Wizard.
The Common Files component is a subcomponent of the of
the Internet Information Services (IIS) component, and the
IIS component is a subcomponent of the Application Server
component.

installed with the ASP.NET component on the web server. In
Windows Server 2003, the ASP.NET component is not
installed as a default. The ASP.NET component is a
subcomponent of the Application Server component. The
component is available through the Add Or Remove
Programs control panel and its Add/Remove Windows
Component Wizard.
For Oracle connectivity, Oracle Client 9.2.0.x and its OLEDB

Provider are required on the web servers. Release 8.1.7.x of
the Oracle Client is not recommended for Windows
Server 2003.
If workspaces will use a Citrix MetaFrame server, Microsoft

Visual J# .NET Redistributable Package, version 1.1
(vjredist1.1.EXE) must be installed. The installation
program for Visual J# .NET is located in
CD_DriveLetter:\twprereq\W2Kx\citrix .
Installation Order
Microsoft Visual J# .NET Redistributable Package must be

installed after ASP.NET in Windows Server 2003 or after
Microsoft .NET Framework 1.1.
For more information on the prerequisites for Team Workspace,

see Windows Server 2003 on page 3.
Upgrade from Version 2003.13.3 to 2003.18.1

Before proceeding with this procedure, realize that the procedure will
temporarily bring down the Team Workspace web site.
To upgrade a Team Workspace site you must have logged in as a site

administrator with sufficient administrative privileges to all Team
Workspace site servers and to the Team Workspace site organizational
unit in Active Directory.
56 Install Team Workspace: Upgrade Team Workspace 2003.13.3 R 2003.18.1.0

To upgrade a site, do the following:
Default Locations of Files
This procedure assumes the following default locations or folders:
The system drive (%SYSTEMDRIVE%) is the C-drive (or C: ).
The system root (%SYSTEMROOT%) is C:\WINNT or c:\windows .
The default drive for the files of Team Workspace is the system drive,
unless otherwise noted.
If you have installed the files of Team Workspace in other locations, make
appropriate changes to the example paths in the procedure.
Before Upgrading
1. Completely backup the database of Team Workspace as well as
each system database in SQL Server, according to your company
procedures.
For more information about backing up the data in SQL Server,

see its documentation.
2. Backup the twsource and twdata shared folders in the

Team Workspace site.
3. Stop all web servers that are a part of the Team Workspace
installation. For example, in a Command Prompt window on each
web server, enter the following:
iisreset /stop
4. On each web server, unregister fupload.dll located in the

tw3rdparty shared folder. In a Command Prompt window, enter a
command similar to the following:
regsvr32 -u \\FileServerName\ShareNameOfTw3rdpary\fupload\fupload.dll
For example:
regsvr32 -u \\myFileServer\tw3rdparty\fupload\fupload.dll

5. On each web server, remove the old Team Workspace .NET

application. To remove it on a web server, do the following:
Select Start >Settings > Control Panel. The Control Panel

window opens.
Double-click Add/Remove Programs in the Control Panel

window to open the Add/Remove Programs window.
Select TWS_Install .
Click Remove.
Close the Add/Remove Programs window.
Upgrade the Team Workspace Site (or Database Server)

The Team Workspace database server must be upgraded before the web
server.
To upgrade the site, do the following:
1. On the database server, unregister the Dynamic Link Libraries

(DLLs) associated with Team Workspace. Do the following in a
Command Prompt window:
cscript //h:cscript
Navigate to the DBServer folder on the installation CD. For

example:
Type the following command with the /U option to unregister

the DLLs:
reg.wsf \\FileServerName\ShareNameOfTwsource /U
For example:
reg.wsf \\myFileServer\twsource /U
2. Check that TWSBlogic.DLL and TWSLam.DLL have been

removed from the Global Assembly Cache using the

Microsoft .NET Framework 1.1 Configuration tool. Do the

following:
Select Start > Programs > Administrative Tools >

Microsoft .NET Framework 1.1. Configuration. The .NET
Configuration 1.1 window displays.
Click the Manage The Assembly Cache link in the .NET

Framework 1.1 Configuration page in the right pane under
Tasks. If you do not see this link, select the My Computer
branch in the left pane, and the correct page should appear in
the right pane.
After clicking the Manage The Assembly Cache link, the

Assembly Cache page displays in the right pane.
Click the View List of Assemblies in the Assembly Cache

link under Tasks. The list of assemblies displays in the right
pane.
If the TWSBlogic or TWSLam assembly is in the cache:
Select the assembly (holding down the Ctrl key will allow
you to select more than one assembly at a time).
Right-click to display a shortcut menu.
Select Delete in the shortcut menu.
Close the .NET Configuration 1.1 window.
3. Unshare the existing twsource .
Right-click the existing twsource folder to display a

shortcut menu.
Select Sharing in the shortcut menu.
Select the Do Not Share This Folder radio button.
Click Apply. The Share Name text box should now be empty.
Click OK in the Properties dialog.

4. To avoid confusion with the new version, rename the old

twsource folder to indicate the version of its files. For example,
you may change the name of the folder to tw-2003.13.3.0 .
5. Create a new folder (tw-2003.18.1.0) and share it as

twsource . This folder will contain the new Team
Workspace 2003.18.1 files.
Right-click the newly created folder to display a shortcut

menu.
Select Sharing in the shortcut menu.
Click the Share This Folder radio button.
In the Share Name text box, enter twsource .
Click Apply.
Click the Permissions button. The Permissions dialog for the

shared folder displays.
Select Everyone in the list box.
Click Remove.
Assign the following privileges to twsource .
Local Users: Check the Allow box for only the Read
permission.
Local Administrators: Check the Allow box for the Full

Control permission. Checking that box also checks the
boxes for the Change and Read permissions.
After assigning the permissions, click OK in the Permissions

dialog.
Click OK in the Properties dialog.
6. Copy the site folder from the old twsource folder

(tw-2003.13.3.0) to the new twsource folder
(tw-2003.18.1.0).

7. Copy the contents of the twsource folder on the Team

Workspace installation CD to the folder shared as twsource on
the file server.
8. Copy the Documents And Settings and the Program

Files folders from the DBServer folder on the Team
Workspace installation CD to the C-drive on the database server.
Click Yes To All if Windows asks whether it should overwrite
files.
Copying the Documents And Settings folder creates a

TW Admin Console shortcut in a Team Workspace program group
in the Start menu.
9. Copy the contents of the \tw3rdparty folder on the

installation CD to the folder shared as tw3rdparty . Click Yes
To All if Windows asks whether it should overwrite files.
10. Install the Team Workspace .NET files.

twsource.
Double-click TWSSetup.MSI to install the Team

Workspace .NET files. The TWSSetup dialog displays with the
Welcome To The TWSSetup Setup Wizard screen.

the dialog.



displays.
11. If the workspaces will have the export facility of Team Workspace
configured in them, and if a license and the installation of Crystal
Reports XI Developer Edition are installed on the server, install
the Crystal Reports Export Application of Team Workspace.
Crystal Reports XI Developer Edition
This product must be purchased separately and my be purchased from

Business Objects SA (www.businessobjects.com).
To install the Crystal Reports Export Application, do the

following:

twsource.
Double-click TWSExportCRAppSetup.MSI to install the

export application. The TWSExportCRAppSetup dialog
displays with the Welcome To The TWSExportCRAppSetup
Setup Wizard screen.

the dialog.



displays.
Workspace. Do the following:
In a Command Prompt window, navigate to the DBServer

folder on the installation CD. For example:
Type the following command with the /A option to register

reg.wsf \\FileServerName\ShareNameOfTwsource /A
For example:
reg.wsf \\myFileServer\twsource /A
13. Create a security code group within .NET Framework to allow it to

execute ASPX files from shared folders.
Start the Microsoft .NET Framework 1.1 Configuration

console. The console is located in the Administrative Tools of
the Control Panel.
In the tree of the console, expand the tree to show the All_Code
branch (My Computer > Runtime Security Policy > Machine >
Code Groups).
Right-click All_Code to display a shortcut menu.
Select New in the shortcut menu to display the Create Code

Group dialog.
In the dialog, select the Create A New Code Group radio

button.
In the Name text box, type TWWebApps_Zone .
Click Next to display the Choose A Condition Type panel in

the dialog.

In the Choose The Condition Type drop-down list box, select

URL . A URL text box appears in the dialog.
Type the following in the URL text box:
file://FileServerName/twsource/*
where FileServerName is the host name or IP address of the

Team Workspace file server as indicated in the Internet
Services Manager console on the web server. The name used in
the URL should match the server name included in the path in
the Network Directory text box on the Home Directory tab in
the properties dialog for the Team Workspace web site (usually
the Default Web Site).
And, where the URL element twsource is the share name

of the folder created and configured previously in Create File
Shares on page 25.
Click Next. The Assign A Permission Set panel appears in the

dialog.
Select the Use Existing Permission Set radio button.
In the drop-down box, select FullTrust .
Click Next.
Click Finish.
Close the .NET Framework Configuration console.
14. In the Command Prompt window, run the Upgrade.WSF script

located in the bin\upgrade subfolder of the folder shared as
twsource . This script will upgrade the database server. For
example:
cd PathToTWSourceDir\bin\upgrade
upgrade.wsf dbupgrade DatabaseServerName all
15. Verify whether the upgrade was successful.
cd ..
twadmin site status DatabaseServerName

If the upgrade was successful, the command will display the

configuration of the Team Workspace site database. Verify the
value of sVersion is set to 2003.18.1.0 .
16. If you have custom themes, copy their folders from the
\www\system folder in the old twsource folder to the new
twsource folder (tw-2003.18.1.0\www\system).
Carrying Forward Customizations
If you have customized any of the files installed with Team Workspace,
you may consider copying those files at the end of the upgrade procedure
from the backup to the upgraded installation. Before copying customized
Team Workspace files to the upgraded installation, and since conflicts
might arise, contact Landmark Technical Support to help determine the
advisability of copying such files to the upgraded installation.
Upgrade the Team Workspace Web Server

The Team Workspace database server must be upgraded before the web
server.
Upgrade each Team Workspace web server.
Do the following on each Team Workspace web server:
Microsoft .NET Framework and Web Service Enhancements
This procedure assumes the server has .NET Framework 1.1 and Web
Service Enhancements 2.0, Service Pack 1 installed as described
in Microsoft .NET Framework and MDAC on a Web Server on page 26.
2. In a Command Prompt window, check whether the Team

Workspace web server is running. For example:
iisreset /status
3. If the web server is running, stop the web server. For example:
iisreset /stop

4. Unregister the Dynamic Link Libraries (DLLs) associated with

Team Workspace. Do the following:
In a Command Prompt window, navigate to the WebServer

cscript //h:cscript
Type the following command with the /U option to unregister

the DLLs:
reg.wsf \\FileServerName\ShareNameOfTwsource /U
For example:
reg.wsf \\myFileServer\twsource /U
5. Using the Microsoft .NET Framework 1.1 Configuration tool,

verify that the following DLLs have been removed from the Global
Assembly Cache.
TWS.OLEDBQueryService
TWS.PowerhubQueryService
TWSBLogic
TWSLam
TWSOrder
TWSQuery
If the DLLS have not been removed, delete them from the Global
Assembly Cache. To verify whether these assemblies are still in
the cache and then to delete any remaining assemblies, do the
following:
Select Start > Programs > Administrative Tools >

Microsoft .NET Framework 1.1. Configuration. The .NET
Configuration 1.1 window displays.
Click the Manage The Assembly Cache link in the .NET

Framework 1.1 Configuration page in the right pane under
Tasks. If you do not see this link, select the My Computer
branch in the left pane, and the correct page should appear in
the right pane.

After clicking the Manage The Assembly Cache link, the

Assembly Cache page displays in the right pane.
Click the View List Of Assemblies In The Assembly Cache

link. A list displays in the right pane.
Are the following assemblies listed?
TWS.OLEDBQueryService
TWS.PowerhubQueryService
TWSBLogic
TWSLam
TWSOrder
TWSQuery
If any are listed:
Hold down the Ctrl key, and select all assemblies from the
above list still remaining.
Right-click to display a shortcut menu.
Select Delete so that each assembly is deleted from the

cache.
Close the .NET Configuration 1.1 window.
6. Copy the IISAdmPwd, TWErrors, and Program Files

folders from the WebSever folder on the Team Workspace
installation CD to the C-drive. Click Yes To All if Windows asks
whether it should overwrite files.



Type the following command with the /W option to register


<dllpath>
different -->
share name -->
</dllpath>
For example:
8. On a server with the Windows Server 2003 operating system, set

Internet Information Services (IIS) 6.0 to worker process mode.
In a Command Prompt window, navigate to the bin folder

located in the folder shared as twsource. For example, if the
folder is on the C-drive:
cd c:\twsource\bin
Type the following:
twadmin.wsf site prepiis2k3 WebServerName
For example:
twadmin.wsf site prepiis2k3 tws_web

After Upgrading the Site

The configurations in parts of Team Workspace have changed to make
them more consistent.
GIS Map Configuration

Configurations of GIS maps configured in a workspace will have to be
changed in order to work in 2003.18.1.0. You may need to change
values entered in the Path and Gateway Script text boxes.
Previously, a maps configuration included the workspace ID. For

example:
Map.aspx?sWSID=WorkspaceID
or
Map.aspx?sWSID=WorkspaceID&sMAPID=MapID
The syntax for the map configuration is now the following:
Where Accessed Path Gateway Script

Application menu user/_map Map.aspx?sMAPID=MapID
The extension is aspx, not asp .
Application in Grid view user/_viewer Map.asp?sMAPID=MapID
The extension is asp, not aspx .
With 2003.18.1.0, each map must be registered with a map ID.

Adding An Additional Web Server to a Site
If your site requires additional web servers, you can add the web
servers to the Team Workspace site with the procedure in this section
Prerequisites
See the Web Server section of Installation Overview on page 23,
and follow the procedures in Microsoft .NET Framework and MDAC
on a Web Server on page 26 to install and configure the .NET
Framework on the new web server.
Installation Procedure for An Additional Web Server

To create an additional web server for a Team Workspace site, do the
following:

computer where the web server runs.
3. Copy the following folders from the \WebServer folder on the

installation CD to the C-drive. If the Confirm Folder Replace
dialog displays, click Yes to All when it ask you to overwrite the
files in the folders.
iisadmpwd
Program Files
twerrors


cscript //h:cscript
70 Install Team Workspace: Adding An Additional Web Server to a Site R 2003.18.1.0

Type the following command with the /W option to register


<dllpath>
different -->
share name -->
</dllpath>
For example:
5. In the Command Prompt window, navigate to the C:\Program

Files\Landmark\Team Workspace\Main\bin folder.
c:
6. Enter the following to create Team Workspace entries in the

Windows Registry:
twweb web addreg DatabaseServerName

Application Manager on page 33. Run the TWWeb.WSF script
in a Command Prompt window with the following syntax
(assuming the location, c:\Program
Files\Landmark\Team Workspace\Main\bin):
twweb web licadd PortNumber@HostName
R 2003.18.1.0 Install Team Workspace: Adding An Additional Web Server to a Site 71



8. If the operating system is Windows Server 2003, allow active

server pages for the Web Services Extensions. Do the following:
Select Start > Control Panel >Administrative Tools >

Internet Information Services (IIS) Manager. The Internet
Information Services (IIS) Manager console displays.
In the left pane, display the branches of the WebServerName

branch.
Select the Web Service Extensions branch. The Web Service

Extensions screen displays in the right pane.
If Prohibited is displaying in the Status column for the

Active Server Pages item in the Web Service
Extension column, do the following:
Select the Active Server Pages row.
Click the Allow button.
Close the Internet Information Services (IIS) Manager console.
72 Install Team Workspace: Adding An Additional Web Server to a Site R 2003.18.1.0

Other Administration Tasks
Uninstalling Release 2003.18.1.0
Generally, to uninstall Team Workspace, Release 2003.18.1.0,

unregister components and remove files and folders in the reverse order
in which they were installed. For example:
Uninstall the Team Workspace web server or servers.
Uninstall the Team Workspace data in the SQL server.
Uninstall any pre-requisites installed solely for Team Workspace.
Delete the Team Workspace files on the server or servers.
Delete entries for Team Workspace in the Windows registry.
To uninstall Team Workspace:
Procedure Deletes All Team Workspace Data
This procedure removes all of Team Workspace from your computer,

including all of its executables and files, and including all of the data,
configurations, workspaces, and Active Directory entries that make up the
Team Workspace site.
After this procedure is complete, all that composed your Team Workspace
site will be deleted and unrecoverable.
Web Server Uninstallation

To uninstall, do the following:
1. Stop each Team Workspace web server.
Log in as a site administrator.
Open a Command Prompt window.
R 2003.18.1.0 Other Administration Tasks: Uninstalling Release 2003.18.1.0 73

Stop the Team Workspace web site. For example:
iisreset /stop
2. On each web server, do the following:
Enter the following command in a Command Prompt window:
cscript //h:cscript
Change folders to the bin folder of Team Workspace. For

example:
c:
Execute the TWWeb.WSF script to delete the

LM_LICENSE_FILE environment variable. Enter the
following:
twweb web licdel
Execute the TWWeb.WSF script to delete registry entries. For

example:
twweb web delreg DatabaseServerName
Enter Y when the script asks whether it should precede with

deleting registry entries on the web server for the database
server.
Unregister the Team Workspace libraries by running the

Reg.WSF script with the /U option:
\\FileServeName\twsource\bin\reg.wsf \\FileServeName\twsource /U
Remove the following folders:
c:\iisadmpwd
c:\twerrors
If the web server is not on the same computer as the database

server, remove the following folder:
c:\Program Files\Landmark\Team Workspace
74 Other Administration Tasks: Uninstalling Release 2003.18.1.0 R 2003.18.1.0

If you delete this folder in Windows Explorer, close the

Command Prompt window, or navigate out of the
Team Workspace folder or any of its subfolders before
trying to delete it; otherwise, Windows will display a message
dialog indicating that a file is being used.
Database/File Server Uninstallation

On the database server, do the following:
2. Open a Command Prompt window.
3. Enter the following command in the Command Prompt window:
cscript //h:cscript
4. Change folders to the bin subfolder within the folder shared as

twsource .
5. Run the TWAdmin.WSF to delete the site. For example:
twadmin site delete DatabaseServerName
6. Enter Y when the script asks whether it should precede with

deleting the site and workspaces.
7. Unregister the Team Workspace libraries by running the

Reg.WSF script with the /U option:
\\FileServeName\twsource\bin\reg.wsf \\FileServeName\twsource /U
8. Remove the TWSExportCRAppSetup and the TWSSetup

programs. To remove them, do the following:
Select Start >Settings > Control Panel. The Control Panel

window opens.
Double-click Add/Remove Programs in the Control Panel

window to open the Add/Remove Programs window.
Select TWSExportCRAppSetup .
Click Remove.
R 2003.18.1.0 Other Administration Tasks: Uninstalling Release 2003.18.1.0 75

After the removal TWSExportCRAppSetup has completed,

select TWSSetup .
Click Remove.
Close the Add/Remove Programs window.
9. Unshare the shared Team Workspace folders: tw3rdparty,

twdata, and twsource.
10. Delete the previously shared Team Workspace folders as well as

the dbs folder.
11. Remove the Team Workspace folder from the following

folders:
C:\Documents and Settings\All Users\Start Menu\Programs
C:\Program Files\Landmark
76 Other Administration Tasks: Uninstalling Release 2003.18.1.0 R 2003.18.1.0

TWS InstallationGuide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TWS InstallationGuide

Uploaded by

Copyright:

Available Formats

Team Workspace Desktop TM

Part No. 160549 R2003.18.1.0 January 2006

Halliburton Digital and Consulting Solutions

All other trademarks are the property of their respective owners.

Team Workspace Site Preparation ............................................................................. 3

Administration Tasks Before Installing ................................................................. 15

R 2003.18.1.0 Contents iii

Site Administrator Tasks ........................................................................................................ 21

Install Team Workspace ................................................................................................. 23

GIS Map Configuration ............................................................................................. 69

Other Administration Tasks ......................................................................................... 73

Team Workspace Desktop is a light-weight technical portal that allows

Team Workspace Desktop

Team Workspace Release Notes (TWS_ReleaseNotes.PDF)

Team Workspace Installation Guide

Team Workspace Online Help (OnlineHelp.HTM)

Team Workspace files.

Third Party Software for Team Workspace.

R 2003.18.1.0 Welcome: Team Workspace Desktop 1

2 Welcome: Team Workspace Desktop R 2003.18.1.0

Team Workspace Site Preparation

The Team Workspace Site

A Team Workspace site is a collection of servers on which the Team

Windows Server 2003

General Site Requirements

Active Directory domain installed and running in Native mode.

Active Directory organizational unit (OU) created for the Team

All servers must use English (United States) as the default

Landmark License Application Manager 2003 (LAM) server with

R 2003.18.1.0 Team Workspace Site Preparation: The Team Workspace Site 3

Database Server Requirements

The IIS Common Files component must be installed on the system

In Windows Server 2003, the Common Files component is not

For example, to add the Common Files, in the Windows

Shared folder for the system files Team Workspace (twsource),

Web Server Requirements

In Windows Server 2003, the ASP.NET component is not installed

For example, to add the ASP.NET component, in the Windows

4 Team Workspace Site Preparation: The Team Workspace Site R 2003.18.1.0

Application Server dialog, check ASP.NET. Click OK in each

If workspaces will send email notifications, the Simple Mail

Team Workspace requires that valid SSL certificates be installed

A Machine Code Group in the Runtime Security Policy branch of

The WebServerName\Users group should have Full Control

Web Services Enhancements for Microsoft .NET (WSE) 2.0,

If workspaces will access an Oracle database, Oracle Client 9.2.0.x

Oracle Client Included with OpenWorks

If workspaces will access an Oracle database, Oracle Provider for

R 2003.18.1.0 Team Workspace Site Preparation: The Team Workspace Site 5

If workspaces will use a Citrix MetaFrame server, the ASP.NET

The ASP.NET component is available through the Add Or Remove

The installation program for Visual J# .NET is located in

The ASP.NET component must be installed before Microsoft Visual

If a workspace has the Team Workspace export application

Citrix MetaFrame Server Requirements

Windows 2000 Server

General Site Requirements

6 Team Workspace Site Preparation: The Team Workspace Site R 2003.18.1.0

Active Directory domain installed and running in Native mode.

Active Directory organizational unit (OU) created for the Team

The OU must be configured to allow the Team Workspace

All servers must use English (United States) as the default

Microsoft .NET Framework 1.1, Service Pack 1. If you need to