You are on page 1of 110

Installation Guide for Windows SAP BusinessObjects Information Steward 4.

0 Support Package 01

2011-08-19

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-19

Contents

Chapter 1

Getting Started........................................................................................................................7 Welcome.................................................................................................................................7 Documentation set for SAP BusinessObjects Information Steward..........................................7 Accessing documentation........................................................................................................8 SAP BusinessObjects information resources ..........................................................................8 Architecture...........................................................................................................................11 Architecture overview............................................................................................................11 Servers and services..............................................................................................................12 Information Steward on Business Intelligence platform components.......................................19 Information workflows............................................................................................................22 Adding a table to a Data Insight project..................................................................................22 Profiling data .........................................................................................................................23 Scheduling and running a Metadata Management integrator source.......................................23 Creating a custom cleansing package with Cleansing Package Builder...................................24 Deployment...........................................................................................................................27 Planning your Information Steward deployment......................................................................27 Information Steward components...........................................................................................28 Component installation prerequisites......................................................................................29 Component run-time dependencies........................................................................................30 Component installation results...............................................................................................33 Deployment guidelines...........................................................................................................34 General deployment guidelines..............................................................................................35 Data Insight deployment guidelines for profile and rule tasks..................................................35 Metadata Management deployment guidelines.......................................................................36 Cleansing Package Builder deployment guidelines.................................................................37 Deployment checklist.............................................................................................................37 Deployment scenarios............................................................................................................38 Scenario 1: Single machine deployment.................................................................................40 Scenario 2: Scaling Data Insight servers................................................................................42 Scenario 3: Scaling for Metadata Management......................................................................43

1.1 1.2 1.3 1.4


Chapter 2

2.1 2.1.1 2.2 2.3 2.3.1 2.3.2 2.3.3 2.3.4


Chapter 3

3.1 3.2 3.2.1 3.2.2 3.2.3 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.4 3.5 3.5.1 3.5.2 3.5.3

2011-08-19

Contents

3.5.4 3.5.5 3.5.6 3.5.7


Chapter 4

Scenario 4: Scaling for Cleansing Package Builder ................................................................45 Scenario 5: Scaling servers for web application users............................................................48 Scenario 6: High availability....................................................................................................49 Scenario 7: Mixed operating systems....................................................................................52 Preparation............................................................................................................................57 Requirements.........................................................................................................................57 System requirements.............................................................................................................58 Software dependencies..........................................................................................................58 Verifying prerequisite software...............................................................................................59 Account permissions..............................................................................................................59 Network requirements............................................................................................................60 Repository database requirements and preparation................................................................60 Requirements for database types...........................................................................................61 Extra requirements for Oracle.................................................................................................63 Setting up a new database.....................................................................................................63 Support for SAP System Landscape Directory (SLD)............................................................63 Installation scenarios..............................................................................................................64 License keys..........................................................................................................................64 Installation.............................................................................................................................67 Standard installation...............................................................................................................67 When installation is complete.................................................................................................71 Silent installation....................................................................................................................71 Command-line switch parameters..........................................................................................72 Installation option parameters.................................................................................................75 Post-Installation....................................................................................................................83 Configuring a Data Services Job Server for Data Insight........................................................83 Updating the license key........................................................................................................84 Deploying web applications with WDeploy.............................................................................84 WDeploy prerequisites...........................................................................................................84 To start WDeploy...................................................................................................................85 To deploy or undeploy components........................................................................................86 Advanced options..................................................................................................................86 To run WDeploy from the command line................................................................................87 Troubleshooting.....................................................................................................................93 Verifying Information Steward servers are running.................................................................94 Verifying Information Steward services .................................................................................94 Verifying Data Insight installation............................................................................................96

4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.2 4.2.1 4.2.2 4.2.3 4.3 4.4 4.5
Chapter 5

5.1 5.1.1 5.2 5.2.1 5.2.2


Chapter 6

6.1 6.2 6.3 6.3.1 6.3.2 6.3.3 6.3.4 6.3.5 6.3.6 6.4 6.5 6.6

2011-08-19

Contents

6.7 6.8 6.9 6.10 6.11 6.12 6.13 6.14


Chapter 7

Verifying Metadata Management installation..........................................................................96 Installing SAP-supplied cleansing packages............................................................................96 Modifying cleansing packages ...............................................................................................98 Uninstalling cleansing packages ............................................................................................99 Metadata Integrator server groups.......................................................................................100 Restarting Enterprise Information Management Servers.......................................................100 Uninstalling Information Steward..........................................................................................100 Uninstalling specific components.........................................................................................101 Additional installation scenarios.........................................................................................103 Remote Job Server Installation............................................................................................103 To install a Remote Job Server............................................................................................103 To modify the configuration of a Remote Job Service..........................................................104 107

7.1 7.1.1 7.1.2


Index

2011-08-19

Contents

2011-08-19

Getting Started

Getting Started

1.1 Welcome
SAP BusinessObjects Information Steward provides business users and IT users with a single environment to discover, assess, define, monitor and imiprove the quality of their enterprise data asset. Through the Data Insight module of Information Steward, business analysts and data stewards can profile their data, create and run validation rules, and monitor data quality through score cards. Through the Metadata Management module, business analysts and data stewards can catalog their data and understand the relationships of their enterprise data. Through the Metapedia module, data stewards can define business terms for your data and organize the terms into categories. Through the Cleansing Package Builder module, data stewards can define cleansing packages to parse and standardize data.

1.2 Documentation set for SAP BusinessObjects Information Steward


You should become familiar with all the pieces of documentation that relate to your SAP BusinessObjects Information Steward product.
Document What this document provides

Administrator Guide

Information about administrative tasks such as monitoring, lifecycle management, security, and so on. An overview of SAP BusinessObjects Information Steward, its components, required components from SAP BusinessObjects Intelligence platform service and SAP BusinessObjects Data Services, and its deployment scenarios. This guide refers to detailed documentation in installation and administration guides. Information about architecture, setting up the application to optimize the performance and procedures for installing SAP BusinessObjects Information Steward in a Windows environment.

Master Guide

Installation Guide for Windows

2011-08-19

Getting Started

Document

What this document provides

Installation Guide for UNIX

Information about architecture, setting up the application to optimize the performance and procedures for installing SAP BusinessObjects Information Steward in a UNIX environment. Important information you need before installing and deploying this version of SAP BusinessObjects Information Steward. Release-specific product behavior changes from earlier versions of SAP BusinessObjects Information Steward to the latest release. This guide also contains information about how to upgrade from SAP BusinessObjects Metadata Management to SAP BusinessObjects Information Steward. Conceptual information and procedures about how to use SAP BusinessObjects Information Steward. Highlights of new key features in this SAP BusinessObjects Information Steward release. This document is not updated for support package or patch releases.

Release Notes

Upgrade Guide

User Guide

What's New

1.3 Accessing documentation


You can access the complete documentation set for SAP BusinessObjects Information Steward in several places. After you install the application, you can access the documentation from the Start menu on Windows or the root drive on UNIX. The most up-to-date documentation is available on SAP BusinessObjects Business Users Support site. 1. Go to http://help.sap.com. 2. Click SAP BusinessObjects at the top of the page. 3. Click All Products in the navigation pane on the left. You can read PDF files online or save them to your computer using the latest version of Adobe Acrobat Reader.

1.4 SAP BusinessObjects information resources


A global network of SAP BusinessObjects technology experts provides customer support, education, and consulting to ensure maximum information management benefit to your business.

2011-08-19

Getting Started

Useful addresses at a glance:


Address Content

Customer Support, Consulting, and Education services http://service.sap.com/

Information about SAP Business User Support programs, as well as links to technical articles, downloads, and online forums. Consulting services can provide you with information about how SAP BusinessObjects can help maximize your information management investment. Education services can provide information about training options and modules. From traditional classroom learning to targeted e-learning seminars, SAP BusinessObjects can offer a training package to suit your learning needs and preferred learning style. Search the SAP BusinessObjects forums on the SAP Community Network to learn from other SAP BusinessObjects users and start posting questions or share your knowledge with the community. SAP BusinessObjects product documentation.

Forums on SCN (SAP Community Network ) http://forums.sdn.sap.com/forum.jspa?foru mID=305 Product documentation http://help.sap.com/businessobjects/

Supported Platforms (Product Availability Matrix) https://service.sap.com/PAM

Get information about supported platforms for SAP BusinessObjects Information Steward. Use the search function to search for Information Steward.

2011-08-19

Getting Started

10

2011-08-19

Architecture

Architecture

SAP BusinessObjects Information Steward runs on the SAP BusinessObjects Business Intelligence platform (previously known as SAP BusinessObjects Enterprise) which is designed for high performance across a broad spectrum of user and deployment scenarios. You can offload processor intensive scheduling and processing to dedicated servers to improve performance. The architecture is designed to meet the needs of virtually any business intelligence (BI) deployment. This section describes how the components of SAP BusinessObjects Information Steward fit into the overall architecture and individual services and components that make up SAP Business Intelligence platform . This information will help administrators understand how to plan the deployment, management, and maintenance of the metadata management application. Related Topics Architecture overview Information Steward on Business Intelligence platform components Information workflows

2.1 Architecture overview


Information Steward uses SAP BusinessObjects Business Intelligence platform for managing user security, scheduling integrator sources as tasks and utilities, managing sources, and on demand services. Information Steward uses Data Services for profiling, rule tasks, browsing metadata, and viewing data. The following diagram shows the architectural components for SAP BusinessObjects Business Intelligence platform, SAP BusinessObjects Data Services, and SAP BusinessObjects Information Steward. Note: The diagram shows only the servers and services in the Business Intelligence platform and Data Services relevant to Information Steward.

11

2011-08-19

Architecture

Related Topics Servers and services Data Services Job Server Web Application Server

2.1.1 Servers and services


SAP BusinessObjects Business Intelligence platform (BI platform) uses the terms server and service to refer to the two types of software running on an Information platform services machine. The term server is used to describe an operating system level process (on some systems, this is referred to as a daemon) hosting one or more services. For example, the Enterprise Information Management Adaptive Processing Server and Information Steward Job Server are servers. A server runs under a specific operating system account and has its own PID. A service is a server subsystem that performs a specific function. The service runs within the memory space of its server under the process id of the parent container (server). For example, the Information StewardTask Scheduling Service is a subsystem that runs within the Information Steward Job Server.

12

2011-08-19

Architecture

A node is a collection of BI platform servers running on the same host. One or more nodes can be on a single host. Information platform services can be installed on a single machine, spread across different machines on an intranet, or separated over a wide area network (WAN).

2.1.1.1 Data Services Job Server


The Job Server component of SAP BusinessObjects Data Services is required for the following reasons: The Data Services Job Server must already be installed on this computer because it provides the following system management tools that are required during the first installation of Information Steward: Repository Manager The Repository Manager creates the required Data Insight objects in the Information Steward repository. The Information Steward installer invokes the Repository Manager automatically when creating the repository the first time the installer is run. Server Manager The Server Manager creates the Information Steward job server group and job servers and associates them to the Information Steward repository. To add job servers to the Information Steward job server group, you must manually invoke the Server Manager. For details, see Adding a job server for Data Insight in the Installation Guide. The Data Services Job Server provides the engine processes that perform the Data Insight profiling and rule tasks. The engine processes use parallel execution and in-memory processing to deliver high data throughput and scalability.

Note: When you installed Data Services, ensure that you selected Job Server under the Server component in the "Select Feature" window of the Data Services installer. In addition, ensure that MDS and VDS are selected during the Data Services installation. These two options are selected by default.

2.1.1.2 Web Application Server


SAP BusinessObjects Information Steward is deployed on: The Central Management Console (CMC) through which you perform administrative tasks for Information Steward A web application server through which you access the Information Steward modules:

13

2011-08-19

Architecture

Data Insight Metadata Management Metapedia Cleansing Package Builder

Note: The Information Steward web application must be installed on the same web application server as that of the SAP BusinessObjects Business Intelligence platform. For specific version compatibility, refer to the Product Availability Matrix available at http://ser vice.sap.com/PAM.

2.1.1.2.1 Administration
You use the Central Management Console (CMC) to perform SAP BusinessObjects Information Steward administrative tasks such as the following: Define Data Insight connections and projects Configure and run metadata integrators Define source groups to subset the metadata when viewing relationships such as Same As, Impact, and Lineage Administer user security for the modules of Information Steward: Data Insight, Metadata Management, and Cleansing Package Builder Configure application settings that affect the behavior and performance of Data Insight profile and rule tasks Schedule Data Insight profile and rule tasks Run or schedule Information Steward utilities

For more information, see the SAP BusinessObjects Information Steward Administrator Guide.

2.1.1.2.2 SAP BusinessObjects Information Steward web application


The SAP BusinessObjects Information Steward is a web-based interface through which users of each module can perform tasks to analyze data and its metadata. Data Insight users can perform tasks such as: Profile data in tables or files and analyze the resulting profile attributes Define rules and set up data quality scorecards View data quality score trend and view sample data that failed each rule View data quality impact on dependent data sources Metadata Management users can perform tasks such as: View metadata from different sources and search for objects without the need to know the source or application in which it exists Add annotations to an object and define custom attributes and values for an object Run pre-defined reports that answer typical business questions such as "Which Universe objects are not used in my reports?" or "Which reports are using my tables?" View impact and lineage of objects within the same source or within different sources.

14

2011-08-19

Architecture

Impact analysis - Allows you to identify which objects will be affected if you change or remove other connected objects. Lineage analysis - Allows you to trace back from a target object to the source object.

Metapedia can perform tasks such as: Define Metapedia terms related to your business data and organize the terms into categories. Cleansing Package Builder can perform tasks such as: Define cleansing packages to parse and standardize data Publish a cleansing package and export it to SAP BusinessObjects Data Services where users can import it to generate a base Data Cleanse transform that can be included in jobs to cleanse your data

For more information, see the SAP BusinessObjects Information Steward User Guide.

2.1.1.3 Metadata integrators


Metadata integrators are programs that do the following: Collect metadata from source systems and store the collected metadata into the SAP BusinessObjects Information Steward repository. Can be scheduled to run at regular intervals. Update the existing metadata. Can run on one job server or multiple job servers for load balancing and high availability. Each run as a separate process. SAP BusinessObjects Information Steward provides the following metadata integrators:
Metadata integrator name Metadata collected

SAP BusinessObjects Enterprise Metadata Integrator

Collects metadata about objects such as universes, Crystal Reports, Web Intelligence documents, and Desktop Intelligence documents. Collects metadata about objects such as Queries, InfoProviders, InfoObjects, Transformations, and DataSources from an SAP NetWeaver Business Warehouse system. Collects metadata about objects such as catalogs, schemas, and tables from the CWM Relational Package. Collects metadata about objects such as projects, catalogs, data sources, and mapping rules from a Data Federator repository.

SAP NetWeaver Business Warehouse Metadata Integrator

Common Warehouse Model (CWM) Metadata Integrator SAP BusinessObjects Data Federator Metadata Integrator

15

2011-08-19

Architecture

Metadata integrator name

Metadata collected

SAP BusinessObjects Data Services Metadata Integrator

Collects metadata about objects such as source tables, target tables, and column mappings from a Data Services repository. Collects metadata from other third-party sources such as the following: Data Modeling metadata such as Sybase Power Designer, Embarcadero ER/Studio, and Oracle Designer Extract, Transform, and Load (ETL) metadata such as Oracle Warehouse Builder and Microsoft SQL Server Integration Services (SSIS) OLAP and BI metadata such as IBM DB2 Cube Views, Oracle OLAP, and Cognos BI Reporting Collects metadata from relational database management systems (RDBMS) which can be DB2, MySQL, Oracle, SQL Server, Java Database Connectivity (JDBC), or a BusinessObjects Universe connection. Collected metadata includes the definition of objects such as tables, view, synonyms, and aliases.

Meta Integration Metadata Bridge (MIMB) Metadata Integrator (also known as MITI Integrator)

Relational databases Metadata Integrator

You can also obtain third-party metadata integrators for other data sources. For more information about third-party metadata integrators, see http://www.metaintegration.net/Products/MIMB/SupportedTools.html. Related Topics User Guide: section "SAP BusinessObjects Enterprise metadata objects" User Guide: SAP NetWeaver Business Warehouse metadata objects User Guide: section Metadata displayed for Data Services User Guide: section Metadata displayed for Data Federator User Guide: section BusinessObjects Data Services objects http://www.metaintegration.net/Products/MIMB/SupportedTools.html http://www.metaintegration.net/Products/MIMB/Documentation/ Deployment scenarios

