User manual BUSINESS OBJECTS DATA SERVICES XI 3.2 ADVANCED DEVELOPMENT GUIDE 12.2.0

[. . . ] SAP BusinessObjects Data Services Advanced Development Guide SAP BusinessObjects Data Services XI 3. 2 (12. 2. 0) Copyright © 2009 SAP® BusinessObjectsTM. SAP BusinessObjects and its logos, BusinessObjects, Crystal Reports®, SAP BusinessObjects Rapid MartTM, SAP BusinessObjects Data InsightTM, SAP BusinessObjects Desktop IntelligenceTM, SAP BusinessObjects Rapid Marts®, SAP BusinessObjects Watchlist SecurityTM, SAP BusinessObjects Web Intelligence®, and Xcelsius® are trademarks or registered trademarks of Business Objects, an SAP company and/or affiliated companies in the United States and/or other countries. SAP® is a registered trademark of SAP AG in Germany and/or other countries. All other names mentioned herein may be trademarks of their respective owners. [. . . ] When working in a multi-user environment, you activate the link between your local repository and the corresponding central repository each time you log in. To ensure that your repository is current, you can get (copy) the latest version of each object in the central repository. Once you get an application in your local repository, you can view and run it from the Designer. However, if you plan to make changes to objects in the application, you must check out those objects. After you check out an object, no other user can 54 SAP BusinessObjects Data Services Advanced Development Guide Multi-user Development Multiple users 5 make changes. Essentially, you lock the version in the central repository; only you can change that version. Other users can only get and view the object. When you are done making changes to an object, save those changes in the local repository and check the object back into the central repository. The software saves the changed object in the central repository and makes the object available for check-out by others. The software maintains all versions of saved objects in the central repository. Thus later, you can copy an old version of a saved object, even after replacing it in your local repository with a new version. An object label provides a convenient mechanism for identifying objects later. Later, if you decide you want to eliminate a recently-added feature, you can get all objects that have the label without that feature. You can also compare two objects--such as two different object versions in the central repository, or an object in your local repository to an object in the central repository. By comparing two objects, you can determine what parts of an object changed and decide whether you want to revert to an older version of an object. Related Topics · Designer Guide: Design and Debug, Comparing Objects SAP BusinessObjects Data Services Advanced Development Guide 55 5 Multi-user Development Security and the central repository Security and the central repository You also have several options to make your central repository secure. Use these options when you need to control access and provide for object tracking within your central repository. These security options apply only to central repositories and include: · · · Authentication -- Allows only valid users to log in to a central repository. Auditing -- Maintains a history of changes made to an object including user names. Implement security for a central repository by establishing a structure of groups and associated users using the Administrator. Related Topics · Implementing Central Repository Security on page 65 56 SAP BusinessObjects Data Services Advanced Development Guide Multi-user Environment Setup 6 6 Multi-user Environment Setup Create a nonsecure central repository Overview of multi-user setup To support multiple developers, configure a multi-user environment and set up several repositories. Specifically, you must: · · · · Create a local repository for each developer. Activate the connection to a central repository. Related Topics · · · Create a nonsecure central repository on page 58 Define a connection to a nonsecure central repository on page 59 Activating a central repository on page 60 Create a nonsecure central repository To support multiple users in a single development environment, it is recommended that you use a central repository. The central repository stores master information for the development environment. This procedure applies to nonsecure repositories only. Related Topics · Implementing Central Repository Security on page 65 To create a nonsecure central repository 1. Create a database to be used for the central repository using your database management system. Choose Start > Programs > SAP BusinessObjects XI 3. 2 > SAP BusinessObjects Data Services > Data Services Repository Manager. [. . . ] With this scheme, a developer will never interfere with the test environment, and a tester will never interfere with a production environment, creating an extremely safe process of migration. Note that if you choose to support multiple central repositories, use a single local repository as a staging location for file transition. SAP BusinessObjects Data Services Advanced Development Guide 99 9 Migrating Multi-user Jobs Copying contents between central repositories Copying contents between central repositories You cannot directly copy the contents of one central repository to another central repository. Rather, you must use your local repository as an intermediate repository. To copy the contents of one central repository to another central repository 1. Get the latest version of all objects in this active central repository so they exist in your local repository. [. . . ]