Flowserve - DS ion Guide

Data Services Installation Guide forWindows

BusinessObjects Data Services XI 3.0 (12.0.0)

© 2008 Business Objects. All rights reserved. Business Objects owns the followingU.S. patents, which may cover products that are offered and licensed by Business

Copyright

Objects: 5,555,403; 5,857,205; 6,289,352; 6,247,008; 6,490,593; 6,578,027;6,831,668; 6,768,986; 6,772,409; 6,882,998; 7,139,766; 7,299,419; 7,194,465;7,222,130; 7,181,440 and 7,181,435. Business Objects and the Business Objectslogo, BusinessObjects, Business Objects Crystal Vision, Business Process OnDemand, BusinessQuery, Crystal Analysis, Crystal Applications, Crystal Decisions,Crystal Enterprise, Crystal Insider, Crystal Reports, Desktop Intelligence, Inxight,the Inxight Logo, LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Letthere be light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, WebIntelligence, Workmail and Xcelsius are trademarks or registered trademarks inthe United States and/or other countries of Business Objects and/or affiliatedcompanies. All other names mentioned herein may be trademarks of their respectiveowners.

Business Objects products in this release may contain redistributions of softwarelicensed from third-party contributors. Some of these individual components may

Third-partyContributors

also be available under alternative licenses. A partial listing of third-partycontributors that have requested or permitted acknowledgments, as well as requirednotices, can be found at: http://www.businessobjects.com/thirdparty

2008-03-14

ContentsPreparing to Install Data Services 9Chapter 1

Pre-installation overview............................................................................10System requirements...........................................................................11Network requirements..........................................................................11User permissions for installing Data Services......................................12Choose components and determine component distribution...............13Create a database for each repository.................................................17Check port assignments.......................................................................18Check network connections.................................................................20Create a Windows cluster....................................................................20

Repository database requirements and preparation.................................22Installing MySQL as the repository database.......................................23To set up a database account for BusinessObjects Data Services......24Setting up an empty database for the repository.................................24

Installation scenarios.................................................................................31Standard installation overview..............................................................31Silent installation overview ..................................................................32

Standard Installation of Data Services 35Chapter 2

Beginning your installation.........................................................................36To accept the license agreement.........................................................36To enter user information and a product keycode................................37To specify the installation location........................................................39To select which features to install.........................................................40

To select a repository.................................................................................42To configure a MySQL database server...............................................43

Data Services Installation Guide for Windows 3

To configure an existing database server.............................................45To configure a Job Server..........................................................................46

To specify login information..................................................................48To configure an Access Server..................................................................49To configure Metadata Integrator...............................................................50

To specify Metadata Integrator configuration details............................51To specify Metadata Integrator SSL details..........................................53

To select a web application server configuration option............................54To configure your Tomcat application server........................................55To configure an existing Web application server..................................56

To start the installation...............................................................................58

Silent Installation of Data Services 59Chapter 3

Silent installation........................................................................................60Silent install parameters............................................................................61Custom install options for silent installation...............................................65Silent/scripted installation .ini file...............................................................66Sample installation script file.....................................................................67

After Installing Data Services 71Chapter 4

Starting Data Services services automatically...........................................72Logging in to the Management Console....................................................72Using the Repository Manager..................................................................72

To create or upgrade repositories........................................................73To create or upgrade repositories in batch mode.................................74

Using the Server Manager.........................................................................76To configure Job Servers......................................................................78To resynchronize Job Servers..............................................................80To configure run-time resources for Job Servers.................................81To configure Access Servers................................................................82

4 Data Services Installation Guide for Windows

Contents

Verifying that Job and Access servers are running..............................84Using the License Manager.......................................................................84

To start License Manager.....................................................................84To view product activation keycodes....................................................85To add a product activation keycode....................................................85To remove a product activation keycode..............................................85To use License Manager from the command line................................86

Installing and configuring the Metadata Integrator....................................87Installing Metadata Integrator...............................................................88Metadata Integrator installation tips and troubleshooting.....................89Configuring the Metadata Integrator....................................................90

Connecting the Data Profiler......................................................................94Troubleshooting installation problems.......................................................95

Repository problems............................................................................95Management Console problems..........................................................96

Upgrading Data Services 97Chapter 5

Data Services component upgrades.........................................................98Repository upgrades............................................................................98

Upgrading your Data Services system......................................................99Using configurations from a previous version....................................100Before installing a new version...........................................................101To install a new version of Data Services...........................................101

Upgrading repositories.............................................................................102To upgrade a repository......................................................................102

After upgrading Data Services.................................................................103

Citrix Support 105Chapter 6

Installing BusinessObjects Data Services on a Citrix Server..................106Initial installation.................................................................................107


Contents

Running Data Services components in multi-user mode.........................108Serial access to the License, Server, and Repository Managers.......108Parallel access to the Management Console and Designer..............108Using a shell script to access the Designer.......................................109

Publishing Data Services.........................................................................114To publish a Data Services component..............................................115Connection management...................................................................117Client setup........................................................................................117

Limitations................................................................................................117

Directory Data 119Chapter 7

Directory listing and update schedule......................................................120U.S. Directory expiration..........................................................................122U.S. Directory expiration schedule..........................................................122U.S. National Directories are zipped.......................................................123Where to copy directories........................................................................123

Copy International directory files to a non-default location ...............124Download directories from the internet....................................................125Install directories from disk on Windows.................................................125

Unzip Windows file with Winzip..........................................................125

Global Parsing Options 127Chapter 8

Data Cleanse repository database requirements and preparation..........128DB2 database setup requirements.....................................................128Microsoft SQL Server database setup requirements.........................129Oracle database setup requirements.................................................129MySQL database setup requirements................................................130

Install Global Parsing Options.................................................................130Silent installation......................................................................................132

To perform a silent-mode installation.................................................132


Contents

To install using the command line......................................................133

Index 137


Contents


Contents

Preparing to Install DataServices

1

Pre-installation overviewBusinessObjects Data Services provides an open and flexible architecturethat supports a multitude of deployment and configuration scenarios. Beforeyou install BusinessObjects Data Services you should:

• Ensure that that your network and systems meet the basic requirementsfor a BusinessObjects Data Services installation.

• Obtain the BusinessObjects Data Services software by electronicdownload or on CD/DVD, as well as any required licensing keycodes.

• Review the BusinessObjects Data Services Release Notes and the DataServices Architecture section of the BusinessObjects Data ServicesGetting Started Guide.

• Ensure that the user who will run the installation setup program hasadequate permissions to complete the installation tasks.

• Decide which BusinessObjects Data Services components to install andwhich of your own components to integrate.

• Determine where the components should be installed and consider howyou should prepare your infrastructure and set up your environment,including server locations.

• If you are using an existing database server, create a database instanceif you want to configure a repository during Data Services installation.

• Check available port assignments and verify that all machines that willbe part of your BusinessObjects Data Services deployment have therequired network access to each other.

• Decide whether you want to take advantage of Windows clusteringfail-over support which attempts to automatically restart your Data Servicesservices in the event of a hardware or Windows software failure.

• Choose an installation method.

The following sections list the core software and system requirements, thechoices available to you within the core requirements, and the install methodsavailable to you for installing BusinessObjects Data Services.

Related Topics• Getting Started Guide: Data Sevices Architecture• System requirements on page 11• Network requirements on page 11• User permissions for installing Data Services on page 12• Choose components and determine component distribution on page 13


Preparing to Install Data Services1 Pre-installation overview

• Create a database for each repository on page 17• Check port assignments on page 18• Create a Windows cluster on page 20

System requirements

For a detailed list of supported environments and hardware requirements,see the Platforms Availability Report available on the Business Objectssupport site: http://support.businessobjects.com/documentation/supported_platforms. This document includes specific version and patch-levelrequirements for databases, applications, web application servers, webbrowsers, and operating systems.

Generally, the following components must be preinstalled and configuredcorrectly before you can install BusinessObjects Data Services:

• Web application server (unless you want to use the Tomcat installationpackaged with Business Objects products, or you do not want to installthe Web Tier components)

• Database software that is compatible with the Data Services repository(unless you want to use the MySQL installation packaged with the DataServices installer).

Note: Only the database client tools or middleware needs to be installedon the Data Services server; the database server itself can reside on aseparate physical machine accessible by network from the Data Servicesserver.

Note: For the repository, BusinessObjects Data Services requires a databasethat stores metadata about all objects created with the Data ServicesDesigner. For best Designer performance, Business Objects recommendsthat the repository database server and the Designer computer reside in thesame network.

Network requirements

When installing BusinessObjects Data Services on multiple machines, youmust ensure that each machine can communicate over TCP/IP with themachine running the database that contains the repository.


1Preparing to Install Data ServicesPre-installation overview

http://support.businessobjects.com/documentation/supported_platforms


Client components, such as the Data Services Designer, require networkaccess to the Data Services Job Server(s).

Note: If your servers are firewalled, you may need to open the necessaryports to allow the Data Services client components to communicate with theservers.

User permissions for installing Data Services

To successfully install BusinessObjects Data Services on Windows, the userrunning the setup program must have the permissions listed in the tablebelow.

Required permissionsCategory

Administrative privileges on the local machine.Operating Sys-tem

TCP/IP access to all machines where you want to install com-ponents — all specified ports must be available.

Network

Rights to add and drop tables to and from the database, plusrights to read, write, and edit table rows.

Database

It is recommended that you use the same user account for in-stalling BusinessObjects Data Services and your web applica-tion server.

Web applica-tion server

Note:

• The following scenarios are not supported:• Installing on a domain controller.• Installing on a machine where the Windows default security settings

given to the local Administrators group have been modified.• To run the Data Services Designer, a user requires both read and write

access to the Data Services installation folder. If you choose to install inthe default Program Files folder, regular users do not have write access.Choose another installation directory or assign the Designer user writeaccess to LINK_DIR.



Choose components and determine componentdistribution

You may choose to upgrade or install components on one or more computersbased on available resources and amount of system traffic.

Note: You must install the Designer on a supported Windows platform. Youcan install the other components on Windows, UNIX, or Linux platforms.

The installation program can install multiple Data Services feature categories.

DescriptionComponentFeature category

Executes batch Data Services jobs.Job Server

Server Components

Provides real-time access to Data Ser-vices, routes real-time messages to theappropriate real-time interface.

Access Server

Provides access to techologies such asJMS (Java Messaging System) andSalesforce.com.

Technology Interfaces

Collects metadata from a BusinessOb-jects Enterprise system for impact andlineage analysis in the Data ServicesManagement Console.

Metadata Integrator

Graphical user interface that is used todesign and test all Data Services jobs.Designer

Client Components Creates and manages all types of DataServices repositories (local, central,profiler, and Global Parsing Option).

Repository Manager



DescriptionComponentFeature category

Web application server that can be usedto deploy BusinessObjects applications.You can also use your own existing webapplication server.

Tomcat application server(optional)

Web Tier Compo-nents

Web application that manages the DataServices environment (monitors, exe-cutes, and schedules jobs), as well asmetadata reporting (auto-documenta-tion, Validation and Operational dash-boards, Data Quality reports, and impactand lineage analysis).

Management Console

Message Client SDK that other applica-tions can use to integrate with real-timeData Services jobs.

Message ClientComponents

Data Services product documentation.DocumentationComponents

For complete description of the components and how they interact, see "DataServices Architecture" in the BusinessObjects Data Services Getting StartedGuide.

Note: You can configure several Job Server and Access Server instancesfrom one Job Server or Access Server installation. Configure Job Server andAccess Server instances using the Server Manager.

You can install Data Services components on one or more computers basedon available resources and the amount of traffic the system processes. Beforeinstalling Data Services components, consider the following:

• A local repository connects a Data Services Designer with a Data ServicesJob Server. You can install a Job Server on the same computer as therepository, on a stand-alone computer (with repository database clientsoftware), or on the same computer as a Data Services Designer.

• Any Data Services Designer can access any local repository and DataServices Job Server. Multiple Data Services Designers cannotsimultaneously access the same local repository. Simultaneous access



risks metadata corruption in the repository. Also, you cannot link DataServices Designer to more than one local repository at any given time.

• Install database client software on the computer containing the Job Serverto support the repository associated with that Job Server. For example,if the repository associated with a Job Server named "oradev" is an Oracledatabase, then Oracle client software must be installed and configuredon the computer containing the "oradev" Job Server.

The following diagram depicts a simple distribution of Data Servicescomponents among computers in a network. Note that you can install eachData Services component on one or more computers. Also note that thereare many possible connections between Data Services components. Eachbox in the diagram represents a different computer.





You can install the Data Services Management Console on any computerwith or without other Data Services components. It is Java-based. You havethe choice to use the packaged Tomcat server, or use a previously installedapplication server.

Note: If BusinessObjects Enterprise is installed on the same machine withthe BusinessObjects Enterprise-packaged Tomcat application server, theinstaller will detect the existing Tomcat instance and share it withBusinessObjects Data Services instead of installing a new instance.

Related Topics• Getting Started Guide: Data Services Architecture• Getting Started Guide: Data Services distributed architecture

Create a database for each repository

Data Services uses four types of repositories:• Local — working repositories where you create and modify applications.• Central — supports multi-user development and allows for check-in and

check-out. Also provides versioning to keep and allow restore for severalversions for the same object.

• Profiler — stores profiling metadata when the built-in Data Services profileris configured.

• Global Parsing Option — stores dictionaries for the Global Parsing Optionsused by Data Cleanse transforms.

You associate each Job Server with one or more local repositories. Thereis no relationship between central repositories and Job Servers.

Create local repositories before you install each Job Server, or configurethem after you install Job Servers by using the Repository Manager.

• To set up a single-user development environment, create a database forthe local repository.

• To set up a multi-user development environment, create databases foreach local repository (one per user) and a database for the centralrepository.

• Multiple Designers can share the same Global Parsing Option repository.• Multiple Designers can share the same profiler and profiler repository.



Related Topics• Repository database requirements and preparation on page 22• Using the Repository Manager on page 72• Advanced Development Guide: Multi-user development

Check port assignments

Verify that all ports to be used by Data Services components are availableand not in use by other programs on each computer.

For a development system, you can install many components on the samecomputer. This simplifies many connections between components (the hostname is always the same), but you must still define connections based onTCP/IP protocol.

Note: If you choose to set ports manually during installation, verify that theports you specify are available. The following example configuration diagramshows default port numbers, as well as the packaged Tomcat installation.Default ports for other web application servers may differ.



This table details Data Services default ports:

Component

To setDefaultDescriptionPort

Job Server

Use Server Manager3500Receives commands fromDesigner, Access Server,and schedulers.

Job Server port orTCP/IP port

Use Server Manager4001Receives commands andsends data to adapters.

Adapter/SNMPcommunicationport

Packaged Tomcat Application Server

Tomcat conf\server.xml28080Supports communication be-tween web browsers and themanagement console.

HTTP port

Tomcat conf\server.xml28005

The Tomcat service uses thisport to start and shutdownthe Web Server which sup-ports the Management Con-sole.

Shutdown port

Access Server

Use Server Manager4000Receives and sends mes-sages from clients and ser-vices

Communicationport

Designer

ChooseTools > Optionsin the Designer.5001Supports communication for

the debugging featureInteractive Debug-ger port

Address Server



Component

To setDefaultDescriptionPort

LINK_DIR\bin\address_server\AddressServerConfig.txt

40010Supports communication forthe Address ServerControl port

LINK_DIR\bin\address_server\AddressServerConfig.txt

40011Supports communication forthe Address ServerApplication port

Check network connections

Before you install Data Services components, check the computers involvedand verify network connections by executing the ping command on eachcomputer.

For example, if the Designer will be on a Windows computer and your JobServer will be on a UNIX computer, from the Windows computer open theDOS prompt and enter:C:\> ping hostname

where hostname is the host name of the UNIX computer.