2.1.1.4 Services

16

2011-08-19

Architecture

The following table describes each of the services that are pertinent to SAP BusinessObjects Information Steward.

Table 2-2: Services pertinent to Information Steward


Part of server that service runs on

Service

Service description

Deployment comments

Cleansing Package Builder Auto-analysis Service

Enterprise Information Management Adaptive Processing Server

Performs the data analysis when you create a custom cleansing package in Cleansing Package Builder. The data analysis uses the information the user provides in the custom cleansing package wizard, along with statistical analysis, to create an abstract version of the records. The abstracted records are then grouped, and each group is processed with data inference algorithms to create the suggestions that the user sees in Design mode of Cleansing Package Builder. Performs all the main functionality of Cleansing Package Builder, such as creating and opening cleansing packages, Design mode, and Advanced Mode. Converts a published cleansing package to the reference data format used by Data Services. This process can take a significant period of time for large cleansing packages. Performs tasks on Data Services such as test rule, delete objects (connection, datastore, workflow) from Data Services, export rules to Data Services.

An Adaptive Processing Server of SAP BusinessObjects Business Intelligence platform must already be installed on this computer.

Cleansing Package Builder Core Service Cleansing Package Builder Publishing Service Information Steward Administrator Task Service

Enterprise Information Management Adaptive Processing Server Enterprise Information Management Adaptive Processing Server Enterprise Information Management Adaptive Processing Server

An Adaptive Processing Server of SAP BusinessObjects Business Intelligence platform must already be installed on this computer. An Adaptive Processing Server of SAP BusinessObjects Business Intelligence platform must already be installed on this computer.

An Adaptive Processing Server of SAP BusinessObjects Business Intelligence platform must already be installed on this computer.

17

2011-08-19

Architecture

Service

Part of server that service runs on

Service description

Deployment comments

Data Service Metadata Browsing Service

Enterprise Information Management Adaptive Processing Server

Provides Data Insight users the capability to browse and import metadata from different data sources. Data sources include relational database systems (such as Oracle and Microsoft SQL Server) , and Applications (such as, SAP ECC and Oracle Applications).

The Data Services Metadata Browsing Service is a component of SAP BusinessObjects Data Services which must already be installed on this computer. An Adaptive Processing Server of SAP BusinessObjects Business Intelligence platform must already be installed on this computer. The Data Services View Data Service is a component of SAP BusinessObjects Data Services which must already be installed on this computer. An Adaptive Processing Server of SAP BusinessObjects Business Intelligence platform must already be installed on this computer. It is recommended that you install the Metadata Relationship Service on a different computer than the web application server. An Adaptive Processing Server of SAP Business Intelligence Platform must already be installed on that computer. You can deploy multiple Metadata Relationship Services for load balancing and availability.

Data Services View Data Service

Enterprise Information Management Adaptive Processing Server

Provides the capability to view the external data in Data Insight connections in Information Steward.

Information Steward Metadata Relationship Service

Enterprise Information Management Adaptive Processing Server

Computes metadata object relationships (such as data lineage and change impact analysis). The Metadata Management module of Information Steward uses the results of these computed relationships to display metadata relationship diagrams.

18

2011-08-19

Architecture

Service

Part of server that service runs on

Service description

Deployment comments

Information Steward Metadata Search Service

Allows you to find an object that exists in any integrator source while viewing metadata on the Metadata Management module of Information Steward. It uses the Lucene Search Engine. Enterprise Information Management Adaptive Processing Server The Metadata Search Service constructs the search index during the execution of the Metadata Integrators, and the File Repository Server stores the compressed search index. The Metadata Search Service also updates the search index for changes to Metapedia terms and categories, custom attributes, and annotations.

You can deploy multiple search services for load balancing and availability. If the Metadata Search Service is not available during the construction and update processes, the search might return incorrect results. For these situations, Information Steward provides a utility to reconstruct the search index. For details, see Recreating search indexes on Metadata Management in the Administrator Guide.

Information Steward Task Scheduling Service Information Steward Integrator Scheduling Service Information Steward Integrator Service

Information Steward Job Server

Processes scheduled Data Insight profile and rule tasks in the Central Management Console (CMC).

An Adaptive Job Server of SAP BusinessObjects Business Intelligence platform must already be installed on this computer.

Information Steward Job Server

Processes scheduled Metadata Management integrator sources in the Central Management Console (CMC).

An Adaptive Job Server of SAP BusinessObjects Business Intelligence platform must already be installed on this computer.

Enterprise Information Management Adaptive Processing Server

Helper service that is used for testing connections to integrator sources.

It is installed with the integrators.

2.2 Information Steward on Business Intelligence platform components

19

2011-08-19

Architecture

The following table describes how SAP BusinessObjects Information Steward uses each pertinent SAP BusinessObjects Business Intelligence platform (BI platform) component.
BI platform component How SAP BusinessObjects Information Steward uses component

Web Application Server

Deploys Information Steward on: The Central Management Console (CMC) through which administrative tasks for Information Steward are performed A web application server through which you access the Information Steward modules: Data Insight Metadata Management Metapedia Cleansing Package Builder Manages the following for SAP BusinessObjects Information Steward Enterprise Information Management Adaptive Processing Server (EIMAdaptiveProcessingServer) and services Information Steward Job Server (ISJobServer) and services Manage Metadata Management module: Integrator source configurations Source group configurations

Central Management Console (CMC)

Manage Data Insight module: Connections Projects Profile and rule tasks Manage Cleansing Package Builder module: Cleansing package owner Information Steward utilities User security (authentication and authorization) Manage repository and application settings

20

2011-08-19

Architecture

BI platform component

How SAP BusinessObjects Information Steward uses component

Maintains a database of information about your BI platform system. The data stored by the CMS includes information about users and groups, security levels, schedule information, BI platform content, and servers. For more information about the CMS, see SAP BusinessObjects Business Intelligence Platform Administrator's Guide. The following objects in the Metadata Management module of Information Steward are stored in the CMS. Integrator Source configurations Source groups Utilities configurations Data Insight connections Projects Tasks Note: Because integrator source configurations and source group definitions are stored in the CMS, you can use the Upgrade management tool to move them from one version of the CMS to another. The schedules and rights information are considered dependencies of these configurations. For details, see the Upgrade Guide and the Lifecycle Management section in the Administrator Guide.

Central Management Server (CMS)

Information Steward Job Server uses the Adaptive Job Server for executing profiling tasks and integrator tasks. Adaptive Job Server The server may host the following services for Information Steward: Information Steward Task Scheduling Service Information Steward Integrator Scheduling Service Required during Information Steward installation to create the Enterprise Information Management Adaptive Processing Server. The EIM Adaptive Processing Server uses BIP adaptive processing server to host the following services: Metadata Relationship Service Metadata Search Service Metadata Integrator Service Data Services Metadata Browsing Service Data Services View Data Service Information Steward Administrator Task Service Cleansing Package Builder Core Service Cleansing Package Builder Auto-analysis Service Cleansing Package Builder Publishing Service

Adaptive Processing Server

21

2011-08-19

Architecture

BI platform component

How SAP BusinessObjects Information Steward uses component

File Repository Server

Stores files associated with: A published cleansing package. The stored information can be accessed by Data Services History logs for Data Insight task and metadata integrator execution Search index for metadata integrator objects

2.3 Information workflows


When tasks are performed in SAP BusinessObjects Information Steward, such as adding a table to a Data Insight project, running a Metadata Management integrator source, or creating a cleansing package, information flows through SAP BusinessObjects intelligence platform services, SAP BusinessObjects Data Services, and SAP BusinessObjects Information Steward. The servers and services within each of these software products communicate with each other to accomplish a task. For an overview of the servers and services, see Architecture overview. The following section describes some of the process flows as they would happen in SAP BusinessObjects intelligence platform services, SAP BusinessObjects Data Services, and SAP BusinessObjects Information Steward.

2.3.1 Adding a table to a Data Insight project


This workflow describes the process of adding a table to a Data Insight project. 1. The user selects the Add > Tables on "Workspace Home" in the Data Insight tab to access the "Browse Metadata" window. 2. The web application server passes the request to the Central Management Server (CMS) and returns a list of connections that the user can view assuming the user has appropriate permissions to view the connections. 3. If the user has the appropriate rights to view the selected connection, the CMS sends the request to the Data Services Metadata Browsing Service. 4. The Data Services Metadata Browsing Service obtains the metadata from the connection and sends the metadata to the web application server. 5. The web application server displays the metadata in the Data Insight "Browse Metadata" window. 6. When the user selects a table and clicks Add to Project, the web application stores the metadata in the Information Steward repository.

22

2011-08-19

Architecture

2.3.2 Profiling data


This workflow describes the process of running a profile task in Data Insight. Running validation rules are similar to the steps here. 1. The user selects the name of a table or file on "Workspace Home" in the Data Insight tab and clicks Profile. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. Choose the tables in the "Workspace home" of the Data Insight tab. Save the task and schedule to run it. The web application server passes the request to the Central Management Server (CMS). The Information Steward web application determines from the CMS system if the user has the right to run profile tasks on the connection that contains the table or file. The administrator determines if the user has the right to create a profile task for the connection, and has the right to schedule the task. If so, the task is scheduled in the CMS system. When the scheduled time arrives, the CMS sends the task information to the Information Steward Task Scheduling Service. The Information Steward Task Scheduling Service sends the profile task to the Data Services Job Server. The Data Services Job Server partitions the profile task based on the performance application settings. The Data Services Job Server executes the profile task and stores the results in the Information Steward repository. The web application server displays the profile results in the Data Insight "Workspace Home" window.

2.3.3 Scheduling and running a Metadata Management integrator source


This workflow describes the process of scheduling and running a Metadata Management integrator source to collect metadata. 1. The user schedules an integrator source on the Central Management Console (CMC) and the request is sent to the CMS system. 2. The CMS determines if the user has the appropriate rights to schedule the integrator source. 3. If the user has the appropriate rights to schedule the object, the CMS commits the scheduled integrator request to the CMS system. 4. When the scheduled time arrives, the CMS finds a suitable Information Steward Job Server based on the Job Server group associated with the integrator and passes the job. If the process has a SAP BusinessObjects Enterprise 3.x source system, the process contacts the registered remote job server and passes along the integrator process information.

23

2011-08-19

Architecture

5. The integrator process collects metadata and stores the metadata in the Information Steward repository. 6. The integrator process also generates the Metadata Management search index files and loads them to the Input File Repository Server. 7. After uploading the search index files, the integrator source notifies the Metadata Management search service. 8. The Metadata Management search service downloads the generated index files and consolidates them into a master index file. 9. The Information Steward Integrator Scheduling Service updates the CMS with the job status.

2.3.4 Creating a custom cleansing package with Cleansing Package Builder


This workflow describes the process of creating and publishing a custom cleansing package in Cleansing Package Builder. 1. In Information Steward, the user clicks the Cleansing Package Builder tab. 2. The Cleansing Package Builder (CPB) application sends the user's login information to the CPB Web Service. 3. The CPB Web Service sends the information to the Enterprise Information Management (EIM) Adaptive Processing server. The EIM Adaptive Processing Server runs on the Business Intelligence platform. 4. The EIM Adaptive Processing Server determines which rights the user has in CPB. 5. The information is sent back through the CPB Web Service to the CPB application. The user sees the cleansing packages they have the rights to view. 6. In the "Cleansing Packages Tasks" screen, the user selects New Cleansing Package > Custom Cleansing Package to start creating a cleansing package. The user provides the necessary information and sample data to create the cleansing package. 7. The CPB application sends the information through the CPB Web Service to the CPB Core Service, using the BusinessObjects Enterprise SDK mechanism. The CPB Core Service handles the main functions of CPB. The CPB Core Service runs on the EIM Adaptive Processing Server. 8. The CPB Core Service sends the response back through the CPB Web Service to the CPB application. The new cleansing package is created in CPB. 9. The application communicates with the CPB Auto-Analysis Service through the CPB Web Service. The CPB Auto-Analysis Service analyzes the data to create suggestions of standard forms and variations. The CPB Auto-Analysis Service runs on the EIM Adaptive Processing Server. 10. When the user has finished refining the cleansing package, the user clicks Publish on the "Cleansing Packages Tasks" screen. 11. The CPB application communicates with the CPB Publishing Service through the CPB Web Service.

24

2011-08-19

Architecture

The CPB Publishing Service assists in the cleansing package's conversion to the reference data format used by Data Services. The CPB Publishing Service runs on the Enterprise Management Adaptive Processing Server. 12. The published cleansing package information is sent to the Input File Repository, where it is stored and can be accessed by Data Services. The Input File Repository runs on the Business Intelligence platform. 13. Data Services communicates directly with the Business Intelligence platform to sync with the published cleansing packages.

25

2011-08-19

Architecture

26

2011-08-19

Deployment

Deployment

SAP BusinessObjects Information Steward uses SAP BusinessObjects Business Intelligence platform (formerly known as SAP BusinessObjects Enterprise) and SAP BusinessObjects Data Services and inherits the scalable architecture that these two platforms provide. This architecture allows deployment of different server components of Business Intelligence platform, Data Services, and Information Steward on different machines for flexibility, reliability, scalability, and better performance. Server processes can be vertically scaled (where one computer runs several, or all, server-side processes) to reduce cost, or horizontally scaled (where server processes are distributed between two or more networked machines) to improve performance. You can also run duplicate instances of a server process across several networked machines for high availability. For example, you can install multiple Metadata Integrators or web applications on separate computers to distribute the workload and improve performance. For sample deployments, see Deployment scenarios. Related Topics Component installation prerequisites Deployment guidelines Deployment scenarios

3.1 Planning your Information Steward deployment


This section provides guidelines for assessing your organization's needs and suggestions for deployment scenarios. By evaluating your needs before you deploy your SAP BusinessObjects Information Steward system, you can keep troubleshooting to a minimum. The section includes examples and suggestions for deployment, but it is important to note that each deployment is unique. The flexibility of the Business Intelligence platform service-based architecture allows you to tailor the deployment to serve your organization's requirements as precisely as possible. Planning your deployment involves the following steps: 1. Decide which components of Information Steward you want to install and determine the basic software and hardware requirements for them. For more information, see the following: Information Steward components Component installation prerequisites Product Availability Matrix at http://service.sap.com/PAM

27

2011-08-19

Deployment

2. Review the key concepts you need to consider for your deployment, including operating system, database, and application server considerations, in addition to security, performance and scalability, and high availability. See "Assessing your organization's environment" in the SAP BusinessObjects Business Intelligence Platform Planning Guide. 3. Choose an initial deployment architecture that will serve your needs within the limits of your resources. For suggestions and common configurations, see Deployment scenarios.

3.2 Information Steward components


You can choose to install SAP BusinessObjects Information Steward components on one or more computers based on available resources and your deployment planning. The following table shows the components that you can choose on the "Select Features" window of the Information Steward installer.
Component in feature tree Description

Information Steward Web Application

Provides web applications that: Administer Information Steward in the Central Management Console (CMC) Comprise the modules of Information Steward: Data Insight Metadata Management Metapedia Cleansing Package Builder Note: If the BI platform web applications were manually deployed, manually deploy the Information Steward web application with WDeploy after installation.

Information Steward Task Server Metadata Relationship Service Metadata Search Service Information Steward Cleansing Package Builder Service SAP BusinessObjects Enterprise Metadata Integrator

Processes profile and rule tasks for the Data Insight module of Information Steward. Processes object relationships (for example, impact and lineage). Provides search capability on the Metadata Management module of Information Steward. Provides the capability to create and refine cleansing packages on the Cleansing Package Builder module of Information Steward. Collects information from an SAP BusinessObjects Business Intelligence platform repository that includes metadata objects such as SAP Crystal Reports, Web Intelligence documents, and universes.

28

2011-08-19

Deployment

Component in feature tree

Description

SAP NetWeaver Business Warehouse Metadata Integrator Common Warehouse Model (CWM) Metadata Integrator Relational Databases (RDBMS) Metadata Integrator

Extracts information from a NetWeaver Business Warehouse system that includes metadata objects such as Queries, InfoProviders, InfoObjects, Transformations, and DataSources. Extracts information from the CWM Relational Package that includes definitions of metadata objects such as catalogs, schemas, and tables. Extracts information from an RDBMS that includes definitions of metadata objects such as catalogs, schemas, stored procedures, and aliases. Supported relational databases include DB2, MySQL, Oracle, SQL Server, Teradata, or a Universe connection using JDBC or ODBC. For more information, see the Supported Platforms document.

