Installation Guide for UNIX ■ SAP BusinessObjects Data Services 4.0 (14.0.

1)

2011-08-18

Copyright

© 2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. 2011-08-18

Contents

Chapter 1

Introduction.............................................................................................................................7 Welcome to SAP BusinessObjects Data Services...................................................................7 Welcome.................................................................................................................................7 Documentation set for SAP BusinessObjects Data Services...................................................7 Accessing documentation......................................................................................................10 SAP BusinessObjects information resources.........................................................................11 Naming Conventions..............................................................................................................12 Planning................................................................................................................................15 System requirements.............................................................................................................16 System locale........................................................................................................................16 Software dependencies..........................................................................................................16 Account permissions..............................................................................................................17 Cron service..........................................................................................................................17 Network permissions.............................................................................................................18 Port assignments...................................................................................................................18 Central Management Server (CMS).......................................................................................20 Web application servers.........................................................................................................21 Database servers...................................................................................................................21 Kernel parameters and user resource limits............................................................................22 AIX user resource limits.........................................................................................................22 Solaris user resource limits....................................................................................................22 Linux user resource limits.......................................................................................................23 Preparation............................................................................................................................25 Preparing the repository database..........................................................................................25 Extra requirements for DB2....................................................................................................26 Extra requirements for MySQL...............................................................................................27 Extra requirements for Oracle.................................................................................................27 Extra requirements for Sybase...............................................................................................27

1.1 1.1.1 1.1.2 1.1.3 1.1.4 1.2
Chapter 2

2.1 2.1.1 2.2 2.3 2.3.1 2.4 2.4.1 2.5 2.6 2.7 2.8 2.8.1 2.8.2 2.8.3
Chapter 3

3.1 3.1.1 3.1.2 3.1.3 3.1.4

3

2011-08-18

................................................................................................... and Server 2008 issues...........50 Additional Information.1 4.................6.......68 To deploy web applications in a distributed environment...............................4......2.................................................................................29 Post-installation steps.....4...........................................................................................6........3 6...................................................................50 To remove SAP BusinessObjects Data Services.....7........................................36 Post-Installation.......................1 6........................55 Directory Data....................................5 6....................49 Windows Vista.................................64 WDeploy prerequisites.....................6.............................................................................2 5..............................56 U.2 6...............61 Using the software with HACMP.............4 6.................................Contents Chapter 4 Installation.............4....................................................................................................................1 5.................................................50 Making changes to your Data Services system..............6...........................................................................2 6................................................................................................29 To run an interactive installation..........................S..................................................49 Repository problems.......................62 WDeploy...........................................................60 To extract directory files.....................................67 To run WDeploy from the command line.................................1 6.............................................................6..................1 6.....................................32 To run a silent installation.................. 7...6 4 2011-08-18 ....................................................7 5........................1 4.........................47 Configuring Job and Access Servers.......................................................................................................................................................................59 To install and set up Download Manager................3 6...........4..........................1 5.......47 Configuring repositories...........67 To deploy or undeploy components.........4.......65 To start WDeploy.............................................................5 6................................. Directory expiration.................................................................................................................................47 Configuring users and groups.....................60 To download directory files...................58 Where to copy directories..........................................6.............................................6 6.........................................................6..........74 4........................................................4 6....................................................67 Advanced options.........2 6......................6.....................................................................................................................................................33 Command-line switch parameters...........5..............2 5...3 6............................................61 High-availability support........................................................................................................................1 Chapter 6 6..................................4 5...............................................................54 Uninstalling cleansing packages .2 Chapter 5 5..............................2..........................53 Installing SAP-supplied cleansing packages....34 Installation option parameters.............................................................................................................................................6 5..........................6 6.........................................................2 4..1 6............................................................56 Directory listing and update schedule.......5 5...........5 6.............4 6............1 4...3 5..................48 Configuring profiler repository connectivity.53 Modifying cleansing packages .................................................................................49 Troubleshooting installation problems....................................................................................................................................................48 Deploying web applications...............4...................................................1.................................

Contents Index 77 5 2011-08-18 .

Contents 6 2011-08-18 .

With SAP BusinessObjects Data Services. 1. metadata repository. Document What this document provides Administrator's Guide Customer Issues Fixed Designer Guide Information about administrative tasks such as monitoring.2 Documentation set for SAP BusinessObjects Data Services You should become familiar with all the pieces of documentation that relate to your SAP BusinessObjects Data Services product. It provides one development UI.1. and management console—enabling IT organizations to lower total cost of ownership and accelerate time to value. transform. and text data processing that allows you to integrate. Information about customer issues fixed in this release. run-time environment. Information about how to use SAP BusinessObjects Data Services Designer. data quality.1 Welcome SAP BusinessObjects Data Services delivers a single enterprise-class solution for data integration. and so on. data connectivity layer. data profiling. and deliver trusted data to critical business processes.Introduction Introduction 1. lifecycle management. IT organizations can maximize operational efficiency with a single solution to improve data quality and gain access to heterogeneous sources and applications. improve. 7 2011-08-18 . security.1.1 Welcome to SAP BusinessObjects Data Services 1.

com • Supplement for Siebel • Supplement for SAP Information about building dictionaries and extraction rules to create your own extraction patterns to use with Text Data Processing transforms. Information for third-party developers to access SAP BusinessObjects Data Services functionality using web services and APIs. Edwards • Supplement for Oracle Applications • Supplement for PeopleSoft • Supplement for Salesforce. Detailed reference material for SAP BusinessObjects Data Services Designer. languages.D. and locations. A compiled “master” PDF of core SAP BusinessObjects Data Services books containing a searchable master table of contents and index: • Administrator's Guide • Designer Guide • Reference Guide • Management Console Guide • Performance Optimization Guide • Supplement for J.Introduction Document What this document provides Documentation Map Installation Guide for Windows Installation Guide for UNIX Information about available SAP BusinessObjects Data Services books. Information about how to improve the performance of SAP BusinessObjects Data Services. Information about how to use SAP BusinessObjects Data Services Administrator and SAP BusinessObjects Data Services Metadata Reports. Information about and procedures for installing SAP BusinessObjects Data Services in a UNIX environment. Information about and procedures for installing SAP BusinessObjects Data Services in a Windows environment. Important information you need before installing and deploying this version of SAP BusinessObjects Data Services. Integrator's Guide Management Console Guide Performance Optimization Guide Reference Guide Release Notes Technical Manuals Text Data Processing Extraction Customization Guide 8 2011-08-18 .

D. Information about the interface between SAP BusinessObjects Data Services and Siebel. SAP Applications.com Adapter Interface. and SAP NetWeaver BW. Edwards OneWorld. and use the SAP BusinessObjects Data Services Salesforce.D. 9 2011-08-18 .D. Information about the interface between SAP BusinessObjects Data Services and Oracle Applications. Document What this document provides Supplement for J. Release-specific product behavior changes from earlier versions of SAP BusinessObjects Data Services to the latest release. and maintaining an Information platform services installation. you may need to refer to several Adapter Guides and Supplemental Guides. A step-by-step introduction to using SAP BusinessObjects Data Services. Information about how to install. Document What this document provides Information Platform Services Administrator's Guide Information for administrators who are responsible for configuring.Introduction Document What this document provides Text Data Processing Language Reference Guide Information about the linguistic analysis and extraction processing features that the Text Data Processing component provides. managing. as well as a reference section for each language supported. This manual also contains information about how to migrate from SAP BusinessObjects Data Quality Management to SAP BusinessObjects Data Services. Edwards World and J.com Supplement for SAP Supplement for Siebel Information about interfaces between SAP BusinessObjects Data Services and J. configure. We also include these manuals for information about SAP BusinessObjects Information platform services. This document is not updated for support package or patch releases. Tutorial Upgrade Guide What's New In addition. Highlights of new key features in this SAP BusinessObjects Data Services release. Information about interfaces between SAP BusinessObjects Data Services and PeopleSoft. Edwards Supplement for Oracle Applications Supplement for PeopleSoft Supplement for Salesforce. Information about interfaces between SAP BusinessObjects Data Services.

you can access the documentation from the Start menu. Choose Start > Programs > SAP BusinessObjects Data Services 4.3. 2.1. Click the appropriate shortcut for the document that you want to view. you can access the online documentation by going to the directory where the printable PDF files were installed.1.Introduction Document What this document provides Information Platform Services Installation Guide for UNIX Information Platform Services Installation Guide for Windows Installation procedures for SAP BusinessObjects Information platform services on a UNIX environment. Go to <LINK_DIR>/doc/book/en/.1 Accessing documentation on Windows After you install SAP BusinessObjects Data Services.1. 1.0 > Data Services Documentation. Using Adobe Reader. 10 2011-08-18 .3 Accessing documentation You can access the complete documentation set for SAP BusinessObjects Data Services in several places. 1. 2.3. 1. open the PDF file of the document that you want to view. Installation procedures for SAP BusinessObjects Information platform services on a Windows environment. 1. Note: Only a subset of the documentation is available from the Start menu. 1. The documentation set for this release is available in <LINK_DIR>\Doc\Books\en.2 Accessing documentation on UNIX After you install SAP BusinessObjects Data Services.

Consulting. 2. and much more. Go to http://help. 3. 11 2011-08-18 . samples.com/irj/sdn/ds tricks. Useful addresses at a glance: Address Content Customer Support. Education services can provide information about training options and modules.sap.additional downloads. 1. From traditional classroom learning to targeted e-learning seminars.1. and online forums. education. All content is to and from the community.3 Accessing documentation from the Web You can access the complete documentation set for SAP BusinessObjects Data Services from the SAP BusinessObjects Business Users Support site. SAP BusinessObjects can offer a training package to suit your learning needs and preferred learning style. SAP BusinessObjects Data Services Community Get online and timely information about SAP BusinessObjects Data Services .1. Click SAP BusinessObjects at the top of the page.sdn.4 SAP BusinessObjects information resources A global network of SAP BusinessObjects technology experts provides customer support.3. downloads. including tips and http://www. and Education services http://service. as well as links to technical articles.Introduction 1. Click All Products in the navigation pane on the left. 1.com/ Information about SAP Business User Support programs. You can view the PDFs online or save them to your computer. Consulting services can provide you with information about how SAP BusinessObjects can help maximize your information management investment.sap.sap. and consulting to ensure maximum information management benefit to your business.com. so feel free to join in and contact us if you have a submission.

sap.sap.jspa?foru mID=305 Search the SAP BusinessObjects forums on the SAP Community Network to learn from other SAP BusinessObjects Data Services users and start posting questions or share your knowledge with the community.sap. sample data.com/forum. Click the link for the version of Data Services you are searching for. jobs. file formats.sap.com/businessobjects/ Supported Platforms (Product Availability Matrix) https://service.sdn.com/irj/boc/blueprints Product documentation http://help. “BI platform” refers to “SAP BusinessObjects BI platform”.2 Naming Conventions In this documentation. Each blueprint contains the necessary SAP BusinessObjects Data Services project.sdn. Blueprints for you to download and modify to fit your needs. data flows. Use the search function to search for Data Services. 1. the following naming conventions apply: Terminology • • “Data Services system” refers to “SAP BusinessObjects Data Services”. Blueprints http://www.Introduction Address Content Forums on SCN (SAP Community Network ) http://forums. 12 2011-08-18 . template tables. SAP BusinessObjects product documentation. and custom functions to run the data flows in your environment with only a few modifications. “CMS” refers to the Central Managment Server provided by BI platform.com/PAM Get information about supported platforms for SAP BusinessObjects Data Services. • • “CMC” refers to the Central Managment Console provided by the BI platform. Note: The BI platform components required by Data Services may also be provided by SAP BusinessObjects Information platform services.