Then from the UNIX computer, log in as root and from the prompt, enter:$ ping hostname

where hostname is the host name of the Windows computer.

Create a Windows cluster

To take advantage of fail-over support for Data Services services in aWindows Clustering Environment, you must create a Windows cluster beforeyou install Data Services (refer to your Microsoft documentation for details).If you choose this option, in the event of a hardware failure or Windows



software failure, the Windows Cluster Manager will attempt to restart yourData Services services.

After you create a Windows cluster:

1. Install Data Services on a shared drive from the first cluster computer.2. After you install Data Services, create a new resource for the Data

Services service as a Generic Service.a. Open the Cluster Administrator.b. Under Active Resources, add a new resource. Enter a Name,

Description and choose Generic Service for the Resource Type.c. Configure resource dependencies. Since Data Services is a Generic

Service, it requires a file share, IP address, Network Name, andavailable physical disk resources.

d. Configure Generic Service Parameters. Enter DI_JOBSERVICE asthe Service name.

3. Create a new resource for the Data Services Web Server Service as aGeneric Service. (If you did not install the Data Services ManagementConsole, skip this step.)a. Under Active Resources, add a new resource. Enter a Name,

Description and choose Generic Service for the Resource Type.b. Configure Generic Service Parameters. Enter DataServicesWebServer

as the Service name and click to select the Use Network Name forcomputer name option.

4. Run the Data Services cluster install utility (js_cluster_install.exelocated in the bin directory of your Data Services installation) on the othercluster computers to populate them with the Data Services service-relatedinformation.a. Copy the js_cluster_install.exe and bodi_cluster_conf.txt

files from the Data Services bin directory on your primary clustercomputer.

b. Paste these files to each non-primary cluster computer and run thefollowing commands to install the Data Services Service and DataServices Web Server Service, and to replicate the shortcuts set up onthe primary cluster computer:js_cluster_install.exe -install if using system accountjs_cluster_install.exe -install -Uuser -Ppasswd -Ddomainwhen not using system account on primary nodejs_cluster_install.exe -remove



c. Data Services components will use a Cluster Network Name tocommunicate with other Data Services components over your network.Open the Data Services Server Manager, enter the Cluster NetworkName and click Apply.

Note: If Job Servers are already configured before you enter theCluster Network Name, the Server Manager will prompt you to entera password for each currently configured repository associated witheach configured Job Server.

d. Click Restart.

Related Topics• Beginning your installation on page 36

Repository database requirements andpreparation

BusinessObjects Data Services stores your design metadata for source andtarget tables as well as database functions and definitions of built-in DataServices objects in database tables. This set of database tables is called theData Services repository.

You can create one repository during installation. If you want to create arepository in an existing database, you must create space for the repositorybefore you run the Data Services installation program. The Data Servicesinstallation program connects to the repository and populates it.

A Data Services repository requires a minimum of 20 MB of free disk spaceon the database server.

The following sections detail required settings for:

• IBM DB2• Microsoft SQL Server• MySQL• Oracle• Sybase ASE

Before you install BusinessObjects Data Services, you should review thisinformation in order to properly prepare your repository database.


Preparing to Install Data Services1 Repository database requirements and preparation

Note: You can also choose to skip creating a repository during installation,and use the Repository Manager to create it at a later time.

Note: If you want to use multi-byte metadata, such as Japanese columnnames on imported tables or multi-byte data in Data Quality reports, yourdatabase must be configured to use Unicode character encoding, such asUTF-8.

Related Topics• Using the Repository Manager on page 72

Installing MySQL as the repository database

MySQL database server is an open-source database that provides local datastorage. The BusinessObjects Data Services setup program can install andconfigure MySQL as the database server for a BusinessObjects Data Servicesinstallation. If you already have MySQL installed, the installation programcan be used to configure the repository database using your existing databaseengine.

Note:

• The packaged MySQL database can be used only to store the differentData Services repository tables. You are not allowed to store your owndata (datamart, data warehouse) in this MySQL instance.

• If you choose to use the packaged MySQL installation, the databaseserver is uninstalled if you uninstall Data Services. Back up the DataServices repository with the MySQL admininstration tools if you want touninstall Data Services before upgrading to a new version.

MySQL installation details

Data Services installation setup creates a new MySQL installation with thefollowing details:

ValueProperty

DataServicesODBC datasource name

DataServicesMySQL schema name

BOE120MySQLMySQL service name


1Preparing to Install Data ServicesRepository database requirements and preparation

Note: The TCP/IP port number, the root user password, and the usernameand password for the account that owns the MySQL schema can beconfigured during installation setup.

The MySQL administration tools are also installed to the MySqlAdmin5 folderat the same level as LINK_DIR. To start or stop the MySQL service, you canuse the installed MySQL administration tools or the "Services" panel locatedin the "Administrative Tools" section of the Windows Control Panel.

For more information about administering the MySQL installation, refer tothe MySQL documentation at http://dev.mysql.com/doc/index.html.

To set up a database account for BusinessObjectsData Services

To administer the repository database, you need to set up a databaseaccount. If you choose to install MySQL as part of your BusinessObjectsData Services installation, you are prompted during installation to set up thisaccount. If you plan to use your own database, you should complete thesteps listed below before you install BusinessObjects Data Services.

1. Create or select a user account that provides BusinessObjects DataServices with the appropriate privileges to your database server.

2. Verify that you can log on to your database and carry out administrativetasks using this account.

Setting up an empty database for the repository

If you want to use an existing database server, you must create a newdatabase on your database server before you install BusinessObjects DataServices.

The following database servers are supported for the repository database:

• IBM DB2• Microsoft SQL Server• MySQL• Oracle• Sybase ASE



http://dev.mysql.com/doc/index.html

Note: For information related to supported database software and versionrequirements, review the online BusinessObjects Data Services supportedplatforms document: http://support.businessobjects.com/documentation/supported_platforms

To use your existing database with BusinessObjects Services, you need toprepare it.

1. Create a new database.2. Create a new user account and password for the database — to be used

by BusinessObjects Data Services.3. Specify that the new user account has required permissions to create,

modify, and delete tables and create procedures so that the databasecan be modified as required.

4. Record the name of the database, the user account, and the passwordwhen you run the BusinessObjects Data Services installation setupprogram.

During the installation setup, you can choose to reinitialize the existingdatabase. This will cause new tables to be created in your existing databaseto store BusinessObjects Data Services data. If you are unsure of theprocedure for creating a new database, consult your specific database serverdocumentation.

Note: If you have an existing Data Services or Data Integrator repository,you can upgrade the repository during installation or use the Data ServicesRepository Manager to upgrade it after installation. If you have an existingData Quality repository, create a new Data Services repository and see theData Services Migration Considerations.

32-bit and 64-bit notes

Data Services 32-bit and 64-bit applications are supported on a variety ofoperating systems. When you use a database client with the Data Services32-bit application, the 32-bit database client libraries must be installed andreferenced in the library paths.

For example, the default installation of the Oracle 64-bit client includesinstallation of the 32-bit client. For non-standard installations, these librariesmust be specified as part of the installation. After installation, the librariesshould be in the $ORACLE_HOME\lib32 directory.





If these 32-bit libraries are not present, you receive an error message statingthat Data Services cannot load the client library. Examples of error messagesinclude:(5.2) 02-05-02 14:55:23 (E) (26797:0001) CON-120103: Systemcall <dlopen> to load and initialize functions failed for<libclntsh.a>. Make sure the SHARED LIBRARY is installed andresides in the correct location.\(5.2) 02-05-02 14:55:23 (E) (26797:0001) REP-100108: Cannotperform operation on Repository<Default Repository> because aconnection to the repository was never opened. A connectionmust be opened to the repository before performing any operation.

When you use a database client with the Data Services 64-bit application,the 64-bit client libraries must be installed and referenced in the library paths.

Related Topics• DB2 database setup requirements on page 26• Microsoft SQL Server database setup requirements on page 27• MySQL database setup requirements on page 27• Oracle database setup requirements on page 28• Sybase database setup requirements on page 29

DB2 database setup requirements

A local or central Data Services repository requires that you create adedicated database and define a user with the rights:

• To create a table• To start a session• To create a sequence

Install the DB2 Application Enabler software and use DB2 Control Centerand DB2 Script Center to verify the connection between the Designercomputer and the Data Services repository computer.

When the database is created, you need to prepare it for the BusinessObjectsData Services installation.

Related Topics• To prepare your database on page 29



Microsoft SQL Server database setup requirements

When you create a repository on Microsoft SQL Server, choose betweenWindows authentication (by selecting the check box) or Microsoft SQL Serverauthentication (by completing the Microsoft SQL Server user name andpassword fields):

• Windows authentication — Microsoft SQL Server validates the loginaccount name and password using information from the Windowsoperating system.

• Microsoft SQL Server authentication — Microsoft SQL Serverauthenticates the existing Microsoft SQL Server login account name andpassword.



MySQL database setup requirements

When you create a repository on MySQL, you must supply the followinginformation in order to log in to the Repository Manager and the Designerlater:

• ODBC (MySQL) Data Source Name• Username• Password

The ODBC name is either the user Data Source Name (DSN), or the systemDSN.

Note: ODBC driver version 3.51.22 is recommended for use with MySQL.

If you select the option to install and configure MySQL that is supplied withyour installation, the installation creates a MySQL database with the defaultsettings for the repository database.




Caution: If you provide the password when creating an ODBC data source,users will be able to log into the Data Services Designer without specifyinga password. If you choose to install the packaged MySQL server, thepassword is automatically specified for the ODBC data source, and anyonewith a valid username can access the Data Services Designer withoutspecifying a password.


Oracle database setup requirements

A local or central Data Services repository requires that you create adedicated database and define a user with the rights:


Grant the user the connect and resource roles. For Oracle 10G/R2, alsogrant the create view role.

Install the Oracle client software and use SQL*Plus to verify the connectionbetween the Designer computer and the Data Services repository.

Note: To store multi-byte characters in a Data Services repository tablewhen the repository is on an Oracle database, you must change the Oracledatabase character set to a code page that supports the multi-byte languagethat you plan to use or you risk corrupting your metadata. For example, tostore Japanese characters, change the Oracle database character set toeither SHIFT_JIS or UTF8.





Sybase database setup requirements

A local or central Data Services repository requires that you create adedicated database and define a user.

Note: For UNIX Job Servers, when logging in to a Sybase repository in theDesigner, the case you type for the database server name must match theassociated case in the SYBASE_Home\interfaces file. If the case does notmatch, you might receive an error because the Job Server cannotcommunicate with the repository.

If you are using both Sybase and Microsoft SQL Server on a Windowsplatform, ensure the Sybase path precedes the Microsoft SQL Server pathin the environment variables %PATH% statement.



To prepare your database

1. Create a new, empty database on your database server.2. Create a new user and assign it a secure password.3. Ensure that the new account has permission to create, modify, delete

tables and create procedures so that BusinessObjects Data Services canmodify the database as required.

Note: If you are not the owner of the database, you must havepermissions to perform the necessary operations.

4. Ensure the following are set up before you begin your installation:

Information requiredDatabase type

DB2 database aliasDB2

Database nameMicrosoft SQL Server




ODBC datasource nameMySQL

tnsnames connect identifierOracle

Sybase server name

Database name

Sybase ASE

Note: The Sybase server name is a combination of the host name andthe port number which is set by your database administrator in the filesql.ini.

5. Record these details because you are required to provide them duringinstallation:• The name of your database, ODBC datasource name, Sybase server

name, Oracle tnsnames connect identifier, or DB2 database alias.• The user account and the password authorized to the database.

For information on how to create a new database, consult your databaseserver documentation or your database administrator.

Related Topics• DB2 database setup requirements on page 26• Microsoft SQL Server database setup requirements on page 27• MySQL database setup requirements on page 27• Oracle database setup requirements on page 28• Sybase database setup requirements on page 29



Installation scenarios

Standard installation overview

A standard installation allows you to specify which components to install.You may want to perform a custom installation when you want to excludesome components, or install only a limited set of components.

The installable feature categories include:• Server Components• Client Components• Web Tier Components• Message Client Components• Documentation Components

By default, MySQL is installed as the repository database, and Tomcat isinstalled as the web application server. You can also choose to use yourown database or web application server during the installation process.

Note: During installation, you can choose whether to configure many of thecomponents, such as Job Servers and Access Servers. If you skip componentconfiguration during installation, you can use the Data Services configurationtools to accomplish these tasks after installation has finished.

Related Topics• Choose components and determine component distribution on page 13• Getting Started Guide: Data Services Architecture

To perform a standard installation

1. Obtain the Data Services software and licensing keycodes.2. Confirm requirements and determine component distribution.3. Check port assignments and network connections.4. Create databases for repositories that you want to configure during

installation.5. Install Data Services components.


1Preparing to Install Data ServicesInstallation scenarios

Following installation, you can perform any additional configuration neededusing Data Services configuration tools. For example, you can:• Create additional local, central, or Global Parsing Option repositories with

the Repository Manager.• Register any repositories in the Management Console.• Create and configure a profiler repository.• Configure additional Job Servers with the Server Manager.• Add any additional license keycodes with the License Manager.

Related Topics• Pre-installation overview on page 10• Beginning your installation on page 36• Using the Repository Manager on page 72• Using the Server Manager on page 76• Using the License Manager on page 84• Logging in to the Management Console on page 72

Silent installation overview

You can run a silent installation to install BusinessObjects Data Servicesfrom the command line using a response file containing installation setupparameters. This method is particularly useful when you need to performmultiple installations or you do not want to interrupt people who are workingon machines in your system.

You can also incorporate the silent installation command into your own buildscripts. For example, if your organization uses scripts to install software onmachines, you can add the silent BusinessObjects Data Services installationcommand to those scripts.

You may want to choose a silent installation if:

• You are already familiar with the BusinessObjects Data Servicesinstallation program.

• You need an automated method for performing similar installations onseveral machines.

• You do not want to run the BusinessObjects Data Services Setup program.


Preparing to Install Data Services1 Installation scenarios

Related Topics• Silent installation on page 60


1Preparing to Install Data ServicesInstallation scenarios


Preparing to Install Data Services1 Installation scenarios

Standard Installation of DataServices

2

Beginning your installationThe following instructions lead you through the initial steps of setting up yourBusinessObjects Data Services installation on Windows. In this stage youwill do the following:

• Agree to the license terms.• Enter the product key codes.• Select where to install BusinessObjects Data Services.• Select which features to install.

When you perform the following installation setup, all the components thatyou select are installed on the local machine.

You can start the installation setup by running setup.exe, or by insertingthe application CD, selecting a language, and clicking Install if your systemis configured for autorun. After the Welcome screen is displayed, click Nextto begin your installation.

Tip: Before beginning your installation, review the Installation Overview toensure that you have prepared all necessary systems.

Related Topics• Pre-installation overview on page 10

To accept the license agreement

At the "License Agreement", review and accept the license agreement forBusinessObjects Data Services. You must accept the agreement to continuewith the installation setup.


Standard Installation of Data Services2 Beginning your installation

1. Review the License Agreement.2. Select I accept the License Agreement.

You cannot continue unless you accept the License Agreement.

3. Click Next to continue the installation setup.The "User Information" screen is displayed.

To enter user information and a product keycode

At the "User Information" screen, enter user information and provide a productcode for your BusinessObjects Data Services installation.


2Standard Installation of Data ServicesBeginning your installation

1. Provide your user credentials in the Full Name and Organization fields.This information personalizes your installation and is recorded in theregistry.

2. Enter a valid code in the Product Keycode field.

Note: You can enter a single base product keycode during Data Servicesinstallation. If you need to add additional keycodes for other features thatyou've purchased, you can enter them after installation with the DataServices License Manager.

3. Click Next to continue the installation setup.The "Directory Selection" screen is displayed.

Related Topics• Using the License Manager on page 84