SAP BusinessObjects Data Services Metadata Integrator

Extracts information from an SAP BusinessObjects Data Services repository that includes definitions of metadata objects such as source tables and columns for ETL jobs, datastores and configurations, and flat files. Extracts information from an SAP BusinessObjects Data Federator repository that includes definitions of metadata objects such as projects, catalogs, datasources, and mapping rules. Extracts the following metadata from other sources: Data Modeling metadata such as Sybase Power Designer, Embar cadero ER/Studio, and Oracle Designer ETL metadata such as Oracle Warehouse Builder and Microsoft SQL Server Integration Services (SSIS) OLAP and BI metadata such as IBM DB2 Cube Views, Oracle OLAP, and Cognos 8 BI Reporting For more information, see http://www.metaintegration.net/Prod ucts/MIMB/Documentation/.

SAP BusinessObjects Data Federator Metadata Integrator Meta Integration Metadata Bridge (MIMB) Metadata Integrator

Related Topics Deployment scenarios Deploying web applications with WDeploy Architecture overview

3.2.1 Component installation prerequisites

29

2011-08-19

Deployment

In general, all Information Steward components require that the Information Steward repository has already been created or will be created during the installation process. Note: To create the Information Steward repository, you must perform the first installation of Information Steward on the same computer as the SAP BusinessObjects Data Services Job Server component. The SAP BusinessObjects BI platform Central Management Server (CMS) must be in the landscape (not necessarily on the same computer). Component-specific prerequisites are described in the following table:
Component Host system prerequisites

Information Steward Web Application

BI platform Web Tier Note: If you are manually installing the web application, you must copy a .war file. For more information, see Deploying web applications with WDeploy.

Information Steward Task Server

BI platform Adaptive Job Server BI platform Adaptive Processing Server SAP BusinessObjects Data Services Job Server

Metadata Relationship Service Metadata Search Service Cleansing Package Builder Service All Metadata Integrators

BI platform Adaptive Processing Server

BI platform Adaptive Job Server BI platform Adaptive Processing Server Note: All Metadata Integrators can be installed only on supported Windows platforms.

Related Topics Component run-time dependencies Deploying web applications with WDeploy

3.2.2 Component run-time dependencies

30

2011-08-19

Deployment

In addition to installation requirements, Information Steward components may have additional run-time dependencies. Component-specific dependencies are described in the following table:

31

2011-08-19

Deployment

Component

Additional dependencies

Information Steward Task Server

To browse and view data, Data Insight requires: Data Services Metadata Browsing Service Data Services View Data Service The BI platform File Repository Server must be available and running in the landscape.

Metadata Search Service Cleansing Package Builder Service All Metadata Integrators

SAP BusinessObjects Enterprise Metadata InSAP BusinessObjects Business Intelligence plattegrator form (BI platform) must be installed. The SAP BusinessObjects Enterprise Metadata Integrator will not collect objects from SAP BusinessObjects Information platform services (IPS). For Web Intelligence documents, the BI platform client tools must be installed on the host system. If you want to collect metadata from an SAP BusinessObjects Enterprise XI 3.x system, you must install the Remote Job Server (see Remote Job Server Installation). In addition, for Crystal Reports or universes whose sources are SAP BusinessObjects NetWeaver BW objects, you must install BusinessObjects XI Integration for SAP Solutions on Enterprise XI 3.x. The BI platform client tools requirement is for reports that were created with the Refresh on Open option because when the Metadata Integrator collects the metadata from the Enterprise XI 3.x system, the Enterprise XI 3.x system will connect to the source BW system to refresh the data automatically. The BusinessObjects Business Intelligence platform Metadata Integrator supports two drivers: SAP BW MDX Query and SAP Operational Data Store. The BusinessObjects XI Integration for SAP Solutions has prerequisites that you must install. For more information, see the BusinessObjects XI Integration for SAP Installation Guide. Information Steward web application To view the Information Steward web application, you must have the latest Adobe Flash player installed.

32

2011-08-19

Deployment

Related Topics Component installation prerequisites

3.2.3 Component installation results


Installing an Information Steward component creates one or more services or applications on the target host system. The services and applications created by each Information Steward component in the installation program feature tree are described in the following table:

33

2011-08-19

Deployment

Feature tree component

Installation result

Information Steward Web Application

Deploys Information Steward: A web application through which you access the Information Steward modules: Data Insight Metadata Management Metapedia Cleansing Package Builder The CMC features through which administrative tasks for Information Steward are performed

Information Steward Task Server

Creates the following services under the Information Steward Job Server (ISJobServer): Information Steward Task Scheduling Service Information Steward Integrator Scheduling Service (required for utilities) Creates the following service under the Enterprise Information Management Adaptive Processing Server (EIMAdaptiveProcessingServer): Information Steward Administrative Task Service

Metadata Relationship Ser- Creates the following service under the Enterprise Information Management Adaptive Processing Server (EIMAdaptiveProcessingServer): vice Information Steward Metadata Relationship Service Metadata Search Service Creates the following service under the Enterprise Information Management Adaptive Processing Server (EIMAdaptiveProcessingServer): Search Service

Cleansing Package Builder Creates the following services under the Enterprise Information Management Adaptive Processing Server (EIMAdaptiveProcessingServer): Service Cleansing Package Builder Core service Cleansing Package Builder Auto-analysis service Cleansing Package Builder Publishing service All Metadata Integrators Creates the following services under the Information Steward Job Server (ISJobServer): Information Steward Integrator Scheduling Service Information Steward Integrator Service

3.3 Deployment guidelines

34

2011-08-19

Deployment

3.3.1 General deployment guidelines


Ideally, you should deploy SAP BusinessObjects Information Steward components across multiple computers based on the expected amount of processing and expected time of day when the processing will occur. The following are some general deployment guidelines. 1. When using a distributed environment, enable and run only the servers that are necessary. For more information, see the Business Intelligence Platform Administrator Guide. 2. Use dedicated servers for resource intensive servers like the Data Services Job Server, Metadata Integrators, and the Cleansing Package Builder Auto-Analysis service. 3. Install the Information Steward Web Application on a separate server. The Business Intelligence platform Web Tier must be installed on the same computer as the Information Steward Web Application. If you do not have Tomcat, you need to manually deploy the Information Steward Web Application. 4. If you have many concurrent users, you can use multiple Information Steward web applications with Load Balancer. 5. The Information Steward repository should be on a separate computer but in the same sub-network as the Information Steward Web applications, Enterprise Information Management Adaptive Processing Server, Information Steward Job Server, and Data Services Job Server to obtain a higher throughput. 6. Make sure that the database server for the Information Steward repository is tuned and has enough resources. 7. Allocate enough memory and hard disk space to individual servers as needed. 8. Follow good scheduling practices to make sure that resource intensive tasks do not overlap each other. Schedule them to run during non-business hours so that on-demand request performance is not affected. Related Topics Administrator Guide: Performance and Scaling Considerations, General best practices Deploying web applications with WDeploy SAP BusinessObjects Business Intelligence platform Web Application Deployment Guide: Failover and load balancing Data Insight deployment guidelines for profile and rule tasks Metadata Management deployment guidelines Cleansing Package Builder deployment guidelines

3.3.2 Data Insight deployment guidelines for profile and rule tasks

35

2011-08-19

Deployment

Guidelines to deploy the Data Insight module of Information Steward components include the following: 1. If you expect your Data Insight profiling and rule tasks to consume a large amount of processing, deploy the Data Services Job Server on a separate computer. 2. To improve the execution of Data Insight profiling tasks, the Data Services Job Server can be on multiple computers that are separate from the web application server to take advantage of Data Services job server groups and parallel execution. You must access the Data Services Server Manager on each computer to do the following tasks: Add a Data Services Job Server and associate it to the Information Steward repository. For more information, see Adding Data Services Job Servers for Data Insight in the Administrator Guide. Specify the path of the pageable cache that will be shared by all job servers in the Pageable cache directory option. 3. For a predictable distribution of tasks when using multiple Data Services Job Servers, try to ensure that the hardware and software configurations are homogeneous. This means that they should all have similar CPU and RAM capacity. 4. Irrespective of using DOP and/or multiple Data Services Job Servers, set the pageable cache directory on high speed and high capacity disk. 5. If you are processing flat files, store them on a high speed disk so that read performance is good. 6. For high availability on a cluster, duplicate SAP BusinessObjects Business Intelligence platform, Business Intelligence platform Web Tier and Information Steward web application, Data Services Job Server and Information Steward Task Server. Related Topics Administrator Guide: Performance and Scaling Considerations, Data Insight best practices

3.3.3 Metadata Management deployment guidelines


Guidelines to deploy the Metadata Management module of Information Steward components include the following: 1. Metadata integrators for BusinessObjects Enterprise, Data Services, and SAP Business Warehouse should be installed on their own dedicated servers if they require large processing time or they run in overlapping time periods with other metadata integrators or Data Insight tasks. 2. The Metadata Relationship Service and Metadata Search Service can be combined. 3. Additional guidelines to consider for Metadata Relationship Service: Should be on a separate computer than the web application server to obtain higher throughput. Can be combined with any Metadata Integrator, or it can be on its own computer. The rationale for this combination is that Metadata Integrators usually run at night or other non-business hours, and the Metadata Relationship Service runs during normal business hours when users are viewing relationships (such as impact and lineage) on the Information Steward web application. 4. Additional guidelines to consider for Metadata Search Service include:

36

2011-08-19

Deployment

Can be combined with any Metadata Integrators, or it can be on its own computer. The rationale for this combination is that Metadata Integrators usually run at night or other non-business hours, and the Search Server runs during normal business hours when users are searching on the Metadata Management tab of Information Steward.

5. The File Repository Servers should be installed on a server with a high speed and high capacity disk. 6. For high availability on a cluster, duplicate SAP BusinessObjects Business Intelligence platform, Business Intelligence platform Web Tier and Information Steward web application, and Metadata Integrators. For more details, see the SAP BusinessObjects Business Intelligence Platform Planning Guide. Related Topics Administrator Guide: Performance and Scaling Considerations, Metadata Management best practices

3.3.4 Cleansing Package Builder deployment guidelines


Guidelines to deploy the Cleansing Package Builder module of Information Steward components include the following: 1. Cleansing Package Builder Auto-Analysis service should be on a dedicated server obtain higher throughput. 2. For high availability on a cluster, duplicate SAP BusinessObjects Business Intelligence platform, Business Intelligence platform Web Tier and Cleansing Package Builder Services. Related Topics Administrator Guide: Performance and Scaling Considerations, Cleansing Package Builder best practices

3.4 Deployment checklist


This section provides a checklist for the steps you need to perform when planning your SAP BusinessObjects Information Steward deployment.

37

2011-08-19

Deployment

Checklist item

Reference

Complete? (Y/N)

Understand the Information Steward compo- Architecture overview nents and how they interact with the BI platform and SAP BusinessObjects Data Services. Understand the workflows (how information travels through the architecture). Information workflows

Y__/N__

Y__/N__ Y__/N__

Identify the operating system and product de- Product Availability Matrix available at pendencies to which you are deploying each http://service.sap.com/PAM component. Choose the database servers you will be accessing. Choose a web application server. Repository database requirements and preparation Web Application Server

Y__/N__ Y__/N__

Identify and plan your security requirements Securing SAP BusinessObjects Informa- Y__/N__ (authentication, SSL, firewalls, reverse proxy). tion Steward in the Administrator Guide Identify performance requirements. Choose whether or not to design for high availability support. Performance and Sizing Considerations Y__/N__ in the Administrator Guide Scenario 6: High availability Y__/N__

If you are using SLD, identify your SLD server. Support for SAP System Landscape Di- Y__/N__ rectory (SLD) Plan your system landscape to meet your cho- Deployment scenarios sen deployment scenario. Y__/N__

3.5 Deployment scenarios


This section describes sample scenarios for administrators planning an installation of SAP BusinessObjects Information Steward. The administrator should plan the installation and landscape using as input the sample scenarios below and performance and security requirements, trying to optimize the machine usage. It is important to note that the optimal configuration for your deployment will depend on many factors: hardware configuration, database software, reporting requirements, operating system, clock speed, hyperthreading, disk speed, application server configuration, load frequency, and so on. The following table shows a summary of the most common deployment scenarios of Information Steward (IS) and the prerequisite components of SAP BusinessObjects Business Intelligence platform (BI platform) and SAP BusinessObjects Data Services (DS). Every deployment is unique, and these examples are provided only as guidelines.

38

2011-08-19

Deployment

Table 3-2: Deployment scenarios 1 through 4


Server/ Scenario 1 Scenario 2 Scenario 3 Scenario 4

Scenario Server 1

Single machine BI platform DS Job Server DS Metadata Browsing Service DS View Data Service IS web application IS Task Server Search Relationship Integrators CPB Services

Scaling Data Insight servers BI platform DS Job Server DS Metadata Browsing Service DS View Data Service IS web application IS Task Server Search Relationship Integrators CPB Services DS Job Server

Scaling for Metadata Management BI platform DS Job Server DS Metadata Browsing Service DS View Data Service IS web application IS Task Server Relationship CPB Services

Scaling for Cleansing Package Builder BI platform DS Job Server DS Metadata Browsing Service DS View Data Service IS web application IS Task Server Search Relationship Integrators

Server 2

Integrator Search

CPB Auto-analysis Service CPB Core Service CPB Publishing Service

Server 3

DS Job Server

Integrator Search

The following topics provide the steps to deploy each of the above four scenarios, plus the following additional scenarios: Scaling servers for web application users High availability Mixed operating systems Related Topics Scenario 1: Single machine deployment Scenario 2: Scaling Data Insight servers Scenario 3: Scaling for Metadata Management Scenario 4: Scaling for Cleansing Package Builder Scenario 5: Scaling servers for web application users

39

2011-08-19

Deployment

Scenario 6: High availability Scenario 7: Mixed operating systems

3.5.1 Scenario 1: Single machine deployment


This scenario installs all components of SAP BusinessObjects Information Steward on one Windows computer which does not currently have the prerequisite components of SAP BusinessObjects Business Intelligence platform and SAP BusinessObjects Data Services. The following diagram and table list the recommended order that the prerequisite software is installed before you start installing Information Steward.

Table 3-3: Installation order and steps for single machine scenario
Order Software product Description

1.

SAP BusinessObjects Business Intelligence platform (BI platform) or SAP BusinessObjects Information platform services (IPS)

1. Follow the procedure in the SAP BusinessObjects Business Intelligence Platform Installation Guide for Windows to start the installation. 2. Select the Full installation type. If you know which components you want to install, you can select the Custom installation type. 3. Enter administrator-level connection information for the CMS server that you created in the previous step.

40

2011-08-19

Deployment

Order

Software product

Description

2.

SAP BusinessObjects Data Services

You must install SAP BusinessObjects Data Services on the computer before you perform the first installation of SAP BusinessObjects Information Steward. Note: This installation requires that you stop and start the Server Intelligence Agent (SIA). Users cannot access the Central Management System (CMS) while the SIA is stopped. Therefore, it is recommended that you perform this installation during scheduled down time to limit the effect on your users. 1. Follow the procedure in To run an interactive installation in the SAP BusinessObjects Data Services Installation Guide for Windows. 2. Ensure that the following components are selected: Job Server under Data Services Server Data Services Metadata Browsing Service Data Services View Data Service

Note: Data Services Metadata Browsing Service and Data Services View Data Service are not selected by default. So, you must manually select them. The other Data Services components are optional. 3. After Data Services installation completes, you must restart the computer. 3. SAP BusinessObjects Information Steward The computer must have the Windows operating system to install SAP BusinessObjects Information Steward on it. Note: This installation requires that you stop and start the Server Intelligence Agent (SIA). Therefore, it is recommended that you perform this installation during scheduled down time to limit the effect on your users. 1. Follow the procedure in Standard installation in the SAP BusinessObjects Information Steward Installation Guide for Windows. 2. For install type, select Primary Install. 3. Enter Administrator connection information for the CMS database that you created when you Installed your BI platform. 4. Keep the default of all components selected on the "Select Features" window. 5. After Information Steward installation completes, configure the Data Services Job Server for Information Steward. For details, see Configuring a Data Services Job Server for Data Insight. 6. To verify that the servers and services are running after installation completes, see Verifying Information Steward servers are running and Verifying Information Steward services .