Introduction Variables Variables Description <INSTALL_DIR> The installation directory for the Data Services system. <LINK_DIR> The root directory of the Data Services system. which is created automatically during installation. This path is defined in the $LINK_DIR environment variable. The default is $HOME/businessobjects. 13 2011-08-18 .

Introduction 14 2011-08-18 .

ensure that the host systems in your deployment can communicate with each other across the network. A larger scale deployment might install individual system components on dedicated host systems to host individual server functions over a network. Set up account permissions. database servers. Determine the location of the components to be installed. You decide how the components that comprise Data Services will be distributed. For a detailed list of supported environments and hardware requirements. and the installation methods that you can use. database. • • When setting up a deployment comprised of two or more host systems networked together. Before installing: • Review your host systems to ensure that they meet the basic requirements. UNIX. and operating systems. or cluster systems that will be used. Choose a database server. SAP BusinessObjects Information platform services. and a web application server on a single host system.Planning Planning SAP BusinessObjects Data Services can be installed on Windows. or Linux platforms. with a combination of supported web servers. Determine system requirements. For example: a single host dedicated to a web application server. A small development deployment might use the installation program's default options to install Data Services. 3. Process Flow The following sections list the core software requirements.com/PAM. databases.sap. and a single host dedicated to the SAP BusinessObjects Information platform services. 15 2011-08-18 . consult the Product Availability Matrix available at http://service. web browsers. 1. 2. a single host dedicated to the Data Services core system. Choose a web application server. 5. This includes the specific subnet. web application servers. machines. Determine network permissions. For more information on how to plan your installation. and web technologies. security. This information includes specific version and patch-level requirements for web application servers. the choices available to you within the core requirements. 4. see the “Architecture” section of the Administrator's Guide.

the installation program will use the existing directory. consult the Product Availability Matrix available at http://service.com/PAM.2 Software dependencies Before you install SAP BusinessObjects Data Services.sap.1 System locale The installation program requires the system to be configured with a UTF-8 locale. 2. ensure that your host systems meet all software dependency requirements. ensure that there is enough room for the deployment and the operating system. For example. see the Platform Availability Matrix available at http://service. • If you have previously installed any SAP BusinessObjects products. For complete information about software environment requirements. set the LANG or LC_ALL environment variables. ensure that the destination partition has enough room for the deployment to expand (when updates and new features are added in the future). • If you want to install the deployment on the operating system partition. on Linux: export LANG=en_US. use the following guidelines: • Before you run the installation program. 16 2011-08-18 .1 System requirements When you install SAP BusinessObjects Data Services on a local drive. To list the available locales on your system.utf8 export LC_ALL=en_US. To set your system locale to UTF-8. use the locale -a command. For a complete list of supported operating systems and hardware requirements.Planning 2.utf8 Note: The locale name may be different depending on your UNIX platform.sap.com/PAM.1. 2.

Planning 2. and edit table rows. it's recommended that you install the Job Server while logged on as a user without root-level access. and read.allow. Installing the Job Server with root-level access ensures that root-level access is not required to administer files and processes created by the Job Server. or production environment uses tightly controlled root-level administration. Database In addition. Automatically restarting the Job Server on Autostart configuration edits must be made by a user with system restart system-level authority. the account that starts the Job Server must have an entry in the cron. a user must have the following permissions: Category Required permissions Network Network connectivity through appropriate ports to all host systems in the deployment. 2. access to shared file system directories for users of the deployment.3. 17 2011-08-18 . Additional notes If your design. If cron security uses cron. Only a few administration functions require root-level access: Function Required permissions Scheduling jobs Permission to access cron. write. it's recommended that you use the same user account for installing Data Services and your web application server.1 Cron service SAP BusinessObjects Data Services schedules UNIX-based jobs by using the cron utility.allow file. Permission for the SAP BusinessObjects user account to create and drop tables. and appropriate network authentication privileges. test.3 Account permissions To install SAP BusinessObjects Data Services.

The software cannot schedule a job to run on the Job Server. use the following guidelines to ensure your network functions properly: • Each host system must be able to communicate with the Central Management Server (CMS).allow /etc/cron. /var/adm/cron/cron. • Each client. must be able to communicate with the Job Server(s). or forward-slash (/). • Each host system must be able to communicate with the host that runs the repository database.allow /usr/lib/cron/cron. you may need to open the necessary ports to allow the client components to communicate with the servers.Planning Operating system cron.allow location AIX Solaris Linux For more information. You can manually execute and monitor jobs from the Designer. The CMS coordinates the functioning of all the servers in the deployment.4. Fully-qualified hostnames are supported. Note: Ensure that deployment hostnames do not include any of the following characters: underscore (_). such as the Designer. verify that all ports to be used by SAP BusinessObjects Data Services components are available and not in use by other programs.allow Note: Installing the Job Server without access to cron causes the following Job Server behavior: • • • The Job Server can operate normally. period (. backslash (\).1 Port assignments On each host system. Note: If your servers are protected by a firewall. see your cronman pages. • Each host system must use a fixed hostname. 18 2011-08-18 . 2.).4 Network permissions When you install SAP BusinessObjects Data Services across multiple host systems. 2.

If your deployment includes a firewall between the Designer and Job Server. Default Port Description 8005 8080 Control port that is used to start and shut down the web application server that supports the Management Console. The ports used by the Job Server and Access Server are configurable in the Server Manager. and schedulers. This table details the default ports used by Data Services components: Default Port Component Description 3500 4000 4001 4010 4011 4012 4013 5001 Job Server Access Server Job Server Job Server port that receives commands from Designers. Installing on a single host simplifies many connections between components (the host name is always the same). By default. 19 2011-08-18 . Metadata Browsing Communication port used by the JMX Connector. Access Servers. Metadata Browsing Listener port used to communicate with the Data Services Service backend engine. Adapter and SNMP communication port that receives commands and sends data to adapters. Interactive debugger port that supports communication for the debugging feature.Planning For a development system. Note: If you use a different web application server. Communication port that receives and sends messages from clients and services. Service View Data Service View Data Service Designer Listener port used to communicate with the Data Services backend engine. you can install many components on the same host. Tomcat application server Tomcat is the default web application server for the BI platform. HTTP port that supports communication between web browsers and the Management Console. but you must still define connections based on the TCP/IP protocol. Note: The Designer also uses a range of ports to communicate with the Job Server for the notification server feature. Communication port used by the JMX Connector. The ports used by the Designer are configurable by choosing Tools > Options within the Designer. the default ports and configuration method may differ. this port range is controlled by the Designer.xml configuration file. The default ports for Tomcat are configurable in the Tomcat conf/server. you can manually set this port range from within the Designer.

as well as the packaged Tomcat installation provided by the BI platform. 2.5 Central Management Server (CMS) Before you can install SAP BusinessObjects Data Services. you must have a working SAP BusinessObjects BI platform Central Management Server (CMS). 20 2011-08-18 . Default ports for other web application servers may differ. the basic CMS functions required by Data Services can be provided by SAP BusinessObjects Information platform services. Data Services relies on the CMS for: • Centralized user and group management • Flexible authentication methods • Password enforcement policies • Administrative housekeeping services • RFC Server hosting • Services for integrating other SAP BusinessObjects software Note: If you do not have a SAP BusinessObjects BI platform installation. The installation program creates Data Services InfoObjects in the CMS.Planning Example: Default configuration The following configuration diagram shows default port numbers.

21 2011-08-18 . consult the Product Availability Matrix available at http://service. revision levels. see the SAP BusinessObjects Information Platform Services Installation Guide 2.6 Web application servers You can integrate SAP BusinessObjects Data Services with a Java web application server.com/PAM. The deployment also supports the following database servers: • IBM DB2 • MySQL • Oracle • Sybase Adaptive Server Enterprise Note: The database client and server must use the Unicode character set. Tomcat is the default Java web application server provided by the SAP BusinessObjects BI platform and Information platform services. and requirements. The web application server must be operational and accessible when you run the installation program. For information about installing SAP BusinessObjects Information platform services. use InstallIPS instead of setup. For a complete list of supported web application servers. the database server must be operational and accessible when you run the installation program. This is useful for deploying web applications to nodes in a web application server cluster. If you want to configure a repository during installation.sap.7 Database servers You need a database to host the SAP BusinessObjects Data Services repository.sap.com/PAM.Planning If you choose to use Information platform services. consult the Product Availability Matrix available at http://service.sh to launch the Information platform services installation program. Note: The “Management Console” option installs only web applications to a supported Java web application server. 2. For a detailed list of supported database versions.

it's recommended that you use the following user resource limits.8. it's recommended that you use the following user resource limits. User resource limit Value Comments file (blocks) data (kbytes) stack (kbytes) memory (kbytes) nofiles (descriptors) 4194302 unlimited 2048 2097151 2000 At least 2 GB 2 MB At least 2 GB At least 2000 2. if you intend to use the USA Regulatory Address Cleanse transform with caching of DPV and LACSLink directories.1 AIX user resource limits For installations on AIX host systems. You can display these settings by running the ulimit -a command from your Data Services user.8.Planning 2.8 Kernel parameters and user resource limits It's recommended that you use the following kernel parameters and user resource limits when installing SAP BusinessObjects Data Services. 2. you must set your operating system's Data Segment Size limit to Unlimited. Note: In addition to the following requirements. You can display these settings by running the ulimit -a command from your Data Services user. 22 2011-08-18 .2 Solaris user resource limits For installations on Solaris host systems. This system parameter must be set before starting the software.

3 Linux user resource limits For installations on Linux host systems. You can display these settings by running the ulimit -a command from your Data Services user. it's recommended that you use the following user resource limits.Planning User resource limit Value Comments file (blocks) data (kbytes) stack (kbytes) time (seconds) nofiles (descriptors) coredump (blocks) vmemory (kbytes) unlimited unlimited 2048 unlimited 1024 unlimited unlimited Unlimited. User resource limit Value Comments file (blocks) data (kilobytes) stack (kilobytes) time (cpu-seconds) nofiles (descriptors) coredump (blocks) memory (kilobytes) lockedmem (kilobytes) processes unlimited unlimited 2048 unlimited 1024 unlimited unlimited 4 7168 2 MB 23 2011-08-18 .8. at least 2 GB At least 1 K 2 MB 2.

Planning 24 2011-08-18 .