To specify the installation location

At the "Directory Selection" screen, enter the location for yourBusinessObjects Data Services installation.

1. Specify where to install the BusinessObjects Data Services componentsin the Destination Folder field.The default location is C:\Program Files\BusinessObjects\BusinessObjects Data Services\.

Restriction: The maximum allowable path length is 100 characters.

Note: Data Services installation setup creates a Windows environmentnamed LINK_DIR for this path. LINK_DIR is used throughout the DataServices documentation to refer to this path.

Depending on your component selection, the Data Services installationsetup may create other folders or files at the same level as the DataServices installation folder:• BusinessObjects Enterprise 12.0



• common

• deployment

• javasdk

• Tomcat55

• LanguagePacks.xml

2. Click Next to continue the installation setup.The "Select Features" screen is displayed.

Note: To run the Data Services Designer, a user requires both read andwrite access to the Data Services installation folder.

To select which features to install

At the "Select Features" screen, choose which components to install.

You can select or deselect the following categories and their sub-components:



DescriptionFeature category

Includes the Job Server, Access Server, MySQL (Serv-er), Metadata Integrator, Address Server, TechnologyInterfaces, and other adapters.

All Server components install by default unless deselect-ed.

Server compo-nents

Includes the Designer and Repository manager.

All client components install by default unless deselected.

Client compo-nents

Includes the optional Tomcat application server installa-tion and the Management Console web application (in-cluding the Administrator, Impact and Lineage Analysis,Operational Dashboards, Data Quality Dashboards, andAuto Documentation).

All Web Tier components install by default unless dese-lected.

Web Tier compo-nents

Includes the C++ and Java libraries for integrating exter-nal application with Data Services real-time jobs.

The Message Client components do not install by defaultunless selected.

Message Clientcomponents

Includes BusinessObjects Data Services product docu-mentation as PDF documents.

The Documentation components install by default unlessdeselected.

Documentationcomponents

1. Select the features that you want to install. Each component displays adrop-down menu that allows you to choose from the following options:• Will be installed on local hard drive — Installs only the selected

component in the tree for that feature.• Entire feature will be installed on local hard drive — Installs all

components in the tree for that feature.



• Entire feature will be unavailable — No components for that featureare installed. An X appears next to the deselected component.

2. To check if you have enough available disk space for the selectedcomponents, click Disk Cost.The disk cost screen appears. Click OK to return to feature selection.

3. If you want to reset the feature selection to default, click Reset.4. When you have made your component selections, click Next to continue

the installation setup.The next screen appears based on the features that you chose to install.

To select a repositoryAt the "Repository Selection" screen, choose which type of database to usefor the repository.

1. Select the type of repository that you want to configure.• Install MySQL database server (Default)


Standard Installation of Data Services2 To select a repository

Note: The MySQL administration tools are also installed to theMySqlAdmin5 folder at the same level as LINK_DIR.

• Use an existing database server• Skip configurationIf you choose to install MySQL or use an existing database, you canconfigure one local repository during installation. If you skip theconfiguration, or you need more repositories, you can configure additionalrepositories later using the Data Services Repository Manager.

2. Click Next to continue the installation setup.The next screen appears based on which configuration you chose toperform.

Related Topics• To create or upgrade repositories on page 73

To configure a MySQL database server

The "MySQL Database Server Configuration" screen appears if you choseto install MySQL as the database server for the new installation.


2Standard Installation of Data ServicesTo select a repository

1. Specify the port number for the MySQL database server in the MySQLPort Number field.The default port number is 3306. Use this number unless this port isunavailable.

2. Specify and confirm a password for the MySQL root user account in theMySQL root User Account area.The root user is required for administrative and maintenance tasks onthe MySQL server, such as creating new users for more repositories orperforming backups.

3. Specify and confirm a username and password for the MySQL Repositoryuser account in the MySQL Repository User Account area.

4. Click Next to continue the installation setup.The "Configure Job Server" screen is displayed.


Standard Installation of Data Services2 To select a repository

To configure an existing database server

The "Local Repository Location" screen appears if you chose to use anexisting database server as your repository for the new BusinessObjectsData Services installation. At this screen, specify the connection informationfor the database where the repository will be created.

1. Select a database type from the Database type drop-down list.Depending on your database type selection, corresponding input fieldsare displayed.

2. Provide the database-specific required information in the fields displayed.

Required informationDatabase type

DB2 datasource nameDB2


2Standard Installation of Data ServicesTo select a repository

Required informationDatabase type

Database server name

Database name

Windows authentication

Microsoft SQLServer

ODBC datasource nameMySQL

Database connection nameOracle

Sybase server name

Database name

Sybase ASE

3. Specify the user name for the account authorized to use the database inthe User name field.

4. Specify the password for the account authorized to use the database inthe Password field.

5. Click Get Version to check the database connection and verify whethera version of the repository already exists. If you are upgrading from anexisting Data Integrator or Data Services repository, click Upgrade tokeep and upgrade the existing repository. If you are creating a newrepository, click Create.

Caution: If you choose to use Create on an existing repository, therepository tables are recreated, and all data in the existing repository willbe lost.

6. Click Next to continue the installation setup.The "Configure Job Server" screen is displayed.

To configure a Job ServerAt the "Configure Job Server" screen, create a new job server.


Standard Installation of Data Services2 To configure a Job Server

1. Select the type of Job Server configuration to perform:• Configure a new Job Server (Default)• Skip Job Server configurationIf you skip the configuration, you can configure a Job Server later usingthe Data Services Server Manager. Any existing Job Servers from aprevious Data Integrator or Data Services installation will be kept, unlessit has been uninstalled or DSConfig.txt has been removed.

2. If you chose to configure a new Job Server, specify a name and portnumber for the new server in the Job Server name and Job Server portfields.The default Job Server port is 3500.

3. If you need to configure SNMP support or change the runtime resourcesfor the Job Server, click Advanced.The Job Server details screen is displayed. Make any necessaryconfiguration changes and click OK.

4. Click Next to continue the installation setup.The "Login Information" screen is displayed.


2Standard Installation of Data ServicesTo configure a Job Server

Note: If you are using a Sybase or DB2 repository, and need to change thelocale of your Job Server, use the Data Services Locale Selector afterinstalling Data Services. To use the Locale Selector, choose Start >Programs > BusinessObjects XI 3.0 > BusinessObjects Data Services> Data Services Locale Selector.

Related Topics• To configure Job Servers on page 78

To specify login information

At the "Login Information" screen, specify the account that the Data ServicesWindows service will use to start Job and Access Servers.

1. Select the type of account to use:• Use system account• Use this accountIf you use the system account, you must reboot the system following DataServices installation.


Standard Installation of Data Services2 To configure a Job Server

Note: The account you use must have:• full access to the Data Services installation directory• rights to Log on as a Service

You can change this account and password later using the WindowsServices tool.

2. If you chose to specify a user account, enter the username and passwordin the User and Password fields.

3. Click Next to continue the installation configuration.The "Configure Access Server" screen is displayed.

To configure an Access ServerAt the "Configure Access Server" screen, create a new access server.

1. Select the type of Access Server configuration to perform:• Configure a new Access Server (Default)• Skip Access Server configuration


2Standard Installation of Data ServicesTo configure an Access Server

Note: The Access Server is only required for real-time processing.Because of this, you should skip configuration if you do not need real-timeprocessing. Real-time and transactional processing is not licensed in allData Service packages and is available as an option.

If you skip the configuration, you can configure an Access Server laterusing the Data Services Server Manager. Any existing Access Serversfrom a previous Data Integrator or Data Services installation will be kept,unless it has been uninstalled or DSConfig.txt has been removed .

2. If you chose to configure a new Access Server, specify a directory andport number for the new server in the Directory and Communicationport fields.The default directory for the Access Server is LINK_DIR\Log\AccessServer_1.

3. Check Enable Access Server if you want the Access Server to startwhen the Data Services system service is started. By default, EnableAccess Server is checked.

4. Click Next to continue the installation setup.If BusinessObjects Enterprise is installed, the "Configure MetadataIntegrator" screen is displayed. If not, the next screen appears based onwhich features you chose to install.

Related Topics• To configure Access Servers on page 82

To configure Metadata IntegratorIf you chose to install Metadata Integrator and BusinessObjects Enterpriseis already installed, the "Configure Metadata Integrator" screen appears. Atthis screen, create a new Metadata Integrator configuration.


Standard Installation of Data Services2 To configure Metadata Integrator

1. Select the type of Metadata Integrator configuration to perform:• Configure a new Metadata Integrator• Skip Metadata Integrator configurationIf you skip the configuration, you can configure Metadata Integrator laterby choosing Start > Programs > BusinessObjects XI 3.0 >BusinessObjects Data Services > Data Services Metadata Integrator.

2. If you chose to create a new Metadata Integrator configuration, specifya name for the new configuration in the Configuration name field.

3. Click Next to continue the installation setup.The next screen appears based on which configuration you chose toperform.

To specifyMetadata Integrator configuration details

At the "Configure Metadata Integrator" screen, specify details for yourMetadata Integrator configuration.


2Standard Installation of Data ServicesTo configure Metadata Integrator

1. Specify the host name of your BusinessObjects Enterprise CMS serverin the Server name field.

2. Check Enable SSL if you want to use a SSL secure connection.3. Specify the user name used to connect to the CMS server to register and

execute the Metadata Integrator in the User field.4. Specify the password for the CMS user in the Password field.5. Select the CMS authentication mode from the Authentication Mode

drop-down list.For more information about the available modes, see the BusinessObjectsEnterprise Administrator's Guide.

6. Specify the folder in which the CMS system adds the Metadata Integratoras a program object in the Folder name field.The default value is Data Services. If the specified folder does not exist,it is created automatically.

7. Specify configuration for your Data Services Repository database in the"Repository Database server" area.If you chose to use the packaged MySQL server or an existingBusinessObjects Enterprise MySQL installation, this area is disabled.


Standard Installation of Data Services2 To configure Metadata Integrator

8. Click Next to continue the installation setup.The next screen appears based on which features you chose to install.

To specify Metadata Integrator SSL details

If you chose to enable SSL for the Metadata Integrator, the "Configurerepository for Metadata Integrator" screen is displayed. At this screen, specifythe SSL details for your Metadata Integrator configuration.

1. Click Browse to specify the location of your SSL certificates.2. Specify the filenames for the Server SSL Certificate, SSL Trusted

Certificates, SSL Private key, and SSL Passphrase in the appropriatefields.

3. Click Next to continue the installation setup.


2Standard Installation of Data ServicesTo configure Metadata Integrator

To select a web application serverconfiguration option

If you chose to install the Web Tier Components, you need to provideinformation about the web application server that will work with yourBusinessObjects applications. Use the "Select Web Application Server"screen to either install Tomcat as your application server, or to work withyour existing web application server.

To configure your web application server for BusinessObjects Data Services,you need account information along with port information.

1. Select one of the following options:• Use a pre-installed Web Application Server• Install Tomcat application server

2. To use your current Web application server, you can Specify your serverfrom the drop-down list provided.


Standard Installation of Data Services2 To select a web application server configuration option

Tip: You can configure the server during the current installation setup.You will need to provide access information for this server in a subsequentscreen.

3. Click Next to continue the installation setup.

The next screen appears, based on your selection.

To configure your Tomcat application server

The "Configure Tomcat" screen is displayed during installation setup if youchoose to install Tomcat as the web application server for your currentBusinessObjects Data Services installation. At this screen, configure Tomcatand the Java SDK.

1. In the fields provided, specify which port numbers will be used by Tomcatfor connection, shutdown, and redirect.

Tip: You can accept the default values for each port setting.

2. Click Next to continue with the installation setup.


2Standard Installation of Data ServicesTo select a web application server configuration option

The "Start Installation" screen is displayed.

Note: If you need to change the Tomcat port settings after installation, youcan modify the Tomcat setup.xml file. By default, this file is installed to theTomcat55\conf folder at the same level as LINK_DIR.

To configure an existing Web application server

The Configure Web Application Server screen is displayed during installationafter you specify an existing server in the Select Web Application Serverscreen. To properly install web components on your web application server,you must provide specific configuration information about your existing webapplication server.

1. Specify the required configuration information for your existing webapplication server.

Required informationWeb Appli-cationServer

• Server Instance: Name of the current web applicationserver instance (e.g. "localhost").

• Service Name: Name of the Windows service if the appli-cation server will be installed as a Windows service (e.g."Tomcat5").

• Application Server Installation Directory: The directorywhere the web application server is installed.

ApacheTomcat 5.5

• Port: Administration port of the application server -mandatory for Weblogic (e.g. "7001").

• Username: User name with administration rights to theapplication server - mandatory for Weblogic.

• Password: Password for account with administration rightsto the application server - mandatory for Weblogic.

• Server Instance: Name of the current web applicationserver instance (e.g. "mserver1").

• Application Server Installation Directory: The directoryfor the web application server instance (e.g. C:\bea\weblogic10\samples\domains\wl_server).

WebLogic10


Standard Installation of Data Services2 To select a web application server configuration option

Required informationWeb Appli-cationServer

• Port: Administration port of the application server -mandatory for Weblogic (e.g. "7001").

• Username: User name with administration rights to theapplication server - mandatory for Weblogic.

• Password: Password for account with administration rightsto the application server - mandatory for Weblogic.

• Server Instance: Name of the current web applicationserver instance (e.g. "mserver1").

• Application Server Installation Directory: The directoryfor the web application server instance (e.g. C:\bea\weblogic92\samples\domains\wl_server).

WebLogic 9

• Port: Administration port of the WebSphere applicationserver - the SOAP port. Default SOAP port will be used ifnot specified.

• Username: User name with administration rights to theWebSphere application server.

Note: If Admin is Secure is not selected you do not needto specify a username or a password.

• Password: Password for account with administration rightsto the application server.

• Server Instance: Name of the current web applicationserver instance (e.g. "server1").

• Virtual Host: The virtual host to which the application mustbe bound (e.g. "default_host").

• Admin is Secure: Select this option to enable securityrequiring administrative access credentials to the applica-tion. If WebSphere was installed with the secure option,this is required.

• Application Server Installation Directory: The directoryfor the web application server instance (e.g. C:\ProgramFiles\IBM\WebSphere\AppServer\profiles\App-Srv01).

WebSphere6.1

2. Click Next to continue the installation setup.The "Start Installation" screen is displayed.


2Standard Installation of Data ServicesTo select a web application server configuration option

Note: To deploy the Management Console to a web server farm, run theData Services installation setup on each web server in the farm.

To start the installationThe "Start Installation" screen is the final screen in the installation setup.

• Review the components that will be installed and any associated settings.If you want to make changes, use the Back button. All entries are retained;you do not need to re-enter all the information.

Note: If you are running the setup.exe program from the command line,and have the -w filename parameter switch enabled, this is the point atwhich you can Cancel the installation process to have the .ini file writtenwith all the installation parameter information. This .ini file can then beused in silent and scripted installations.

• Click the Next button to start the installation process.• At the end of installation, you can launch the Data Services License

Manager automatically by checking Launch License Manager beforeclicking Finish.


Standard Installation of Data Services2 To start the installation

Silent Installation of DataServices

3

Silent installationA silent installation is one that you run from the command line to installBusinessObjects Data Services on any machine in your system. When yourun a silent installation, you can specify all the parameters to be used for theinstall at the same time on the command line, rather than following the installwizard.

The silent install command line includes a series of parameters that provideinformation for installation settings and directory paths. You can also specifyoptions that control the level of prompts during an install.

The silent BusinessObjects Data Services installation is particularly usefulwhen you need to perform multiple installations or you do not want to interruptpeople who are working on machines in your system.

You can also use the silent installation command in your own scripts. Forexample, if your organization uses scripts to install software on machines,you can insert the silent BusinessObjects Data Services installation commandinto your scripts.