41

2011-08-19

Deployment

3.5.2 Scenario 2: Scaling Data Insight servers


This scenario expands the number of computers to run profile and rule tasks. To enable grid computing for profile tasks, see the Performance and Sizing Considerations section in the Administrator Guide. Use this scenario to provide load balancing and parallel execution for Data Insight profile and rule tasks. The following diagram shows the components to install on each computer and the table lists the recommended order of installing prerequisite software, installing Information Steward, and post-installation steps required for this scenario.

Table 3-4: Installation order and steps for large amount of profile or rule task processing
Comput er Software product Description

Server 1

SAP BusinessObjects Business Intelligence platform (BI platform) or SAP BusinessObjects Information platform services (IPS) SAP BusinessObjects Data Services SAP BusinessObjects Information Steward

Follow the same steps as in Scenario 1: Single machine deployment.

42

2011-08-19

Deployment

Comput er

Software product

Description

Server 2 , Server 3, ... Server n

SAP BusinessObjects Data Services

Note: Ensure that the additional computers (in this example, Server 2 to Server n) have the same hardware and software so that the Data Services Job Servers are running on identical systems. 1. Follow the procedure in To run an interactive installation in the SAP BusinessObjects Data Services Installation Guide. Ensure that the following component is selected: Data Service Job Server 2. After installation completes, invoke the Data Services Server Manager on this computer to create a Data Services Job Server and associate it with the Information Steward repository. For details, see Configuring a Data Services Job Server for Data Insight.

3.5.3 Scenario 3: Scaling for Metadata Management


This scenario expands the number of computers to handle Metadata Management integrator sources. Use this scenario to provide high availability when running integrator sources that consume a lot of resources and might take hours to collect metadata for the Metadata Management module of Information Steward. The following diagram shows the components to install on each computer and the table lists the recommended order to install prerequisite software and which components to select for each product.

43

2011-08-19

Deployment

Table 3-5: Installation order and steps for a large amount of integrator source processing
Comput er Software product Description

Server 1

SAP BusinessObjects Business Intelligence platform (BI platform) or SAP BusinessObjects Information platform services (IPS) SAP BusinessObjects Data Services SAP BusinessObjects Information Steward

Follow the same steps as in Scenario 1: Single machine deployment.

Server 2, Server 3, ... Server n

SAP BusinessObjects Business Intelligence platform (BI platform) or SAP BusinessObjects Information platform services (IPS)

Note: Ensure that the additional computers to run the integrator sources have the Windows operating system. Ideally, the integrator source system should exist on this computer. 1. Follow the procedure in the SAP BusinessObjects Business Intelligence Platform Installation Guide for Windows to start the installation. 2. Select the Custom/Expand installation type and select the following components: Platform Processing Services Platform Scheduling Services 3. Select Expand an existing Business Intelligence Platform on the "Expand Installation" screen. 4. Select the CMS Database Type for the CMS database that you created on Server 1. 5. Enter the Server Intelligence Agent (SIA) node name for this computer.

SAP BusinessObjects Information Steward

Note: The Information Steward installation requires that you stop and start the Server Intelligence Agent (SIA). Users cannot access the Central Management System (CMS) while the SIA is stopped. Therefore, it is recommended that you perform this installation during scheduled down time to limit the effect on your users. 1. Follow the Standard installation procedure in the Installation Guide. 2. For install type, select Expanded Install. 3. For the CMS database, you must enter the Administrator connection information as in Server 1. 4. Skip the repository creation. 5. Select the Metadata Integrator component that you want to install.

44

2011-08-19

Deployment

Related Topics Standard installation

3.5.4 Scenario 4: Scaling for Cleansing Package Builder


This scenario expands the number of computers to handle a large amount of Cleansing Package Builder processing. The Cleansing Package Builder Auto-analysis Service is the most resource-intensive service of the Cleansing Package Builder module of Information Steward. Use this scenario to separate the most resource-intensive service of the Cleansing Package Builder onto its own computer. The following diagram shows the components to install on each computer and the table lists the recommended order to install prerequisite software and which components to select for each product.

45

2011-08-19

Deployment

Table 3-6: Installation order and steps for a large amount of Cleansing Package Builder processing
Comput er Software product Description

Server 1

SAP BusinessObjects Business Intelligence platform (BI platform) or SAP BusinessObjects Information platform services (IPS) SAP BusinessObjects Data Services SAP BusinessObjects Information Steward

Follow the same steps as in Scenario 1: Single machine deployment.

46

2011-08-19

Deployment

Comput er

Software product

Description

Server 2

SAP BusinessObjects Business Intelligence platform (BI platform) or SAP BusinessObjects Information platform services (IPS)

1. To start the installation, follow the procedure in the SAP BusinessObjects Business Intelligence Platform Installation Guide for Windows. 2. Select the Custom/Expand installation type and select the following components under Platform Services: Platform Processing Services Platform Scheduling Services 3. Select Expand an existing Business Intelligence Platform on the "Expand Installation" screen. 4. Select the CMS Database Type for the CMS database that you created on Server 1. 5. Enter the Server Intelligence Agent (SIA) node name for this computer.

SAP BusinessObjects Information Steward

1. Follow the Standard installation procedure in the Installation Guide. Note: The Information Steward installation requires that you stop and start the Server Intelligence Agent (SIA). Users cannot access the Central Management System (CMS) while the SIA is stopped. Therefore, it is recommended that you perform this installation during scheduled down time to limit the effect on your users. For install type, select Expanded Install. For the CMS database, you must enter the Administrator connection information as in Step 1. For the Information Steward repository, enter the same connection information as on Server 1 and skip the repository creation. Select the Cleansing Package Builder component.

2. After Information Steward installation completes, enable only the Cleansing Package Builder Auto-analysis Service on this computer. From the CMC Home page, go to the "Servers" management area. Expand the Service Categories node and select Enterprise Information Management Services Right-click "EIMAdaptiveProcessingServer" and click Stop Server Right-click "EIMAdaptiveProcessingServer" and click Select Services. From the list on the right, select Cleansing Package Builder Core service and Cleansing Package Builder Publishing service, click < to remove them, and click OK. Right-click "EIMAdaptiveProcessingServer" and click Start Server.

47

2011-08-19

Deployment

Comput er

Software product

Description

Server 3

SAP BusinessObjects Business Intelligence platform (BI platform) or SAP BusinessObjects Information platform services (IPS) SAP BusinessObjects Information Steward

Follow the same steps as in Server 2.

1. Step 1 is the same as in Server 2 for SAP BusinessObjects Information Steward 2. Enable only the Cleansing Package Builder Core Service and Cleansing Package Builder Publishing Service on this computer: From the CMC Home page, go to the "Servers" management area. Expand the Service Categories node and select Enterprise Information Management Services. Right-click "EIMAdaptiveProcessingServer" and click Stop Server. Right-click "EIMAdaptiveProcessingServer" and click Select Services. From the list on the right, select Cleansing Package Builder Autoanalysis service, click < to remove it, and click OK. Right-click "EIMAdaptiveProcessingServer" and click Start Server.

Related Topics Standard installation

3.5.5 Scenario 5: Scaling servers for web application users


This scenario expands the number of computers to handle a large number of web application users. Use this scenario to provide high availability and load balancing for web applications. Note: If you distribute the Information Steward Web Application on multiple computers, you will need to install a load balancer (software or hardware) to distribute the users among the web servers. The following diagram shows the components to install on each computer and the table lists the recommended order to install prerequisite software and which components to select for each product.

48

2011-08-19

Deployment

Table 3-7: Installation order and steps for a large number of web application users
Comput er Software product Description

Server 1

BI platform Data Services Information Steward

1. Follow the same steps as in Scenario 1: Single machine deployment. 2. After installation, generate a deployment file using WDeploy for manual deployment. For more information, see Deploying web applications with WDeploy. 1. Install the WDeploy file generated on Server 1 onto this Web Application Server or Web Server. For more information, see To deploy or undeploy components.

Server 2

Web Application Server or Web Server

3.5.6 Scenario 6: High availability


This scenario expands the single machine scenario to deploy more than one complete Information Steward installation on different machines forming a cluster environment. Use this scenario to provide high availability and load balancing of the Information Steward components.

49

2011-08-19

Deployment

Table 3-8: Installation order and steps for high availability


Comput er Software product Description

Server 1

SAP BusinessObjects Business Intelligence platform (BI platform) or SAP BusinessObjects Information platform services (IPS) SAP BusinessObjects Data Services SAP BusinessObjects Information Steward

Follow the same steps as in Scenario 1: Single machine deployment.

50

2011-08-19

Deployment

Comput er

Software product

Description

Server 2

SAP BusinessObjects Business Intelligence platform (BI platform) or SAP BusinessObjects Information platform services (IPS)

1. Follow the procedure in the SAP BusinessObjects Business Intelligence Platform Installation Guide to start the installation. 2. Select the Custom installation type and unselect Central Management Server under Platform Services in the component feature tree. 3. Select Expand an existing Business Intelligence Platform on the "Expand Installation" screen. 4. Select the CMS Database Type for the CMS database that you created on Server 1. 5. Enter the Server Intelligence Agent (SIA) node name for this computer. 6. After BI platform installation completes, stop and remove the Input File Repository and Output File Repository on this node. Note: The Information Steward installation requires that you stop and start the Server Intelligence Agent (SIA). Users cannot access the Central Management System (CMS) while the SIA is stopped. Therefore, it is recommended that you perform this installation during scheduled down time to limit the effect on your users. 1. Follow the procedure in To run an interactive installation in the SAP BusinessObjects Data Services Installation Guide. 2. Ensure that the following components are selected: Job Server under Data Services Server Data Services Metadata Browsing Service Data Services View Data Service Note: Data Services Metadata Browsing Service and Data Services View Data Service are not selected by default. So, you must manually select them. The other Data Services components are optional.

SAP BusinessObjects Data Services

SAP BusinessObjects Information Steward

51

2011-08-19

Deployment

Comput er

Software product

Description

Note: The Information Steward installation requires that you stop and start the Server Intelligence Agent (SIA). Therefore, it is recommended that you perform this installation during scheduled down time to limit the effect on your users. 1. Follow the Standard installation procedure in the Installation Guide. 2. For install type, select Expanded Install. 3. For the CMS database, you must enter the Administrator connection information as in Step 1. 4. For the Information Steward repository, enter the same connection information as on Server 1 and skip the repository creation. 5. Keep the default of all components selected on the "Select Features" window. 6. When the installation finishes, configure the Data Services Job Server for Information Steward. For more information, see "Configuring a Data Services Job Server for Data Insight".

Related Topics Standard installation

3.5.7 Scenario 7: Mixed operating systems


This scenario illustrates a situation in which you want to add SAP BusinessObjects Information Steward in a mixed operating system environment. For example, suppose you have the following environment: Linux on two computers clustered with SAP BusinessObjects Enterprise 4.x Linux for Web Logic on a third computer for the web applications Windows with SAP BusinessObjects Enterprise 4.x on a fourth computer The following diagram shows this environment after you install the prerequisite components of SAP BusinessObjects Business Intelligence platform and SAP BusinessObjects Data Services, and then Information Steward. The table after the diagram lists the recommended order that the software components should be installed to ensure that the prerequisite software is installed before you start installing Information Steward.

52

2011-08-19

Deployment

Order

Task

Notes

1.

Install SAP BusinessObjects Business Intelligence platform (BI platform) clustered on Linux 64-bit computers.

1. Follow the procedure in the SAP BusinessObjects Business Intelligence Platform Installation Guide for UNIX to start the installation. 2. Select the Custom installation type. 3. On the "Select Features" window, unselect the Web Tier component. 4. After installation, generate a deployment file using WDeploy for manual deployment. For more information, see "Deploying web applications with WDeploy". 5. Verify that communication is working for the BI platform components: a. Go to the "Servers" management area of the CMC to ensure that the following servers are enabled in the "Servers List": computernameAdaptiveProcessingServer computernameAdaptiveJobServer computernameCentralManagementServer computernameInputFileRepository computernameOutputFileRepository b. Invoke the Central Configuration Manager to ensure that the services associated with the above servers are enabled.

53

2011-08-19

Deployment

Order

Task

Notes

2. (a)

Install SAP BusinessObjects Business Intelligence platform and the SAP BusinessObjects Enterprise Client Tools on the Windows computer.

You must install SAP BusinessObjects Business Intelligence platform on the Windows computer before you install SAP BusinessObjects Information Steward. 1. Back up the CMS database and SAP BusinessObjects Business Intelligence platform (BI platform) filestore that currently exists on Linux. 2. Follow the procedure in the SAP BusinessObjects Business Intelligence platform Installation Guide for Windows.to start the installation. 3. Select Expand an existing Information Platform Services on the "Expand Installation" screen. 4. Select the CMS Database Type for the CMS database that you created on Server 1. 5. Enter the Server Intelligence Agent (SIA) node name for this computer. 6. On the "Select Features" window, select the following components to install on this Windows computer: Adaptive Process Server (APS) Adaptive Job Server (AJS) 7. To verify that communication is working for the BI platform components: a. Go to the "Servers" management area of the CMC to ensure that the following servers are enabled in the "Servers List": computernameAdaptiveProcessingServer computernameAdaptiveJobServer computernameCentralManagementServer b. Invoke the Central Configuration Manager to ensure that the services associated with the above servers are enabled. 8. Follow the procedure "To run an interactive installation of Client Tools" in the SAP BusinessObjects Business Intelligence platform Installation Guide for Windows to start the installation of BI platform client components (such as SAP Crystal Reports).

54

2011-08-19

Deployment

Order

Task

Notes

2. (b)

Install SAP BusinessObjects Data Services on the Linux cluster.

You must install SAP BusinessObjects Data Services on the computer before you perform the first installation of SAP BusinessObjects Information Steward. 1. Follow the procedure in To run an interactive installation in the SAP BusinessObjects Data Services Installation Guide for UNIX. 2. You must enter the Administrator connection information for the CMS database that you created when you Installed your BI platform (do not choose the Skip option). 3. Ensure that the following components are selected: Job Server under Data Services Server Data Services Metadata Browsing Service Data Services View Data Service The other components are optional. 4. After Data Services installation completes, restart your computer. Note: This installation requires that you stop and start the Server Intelligence Agent (SIA). Users cannot access the Central Management System (CMS) while the SIA is stopped. Therefore, it is recommended that you perform this installation during scheduled downtime to limit the effect on your users. 1. Follow the procedure in Standard installation in the SAP BusinessObjects Information Steward Installation Guide for UNIX. 2. For install type, select Primary. 3. For the CMS database, you must enter the Administrator connection information that you created when you Installed your BI platform. 4. If you want to deploy them on a separate machine than the Metadata Integrators, select the following components: Metadata Relationship Service Metadata Search Service 5. If you will use the Data Insight module, select the following component: Information Steward Task Server 6. If you will use the Cleansing Package Builder module, select the following component: Cleansing Package Builder Service 7. To verify that the servers and services are running after installation completes, see Verifying Information Steward servers are running and Verifying Information Steward services in the SAP BusinessObjects Information Steward Installation Guide for UNIX.

2. (c)

Install SAP BusinessObjects Information Steward on the Linux cluster.

55

2011-08-19

Deployment

Order

Task

Notes

3.

Install SAP BusinessObjects Information Steward on the Windows computer.

Note: This installation requires that you stop and start the Server Intelligence Agent (SIA). Users cannot access the Central Management System (CMS) while the SIA is stopped. Therefore, it is recommended that you perform this installation during scheduled downtime to limit the effect on your users. 1. Follow the procedure in Standard installation in the SAP BusinessObjects Information Steward Installation Guide for Windows. 2. For install type, select Expanded Install. 3. For the CMS database, you must enter the Administrator connection information that you created when you Installed your BI platform. 4. Select the following components for the Metadata Management module: Metadata Integrator for each source system that you want to collect metadata from to obtain impact and lineage relationships 5. To verify that the servers and services are running after installation completes, see Verifying Information Steward servers are running and Verifying Information Steward services in the SAP BusinessObjects Information Steward Installation Guide for Windows.

4. (a)

Install the Web Application component of SAP BusinessObjects Business Intelligence platform

