1、SAP PI SLD根底及配置2021/04/21課程目的完本錢課程后，需求學(xué)員掌握如下知識：Understand the SLD Content TypeUnderstand the SLD Data suppliersUnderstand the SLD Data consumersUnderstand the SLD and Enterprise Service RepositoryUnderstand the SLD and Integration Directory2Course AgendaOverviewSLD Content TypeSLD Data SuppliersSLD

2、Data ConsumersOverviewSLD and Enterprise Service RepositorySLD and Integration DirectoryTopologySummary3System Landscape DirectorySLD is the central repository of information about the software and systems in the data center expressed in a standard schema called the CIM (Common Information Model).CI

3、M was developed by the Distributed Management Task Force, or DMTF, an industry consortium whose goal is to enable management of IT systems in distributed environments using web standards.SLD represents the central information provider for NetWeaver system Landscapes.Manages software components and p

4、latform dependencies.Facilitates, upgrades , transports and Installations.Information provider for SAP PI.4Challenges addressed by SLDWhere can I get a consistent and up-to-date overview of SAP software installed in my landscape?Technical Information about SAP products regularly updated?How can one

5、make sure that the central administration toolsuse the same, up-to-date landscape information?Infrastructure data like hosts and ports of back-end systems should be stored centrally!Configuration of software development should be maintained centrally including interdependencies!How can I make sure t

6、hat the names of Java development objects are unique internally +externally although I have several development teams?5The Three DimensionsSystem Landscapes have three dimensions:Solution Dimension what software processes are installedTransport Dimension DEV, QA , PRODTechnical Dimension what produc

7、ts are installed on which hosts on particular networksThe SLD should capture all three dimensions of the System Landscape.R/3R/3R3BWCRMBWCRMBWCRMDEVQAPRODQuality Assurance (Transport Landscape)Business ProcessesTechnical Information (Server Landscape)Data CenterAccess6The Basic Idea of SLDGraphical

8、Design ToolTechnical ConfigurationValidation RegistrationSoftware LogisticsLandscape DescriptionComponent InformationSystem Landscape Directory3rd Party / customer component typesAny Landscape ElementCustomer LandscapeWBEMXMLWBEMXMLCIMCIMApplications and ToolsPPMSComponent TypesLandscape PatternsPos

9、sible CombinationsMaster Component RepositorySAPSynchronize XMLUpdate7SLD Initial Page8Course AgendaOverviewSLD Content TypeSLD Data SuppliersSLD Data ConsumersOverviewSLD and Enterprise Service RepositorySLD and Integration DirectoryTopologySummary9CatalogsThe two main areas of SLD are: the softwar

10、e catalog and the landscape description.The Software Catalog describes the installed products and their constituent components. The software catalog is delivered with content about all SAP products. Customers and Partners can extend this catalog with information about software from other vendors. It

11、 describes the component information, possible combinations and dependencies.The Landscape Description describes the systems in the data center from two perspectives: a logical view (business systems) and a physical view (technical systems). It describes the concrete implementation of the customer l

12、andscape.software catalog information is used in the Enterprise Service Repository to organize development efforts and Information from the landscape description is used in the Integration Directory to meet the specific configuration requirements of Integration Scenarios.10Functioning of SLDImportin

13、g/synchronizing PPMS data as XML file into Master Component Repository at the SAP site. The Master Component Repository contains the up-to-date information about all SAP products. This will be published on the Service Market Place and Customers can update their individual component information. They

14、 can also add additional information about the 3rd party products which are in operation into their individual component information.The Landscape description contains information about all installed products/components at the Customer site.Applications and Tools can use information from the SLD as

15、the central information provider.11Products and Software ComponentsThe component information is based on Software products and their versions, SWC and their versions .Software Component: The software Component is a unit of software delivery that has its own support package track. (Ex: SAP_HR, SAP_BA

16、SIS etc)Product: A software product comprises of one or more software components. (Ex: SAP R/3)Product Version: It represents a particular version of the product. (Ex: SAP R/3 4.6c, 4.6d, 4.7)Software Component Version: It represents a particular version of the SWC.The relationship between a softwar