The silent installation command consists of the command setup.exe, followedby the install destination, and a number of parameters that provide informationabout the installation.

The following example installs BusinessObjects Data Services with Tomcatand MySQL onto the machine with no user interface and no prompts throughto the end of the installation:setup.exe /qn+ INSTALLDIR="C:\Program Files\BusinessObjects\"ADDLOCAL="Data_Integrator,Tomcat,MySQL"

The example uses the most common parameters. You can choose anynumber of valid parameters, but it is good practice to keep the silentinstallation as simple as possible. If you need to specify many parametersit is best to create an installation .ini file.

Related Topics• Silent/scripted installation .ini file on page 66


Silent Installation of Data Services3 Silent installation

Silent install parametersThe following table lists the most common parameters used in a silentinstallation of BusinessObjects Data Services. To use a parameter, place iton the command line after the setup.exe command and after the path forthe installation files. Or, you may use these parameters in the installation.ini file.

Note: These parameters are case sensitive.

DescriptionInstallation parameter

Specifies that the user is onlyprompted when the installation iscomplete.

/qn+

Specifies that the user is notprompted during the install, or whenthe install is complete.

/qn

Specifies that the user is notprompted during the install, or whenthe install is complete.

/qa /qb

Specifies the machine and directorywhere you want to install the newBusinessObjects Data Servicescomponents.

For example, C:\ProgramFiles\Business Objects\BusinessObjects Data Services

INSTALLDIR

Specifies your base product activa-tion keycode.PIDKEY


3Silent Installation of Data ServicesSilent install parameters


Specifies the user ID for thedatabase.

For trusted authentication this param-eter is not required, useDATABASEAUTHENTICATION=trust-ed.

DATABASEUID

Specifies the MySQL root password.DATABASEPWD_MYSQLROOT

Specifies the account password forthe database you'll be using forBusinessObjects Data Services.

For trusted authentication, this param-eter is not required, useDATABASEAUTHENTICATION=trust-ed instead.

DATABASEPWD

Identify the type of database for therepository.

For Oracle, enter OracleDatabas-eSubsystem.

For DB2, enter DB2DatabaseSubsys-tem.

For Sybase, enter SYBASEDatabas-eSubsystem.

For ODBC SQL, enter ODBCDatabas-eSubsystem.

For Remote MySQL, enter MySql-DatabaseSubsystem.

DATABASEDRIVER


Silent Installation of Data Services3 Silent install parameters


Specifies the ODBC DSN for theData Services repository database.DATABASEDSN

Specifies the port used for MySQLServer. Defaults to port 3306 if it isnot specified.

DATABASEPORT

Specifies the name of the CMSdatabase. This database name de-faults to BOE120 if this parameter isnot specified.

DATABASEDB

Changes the name of the MySQLaudit database, otherwise, the defaultname of BOE120_Audit will be used.

DATABASEDB_AUDIT

Specifies the user ID for thedatabase.

For trusted authentication this param-eter is not required, useDATABASEAUTHENTICATION=trust-ed.

DATABASEUID_AUDIT

Specifies the account password forthe database you'll be using forBusinessObjects Data Services.

For trusted authentication, this param-eter is not required, useDATABASEAUTHENTICATION=trust-ed instead.

DATABSEPWD_AUDIT


3Silent Installation of Data ServicesSilent install parameters


Changes the default directory whereTomcat is installed.

If you don't specify this parameter,Tomcat will be installed the directoryTOMCAT under the default directoryfor BusinessObjects Data Services.

TOMCATDIR

Specifies a different connection port.If this option is not specified, port28080 will be used.

TOMCAT_CONNECTION_PORT

Specifies a different redirect port. Ifthis option is not specified, port28443 will be used.

TOMCAT_REDIRECT_PORT

Specifies a different shutdown port.If this option is not specified, port28005 will be used.

TOMCAT_SHUTDOWN_PORT

Specifies which components will beinstalled. This is the same as runninga Custom install. Each component isspecified, comma separated andgrouped within quotes.

ADDLOCAL

Related Topics• Silent/scripted installation .ini file on page 66• Custom install options for silent installation on page 65


Silent Installation of Data Services3 Silent install parameters

Custom install options for silentinstallation

This is an exhaustive list of all Custom Install Options that are available asfeatures that can be included or excluded during a silent installation.

Silent Install of Data Services Designersetup.exe /qn+ INSTALLDIR='C:\Program Files\BusinessObjects\'ADDLOCAL='Data_Integrator_Designer'

The following table specifies each feature category and its correspondingsilent installation feature names.

Note: Silent installation feature names are case sensitive.

Silent Installation Feature NameFeature Category

Data_Integrator

Data_Integrator_Server

Data_Integrator_AccessServer

Data_Integrator_JobServer

Data_Integrator_Interfaces

Data_Integrator_MetadataIntegrator

Server Components

Data_Integrator_Client

Data_Integrator_Designer

Data_Integrator_Repository

Client Components

Data_Integrator_WebTier

Data_Integrator_ManagementConsole

Web Tier Compo-nents


3Silent Installation of Data ServicesCustom install options for silent installation

Silent Installation Feature NameFeature Category

Data_Integrator_DocumentationDocumentation Com-ponents

MySQLPackaged MySQLDatabase

TomcatPackaged TomcatApplication Server

Note: Dependencies between features are automatically enforced even ifnot explicitly specified in the silent install command line.

Silent/scripted installation .ini fileThere are three additional parameters than can be used with setup.exe onthe command line. These parameters provide a way to pass installationsettings to an .ini file. During a regular full user interface install, installationsettings such as target directories are set as properties in the screens. Theproperties set can be written to the .ini file to replicate the install at a laterdate without having to use the user interface.

DescriptionInstallationparameter

Writes the .ini file to filename. (You may specify the fullpath.)

The simplest way to write to the .ini file is to go throughthe user interface install and select whatever parametersyou want in each dialog box. At the Start Installation screen,cancel out of the install. The .ini file is written with theclosing of the installation setup sequence.

-w filename


Silent Installation of Data Services3 Silent/scripted installation .ini file

DescriptionInstallationparameter

Reads the .ini file and passes the properties to the installeras settings.

Within the .ini file there is a section titled [OTHERS]. If youset QUIET= to /qb, then it will do an install showing theprogress meter. If set to /qa, then it will do a full silent install.

-r filename

Sets the install log to this path and file name and is used inconjuction with the -r switch. If not specified, the log file willbe written to the default %TEMP% folder.

-l filename

Each installation setup screen that has relevant properties writes thatconfiguration information to the file.

Sample installation script fileThis is a sample installation script file that was generated from the commandline: setup.exe -w "FILEPATH". The standard installation program runs, andthe parameters are written to the .ini file by cancelling out of the installationat the "Start Installation" screen.

This file can now be used for future silent installs or scripted installs byincluding the file name and path in the command line: setup.exe -r"FILEPATH".[OTHER]QUIET=/qa[INSTALL]ALLUSERS=""AS_ADMIN_IS_SECURE=""AS_ADMIN_PASSWORD=""AS_ADMIN_PORT="28080"AS_ADMIN_USERNAME="admin"AS_DIR="../Tomcat55"AS_INSTANCE="localhost"AS_SERVER="tomcat55"AS_SERVICE_NAME="BOE120Tomcat"AS_VIRTUAL_HOST=""ApplicationUsers="AllUsers"AspNetVersionRequirementMet="1"BOBJRESETFEATURES=""


3Silent Installation of Data ServicesSample installation script file

CMSAUTHENTICATION=""CMSUSERNAME=""COMPANYNAME="Company Name, Inc."DATABASEDB="EIM120"DATABASEDB_AUDIT="BOE120_AUDIT"DATABASEDRIVER="MySQLDatabaseSubSystem"DATABASEDSN=""DATABASEPWD="bobj"DATABASEPWD_AUDIT="bobj"DATABASEPWD_MYSQLROOT="root"DATABASEUID="bobj"DATABASEUID_AUDIT="bobj"DIASCONFIG="Yes"DIASENABLE="Yes"DIASPATH="C:\Program Files\Business Objects\BusinessObjectsData Services\Log\AccessServer_1"DIASPORT="4000"DIJSCACHEPATH="C:\Program Files\Business Objects\BusinessObjectsData Services\Log\pCache"DIJSCOMMPORT="4001"DIJSCONFIG="Yes"DIJSENABLECOMMPORT="No"DIJSENABLESNMP="No"DIJSENDPORT="32767"DIJSNAME="JobServer_1"DIJSPORT="3500"DIJSSTARTPORT="1025"DILIPW="password"DILIUSER="DOMAIN\username"DILIUSESYSACCOUNT="No"DILRDBNAME=""DILRDBTYPE=""DILROPTYPE=""DILRPASSWORD=""DILRSERVERNAME=""DILRUSERNAME=""DILRWINDOWSAUTHENTICATION=""DIMICERTFILE=""DIMICERTFOLDER=""DIMICFGNAME=""DIMICONFIGURE=""DIMIDBHOST=""DIMIDBPORT=""DIMIFOLDERNAME=""DIMIPASSPHRASEFILE=""DIMIPRIVKEYFILE=""DIMISID=""DIMISSLENABLED=""DIMITRUSTEDCERTFILE=""DIREPOSELECTION="MySQL"DSCFGFOUND="Yes"DotNetFrameworkVersionRequirementMet="1"ENABLESERVERS=""


Silent Installation of Data Services3 Sample installation script file

ENTERPRISE110=""EXPANDCMS="1"FOUNDDOTNET=""HASIIS4=""INSTALLDIR="C:\Program Files\Business Objects\"INSTALLLEVEL="3"INSTALLSWITCH=""INSTALL_DB_TYPE="NoNeed"IS_CA_INSTALLED=""IS_CLIENT_INSTALL=""IS_UPGRADE_UNSUPPORTED=""KeycodeIsValid=""KeycodeIsValid_AFSets=""KeycodeIsValid_DM=""KeycodeIsValid_Prediction=""KeycodeIsValid_RAS=""KeycodeIsValid_SPC=""LUGE=""MYSQLDIR="C:\Program Files\Business Objects\MySql5\"MYSQLPORT="3306"NAMESERVER=""NEWCMSPASSWORD=""NODAS=""NO_INPUT_NEEDED=""PIDKEY="00000-0000000-0000000-0000"PREVIOUS_CA=""PREVIOUS_CE_UPGRADE=""Preselected=""Privileged="1"ProductID="none"ProductName="BusinessObjects Data Services"RAS_RegWizCmdLine=""RESUME=""REUSEDSCONFIG=""RegWizCmdLine=""SKIP_DEPLOYMENT=""SUPPORTED_UPGRADES=""TOMCATDIR="C:\Program Files\Business Objects\Tomcat55\"TOMCAT_CONNECTION_PORT="28080"TOMCAT_REDIRECT_PORT="28443"TOMCAT_SHUTDOWN_PORT="28005"UNSUPPORTED_UPGRADES=""USERNAME="User Name"WCADOTNETINSTALL=""WCAJAVAINSTALL="True"WCATOMCATINSTALL="True"WDEPLOY_LATER=""WEBSERVER_CONFLICT="1"WEBSITE_HOST="LOCAL-HOST"WEBSITE_METABASE_NUMBER=""WEBSITE_PORT="80"_ServiceAccountName="Local System Account"[FEATURES]


3Silent Installation of Data ServicesSample installation script file

REMOVE=""ADDLOCAL="Data_Integrator_AccessServer,Data_Integrator_Server,Data_Integrator_JMSAdapter,Data_Integrator_Interfaces,Data_Integrator_SFDCAdapter,MySQL,Data_Integrator_JobServer,Data_Integrator_MetadataIntegrator,Data_Integrator,Data_Integrator_R3Functions,Data_Integrator_Designer,Data_Integrator_JDEdwards,Data_Integrator_MultiUser,Data_Integrator_OraApps,Data_Integrator_PeopleSoft,Data_Integrator_SAPBW,Data_Integrator_SAPR3Abap,Data_Integrator_SAPR3Bapi,Data_Integrator_SAPR3Idoc,Data_Integrator_Siebel,Data_Integrator_Client,Data_Integrator_Repository,Tomcat,Data_Integrator_WebTier,Data_Integrator_ManagementConsole,Data_Integrator_Documentation"ADDSOURCE=""ADVERTISE=""


Silent Installation of Data Services3 Sample installation script file

After Installing DataServices

4

Starting Data Services servicesautomatically

The Data Services service and packaged Tomcat service start automaticallywhen the computer restarts. The Data Services service then starts JobServers and Access Servers on the restarted computer.

You can change service startup to Manual in the Windows Services window.

Note: The Data Services Address Server service is set to Manual startupby default, but must be started before using the Global Address Cleanse orGlobal Suggestion List transforms. If you do not need Global Address Cleanseor Global Suggestion List functionality, Business Objects recommends thatyou leave the Address Server service as Manual and do not start it.

Logging in to the Management ConsoleAfter an Access Server is running, you can configure it by using the DataServices Management Console.

From the Start menu, select Programs > BusinessObjects XI 3.0 >BusinessObjects Data Services > Data Services Management Console.Log in to Data Services Management Console using the default name (admin)and password (admin).

Related Topics• Management Console Administrator Guide: Logging in• Management Console problems on page 96

Using the Repository ManagerUse the Data Services Repository Manager to check the version, to upgrade,or to create a repository after installation:

1. From the Start > Programs > Business Objects XI 3.0 >BusinessObjects Data Services menu, choose Data ServicesRepository Manager.

2. To check the version of an existing repository, click Get version.


After Installing Data Services4 Starting Data Services services automatically

Related Topics• To create or upgrade repositories on page 73• To create or upgrade repositories in batch mode on page 74

To create or upgrade repositories

1. If you are creating a new repository, ensure that you created a databasefor the new repository to use.

2. In the Data Services Repository Manager window, select the databasetype of your repository.

3. Complete the information for your database type.4. Enter the user name and password that you want to use for your

repository.5. Select one of the following repository types:

DescriptionReposi-torytype

(Default) Stores definitions of Data Services objects in yourlocal repository.

Local

Stores definitions of Data Services objects in a central repos-itory for multiple-user users.

Central

Stores information generated by the Data Profiler for determin-ing the quality of your data.

Profiler

Stores dictionary information for Global Parsing Options usedby Data Cleanse transforms.

GPO

6. If you are creating a new repository, click Create. If you are upgradingan existing repository, click Upgrade.

7. If you want to create or upgrade another repository, repeat steps 1 through6.

8. When you finish creating or upgrading repositories, click Close.


4After Installing Data ServicesUsing the Repository Manager

Note: If you created a profiler repository, you must associate it to a JobServer and connect it to the Management Console Administrator.

Related Topics• Management Console Administrator Guide: Connecting repositories tothe Administrator

• Using the Server Manager on page 76• To configure Job Servers on page 78• Repository database requirements and preparation on page 22

To create or upgrade repositories in batch mode

You can use the executable called RepoManBatch.exe (stored in theLINK_DIR\bin directory) to create or update repositories in batch mode.Specify parameters using a command prompt.C:\Program Files\Business Objects\BusinessObjects Data Services\bin>RepoManBatch.exe

Usage:-U<User> : Repository login user-P<Password> : Repository login password-S<Server> : Repository server name-N<DatabaseType> : Repository database type-Q<Database> : Repository database-g : Repository using Windows Authentication

(Microsoft SQL Server only)-t<local> : Repository type: local, central, pro

filer, GPO-c : Repository create-u : Repository upgrade-v : Repository version-d : Show details-a : Repository security

C:\Program Files\Business Objects\BusinessObjects Data Services\bin>

For example:RepoManBatch -Usa -P -NMicroSoft_SQL_Server -SServer -QJake -c -tcentral -d

orRepoManBatch -UJake -PJake -NOracle -Sdbsvr -v


After Installing Data Services4 Using the Repository Manager