1. Follow the procedure in the SAP BusinessObjects Business Intelligence Platform Installation Guide for UNIX to start the installation. 2. For install type, select Custom. 3. On the "Select Features" window, select the Web Tier component. 4. Follow the procedure in the SAP BusinessObjects Business Intelligence Platform Web Application Deployment Guide for UNIX to deploy the web application with the WDeploy tool. 1. Download the installation package for SAP BusinessObjects Information Steward for Linux. 2. Follow the procedure in Deploying web applications with WDeploy in the SAP BusinessObjects Information Steward Installation Guide for Windows to deploy the Information Steward web applications to the computer where Web Logic is installed. 3. Use the wdeploy tool to prepare the web application server components (WAR files) on the Linux computer. 4. Copy the WAR files to the Linux computer.

4. (b)

Install the Information Steward Web Application on the Linux computer.

56

2011-08-19

Preparation

Preparation

This section details how to prepare for the installation of Information Steward. Process Flow 1. Review the Deployment section. Determine which product components you will install on each host system. Consider how you should prepare your infrastructure and set up your environment, including server locations. 2. Ensure that your network and host systems meet the basic requirements for an Information Steward installation. 3. Ensure that sufficient disk space is available to install, allowing both the operating system and the software to grow over time as patches or new components become available. 4. Ensure that the user who will run the installation program has administrative privileges. 5. Obtain the installation media or download the latest release and any patches or service packs from the support portal at http://service.sap.com/swdc. 6. Decide which database server to use for the Information Steward repository and prepare the database. 7. Decide which options you will change during the installation process. In most cases, you can accept the default values. More advanced installations require that you plan the installation process. The installation program will prompt for the following information: License information (the name of the user and company associated with your software). Administrator-level connection information for the Central Management Server (CMS). Repository database connection information, including type, connection, and authentication details.

Caution: The installation program will restart the Server Intelligence Agent (SIA), which might affect all users currently logged into the CMS. Plan for this downtime to minimize the disruption for your CMS users.

4.1 Requirements

57

2011-08-19

Preparation

4.1.1 System requirements


When you install SAP BusinessObjects Information Steward on a local drive, use the following guidelines: Before you run the installation program, 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, ensure that there is enough room for the deployment and the operating system. If you have previously installed SAP BusinessObjects products, the installation program will use the existing installation directory. For a complete list of supported operating systems and hardware requirements, consult the Product Availability Matrix available at http://service.sap.com/PAM. Related Topics Component installation prerequisites

4.1.2 Software dependencies


Before you install SAP BusinessObjects Information Steward, ensure that your host systems meet all software dependency requirements. For complete information about the software environment requirements, see the Product Availability Matrix available at http://service.sap.com/PAM. In general, the following SAP BusinessObjects BI platform components must be preinstalled and configured correctly before you can install and use Information Steward: Adaptive Job Server Adaptive Processing Server File Repository Server (for Metadata Integrators) For additional information about runtime software dependencies for each Information Steward component, see the Deployment section. Note: Information Steward uses the same web application server and Java 2 Software Development Kit (JDK) that the BI platform uses.

58

2011-08-19

Preparation

If you want to use Information platform services to provide the BI platform components required by Information Steward, use InstallIPS.exe instead of setup.exe to launch the Information platform services installation program.

Related Topics Component installation prerequisites

4.1.3 Verifying prerequisite software


The SAP BusinessObjects Information Steward installation program checks if prerequisite software components are already installed on the computer. If a dependency prerequisite is critical, the installation program will not allow the installation to proceed. To verify that critical prerequisite software components are installed before you start the installation program: To verify that the required SAP BusinessObjects BI platform servers and services are running and enabled: 1. Go to the "Servers" management area of the Central Management Console (CMC) to ensure that the following servers are enabled in the "Servers List": SIANodeNameAdaptiveProcessingServer SIANodeNameAdaptiveJobServer SIANodeNameCentralManagementServer SIANodeNameInputFileRepository SIANodeNameOutputFileRepository If these servers are missing, see your BI platform documentation for information on how to install and configure them. 2. Invoke the Central Configuration Manager to ensure that the services associated with the above servers are enabled.

4.1.4 Account permissions


To install SAP BusinessObjects Information Steward, a user must have the following permissions:

59

2011-08-19

Preparation

Category

Required permissions

Operating System

Local administrator privileges. Note: If you are installing Information Steward on a Windows host system that has User Account Control (UAC) enabled, you should run the installation program with the host system's built-in administrator account. If you use a normal account, a UAC prompt will appear.

Network Database

TCP/IP access to all host systems where you want to install components - all specified ports must be available. Permission for the SAP BusinessObjects user account to create and drop tables, and read, write, and edit table rows.

SAP BusinessObjects Administrator privileges. BI platform In addition, it's recommended that you use the same user account for installing Information Steward and your web application server.

4.1.5 Network requirements


When you install SAP BusinessObjects Information Steward on multiple host systems, ensure that your deployment meets the following network requirements: Each host system must be able to communicate with the Central Management Server (CMS). All host systems in the deployment must be able to communicate with each other. Related Topics Architecture

4.2 Repository database requirements and preparation


The SAP BusinessObjects Information Steward repository is a database that stores the following information: All profile results and sample records for all profiling attributes, rule results and sample data that failed the rules, and scorecard results that Data Insight users and the Calculate Scorecard utility generate.

60

2011-08-19

Preparation

All metadata that the Metadata Integrators collect so that the Metadata Management module can display relationships between objects (such as impact and lineage between objects). All categories and terms that Metapedia users create. All private and published cleansing packages that Cleansing Package Builder users create or refine.

You can either create a new database for the repository or use an existing repository. The Information Steward installation process will either create new tables or upgrade the existing tables within the repository. For information about managing the size of your Information Steward repository, see the Performance and Sizing Considerations section in the Administrator Guide. Related Topics Setting up a new database

4.2.1 Requirements for database types


The following table shows the requirements to use database types as the repository for SAP BusinessObjects Information Steward:

61

2011-08-19

Preparation

Database type

Requirements to use as repository for Information Steward

Microsoft SQL Server

Windows authentication Microsoft SQL Server validates the login account name and password using information from the Windows operating system.

Microsoft SQL Server authentication Microsoft SQL Server authenticates the existing Microsoft SQL Server login account name and password.

DB2

Server: DB2 database alias Login credentials used to access the database If you create a new DB2 8.x database: In the creation wizard, set the code set to UTF-8 or UTF-16. Create three buffer pools, one for each page size: 8K, 16K and 32K. The buffer pool size should be set to 1000. Create one temporary system table space for the 32K buffer pool. Create one regular table space for the 32K buffer pool. If you create a new DB2 9.x database: In the creation wizard, set the code set to UTF-8 or UTF-16 and the default buffer pool and table space page size to 32K. Server: TNSNAMES connect identifier Login credentials used to access the database Oracle JDBC driver

Oracle

Bundled database You can also use the default database that is bundled with SAP BusinessObjects Business Intelligence platform (Microsoft SQL Server 2008) or Information platform services (Microsoft SQL Server 2008) as the Information Steward repository host. Caution: If you use the bundled database as your Information Steward repository host, you must use the database client tools to manage backup and restore of the database. Be sure to back up your repository before uninstalling the BI platform. If you want to create another database within the bundled database server, you can download and install Microsoft SQL Server 2008 Management Console Express. For more information, see the Microsoft documentation. For more information about configuring the bundled database, see Configuring the bundled database in the SAP BusinessObjects Data Services Installation guide.

62

2011-08-19

Preparation

4.2.2 Extra requirements for Oracle


Information Steward requires a JDBC driver to connect to Oracle databases. If you want to use Oracle for the repository database: 1. Download the Oracle JDBC driver for your database and obtain a license for each host system in your Information Steward deployment. Information Steward requires the ojdbc14.jar driver. 2. Copy the .jar file to a local directory and make a note of the location. You will be asked to provide the location of the JDBC driver during the installation process.

4.2.3 Setting up a new database


This procedure creates a SAP BusinessObjects Information Steward repository database and configures it for the user who will connect to it. The installation process will create the tables within the Information Steward repository. 1. Create a new database on your database server. Compatible database types include DB2, Microsoft SQL Server, Oracle, and Oracle RAC. For the most current list of supported database software and version requirements, see the Product Availability Matrix available at http://service.sap/com/PAM. Note: For requirements specific to each database type, see Requirements for database types. 2. Create a new user and assign a secure password. 3. Ensure that the new user has permission to create, modify, and delete database objects so that Information Steward can modify the database as required. Note: If you are not the owner of the database, you must have permissions to perform the necessary operations.

4.3 Support for SAP System Landscape Directory (SLD)


SAP System Landscape Directory (SLD) is a directory service that maintains a list of installed SAP and (optionally) non-SAP software. SLD provides two main categories of information: Software already installed Software that could be installed at a later time

63

2011-08-19

Preparation

SAP systems come with a data supplier (DS) component that automatically updates the landscape directory. Non-SAP software that supports SLD registers through an open API. The information gathered on installed software includes: Version Host information Connection information To use SLD support, ensure that SAP Host Agent is installed and working on the system(s) that host SAP BusinessObjects Information Steward. SAP Host Agent may be installed and configured before or after installing SAP BusinessObjects Information Steward.

4.4 Installation scenarios


The following installation methods are available to you for installing SAP BusinessObjects Information Steward on Windows: Standard installation Installs from the installation wizard. Silent installation Installs from the command line. Upgrade Upgrades an existing SAP BusinessObjects Metadata Management XI 3.x repository to an SAP BusinessObjects Information Steward repository during installation. For information about upgrading your Metadata Management objects (such as integrator source configurations, source groups, and security information), see the Upgrade Guide. Remote Job Server installation Installs a Remote Job Server component for a Metadata Integrator to collect metadata from an SAP BusinessObjects Enterprise XI 3.x system. Distributed deployment Installs a subset of Information Steward components on each computer that has the prerequisite software.

Related Topics Standard installation To install a Remote Job Server Deployment

4.5 License keys


You purchase a license key for the SAP BusinessObjects Information Steward features that you want. To purchase license keys: Contact your sales representative. Contact your regional office.

64

2011-08-19

Preparation

Related Topics Updating the license key

65

2011-08-19

Preparation

66

2011-08-19

Installation

Installation

You can run the installation program several ways: Interactive installation An interactive wizard prompts for all information related to the installation. Use this option to select individual options from a series of screens. This is the default installation method. Silent installation Installation options are given on the command-line, which override the installation program's default values. The command-line can be used to give some or all installation options. When an installation option is not given on the command-line, the installation program uses a default value. Installation options can be given in a response file rather than directly on the command-line. 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. Installation options stored in the response file can be overridden by giving them on the command-line. When the -q (quiet mode) switch is used, the installation program does not prompt for any user input during the installation. When the installation program detects an identical previously-installed version, it will enter maintenance mode, allowing you to remove, repair, or modify the software.

5.1 Standard installation


To install the Information Steward system, you must use an account with administrative privileges. Note: This installation requires that you stop and start the Server Intelligence Agent (SIA). Users cannot access the Central Management System (CMS) while the SIA is stopped. Therefore, it is recommended that you perform this installation during scheduled down time to limit the effect on your users. When the Installer starts, a series of prerequisite checks are performed. The results of these checks are displayed for your information. If your system does not meet the minimum requirements, the installation program will not install SAP BusinessObjects Information Steward. Microsoft C++ redistributable components will be installed automatically if they are not found. 1. Start the installation program. a. Log in at the console or use Microsoft Remote Desktop connection with a minimum screen resolution of 1024 x 768.

67

2011-08-19

Installation

b. Locate the installation program. If you are installing from physical media, look for setup.exe in the top-level folder. If you are installing from a compressed download, extract it and locate setup.exe. Note: If you are running the installation program from a network location, use a mapped drive and not a UNC path. c. Run setup.exe by double-clicking it in Windows Explorer or calling it from the command-line. The setup language selection dialog box appears. 2. Choose a language for the setup program to use during the installation process. The language setting is used by the installation program to display information to you in the language of your choice. If you select a non-English language, the corresponding language pack is automatically installed on the server. For a complete list of supported languages, see the Product Availability Matrix available at http://service.sap.com/PAM. Note: The installation program will automatically run in the same language as your operating system. The language used by the installation program will determine the names used for Windows components configured by the installation program, such as Windows service names and Start menu shortcuts. These names cannot be changed later and are not affected by language settings once the installation is complete. The prerequisite check screen appears. 3. The installation program checks for required components. Review the results and decide whether to continue the installation, or abort and correct any unmet requirements. If a dependency prerequisite condition is critical, the installation program will not allow the installation to proceed. If the missing or unsupported component is optional you have the option to either continue with the installation setup or stop and correct the condition. The installation program will provide information on how to correct the condition. During a silent installation, the installation program does not display the results of dependency prerequisites. If a critical component or supported version is not found, the installation program writes an error to the installation log file and aborts. If an optional component or supported version is not found, the missing or unsupported component is noted in the installation log file. The welcome screen appears. 4. Review the recommendations made by the installation program welcome screen. The license agreement screen appears. 5. Review and accept the License Agreement. Note: You cannot continue unless you accept the License Agreement. The user information screen appears. 6. Enter the name, company, and the product key code that you purchased. Store the key code and registration information in a safe place in case you need to reinstall the software. The destination location screen appears.

68

2011-08-19

Installation

7. Specify the location where you want to install the software. Note: If you have other SAP BusinessObjects products already installed on the host machine, the destination folder cannot be changed. The language pack selection screen appears. 8. To install support for a language, select it from the list. The language currently being used by the operating system is selected automatically. English language support cannot be deselected because it is used when a problem is detected with an individual language. The install type selection screen appears. 9. Specify the install type. Select Primary Install to configure the repository during the install procedure. Typical scenarios include the following: Create a repository to overwrite an existing repository. Create a new repository on a system with no existing repository. Connect to an existing repository. Upgrade an existing Metadata Management 3.x repository. Note: This install type requires the Data Services Patch 0.3 (or newer) Job Server component to be installed on the local system. Select Expanded Install to install Information Steward application features without configuring the repository. Select this option if you already have an up-to-date version of the Information Steward repository. If the repository is not valid, an error will occur and you must select Primary Install. If you choose Expanded Install, the repository database connection screen and repository configuration option screen will not appear later in the installation process. Note: Expanded Install is not used for adding new Information Steward features to an existing install. For more information, see Installation. The Central Management Server (CMS) connection screen appears. 10. Enter administrator-level connection information for your CMS. a. If there are multiple Server Intelligence Agent (SIA) nodes configured, choose the SIA node to use with Information Steward. The Central Management Server (CMS) connection screen appears. b. If you are using an existing repository on Oracle, specify the location of the Oracle JDBC driver. Restriction: Information Steward supports only the Enterprise authentication method during installation. The Information Steward installation program does not support SSL for the CMS connection. To configure SSL after installation, see Configuring servers for SSL in the SAP BusinessObjects Business Intelligence Platform Administrator Guide.

69

2011-08-19

Installation

11. A warning that the Server intelligence Agent servers will be restarted appears. If no users are currently accessing the CMS, click Yes to continue. Otherwise, click No to abort the installation and start the Information Steward installation when no users are accessing the CMS. If you are continuing the installation, the feature selection screen appears. 12. Select the Information Steward components that you want to install. Note: If you deselect the Metadata Relationship Service, ensure that it is installed on at least one computer in your enterprise deployment. The Metadata Relationship Service is required to process relationships (such as impact and lineage) of metadata objects. The Information Steward web application option is available if you have installed the Web Application option in the SAP BusinessObjects BI platform software. The web application installation method is the same in both the BI platform and Information Steward. Therefore, the installer checks whether you have manually or automatically installed web services, and automatically chooses the same installation option in Information Steward. If you manually deployed the web applications for the BI platform, use WDeploy to manually deploy the Information Steward web applications after installation. Tip: To verify whether you have sufficient available disk space for the selected components, click Disk Cost. The repository database connection screen appears. 13. Enter the connection information for the Information Steward repository database. Note: If you use an MS SQL Server that uses an instance, you must enter the instance name in the Machine Name field, in the format server_name\instance_name. If a repository connected to the CMS is detected, the repository information is filled in automatically. This information can be changed if necessary. The repository configuration screen appears. 14. Choose Create repository to create a new Information Steward repository or Upgrade repository to upgrade an existing repository. Note: If you want to use an existing repository that has already been updated with the installation program, click Skip repository configuration. The start installation confirmation screen appears. 15. Click Next to begin the installation process. During the installation process, the installation program saves your installation selections in a cache, transfers files, and performs additional configuration actions. The installation completion screen appears.

70

2011-08-19

Installation

Related Topics Deploying web applications with WDeploy