17、e product and its constituent components is described in the SLD by an association called a software feature.ProductSoftware ComponentSoftware Component VersionSoftware FeatureProduct Version0.10.11*12Products and Software ComponentsEach product version consists of multiple software features which a

18、re are implemented by various software components (versions).The product SAP R/3 Enterprise has a product version SAP R/3 4.7Various software components (versions) fill the features of this software product. These software components (or versions) are, SAP SAP HR 4.70, Basis 6.20, and SAP Enterprise

19、 Retail 1.10. The internal PPMS (SAP Product and Production Management System) provides the data for SWC and software products for SAP products.SAP provides this master data for updating the local component information. Using data import current data is added to SLD. Defining third party products an

20、d software components is easy in SLD, because of the wizards that guide you through the process.SAP R/3SAP BASIS, SAP HR, SAP ENTERPRISE RETAILSAP BASIS 6.20, SAP HR 4.7, SAP ENTERPRISE RETAIL 1.10SOFTWARE FEATURE1*13Technical Systems and Business SystemsTechnical Systems are defined in the

21、 Systems catalog. Technical System corresponds to the physical details of the system in which the software is installed.Types of Technical SystemWeb AS ABAPWeb AS JavaStandalone JavaThird-Party A Technical System may have multiple products installed on it.WebAsABAPName;host name;system number;Releas

22、eInstalled clientsBusiness SystemMessage ServerInstalled ProductsWebAsJavaName;host name;SID;SystemHomeStandaloneJavaTechnical System IdBusiness SystemThirdPartyBusiness SystemInstalled ProductsTechnical System14Technical Systems and Business SystemsBusiness systems are logical senders/ receivers th

23、at exchange messages by using SAP PI and these are entered in the System Landscape Directory.Technical Systems are the basis for defining Business systems. SLD defines the association between Technical and Business Systems.The association between the Technical and Business systems depend upon the ty

24、pe of the Technical System.For a TS of type Web AS ABAP, each client is a Business System. This is similar to depicting each client as a Logical system in ALE Configuration.There are wizards to guide you through the process of creating technical and business systems. You can launch these wizards fro

25、m the main screen of the SLD.WebAs ABAPRelated Integration ServerClientTechnical SystemInstalled ProductsWebAs JavaNameThird Party SystemsRelated Integration ServerStandalone JavaTechnical SystemBusiness SystemRelated Integration ServerTechnical SystemTechnical SystemInstalled ProductsName15Course A

26、gendaOverviewSLD Content TypeSLD Data SuppliersSLD Data ConsumersOverviewSLD and Enterprise Service RepositorySLD and Integration DirectoryTopologySummary16 How does SLD gets Landscape Description?SAP systems contains data suppliers that collect and send data to SLD:This must be configured per lands

27、cape elementOnce configured, it sends reliable and up to date data automatically:At system startupPeriodically (batch job) ABAP Data SupplierJava Data SupplierOther Data SupplierSLDABAP SystemJAVA SystemOther SystemJAVA System GatewayRFC17Data Supplier ABAP Based Systems18Data Supplier Java Based Sy

28、stemSLD Data Supplier19Course AgendaOverviewSLD Content TypeSLD Data SuppliersSLD Data ConsumersOverviewSLD and Enterprise Service RepositorySLD and Integration DirectoryTopologySummary20Course AgendaOverviewSLD Content TypeSLD Data SuppliersSLD Data ConsumersOverviewSLD and Enterprise Service Repos

29、itorySLD and Integration DirectoryTopologySummary21SLD Consumers - OverviewSLDSoftware Lifecycle Manager of SAP NetweaverWeb Dynpro RuntimeSAP Netweaver Development InfrastructureSAP Netweaver Process IntegrationPartner ApplicationsSAP Netweaver AdministratorAdaptive Computing ControllerSAP Solution

30、 Manager22SLD Data Consumers - Overview ContinuedSAP NetWeaver PI :Main use cases of SAP NetWeaver PI is for providing business system names and provides transports targets for content transports of PIDevelopment and Design of interface in PI are derived from the contents of SLDSLD maps “business sy