Usage:

DescriptionFlag

Repository login user-U

Repository login password-P

Repository server name:• For Microsoft SQL Server: database server name• For Oracle: database connection name• For DB2: data source• For Sybase ASE: server• For MySQL: ODBC data source name

-S

Repository database type:• Microsoft_SQL_Server• DB2• Oracle• Sybase• MySQL

-N

Repository database name-Q

Repository Type: local, central, profiler, GPO-t

Create repository-c

Upgrade repository-u

Get repository version-v

Show details-d

Central repository security-a


4After Installing Data ServicesUsing the Repository Manager

Using the Server ManagerUse the Data Services Server Manager to create, edit, or delete Job Serversand Access Servers after installation:

1. From the Start menu, choose Programs > Business Objects XI 3.0 >BusinessObjects Data Services > Data Services Server Manager.

The Data Services Server Manager utility window opens. This windowshows the Job Servers and Access Servers currently configured to runon your computer.


After Installing Data Services4 Using the Server Manager

2. Follow the procedures in the next sections to configure Job and Accessservers as needed.

3. In the Data Services Server Manager window, click Restart.

Related Topics• To configure Job Servers on page 78


4After Installing Data ServicesUsing the Server Manager

• To resynchronize Job Servers on page 80• To configure run-time resources for Job Servers on page 81• To configure Access Servers on page 82• Configuring the Metadata Integrator on page 90

To configure Job Servers

1. In the Data Services Server Manager window, click Edit Job ServerConfig.

2. In the Job Server Configuration Editor window, click Add to add a JobServer.

3. In the Job Server Properties window, enter information about the JobServer.

DescriptionProperty

Enter a name that uniquely identifies the Job Server.Job Server name

Enter the TCP/IP port that the Job Server uses to re-ceive commands from the Designer and the AccessServer. If a computer hosts multiple Jobs Servers,each Job Server must have a unique port number.Choose a port number for a server that is not usedby another process on the computer. If you are unsureof which port number to use, use the default portnumber and increment it for each additional JobServer you configure.

Job Server port

Select this check box if the Job Server managesadapters or if this Job Server will be the one to com-municate with an SNMP agent. Each computer thathosts adapters and an SNMP agent must have exactlyone Job Server designated to manage them.

Support Adapter andSNMP communica-tion

Enter the port number that the Job Server uses forcommunicating with adapters or an SNMP agent. Thedefault is 4001.

Communication port

Check this to enables this Job Server to send eventsto the SNMP agent.Enable SNMP



4. Under Associated Repositories, enter the local and profiler repositoriesto associate with this Job Server. Each Job Server must be associatedwith at least one local repository.a. Click Add to associate a new local or profiler repository with this Job

Server.b. Enter the required information for your database type.c. Enter the user name and password that you want to use for your

repository.d. Select the Default repository check box if this is the default repository

for this Job Server. You must specify exactly one default repository.

Note: Do not select the Default repository check box if this is a profilerrepository.

e. Click Apply to save your entries and associate the repository with theJob Server.The associated repository updates with the Job Server's computername and port number.

f. Repeat steps a through e until you are done adding all associatedrepositories.

5. To edit an associated repository:a. Select a repository and click Edit to change the repository's default

setting.b. Under Repository Information, enter the password.c. Select or clear the Default repository check box, indicating whether

this is the default repository for the Job Server.d. Click Apply to save the change.

6. To delete an associated repository:a. Select a repository and click Delete.b. Under Repository Information, enter the password.c. Click Apply to remove this associated repository.

7. When you finish adding all associated repositories, including one default,click OK.

8. From the Job Server Configuration Editor window, complete any othernecessary steps. You can:• Add another Job Server

a. Click Add.b. Repeat steps 3 through 7.



• Change a Job Server's configurationa. Select the Job Server.b. Click Edit.c. Repeat steps 3 through 7.

• Remove a Job Servera. Select the Job Server.b. Click Delete.

Note: If the Job Server has associated repositories, you must firstdelete those and then click OK before you can delete the JobServer.

• Resynchronize your Job Server configuration with a local repository.Resynchronizing registers the Job Server again in all associatedrepositories.

9. When you have configured all the Job Servers you want, click OK.You return to the Data Services Server Manager window.

10. Click Restart to restart the services with the updated configurations.

Related Topics• Designer Guide: SNMP support• To resynchronize Job Servers on page 80• To configure run-time resources for Job Servers on page 81

To resynchronize Job Servers

Situations when you must resynchronize the Job Server and the localrepository include:

• When the Job Server information is not available or not correct in thelocal repository.

• You have uninstalled Data Services and are reinstalling the same DataServices version without creating a new local repository.

• You created a new local repository using the Repository Manager afterinstalling Data Services.

To resynchronize Job Servers:

1. In the Job Server Configuration Editor window, select the name of yourJob Server.



2. Click Resync with Repository.3. In the Job Server Properties window, select an associated local repository.4. Click Resync.5. When asked whether to update this associated repository with this local

machine information, click Yes.6. Under Repository Information, enter the local repository password.7. Click Apply.8. Click OK on the Job Server Properties window.

If you resynchronize your Job Server configuration with a local repository,you must reassociate this repository with the Management Console.

Related Topics• Management Console Administrator Guide: Connecting repositories tothe Administrator

To configure run-time resources for Job Servers

1. Open the Data Services Server Manager and find the "Runtime resourcesconfigured for this computer" section.

2. For the Specify a directory with enough disk space for pageablecache option, you can accept the default directory(LINK_DIR\Log\PCache) or click the ellipses button to browse to a differentdirectory.

Note: For memory-intensive operations such as Group By, Order By,and Detailed profiling, specify a pageable cache directory that:

• Contains enough disk space for your data. To estimate the amount ofspace required for pageable cache, consider factors such as:• Number of concurrently running jobs or data flows.• Amount of pageable cache required for each concurrent data flow.

• Exists on a separate disk or file system from the Data Services systemand Operating system (such as the C: drive on Windows, or the rootfile system on UNIX).

• Limits the disk space that Data Services data flows consume. TheData Services pageable cache uses all available disk space on thefile system that contains the pageable cache directory. So, to limit thedisk space that Data Services data flows consume, create a file system



(or partition on Windows) with a limited size. Use the new file system(partition on Windows) as the pageable cache directory.

Data Services uses this directory:

• For pageable caching, which is the default cache type for dataflows.

• When selecting a file transfer type and Automatic is specified inthe Data_Transfer transform.

3. In the "Peer-to-peer options" area, change the values for Start port andEnd port to restrict the number of ports used by Data Services. Thedefault values for Start port and End port are 1025 and 32767,respectively.

Data Services uses these ports for peer-to-peer communications whensending data between data flows or sub data flows.

Related Topics• To configure Access Servers on page 82• Performance Optimization Guide: Caching data• Reference Guide: Data_Transfer• Performance Optimization Guide: Using grid computing to distribute dataflows execution

To configure Access Servers

When you configure the location for an Access Server installation, DataServices creates space for the Access Server log files.

1. In the Data Services Server Manager window, click Edit Access ServerConfig.

2. In the Access Server Configuration Editor window, click Add.3. In the Access Server Properties window, enter the Access Server

configuration information.



DescriptionField

The location of the log files for this instance ofthe Access Server. Click the ellipses button tobrowse to the Log directory under the directorywhere you installed Data Services.

Do not change this value after the initial configu-ration.

Directory

The port on this computer that the AccessServer uses to listen for incoming messagesfrom clients.

Make sure that this port number is unused andis unique for each Access Server.

Communication Port

You can leave this box blank.Parameters

An option to control the automatic start of theAccess Server when the Data Services Servicestarts.

Enable Access Server

Click OK. You return to the Access Server Configuration Editor window:

4. Optionally, perform further actions:• To change an Access Server's configuration:

In the Access Server Configuration Editor window, highlight the AccessServer, click Edit, and repeat step 3.

• To remove an Access Server:

In the Access Server Configuration Editor window, highlight the AccessServer and click Delete.

5. After you configure your Access Servers, click OK to return to the DataServices Server Manager window.



6. Click Restart to restart the services with the updated configuration.

Verifying that Job and Access servers are running

To verify that Job Servers are running, check in the Windows Task ManagerProcesses tab for:

• al_jobservice.exe (represents the Data Services service)• al_jobserver.exe (one per Job Server)• AL_AccessServer.exe (one per Access Server)

If you do not see all the processes expected, check for error messages inthe Job Server event log in LINK_DIR/log/JobServername/server_eventlog.txt.

• Access Server logs are in AccessServerPathName/error_mm_dd_yyyy.log

Using the License ManagerLicense Manager is a Business Objects application that lets you manageyour product activation keycodes—the alphanumeric codes that are referredto each time that you run certain Business Objects products. By using theLicense Manager application, you can view, add, and remove productactivation keycodes for Business Objects products (such as BusinessObjectsData Services) that require them.

Note: License Manager accesses keycodes on the local system only; youcannot access the keycodes from a remote system. When updating keycodes,make the changes on all Data Services computers by launching LicenseManager on each computer, including Designer and Job Server computers.

To start License Manager

You can run License Manager after the Data Services installation hascompleted. You can either locate where it’s installed or access it through theStart menu.

• From the Start menu, choose Programs > BusinessObjects XI 3.0 >BusinessObjects Data Services > Data Services License Manager.


After Installing Data Services4 Using the License Manager

To view product activation keycodes

1. Start License Manager.When you click the shortcut on the Start menu, the License Managerwindow displays your key code(s) sorted alphabetically.

2. Select a licensed product or feature in the Registered Keycodes tree toview detailed information:• Product or feature keycode• Whether the keycode is a trial version• Whether the keycode is expired• Number of days remaining until the keycode expires

Related Topics• To start License Manager on page 84

To add a product activation keycode

1. Start License Manager.2. In the Product Activation Keycodes text box, type the keycode(s) that

you want to add (each keycode must be on a separate line) and clickAdd.

3. When you have added your keycode(s), close the License Manager.4. To make sure the new keycode(s) take effect, restart your application.


To remove a product activation keycode

1. Start License Manager.2. In the Registered Keycodes tree, select the keycode(s) that you want

to remove and click Remove.3. When you have removed your keycode(s), close the License Manager.4. Restart your application.


4After Installing Data ServicesUsing the License Manager


To use License Manager from the command line

License Manager includes a command-line mode that you can use if youdon't want to use the graphical interface, or need to script License Manageroperations.

SyntaxLicenseManager [-v | -a keycode | -r keycode [registry_location]]

DescriptionParameter

Displays the product activation keycodes stored in theregistry in a format similar to the License Managergraphical interface. For example:------ Registered Keycodes ------EIM TitanSuite 12.0Data Services XI 3.0 PremiumKeycode: 00000-0000000-0000000-0000Trial Option: YesExpired: NoDays Remaining: 54

-v or --view


After Installing Data Services4 Using the License Manager


Adds the specified license keycode to the registry,and displays the keycodes stored in the registry in aformat similar to the License Manager graphical inter-face. Returns status messages for the following con-ditions:

• An internal error occurred.• Successfully added the keycode.• Successfully added the keycode and replaced a

trial version.• Keycode not added because it is invalid.• Keycode not added because it is a duplicate.

-a or --add keycode

Removes the specified product activation keycodefrom the registry, and displays the keycodes storedin the registry in a format similar to the License Man-ager graphical interface. If registry_location is speci-fied, the removal is restricted to that registry node.Returns status messages for the following conditions:

• An internal error occurred.• Removed one keycode from the registry.• Removed multiple keycodes from the registry.• Keycode not removed because it is invalid.• Keycode not removed because it was not found.

-r or --remove keycode [registry_location]

Installing and configuring the MetadataIntegrator

The Metadata Integrator reads through Crystal Reports, Business View,Universe, Desktop Intelligence document, and Web Intelligence documentdefinitions on a Central Management Server (CMS) to find the tables andcolumns used by the reports, views, and documents. The Metadata Integrator


4After Installing Data ServicesInstalling and configuring the Metadata Integrator

stores the information in Data Services repository for impact analysis andlineage analysis. You can install the Metadata Integrator on multiple CMSsystems and store the report information in one Data Services repository.

Related Topics• Installing Metadata Integrator on page 88• Metadata Integrator installation tips and troubleshooting on page 89• Configuring the Metadata Integrator on page 90

Installing Metadata Integrator

You can install the Metadata Integrator on multiple CMS systems and storethe report information in one Data Services repository.

Metadata Integrator has the following prerequisites:

• Runs on Windows only

• Must have the BusinessObjects Enterprise client installed

Installing on the same computer as Data Services

Metadata Integrator can be installed with the Data Services ServerComponents. However, if no Central Management Server (CMS) exists onthe same computer as Data Services, the Metadata Integrator configurationscreens do not appear during installation.

You have the option to configure the Metadata Integrator during Data Servicesinstallation, or you can defer configuration.

Related Topics• To configure the Metadata Integrator on page 91

Installing on a different computer than Data Services

In many cases, your Central Management Server resides on a separatecomputer than Data Services.

Perform a standard installation of Data Services, but choose only MetadataIntegrator in the feature selection screen.


After Installing Data Services4 Installing and configuring the Metadata Integrator

Related Topics• Standard installation overview on page 31• To configure the Metadata Integrator on page 91

Metadata Integrator installation tips andtroubleshooting

Below are several Metadata Integrator installation tips and problems thatyou can troubleshoot:

Configuration fails during installation

If the CMS is unavailable during the Metadata Integrator installation, or if theCMS version has changed since installation, the Metadata Integrator will notrun successfully. Is these cases, the Metadata Integrator will report an errorsuch as the following when launched:java.lang.NoClassDefFoundError:com/crystaldecisions/sdk/exception/SDKExceptionat com.acta.crystalrepo.config.crConfigFrame.setupWizardPages(crConfigFrame.java:84)at com.acta.crystalrepo.config.crConfigFrame.run(crConfigFrame.java:73)at com.acta.crystalrepo.config.crConfigLaunch.main(crConfigLaunch.java:68)Exception in thread "main"

To reconfigure the Metadata Integrator environment

1. In LINK_DIR/ext/cmsCollector, run cmsSetEnv.cmd to reset allcommand files to point to the installed version of CMS.

2. Run cmsConfig.cmd to update any configured Metadata Integrators topoint to the installed version of CMS.

Changing Data Services repository connection information

• To change the Data Services repository connection information suppliedduring configuration, run the configuration utility:LINK_DIR/ext/cmsCollector/cmsConfig.cmd



Metadata Collector fails to start with java version error

If the Metadata collector indicates the run has failed, click the run instanceto view the error log. If the error indicates the java run-time environmentcannot be found or is the wrong version, you must define the JAVA_HOMEenvironment variable.

To define the JAVA_HOME environment variable, add the environmentvariable and reboot your machine for it to take effect. Java 1.3.1 or higheris required. JAVA_HOME must be set to the java run-time root directory. Forexample:JAVA_HOME=C:\Program Files\Java\j2re1.4.2_03

Metadata Collector fails to start

If the Metadata collector indicates the run has failed, click the run instanceto view the error log. The error indicates you do not have the permission torun the program.

Press the Process tab and select Logon to determine the user name andpassword used to run the collector. To check the permissions, press theRights tab to see what permissions are set. If you do not have permissionto run programs, check with your Business Objects administrator to get thecorrect permission.

Metadata Integrator runs but report information is missing

From the Central Management Console, click the run instance for theMetadata Integrator even though it says the run was successful. The collectorwill only be in a failed state if the CMS is unable to start the program. Thereis no mechanism to get run-time errors listed as a failed run. The work aroundis to look at successful runs to see if any errors are reported.

Configuring the Metadata Integrator

Invoke the Metadata Integration Configuration window with one of thefollowing actions:



• During Data Services installation on the computer where theBusinessObjects Enterprise CMS resides, click Configure on theMetadata Integrator Manager window.