5.1.1 When installation is complete


When the installation is complete, review the information in the "Post Installation Steps" screen. If you did not automatically deploy the bundled Tomcat web application server, you must deploy the web applications with the WDeploy web application deployment tool. If you will run Data Insight profiling and rule tasks, you must access the SAP BusinessObjects Data Services Server Manager to create a job server and associate it to the Information Steward repository. If you uninstalled Information Steward and installed it again to recreate the Information Steward repository, you must restart the Enterprise Information Management servers. Related Topics Deploying web applications with WDeploy Configuring a Data Services Job Server for Data Insight Restarting Enterprise Information Management Servers

5.2 Silent installation


Every option in the installation wizard can be given from the command-line. This type of installation is known as a silent install. Installation options can be given directly on the command-line as a parameter, or can be stored in a response file. Giving installation options on the command-line Installation options can be passed directly to the installation program from the command-line as a parameter. For example, the installation option ISCMSPort=6401 can be given on the command-line as a parameter when running the installation program to set the Central Management Server (CMS) port number to 6401, instead of the default value of 6400. In the following example of giving the ISCMSPort parameter on the command line, ellipses ([...]) indicate where other installation options would normally be present: setup.exe [...] ISCMSPort=6401 [...]

71

2011-08-19

Installation

Giving installation options in a response file Installation options can be stored in a response file, which is a text file containing installation option parameters in key-value format. When using a response file to give installation options, the installation program is run from the command-line with the -r <RESPONSE_FILE> parameter, where <RE SPONSE_FILE> is the name of the response file. The response file contains multiple installation options, with one installation option per line. In the following example, the response file is given as a parameter: setup.exe [...] -r C:\response.ini [...] For example, the installation option ISCMSPort=6401 can be given on a line in the response file to set the Central Management Server (CMS) port number to 6401, instead of the default value of 6400. In the following example of giving the ISCMSPort parameter in a response file, ellipses ([...]) indicate where other installation options would normally be present:
[...] ISCMSPort=6401 [...]

Note: The installation program returns the cursor to the command-line prompt when it starts. To run the installation program from a script, or force the installation program to wait until it has completed before returning to the command-line, use the Windows Command Interpreter start /wait command to invoke setup.exe. For example: start /wait setup.exe [<COMMAND_LINE_OPTIONS>] Related Topics Installation option parameters Response file example

5.2.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.

72

2011-08-19

Installation

Switch parameter Description

Example

-w <FILENAME>

Writes a response file to <FILENAME> setup.exe -w "C:\response.ini" , containing the options selected from the installation wizard. Reads installation options from a response file named <FILENAME>. setup.exe -r "C:\response.ini"

-r <FILENAME> -q

Installs with no console output or setup.exe -q -r "C:\re prompting. If a problem is encountered, sponse.ini" the installation program will write a message to the installation log file and exit.

5.2.1.1 To use a response file


To use a response file, run the installation program with the -r <RESPONSE_FILE> parameter. The installation program reads all installation options from the response file, and no further input is required. For example, the following command reads installation options from the response file C:\response.ini :
setup.exe -r C:\response.ini

To override an installation option in a response file, give that option on the command-line. Installation options given on the command-line take precedence over the options in the response file. For a complete list of installation options, see Installation option parameters. If an unexpected condition is encountered, the installation program writes an error message to the installation log file and exits. Installation activity, warnings, and errors are written to the installation log file in the folder: <INSTALL_DIR>\InstallData\logs\<DATE>\setupengine.log If the <INSTALL_DIR> folder has not been created by the time the installation program exits, look for setupengine.log in the temporary folder specified by the system TEMP environment variable. Related Topics Installation option parameters

5.2.1.1.1 To write a response file


To create a response file, run the installation program with the -w <RESPONSE_FILE> parameter and select the desired installation options with the installation wizard. When the wizard completes, the

73

2011-08-19

Installation

installation program exits and the response file is created. The response file can then be used for future installations. For example, the following command creates the response file C:\response.ini :
setup.exe -w C:\response.ini

Once created, the response file can be updated with a text editor. Caution: When you specify passwords in the installation program, they are stored in the response file in plain text. For security reasons, it is recommended that you remove the passwords from the response file and specify the parameters on the command-line instead. For example, locate ISCMSPassword=password in the response file, remove the password, and then specify it on the command-line:
setup.exe -r C:\response.ini ISCMSPassword=password

5.2.1.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. A response file installation is useful when setting up a cluster, or for creating development or test environments with standardized options. When an option is given both on the command-line and in a response file, the command-line options take precedence over the response file options. This feature allows an administrator to override an option in a response file when required, and provides three levels of precedence for installation options: 1. Installation options given on the command-line take highest precedence, and will always override response file and default values. 2. Installation options given in a response file are used when not given on the command-line, and override default values. 3. Installation option default values are used when not given on the command-line or in a response file. For example, the following command reads installation options from the response file C:\response.ini , but overrides the response file's setting for the installation destination folder:
setup.exe -r C:\response.ini InstallDir="C:\SAP\SAP BusinessObjects Information Steward\"

5.2.1.2 Quiet mode installations


A quiet mode installation is a command-line installation that does not prompt for installation options. Installation options must be provided on the command-line or in a response file. Any installation options not provided on the command-line or in a response file will be left at their default values.

74

2011-08-19

Installation

The -q switch bypasses the installation program's installation wizard, and allows an installation to be performed with no human input and no console output. For example, the following command installs the web tier and overrides the installation destination folder (set to C:\SAP\InformationSteward\ instead of the default folder).
setup.exe -q InstallDir="C:\SAP\InformationSteward\" features=WebTier productkey=XXXXX-XXXXXXX-XXXXXXX-XXXX selectedlanguagepacks=en setupuilanguage=en

If an unexpected condition is encountered, an error message is written to the installation log file and the installation program exits. Installation activity, warnings, and errors are written to the installation log file in the folder: <INSTALL_DIR>\InstallData\logs\<DATE>\setupengine.log If the <INSTALL_DIR> folder has not been created by the time the installation program exits, look for setupengine.log in the temporary folder specified by the system TEMP environment variable. Note: If you are installing SAP BusinessObjects Information Steward on a Windows 7 or Vista system that has User Account Control (UAC) enabled, you should run the installation program with the system's built-in administrator account. If you use a normal account, a UAC prompt will appear.

5.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.

Table 5-1: Installation option parameters


Parameter Description

SetupUILanguage=<CODE>

Determines the language for the installation program to use during the installation. Substitute the language code where <CODE> is: English: EN Destination folder into which the installation program will install the software. When installing to a host that already has an installation of SAP BusinessObjects Data Services, SAP BusinessObjects BI platform, or SAP BusinessObjects Information platform services, the value of InstallDir will be automatically set to the same path as the existing installation.

InstallDir=<PATH>

75

2011-08-19

Installation

Parameter

Description

SelectedLanguagePacks=<CODE>

Installs language support for users and administrators to interact with SAP BusinessObjects Information Steward in a supported language. If more than one language pack is to be installed, use a semicolon delimited list without spaces, within quotes, to separate each code. In the following example, 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. Substitute <NAME> with the name. Name of the company to whom the software is registered. Substitute <NAME> with the name. Product license key issued when you purchased the software. Substitute <KEY> with the product key in the format XXXXXXXXXXX-XXXXXX-XXXX. The Information Steward install type. Substitute <TYPE> with First for Primary Install or Expand for Expanded Install. Authentication type used by the Central Management Server (CMS). Substitute the authentication type where <TYPE> is: Enterprise authentication: secEnterprise Note: This value must match the value specified for ISCMSAuth. Restriction: Information Steward supports only the Enterprise authentication method during installation. CMSUserName=<USER> User name for the CMS administrator account. Substitute <USER> with the user name. Note: This value must match the value specified for ISCMSUser. CMSPassword=<PASSWORD> Password for the CMS administrator account. Substitute <PASS WORD> with the password. Note: This value must match the value specified for ISCMSPassword.

RegisteredCompany=<NAME>

ProductKey=<KEY>

InstallType=<TYPE>

CMSAuthentication=<TYPE>

76

2011-08-19

Installation

Parameter

Description

ISCMSAuth=<TYPE>

Authentication type used by the Central Management Server (CMS). Substitute the authentication type where <TYPE> is: Enterprise authentication: secEnterprise Note: This value must match the value specified for CMSAuthentica tion. Restriction: Information Steward supports only the Enterprise authentication method during installation.

ISCMSUser=<USER>

User name for the CMS administrator account. Substitute <USER> with the user name. Note: This value must match the value specified for CMSUserName.

ISCMSPassword=<PASSWORD>

Password for the CMS administrator account. Substitute <PASS WORD> with the password. Note: This value must match the value specified for CMSPassword.

ISCMSPort=<PORT>

Network TCP listening port number used by the Central Management Server (CMS). Substitute <PORT> with the port number. Note: This value must match the value specified for MasterCMSPort.

ISCMSSystem=<HOST>

Hostname of the Central Management Server (CMS). Substitute <HOST> with the CMS hostname. Note: This value must match the value specified for MasterCMSName.

ISCMSSystemStr=<STRING>

Complete system string for the Central Management Server (CMS). Substitute <STRING> with the CMS hostname and port in the format hostname:port. Note: This value must match the values specified for ISCMSSystem and ISCMSPort.

77

2011-08-19

Installation

Parameter

Description

ISEnableSSL=<SWITCH>

Specifies whether the Central Management Server (CMS) uses SSL security. If the CMS is configured for SSL support, set <SWITCH> to 1. If the CMS is not configured for SSL support, set <SWITCH> to 0. Restriction: Information Steward does not support SSL for the CMS. ISEnab leSSL must be set to 0.

ISMoreThanOneSIANode=<SWITCH>

Specifies whether the Central Management Server (CMS) has more than one local Server Intelligence Agent (SIA) node configured. If more than one SIA node is configured, set <SWITCH> to 1. If only one SIA node is configured, set <SWITCH> to 0. Specifies whether the InfoObjects are already present in the CMS and are up to date. If the InfoObjects are already present in the CMS, set <SWITCH> to 1. If the InfoObjects are not present, set <SWITCH> to 0. Connection string used to connect to an Oracle repository database. Substitute <VALUE> with the connection string. Hostname for the database server that will contain the Information Steward repository. Substitute <HOST> with the hostname. Note: This value must match the value specified for ISRepoDBHostStr.

ISRepoAvailable=<SWITCH>

ISRepoConnStr=<VALUE>

ISRepoDBHost=<HOST>

ISRepoDBHostStr=<VALUE>

Hostname for the database server that will contain the Information Steward repository. Substitute <HOST> with the hostname. Note: This value must match the value specified for ISRepoDBHost.

ISRepoDBName=<NAME>

Database name for the database that will contain the Information Steward repository. Substitute <NAME> with the database name. Password for the database account that will be used to access the repository database. Substitute <PASSWORD> with the account password. Network TCP listening port number used by the database that will host the Information Steward repository. Substitute <PORT> with the port number.

ISRepoDBPasswd=<PASSWORD>

ISRepoDBPort=<PORT>

78

2011-08-19

Installation

Parameter

Description

ISRepoDBType=<TYPE>

Type of database that will host the Information Steward repository. Substitute the database type where <TYPE> is: Microsoft SQL Server: Microsoft_SQL_Server Oracle: Oracle DB2: DB2 Sybase ASE: Sybase User name for the database account that will be used to access the repository database. Substitute <USER> with the account user name. Connection string used to connect to an ODBC repository database. Substitute <VALUE> with the connection string. Specifies the repository operation to perform during installation. Substitute the operation where <VALUE> is: Create a new repository: Create Upgrade an existing repository: Upgrade Skip repository creation: Skip Specifies the name of the local Server Intelligence Agent (SIA) node, which points to the specified Central Management Server (CMS). Substitute <NODE> with the SIA node name. Hostname of the Central Management Server (CMS). Substitute <HOST> with the CMS hostname. Note: This value must match the value specified for ISCMSSystem.

ISRepoDBUser=<USER>

ISRepoODBCStr=<VALUE>

ISRepoOption=<VALUE>

ISSIANode=<NODE>

MasterCMSName=<HOST>

MasterCMSPort=<PORT>

Network TCP listening port number used by the Central Management Server (CMS). Substitute <PORT> with the port number. Note: This value must match the value specified for ISCMSPort.

Features=<CODE>

List of components to install. To select multiple features, use a comma-delimited list without spaces to give each code. In the following example, the web tier and Task Server will be selected for install:
Features=WebTier,TaskServer

For a complete list of feature codes, see Feature codes.

79

2011-08-19

Installation

5.2.2.1 Feature codes


Use the following feature codes to select features for installation. To select multiple features, separate each feature code with a comma, without spaces. For example, the following feature list selects the web tier and documentation files:
features=WebTier,Documentation

root WebTier TaskServer ISServices RelationshipServer SearchServer CPBServices BOEIntegrator BWIntegrator DFIntegrators BODIIntegrators CWMIntegrators RDBMSIntegrators MITIIIntegrators

Integrators

5.2.2.2 Response file example


The following example response file contains options for installing SAP BusinessObjects Information Steward. Example: In this example, the response file is named C:\response.ini.
### #property.CMSAUTHENTICATION.description# cmsauthentication=secEnterprise ### #property.CMSPassword.description# cmspassword=cmspassword ### #property.CMSUSERNAME.description# cmsusername=Administrator

80

2011-08-19

Installation

### Installation directory installdir=C:\Program Files (x86)\SAP BusinessObjects\ ### #property.CMSAuthMode.description# iscmsauth=Enterprise ### #property.CMSPassword.description# iscmspassword=cmspassword ### #property.CMSServerPort.description# iscmsport=6400 ### #property.CMSSystem.description# iscmssystem=localhost ### #property.CMSSystemStr.description# iscmssystemstr=localhost ### #property.CMSUser.description# iscmsuser=Administrator ### #property.EnableSSL.description# isenablessl=0 ### #property.ISMoreThanOneSIANode.description# ismorethanonesianode=0 ### #property.ISRepoAvailable.description# isrepoavailable=false ### #property.RepoConnStr.description# isrepoconnstr= ### #property.RepoDBHost.description# isrepodbhost=repo_host ### #property.RepoDBHostStr.description# isrepodbhoststr=repo_desc ### #property.RepoDBName.description# isrepodbname=repo_name ### #property.RepoDBPasswd.description# isrepodbpasswd=dbpassword ### #property.RepoDBPort.description# isrepodbport=1433 ### #property.RepoDBType.description# isrepodbtype=MS SQL Server 2005 ### #property.RepoDBUser.description# isrepodbuser=dbuser ### #property.RepoOdbcStr.description# isrepoodbcstr= ### #property.ICCRepoOption.description# isrepooption=Create ### #property.SIANode.description# issianode=sianode ### #property.MasterCmsName.description# mastercmsname=localhost ### #property.MasterCmsPort.description# mastercmsport=6400 ### Product keycode productkey=XXXXX-XXXXXXX-XXXXXXX-XXXX ### Registered Company registeredcompany=Company Name ### Registered User registereduser=User Name

81

2011-08-19

Installation

### #property.SelectedLanguagePack.description# selectedlanguagepacks=en ### Setup UI language setupuilanguage=en ### #property.SIAName.description# sianame=pubsboe ### Available features ### -----------------### root ### WebTier ### TaskServer ### ISServices ### RelationshipServer ### SearchServer ### CPBServices ### Integrators ### BOEIntegrator ### BWIntegrator ### DFIntegrators ### BODIIntegrators ### CWMIntegrators ### RDBMSIntegrators ### MITIIntegrators features=WebTier,TaskServer,RelationshipServer,SearchServer,CPBServices,ISServices,BOEIntegrator,BWIntegra tor,DFIntegrators,BODIIntegrators,CWMIntegrators,RDBMSIntegrators,MITIIntegrators

82

2011-08-19

Post-Installation

Post-Installation

This section describes the activities that should be performed after the installation program has finished.

6.1 Configuring a Data Services Job Server for Data Insight