31、stem name to “technical system so that PI can determine the receiver of a messageWeb Dynpro :WebDynpro requires SLD for adaptive RFC callsSAP Netweaver Development Instrastructure (NWDI) :To Develop Java SLD provides :Definition for the software products and software componentNaming serviceStorage o

32、f development configuration required for developmentSAP Solution Manager:SLD provides solution manager with the details of the ABAP and Java system in the landscape23SLD Data Consumers - Overview ContinuedInformation that is stored in SLD is important for further applications in the production lands

33、capeSAP NetWeaver AdministratorTool for administration and monitoring, which offers a central entry point to whole SAP NetWeaver system landscapeRequires SLD for remote monitoring functionsDuring SLD downtime, central administration of systems is not possibleAdaptive Computing ControllerFrom a singl

34、e point through observation, dynamic resource distribution and operation user can control an adaptive computing landscape. Needs SLD for its operation (to start, stop and change of resources)During SLD downtime, only the monitoring functions of Adaptive Computing Controller are available24Course Age

35、ndaOverviewSLD Content TypeSLD Data SuppliersSLD Data ConsumersOverviewSLD and ESRSLD and Integration DirectoryTopologySummary25SLD and ESRAll design/development work in the ESR (Enterprise Service Repository) is organized by SWC version. This makes us understand the interfaces logically belong to a

36、 SWC and to a particular version.Before development begins, the SWCVs must be imported from the SLD to the Integration Repository.As the Local Software component is not having any link with SLD or ID, it is used only for testing purpose. Wherever development of interfaces is concerned SWCVs imported

37、 from the SLD only can be usedAdditionally when we define integration scenarios in the ESR, the application components that we assign in the scenario editor are assigned from product versions in the SLD.Dependencies between SWCVs can be created in the SLD and these dependencies will automatically be

38、 reflected in ESR.26SLD and Enterprise Service RepositorySoftware Component VersionBusiness ScenarioApplication ComponentRoleProduct VersionMapping ObjectsInterface ObjectsIntegration Repository (Design)Product VersionProductSoftware Component VersionSoftware ComponentSystem Landscape Directory27Cou

39、rse AgendaOverviewSLD Content TypeSLD Data SuppliersSLD Data ConsumersOverviewSLD and ESRSLD and Integration DirectoryTopologySummary28SLD and Integration DirectoryAt configuration time a collaborative process is set up for a specific system landscape. The configuration data is organized, structured

40、, and saved in the ID (Integration Directory) in the form of configuration objects.A Service is used to address a sender or receiver of messages during the configuration time.It is possible to address a particular Business System as a service.Routing RelationsBusiness SystemSender ServiceIntegration

41、 DirectoryTechnical SystemSystem Landscape DirectoryBusiness SystemReceiver ServiceBusiness System29SLD and Integration Directory continuedA business system (BS) is an actual application system in a system landscape. A business system (service) has information about the inbound/outbound interfaces a

42、nd the SWC versions of the business system.Business system services are used when configuring internal company processes.Routing Relations in the ID point to the Business Systems (BS) that are maintained in the systems catalog in the SLD, and through appropriate association, to the technical systems

43、.30Course AgendaOverviewSLD Content TypeSLD Data SuppliersSLD Data ConsumersOverviewSLD and ESRSLD and Integration DirectoryTopologySummary31Topology - Reasons to have several SLDThe following are some of the reasons to have several SLDs:Isolated Production Environment.Improve availability for appli

44、cations relying on SLD dataSandbox SLD to test content imports, CIM data updates, patches, Different user groups with different views (such as distributed locations with localadmin groups)32Topology Central OrganizationCentral Organization: One single SLD for entire customer enterprise networkAdvant

45、ages:Easy setup + low operation effortNo redundancy, consistent foundationDrawbacks:High demand on SLD regarding availability and stabilityDifferent user groups (developers, administrators, ) are working within the production SLDData of all systems visible/accessibleSAPSAPSAPSAPSAPSAPIntranetIntranetSLDExtranet33Topology Distributed OrganizationDistributed Organization: Several distributed SLDsAdvantages:Availability improvedRestricted views possibleEnvironments can be isolatedDrawbacks:Higher operation effortSeveral CIM model updates requiredPossib