• During installation for the Metadata Integrator when the CMS is installedon a different computer than Data Services, click Configure on theMetadata Integrator Manager window.

• If you deferred the configuration or you want to modify the configuration,use the Start > Programs > Business Objects XI 3.0 >BusinessObjects Data Services > Data Services Metadata Integratoroption. This Start menu option exists when you install either Data Servicesor the Data Services Metadata Integrator.

Related Topics• Installing on a different computer than Data Services on page 88

To configure the Metadata Integrator

1. When the Metadata Integrator Configuration window displays, chooseone of the following options:a. To add a new Metadata Integrator, select the Add Metadata Integrator

option and click Next.

Configure multiple Metadata Integrators when you have multiple CMSservers. For example, one CMS server might manage your CrystalReports, and a different CMS server manages your Business ObjectsDocuments (Desktop Intelligence or Web Intelligence).

b. To change an existing Metadata Integrator, select the Edit MetadataIntegrator option, select the name of the Metadata Integrator in thedrop-down list, and click Next.

c. To delete a Metadata Integrator, select the name of the MetadataIntegrator in the drop-down list, select the Delete option, and clickNext.

2. On the Business Objects Enterprise window, enter the following CMSconnection information. Consult your Business Objects administrator ifyou need assistance with these values.



DescriptionOption

Name for this Metadata Integrator configura-tion. The default name is "Metadata Integra-tor" followed by a sequential number. For ex-ample:Metadata Integrator 2

Configuration Name

Host name of the Central ManagementServer (CMS) server.CMS Server Name

The user name to connect to the CMS serverto register and execute the Metadata Integra-tor. If you want a different user to execute theMetadata Integrator, use the Central Manage-ment Console to change the rights for theuser. See the BusinessObjects EnterpriseAdministrator's Guide for details.

CMS User Name

The password to connect to the CMS serverto register and execute the Metadata Integra-tor.

CMS Password

The CMS authentication mode. See theBusiness Objects Enterprise Administrator'sGuide for available modes.

CMS AuthenticationMode

The folder in which the CMS system adds theMetadata Integrator as a program object. Thisfolder is only visible in the Business ObjectsCentral Management Console. The defaultvalue is Data Services (the wizard createsthis folder if it does not exist).

CMS Folder Name



3. Click Next.4. On the "Metadata Repository" window, enter the following information to

connect to the Data Services repository. Consult your databaseadministrator if you need assistance with these values.

DescriptionOption

The database type of the Data Servicesrepository. The available database types are:

• DB2• Microsoft SQL Server• Oracle• Sybase ASE• MySQL

Database type

Host name on which the Data Servicesrepository resides.Computer Name

Port number that the Central ManagementServer (CMS) uses to connect to the DataServices repository.

Database Port

This field requires additional informationbased on the Database type you select.

Service Name/SID

Database name

Datasource

Database Name

Connection String

Database Port and Server

The login name to connect to the Data Ser-vices repository.User name



DescriptionOption

The login password to connect to therepository.Password

5. (Optional) Click Test to check the connection to the metadata repository.6. Click Next.

The status window for Metadata Integrator Configuration displays.

7. Click Finish.

Connecting the Data ProfilerThe Data Profiler installs automatically when you install Data Services. Touse the Data Profiler, perform the following steps:

1. Define a profiler repository in which the Data Profiler will store thegenerated profile data.

2. Associate the profiler repository with a Job Server on which the profilertasks will run.

3. Connect the profiler repository to the Data Services Administrator whichwill manage the profile data and profiler tasks.

4. Connect the profiler server to the Designer from which you submit profilertasks and view the generated profile data.

5. If you plan to use Detailed profiling or Relationship profiling, ensure thatyou specify a pageable cache directory that contains enough disk spacefor your data and that you place on a separate disk or file system fromthe Data Services system.

Related Topics• To create or upgrade repositories on page 73• To configure Job Servers on page 78• To configure run-time resources for Job Servers on page 81• Management Console Administrator Guide: Connecting repositories tothe Administrator


After Installing Data Services4 Connecting the Data Profiler

• Designer Guide: Connecting to the profiler server

Troubleshooting installation problemsErrors that prevent installation progress (for example, an incorrect servername, user name, or password) result in an immediate error messagedescribing the problem.

For some common issues, such as the service scheduler failing to launchData Services, reboot the computer after installation has finished.

Related Topics• Repository problems on page 95• Management Console problems on page 96• Metadata Integrator installation tips and troubleshooting on page 89

Repository problems

Common repository-related installation errors include:

• The DBMS connection was lost while building the repository tables. If thishappens, recreate the repository with the Repository Manager.

• There is not enough space available in the database for the repositorytables. If this happens, use your DBMS administration tools to allocatemore space for the repository and run the Repository Manager.

If you experience problems when upgrading or creating a repository, youcan select the Show Details check box before you click Update or Createagain. This option allows you to view the SQL code that Data Services usesto perform these operations. The Show Details option can help you diagnoseproblems.

Related Topics• Using the Repository Manager on page 72


4After Installing Data ServicesTroubleshooting installation problems

Management Console problems

Common Management Console and web application-related installationproblems include:

• Login page not found when choosing Programs > BusinessObjects XI3.0 > BusinessObjects Data Services > Data Services ManagementConsole from the Start menu.

This problem can occur when the web application service is not runningor needs to be restarted. For the packaged Tomcat web application server,use the Services tool in the Administrative Tools section of the WindowsControl Panel. For other web application servers, refer to your productdocumentation.

• Web application deployment fails because web application serverinformation was incorrectly entered during the installation process.

The Data Services installation setup does not verify the specified webapplication server information. If there is an error in the information, theweb applications can not be deployed during installation. You can manuallydeploy the web applications after installation. The required WAR files(DataServices.war, webservice.war, and doc.war) are installed to thedeployment/workdir/webserver/application/ folder, wherewebserveris the type of web application server. The deployment folder can be foundon the same level as LINK_DIR.

For instructions on how to manually deploy WAR files, refer to your webapplication server documentation.

• The Management Console cannot be launched on WebSphere.

If your WebSphere installation uses a port other than 9080 for theapplication port, you may need to modify the link to the ManagementConsole. In LINK_DIR/ext/DataServices.html, replace 9080 in thefollowing line with your WebSphere application port:<META HTTP-EQUIV=Refresh CONTENT= "0; URL=http://hostname:9080/DataServices/">


After Installing Data Services4 Troubleshooting installation problems

Upgrading Data Services

5

To upgrade from an existing Data Integrator or Data Services installation,install the new Data Services components and then upgrade your repositories.To upgrade from an existing Data Quality XI installation, see theBusinessObjects Data Services Migration Considerations.

Data Services component upgradesIn addition to upgrading repositories, you must upgrade all Data Servicescomponents to the same version.

