SLD Registering Third-Party

Download SLD Registering Third-Party

Post on 21-Apr-2015

222 views

Category:

Documents

4 download

Embed Size (px)

TRANSCRIPT

<p>Registering Third-Party Systems in the System Landscape Directory</p> <p>SAP Net Weaver 7.1Vers ion 1.0</p> <p>Copyright Copyright 2008 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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.</p> <p>(C) SAP AG</p> <p>Registering Third-Party Systems in the SLD</p> <p>2</p> <p>Icons in Body TextIcon Meaning Caution Example Note Recommendation Syntax</p> <p>Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.</p> <p>Typographic ConventionsType Style Example text Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation. Example text EXAMPLE TEXT Emphasized words or phrases in body text, graphic titles, and table titles. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.</p> <p>Example text</p> <p>Example text </p> <p>EXAMPLE TEXT</p> <p>(C) SAP AG</p> <p>Registering Third-Party Systems in the SLD</p> <p>3</p> <p>Registering Third-Party Systems in System Landscape Directory ........................5 Third-Party Systems Model Description ............................................................7 Registering Third-Party Systems.....................................................................11 Setting Up the Environment to Send Data ...................................................12 Testing the Registration of Third-Party Systems..........................................14 Defining Own Third-Party Products and Software Components in SLD and Export and Import Definitions.......................................................................15 Creating Your Own Data..............................................................................17 Transferring Your Data to sldreg..................................................................19 Appendix A: sldreg DTD..................................................................................20 Appendix B: XML Example..............................................................................23 Appendix C: XML Data Structure ....................................................................27 Appendix D: Mandatory Data Groups..............................................................34 Appendix E: Optional Data Groups .................................................................42 Appendix F: Key and Normal Properties of Classes........................................46 Appendix G: Overview of sldreg Command Line Parameters .........................52 Appendix H: Technical Notes on Using sldreg ................................................54 Appendix I: Supplying Data to the System Landscape Directory directly via HTTP...............................................................................................................55</p> <p>(C) SAP AG</p> <p>Registering Third-Party Systems in the SLD</p> <p>4</p> <p>Registering Third-Party Systems in System Landscape DirectoryThe System Landscape Directory (SLD) is a central repository of system landscape information that is relevant for the management of the software lifecycle. It contains a description of the system landscape, that is, the software components that are currently installed. The software components are installed on systems that form the entities that are visible to the administrator. An administrator must have knowledge about all the systems that are installed in the landscape and about the versions of the software components that are installed on these systems. This kind of information is stored in the SLD and is called Landscape Description (LD). SLD is also a repository of software components that can theoretically be installed in the landscape. This kind of information is stored in the SLD as Component Repository (CR). SLD data suppliers automatically register the systems on the SLD server and keep the system information up-to-date. They collect and send data about the systems to the SLD. For every newly-discovered system or component, the SLD creates an association to the corresponding entry in the Component Repository. Thus, SLD provides reliable and up-to-date system landscape information.</p> <p>SLDLD1) B C 2) 2) 1)</p> <p>SystemSLD Data Supplier</p> <p>Software ComponentsD B C</p> <p>CRA</p> <p>B C</p> <p>Figure 1: Automatic registration of systems and components For the SLD, applications that do not run on the SAP Application Server are thirdparty systems. Non-ABAP and non-Java SAP systems with unspecified characteristics fall into the same category. These systems register their current</p> <p>(C) SAP AG</p> <p>Registering Third-Party Systems in the SLD</p> <p>5</p> <p>system landscape data in the SLD using an external data supplier which uses the HTTP/HTTPS protocol.</p> <p>Note This step is valid only for software solution providers (SSPs) certified by SAP. Besides the registration of the system, a description of your product and software component is required. These data are shipped independently of the installed systems at customer side. SAP collects all these data in a software catalog called PPMS. The PPMS data are shipped on a regular basis (see SAP note 669669). You need a PPMS entry to be visible in SAP Solution Manager. For a PPMS entry you need a contact person at SAP. You can request one from SAP Active Global Support. The registration procedure is typically triggered at startup time of the third-party system and optionally with a slow period (twice a day). Due to this approach, some runtime is required while a plug-in is called at startup. If your software does not have such an active part, the registration process needs to be called at least once during the installation or at every operating system startup. This guide describes in detail the registration of third-party systems in the SLD. In addition, a second guide provides quick description of the standard registration procedure for third-party systems in the SLD. The SLD receives data via the sldreg executable in XML format. This XML has to comply with the document type definition (DTD). This DTD must not be declared in the sent XML, it is validated by the SLD server only. More Information Appendix A: sldreg DTD Appendix C: XML Data Structure SAP Note 1018839</p> <p>(C) SAP AG</p> <p>Registering Third-Party Systems in the SLD</p> <p>6</p> <p>Third-Party Systems Model DescriptionBasic Third-Party System A simplified model describing a third-party system is shown in the figure below.</p> <p>SAP_ComputerSystem 0..1SAP_ApplicationSystemHost</p> <p>* SAP_ApplicationSystem * 0..1SAP_InstalledSWComponentOnApplicationSystem SAP_InstalledProductOnApplicationSystem</p> <p>* * SAP_InstalledProduct * * SAP_InstalledSoftwareComponen t *SAP_SoftwareComponentType SAP_CollectedSoftwareComponent</p> <p>*</p> <p>SAP_InstalledProductImage</p> <p>SLD CR Content 1 SAP_Product 0..1 SAP_SoftwareComponent</p> <p>Figure 1: Model of a Third-Party System Each third-party system is an instance of the SAP_ApplicationSystem class. Other instances of SAP_ApplicationSystem are typically specializations (subclasses) of this class. Direct instances are either third-party systems or systems without specific properties modeled. The latter ones are called "unspecific systems" in this document. They are associated with a set of software components that are installed - different instances of the SAP_InstalledSoftwareComponent class. Each software component that is installed on an application system is part of one product that is installed. In most cases, a third-party system includes one software component that belongs to one product that is installed. However, the model also allows a more complicated case - a set of software components to be part of more than one product that is installed.</p> <p>(C) SAP AG</p> <p>Registering Third-Party Systems in the SLD</p> <p>7</p> <p>The SAP_Product and SAP_SoftwareComponent classes are included in the SLD CR. Unlike SAP products and components, third-party products and software components are not necessarily included in the CR. However, sldreg does not have authorization to create CR instances of third-party products and components. Only if these CR instances are created, sldreg does create the corresponding associations - SAP_SoftwareComponentType and SAP_InstalledProductImage. Therefore, the SLD CR Content for your software has to be either provided with the SAP CR content, or you have to create the third-party products and software components in the SLD yourself. Self-defined CR content can be exported and imported in any other SLD. The registration procedure of third-party systems includes the creation of one instance of the SAP_ApplicationSystem class, one or more instances of the SAP_InstalledSoftwareComponent class, one or more instances of the SAP_InstalledProduct class, and a basic instance of the SAP_ComputerSystem class. For more information, see the ThirdPartySystem.xml example under Registration of Third-Party Systems in SLD - Example Code at http://www.sdn.sap.com/irj/sdn/nw-sld. Optional: Third-Party System Using a Database A third-party system may use a database system. The figure below shows a simplified version of such a model. It covers all classes and associations that are additionally involved.</p> <p>(C) SAP AG</p> <p>Registering Third-Party Systems in the SLD</p> <p>8</p> <p>SAP_ComputerSystem 0..1SAP_ApplicationSystemHost</p> <p>1</p> <p>* SAP_ApplicationSystem *SAP_ApplicationSystemUsingDB SAP_DBInstanceHost</p> <p>0..1 SAP_DatabaseSystem 1SAP_DBSystemInstance</p> <p>1..* SAP_DatabaseInstance *</p> <p>Figure 2: Model of Third-Party System Using a Database</p> <p>In many cases you also have to register the database system in the SLD repository. This means that you have to create one instance of the SAP_DatabaseSystem class and at least one instance of the SAP_DatabaseInstance class. The model also requires that you associate each instance of the SAP_DatabaseInstance class with exactly one instance of the SAP_DatabaseSystem and the SAP_ComputerSystem classes. In many cases the computer system on which the instances of the SAP_DatabaseInstance class reside, can be different from the computer system on which the third-party system is installed. Thus, the data supplier must provide data about the computer system and host of the SAP_DatabaseInstance classes. For more information, see the ThirdPartySystem_extended.xml example under Registration of Third-Party Systems in SLD - Example Code at http://www.sdn.sap.com/irj/sdn/nw-sld. SAP Only: Support Package The following figure shows the UML part for an applied SAP Support Package associated to an installed software component.</p> <p>(C) SAP AG</p> <p>Registering Third-Party Systems in the SLD</p> <p>9</p> <p>SAP_ApplicationSystem 0..1SAP_InstalledSWComponentOnApplicationSystem SAP_InstalledSupportPackageSoftwareComponent</p> <p>* 1 SAP_InstalledSoftwareComponent *SAP_SoftwareComponentType</p> <p>SAP_InstalledSupportPackage * *SAP_SupportPackageType</p> <p>SLD CR Content 0..1 SAP_SoftwareComponent 0..1 SAP_SupportPackage</p> <p>Figure 3: Model of Third-Party System Using an Installed Support Package For SAP internal use, you need to specify an installed software component (SAP_InstalledSoftwareComponent) and an installed Support Package. To do so, create an instance of the SAP_InstalledSupportPackage class and associate this instance with the SAP_InstalledSupportPackageSoftw...</p>