If you will run Data Insight profile and rule tasks, you must access the Data Services Server Manager to create a job server and associate it with the Information Steward repository. This association adds the job server to a pre-defined Information Steward job server group that Data Insight will use to run tasks. For details about how job server groups improve performance, see the Performance and Sizing Considerations section in the Administrator Guide. To configure a job server and associate it with the Information Steward repository: 1. Access the Data Services Server Manager from the Windows Start menu: Start > Programs > SAP BusinessObjects Data Services XI 4.0 > Data Services Server Manager 2. On the "Job Server" tab, click Configuration Editor. 3. On the "Job Server Configuration Editor" window, click Add. 4. In the "Job Server Properties" window, enter a name for Job Server name. 5. In the "Associated Repositories" section, click Add and fill in the "Repository Information" of the Information Steward repository that you want to associate with this Job Server. Database type Database Server name Database name Username Password 6. Click Apply and OK. The "Job Server Configuration Editor" window now displays the job server you just added. 7. Click Close and Restart to restart the job server with the updated configurations. For more information about using the Data Services Server Manager, see Server management in the SAP BusinessObjects Data Services Administrator's Guide.

83

2011-08-19

Post-Installation

6.2 Updating the license key


Situations when you might need to update your license key code for SAP BusinessObjects Information Steward include the following: Update an expired key code Upgrade from a trial version Include additional features that you have purchased To update the license key: 1. Go to the "License Keys" management area of the CMC. 2. If you are upgrading from a trial version of the product, be sure to delete the Evaluation key prior to adding any new license keys or product activation key codes. a. From the list of key codes, select the Evaluation key code. b. Click Delete. 3. Type the new key in the Add Key field. 4. Click Add. The key is added to the list.

6.3 Deploying web applications with WDeploy


WDeploy is installed as a part of the SAP BusinessObjects BI platform to aid in the deployment of web applications to Java-based web application servers. WDeploy provides a graphical method of running the wdeploy deployall or wdeploy undeployall commands. To perform other deployment operations, such as deploying one web component at a time, use the command-line mode. WDeploy defaults to an English interface, but prompts the user to choose a language if any language packs are installed and the tool is run for the first time. The following languages are supported: English

6.3.1 WDeploy prerequisites


To use WDeploy, ensure that the following requirements are met:

84

2011-08-19

Post-Installation

