How-to Guide SAP NetWeaver 2004s How To Extend User Details May 2006 Applicable Releases: SAP NetWeaver 2004s
Copyright 2006 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, 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 in several other countries all over the world. 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. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver How-to Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings ( Code ) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.
1 Scenario This scenario describes how to create additional attributes for user information easily and simply. Depending on the user persistence-mode, you can add extra information (address, phone number, and so on) to an existing user. This information is stored and read out from the portal-user persistence (LDAP, MS-ADS, DB, ). In addition, you can create own (custom) user attributes. The additional attributes are stored as UME attributes. The store depends on the UME configuration. The advantage of this scenario is that the portal-users can add their own (personal) information to their profile and also be able to take knowledge about other users profiles. Also the users are able to search for these attributes and get the relevant hits in a search-result-list. 2 Prerequisites You must be assigned to the super administrator in order to carry out the tasks described in this guide. This scenario is based on an example, were a customers need is to extend the User information with the attribute Expert Area. The users should be able to outline their expertise within that area they work in. - 1 -
3 The Step By Step Solution In the first step, you define additional custom UME attributes, in the second step, you map these UME attributes to KM properties. The goal of this Guide is to enable the KM to read and display the defined UME-attributes. 3.1 Specify Additional Attributes in UME The properties used in this example must be known within the UME. For more information, see: http://help.sap.com/saphelp_nw2004s/helpdata/en/0b/50ad3e1d1edc61e10000000a114 084/frameset.htm 1. Additional Attributes in UME: Start the Config Tool by executing <SAPJ2EEEngine_installation>\j2ee \configtool\configtool.bat In the tree, navigate to Global server configuration services com.sap.security.core.ume.service. Edit the ume.admin.addattrs In Value at the bottom of the screen, enter the new value expertarea Choose Set Apply your changes Restart the nodes in the cluster for the changes to take effect - 2 -
3.2 Creating a Metadata Property in CM Configuration Call up the Configuration IView as follows: Choose System Administration System Configuration Knowledge Management Content Management (Use the same path and configuration 3.2-3.5). Make sure that the advanced view is activated in the Configuration IView. You can check this via Mode Advanced in the menu bar. (The advanced view displays all configuration classes and parameters.) 2. Create an additional Property Goto Global Services Property Metadata Properties Search for an UME property, e.g. ume_user_zip and duplicate it Specify the following attributes (sample): UniqueID= ume_user_expertarea PropertyID= expertarea Indexable (optional) = TRUE Hint: If you want translate the property see section 3.8, then you need a Key for Label. In this example the Key is named: UME_USER_EXPERTAREA Save the newly created metadata property - 3 -
3.3 Adding the Metadata Property in the Property Structure 3. Add the property to the property structure Go to Global Services Property Structure Property Groups. You can create a new group or use an existing one, for example, edit userdetailscompany. Add the metadata property created in section 3.2 (with the namespace information) to the Group Items attribute (delimited by commas). 3.4 Creating the UME Attribute Mapping In order to prevent a reduction in performance, you must additionally map the UME attribute. 4. Define UME Attribute Mapping in CM Configuration Go to Repository Managers UME Object Settings UME Principals UME Attribute Mapping. Create a new UME Attributes entry: Property Name = expertarea UME Attribute Name = expertarea UME Attribute Namespace = com.sap.security.core.usermanagement - 4 -
3.5 Activating the UME Principals Mapping 5. Activate the UME Principals Mapping Go to Repository Managers UME Object Setting UME Principals UME Principals Edit IUser In the list of available properties, check your new property expertarea Save your changes 3.6 Checking the User Profile 6. Check your User Profile In the portal header, choose Personalize User Profile In the Customized Information section, check that the Expert Area attributes are available Save the user profile - 5 -
3.7 Checking the User Details 7. Checking the User Details Choose Content Administration KM Content Choose any repository where your user ID works (for example in the KM Content iview under Content Administration KM Content) Click your user name and check that the additional attributes are displayed Hint: The expert Area is only displayed if you have configured any entry. If still nothing is displayed you should delete the cache of the UME Repository Manager (in the standard UME Repository Manager configuration this cache is named ca_coll_rep_ume_med) 3.8 Additional Tasks You may have to perform some additional tasks for this scenario, for example, translating the created properties with multiple values or making the properties available for advanced search. SAP recommends referring to http://sap.help.com or http://service.sap.com/nw2004s-howtoguides to get the latest documentation and information, as links to other How-To-Guides within this guide might change. - 6 -
www.sdn.sap.com/irj/sdn/howtoguides