Business Objects recommends that after you back up existing repositories(using your database's backup utility) and read the release notes, you upgradecomponents in the following order:

1. Data Services Designer2. Data Services repository3. Data Services Job Server4. Data Services Access Server5. Data Services Message Client libraries

Note: If you are using the SAP ERP or R/3 ABAP interface, re-install theData Services functions for SAP ERP or R/3.

Related Topics• Supplement for SAP: Installing Data Services functions on SAP R/3

Repository upgrades

Minor releases do not require a repository upgrade. For example, if 11.7 isa major release and 11.7.3 is a minor release, then when upgrading from11.7 to 11.7.3, it would not be necessary to upgrade your repository. However,product features introduced in the latest product version might not be availablewithout the repository upgrade. To see whether you need to upgrade yourrepository for a particular release, see the Release Notes for that release.

Using database backup utilities, always make a copy of your existingrepository before upgrading. Note that you will upgrade using the originalrepository (not your backup copy).

Several repository upgrade paths are available.


Upgrading Data Services5 Data Services component upgrades

ProcedureTo upgrade from

Install this release using one of thefollowing methods:• Upgrade your repository during

the installation process

• Upgrade your repository after in-stalling the Client Components byrunning the Repository Managerutility and choosing the Upgradeoption.

Data Integrator Version 11.0.x, 11.5.x,11.6.x, 11.7.x

Note: If you are using an end-of-life version of Data Integrator, first upgradeto a supported version before upgrading to Data Services. For example, ifyou have Data Integrator 6.5, first upgrade to Data Integrator 11.7 and thenupgrade to Data Services.

Related Topics• Upgrading repositories on page 102

Upgrading your Data Services systemWhen moving to a new product version, upgrade your test or developmentenvironment before upgrading your production environment.

To install a new product version on a computer hosting an existing version,run the installation program without uninstalling the existing version.Uninstalling the existing version can cause a potential loss of repositoryinformation if you are using the packaged MySQL database server, whichis uninstalled with Data Services.

Note: The procedure in the following section directs you to follow instructionsin this guide that explain how to use the Data Services installation program.

Business Objects recommends that while upgrading Data Services you donot use the installation program to reconfigure Job or Access Servers orupgrade the repository. Instead, after updating components with the


5Upgrading Data ServicesUpgrading your Data Services system

installation program, use the Server Manager and Repository Manager toreconfigure Job and Access Servers and upgrade the repository.

Related Topics• Beginning your installation on page 36• Using configurations from a previous version on page 100

Using configurations from a previous version

If you want to use custom configurations from a previous version of theproduct:

1. Move the DSConfig.txt file, from the bin subdirectory, into a newlycreated "dummy" installation directory structure before installing the newversion.

Example "dummy" directory structure:

C:\Program Files\Business Objects\BusinessObjects DataServices\bin\DSConfig.txt

During the installation process, Data Services will overwrite the "dummy"directory structure with the new installation structure, merging customsettings (such as repository and Access Server connections added to theAdministrator) from your old DSConfig.txt file into the new DSConfig.txtfile.

2. Before installing the new version, manually move the followingsubdirectories out of your installation directory.• Conf - Contains Administrator settings• Log - Contains old logs

3. If your current installation includes support for real-time message handling,then when you configured an Access Server (using the Data ServicesServer Manager) you specified a location for each Access Serverconfiguration directory. If those directories are in the Data Servicesinstallation directory make a copy of each Access Server configurationdirectory.Save your current copy until after you test the upgrade and confirm thatyour new system is working as expected. When you merge the oldDSConfig.txt file with the new one, Data Services should find the AccessServer configuration directories. If not, use the Server Manager to pointto the backup Access Server directories.


Upgrading Data Services5 Upgrading your Data Services system

4. Uninstall the existing product.5. Install the new product, then move the contents of the old Conf and Log

subdirectories into the new subdirectories.

Related Topics• Beginning your installation on page 36

Before installing a new version

1. Review the Release Notes for the version of Data Services you will beinstalling.

2. Review the Data Services Migration Considerations to identify anybehavior changes from previous versions.

3. Open your Windows Services panel and stop all Data Integrator or DataServices services (Data Services Service and the Data Services AddressServer).You can use the Task Manager to verify that no Data Integrator or DataServices-related processes (processes beginning with al_) are running.

4. Proceed to install the new version.

Related Topics• To install a new version of Data Services on page 101

To install a new version of Data Services

1. Use the Data Services installation program to install the new Data Servicesversion.

2. Restart the computer if prompted by the installation program.3. Use the Repository Manager to create or upgrade repositories, if needed.

From the Start menu, select Programs > Business Objects XI 3.0 >BusinessObjects Data Services > Data Services Repository Manager.

4. Use the Server Manager to make changes to your Job and AccessServers.From the Start menu, select Programs > Business Objects XI 3.0 >Business Objects Data Services > Data Services Server Manager.

5. Verify that Data Services processes are running.


5Upgrading Data ServicesUpgrading your Data Services system

In the Windows Task Manager, click the Processes tab, and look for:

• al_jobserver.exe

• al_jobservice.exe

• AL_AccessServer.exe

6. Install the new version of the Message Client libraries on any computerswhere they are used.If you are upgrading your Message Client library, you must stop your webapplication, install the Message Client library files, then restart your webapplication computer.

Related Topics• Beginning your installation on page 36• Upgrading repositories on page 102

Upgrading repositoriesAfter installing a new version of Data Services, you can create newrepositories or upgrade existing repositories. To associate an existingrepository with your new installation of Data Services, you must upgrade thatrepository.

Before upgrading repositories with the Repository Manager:

• Back up each repository that you intend to upgrade by using an externaldatabase backup utility. For more information, see your databasedocumentation.

• Install the new version of Data Services Client Components.

To upgrade a repository

1. From the Start menu on the computer where you installed the Designer,select Programs > Business Objects XI 3.0 > BusinessObjects DataServices > Data Services Repository Manager.

2. Enter the repository connection information for your original repository inthe Repository Manager window.

Note: Do not attempt to upgrade the backup copy of your repository oryou will experience upgrade errors.


Upgrading Data Services5 Upgrading repositories

3. Click Get Version.The Repository Manager displays the version number recorded in therepository.

4. Click Upgrade.The Repository Manager converts the pre-existing repository to the formatrequired by the new version of Data Services and adds metadata for newand changed objects.

5. Repeat steps 2 through 4 for each repository you want to upgrade.

Note: Corresponding local and central repositories must have the sameData Services version.

6. Click Close.

Note: If you need to create or upgrade multiple repositories, you can usethe RepoManBatch.exe utility.

Related Topics• Using the Repository Manager on page 72• To create or upgrade repositories in batch mode on page 74

After upgrading Data ServicesRun tests of your production jobs to ensure that your existing designs continueto run as expected in the new version of Data Services. When you areconfident that the new version of Data Services performs as well as or betterthan the previous version, consider upgrading your production environment.

Unsuccessful upgrade

Errors that prevent installation progress (for example, an incorrect servername, user name, or password) yield immediate error messages.

Successful upgrade

A "successful completion" message verifies successful Data Servicesinstallation.

The LINK_DIR system variable is defined during the Data Services installation.Its value is set to the location of the directory in which you installed DataServices.


5Upgrading Data ServicesAfter upgrading Data Services

Related Topics• Troubleshooting installation problems on page 95


Upgrading Data Services5 After upgrading Data Services

Citrix Support

6

You can set up Data Services to run under Citrix Presentation Server.Presentation Server provides an access infrastructure for enterpriseapplications.

Presentation Server supports many methods of running applications. Thissection provides information about how to install one copy of a Data Servicescomponent, run it as a Presentation Server-published application or publisheddesktop on a server, and set client user permissions for it.

Definitions

The following definitions introduce basic Citrix concepts. To learn more aboutCitrix Presentation Server, see Citrix Presentation Server documentation.

DescriptionConcept

A Citrix-defined protocol/connection to a server. The ICAclient connection allows Presentation Server to run any ap-plication on its server and manage how each client accessesthe user interface of the application.

ICA Client

The Presentation Server component installed on a client. Itmanages ICA client connections and published applicationsfor a given user.

Program Neigh-borhood

Application software (for example, Data Services Designer)installed on a Presentation Server server and published tousers. An administrator can choose which users can run andview the application.

Published Appli-cation

When a user starts their Program Neighborhood software,they see all the published applications to which they haveaccess. This is an application set and can include multipleapplications published on multiple Presentation Serverservers.

Application Set

Installing BusinessObjectsData Serviceson a Citrix Server

Data Services user interfaces are certified to run on Citrix Presentation Serveras an application set. The set consists of:


Citrix Support6 Installing BusinessObjects Data Services on a Citrix Server

• Designer (includes the Metadata Reporting tool)• Management Console• License Manager• Repository Manager• Server Manager

Initial installation

The installation process for Data Services on a Presentation Server serveris slightly different from a typical Data Services installation. The PresentationServer server runs Microsoft terminal services in application mode. Therefore,you must install Data Services using the Add/Remove programs service inthe Windows control panel.

To install Data Services, follow the prompts of the Add/Remove programwizard and use the file browser of the wizard to run setup.exe from theinstall CD (or network directory). Business Objects recommends that youinstall the Designer and the Job Server on separate computers.

After you install Job Servers and Access Servers, you must provideconnection settings to users because their remote setups will look for theservers locally by default. Similarly, manage sources, targets, and repositoriesfrom the Presentation Server server in the usual fashion. However, individualclients must use database connection names defined on the server (not thelocal client). The Designer defaults to looking for configuration informationlocally. For example, to connect to an Oracle repository, define the Oracleconnection name on the Presentation Server server and provide theconnection information to your users.

Note: Because Citrix Presentation Server is running on a server, be awarethat the first time you install Data Services, you must reboot the server.

Related Topics• Limitations on page 117


6Citrix SupportInstalling BusinessObjects Data Services on a Citrix Server

Running Data Services components inmulti-user mode

While Presentation Server allows you to publish Data Services interfacecomponents to one user or multiple users at the same time, Business Objectsrecommends running all but the Designer and Management Console in serialmode.

Serial access to the License, Server, and RepositoryManagers

As a work flow issue, it is safest to allow only one user at a time to accessthe License Manager, Repository Manager, and Server Manager. In mostcases, this restriction will not be an issue, because users typically do notaccess these components often. To set these components for serial access,use Presentation Server to configure their application limit to one instanceper server.

Parallel access to the Management Console andDesigner

Use Presentation Server to configure the Management Console and theDesigner to run any number of instances in parallel per server.

• When you configure the Management Console, simply publish it ascontent.

• However, when you configure the Designer, you also must limit theapplication to one instance per user and ensure that your configurationpreserves user settings. Business Objects recommends that you use aDOS shell script to do this.

Related Topics• Publishing Data Services on page 114


Citrix Support6 Running Data Services components in multi-user mode

Using a shell script to access the Designer

When you install the Designer, the environment variable LINK_DIR is set topoint to the install directory. This variable allows the Designer to locatesettings and persistent environment information.

There is only one LINK_DIR variable per Designer installation. This meansthat when multiple users run a single Designer installation (in serial orparallel), all instances of the Designer will read the same path from theLINK_DIR variable. The result is that the Designer’s users will change eachother’s settings.

To solve this problem for Citrix, use the following script to create theLINK_DIR variable for each user. The script provides each user with theirown copy of Designer resources and points the LINK_DIR variable to thisresource copy when users log in to the Designer.

The following diagram shows how two Designer processes can run on thesame computer.


6Citrix SupportRunning Data Services components in multi-user mode

Example: Sample batch file #1CopyRunDesigner.bat

Instead of running the Designer from a user’s client machine, run theCopyRunDesigner.bat file. Note that:

• The script is a DOS shell script. You can create a similar script in anyoperating system language.

• This is an example script. Substitute a literal root directory name forD:\USERS and variables for %TEMP% (root directory for each user’sresources), %USERNAME% (login for each user), and %PATH% (userenvironment path that points to the Designer installation).



• The CreateRunDesigner batch file copies the minimum set of files forDesigner to run. It also:• Creates a temporary resource directory for the user• Copies Designer resources from a Designer installation (either on the

Presentation Server server or the network to this directory)• Sets up the user environment path to point to the Designer installation• Sets up LINK_DIR in the user’s environment to point to the resource

directory• Optionally copies a user-specific DSConfig.txt to the user's resource

directory• Starts the Designer process

• When the user ends the Designer session, this batch file:• Optionally caches the user-specific DSConfig.txt• Removes the copied resources from the server.

@echo offrem Copies Designer resources from the install directory andputs the directory anywhere you specifySET TEMP=D:\USERS

rem Determines if the temporary directory exists. If it exists,it is deletedIF EXIST %TEMP%\%USERNAME%\DI RD /S /Q %TEMP%\%USERNAME%\DI

rem Creates a temporary directory for the user, which is thesubdirectory temp/username used by Data Integrator to cacheuser settingsMD%TEMP%\%USERNAME%\DIXCOPY "%LINK_DIR%"\Admin %TEMP%\%USERNAME%\DI\ADMIN /S /Q/IXCOPY "%LINK_DIR%"\bin\fcache %TEMP%\%USERNAME%\DI\fcache/T /E /I /QXCOPY "%LINK_DIR%"\bin\Locales %TEMP%\%USERNAME%\DI\bin\Locales /S /Q /IXCOPY "%LINK_DIR%"\bin\visuals %TEMP%\%USERNAME%\DI\bin\visuals /S /Q /ICOPY "%LINK_DIR%"\bin\*.txt %TEMP%\%USERNAME%\DI\binCOPY "%LINK_DIR%"\bin\*.bin %TEMP%\%USERNAME%\DI\binCOPY "%LINK_DIR%"\bin\*.jar %TEMP%\%USERNAME%\DI\binCOPY "%LINK_DIR%"\bin\*.bat %TEMP%\%USERNAME%\DI\binCOPY "%LINK_DIR%"\bin\*.xem %TEMP%\%USERNAME%\DI\binCOPY "%LINK_DIR%"\bin\*.xsl %TEMP%\%USERNAME%\DI\bin

rem Uses the following two lines to support the metadata exchange optionCOPY "%LINK_DIR%"\bin\xalantransform.exe %TEMP%\%USER



NAME%\DI\binCOPY "%LINK_DIR%"\bin\xalantransformer.dll %TEMP%\%USERNAME%\DI\binXCOPY "%LINK_DIR%"\log\Errorlog.* %TEMP%\%USERNAME%\DI\Log/I /QCOPY "%LINK_DIR%"\log\Tracelog.* %TEMP%\%USERNAME%\DI\LogXCOPY "%LINK_DIR%"\log\BulkLoader %TEMP%\%USERNAME%\DI\log\BulkLoader /T /E /I /QXCOPY "%LINK_DIR%"\log\Metaexchange %TEMP%\%USERNAME%\DI\log\Metaexchange /S /Q /IXCOPY "%LINK_DIR%"\Lib %TEMP%\%USERNAME%\DI\Lib /S /Q /IXCOPY "%LINK_DIR%"\Doc\Books %TEMP%\%USERNAME%\DI\Doc\Books/S /Q /I

rem Sets the environment to the Designer install directorySET PATH=%PATH%;"%LINK_DIR%"\BIN

rem Sets the user environment for this loginSET LINK_DIR=%TEMP%\%USERNAME%\DI

rem Optional, restores user settingsIF EXIST %TEMP%\%USERNAME%\DSConfig.txt COPY %TEMP%\%USERNAME%\DSConfig.txt %TEMP%\%USERNAME%\DI\BIN\DSConfig.txt

rem Executes BusinessObjects Data Services DesignerAL_Designer.exe

rem Optional, backs up user settingsCOPY %TEMP%\%USERNAME%\DI\BIN\DSConfig.txt %TEMP%\%USERNAME%\DSConfig.txt

rem Removes the temporary user directoryRD /S /Q %TEMP%\%USERNAME%\DI

Example: Sample batch files #2CopyResources.bat

As an alternate option, you can also break the script into two smaller files.

The first file creates a resource directory for the user.@echo offrem Copies Designer resources from the install directory andputs the directory anywhere you specifySET TEMP=D:\USERS

rem Creates a temporary directory for the user, which is thesubdirectory temp/username used by Data Integrator to cacheuser settingsMD %TEMP%\%USERNAME%\DIXCOPY "%LINK_DIR%"\Admin %TEMP%\%USERNAME%\DI\ADMIN /S /Q



/IXCOPY "%LINK_DIR%"\bin\Fcache %TEMP%\%USERNAME%\DI\fcache/T /E /I /QXCOPY "%LINK_DIR%"\bin\Locales %TEMP%\%USERNAME%\DI\bin\Locales /S /Q /IXCOPY "%LINK_DIR%"\bin\Visuals %TEMP%\%USERNAME%\DI\bin\visuals /S /Q /ICOPY "%LINK_DIR%"\bin\*.txt %TEMP%\%USERNAME%\DI\binCOPY "%LINK_DIR%"\bin\*.bin %TEMP%\%USERNAME%\DI\binCOPY "%LINK_DIR%"\bin\*.jar %TEMP%\%USERNAME%\DI\binCOPY "%LINK_DIR%"\bin\*.bat %TEMP%\%USERNAME%\DI\binCOPY "%LINK_DIR%"\bin\*.xem %TEMP%\%USERNAME%\DI\binCOPY "%LINK_DIR%"\bin\*.xsl %TEMP%\%USERNAME%\DI\bin

rem Uses the following two lines to support metadata exchange

COPY "%LINK_DIR%"\bin\xalantransform.exe %TEMP%\%USERNAME%\DI\binCOPY "%LINK_DIR%"\bin\xalantransformer.dll %TEMP%\%USERNAME%\DI\binXCOPY "%LINK_DIR%"\log\Errorlog.* %TEMP%\%USERNAME%\DI\Log/I /QCOPY "%LINK_DIR%"\log\Tracelog.* %TEMP%\%USERNAME%\DI\LogXCOPY "%LINK_DIR%"\log\BulkLoader %TEMP%\%USERNAME%\DI\log\BulkLoader /T /E /I /QXCOPY "%LINK_DIR%"\log\Metaexchange %TEMP%\%USERNAME%\DI\log\Metaexchange /S /Q /IXCOPY "%LINK_DIR%"\Lib %TEMP%\%USERNAME%\DI\Lib /S /Q /IXCOPY "%LINK_DIR%"\Doc\Books %TEMP%\%USERNAME%\DI\Doc\Books/S /Q /IRunDesigner.bat

The second file runs the Designer if resources are already copied.@echo offrem Puts directory anywhere you specifySET TEMP=D:\USERS

rem Determines if the temporary directory exists. If it doesnot exist, uses the previous script CopyResourcesIF NOT EXIST %TEMP%\%USERNAME%\DI CALL COPYRESOURCES

rem Sets the environment to the Designer install directorySET PATH=%PATH%;”%LINK_DIR%”\BIN

rem Sets the user environment for this loginSET LINK_DIR=%TEMP%\%USERNAME%\DI

rem Executes BusinessObjects Data Services DesignerAL_Designer.exe



This method eliminates the need to copy resources each time the userstarts the Designer. However, you have to store multiple resource cacheson the server for each user. Also, in this scenario the user’s computer doesnot have to cache user settings (DSConfing.txt) since they remain on theserver between runs.

Directory structure

Use the following directory structure for the all Designer batch files:User (the literal value you use in the script)

Admin/*Bin

FcacheLocales/*Visuals/**.txt*.bin (localization only)*.jar*.bat*.xem*.xsl

LogErrorlog.*Tracelog.*BulkLoaderMetaexhange/*

Lib/* (web services, adapter, admin jar files)Doc

Books/*

This directory structure includes some options that may not be necessaryfor your installation. However, Business Objects recommends that you includethese folders and their contents because they are used with metadataexchange and SNMP.

Publishing Data ServicesAfter you install Data Services, you can set up its user interface componentsas Published Applications to make them available to clients. The PresentationServer Management console includes a wizard to help you do this. Run itonce for each Data Services component (Designer, Management Console,Repository Manager, Server Manager, and License Manager). You mustpublish each component separately.


Citrix Support6 Publishing Data Services

To publish a Data Services component

1. Start the Citrix Presentation Server Management console.2. Select Applications from the menu tree and choose Publish Application

from the menu.3. On the "Specify What to Publish" page, enter the following values for

each Data Services component:

Content addressWorking di-rectory

Command linePublishas

Component

C:CopyRunDesigner.bat

Applica-tion

Designer

"$LINK_DIR"\binRepoMan.exeApplica-tion

Repository Manager

"$LINK_DIR"\binAWServerConfig.exe

Applica-tion

Server Manager

"$LINK_DIR"\binLicenseManager.exe

Applica-tion

License Manager (op-tional)

"$LINK_DIR"/ext/DataServices.html

ContentManagement Console

Note:a. Publish the Designer .bat file(s) instead of al_designer.exe.b. To allow for spaces in the install path name, use quotes around any

variable that includes a directory name.c. After using Presentation Server to configure the Management Console

as content, share the ext directory with all Management Consoleusers.

The Publish Application Wizard allows you to enter a file name for thestart icon used by applications published as content. For the ManagementConsole, enter the path to Admin_small.ico if you want users to haveaccess to the icon. Note that Designer components run as a shortcut onthe client desktop.

4. The next page in the wizard allows you to define Program Neighborhoodsettings. Complete the configuration:


6Citrix SupportPublishing Data Services

DescriptionSetting

Choose 256 colors at minimum. Lower resolution set-tings may work but will not allow users to easily distin-guish icons and object bitmaps. Program Neighborhoodprovides an option to maximize any application atstartup. Business Objects recommends that you do notmaximize the Designer at startup because older ver-sions of the Designer might fail.

Application Appear-ance

Business Objects recommends that you use only thebasic security level option in Program Neighborhood.Higher levels of security may work but have not beentested.

ICA Client Require-ments

The Designer, Repository Manager, Server Manager,and License Manager were not designed to be runby multiple users at the same time. However, Citrixwill allow several instances of these programs to beactive at the same time on the same server. Busi-ness Objects recommends that you set the maximumnumber of instances for the Repository Manager,Server Manager, and License Manager executablesto 1.

For the Designer, you can allow multiple instancesof the .bat file to run, but limit one instance of this.bat file per user.

Since the Management Console is published ascontent, you can run multiple instances of it.

Application Limits

You can specify which servers in a Presentation Serverserver farm will run an application for client users. Se-lect the server on which you installed Data Servicesfor this purpose. If you installed Data Services on sev-eral servers, publish only one.

Specify Servers

You can specify which users can access a particularapplication. If you specify three users, the Data Ser-vices component defined by the application appears ineach of the users' Program Neighborhoods.

Specify Users


Citrix Support6 Publishing Data Services

Connection management

After installing Data Services components, give each user permission toestablish an ICA connection with the Presentation Server. Run the CitrixConnection Configuration tool to assign user permissions to a connection.

Client setup

If users will be running Data Services components from client computers,install the Citrix Program Neighborhood software on these computers.

Note: Data Services components were tested as a Citrix ProgramNeighborhood application set. These components were not tested as aProgram Neighborhood agent or web interface.

Related Topics• Initial installation on page 107

LimitationsThe following are known limitations to running Data Services on Citrix:

• Data Services stores files in the Job Server’s log directory when youcapture sample data using the View Data feature. If the Designer runson the same computer as the Job Server, the default location of the logdirectory changes each time a user logs in through Citrix. This changeprevents the Designer from locating the View Data log files for a givenuser. To avoid this issue, Business Objects recommends running the JobServer on a different computer than Designer. This limitation does notapply to the interactive debugger.

• If the Server Manager is published to a Citrix client and you try to add aJob Server from the client, the Data Services service might not start. Ifthis occurs, log onto the Job Server’s computer and restart the DataServices service. You must have sufficient user privileges to restart aservice using the computer’s operating system. When the Data Servicesservice is installed, it uses the ID and password that belong to the userwho runs the installer as its default login values.


6Citrix SupportLimitations

• Citrix runs the Designer process on the server and publishes only its userinterface to the client. Since the Designer runs on the server, users musthave sufficient read/write permissions for directories or files on the serverif you want users to access a file on the server as part of a Designer job.

• If registry popup windows appear when users attempt to start the Designer,then either give user accounts authority to query registry keys on theserver or give users administrator authority on the server.


Citrix Support6 Limitations

Directory Data

7

What are directories?

To correct addresses and assign codes with Data Services, the AddressCleanse transform relies on directories, or databases. When Address Cleanseuses the directories, it’s similar to the way that you use the telephonedirectory. A telephone directory is a large table in which you look upsomething you know—someone’s name—and locate something that youdon’t know—their phone number.

You may not need to use all of the reference files depending on whichtransforms or options you use in Data Services. Dependng on which optionyou own, some disks or online packages that you receive may contain extrafiles in addition to your directories. For example, you may see an Extractfolder. If you do not need these extra files, do not copy them to your computer.For information about extra folders, see the ReadMe.txt file included withthe reference files.

Directory listing and update schedule

Updated Month-ly (M)

Bimonthly (B)

Quarterly (Q)

SizeDirectory file-name

Directory type

MB691MBzip4us.dirZIP4 and Auxiliary Directories

MB2 MB

2 MB

2 MB

97 MB

cityxx.dir

zcfxx.dir

revzip4.dir

zip4us.rev

Auxiliary Directories

Weekly1MBewyymmdd.dirEarly Warning System Direc-tory

M560 MBdpv_pathDPV Data


Directory Data7 Directory listing and update schedule

Updated Month-ly (M)

Bimonthly (B)

Quarterly (Q)

SizeDirectory file-name

Directory type

M472 MBelot.dirEnhanced Line of Travel Di-rectory

M42 MBcanada.dir

cancity.dir

canfsa.dir

canpci.dir

Canada engine - AddressData

MB200 MBapc.dir

aucity.dir

aus.dir

Australia engine - AddressData

Qup to 8GB(for allcountries)

all filesGlobal Address engine - Data

Note: You will receive filesonly for those countries yourcompany has purchased.

Q677 MBcgeox.dirCentroid Level Geo Data

Q4 GBageox.dirAddress Level Geo Data

M199 MBz4change.dirZ4Change Data

Q30 MBall filesJapan engine - Address Data

Related Topics• Designer Guide: Address Server for the EMEA engine and GlobalSuggestion Lists


7Directory DataDirectory listing and update schedule

U.S. Directory expirationWe publish and distribute the ZIP4 and supporting directories under anon-exclusive license from the USPS. The USPS requires that our softwaredisable itself when a user attempts to use expired directories.

If you do not install new directories as you receive them, our program issuesa warning in the log files when the directories are due to expire within 30days. We recommend that you heed the warning and install the latestdirectories to ensure that your projects are based on up-to-date directorydata.

Note: Incompatible or out-of-date directories can render the softwareunusable. The directories are lookup files used by Business Objectsapplications. The system administrator must install monthly or bimonthlydirectory updates to ensure that they are compatible with the current software.

U.S. Directory expiration scheduleYou can choose to receive updated U.S. national directories on a monthlyor bimonthly basis. Bimonthly updates are distributed during the even months(see table).

Do not become concerned if you have not received your updated directorieson the exact distribution date. It’s normal for distribution to take a few weeksto reach all of our customers.

Date that the directories expireDate that we begin to distribute an up-date

May 31February 15

July 31April 15

September 30June 15

November 30August 15

January 31October 15

March 31December 15


Directory Data7 U.S. Directory expiration

U.S. National Directories are zippedThe directories included on the U.S. National Directory update are zippeddirectory files. The contents are zipped so that they still fit on a single disk.Because the files are zipped, you cannot access the ZIP4US directory filesdirectly from the disk. You must copy the zipped directory file to your computerand unzip it.

Here is a list of files that are zipped in all shipments.

Zip file nameDirectory name

us_dirs_2004.zip2004-2008 U.S. Nation-al directory

us_ageo1_2.zip

us_ageo3_4.zip

us_ageo5_6.zip

us_ageo7_8.zip

us_ageo9_10.zip

U.S. Address-levelGeoCensus

us_cgeo.zip

us_cgeo1.zip

us_cgeo2.zip

U.S. Centroid-levelGeoCensus

Related Topics• Unzip Windows file with Winzip on page 125

Where to copy directoriesWe recommend that you install directories in a common area where theycan be accessed by all computers and users that require them. By default,Data Services looks for directories in <DataServicesInstallLocation>\Business Objects\BusinessObjects Data


7Directory DataU.S. National Directories are zipped

Services\DataQuality\reference_data on Windows. If you place yourdirectories in a different location, you must then update your substitution file.

Related Topics• Copy International directory files to a non-default location on page 124

Copy International directory files to a non-defaultlocation

If you use the EMEA engine or Global Suggestions Lists and store your datadirectories in a location other than the default (x:\Business Objects DataServices\DataQuality\reference_data), do the following.

1. Stop any data flows that use the EMEA engine, Global engine or GlobalSuggestion Lists.

2. Stop the Address Server.

3. Copy the following files from <DataServicesInstallLocation>\Business Objects DataServices\DataQuality\reference_data to the location where youstore your data directories.• AddressServerGlobal.db

• MultiLineKeywords.db

• GaDirectoryDb.xml

• GaDirectoryDbemea.xml

• Ga_country.dir

• Ga_region_gen.dir

Note: Copy the reference files from to the default location to where youstore your directories every time you install an Data Services update.Copy the reference files over to the location where you store your datadirectories before you install the new directories.

4. Update the REFERENCE_DATA_DIRECTORY parameter in the AddressServerConfig.txt file located in <DataServicesInstallLocation>\Business Objects Data Services\bin\address_server\ tothe new reference directory location.

5. Update the RefFilesAddressCleanse substitution parameter configurationto the new reference directory location

6. Restart the Address Server.


Directory Data7 Where to copy directories

Download directories from the internetThe directory files are available for download on the Business ObjectsElectronic Software Download (ESD) site. Follow the instructions below todownload directory files.1. Access the Business Objects Electronic Software Download (ESD) site.

https://businessobjects.subscribenet.com/control/bobj/login2. Enter your username and password and click Login3. Select Products - Purchased to see a list of available downloads.4. Select the file you want to download.5. Select the file type you want to download.

Note: Select the ISO Image option if you plan to use a CD/DVD writingutility to create install disks.

Install directories fromdisk onWindowsTo install directories on Windows:

1. Insert the directories disk.2. Choose the directories you need from the disk and copy them to the

location where you store your directories. By default, Data Services looksfor the directory files in <DataServicesInstallLocation>\BusinessObjects\BusinessObjects DataServices\DataQuality\reference_data.

Unzip Windows file with Winzip

The steps listed here describe how to install the zipped directories usingWinZip for Windows. If you choose to use a different unzip tool, refer to unzipprocedure included with that tool.

1. Copy the zipped directory files manually from the disk to the locationwhere you keep your directories.

2. Locate and double-click the <filename> file.3. Click the Extract button.4. Select the folder where the files will be unzipped.


7Directory DataDownload directories from the internet

https://businessobjects.subscribenet.com/control/bobj/login

5. When the unzip process is finished, exit the unzip program.6. Repeat steps 1 through 5 for each required file.


Directory Data7 Install directories from disk on Windows

Global Parsing Options

8

Global Parsing Options are packages that enhance the ability of DataServices to accurately process various forms of global data by includinglanguage-specific reference data and parsing rules.

Data Cleanse repository databaserequirements and preparation

This section describes information necessary for you to create a Data Cleanserepository in various types of databases for use by Global Parsing Options.

Common requirements

Each installed Global Parsing Option requires free disk space in the repositorydatabase. For the English person and firm dictionary, the largest dictionary,approximately 600MB of free disk space is required.

In addition to the database space, temporary free hard drive space is requiredto run the Global Parsing Options installer. The amount required varies greatlydepending on which dictionary is being installed and what type of databaseis being used for the repository.

Temporary space requirements for the English person and firm dictionaryare shown as an example:

Temporary space requirementDatabase type

6,920MBDB2

420MBMicrosoft SQL Server

390MBMySQL

1,100MBOracle

DB2 database setup requirements

A Data Cleanse repository requires that you create a database and definea user with the rights:

• To create a table


Global Parsing Options8 Data Cleanse repository database requirements and preparation

• To start a session• To create a sequence

The DB2 database must also be configured with the following settings:

• Code Page: 1208• Character Set: UTF-8

Note: When creating a DB2 9 database, be sure to check the EnableDatabase for XML option.

The DB2 client must be configured with the following environment variable:

• DB2CODEPAGE = 1208

You can use the db2set utility to configure this environment variable. Seethe DB2 documentation for more information.

Microsoft SQL Server database setup requirements

When you create a repository on Microsoft SQL Server, choose betweenWindows authentication (by selecting the check box) or Microsoft SQL Serverauthentication (by completing the Microsoft SQL Server user name andpassword fields).

• Windows authentication — Microsoft SQL Server validates the loginaccount name and password by using information from the Windowsoperating system.

• Microsoft SQL Server authentication — Microsoft SQL Serverauthenticates the existing Microsoft SQL Server login account name andpassword.

Install Microsoft SQL Server client software and use Microsoft SQL Server'sSQL Query Tool to verify the connection between the Data Services Designercomputer and the Data Cleanse repository server.

Note: The Global Parsing Options installer requires Service Pack 4 to beapplied to Microsoft SQL Server 2000 installations.

Oracle database setup requirements

A Data Cleanse repository requires that you create a database and definea user with the rights:


8Global Parsing OptionsData Cleanse repository database requirements and preparation


Grant the user the connect and resource roles. For Oracle 10G/R2, alsogrant the create view role.

The Oracle server must also be configured with the following character sets:

• NLS_CHARACTERSET: AL32UTF8• NLS_NCHARSET: AL16UTF16

To determine the currently configured character set, you can use the followingselect statement on the Oracle server:Select * from nls_database_parameters WHEREPARAMETER = 'NLS_CHARACTERSET' ORPARAMETER = 'NLS_NCHAR_CHARACTERSET'

Install the Oracle client software and use SQL*Plus to verify the connectionbetween the Data Services Designer computer and the Data Cleanserepository. Set the NLS_LANG entry in the client registry to AMERICAN_AMERICA.AL32UTF8.

Note: The Oracle client version must match the Oracle server version. Forexample, if your server uses Oracle 9, use the Oracle 9 client.

MySQL database setup requirements

A Data Cleanse repository requires that you create a database and definea user.

The MySQL server and client must also be configured with UTF-8 as thedefault character set. In the DSN connection configuration window, set theODBC connection code page to UTF8.

Install Global Parsing OptionsBefore you install Global Parsing Options, you must create a Data Cleanserepository on a database server. Additionally, you must install Data Servicesbefore any Global Parsing Options; the Global Parsing Options installergathers some information from the existing Data Services installation.


Global Parsing Options8 Install Global Parsing Options

1. Specify whether or not you want to load the dictionaries into the DataCleanse repository during installation and click Next.If you choose not to load the dictionaries now, the installer will copy servercache and dictionary source information only. You can then load theminto the Data Cleanse repository at a later time by using the Data ServicesRepository Manager.

2. If you chose to load the dictionaries, specify the connection informationto your Data Cleanse repository and click Next. The information requireddepends on the database type of the Data Cleanse repository.


Database Name

User Name

Password

DB2

Database Server

Database Name

Windows Authentication

User Name

Password

Microsoft SQLServer

Database Server

Database Name

Port Number

User Name

Password

MySQL

Connection Name

User Name

Password

Oracle


8Global Parsing OptionsInstall Global Parsing Options

3. Select the dictionaries that you are licensed to install and want to loadinto the Data Cleanse repository and click Next.

4. Confirm the dictionaries to be loaded and click Next.The installer copies any necessary files and begins loading the specifieddictionaries into the Data Cleanse repository. This can be atime-consuming process, particularly if you are loading multipledictionaries.

Silent installationA silent installation is one that you run from the command line to install GlobalParsing Options. When you run a silent installation, you can specify all theparameters to be used for the install at the same time on the command line,rather than following the install wizard.

The silent install command line includes a series of parameters that provideinformation for installation settings and directory paths. You can also specifyoptions that control the level of prompts during an install.

The silent Global Parsing Options installation is particularly useful when youneed to perform multiple installations or you do not want to interrupt peoplewho are working on machines in your system.

You can also use the silent installation command in your own scripts. Forexample, if your organization uses scripts to install software on machines,you can insert the silent Global Parsing Options installation command intoyour scripts.

The silent installation command consists of the command setup.exe, followedby a number of parameters that provide information about the installation.

To perform a silent-mode installation

Before running the Global Parsing Options installer in silent-mode, it mustfirst be run in recording mode.

1. Run the installer in recording mode by specifying the /r option.setup.exe /r


Global Parsing Options8 Silent installation

The installer will record all selections made to the setup.iss file in thecomputer's Windows folder. If you want to specify a different location forthe ISS file, specify the /f1 option: /f1"./path/to/setup.iss"

2. Run the installer in silent mode by specifying the /s option. Use the /f1option to specify the location of the setup.iss file.setup.exe /s /f1"./path/to/setup.iss"

The installer silently completes Global Parsing Option installation, using allthe responses entered during recording mode.

To install using the command line

setup.exe Install gpo_zip_location gpo_zip_name database_type

[database_connection_info]

Caution: When installing Global Parsing Options from the command line,there is no automatic check for existing data in the target database. Anyexisting dictionary information in the target database will be lost andoverwritten by the new dictionary.


Location of the Global Parsing Option dictionary zipfiles.

For example, D:\gpo_zip_location

Filename of the Global Parsing Option zip file to in-stall.

For example, PERSON_FIRM_EN.zipgpo_zip_name


8Global Parsing OptionsSilent installation


The database type of the Data Cleanse repository.

Valid types:• DB2• Microsoft_SQL_Server_2000• Microsoft_SQL_Server_2005• MySQL• Oracle

database_type

Connection information required to connect to theData Cleanse repository.

For DB2:• Database Name• User Name• Password

For Microsoft SQL Server 2000 & 2005:• Database Server• Database Name• Windows Authentication (TRUE or FALSE)• User Name• Password

For MySQL:• Database Server• Database Name• Port Number• User Name• Password

For Oracle:• Connection Name• User Name• Password

database_connection_info



Example:

To install the English person and firm dictionary to a Microsoft SQL Server2000 database named DCRepository on the local computer using a usernamed GPOUser with a password of GPOPassword and no WindowsAuthentication, you could use the following command:setup.exe Install D:\ PERSON_FIRM_EN.zip Microsoft_SQL_Server_2000localhost DCRepository FALSE GPOUser GPOPassword


8Global Parsing OptionsSilent installation



IndexAAccess Server

configuration file, upgrading 100configuring, Windows 76, 82verify running 84

Administratorconfiguration file, upgrading 100

CClientTest.exe 103COM API, description 103components

distribution 13ports 18upgrading 98

configuringAccess Servers 76, 82Job Servers 76, 78, 95runtime resources for Job Servers 81

Configuring Job Server run-time resourcesresources, runtime for Job Serversconfiguring 81

DData Profiler

configuring 94Data Services

installing on Windows 72services, starting automatically 72

Data Services Web Serverstarting 72

DSConfig.txt file, upgrading customconfigurations 100

Ffunctor_list2312d.dll 103functor2312d.dll 103

Iinstallation

errors 95Windows 72

itc2312d.dll 103

JJob Server

configuration 76, 78, 95repository, synchronizing with 78verify running 84

LLINK_DIR system variable 103log, configuration file, upgrading 100logging in, Management Console 72

MManagement Console 20, 72, 103

log in 72troubleshooting 96


Message Client libraryCOM 103

mny2012d.dll 103multi-user development

requirements for 13

Nnetwork1712d.dll 103

Ppointer2312d.dl 103ports

default numbers 18description 18Job Server, configuring 103

Rrepository

central 17configuring 72creating, multiple 74Job Server, synchronizing with 78local 17troubleshooting 95upgrading 98, 102upgrading, multiple 102

Repository Manager 72restarting Data Services services 76

SServer Manager 76services, starting automatically 72SNMP, enable for a Job Server on Windows

103starting services 72Support adapter and SNMP option 103sync2312d.dll 103

TTCP/IP

port for Job Server 103thread2312d.dll 103threxcept2312d.dll 103tls7712d.dll 103

Uupgrading

components 98paths 98repository 98, 102successful 103

Vversions, repository 98


Index

Date post:	29-Aug-2014
Category:	Documents
Upload:	daniel-colina
View:	74 times
Download:	0 times