25 2011-08-18 . you will be asked to supply a Central Management Server (CMS) registration name for the repository.com/swdc. and delete tables. 2. Record the database. Process Flow 1. 3. • Repository database connection information. and to create stored procedures. The installer will prompt for the following information: • License information (the name of the user and company associated with your software). and account that will be used to store repository information. tablespace or schema (if applicable). • Job Server and Access Server configuration information. 4. • When you use a database server on a network. connection.Preparation Preparation This section details how to prepare for the installation of SAP BusinessObjects Data Services. contact your database administrator. In most cases. allowing both the operating system and the software to grow over time as patches or new components become available. 3. Gather the installation media or download the latest release and any patches or service packs from the support portal at http://service. To establish which drivers are required for your database. During the installation process.1 Preparing the repository database Before you can create a repository for SAP BusinessObjects Data Services. Obtain the installation media. • Ensure that your database server is configured to use Unicode character encoding (such as UTF-8). modify. • Ensure that the database accounts have privileges to create. tablespace. More advanced installations require that you plan the installation process. and authentication details. including type. Ensure that sufficient disk space is available to install. and account information so you can enter the details when prompted by the Data Services installation program. Decide which options you will change during the installation process. as well as the connection and authentication credentials so that the installation program can initialize the repository database. you must complete the following tasks: • Create a database. install the appropriate database client drivers and verify that they work before you install Data Services.sap. you can accept the default values. • Administrator-level connection information for the Central Management Server (CMS).

1. 26 2011-08-18 . • Ensure that the software has a temporary table space with a page size of 8-16K.Preparation Note: The CMS registration name determines how the repository will appear in the Central Management Console (CMC). and must be unique.1 Extra requirements for DB2 If you are using DB2 for the repository database: • Install the DB2 Application Enabler software and use DB2 Control Center and DB2 Script Center to verify the connection between the Designer host system and the repository host system. The table below shows which information is required for third-party databases: Database Information required MySQL • • • • • • • • • • • • • • • • • • • • CMS registration name Database name Server name Port number (default is 3306) Login credentials used to access the database CMS registration name Database name Server name Port number Login credentials used to access the database CMS registration name Database name Server name: DB2 database alias Port number Login credentials used to access the database CMS registration name Server: TNSNAMES connect identifier Port number SID Login credentials used to access the database Sybase ASE DB2 Oracle 3.

ensure that the Sybase path precedes the Microsoft SQL Server path in the environment variables %PATH% statement.3 Extra requirements for Oracle If you are using Oracle for the repository database: • Grant the database account the connect and resource roles. If the case does not match. 3.Preparation 3. when you register a Sybase repository in the Central Management Console (CMC). or you risk corrupting the metadata.2 Extra requirements for MySQL If you are using MySQL for the repository database: • Ensure that the unixODBC driver manager is installed and configured. 3. 27 2011-08-18 . see “Configuring ODBC data sources on UNIX” in the Administrator's Guide. the case you type for the database server name must match the associated case in the SYBASE_Home\interfaces file. • For Job Servers on UNIX. to store Japanese characters. you might receive an error because the Job Server cannot communicate with the repository. you must change the Oracle database character set to a code page that supports the multi-byte language that you plan to use.4 Extra requirements for Sybase If you are using Sybase for the repository database: • If you are using both Sybase and Microsoft SQL Server on a Windows host system.1. For Oracle 10G/R2. change the Oracle database character set to either SHIFT_JIS or UTF8. For more information about obtaining and using the unixODBC driver.1. • Install the Oracle client software and use SQL*Plus to verify the connection between the Designer machine and the repository. Note: To store multi-byte characters in a repository table when the repository is on an Oracle database. For example.1. also grant the create view role.

Preparation 28 2011-08-18 .

utf8 export LC_ALL=en_US. For example: export LANG=en_US. or download the SAP BusinessObjects Data Services installation media. When an installation option is not given on the command-line. mount. Installation options can be given in a response file rather than directly on the command-line. 4.utf8. 1. When the -q (quiet mode) switch is used. • Silent installation Installation options are given on the command-line.1 To run an interactive installation Log on and load. If the installation program encounters an unexpected condition and is unable to continue. This is the default installation method.utf8 The installation log file will be saved to <INSTALL_DIR>/InstallData/logs/<DATE>/Install DU<COMPONENT>. Note: The installation program requires a minimum of 80 columns and 30 rows to display correctly. such as en_US. Change to the directory containing the setup. Use this option to select individual options from a series of screens. Ensure that LC_ALL has been set to a supported UTF-8 character set. it will undo any work completed up to that point and return the system to the state that it was in before the installation started.Installation Installation You can run the installation program several ways: • Interactive installation An interactive wizard prompts for all information related to the installation. 29 2011-08-18 . which override the installation program's default values. The command-line can be used to give some or all installation options. If you are running the program in a terminal application.log. be sure to set the window size accordingly. Installation options stored in the response file can be overridden by giving them on the command-line. the installation program uses a default value.sh installation program. This type of silent installation uses the -r command-line parameter to read installation options from the response file. Use this option if you want to install multiple machines with the same configuration. the installation program does not prompt for any user input during the installation.

The welcome screen appears. the installation program does not display the results of dependency prerequisites./setup. Store the keycode and registration information in a safe place in case you need to reinstall the software.sap. If a critical component or supported version is not found. 5. 2. you have the option to either continue with the installation process or stop and correct the condition. Review the destination folder shown. Review the welcome screen. Enter the name. The language setting is used by the installation program to display information to you in the language of your choice. 8. 4. 6. English language support cannot be deselected because it is used if a problem is detected with an individual language. The language used by the installation program will determine the names used for components configured by the installation program. 7. see the Product Availability Matrix available at http://service. and the product keycode you purchased. To install support for a language. These names cannot be changed later and are not affected by language settings once the installation is complete. The license agreement screen appears. the installation program writes an error to the installation log file and aborts. Review and accept the license agreement. If you select a non-English language. For a complete list of supported languages. The installation program will provide information on how to correct the condition. The installation program starts and the language selection screen appears.Installation Use the InstallDir=<DESTINATION_DIR> parameter to set the destination folder from the command line. select it from the list. Choose a language for the installation program to use during the installation process. Note: The installation program will automatically run in the same language as your operating system. the installation program will not allow the installation to proceed. The user information screen appears. the corresponding language pack is automatically installed on the server. The language currently being used by the operating system is selected automatically. the missing or unsupported component is noted in the installation log file. If the missing or unsupported component is optional. The installation program checks for required components. use the command . or abort and correct any unmet requirements. During a silent installation.com/PAM. 3. to install the Data Services system into the /opt/sap directory. Review the results and decide whether to continue the installation. The destination folder selection screen appears. 30 2011-08-18 . If an optional component or supported version is not found. The installation program runs prerequisite checks and displays the results. company. For example. If the folder does not exist. the installation program will create it. The language pack selection location screen appears. If a dependency prerequisite condition is critical. This is the folder into which the installation program will install Data Services.sh InstallDir=/opt/sap.

and can skip the CMS configuration on the other host systems. choose Install Data Services with CMS Server. Note: You cannot upgrade an existing repository during the installation process. and runtime resources. 9. you only need to configure the InfoObject and APS services once. This file should contain the complete connection string for your configuration. b. If you want to configure repositories after installation. you can use the Repository Manager after installing Data Services. Restriction: Data Services supports only the Enterprise authentication method during installation. select Configure a new Job Server. For example: (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = vanpgc13b9)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = orcl)) ) c. Enter the connection information for the repository database. b. To configure a local repository. enter the SSL configuration information. Select additional languages if you want to process unstructured text in other languages. 12. Enter the name and port for the Job Server. a. you can skip the Job Server configuration screen. Select the Data Services components that you want to install. b. If you want to configure additional Job Server properties. 11. If you chose to enable SSL for the CMS connection. The feature selection screen appears. The Access Server configuration screen appears. Note: Text Data Processing support for English is installed by default and cannot be uninstalled. Choose the type of the database that you want to use to host the repository. To configure a Job Server. Choose Create to create a new repository. a. select Use an existing database. SNMP communication. you can skip the repository configuration screen. a. you must specify the location of the Oracle RAC connection string file. 31 2011-08-18 . Note: In distributed installations. Enter administrator-level connection information for your Central Management Server (CMS).Installation The Central Management Server (CMS) selection screen appears. select Job Server advanced configure. The Job Server configuration screen appears. such as SSL. If you want to configure Job Servers after installation. Note: If you want to use Oracle RAC for the repository database. If you want to upgrade an existing repository. 10. The repository configuration screen appears. To configure the Data Services InfoObject and Adaptive Processing Server (APS) services.

transfers files. a. you have the option to create a single repository that will be registered in the CMC. During the installation process. a. For more complex configurations. 15. you must deploy web applications with the WDeploy web application deployment tool. you can skip the Access Server configuration screen. and configuring Job and Access Servers. If you are not using the bundled Tomcat web application server. For more information see the “Post-Installation” section and the Administrator's Guide. you need to perform additional configuration steps such as creating users and groups. Enter the username and password to use to log into the SLD server. b. and performs additional configuration actions. a single Job Server. If you only use batch processing. Enter the directory and port for the Access Server. During installation. and a single Access Server. choose Integrate with SAP Solution Manager. 4. Specify whether you want to enable the Access Server or enable SSL. Note: The Access Server is only required for real-time scenarios. To configure an Access Server. Choose Next to begin the installation process. The start installation confirmation screen appears. you do not need to configure an Access Server. Related Topics • Post-Installation • WDeploy • Configuring users and groups • Configuring repositories • Configuring Job and Access Servers 32 2011-08-18 . The installation completion screen appears. registering repositories in the CMC. 14. If you want to configure Data Services with SAP Solution Manager. The SAP Solution Manager integration screen appears.Installation 13. If you want to configure Access Servers after installation.1. the installation program saves your installation selections in a cache. b. select Configure a new Access Server. or if you need to make changes. Enter the hostname and port for your SLD server.1 Post-installation steps When the installation is complete. review the information in the "Post Installation Steps" screen.