When using WebSphere 6 or WebSphere 7 with a non-default profile name (a profile name that isn't set to AppSrv01), manually update the as_profile_name parameter in the config.websphereX configuration file before launching WDeploy. For example: 1. Update as_profile_name in config.websphereX. By default, the configuration file is found in <BIP_INSTALL_DIR>\wdeploy\conf . 2. Launch WDeploy. 3. Select WebSphere 6 or WebSphere 7 and provide all parameters. 4. Perform the deployment. For information on giving the profile name with the WDeploy command-line mode, see the WebSphere 6 or WebSphere 7 configuration file.

Set the JAVA_HOME environment variable to the desired JDK folder. For example, JAVA_HOME may be set to: <BIP_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\java Or: <BIP_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\win64_x64\jdk

Ensure that the host system has at least 5 GB of free space for the deployment of web applications. For example, ensure that there is at least 5 GB available on the drive defined in the TEMP environment variable.

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 4 GB of RAM. When using SAP NetWeaver AS Java 7.2, ensure that the host system has at least 8 GB of RAM. Ensure that the host web application server minimum heap size (-Xms), maximum heap size (-Xmx), and Permanent Generation (-XX:MaxPermSize) settings are configured. For example: JAVA_OPTS=-Xms128m -Xmx1024m -XX:MaxPermSize=512m Note: For SAP NetWeaver AS 7.2, ensure that the maximum heap size is at least 2048 megabytes: JAVA_OPTS=-Xms128m -Xmx2048m -XX:MaxPermSize=512m

6.3.2 To start WDeploy


Run WDeploy by selecting Start > Programs > SAP BusinessObjects Enterprise XI 4.0 > WDeploy. It can also be started by running <BIP_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\wdeploy\wdeployGUI.bat.

85

2011-08-19

Post-Installation

Note: If you are using SAP BusinessObjects Information platform services instead of the SAP BusinessObjects BI platform, WDeploy is found in the Information platform services program group. When WDeploy is run for the first time, it prompts for which language to use for displaying information in the user interface. Select a language and continue.

6.3.3 To deploy or undeploy components


WDeploy allows users to deploy and undeploy all web applications to a web application server. Any web applications not deployed by the SAP BusinessObjects BI platform installation program or WDeploy will be unaffected. Note: Not all web applications are deployed automatically. Web applications that are not deployed automatically must be deployed with the WDeploy command-line mode or with the web application server administrative console. 1. 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. Select a supported web application server from the Select Web Application Server Type drop-down. Before deploying or undeploying web applications to a web application server, ensure that the WDeploy web application server configuration file (config.<WEB_APP_SERVER>) is correctly configured. By default, the configuration files are found in <BIP_INSTALL_DIR>\wdeploy\conf . 3. When a web application server is selected, 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. 4. For more advanced options, select Options.

6.3.4 Advanced options


The WDeploy Options screen allows you to select custom folders to use for the deployment of web applications.

86

2011-08-19

Post-Installation

Option

Description

Select WDeploy work directory

The folder in which WDeploy manipulates the web applications WAR or EAR archives (for example, to split static and dynamic content in a web application). This folder stores the results of the wdeploy predeploy action, and stores data required to undeploy web applications. Example value: <BIP_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\wdeploy\workdir The location of source used to create WAR or EAR.

Select Source location of web applications: Web application source tree location

Example value: <BIP_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\wdeploy\warfiles\webapps The location of source content used to create WAR.

Select Source location of web applications: Generic WAR files location

Example value: <BIP_INSTALL_DIR>\SAP BusinessObjects Enterprise XI 4.0\java\apps The web application root context path to which all web applications are deployed.

Web applications root context

Example value: \BOE

Note: Non-English characters are not valid in paths used in WDeploy.

6.3.5 To run WDeploy from the command line


Use the wdeploy command-line tool to deploy the Information Steward web application components to a web application server and perform other advanced deployment functions unavailable in the GUI tool. For Information Steward, there are multiple components that you must deploy:

87

2011-08-19

Post-Installation

BOE CPBWebservice

By default, the Wdeploy tool and the web components are installed to the following locations during the. SAP BusinessObjects BI platform installation: wdeploy: <BIP_INSTALL_DIR>\wdeploy web components: <BIP_INSTALL_DIR>\warfiles\webapps Syntax wdeploy <server_type> [-Das_admin_password=<password>] [-DAPP= <app_name>] <command>

88

2011-08-19

Post-Installation

Parameter

Description

<server_type>

Specifies the type of 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. Note: For Tomcat web application servers, the password is not required.

-DAPP=<app_name> Specifies the web application component to deploy. Available values for <app_name> include: <command> BOE CPBWebservice

Specifies the command for wdeploy to execute. Available values for <command> include: deploy Prepares and deploys a single web application component to the web application server. 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. undeployall Removes all web application components from the web application server.

89

2011-08-19

Post-Installation

6.3.5.1 To configure WDeploy


To configure the wdeploy configuration file to specify the web application server settings: 1. Open the configuration file for your web application server. By default, the configuration files are installed to <BIP_INSTALL_DIR>\wdeploy\conf . Available configuration files include: config.sapappsvr72 config.tomcat55 config.tomcat6 config.weblogic9 config.weblogic10 config.websphere6 config.websphere7 2. Set the parameters to match your application server settings. 3. Save and close the configuration file.

6.3.5.2 To deploy all web components


Deploying all web components deploys BOE and CPBWebservice, in addition to any other SAP BusinessObjects web application components available on the host system. To deploy all web content: 1. Access <BIP_INSTALL_DIR>\wdeploy from the command prompt. 2. Run wdeploy with the deployall command: wdeploy <server_type> deployall -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 deployed to the web application server. Example: WebSphere 6 wdeploy websphere6 deployall -Das_admin_password=mypass Note: After you deploy the web applications on Tomcat, you must restart the Tomcat application server for the changes to take effect.

90

2011-08-19

Post-Installation

6.3.5.3 To deploy one web component


To deploy a single web application component: 1. Access <BIP_INSTALL_DIR>\wdeploy from the command prompt. 2. Run wdeploy with the deploy command and the -DAPP=<app_name> parameter: wdeploy <server_type> -Das_admin_password=<password> -DAPP=<app_name> de ploy 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 deployed to the web application server Example: CPBWebservice on WebLogic 10 wdeploy weblogic10 -Das_admin_password=mypass -DAPP=CPBWebservice deploy Note: After you deploy the web application on Tomcat, you must restart the Tomcat application server for the changes to take effect.

6.3.5.4 To verify deployment


To verify the deployment was performed properly: 1. Check whether the web applications have been deployed to the correct location. On Tomcat: $CATALINA_HOME/webapps On WebSphere: <server_folder>/installedApps/<Node_Cell_folder> For example, C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\in stalledApps\SHG-D-01-CGAONode01Cell On WebLogic: <server_folder>/stage/

91

2011-08-19

Post-Installation

For example, C:\bea\wlserver_10.0\samples\domains\wl_server\servers\examp lesServer\stage 2. Log in to Information Steward. 3. Verify that the web application initializes properly. All cleansing packages should be retrieved and displayed. 4. (Optional) Perform additional tasks in Cleansing Package Builder. Search Open a cleansing package Create a cleansing package

6.3.5.5 To undeploy all web components


Undeploying all web components undeploys BOE and CPBWebservice, in addition to any other SAP BusinessObjects web application components deployed on the host system. To undeploy all web components: 1. Access <BIP_INSTALL_DIR>\wdeploy from the command prompt. 2. Run wdeploy with the undeployall command: wdeploy <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 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.3.5.6 To undeploy one web component


To undeploy a single web component: 1. Access <BIP_INSTALL_DIR>\wdeploy from the command prompt.

92

2011-08-19

Post-Installation

2. Run wdeploy with the undeploy command and the -DAPP=<app_name> parameter: wdeploy <server_type> -Das_admin_password=<password> -DAPP=<app_name> un deploy 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: CPBWebservice on WebLogic 10 wdeploy weblogic10 -Das_admin_password=mypass -DAPP=CPBWebservice undeploy Note: After you undeploy the web application on Tomcat, you must restart the Tomcat application server for the changes to take effect.

6.3.6 Troubleshooting

6.3.6.1 To deploy web applications in a distributed environment


In a distributed deployment where the Information Steward 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 Information Steward InfoObjects

BI platform web tier Information Steward web applications

To manually deploy the Information Steward 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/.

93

2011-08-19

Post-Installation

2. Use wdeploy to deploy the BOE web application on Host A: Deploy all SAP BusinessObjects web applications from the command-line or GUI. Or Deploy only the BOE web application from the command-line.

Related Topics Deploying web applications with WDeploy To deploy all web components To deploy one web component

6.4 Verifying Information Steward servers are running


To verify that the SAP BusinessObjects Information Steward servers are running and enabled: 1. From the CMC Home page, go to the "Servers" management area. 2. Expand the Service Categories node and select Enterprise Information Management Servers. The list of servers in the right pane includes a State column that provides the status for each server in the list. 3. Verify that the following Enterprise Information Management Servers are Running and Enabled. "EIMAdaptiveProcessingServer" "ISJobServer" 4. If a Enterprise Information Management Servers server is not running or enabled, do the following: a. Select the server name from the list. b. Open the Actions drop-down menu and select Start Server or Enable Server. For information about the services that run under Enterprise Information Management Servers, see the Architecture section. Related Topics Services

6.5 Verifying Information Steward services


To verify that the SAP BusinessObjects Information Steward services were added: 1. Access the Central Management Console (CMC) on SAP BusinessObjects Business Intelligence platform or SAP BusinessObjects Information platform services.

94

2011-08-19

Post-Installation

2. From the CMC Home page, go to the "Servers" management area. 3. Expand the Service Categories node and select Enterprise Information Management Services. The right pane lists the following servers: "EIMAdaptiveProcessingServer" "ISJobServer" 4. Ensure that the relevant services appear for "EIMAdaptiveProcessingServer". a. Right-click "EIMAdaptiveProcessingServer" and click Stop Server. b. Right-click "EIMAdaptiveProcessingServer" and click Select Services. c. Verify that for each Information Steward feature that you installed, the list of services for EIMAdaptiveProcessingServer includes the following services:
Services Feature Installed EIM Adaptive Processing Server Information Steward Job Server (ISJobServer)

Information Steward Task Server Information Steward Admin Task Service

Information Steward Task Scheduling Service Information Steward Integrator Scheduling Service

Metadata Relationship Service Metadata Search Service

Information Steward Metadata Relationship Service Information Steward Metadata Search Service Cleansing Package Builder Auto-analysis service Cleansing Package Builder Core service Cleansing Package Builder Publishing service

None None

Cleansing Package Builder Service

None

All Metadata Integrators None

Information Steward Integrator Scheduling Service Information Steward Integrator Service

d. If any of the EIMAdaptiveProcessingServer services are not in the list on the right, select the service name from the "Available services" list on the left, click > to add it, and click OK. e. Right-click "EIMAdaptiveProcessingServer" and click Start Server. 5. Ensure that the relevant services appear for "ISJobServer". a. Right-click "ISJobServer" and click Stop Server. b. Right-click "ISJobServer" and click Select Services.

95

2011-08-19

Post-Installation

c. Verify that for each Information Steward feature that you installed, the list of services for "ISJobServer" includes the services listed in the table in step 3c. d. If any of the "ISJobServer" services are not in the list on the right, select the service name from the "Available services" list on the left, click > to add it, and click OK. e. Right-click "ISJobServer" and click Start Server.

6.6 Verifying Data Insight installation


To validate the installation of the Data Insight component: 1. Log in to the Central Management Console (CMC). 2. Create a connection, test, and save it. 3. Log in to Information Steward. 4. In the Data Insight tab, browse and import a table from the connection using the Enterprise Project. 5. View the table data. 6. Single profile the table. 7. Delete the table from the project.

6.7 Verifying Metadata Management installation


To validate the installation of the Metadata Management component: 1. Log in to the Central Management Console (CMC). 2. Create an RDB Integrator source using a small repository, test and save it. 3. Run the Integrator source and wait until it finishes successfully. 4. Log in to Information Steward. 5. In the Metadata Management tab, browse the contents of the Integrator source. 6. Search for a table name and validate the result. 7. View the lineage diagram for a view or table.

6.8 Installing SAP-supplied cleansing packages


Cleansing packages can be installed on Windows, AIX, Solaris and Linux. Before you install SAP-supplied cleansing packages, 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.com/bosap-downloads.

96

2011-08-19

Post-Installation

Installed SAP BusinessObjects Data Services. (Optional) Installed SAP BusinessObjects Information Steward. The Cleansing Package Builder module of Information Steward is required in order to modify an SAP-supplied cleansing package.

Note: Before installing, download the files to the local hard drive. SAP supplies person and firm cleansing packages for a variety of regions. 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. Installing a cleansing package makes it available in the Data Cleanse transform in Data Services and also in Information Steward Cleansing Package Builder. Note: The Cleansing Package installer will restart the Server Intelligence Agent (SIA). When this occurs, all users currently logged into the SAP BusinessObjects Business Intelligence platform Central Management Server (CMS) may encounter a disruption in service. To minimize the disruption to your CMS users, plan for this downtime at a convenient time for them. The service interruption occurs only during the initial installation. Subsequent installation of additional cleansing packages do not require an SIA restart. To install SAP-supplied cleansing packages: 1. Access to the directory where you downloaded cleansing packages from the SAP Service Marketplace, and double-click the setup.exe file to start the installer. The Data Quality Management cleansing packages installation wizard starts. 2. Read the explanatory text on screen. 3. Review and accept the license agreement. 4. Choose Data Services / Information Steward. 5. Enter your login information. This login information is for the administrator-level SAP BusinessObjects BI platform Central Management Server (CMS).
Option Description

System Enable SSL User Name Password Authentication

Name of the server hosting the CMS. SSL is required and cannot be changed here. CMS user name. Password corresponding to your CMS user name. Enterprise authentication is required and cannot be changed here.

6. Choose the cleansing packages that you want to install. If you choose to install cleansing packages that already exist on your Central Management Server, a warning message appears. If you choose to proceed, the installer overwrites the existing cleansing packages. 7. To learn how much disk space is needed for this installation and how much disk space is available, click the Disk Cost button. 8. Proceed until installation is complete.

97

2011-08-19

Post-Installation

The cleansing packages that you selected are now installed and available for you to use. Related Topics Modifying cleansing packages Uninstalling cleansing packages

6.9 Modifying cleansing packages


After you have installed some cleansing packages, you may want to install additional cleansing packages, or remove some cleansing packages that you installed previously. To add or remove cleansing packages: 1. Access to the directory where you downloaded cleansing packages from the SAP Service Marketplace, and double-click the setup.exe file to start the installer. The Data Quality Management cleansing packages installation wizard starts. 2. Select Modify. 3. Enter administrator-level SAP BusinessObjects BI platform Central Management Server (CMS) login information.
Option Description

System Enable SSL User Name Password Authentication

Name of the server hosting the CMS. SSL is required and cannot be changed here. CMS user name. Password corresponding to your CMS user name. Enterprise authentication is required and cannot be changed here.

4. Choose the cleansing packages that you want to install or uninstall. Note: During one instance, you can either install or uninstall cleansing packages. You cannot install and uninstall at the same time. We recommend that you first install the cleansing packages, and then run the installer again to remove cleansing packages. We recommend only uninstalling cleansing packages using the installer. If you modify the installed cleansing packages, and then uninstall using the installer, you will still see the modified cleansing packages in the CMC. Only use the CMC to delete modified cleansing packages. If you have not modified the cleansing packages, and then uninstall using the installer, the cleansing packages are automatically removed from the CMC. If you want to install the cleansing package that you previously deleted in the CMC, you may not see it in the list of cleansing packages available during the install. First, remove the cleansing

98

2011-08-19

Post-Installation

package with the installer. Run the installer again, and then you will see the cleansing package available. If you choose to install cleansing packages that already exist on your Central Management Server, a warning message appears. If you choose to proceed, the installer overwrites the existing cleansing packages. 5. Proceed until installation is complete. Related Topics Installing SAP-supplied cleansing packages Uninstalling cleansing packages

6.10 Uninstalling cleansing packages


We recommend only uninstalling cleansing packages using the installer. If you modify the installed cleansing packages, and uninstall using the installer, you will still see the modified cleansing packages in the CMS. Only use the CMS to delete modified cleansing packages. To uninstall cleansing packages: 1. Access to the directory where you downloaded cleansing packages from the SAP Service Marketplace, and double-click the setup.exe file to start the installer. The Data Quality Management cleansing packages installation wizard starts. 2. Select Remove. 3. Enter administrator-level SAP BusinessObjects BI platform Central Management Server (CMS) login information.
Option Description

System Enable SSL User Name Password Authentication

Name of the server hosting the CMS. SSL is required and cannot be changed here. CMS user name. Password corresponding to your CMS user name. Enterprise authentication is required and cannot be changed here.

4. Choose the cleansing packages that you want to uninstall. 5. Proceed until uninstallation is complete. Note: If you modified the cleansing packages, in addition to uninstalling with this installer, you must also uninstall the cleansing packages from the Central Management Server. If you have not modified the cleansing packages, they are automatically uninstalled from the CMS.

99

2011-08-19

Post-Installation

Related Topics Installing SAP-supplied cleansing packages Modifying cleansing packages

6.11 Metadata Integrator server groups


The SAP BusinessObjects Information Steward installer creates a new server group when a new Inte grator is deployed. For example, the Server Group BusinessObjects Enterprise Metadata Integrator is created for the SAP BusinessObjects Enterprise Integrator. this server group is used by the scheduler to run the integrator process on the correct Information Steward Job Server. You must not create, replace or change a deployed Information Steward Server Group. Doing so could cause the Information Steward Job Server to stop working. In this case, you must re-install the Integrators.

6.12 Restarting Enterprise Information Management Servers


If you uninstalled Information Steward and installed it again to recreate the Information Steward repository, you must restart the Enterprise Information Management servers. 1. Go to the "Servers" management area of the CMC. 2. Expand the Service Categories node and select Enterprise Information Management Servers. 3. Select all servers in the right pane, right-click and select Restart Server.

6.13 Uninstalling Information Steward


You might want to uninstall SAP BusinessObjects Information Steward for reasons such as the following: You want to move the software from one host system to another. You want to move a particular Information Steward component to a more powerful host system. You do not want to have Information Steward components installed on a particular host system. Note: Uninstalling Information Steward removes the Information Steward integrator configurations. To keep the existing integrator configurations, do not uninstall Information Steward but install another version on top of an existing version (for example install Metadata Management 12.1 on top of 12.0) and select the Upgrade repository option. To uninstall Information Steward:

100

2011-08-19

Post-Installation

1. Go to Start > Settings > Control Panel > Add/Remove Programs (or Change/Remove Programs). 2. Select SAP BusinessObjects Information Steward, and click Remove. Note: After you uninstall Information Steward, the Information Steward directory in the Business Objects installation directory is not deleted because the following files are not removed: zip files in ccmrestore/integrators MM/config/InfoObjectDelee.list files in MM/log files in MM/xml

6.14 Uninstalling specific components


You might want to uninstall specific components of SAP BusinessObjects Information Steward if you want to deploy them on a different host system. To uninstall specific components: 1. Run the SAP BusinessObjects Information Steward installation program. 2. At the "BusinessObjects Business Intelligence Platform Server Login" window, specify connection information for your SAP BusinessObjects Central Management Server (CMS). 3. At the "Select Features"" window, deselect components that you want to remove from this host system. Note: If you uninstall any of the Metadata Integrator components, the Information Steward Job Server will be deleted and the Metadata Integrator binary files will be removed from the installation directory. However, the integrator configurations in the CMS repository will not be removed. If you uninstall the Information Steward CMS Repository Objects component, all integrator configurations and other components in the CMS Repository will be removed.

4. Complete the remaining windows of the installation program. Related Topics Standard installation

101

2011-08-19

Post-Installation

102

2011-08-19

Additional installation scenarios

Additional installation scenarios

7.1 Remote Job Server Installation


The SAP BusinessObjects Enterprise Metadata Integrator in SAP BusinessObjects Information Steward 4.0 can collect metadata from an SAP BusinessObjects Enterprise XI 3.x system by using the Remote Job Server. If you want to collect metadata from an SAP BusinessObjects Enterprise XI 3.x system, you must perform the following tasks: 1. Install the Information Steward Remote Job Server and the SAP BusinessObjects Enterprise Metadata Integrator on a computer that has SAP BusinessObjects Enterprise XI 3.x full client and server components installed. Note: If any of your Crystal Reports or Web Intelligence documents were created with the Refresh on Open option, you must also configure the database clients to connect to the source databases. This connection is required because whenever the report or document is opened (even to read the metadata when the SAP BusinessObjects Enterprise Metadata Integrator collects the metadata), SAP BusinessObjects Enterprise XI 3.x automatically refreshes the data. 2. Configure the Remote Job Service to accept requests from SAP BusinessObjects Business Intelligence platform 4.0 to run the SAP BusinessObjects Enterprise Metadata Integrator on SAP BusinessObjects Enterprise XI 3.x. Related Topics To install a Remote Job Server To modify the configuration of a Remote Job Service

7.1.1 To install a Remote Job Server


Perform this SAP BusinessObjects Information Steward Remote Job Server installation on a computer that has SAP BusinessObjects Enterprise XI 3.x full client and server components installed.

103

2011-08-19

Additional installation scenarios

During installation, you configure the Information Steward Remote Job Service to accept requests from SAP BusinessObjects Information Steward through SAP BusinessObjects Business Information Platform 4.0 to run the Metadata Integrator on SAP BusinessObjects Enterprise XI 3.x. 1. On the computer where SAP BusinessObjects Enterprise XI 3.x is installed, perform the first few steps of a standard installation for Information Steward. 2. At the "BusinessObjects Enterprise Server Login" window, specify the logon information for the CMS system that you will use to configure and schedule integrator source runs. Restriction: The Information Steward installation program does not support SSL for the CMS connection. To configure SSL after installation, see Configuring the Remote Job Server for SSL in the Administrator Guide. If the Installation Wizard detects that SAP BusinessObjects Enterprise XI 3.x is installed on this computer, the "Select Features" window shows only the SAP BusinessObjects Enterprise Metadata Integrator component enabled. 3. If you are using an existing repository on Oracle, specify the location of the Oracle JDBC driver on the "JDBC Driver Path" window. 4. In the "Select Features" window, keep the SAP BusinessObjects Enterprise Metadata Integrator component selected and click Next. 5. On the "Configure BusinessObjects Information Steward Remote Job Server service port" screen, verify the port number that the Remote Job Service will use to listen for requests from the BI platform to run the Metadata Integrator. If you do not want the default port number 5005, enter a new value. 6. Click Next. 7. On the "Start Installation" screen, verify that the Remote Job Server displays in the list of "Components selected for installation" and click Next. The "Updating System" window shows the progress of copying the files. Related Topics Standard installation To modify the configuration of a Remote Job Service

7.1.2 To modify the configuration of a Remote Job Service


After you install the SAP BusinessObjects Information Steward Remote Job Server, you can change its configuration. 1. On the computer where the SAP BusinessObjects BI platform resides, launch the Information Steward Service configuration from the Windows Start menu. Start > Program Files > SAP BusinessObjects Information Steward 4.0 > Information Steward Service Configuration. The "SAP BusinessObjects Information Steward Service Configuration" window appears.

104

2011-08-19

Additional installation scenarios

2. The "General" tab describes the service and indicates its status. You can change the following options:
Option Description

Startup type Service status

Possible values are Automatic and Manual. The default value is Automatic. If the service is running, you can click Stop. If the service is stopped, you can click Start.

3. The "Java" tab defines the location of the Java run-time environment used by the Remote Service. You can change the following options:
Option Description

User Default Java Home Java Options

Enables or disables the Java Home option. If this option is selected, the JAVA_HOME environment variable must be set. The directory where the Java SDK is installed. Specify Java run-time options.

Initial memory pool The default value is 512MB. (MB) For more information about changing your Java memory settings, consult your JVM documentation. Maximum memory pool (MB) The default value is 1024MB. For more information about changing your Java memory settings, consult your JVM documentation.

4. The "Listener" tab defines the port to listen for service requests and connectivity to the SAP BusinessObjects BI platform Central Management Server (CMS) that will send service requests. You can set the following options:

105

2011-08-19

Additional installation scenarios

Option

Description

Application port CMS Server name User name

Number of the port that the listener service will use to listen for requests to run the SAP BusinessObjects Enterprise Metadata Integrator. Host name of the SAP BusinessObjects BI platform Central Management Server (CMS) that will send requests to run the Metadata Integrator on the BI platform. The CMS user name to connect to the CMS server. The default value is Administrator. If you want a user other than Administrator to run the Metadata Integrator, change the value to the appropriate name.

Password Authentication mode

The password to connect to the CMS server to register and run the Metadata Integrator. The default is no password. The CMS authentication mode. The default value is Enterprise. See the SAP BusinessObjects Business Intelligence Platform Administrator's Guide for available modes.

5. To verify that the port number is available, click Test port. The Remote Job Service uses this port to listen for requests to run the Metadata Integrator from SAP BusinessObjects Business Intelligence platform 4.0. 6. To verify that the Remote Service can connect successfully to the CMS on SAP BusinessObjects Business Intelligence platform 4.0, click Test connection. 7. Click the "Protocol" tab if you are using the Secure Sockets Layer (SSL) protocol for all network communication between clients and servers in your SAP BusinessObjects Enterprise XI 3.x and SAP BusinessObjects Business intelligence platform 4.0 deployments. For information about the SSL options on the "Protocol" tab, see Configuring the Remote Job Server for SSL in the Administrator Guide. Related Topics To install a Remote Job Server

106

2011-08-19

Index
A
adaptive job server 19 adaptive processing server 19 adding cleansing packages 98 Data Insight verifying installation 96 Data Services job server configuring for Information Steward 83 Data Services Job Server description 13 Data Services job server group post installation 71 Data Services Metadata Integrator 28 database security requirements connection 61 deleting cleansing packages 98, 99 deployment checklist 37 general guidelines 35 high availability 49 Information Steward Task Server 36 large amount of Cleansing Package Builder processing 45 large amount of integrator source processing 43 large amount of profile and rule task processing 42 metadata integrators 36 on Linux and Windows 52 on one computer 40 scaling web servers 48 distributing Information Steward components 35 documentation accessing 8 finding 8

I
Information Steward architecture 11 choosing components 28 deploying on Linux and Windows 52 product overview 7, 59 services 16 software requirements 58 uninstalling on Windows 100, 101 Information Steward Cleansing Package Builder Service 28 Information Steward components distributing 35 installation prerequisites 29 run on BI platform servers 11 run-time dependencies 30 Information Steward repository creating database for 63 requirements 60 Information Steward Task Server 28 installation prerequisites 29 run-time dependencies 30 Information Steward Web Application 28 installation prerequisites 29 run-time dependencies 30 information workflows 22 installation cleansing packages 96 command-line 72 feature codes 80 methods 67 parameters 75 response file 73, 74 response file example 80 scenarios 64 silent 74 installation prerequisites 29

B
BI platform components that Information Steward uses 11 Business Intelligence platform components how Information Steward uses 19 Business Warehouse Metadata Integrator 28

C
Central Management Console See CMC 19 Central Management Server See CMS 19 Cleansing Package Builder Service 28 installation prerequisites 29 run-time dependencies 30 cleansing packages adding 98 deleting 99 editing 98 installation 96 modifying 98 removing 98, 99 uninstalling 99 CMC 19 CMS 19 command-line installation program parameters 72 Common Warehouse Model (CWM) Metadata Integrator 28 components Business Intelligence platform 19 components of Information Steward 28 connections database security 61 CWM 28

E
Enterprise Metadata Integrator 28

F
file repository server 19

J
job server configuring on Data Services 83

H
high availability deployment scenario 49

D
Data Federator Metadata Integrator 28

107

2011-08-19

Index

L
license key updating 84 License keys description 64 load balancer for web applications 35

P
post installation restart Enterprise Information Management Servers 71, 100 pre-installation tasks overview 57 profiling and rule tasks deployment guidelines 36

M
Meta Integration Metadata Bridge (MIMB) Metadata Integrator 28 metadata integrator Common Warehouse Model (CWM) Metadata Integrator 28 Meta Integration Metadata Bridge (MIMB) Metadata Integrator 28 Relational Database (RDBMS) Metadata Integrator 28 SAP BusinessObjects Data Federator Metadata Integrator 28 SAP BusinessObjects Data Services Metadata Integrator 28 SAP BusinessObjects Enterprise Metadata Integrator 28 SAP NetWeaver Business Warehouse Metadata Integrator 28 metadata integrators deployment guidelines 36 server groups 100 Metadata Integrators definition 15 installation prerequisites 29 run-time dependencies 30 Metadata Management verifying installation 96 Metadata Relationship Service 28 run-time dependencies 30 Metadata Search Service 28 run-time dependencies 30 MIMB 28 modifying cleansing packages 98

Service Metadata Relationship Service 28 Metadata Search Service 28 services 12 pertinent to Information Steward 16 verify running 94 silent installation description 71 software dependencies 58

R
Relational Database (RDBMS) Metadata Integrator 28 Relationship Service installation prerequisites 29 Remote Job Server changing configuration of 104 collecting metadata from BusinessObjects Enterprise XI 3.x 103 installing 103 removing cleansing packages 99 response file 73, 74 example 80 feature codes 80 parameters 75 restart Enterprise Information Management Servers post installation 71, 100 run-time dependencies 30

T
task server 28

U
uninstalling cleansing packages 99 uninstalling on Windows 100 uninstalling specific components 101 updating license key 84

V
verifying installation Data Insight 96 Metadata Management 96

W
wdeploy 84 advanced options 86 command-line configuration 90 command-line syntax 87 deploying all components 86, 90 deploying one component 91 prerequisites 84 to start 85 undeploying all components 86, 92 undeploying one component 92 verifying deployment 91 web application 28 web application deployment post installation 71 web application server 19 Web application server 13, 14 administration 14 web applications deploying with wdeploy 84 deploying with wdeploy command-line tool 87 load balancer 35 workflow adding table to project 22

S
SAP BusinessObjects Data Federator Metadata Integrator 28 SAP BusinessObjects Data Services Metadata Integrator 28 SAP BusinessObjects Enterprise Metadata Integrator 28 SAP Host Agent 63 SAP NetWeaver Business Warehouse Metadata Integrator 28 SAP System Landscape Directory (SLD) 63 Search Service installation prerequisites 29 server adaptive job server 19 adaptive processing server 19 file repository server 19 server groups for metadata integrators 100 servers 12 verify running 94

N
network requirements 60

108

2011-08-19

Index

workflow (continued) scheduling and running a profile task 23

workflow (continued) scheduling and running an integrator source 23

109

2011-08-19

Index

110

2011-08-19