instead of the default value of 3500.] Related Topics • Installation option parameters • Response file example 33 2011-08-18 ... For example... the installation program is run from the command-line with the -r <RESPONSE_FILE> parameter. In the following example of giving the DSConfigJSPort parameter in a response file. the installation option DSConfigJSPort=3501 can be given on a line in the response file to set the Job Server port number to 3501..sh [..] DSConfigJSPort=3501 [. Giving installation options on the command-line Installation options can be passed directly to the installation program from the command-line as a parameter./setup... In the following example of giving the DSConfigJSPort parameter on the command-line.sh [.] -r $HOME/response. ellipses ([. Installation options can be given directly on the command-line as a parameter. instead of the default value of 3500.. When using a response file to give installation options.] Giving installation options in a response file Installation options can be stored in a response file. This type of installation is known as a silent install.] DSConfigJSPort=3501 [.Installation 4. with one installation option per line.. or can be stored in a response file../setup. ellipses ([. In the following example.. which is a text file containing installation option parameters in key-value format..] For example. the response file is given as a parameter: . The response file contains multiple installation options... where <RE SPONSE_FILE> is the name of the response file. the installation option DSConfigJSPort=3501 can be given on the command-line as a parameter when running the installation program to set the Job Server port number to 3501.]) indicate where other installation options would normally be present: [.ini [..]) indicate where other installation options would normally be present: .2 To run a silent installation Every option in the installation wizard can be given from the command-line.

and errors are written to the installation log file in the folder: <INSTALL_DIR>/InstallData/logs/<DATE>/InstallDU<COMPONENT>.sh -q -r "$HOME/re prompting.sh -r "$HOME/re sponse. 34 2011-08-18 . run the installation program with the -r <RESPONSE_FILE> parameter.sh -w "$HOME/re ./setup.Installation 4.1. Installation options given on the command-line take precedence over the options in the response file. warnings. Reads installation options from a response file named <FILENAME>. If an unexpected condition is encountered./setup.log in the temporary folder specified by the system TEMP environment variable. For a complete list of installation options. If a problem is encountered. see “Installation option parameters”./setup. For example.log If the <INSTALL_DIR> folder has not been created by the time the installation program exits. sponse.ini: .ini" -r <FILENAME> -q Installs with no console output or ./setup.ini" the installation program will write a message to the installation log file and exit.1 To use a response file To use a response file. 4. the installation program writes an error message to the installation log file and exits.2. Installation activity.ini" the installation wizard.1 Command-line switch parameters The following table lists the switch parameters that can be given to the installation program on the command-line to perform a silent installation. The installation program reads all installation options from the response file. the following command reads installation options from the response file $HOME/re sponse.2.ini To override an installation option in a response file. give that option on the command-line.sh -r $HOME/response. look for install. and no further input is required. . Switch parameter Description Example -w <FILENAME> Writes a response file to <FILENAME> . containing the options selected from sponse.

1.sh -w $HOME/response. and override default values. the command-line options take precedence over the response file options.2. run the installation program with the -w <RESPONSE_FILE> parameter and select the desired installation options with the installation wizard. When an option is given both on the command-line and in a response file./setup.Installation Related Topics • Installation option parameters 4. Installation options given in a response file are used when not given on the command-line./setup. remove the password. it is recommended that you remove the passwords from the response file and specify the parameters on the command-line instead.ini: .1. The response file can then be used for future installations./setup. 2. For example. and then specify it on the command-line: . the response file can be updated with a text editor.1 To write a response file To create a response file. 3.1.2 To read a response file A response file installation is started on the command-line. but installation options are read from an ASCII text file with the options stored in key-value format. locate DSCMSPassword=password in the response file. the installation program exits and the response file is created. and provides three levels of precedence for installation options: 1. Installation option default values are used when not given on the command-line or in a response file.ini. the following command creates the response file $HOME/response. When the wizard completes. they are stored in the response file in plain text.sh -r $HOME/response. For example. and will always override response file and default values. Installation options given on the command-line take highest precedence. A response file installation is useful when setting up a cluster.ini DSCMSPassword=password 4. For example. Caution: When you specify passwords in the installation program. or for creating development or test environments with standardized options. the following command reads installation options from the response file $HOME/re sponse.ini InstallDir=/opt/sap/sap_bobj/ 35 2011-08-18 . For security reasons. but overrides the response file's setting for the installation destination folder: .sh -r $HOME/response. This feature allows an administrator to override an option in a response file when required.ini Once created.1.2.

2 Installation option parameters The following table lists the parameters that can be used to select installation options both on the command-line and in response files. The -q switch bypasses the installation program's installation wizard. the following command installs the Job Server and Access Server. 4.2. and errors are written to the installation log file in the folder: <INSTALL_DIR>/InstallData/logs/<DATE>/InstallDU<COMPONENT>.DataServicesAccessServer pro ductkey=XXXXX-XXXXXXX-XXXXXXX-XXXX selectedlanguagepacks=en setupuilanguage=en If an unexpected condition is encountered. Substitute the language code where <CODE> is: • English: EN Destination folder into which the installation program will install the software. InstallDir=<PATH> 36 2011-08-18 .log in the temporary folder specified by the system TEMP environment variable.sh -q InstallDir=/opt/sap/sap_bobj/ choosesldintegration=nointegrate dsconfigasselection=skip dsconfigcmsselection=skip dsreposelection=skip features=DataServicesJobServer. look for install. Installation activity. Table 4-1: Installation option parameters Parameter Description SetupUILanguage=<CODE> Determines the language for the installation program to use during the installation.log If the <INSTALL_DIR> folder has not been created by the time the installation program exits./setup. Installation options must be provided on the command-line or in a response file. For example. .1.2 Quiet mode installations A quiet mode installation is a command-line installation that does not prompt for installation options. an error message is written to the installation log file and the installation program exits. warnings.Installation 4. and overrides the installation destination folder (set to /opt/sap/sap_bobj instead of the current working folder). Any installation options not provided on the command-line or in a response file will be left at their default values. and allows an installation to be performed with no human input and no console output.2.

Substitute <NAME> with the name.Installation Parameter Description SelectedLanguagePacks=<CODE> Installs language support for users and administrators to interact with SAP BusinessObjects Data Services in a supported language. Specifies the node name for the Central Management Server (CMS). set <SWITCH> to 1. If the CMS is configured for SSL support. RegisteredCompany=<NAME> ProductKey=<KEY> ChooseSLDIntegration=<VALUE> DSCMSAuth=<TYPE> DSCMSNode=<NODE> DSCMSSystem=<HOST> DSCMSUser=<USER> 37 2011-08-18 . Hostname of the Central Management Server (CMS). If more than one language pack is to be installed. To disable SLD integration. Substitute <USER> with the user name. Name of the company to whom the software is registered. Authentication type used by the Central Management Server (CMS). language support for English will be installed: SelectedLanguagePacks="en" Substitute the following language codes where <CODE> is: • English: EN RegisteredUser=<NAME> Name of the user to whom the software is registered. Determines whether SAP System Landscape Directory (SLD) support will be enabled or not. Susbstitute the authentication type where <TYPE> is: • Enterprise authentication: secEnterprise Restriction: Data Services supports only the Enterprise authentication method during installation. Substitute <NODE> with the CMS node name. set <VALUE> to noin tegrate. User name for the CMS administrator account. set <SWITCH> to 0. to separate each code. If the CMS is not configured for SSL support. use a semi-colon delimited list without spaces. Product license key issued when you purchased the software. Substitute <NAME> with the name. within quotes. set <VALUE> to integrate. In the following example. To enable SLD integration. Substitute <KEY> with the product key in the format XXXXXXXXXXX-XXXXXX-XXXX. DSCMSEnableSSL=<SWITCH> Specifies whether the Central Management Server (CMS) uses SSL security. Substitute <HOST> with the CMS hostname.

Substitute <PORT> with the port number.txt configuration file to merge with the new installation configuration. To not enable the Access Server. Determines whether the installation program will merge an existing DSConfig. set <SWITCH> to 0.Installation Parameter Description DSCMSPassword=<PASSWORD> Password for the CMS administrator account. Substitute <PORT> with the port number. Directory where the Access Server should be configured. so that it must be enabled manually at a later time. Determines whether to configure a new Job Server during installation. set <VALUE> to skip. set <SWITCH> to 0. To enable the Access Server automatically after the installation. set <VALUE> to new. To configure a new Access Server. set <VALUE> to skip. Substitute <PATH> with the full path of the existing configuration file. To configure a new Job Server. Existing DSConfig. To not configure a new Job Server. Substitute <PASS WORD> with the password. To merge an existing configuration file. Network TCP listening port number used by the Job Server. To not configure CMShosted components. set <VALUE> to install. set <VALUE> to skip. Server name for the Job Server to create during the installation process. set <SWITCH> to 1. To not merge an existing configuration file. Network TCP listening port number used by the Access Server. set <VALUE> to in stall. To configure CMS-hosted components. Determines whether or not SSL support will be enabled on the Access Server. Substitute <DIRECTORY> with the full directory path. Determines whether to configure a new Access Server during installation. To enable SSL on the Access Server. DSConfigASCommPort=<PORT> DSConfigASDirectory=<DIRECTO RY> DSConfigASEnableAS=<SWITCH> DSConfigASEnableASSSL=<SWITCH> DSConfigASSelection=<VALUE> DSConfigCMSSelection=<VALUE> DSConfigJSSelection=<VALUE> DSConfigJSServerName=<NAME> DSConfigJSServerPort=<PORT> DSConfigMergeSelection=<VALUE> DSExistingDSConfigFile=<PATH> 38 2011-08-18 . set <VALUE> to new. Determines whether the Access Server will be enabled automatically after the installation is complete. To not configure a new Access Server. Determines whether to configure InfoObjects and the Management Console on a CMS during installation. set <SWITCH> to 1. set <VALUE> to skip. To not enable SSL support.txt configuration file with the new installation configuration. Substitute <NAME> with the Job Server name.

To enable SSL on the Job Server. set <SWITCH> to 1. Substitute <PASSWORD> with the password. set <SWITCH> to 0. Substitute <DIRECTORY> with the full directory path. set <SWITCH> to 1. and SNMP communication. Substitute <PORT> with the port number. To enable communication support on the Job Server. set <VALUE> to true. Starting network TCP listening port number used by the Job Server when sending data between data flows or sub data flows. To enable SNMP on the Job Server. and SNMP communication. set <SWITCH> to 1. set <VALUE> to this. set <SWITCH> to 0. To not enable communication support. Determines whether SSL support will be enabled on the Job Server. Substitute <PORT> with the port number. set <VALUE> to system. Ending network TCP listening port number used by the Job Server when sending data between data flows or sub data flows. DSJSDetailCacheDirectory=<DI RECTORY> DSJSDetailCommPort=<PORT> DSJSDetailEnableSSL=<SWITCH> DSJSDetailEnableSNMP=<SWITCH> DSJSDetailEndPort=<PORT> DSJSDetailStartPort=<PORT> DSJSDetailSupportComm=<SWITCH> DSJSPCacheEnableSSL=<SWITCH> DSLoginInfoAccountSelec tion=<VALUE> DSLoginInfoThisPassword=<PASS WORD> 39 2011-08-18 . set <VALUE> to false. message broker. Determines whether or not the Job Server will support adapter. Network TCP listening port number used by the Job Server for adapter. Determines whether SNMP support will be enabled on the Job Server. To log onto the host system using the system account. set <SWITCH> to 0.Installation Parameter Description DSInstallInfoObjects=<VALUE> Determines whether or not the installation program will configure the Data Services InfoObjects on the Central Management Server (CMS) during the installation process. To not enable SSL support. Determines whether the Data Services service will log onto the host system using the system account or a specific user account. To configure the InfoObjects during installation. Determines whether or not SSL support will be enabled for pageable cache on the Job Server. Directory where the Job Server pageable cache should be configured. message broker. set <SWITCH> to 0. To not enable SSL support. Password for the account that the Data Services service should use to log onto the host system. To log onto the host system using a specific user account. Substitute <PORT> with the port number. set <SWITCH> to 1. To not enable SNMP support. To enable SSL support. To not configure the InfoObjects.

Connection string used to connect to an Oracle repository database. Substitute <USER> with the user name.Installation Parameter Description DSLoginInfoThisUser=<USER> User name for the account that the Data Services service should use to log onto the host system. DSRepoDBName=<NAME> DSRepoDBPasswd=<PASSWORD> DSRepoDBPort=<PORT> DSRepoDBType=<TYPE> DSRepoDBUser=<USER> DSRepoNameForCMS=<NAME> DSRepoOracleConnStr=<VALUE> 40 2011-08-18 . Substitute <USER> with the account user name. Network TCP listening port number used by the Metadata Browsing Service for the JMX connector. Substitute <NAME> with the database name. Substitute <NAME> with the repository name. Network TCP listening port number used by the database that will host the Data Services repository. Type of database that will host the Data Services repository. Substitute <PASSWORD> with the account password. Network TCP listening port number used by the Metadata Browsing Service. Password for the database account that will be used to access the repository database. Substitute <HOST> with the hostname. Name that will be used to register the Data Services repository in the Central Management Server (CMS). Substitute <VALUE> with the connection string. Substitute <PORT> with the port number. Database name for the database that will contain the Data Services repository. DSMDSJMXPort=<PORT> DSMDSPort=<PORT> DSRepoCreateUpgrade=<VALUE> DSRepoDBDataSource=<VALUE> DSRepoDBHost=<HOST> Hostname for the database server that will contain the Data Services repository. set <VALUE> to Create. Determines whether to create or upgrade a Data Services local repository during the installation process. Substitute <PORT> with the port number. Substitute <PORT> with the port number. To create a new local repository. Substitute the database type where <TYPE> is: • MySQL: MySQL • Oracle: Oracle • DB2: DB2 • Sybase ASE: Sybase User name for the database account that will be used to access the repository database.

DataServicesAccessServer DSRepoWindowsAuth=<SWITCH> DSVDSJMXPort=<PORT> DSVDSPort=<PORT> Features=<CODE> For a complete list of feature codes. set <VALUE> to exist ing.Installation Parameter Description DSRepoOracleRAC=<VALUE> DSRepoOracleSID=<VALUE> DSRepoSelection=<VALUE> User-specific Oracle RAC value required to use Oracle as the repository database. To select multiple features. 4. List of components to install. For example. without spaces. In the fol lowing example. separate each feature code with a comma. set <SWITCH> to 0. To select multiple features.DataServicesDocumentation • root: install all features • DataServicesServer: install all server components • • DataServicesJobServer DataServicesAccessServer 41 2011-08-18 . Determines whether or not to configure a new repository during the installation process.2. the following feature list selects the Job Server and documentation files: features=DataServicesJobServer. Network TCP listening port number used by the Viewdata Service.2. use a comma-delimited list without spaces to give each code.1 Feature codes Use the following feature codes to select features for installation. Network TCP listening port number used by the Viewdata Service for the JMX connector. Substitute <PORT> with the port number. To not configure a new repository. Substitute <PORT> with the port number. the Job Server and Access Server will be selected for install: Features=DataServicesJobServer. To configure a new repository. User-specific Oracle SID required to use Oracle as the repository database. set <VALUE> to new. set <SWITCH> to 1. If the database uses a different authentication method. see Feature codes. If the database uses Windows authentication. Specifies whether or not the repository database uses Windows authentication.

Example: In this example. the response file is named $HOME/response.CMSNode.description# dscmsnode=boenode ### #property.CMSAuthMode.CMSServerName.2 Response file example The following example response file contains options for installing SAP BusinessObjects Data Services.description# dscmssystem=localhost 42 2011-08-18 .CMSEnabledSSL.description# dscmsenablessl=0 ### #property.ChooseSLDIntegration.description *** choosesldintegration=nointegrate ### #property.2. ### *** property.description# dscmsauth=secEnterprise ### #property.description# dscmsnodelist=boenode ### CMS administrator password dscmspassword=password ### #property.Installation • • • • • DataServicesMetadataIntegrator: DataServicesDesigner DataServicesClient: install all client components DataServicesManagementConsole DataServicesEIMServices: install services to the Adaptive Processing Server (APS) • • • • DataServicesRFCService DataServicesAdminService DataServicesMetadataService DataServicesViewdataService • • DataServicesMessageClient TextDataProcessingLanguages: install all text data processing languages • • • • • • TextDataProcessingEnglish TextDataProcessingFrench TextDataProcessingGerman TextDataProcessingJapanese TextDataProcessingChinese TextDataProcessingSpanish • • DataServicesDataDirect: install the DataDirect ODBC driver manager library DataServicesDocumentation: install documentation files 4.CMSNodeList.ini.2.

DSConfigJSSelection.DSExistsOnCMS.description# dsconfigasenableas=1 ### #property.DSConfigASEnableAS.DSJSDetailCacheDirectory.DSConfigCMSSelection.description# dslogininfoaccountselection=this ### #property.description# dsjsdetailstartport=1026 ### #property.description# dsjsdetailenabessl=1 ### #property.CMSUser.description# dsconfigjsselection=new ### #property.description# dsjsdetailcachedirectory=/opt/sap/sap_bobj/dataservices/Log/pCache ### #property.description# dscmsuser=Administrator ### #property.description# dsconfigmergeselection=skip ### #property.description# dsjsdetailendport=32767 ### #property.DSConfigASSelection.DSJSDetailStartPort.DSInstallInfoObjects.description# dsconfigasdirectory=/opt/sap/sap_bobj/dataservices/bin/AccessServer_1 ### #property.DSJSDetailSupportComm.DSJSDetailEnableSNMP.description# dsconfigjsserverport=3500 ### #property.DSJSDetailEnabeSSL.description# dsjsdetailsupportcomm=0 ### #property.DSExistingDSConfigFile.description# dsexistingdsconfigfile= ### #property.DSJSPCACHEEnableSSL.description# dslogininfothispassword=Password ### #property.DSConfigJSServerName.DSConfigASDirectory.DSJSDetailCommPort.DSLoginInfoThisPassword.DSLoginInfoAccountSelection.description# dsconfigasenableasssl=1 ### #property.Installation ### #property.description# dsconfigjsservername=JobServer_1 ### #property.DSConfigMergeSelection.description# dsjspcacheenablessl=1 ### #property.description# dsjsdetailenablesnmp=0 ### #property.description# dsconfigcmsselection=install ### #property.description# dsinstallinfoobjects=false ### #property.DSLoginInfoThisUser.description# dsconfigasselection=new ### #property.description# dsconfigascommport=4000 ### #property.description# dslogininfothisuser=DOMAIN\USER ### JMX connector dsmdsjmxport=3889 43 2011-08-18 .DSConfigJSServerPort.DSJSDetailEndPort.DSConfigASEnableASSSL.description# dsjsdetailcommport=4001 ### #property.description# dsexistsoncms=1 ### #property.DSConfigASCommPort.

DSRepoDBUser.DSRepoNameForCMS.description# selectedlanguagepacks=en ### *** property.description# dsmorethanonecmsnode=0 ### #property.description# dsrepocreateupgrade=Create ### #property.DSRepoDBName.DSRepoDBPasswd.SetupUILanguage.description# dsreponameforcms=shared_new ### #property. registereduser=User Name ### #property.description# dsrepodbhost=localhost ### #property.DSRepoOracleConnStr.description# dsrepodbpasswd=dbpasswd ### #property.SelectedLanguagePack.description# dsrepodbuser=dbuser ### #property.description# dsrepodbtype=Microsoft_SQL_Server ### #property.description# dsrepooraclerac=No ### #property.description# dsreposelection=existing ### #property. productkey=XXXXX-XXXXXXX-XXXXXXX-XXXX ### Name of company registered for this product.description# dsrepooraclesid= ### #property.description# dsrepodbport=1433 ### #property.Installation ### Metadata service port dsmdsport=9001 ### #property.description# dsrepodbdatasource= ### #property. registeredcompany=Company Name ### Name of user registered for this product.DSRepoOracleRAC.DSRepoCreateUpgrade.DSRepoSelection.DSRepoWindowsAuth.description *** setupuilanguage=en ### Available features ### -----------------### root ### DataServicesServer ### DataServicesJobServer 44 2011-08-18 .DSRepoDBDataSource.DSRepoDBHost.description# dsrepooracleconnstr= ### #property.description# dsrepodbname=ds_repo ### #property.DSRepoOracleSID.DSRepoDBPort.description# dsrepowindowsauth=0 ### JMX connector dsvdsjmxport=8899 ### Viewdata service port dsvdsport=9988 ### Installation folder for SAP BusinessObjects products installdir=/opt/sap/sap_bobj/ ### Keycode for the product.DSMoreThanOneCMSNode.DSRepoDBType.

DataServicesAdminSer vice.TextDataProcessin gEnglish.Installation ### DataServicesAccessServer ### DataServicesMetadataIntegrator ### DataServicesClient ### DataServicesDesigner ### DataServicesManagementConsole ### DataServicesEIMServices ### DataServicesRFCService ### DataServicesAdminService ### DataServicesMetadataService ### DataServicesViewdataService ### DataServicesMessageClient ### TextDataProcessingLanguages ### TextDataProcessingEnglish ### TextDataProcessingFrench ### TextDataProcessingGerman ### TextDataProcessingJapanese ### TextDataProcessingChinese ### TextDataProcessingSpanish ### DataServicesDataDirect ### DataServicesDocumentation features=DataServicesJobServer.DataServicesMessageClient.DataServicesViewdataService.DataServicesRFCService.DataServicesDocumentation 45 2011-08-18 .DataServicesAccessServer.DataServicesMetadataService.

Installation 46 2011-08-18 .

you must log in as a user with administrative access. see the Administrator's Guide. Log into the CMC. 5. the process to configure a Data Services repository is: 1. In general. For more information about configuring users and groups for Data Services. you need to configure repositories and register them in the Central Management Console (CMC). For more information about creating and configuring repositories. the process to configure Data Services users and groups is: 1. see the Administrator's Guide. 5. Register the repository in the CMC with the Data Services application.Post-Installation Post-Installation This section describes the activities that should be performed after the installation program has finished.2 Configuring users and groups Before you can use the Data Services system. 47 2011-08-18 . Create the repository in the database with the Repository Manager. In general. 5. Create a database for the repository on your database server. Create user accounts and assign them to Data Services user groups with the Users and Groups application. To create and modify user accounts. Assign repository access to your users and groups with the Data Services application.1 Configuring repositories Before you can use the Data Services system. you need to configure users and groups in the Central Management Console (CMC). Log into the CMC. Assign user access to the repository with the Data Services application. 3. 3. 4. 2. 2.

However. Associate local and profiler repositories with the Job Server. b. the database connectivity settings on all host machines in the Data Services deployment must match. Restart the Data Services service and verify that the Job and Access Servers are running. the Job Server has the information required to connect to the profiler repository and the profiler request is processed successfully. Add the Job Server configuration. Without matching connectivity settings. the results of profiling tasks will not be visible from within the Designer. Add and configure Access Servers with the Server Manager. The Job Server is configured on the same host machine as the MySQL database. Ensure that the same profiler database connectivity settings are used on each host machine. If the Designer then tries to view the profiled data. you need to use the Server Manager to configure Job Servers for batch jobs and Access Servers for real-time applications before you can use the Data Services system. the results of the profiling task will not be visible.Post-Installation 5. 5. If connectivity to the profiler database is not configured on the Designer host machine. 48 2011-08-18 . Example: MySQL repository In this example.3 Configuring Job and Access Servers If you did not configure them during installation. When the Designer submits a profiler task to the Job Server. Add and configure Job Servers with the Server Manager. 3. 2.4 Configuring profiler repository connectivity For the Designer to connect to a profiler repository. the process to configure Data Services Job Servers and Access Servers is: 1. In general. if the same DSN and connectivity settings are already configured on the Designer host machine. the DSN information. see the Administrator's Guide. and all its connectivity settings to the database are configured on that host machine. it attempts to connect to the profiler repository directly and not through the profiler server. the profiler repository is a MySQL database running on a separate host machine from the Designer. For more information about using the Server Manager to configure Job and Access Servers. the results of the profiling task are visible as expected. For example. a.

1 Repository problems Common repository-related installation errors include: • • The DBMS connection was lost while building the repository tables. reboot the host system after installation has finished. For more information about the Repository Manager. 5. This option allows you to view the SQL code that SAP BusinessObjects Data Services uses to perform these operations.Post-Installation 5. If the installation program did not automatically deploy web applications to your web application server. 49 2011-08-18 . an incorrect server name. you must deploy the web applications manually with the WDeploy tool. see the Administrator's Guide.6. The Show Details option can help you diagnose problems. you can select the Show Details check box before you click Update or Create again. If this happens. use your DBMS administration tools to allocate more space for the repository and run the Repository Manager. or password) result in an immediate error message describing the problem. or with the web application server administrative console.5 Deploying web applications The installation only installs web applications to Tomcat 6. such as the service scheduler failing to launch SAP BusinessObjects Data Services. For some common issues. If this happens.6 Troubleshooting installation problems Errors that prevent installation progress (for example. recreate the repository with the Repository Manager. The WDeploy tool automates the deployment of web applications to supported web application servers. Related Topics • To run WDeploy from the command line 5. If you experience problems when upgrading or creating a repository. There is not enough space available in the database for the repository tables. user name.

2 Windows Vista.7 Making changes to your Data Services system 5.sh to start the removal program. Change directory to <INSTALL_DIR>. For example. or Windows Server 2008. Any remaining folders can be removed manually with the rm -R <DIR> command. Run the command . 7. you can use the grantFileAccess. you must enclose it in double quotes. It is recommended that you back up the CMS database and your repository databases before uninstalling Data Services. This batch file is installed to the <LINK_DIR>\bin folder and takes one parameter as input. 5./modifyOrRemoveProducts. 2.6. To manually update the file access rights. and Server 2008 issues File or application in use When installing or uninstalling SAP BusinessObjects Data Services on Windows Vista. Log files.7. Windows 7. if you installed the software to C:\Program Files\Business Objects\BusinessObjects Data Services\: grantFileAccess. Update to file access rights failed When installing SAP BusinessObjects Data Services on Windows Vista.bat "C:\Program Files\Business Objects\BusinessObjects Data Services\" If your installation path contains spaces.Post-Installation 5.1 To remove SAP BusinessObjects Data Services These instructions describe the process to permanently uninstall SAP BusinessObjects Data Services from a host system. Ignoring these messages will have no impact on the installation or behavior of the software. you may receive this warning if the installation setup program is unable to set file access rights. the software installation path (LINK_DIR). configuration files for web applications.bat batch file. Windows 7. You can safely ignore these messages and continue to install or uninstall the software. 1. 50 2011-08-18 . and web applications will not be removed by the removal program. you may receive messages about files in use or applications that should be closed. or Windows Server 2008.

51 2011-08-18 .Post-Installation The software has been removed from the host system.

Post-Installation 52 2011-08-18 .

Before you install SAP-supplied cleansing packages.com/bosap-downloads. When this occurs.1 Installing SAP-supplied cleansing packages Cleansing packages can be installed on Windows. To install SAP-supplied cleansing packages: 1. Note: Before installing.Additional Information Additional Information 6. Review and accept the license agreement. • Installed SAP BusinessObjects Data Services. Solaris and Linux. ensure you have met the following prerequisites: • Downloaded SAP BusinessObjects Data Quality Management Cleansing Packages for the appropriate platform from the SAP Service Marketplace at http://service. SAP supplies person and firm cleansing packages for a variety of regions. 53 2011-08-18 . The Data Quality Management cleansing packages installation wizard starts. all users currently logged into the SAP BusinessObjects Business Intelligence platform Central Management Server (CMS) may encounter a disruption in service.sh file to start the installer.sap. plan for this downtime at a convenient time for them. The Cleansing Package Builder module of Information Steward is required in order to modify an SAP-supplied cleansing package. Access to the directory where you downloaded cleansing packages from the SAP Service Marketplace. Subsequent installation of additional cleansing packages do not require an SIA restart. Installing a cleansing package makes it available in the Data Cleanse transform in Data Services and also in Information Steward Cleansing Package Builder. Each cleansing package is designed to enhance the ability of Data Cleanse to appropriately cleanse the data according to the cultural standards of the region. The service interruption occurs only during the initial installation. Note: The Cleansing Package installer will restart the Server Intelligence Agent (SIA). 3. download the files to the local hard drive. 2. To minimize the disruption to your CMS users. 4. and run the setup. Choose Data Services / Information Steward. Read the explanatory text on screen. • (Optional) Installed SAP BusinessObjects Information Steward. AIX.

This login information is for the administrator-level SAP BusinessObjects BI platform Central Management Server (CMS). Enterprise authentication is required and cannot be changed here. Select Modify. 7. To add or remove cleansing packages: 1. CMS user name. you may want to install additional cleansing packages. 8. The cleansing packages that you selected are now installed and available for you to use. Access to the directory where you downloaded cleansing packages from the SAP Service Marketplace. The Data Quality Management cleansing packages installation wizard starts. 54 2011-08-18 . 6. or remove some cleansing packages that you installed previously. 3. the installer overwrites the existing cleansing packages. Choose the cleansing packages that you want to install. Proceed until installation is complete. select Disk Cost. Password corresponding to your CMS user name. Option Description System Enable SSL User Name Password Authentication Name of the server hosting the CMS. and run the setup. SSL is required and cannot be changed here. If you choose to install cleansing packages that already exist on your Central Management Server. a warning message appears.sh file to start the installer. Related Topics • Modifying cleansing packages • Uninstalling cleansing packages 6. Enter administrator-level SAP BusinessObjects BI platform Central Management Server (CMS) login information. To learn how much disk space is needed for this installation and how much disk space is available.2 Modifying cleansing packages After you have installed some cleansing packages. 2.Additional Information 5. Enter your login information. If you choose to proceed.

Password corresponding to your CMS user name. If you choose to proceed. Only use the CMC to delete modified cleansing packages. and uninstall using the installer. If you want to install the cleansing package that you previously deleted in the CMC. First. you will still see the modified cleansing packages in the CMC. If you have not modified the cleansing packages. the installer overwrites the existing cleansing packages. 5. 4. you can either install or uninstall cleansing packages. the cleansing packages are automatically removed from the CMC. you will still see the modified cleansing packages in the CMS. SSL is required and cannot be changed here. Related Topics • Installing SAP-supplied cleansing packages • Uninstalling cleansing packages • 6. If you modify the installed cleansing packages. Proceed until installation is complete. you may not see it in the list of cleansing packages available during the install. and then uninstall using the installer. If you choose to install cleansing packages that already exist on your Central Management Server. CMS user name. remove the cleansing package with the installer. Note: • During one instance. You cannot install and uninstall at the same time. We recommend only uninstalling cleansing packages using the installer. To uninstall cleansing packages: 55 2011-08-18 . Enterprise authentication is required and cannot be changed here. and then run the installer again to remove cleansing packages. Run the installer again. and then uninstall using the installer. and then you will see the cleansing package available. We recommend that you first install the cleansing packages.3 Uninstalling cleansing packages We recommend only uninstalling cleansing packages using the installer. Choose the cleansing packages that you want to install or uninstall. If you modify the installed cleansing packages.Additional Information Option Description System Enable SSL User Name Password Authentication Name of the server hosting the CMS. Only use the CMS to delete modified cleansing packages. a warning message appears.

6. 2. and run the setup. Option Description System Enable SSL User Name Password Authentication Name of the server hosting the CMS. Note: If you modified the cleansing packages. SSL is required and cannot be changed here. Password corresponding to your CMS user name. Choose the cleansing packages that you want to uninstall. you must also uninstall the cleansing packages from the Central Management Server.sh file to start the installer.1 Directory listing and update schedule 56 2011-08-18 . Proceed until uninstallation is complete. If you have not modified the cleansing packages.4 Directory Data To correct addresses and assign codes with SAP BusinessObjects Data Services. Access to the directory where you downloaded cleansing packages from the SAP Service Marketplace. in addition to uninstalling with this installer. Related Topics • Installing SAP-supplied cleansing packages • Modifying cleansing packages 6. A telephone directory is a large table in which you look up something you know—someone’s name—and locate something that you don’t know—their phone number. The Data Quality Management cleansing packages installation wizard starts. the Address Cleanse transform relies on directories. they are automatically uninstalled from the CMS. 3. CMS user name.Additional Information 1. When Address Cleanse uses the directories.4. 4. it’s similar to the way that you use the telephone directory. or databases. Select Remove. 5. Enter administrator-level SAP BusinessObjects BI platform Central Management Server (CMS) login information. Enterprise authentication is required and cannot be changed here.

dir cancitypoc.Additional Information Updated Monthly (M) Directory type Directory filename Approximate Size Quarterly (Q) M M ZIP4 Directory Auxiliary Directories zip4us.dir Canada engine .8 GB 3. Q Q Q Q 3.dir geo_gb_nt.dir canpcmpoc.dir geo_fr_nt.dir geo_de_nt.dir canpcipoc.dir Data Global Address engine .United Kingdom geo_ca_nt.POC Address Data POC data canadapoc.rev zip4us.POC Address canpcm.dir zip4us.Canada Geocoder .Data Note: You will receive files only for those countries your company has purchased.4 GB 3.dir M M M Canada engine .shs 800 MB 2 MB 2 MB 1 MB 97 MB 4 MB 1 MB 660 MB 500 MB 72 MB Early Warning System Directory DPV Data Enhanced Line of Travel Directory ewyymmdd.Non.dir cityxx.8 GB 57 2011-08-18 .Germany Geocoder .dir all files elot.8 GB 5.dir zcfxx.France Geocoder . Geocoder .dir canfsapoc.dir all files 45 MB up to 28 GB (for all countries) M Q Note: Australia and Japan directories are updated monthly.dir revzip4.

ZIP4 and Auxiliary.dir Q Z4Change Data LACSLink SuiteLink z4change.dir geo_us_nt. national directories on a monthly or bimonthly basis. To ensure that your projects are based on up-to-date directory data. When running in Non-Certified mode. and Z4Change Directories expire on first day of the fourteenth month after directory creation.S.Additional Information Updated Monthly (M) Directory type Directory filename Approximate Size Quarterly (Q) Q Geocoder . • • 58 2011-08-18 . Expiration schedule You can choose to receive updated U.dir all files all files M M M 6.7 GB 2. Parcel level cgeo2.dir ageo*. and Z4Change Directories expire on 1st day of the fourth month after directory creation.United States cgeo2. Directory expiration We publish and distribute the ZIP4 and supporting directory files under a non-exclusive license from the USPS. DPV. The USPS requires that our software disable itself when a user attempts to use expired directories.dir ageo*_pt. The directories are lookup files used by SAP BusinessObjects software.United States. Bimonthly updates are distributed during the even months. LACSLink directories expire 105 days after directory creation. Note: Incompatible or out-of-date directories can render the software unusable.7 GB 60 GB 640 KB 2.dir 640 KB 2. the software issues a warning in the log files when the directories are due to expire within 30 days.dir ageo*.4.S. DPV. eLOT. SuiteLink directories expire on the 1st day of the third month after directory creation. eLOT. Directory expiration guidelines are: • ZIP4 and Auxiliary.2 U. If you do not install new directories as you receive them.dir geo_us_nt. it's recommended that you heed the warning and install the latest directories.5 GB 100 GB 199 MB 465 MB 760 MB Geocoder . The system administrator must install monthly or bimonthly directory updates to ensure that they are compatible with the current software.

S.3 Where to copy directories We recommend that you install the directory files in a common file system directory local to the host system on which SAP BusinessObjects Data Services is installed.S.2. Directory name Zip file name 2004-2008 U. 6.exe Related Topics • To extract directory files 6.Additional Information 6.exe us_ageo9_10.4.exe U.exe U. National directory us_dirs_2004.4. Address-level GeoCensus us_ageo1_2.3.1 To copy international directory files to a non-default location 59 2011-08-18 .exe us_cgeo1.exe us_ageo5_6.1 U.exe us_ageo7_8.exe us_cgeo2.S. By default.4. Centroid-level GeoCensus us_cgeo.exe us_ageo3_4.S. National and Auxiliary file self-extracting files are named as follows.S. If you place your directories in a different location. the software looks for directories in <LINK_DIR>/DataQuality/reference_data. you must update your substitution file. National and Auxiliary files The U.

4 To install and set up Download Manager Before you can download directory files. 2. 60 2011-08-18 . Follow the steps to install and set up the Download Manager. To download directories: 1. Access the SAP Service Marketplace (SMP): http://service. Access the SAP Service Marketplace (SMP) site: http://service.dir • ga_region.com/bosap-support 2. From the left pane. 3. To install and set up Download Manager: 1.sap.xml • ga_country.dir Note: • • Every time you install an SAP BusinessObjects Data Services software update.com/bosap-support 2. 3. Click the Get Download Manager button. select Downloads > SAP Software Distribution Center > Downloads > Installations and Upgrades > My Company's Application Components. 6.5 To download directory files The directories are available for download from the SAP Service Marketplace (SMP). Select Download Basket.4. Copy the reference files over to the location where you store your data directories before you install the new directories.sap. 5. 4. Select Downloads.4. you need to install and set up Download Manager. 3. Select Downloads. copy the reference files from to the default location to where you store your directories. do the following: 1. 6. Update the RefFilesAddressCleanse substitution parameter configuration to the new reference directory location.Additional Information If you use the Global Address Cleanse transform's Global Address engine or Global Suggestion Lists' Global Address engine and store your data directories in a location other than the default ( <LINK_DIR>/DataQuality/reference_data ). Stop any data flows that use the Global Address engine or Global Suggestion Lists. Copy the following files from <LINK_DIR>/DataQuality/reference_data to the location where you store your data directories: • ga_directory_db.

Additional Information A list of your company's applications and any license-free products or components appear. Install the necessary components to support the system on duplicate hardware systems.0. click Get Download Manager. 6. or group of networked computers. About HACMP software HACMP software makes applications and software systems highly available. To use HACMP software to make a system highly available: 1. To access the Download Manager documentation. The software includes start and stop scripts that support HACMP software.4. use HACMP software to minimize downtime of your system.6 To extract directory files The steps listed here describe how to install the zipped directories using Info-Zip. Copy the zipped directory files manually from the CD to the location where you keep your directories. 4. 7. For ZIP4US. 6. restoring essential services when a system component or application fails. you define each complete system as a resource group. creating clusters or nodes that can support identical services that the system processes. HACMP software quickly restores essential services by starting the failed system on an alternate computer. 1. Define takeover relationships that determine which cluster or node supports the resource group at any given time. The files you select are placed in the Download Basket. Repeat for each required file. 3.zip -d <outputfolder>. To support HACMP software. Follow the steps included in the Download Manager documentation to download the directory files. you replicate software and hardware systems to guarantee backup of essential services. Define the system as a resource group (a logical group that the HACMP software and AIX operating system manages). 2. 2. type unzip us_dirs_2004. There are three types of takeover relationships: 61 2011-08-18 . Type unzip <filename>. 6. called a cluster. 3. Within HACMP software. When a component fails in a resource group. 5.5 High-availability support If you run SAP BusinessObjects Data Services on AIX and you have High Availability Clustered Multi-Processing (HACMP) software version 4. called a node.4. see the unzip procedure included with that tool. click Download Basket.zip -d /Business Objects/BusinessObjects Data Services/DataQuality/reference_data). If you use a different unzip tool. Select the files you want to download and add them to the Download Basket. To access the Download Basket.

You must use the same user ID on all clusters where you install the software.5. and targets—must also be highly available. Rotating Clusters are listed along with a priority rank. You must enable automatic recovery for all scheduled jobs. 6. On each cluster node.1 Using the software with HACMP SAP BusinessObjects Data Services contains start and stop scripts that support HACMP software.1 To use the software with HACMP 1. The start script: • • • Identifies jobs scheduled before the previous cluster failed and launches those jobs in recovery mode Identifies jobs scheduled to start during cluster down time and launches those jobs Synchronizes the cron file on the new cluster with the cron file on the previous cluster When using the software with HACMP. You cannot use a concurrent takeover relationship for the software resource group. Control of the resource group goes to the active cluster with the highest priority ranking. Control can change due to failure or to the reactivation of a cluster with a higher priority rank. Concurrent Multiple clusters support the resource group at the same time. you should be aware of several requirements and restrictions: • • • • • • • There can be no single point of failure.5. 6. SAP BusinessObjects Data Services and its configuration is made available for the rest of the cluster nodes. The database systems that support jobs—the repository. You must also enable the recurrent option for all scheduled jobs. define the same mount point for the file system.Additional Information Cascading Clusters are listed along with a priority rank. 2.1. These scripts run when a new cluster takes control of the software resource group. Install the Job Server on a file system in the shared volume group from a single cluster node. 62 2011-08-18 . You can use HACMP only with batch jobs. sources. Control only changes due to the failure of a cluster. or the additional availability provided by HACMP is compromised. Control of the resource group goes to the active cluster with the highest priority ranking.

Define the software as a resource group (a logical group that the HACMP software and AIX operating system manages). Define takeover relationships that determine which cluster or node supports the software resource group at any given time.5.sh $ ./svrcfg starts the Server Manager. Enter 7 to configure HACMP. . Copy the start and stop scripts (acta_start. 5.2 To configure the software to use HACMP 1. The Server Manager main screen appears. The HACMP configuration screen appears.sh and acta_stop. Run the Server Manager. 2. 4. c. 3.1. Designate the start and stop scripts as the start and stop scripts for the software resource group./al_env. In the HACMP software: a. $ cd $LINK_DIR/bin/ $ . Enter 1 and stop the Job Service. b. 6./svrcfg Note: The second command sets required environment variables before .sh) from the <LINK_DIR>/hacmp directory to the HACMP scripts directory on each of the cluster nodes. Configure the software to use HACMP.Additional Information 3. 63 2011-08-18 .

Additional Information -----------------------------------------------------------------** Current HACMP Configuration for Data Services Resource Group ** -----------------------------------------------------------------Service IP Label ---------------aixserver1 Domain Name ----------- -----------------------------------------------------------------e: Edit Configuration 4. To perform other deployment operations. 64 2011-08-18 .6 WDeploy WDeploy is installed as a part of SAP BusinessObjects Enterprise to aid in the deployment of web applications to Java-based web application servers. a repository might not get updated to use the configured Service IP Label if the associated database is unavailable. When you finish configuration. and reschedule batch jobs. 5. Y Manually resynchronizes all repositories. 6. such as deploying one web component at a time. The WDeploy tool provides a graphical method of running the wdeploy deployall or wdeploy undeployall commands. Command Description y: Re-sync all repos q: Quit E Specifies the Service IP Label used while configuring the SAP BusinessObjects Data Services resource group. This means: • The Job Service must be stopped prior to editing the configuration. use the command-line version of WDeploy. you can use this option to resynchronize the repository. Enter q and then x to exit the Server Manager. Note: Resynchronizing all repositories is not required unless you see an error message after editing the configuration. • You must re-add repository connections to the Management Console. the software resynchronizes all repositories and the configurations for the SNMP agent with the current Service IP Label and domain name. After correcting the problem. reconfigure real-time services and adapters. For example. Configure HACMP.

1 WDeploy prerequisites To use the WDeploy GUI tool. manually update the as_profile_name parameter in the config.6. 4.websphereX configuration file before launching the WDeploy GUI tool. but prompts the user to choose a language if any language packs are installed and the tool is run for the first time. Select “WebSphere 6” or “WebSphere 7” and provide all parameters. Update as_profile_name in config.websphereX. 2. 3. The following language packs are supported: • Czech • Simplified Chinese • Traditional Chinese • Danish • Dutch • English • Finnish • French • German • Italian • Japanese • Korean • Norwegian Bokmal • Polish • Portuguese • Russian • Spanish • Swedish • Thai Related Topics • WDeploy prerequisites • To run WDeploy from the command line 6. ensure that the following requirements are met: • When using WebSphere 6 or WebSphere 7 with a non-default profile name (a profile name that isn't set to AppSrv01). 65 2011-08-18 .Additional Information The WDeploy GUI defaults to an English interface. Perform the deployment. For example: 1. Launch the WDeploy GUI tool.

ensure that the maximum heap size is at least 2048 megabytes: JAVA_OPTS=-Xms128m -Xmx2048m -XX:MaxPermSize=512 • Set the PERL_HOME environment variable. ensure that the following modules are also installed: • Text::CharWidth Gets the number of occupied columns of a string on terminal.engine/perl. see WebSphere 6 or 7 configuration file. fullwidth. It is recommended that you use the version of Perl installed with SAP BusinessObjects Enterprise. Ensure that the host web application server minimum heap size (-Xms). ensure that there is at least 5 GB available on the drive defined in the TEMP environment variable. For example: JAVA_OPTS=-Xms128m -Xmx1024m -XX:MaxPermSize=512 Note: For SAP NetWeaver AS 7. When using SAP NetWeaver AS Java 7. • • • Ensure that the web application server host system has at least 15 GB of free hard disk space before attempting to deploy web applications. ensure that the host system has at least 8 GB of RAM. see the CharWidth.8.org. To use your own version of Perl 5. JAVA_HOME may be set to: <BIP_INSTALL_DIR>/sap_bobj/enterprise_xi40/java Or: <BIP_INSTALL_DIR>/sap_bobj/enterprise_xi40/<PLATFORM>64_x64/jdk • Ensure that the host system has at least 5 GB of free space for the deployment of web applications.pm article at http://search. • Set the JAVA_HOME environment variable to the desired JDK folder.cpan. set PERL_HOME to <BIP_INSTALL_DIR>/Install Data/setup. and combining characters and languages without whitespaces between words. For example.2.cpan. 66 2011-08-18 . and Permanent Generation (-XX:MaxPermSize) settings are configured.8. For example. Ensure that the host system has at least 4 GB of RAM. For more information.9 installed. For more information. see the WrapI18N.2. maximum heap size (-Xmx).pm article at http://search.org.Additional Information For information on giving the profile name with the WDeploy command-line tool. If you do not already have Perl 5.9. • Text::WrapI18N Line wrapping module with support for multibyte.

ensure that the WDeploy web application server configuration file (config.3 To deploy or undeploy components The WDeploy GUI tool allows users to deploy and undeploy all web applications to a web application server.6.4 Advanced options The WDeploy GUI tool Options screen allows you to select custom folders to use for the deployment of web applications. 67 2011-08-18 . Select a language and continue. 1.2 To start WDeploy The WDeploy GUI tool is located in the folder <BIP_INSTALL_DIR>/sap_bobj/enter prise_xi40/wdeploy. The syntax of the WDeploy command is: . 4.Additional Information 6.6. 6. 6. Web applications that are not deployed automatically must be deployed with the WDeploy command-line tool or with the web application server administrative console. Select one of the following actions: • Deploy all available SAP BusinessObjects Web Applications to the server • Undeploy all available SAP BusinessObjects Web Applications from the server 2. When a web application server is selected. it prompts for which language to use for displaying information in the user interface. 3. select Options.6. Any web applications not deployed by the SAP BusinessObjects Enterprise installation program or WDeploy tool will be unaffected.sh When the WDeploy GUI tool is run for the first time. Before deploying or undeploying web applications to a web application server. Note: Not all web applications are deployed automatically. Select a supported web application server from the Select Web Application Server Type drop-down. For more advanced options. review the information in the "Web Application Server Information" section and the "Application Server Domain Root Directory" section to ensure that it is correct for your web application server./wdeployGUI.<WEB_APP_SERVER>) is correctly configured.

5 To run WDeploy from the command line 68 2011-08-18 . This folder stores the results of the wdeploy predeploy action. and stores data required to undeploy web applications. to split static and dynamic content in a web application). Example value: <BIP_INSTALL_DIR>/sap_bobj/enter prise_xi40/wdeploy/workdir The location of source used to create WAR or EAR Select Source location of web applications: Example value: Web application source tree location <BIP_INSTALL_DIR>/sap_bobj/enter prise_xi40/warfiles/webapps The location of source content used to create the generic WAR files. Web applications root context Example value: /BOE Note: Non-English characters in paths are not valid in the WDeploy GUI tool. 6.6.Additional Information Option Description Select WDeploy work directory Select the folder in which WDeploy manipulates the web applications WAR or EAR archives (for example. Select Source location of web applications: Example value: Generic WAR files location <BIP_INSTALL_DIR>/sap_bobj/enter prise_xi40/java/applications Select the web application root context path to which all web applications are deployed.

sh <server_type> [-Das_admin_password=<password>] [-DAPP=<app_name>] <command> 69 2011-08-18 .Additional Information Use the wdeploy command-line tool to deploy the Data Services web application components to a web application server and perform other advanced deployment functions unavailable in the GUI tool. the wdeploy tool and the web components are installed to the following locations during the. SAP Business Objects Enterprise installation: • wdeploy: <BIP_INSTALL_DIR>/sap_bobj/enterprise_xi40/wdeploy • web components: <BIP_INSTALL_DIR>/sap_bobj/enterprise_xi40/warfiles/webapps Syntax wdeploy. There are several web components available to deploy: • DataServices • Doc • Webservice By default.

• undeployall Removes all web application components from the web application server. Available values for <server_type> include: • • • • • • • sapappsvr72 tomcat55 tomcat6 weblogic9 weblogic10 websphere6 websphere7 -Das_admin_pass word=<password> Specifies the administrator password to use to deploy the application. Available values for <command> include: • deploy Prepares and deploys a single web application component to the web application server. -DAPP=<app_name> Specifies the web application component to deploy. the password is not required. 70 2011-08-18 . • deployall Prepares and deploys all web application components to the web application server. • undeploy Removes a single web application component from the web application server.Additional Information Parameter Description <server_type> Specifies the type of the web application server. Available values for <app_name> include: • • • <command> DataServices doc webservice Specifies the command for wdeploy to execute. Note: For Tomcat web application servers.

tomcat55 • config.sh websphere6 deployall -Das_admin_password=mypass 71 2011-08-18 .6. the configuration files are in stalled to <BIP_INSTALL_DIR>/sap_bobj/enterprise_xi40/wdeploy/conf. For example. Set the parameters to match your application server settings. Doc. and Webservice. Access <BIP_INSTALL_DIR>/sap_bobj/enterprise_xi40/wdeploy from the command prompt. 2.weblogic10 • config.websphere6 • config. Save and close the configuration file.html file located in <LINK_DIR>/ext and change the default port number to match the port number for your web application server.5.sapappsvr72 • config. To deploy all web content: 1.Additional Information 6. the default port number for Tomcat is 8080.5. 3. Open the configuration file for your web application server.websphere7 2.2 To deploy all web components Deploying all web components deploys DataServices. URL=http://hostname:8080/DataServices/"> All web components are deployed to the web application server. Open the DataServices. 6. When you deploy on Tomcat.tomcat6 • config.weblogic9 • config. exclude the -Das_admin_pass word=<password> parameter. Available configuration files include: • config. <META HTTP-EQUIV=Refresh CONTENT="0. 3. Run wdeploy with the deployall command: wdeploy.sh <server_type> deployall -Das_admin_password=<password> Note: Tomcat does not require a password.1 To configure wdeploy To configure the wdeploy configuration file to specify the web application server settings: 1. Example: WebSphere 6 wdeploy.6. By default.

5.6. 6. When you deploy on Tomcat.5.Additional Information Note: After you deploy the web applications on Tomcat. Access <BIP_INSTALL_DIR>/sap_bobj/enterprise_xi40/wdeploy from the command prompt.4 To verify deployment To verify the deployment was performed properly: 1. Run wdeploy with the deploy command and the -DAPP=<app_name> parameter: wdeploy. 2.6. 6.3 To deploy one web component To deploy a single web application component: 1. you must restart the Tomcat application server for the changes to take effect.sh weblogic10 -Das_admin_password=mypass -DAPP=DataServices deploy Note: After you deploy the web application on Tomcat. exclude the -Das_admin_pass word=<password> parameter. Check whether the web applications have been deployed to the correct location.sh <server_type> -Das_admin_password=<password> -DAPP=<app_name> deploy Note: Tomcat does not require a password. The specified web component is deployed to the web application server Example: DataServices on WebLogic 10 wdeploy. • On Tomcat: $CATALINA_HOME/webapps • On WebSphere: <server_folder>/installedApps/<Node_Cell_folder> 72 2011-08-18 . you must restart the Tomcat application server for the changes to take effect.

Additional Information

For example, C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\in stalledApps\SHG-D-01-CGAONode01Cell • On WebLogic: <server_folder>/stage/ For example, C:\bea\wlserver_10.0\samples\domains\wl_server\servers\examp lesServer\stage 2. Log in to the Management Console, add a repository, and click on each of the modules. Each module should display correctly. 3. (Optional) Verify that you can add a web service successfully. 4. Click About to verify that the version is up-to-date.

6.6.5.5 To undeploy all web components
Undeploying all web components undeploys DataServices, Doc, Webservice. To undeploy all web components: 1. Access <BIP_INSTALL_DIR>/sap_bobj/enterprise_xi40/wdeploy from the command prompt. 2. Run wdeploy with the undeployall command: wdeploy.sh <server_type> undeployall -Das_admin_password=<password> Note: Tomcat does not require a password. When you deploy on Tomcat, exclude the -Das_admin_pass word=<password> parameter. All web components are removed from the web application server. Example: WebSphere 6 wdeploy.sh websphere6 undeployall -Das_admin_password=mypass Note: After you undeploy the web applications on Tomcat, you must restart the Tomcat application server for the changes to take effect.

6.6.5.6 To undeploy one web component

73

2011-08-18

Additional Information

To undeploy a single web component: 1. Access <BIP_INSTALL_DIR>/sap_bobj/enterprise_xi40/wdeploy from the command prompt. 2. Run wdeploy with the undeploy command and the -DAPP=<app_name> parameter: wdeploy.sh <server_type> -Das_admin_password=<password> -DAPP=<app_name> undeploy Note: Tomcat does not require a password. When you deploy on Tomcat, exclude the -Das_admin_pass word=<password> parameter. The specified web component is removed from the web application server. Example: DataServices.war on WebLogic 10 wdeploy.sh weblogic10 -Das_admin_password=mypass -DAPP=DataServices undeploy Note: After you undeploy the web application on Tomcat, you must restart the Tomcat application server for the changes to take effect.

6.6.6 To deploy web applications in a distributed environment
In a distributed deployment where the Data Services web applications are deployed to a different system than the Central Management Server (CMS), a broken link may appear in a Central Management Console (CMC) that resides on the same host system as the CMS. For example, consider the following deployment:
Host A Host B

BI platform Central Management Server (CMS) BI platform web tier Data Services InfoObjects

BI platform web tier Data Services web applications

To manually deploy the Data Services web application and repair the broken link on Host A: 1. Copy the BOE directory from Host B to Host A. By default, the BOE directory is located in <BIP_INSTALL_DIR>/warfiles/webapps/. 2. Use wdeploy to deploy the BOE web application on Host A: • Deploy all SAP BusinessObjects web applications from the command-line or GUI.

74

2011-08-18

Additional Information

Or • Deploy only the BOE web application from the command-line.

Related Topics • WDeploy • To deploy all web components • To deploy one web component

75

2011-08-18

Additional Information 76 2011-08-18 .

S.S.Index $LINK_DIR 12 A Access Server configuring 48 account permissions 17 adding cleansing packages 54 directories (continued) update schedule 57 directory data 56 J Job Server configuration 49 configuring 48 high availability support for batch jobs 61 E environment variables $LINK_DIR 12 B Batch jobs high availability support on AIX 62 F firewall ports 18 L LINK_DIR 12 C cleansing packages adding 54 deleting 55 editing 54 installation 53 modifying 54 removing 54. 35 response file example 42 silent 36 software removal 50 installation program to run 29 introduction 7 P permissions network 18 planning your installation 15 port assignments 18 post-installation 47 D database requirements DB2 26 MySQL 27 Oracle 27 Sybase 27 deleting cleansing packages 54. 34 errors 49 feature codes 41 installation program 29 methods 29 parameters 36 preparation for 25 repsonse file 33 response file 34. 55 uninstalling 55 command-line installation 33 installation program parameters 34 configuring Job Servers 49 cron 17 G groups configuring 47 M modifying cleansing packages 54 H High Availability Clustered Multi Processing (HACMP) configuring for 63 support for on AIX 61 using 62 N naming conventions terminology 12 variables 12 network permissions 18 I INSTALL_DIR 12 installation cleansing packages 53 command-line 33. directory expiration 58 U. National and Auxiliary files 59 R remove software 50 removing cleansing packages 55 repositories configuring 47 repository troubleshooting 49 repository database preparing 25 requirements 25 requirements account permissions 17 77 2011-08-18 . 55 directories downloading 60 extracting 61 installing Download Manager 60 list 57 location 59 non-default location 59 U.

Index requirements (continued) Central Management Server (CMS) 20 database server 21 DB2 26 kernel parameters 22 MySQL 27 Oracle 27 software 16 Sybase 27 system 16 system locale 16 user resource limits 22 response file 34. 71 deploying one component 72 gui tool 64 gui tool advanced options 67 prerequisites 65 run gui tool 67 start gui tool 67 syntax 68 undeploying all components 67. 35 example 42 feature codes 41 parameters 36 T troubleshooting Windows 7 50 Windows Server 2008 50 Windows Vista 50 W wdeploy configuring 71 deploying all components 67. 73 undeploying one component 73 verifying deployment 72 web applications deploying with wdeploy gui tool 64 web application server 21 web applications deploying after installation 49 deploying with wdeploy command-line tool 68 U uninstallation 50 uninstalling cleansing packages 55 user requirements 17 user resource limits AIX 22 Linux 23 Solaris 22 users configuring 47 S system requirements 16 system variables LINK_DIR 12 78 2011-08-18 .