Sapr3 Bc Guide

STRUN PRUKA PRO SAP BASIS COMPONENTS (BC)

Frantiek Vilm

Frantiek Vilm Autor: Verze dokumentu: Datum vzniku: Datum posledn pravy: Frantiek Vilm 2.0 (2428) 01.03.2002 13.12.2007 14:03

Pouit tohoto dla: This work is licensed under the Creative Commons Attribution-NoDerivs 2.5 License. To view a copy of this license, visit http://creativecommons.org/licenses/bynd/2.5/ or send a letter to Creative Commons, 543 Howard Street, 5th Floor, San Francisco, California, 94105, USA. V dnm ppad nen autor tohoto dla odpovdn komukoli za pm, nepm, mimodn nebo jin nsledn kody, zpsoben pouitm tto pruky vetn ulho zisku, peruen innosti, ztrty program nebo jinch dat v informanm systmu i jinde, a to i kdyby autor byl na monost takovch kod upozornn pedem. Spolenost SAP AG dnm zpsobem nereprezentuje ani neru za pesnost, adekvtnost i plnost jakchkoli informac obsaench v tomto dle a nen zodpovdn za ppadn chyby nebo opomenut. SAP, R/3, mySAP.com, mySAP, SAP Netweaver, ABAP, SAP xApps are trademarks or registered trademarks of SAP AG in Germany and in several other countries. ORACLE is a registered trademark of ORACLE Corporation. MaxDB is a trademark of MySQL AB, Sweden. Microsoft, WINDOWS, NT are registered trademarks of Microsoft Corporation. JAVA is a registered trademark of Sun Microsystems, Inc. IBM, DB2, AIX, i5/OS, iSeries, Informix are registered trademarks of IBM Corporation. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.


Obsah1. vod..........................................................................................................................1 1.1.1. O EM POJEDNV TATO PRUKA?.......................................................................1 1.2. CO JE TO BC SAP NETWEAVER?........................................................................1 1.2.1. OBECN INFORMACE A REFERENCE..........................................................................3 1.3. DOPORUEN LITERATURA...........................................................................................4 1.4. SAP SERVICE MARKETPLACE.......................................................................................5 2. Sprva aplikanch server.......................................................................................6 2.1. ARCHITEKTURA APLIKANHO SERVERU............................................................................6 2.1.1. SOFTWAROV ORIENTOVAN POHLED.......................................................................6 2.1.2. PROCESY V APLIKAN VRSTV ABAP TECHNOLOGIE..................................................7 2.1.3. PROCESY V APLIKAN VRSTV JAVA TECHNOLOGIE.................................................13 2.1.4. ZEN PAMTI, SDLEN PAM A LOHY.................................................................14 2.1.5. SAP SYSTM A INSTANCE...................................................................................16 2.1.6. SYSTMOV KONFIGURACE..................................................................................16 2.1.7. SAP SYSTEM LANDSCAPE.................................................................................16 2.1.8. ADRESE APLIKANHO SERVERU ABAP TECHNOLOGIE............................................17 2.2. ZKLADN OPERACE..................................................................................................19 2.2.1. OBECN POZNMKY K PIHLEN DO SYSTMU........................................................19 2.2.2. START............................................................................................................20 2.2.3. STOP.............................................................................................................20 2.2.4. START A STOP R/3 V PROSTED MSCS..............................................................21 2.2.5. TEST BHU SERVERU A DATABZOVHO SPOJEN.......................................................21 2.2.6. ZAMKNUT A ODEMKNUT UIVATEL........................................................................21 2.3. ZKLADN KONTROLY................................................................................................21 2.4. RZN PROBLMY...................................................................................................22 2.4.1. OBECN.........................................................................................................22 2.4.2. NEMEME SE PIHLSIT DO SYSTMU...................................................................22 2.4.3. MONITORY.......................................................................................................23 2.4.4. NESTARTUJE APLIKAN SERVER............................................................................23 2.4.5. PRACOVN PROCESY..........................................................................................24 2.4.6. PROBLMY S PAMT..........................................................................................24 2.4.7. PROBLM S PAMT SCSA.................................................................................24 2.4.8. NEDOSTATEK PAMTI PXA..................................................................................24 2.4.9. SYSTM DOWNTIME...........................................................................................24 2.4.10. FILE SYSTM JE PLN.......................................................................................24 2.4.11. NEN DOSTUPN DNS SERVER..........................................................................24 2.4.12. OPERAN SYSTM W2000.............................................................................24 2.4.13. PROBLMY S JAVA VM....................................................................................25 2.5. JOBY PROCESY NA POZAD......................................................................................25 2.5.1. STANDARDN JOBY.............................................................................................26 2.5.2. PROBLMY S JOBY............................................................................................26 2.6. UPDATES V APLIKAN VRSTV....................................................................................26 2.7. SYSTMOV ZMKY..................................................................................................28 2.7.1. SELN ADY..................................................................................................29 2.7.2. ATP SERVER...................................................................................................29 2.8. GATEWAY MONITOR..................................................................................................30 2.9. MICROSOFT MANAGEMENT KONSOLE MMC..............................................................30 2.9.1. PROBLMY SE SAP SERVICE..............................................................................30 2.9.2. RUN INSTALACE MMC....................................................................................30Obsah

iii


2.10. SPRVA SPECILNCH SERVER WAS.......................................................................30 2.10.1. SERVER NW XI............................................................................................30 2.11. ADMINISTRACE WAS JAVA......................................................................................30 2.11.1. NSTROJ VISUAL ADMINISTRATOR......................................................................31 2.11.2. NASTROJ SHELL CONSOLE ADMINISTRATOR..........................................................31 2.11.3. NSTROJ CONFIG TOOL...................................................................................31 2.11.4. NSTROJ SOFTWARE DEPLOYMENT MANAGER GUI...............................................31 2.11.5. NSTROJE V ABAP SERVERU...........................................................................31 2.12. VYSOK DOSTUPNOST SYSTM................................................................................31 2.12.1. TMATA HA..................................................................................................32 2.12.2. TMATA ATG................................................................................................32 3. Sprva databze Oracle..........................................................................................33 3.1. OBECN A RZN POZNMKY......................................................................................33 3.1.1. DBA COCKPIT................................................................................................33 3.1.2. BR*TOOLS.....................................................................................................34 3.1.3. SQL TOOLS....................................................................................................35 3.1.4. MCOD........................................................................................................35 3.1.5. POUIT TERMINLOVHO SERVERU........................................................................35 3.1.6. SYSTMOV TY A SKUPINY V UNIXU.................................................................35 3.2. ZKLADN OPERACE..................................................................................................35 3.2.1. START DB......................................................................................................36 3.2.2. STOP DB.......................................................................................................36 3.2.3. START A STOP DB V PROSTED MSCS..............................................................36 3.2.4. ZMNA DOSTUPNOSTI DB...................................................................................36 3.2.5. LISTENER V UNIXU..........................................................................................37 3.3. NASTAVOVNI PARAMETR V INIT.ORA.................................................................37 3.4. ZMNY STRUKTURY DB..............................................................................................37 3.4.1. PIDN TABLESPACE:........................................................................................37 3.4.2. ZMNA ARCHIVNHO MODU...................................................................................37 3.4.3. USPODN TABLESPACES.................................................................................38 3.4.4. ANALZA VOLNHO PROSTORU..............................................................................39 3.5. REORGANIZACE DB.................................................................................................39 3.5.1. REORGANIZACE OBJEKTU TABLESPACE................................................................39 3.6. ZLOHOVN...........................................................................................................40 3.6.1. NASTAVEN ZLOH.............................................................................................40 3.6.2. NSTROJE BRBACKUP A BRARCHIVE.......................................................................40 3.6.3. TEST OBNOVA SOUBORU:.................................................................................41 3.6.4. PROBLMY PI ZLOHOVN.................................................................................41 3.6.5. PERUEN ONLINE TABLESPACE ZLOHY.................................................................41 3.6.6. BACKINT KONFIGURACE...............................................................................42 3.7. VERIFIKACE DB......................................................................................................42 3.8. RESTORE A RECOVERY DATABZE................................................................................43 3.8.1. KDE HLEDAT INFORMACE.....................................................................................43 3.8.2. DLEIT ZSADY.............................................................................................43 3.8.3. ANALZA CHYB DATABZE....................................................................................43 3.8.4. TYPY CHYB DATABZE A ZPSOB JEJICH EEN........................................................43 3.8.5. KOMPLETN OBNOVA DATABZE.............................................................................45 3.9. PLNOVN KONTROL A ZLOHOVN DATABZE................................................................47 3.10. VELK DB OPERACE A OFFLINE ZLOHA.......................................................................48 3.11. RZN PROBLMY..................................................................................................49 3.11.1. OBECN........................................................................................................49 ivObsah


3.11.2. CHECK POINT NOT COMPLETED...........................................................................49 4. Sprva databz dalch dodavatel.......................................................................50 4.1. MICROSOFT SQL SERVER 2000...............................................................................50 4.1.1. NSTROJE.......................................................................................................50 4.1.2. ZKLADN OPERACE...........................................................................................50 4.2. MYSQL MAXDB...................................................................................................50 4.2.1. SYSTMOV TY A SKUPINY V UNIXU.................................................................50 4.2.2. NSTROJE.......................................................................................................51 4.3. INFORMIX...............................................................................................................51 4.3.1. SYSTMOV TY A SKUPINY V UNIXU.................................................................51 4.3.2. NSTROJE.......................................................................................................51 4.3.3. ZKLADN OPERACE...........................................................................................51 4.4. DB2 UDB PRO UNIX A WINDOWS...........................................................................52 4.4.1. SYSTMOV TY A SKUPINY V UNIXU.................................................................52 4.4.2. DBA COCKPIT................................................................................................52 4.4.3. ZKLADN OPERACE...........................................................................................52 4.4.4. SPECIFIKA PRO BI............................................................................................53 4.5. DB2 UDB PRO IBM ISERIES..................................................................................53 4.5.1. DATABZE LIBRARY............................................................................................53 4.5.2. NSTROJE.......................................................................................................53 4.5.3. ZKLADN OPERACE...........................................................................................53 4.5.4. SPECIFIKA PRO BI............................................................................................53 4.5.5. SPECIFIKA PRO XI............................................................................................53 5. Konfigurace aplikanho serveru.............................................................................54 5.1. ZALOEN PROFILU A NASTAVEN PARAMETRU PROFILU.......................................................54 5.2. INSTANCE A OPERAN MDY.......................................................................................55 5.3. SEZNAM PARAMETR PROFILU.....................................................................................56 6. Vkon, monitorovn a trasovn aplikanho serveru............................................57 6.1. VKON SYSTMU.....................................................................................................58 6.1.1. PERFORMANCE MONITORY...................................................................................59 6.1.2. SDLEN PAM KONTROLA A LADN...................................................................61 6.1.3. VKON DATABZE..............................................................................................62 6.2. SYSTMOV LOG.....................................................................................................63 6.3. SYSTM MONITOROVN CCMS..............................................................................63 6.3.1. DATOV KOLEKTORY A CCMS AGENTI..................................................................64 6.3.2. ALERT MONITOR...............................................................................................64 6.4. TRASOVN............................................................................................................67 6.5. SAP SUPPORT SERVICES........................................................................................68 7. Sprva uivatel a bezpenost...............................................................................69 7.1. AUTENTIFIKACE UIVATEL A SINGLE SIGN-ON...............................................................69 7.2. AUTORIZACE ZKLADN KONCEPT A POJMY...................................................................70 7.3. CENTRLN ADMINISTRACE UIVATEL............................................................................70 7.4. ANALZA OPRVNN................................................................................................70 7.5. AUDIT INFORMAN SYSTM (AIS)...............................................................................70 7.6. BEZPEN KONEKTIVITA............................................................................................71 7.7. BEZPENOSTN AUDIT...............................................................................................71 7.8. SPECILN UIVATEL SAP* A DDIC..........................................................................71 7.9. NKTER OBJEKTY OPRVNN....................................................................................72 7.10. NKTER PARAMETRY PROFILU..................................................................................72 7.11. ZAKZAN HESLA...................................................................................................72 7.12. ZAMEN TRANSAKCE A POUIT SE38......................................................................73Obsah

v


7.13. GENEROVN PROFIL UPOZORNN........................................................................73 7.14. ZKLADN ROLE PRO KONCOV UIVATELE....................................................................73 7.15. NASTAVEN KLIENTA................................................................................................73 7.16. SYSTMOV MEN POUIT LICENC..........................................................................73 7.17. VYROVNN KMENOVHO SOUBORU UIVATEL..............................................................73 7.18. LOGOVAC SKUPINY................................................................................................74 8. Transportn systm..................................................................................................75 8.1. VEOBECN TERMNY...............................................................................................75 8.2. PROCES IMPORTU TRANSPORTNHO POADAVKU...............................................................76 8.3. NSTROJE TP A R3TRANS...................................................................................76 8.4. KONFIGURACE TRANSPORTNHO SYSTMU......................................................................77 8.4.1. EXTENDED TRANSPORT CONTROL........................................................................77 8.4.2. TESTOVN TRANSPORTNHO SYSTMU....................................................................77 8.4.3. EEN PROBLM V TMS.................................................................................78 8.4.4. SPOJOVN TRANSPORTNCH POADAVK.................................................................78 8.5. POSTUP IMPORTU TRANSPORTNCH POADAVK...............................................................79 8.5.1. VOD K POSTUPU.............................................................................................79 8.5.2. KROK 1: PPRAVA PRO IMPORT TRANSPORTU DO VVOJOVHO Z EXTERNHO ZDROJE. .79 8.5.3. KROK 2: VLASTN IMPORT...................................................................................80 8.6. IMPORT POMOC PROGRAMU TP...................................................................................80 8.7. TRANSPORT KOPI....................................................................................................80 9. Instalace systmu a systmov kopie.....................................................................81 9.1. SAP KOMPONENTY..................................................................................................81 9.2. NSTROJ R3SETUP.............................................................................................81 9.3. NSTROJ SAPINST.................................................................................................82 9.4. SAP SYSTMOV KOPIE A MIGRACE.............................................................................82 9.4.1. SAP HOMOGENN SYSTMOV KOPIE.....................................................................83 9.4.2. SAP HETEROGENN SYSTMOV KOPIE..................................................................84 9.5. ADD-ON...............................................................................................................84 9.6. SWITCH FRAMEWORK...............................................................................................84 9.7. JAZYKOV PODPORA.................................................................................................84 9.8. LICENCE................................................................................................................85 9.9. RZN ZKUENOSTI Z INSTALACE.................................................................................85 9.9.1. LINUX SUSE 64BIT, ORACLE 9.2......................................................................86 9.9.2. PATCHE ORACLE..............................................................................................86 9.9.3. STRUN PEHLED KROK PO INSTALACI................................................................86 10. Proces oprav aplikanho serveru SAP a licence.................................................88 10.1. VOD.................................................................................................................88 10.2. STAHOVN BALK...............................................................................................88 10.3. ABAP KERNEL PATCHES.......................................................................................88 10.4. ABAP SUPPORT PACKAGES OBECN........................................................................90 10.5. ABAP SUPPORT PACKAGES HR A HRCZ................................................................93 10.6. AKTUALIZACE SP V CRM A DALCH PRODUKTECH.......................................................94 10.7. SAP NOTE CORRECTIONS......................................................................................94 10.8. ZAMEN OBJEKTY A OBJEKTY V TRP........................................................................94 10.9. VYROVNN OBJEKT..............................................................................................94 10.9.1. MODIFIKACE DICTIONARY OBJEKT.......................................................................95 10.10. JAVA SUPPORT PACKAGES.....................................................................................95 10.10.1. PATCHES PRO SAP WEB AS JAVA..................................................................95 11. Upgrade systmu...................................................................................................96 11.1. UPGRADE STRATEGIE..............................................................................................96 viObsah


11.2. SYSTM SWITCH UPGRADE.....................................................................................96 11.3. NSTROJE PRO UPGRADE........................................................................................97 11.3.1. UPGRADE ASSISTANT.......................................................................................97 11.3.2. APPLICATION-SPECIFIC UPGRADE TOOLBOX..........................................................97 11.3.3. PREPARE................................................................................................97 11.3.4. ICNV........................................................................................................98 11.3.5. SAPUP NEBO R3UP.......................................................................................99 11.3.6. TRANSAKCE SGEN.....................................................................................102 11.4. UNICODE KONVERZE........................................................................................102 12. Sprva klient......................................................................................................103 12.1. CO JE TO KLIENT.................................................................................................103 12.2. VYTVOEN KLIENTA.............................................................................................103 12.3. VLASTNOSTI KLIENTA............................................................................................103 12.4. KOPROVN A TRANSPORT KLIENTA OBECN...............................................................104 12.5. TRANSPORT KLIENTA (EXPORT A IMPORT)...................................................................105 12.6. KOPROVN KLIENTA LOKLN..............................................................................105 12.7. KOPROVN KLIENTA VZDLEN............................................................................106 12.8. VMAZ KLIENTA...................................................................................................106 12.9. VCHOZ KLIENT..................................................................................................106 12.10. ITN ADRESE TRANS...................................................................................107 12.11. PROBLMY PI KOPROVN KLIENT.......................................................................107 13. SAP konektivita...................................................................................................108 13.1. INTERNET COMMUNICATION FRAMEWORK..................................................................108 13.2. SAPCONNECT....................................................................................................109 13.3. KOMUNIKACE......................................................................................................109 13.3.1. TESTOVN SPOJEN.......................................................................................109 13.3.2. SAPROUTER........................................................................................109 13.3.3. TECHNOLOGIE ALE.......................................................................................110 13.4. INTEGRACE S EP NW 7.0...................................................................................110 13.5. RFC SPOJEN NA SAPNET R/3 FRONTEND............................................................110 14. Archivace............................................................................................................110 15. Tisk a SAPscript...................................................................................................111 15.1. ZKLADN POJMY..................................................................................................111 15.2. FORMTY TISKU...................................................................................................112 15.3. SAPSCRIPT.......................................................................................................112 16. drba objekt v R/3 repository..........................................................................114 16.1. VYTVEN A DRBA OBJEKT................................................................................114 16.2. HISTORIE TABULEK...............................................................................................115 16.3. POVOLEN DRBY TABULKY A VIEW..........................................................................115 16.4. INDEXY..............................................................................................................115 16.4.1. VMAZ INDEXU.............................................................................................115 16.5. ZVLTN TABULKY...............................................................................................115 16.5.1. APQD.....................................................................................................115 16.5.2. BKORM..................................................................................................116 16.5.3. BSEG.....................................................................................................116 16.5.4. DBTABPRT A DBTABLOG.......................................................................116 16.5.5. SNAP.....................................................................................................116 16.5.6. DOASN SEKVENN DATA TEMSE...............................................................116 17. Pehled vvojovch nstroj................................................................................117 17.1. PACKAGES JAKO SADY OBJEKT...............................................................................118 18. SAP GUI Frontend............................................................................................119Obsah

vii


18.1. CO JE TO SAP GUI...........................................................................................119 18.2. INSTALACE..........................................................................................................119 18.3. ZPLATY............................................................................................................119 18.4. OK-CODE..........................................................................................................119 18.5. PROBLMY.........................................................................................................119 19. Poznmky o dalch oblastech............................................................................120 19.1. KONFIGURACE ONLINE DOKUMENTACE......................................................................120 19.2. MINISAP.........................................................................................................120 19.3. SYSTMY CRM.................................................................................................121 19.4. ERRORS............................................................................................................121 19.5. NKTER SYSTMOV ABAP TDY........................................................................121 19.6. ASOV ZNY, LETN A ZIMN AS............................................................................121 19.7. VZOR HLEN O ODSTVCE...................................................................................121 20. Seznam SAP notes.............................................................................................123 21. Rejstk................................................................................................................127 22. Plohy..................................................................................................................136 22.1. LEGENDA...........................................................................................................136 .............................................................................................................................137

viii

Obsah

STRUN PRUKA PRO SAP BASIS COMPONENTS (BC) 1.VOD

1. VODToto dlko vzniklo z poteby poznamenat si nkter zkuenosti, kter by mohli pomoci tm kte maj na starost firemn systmy SAP a maj na starosti i jin vci, ne jen SAP. Ale i konzultanti a zkuen administrtoi mohou tuto pruku pout alespo jako portl k dalm odkazm. Tyto poznmky vznikaly po provedench akcch, po rozhovorech s konzultanty, pi hledn rznch informac v SAP Library a v SAP notes. Clem tto pruky nen popsat pesn postupy, co je kolem firemnch manul, ale piblin popsat, jak na administraci pomoc mrn znalosti architektury systmu a souvislost. Pi tto pleitosti chci zvlt podkovat pnm Ing. Tomovi Holkovi, Ing. Martinu Huclovi, Ing. Janu Kaparovi, Ing. Karlovi Kluckmu, Ing. Janu Knigsmarkovi, Ing. Zdekovi Malmu a Ing. Radimu Martincovi, kte byli asto npomocni radou. Veker nepesnosti, chyby a omyly padaj samozejm pouze na mou hlavu. Aktuln verzi tto pruky najdete na adrese: www.volny.cz/priruckabc/SAPR3_BC_Guide.pdf Pipomnky laskav poslejte na adresu: [email protected].

1.1.1.O EM POJEDNV TATO PRUKA?Tato pruka pojednv v rmci SAP Netweaver o aplikan ABAP server zvan SAP Web AS a z aplikan vrstvy hlavn o to, co je zahrnuto v softwarovch komponentch SAP Basis Component a CrossApplication Component. Vysvtlen tchto termn je uvedeno v dalch kapitolch.

1.2.CO JE TO BC SAP NETWEAVER?Literatura: [Karch 2005], [KeoghJ 2005], [Woods 2004]. BC je oznaen pro technologick komponenty Basis Components systm firmy SAP AG, kter jsou zkladn aplikan platformou (server a integran platforma) vech mySAP.com een. Tyto komponenty zajiuj nkter abstrakce jako nap. SAP Basis (abstrahuje OS, databzov, sov a grafick rozhran.), ABAP. Nyn je nahrazuj komponenty oznaen nzvem SAP Netweaver komponenty a SAP Basis a ABAP zajiuje aplikan server SAP Web AS ( o nm ne). SAP Netweaver technologick platforma je modern integran a aplikan platforma, kter pomh redukovat nklady na vlastnictv (TCO). Pomh integrovat a uspodvat lidi, informace a byznys procesy pesahujc organizan a technologick hranice. SAP Netweaver jednodue integruje informace a aplikace prakticky jakhokoliv pvodu. Spolupracuje a me bt rozen pomoc pednch technologi dostupnch na trhu (Microsoft .NET, Suns J2EE, a IBM WebSphere). SAP Netweaver je technologick zklad pro mySAP Business Suite a SAP xApps een a zajiuje maximum dostupnosti, bezpenosti a roziitelnosti, stejn jako hladk provoz kriticky dleitch byznys proces. BASIS, bze a nsledn SAP Netweaver je vrstva, kter: 1) Nabz platformov nezvisl zklad pro psan podnikovch aplikac. 2) Nabz runtime prosted pro vykonvn podnikovch aplikac. 3) Nabz rzn nstroje, kter podporuj vvoj, levn provdn provoznch operac a upgrade. 4) K tmto ve uvedenm clm co nejvce pouv veobecn akceptovan standardy.

1/137


Zaneme trochu ze iroka1, abychom si mohli ukzat msto BC i SAP Netweaver. SAP nabz een pod souhrnnm oznaenm mySAP Business Suite/Solutions 2. Je to soubor adaptivnch een k optimalizaci obchodnch proces. Jsou to tato een: mySAP ERP, mySAP CRM, mySAP SRM, mySAP SCM, mySAP PLM. een mySAP ERP ucelen e ERP procesy v podniku. een jsou poskldan3 z povinnch i nepovinnch pslunch aplikanch komponent zvanch SAP Components, odvtvovch komponent a technologickch komponent SAP NetWeawer. Tato een jsou dodvna v rznch produktech4. SAP Components jsou: 5 SAP R/3 (a nsledn produkty ), SAP SCM, SAP CRM, SAP SRM, SAP SEM, SAP KW. Komponenta SAP R/3 obsahuje rzn moduly R/3 komponenty, nap. pro etnictv, controling, logistiku, vrobu a personalistiku a je pte celho podnikovho een, kter obsahuje vechny funkcionality potebn k podpoe podnikn v jednom systmu. SAP R/3 nebo jej nslednci jsou komponenty, ktermi se zan integran proces vtiny ostatnch een. V rmci mySAP SCM je pozoruhodn produkt uren pro plnovn produkce, kter je v souasn dob pika mezi podobnmi. Jedn se o SAP Advanced Planner and Optimizer (SAP APO), kter vyuv databzi in memory zvanou SAP LiveCache6. Proto jsou odezvy tohoto systmu tm okamit. SAP Netweaver komponenty jsou7:

1

SAP Web Application Server (SAP Web AS), kter je soust a zkladnm kamenem SAP NetWeaver Components. Tm vechny komponenty (SAP Components a SAP Netweaver) b nad SAP Web AS. Do release 46D se aplikan server nazv SAP Basis. SAP Business Intelligence (SAP BI), Business Explorer (Bex), SAP Business Information Warehouse (SAP BW), SAP Enterprise Portal (SAP EP), SAP Exchange Infrastructure (SAP XI), SAP Mobile Infrastructure (SAP MI)

Mnoho dalch informac a i souvislostech rznch komponent najdeme v tzv. Master Guide pro jednotliv een, kter nalezneme v SAP Service Marketplace. 2 Viz. www.sap.com/cz/solutions/. 3 Viz Product Availability Matrix v service.sap.com/releasestrategy/ . 4 Produkty: mySAP Customer Relationship Management (mySAP CRM ), mySAP ERP, mySAP ERP Financials (Finann zen), mySAP ERP Human Capital Management (mySAP ERP HCM), mySAP Product Lifecycle Management (mySAP PLM), mySAP Supplier Relationship Management (mySAP SRM), mySAP Supply Chain Management (mySAP SCM). Viz www.sap.com/cz/solutions/. 5 SAP R/3 nad SAP Basis 46D nebo jej nslednci nap. SAP R/3 Enterprise nad SAP Web AS ABAP 6.20 a 6.30 a centrln komponenta mySAP.com ERP zvan SAP ECC 5.0 nad SAP Web AS ABAP 6.40. 6 Zvltn instance databze MaxDB (SAPDB) - www.mysql.com/maxdb. 7 Viz www.sap.com/cz/solutions/netweaver/ a kapitola 9.1.

2/137


SAP Master Data Management (SAP MDM). Integran platforma SAP Netweaver umouje integraci vech ostatnch een SAP.

Odvtvov komponenta SAP for Industries nabz een pro rzn odvtv prmyslu v rmci tzv. SAP for Industries. Existuj een nejen pro prmysl8, ale i pro veejnou sprvu, koly a nemocnice. Jet je nabzena kompozitn aplikace SAPxApps9.

1.2.1.OBECN INFORMACE A REFERENCESAP Library je vlastn dokumentace dodvan k produktm. Online je k dispozici v SAP Help Portal (viz ne). Odkazy na SAP Library v tto pruce mohou bt zastaral. Pehlednost SAP Library se obecn dle mho nzoru zlepuje. V tto pruce se zkratkami SAP BC (pro R/3 46c) a SAP NW200410 (pro SAP Netweaver 2004 a podobn) uruje pslun SAP Library. SAP Library se aktualizuje po Support Package Stack11. Proto tyto odkazy na rzn release nemus bt aktuln: Basis Components v SAP Library Release 4.6C, April 2001. [SAP BC] SAP NetWeaver Components v SAP NetWeaver Components, Release 6.30, October 2003 SAP NetWeaver 2004 including BI Content. [NW2004]. SAP NetWeaver 2004s including BI Content Add-On ( jinm pohledem je nap. SAP NetWeaver by Key Capability). [NW2004s]. Doporuuji SAP Help Portal na internetu: help.sap.com. Zvlt vyhledvn je uiten. Je tam mimo jin online SAP Library. Dal vznamny zdroj informac a dokument je vem oblastem pro registrovan uivatele je SAP Service Marketplace [SAP SMP]: service.sap.com. Vce v kapitole 1.4. SAP Notes jsou na service.sap.com/notes/. V textu je asto oznaen note. Doporuuji asto prohlet SAP HotNews v SAP Notes. Nejlpe SAP HotNews . Nabdka nakladatelstv SAP PRESS na www.sap-press.de/. Tato pruka je urena vtinou pro systmy nad DBMS firmy Oracle (vyzkoueno nad 8.1.7 a R/3 release 4.6C) a vtinou pro Microsoft OS. Dal velk zdroj informac je SAP Developer Network na adrese: www.sdn.sap.com/. Rozcestnk: sap.ittoolbox.com/ ITToolbox for SAP Knowledge Base. Celkem pouiteln portl: searchsap.techtarget.com/. Dal nkter strnky z rznmi informacemi: www.sap-basis-abap.com/sapbs.htm www.basisconsultant.com/ www.basisguru.com/ www.sapadministration.com/ www.sapfans.com/ www.kabai.com/ www.geocities.com/rmtiwari/ www.sap-img.com/ www.sapgenie.com/ 8

Odvtv: Leteck prmysl & zbrojn vroba, automobilov prmysl, bankovnictv, chemick prmysl, prmysl spotebnho zbo, strojrenstv & stavebnictv, poskytovatel finannch slueb, zdravotnictv, university & vzkum, High Tech, pojiovnictv, mdia, zpracovatelsk prmysl, hornictv, petrochemick prmysl, farmaceutick prmysl, veejn sektor, retail, poskytovatel slueb, telekomunikace, utility. 9 Produkty: SAP Global Trade Services, SAP xApp Resource and Prog. Mgmt., SAP xApp Product Definition. 10 V URL meme zkusit zamnit odkaz na novj platformu, nap. nw2004 na nw2004s. Mohlo by to fungovat. NW2004s byl pozdji pejmenovn na NW 7.0 a dle. Tedy msto nw2004s se pouije nw70. 11 Aktualizovan verze SAP Library jsou ke staen na service.sap.com/nw04maintenance.

3/137


home4sap.com/ www.saptopsites.com/sapresources.html www.saptutorials.com/ www.sapbrain.com www.sapdevelopment.co.uk/ www.thespot4sap.com/ Samozejm nesmme zapomenout zkusit npovdu pmo v systmu, kterou v systmu stisknutm tlatka F1 na pslunm polku i dokumentaci k programm, pokud je napsna. O systmech na i5/OS od IBM mohu odkzat nap. na knihu z Redbooks: Implementing SAP Applications on the IBM System i Platform with IBM i5/OS.

1.3.DOPORUEN LITERATURAZde je uvedena vbrov literatura, kter se dotk administrace a programovn R/3 i SAP NW systm.

[Hagerman 2004]. S. Hagermann, L. Will: SAP R/3 System Administration, SAP PRESS, 2004, 520 s., ISBN 1592290140. [Hertleif 2003]. Werner Hertleif, Christoph Wachter: SAP Smart Forms, SAP Press, 2003, 450 s., ISBN 1592290108. [IBM 2003]. IBM Business Consulting GmbH: SAP Authorization System: Design and Implementation of Authorization concepts for SAP R/3 and SAP Enterprise Portle, SAP PRESS, 2003, 315 s., ISBN 1592290167. [Janssen 2007]. Susanne Janssen; Ulrich Marquard: Sizing SAP Systems, SAP PRESS, 2007, 85 s., ISBN 1592291562. [Karch 2005]. Steffen Karch; Loren Heilig: SAP NetWeaver Roadmap, SAP PRESS, 2005, 305 s., ISBN 1592290418. [KellerB 1998]. Bernard Keller, Thomas Teufel: SAP R/3 Process Oriented Implemenation, Addison-Wesley Pub Co; 1998, 845 s., ISBN 0201924706. [KellerH 2002]. Horst Keller, Sascha Kruger: ABAP Objects, Introduction to Programming SAP Applications, Addison-Wesley Pub Co, 2002, 576 s., ISBN: 0201750805. [KellerH 2003]. H. Keller, J. Jacobitz: ABAP Objects, The Official Reference, SAP PRESS, 2003, 1100 s., ISBN 1592290116. [KellerH 2005]. Horst Keller, Joachim Jacobitz: The Official ABAP Reference, SAP PRESS, 2005, 1200 s., ISBN 1592290396. [KellerH 2007]. Horst Keller: ABAP Objects, SAP PRESS, 2007, 950 s., ISBN: 1592290795. [KeoghJ 2005]. James Keogh, Jose Hernandez, Jos Antonio Hernndez, Franklin Martinez: SAP R/3 Handbook, McGraw-Hill Professional, 2005, 606 s, ISBN 0072257164. [Koesegi 2006]. Armin Koesegi, Rainer Nerding: SAP Change and Transport Management, SAP Press, 2006, 712s., ISBN 1592290590. [Lacko 2002]. Luboslav Lacko: Oracle Sprva, programovn a pouit databzovho systmu, CP Books (Computer Press), 2002, 480 s., ISBN 8072266993. [Lawlor 2004]. William Lawlor: Common SAP R/3 Functions Manual, Springer, 2004, 396 s., ISBN 1852337753.

4/137


[Loney 2002]. Kevin Loney; Marlene Theriault: Mistrovstv v Oracle Kompletn prvodce tvorbou, sprvou a drbou databz, CP Books (Computer Press), 2002, 896 s., ISBN 8072266357. [McFarland 2000]. Sue McFarland Metzger, Susanne Roehrs: Sap R/3 Change and Transport Management: The Official Sap Guide (Official Sap Guide), Sybex Inc; Bk & Cd edition edition (January 12, 2000), 870 s., ISBN 0782125646. [Missbach 2001]. Dr Michael Missbach, Uwe M Hoffmann: Sap Hardware Solutions: Servers, Storage, and Networks for Mysap.com, Prentice Hall PTR, 369 s., 2001, ISBN 0130280844. [Missbach 2004]. Michael Missbach, Ralf Sosnitzka, Josef Stelzel a Matthias Wilhelm: SAP System Operations, SAP Press, 2004, 350 s., ISBN 1592290256. [Mibach 2005]. Mibach, Gibbels, Krnstadt, Stelzel, Wagenblast: Adaptive Hardware Infrastructures for SAP, SAP Press, 2005, 534 s., ISBN 1592290353. [Neureither 2004]. Andreas Schneider Neureither: SAP System Landscape Optimization, SAP PRESS, 2004, 225 s., ISBN 1592290264. [SAP Labs 2002]. SAP Labs, Inc.; Palo Alto, Kalifornia: System Administration made Easy for SAP Basis 4.6C/D, 2002, 746 s., ISBN 1893570444. [Schneider 2006]. Thomas Schneider: SAP Performance Optimization Guide: Analyzing and Turning SAP Systems , SAP Press, 4. vyd., 2006, 515 s., ISBN 1592290698. [Stefani 2002]. Helmut Stefani: Archiving your SAP Data, SAP Press, 2002, 350 s., ISBN 1592290086. [Verruijt 2006]. Kees Verruijt, Arnoud Roebers, Anjo de Heus: Job Scheduling for SAP, SAP Press, 2006, 301 s., ISBN 1592290930. [Willinger 2004]. Michael Willinger, Johann Gradl: Migrating Your SAP Data, SAP PRESS, 2004, 300 s., ISBN 1592290280. [Woods 2004]. Dan Woods, Jeffrey Word: SAP NetWeaver For Dummies, Wiley Publishing, Indianopolis, 2004, 432 s., ISBN 0764568833.

1.4.SAP SERVICE MARKETPLACE[SAP SMP] service.sap.com/serviceconnection. SAP Service Marketplace nebo SAP Support Portal12, dve znm jako OSS, dnes jako SAPnet, m portl na adrese service.sap.com [SAP SMP]. Nebo pokud mme ustanoveno spojen13 na SAPNet pes VPN nebo SNC, pak pomoc transakce OSS1 nebo pomoc saplogon. Tento zpsob pestv bt podporovn. Byl to primrn zdroj potebnch balk, program a informac jako nap. SAP notes. Struktura komponent SAPNet je uvedena v SAP note 36677. V souasn dob se mnoh funkcionality pesouvaj do produktu Solution Manager, jeho soust se stv Maintenance Optimizer. Pokud se SAP note odkazuje na soubory ze sapserv* a mme spojen z OSS pes VPN nebo SCN , tak je stahujeme pomoc ftp z potae, kde b saprouter a je nejble bodu pipojen na stran OSS. V ppad VPN pouijeme ftp sapservX, kde adresa je sapserv1, tedy ftp 194.117.106.129, et ftp a heslo ftp. Pro SNC je adresa sapserv2 (194.39.131.34). Adresy sapservX jsou uvedeny v SAP note 17285. Pehled je v SAP note 35010. Vce k technickmu nastaven je v kapitole 13.5. V souasn dob je teba pro oteven spojen pro pstup SAP konzultant do systmu sputn na PC program LOP - Line Opener Program.12 13

Nzvy se rzn mn. K tomu t service.sap.com/internetconnection a service.sap.com/serviceconnection.

5/137


2. SPRVA APLIKANCH SERVERSAP Library: System Management [SAP NW2004]. Technical Operations Manual for SAP NetWeaver [SAP NW2004s].

[SAP SMP]: service.sap.com/systemmanagement. Sap Developer Network: SAP NetWeaver Operations. Dal rzn tipy i pro jin oblasti nalezneme v Best Practice for Solution Management dostupnch pes transakci SOLUTION_MANAGER v Solution Manageru. Dalm zdrojem informac je transakce transakci SSAA. V Analze chyb (program RSRRR_ROADMAP) najdeme dal informace i o i5/OS a jinch db ne Oracle.

2.1.ARCHITEKTURA APLIKANHO SERVERUSAP Library: Client/Server Technology (BC-CST) "Functional Units in SAP NetWeaver" Architecture of the SAP NetWeaver Application Server [SAP NW2004s]

Instalan pruky v [SAP SMP]:servic.sap.com/instguides/.

Zajmav novj pehled je uveden v Solution Operation Guide mySAP ERP 2005. SAP kernel (jdro) je odpovdn za vykonvn aplikac, zen uivatelskch proces, distribuci loh pracovnm procesm, zen pamti, pstup do databze, komunikaci s ostatnmi aplikacemi a zen SAP systmu. Je rozhranm mezi operanm systmem, databz a SAP aplikacemi, kter je zajitno samotnmi procesy disp+work v kad SAP instanci. V tto pruce se mluv o verzi jdra 46D, ale i o 6.xx a 7.xx. SAP kernel je kolekce vykonavatelnch soubor a knihoven v adresi v /usr/sap//exe/run14.

2.1.1.SOFTWAROV ORIENTOVAN POHLEDZkladn vrstvy15: 1) Databzov vrstva Tvo ji databze a DBMS (Database Management Systm). Dal zajmav informace najdeme v Fundamentals of database Layout, SAP AG, 200016. 2) Aplikan vrstva Tvo ji aplikan servery SAP Web Application Servers a message server. SAP Web AS obsahuje tyto sousti: Internet Communication Manager, kter zajiuje komunikaci s internetovskm prostedm, runtime engine pro ABAP, JAVA a Web Dynpro, Web Services Infrastructure, kter zasteuje podpory web slueb a konen Open SQL, kter zajiuje nezvislost aplikac na konkrtn relan databzi. 3) Prezentan vrstva Tvo ji hlavn klienti SAP GUI.

14

V i5/OS od jdra 6.40 je to kolekce Integrated Language Environment (ILE) objekt a Integrated File System vykonavateln soubory v adresi /usr/sap/SID/SYS/exe/run (Programs (*PGM), Service programs (*SRVPGM), Commands (*CMD), Physical files (*FILE PF), Data areas (*DTAARA), Message files (*MSGF), Menus (*MNU), Panel groups (*PNLGRP), Locales (*LOCAle)). Viz tak poznmka 24). 15 SAP Library: 16 Dokument DB_LAYOUT_EXTERNAL.pdf.

6/137

STRUN PRUKA PRO SAP BASIS COMPONENTS (BC) 2.SPRVA APLIKANCH SERVER

2.1.2.PROCESY V APLIKAN VRSTV ABAP TECHNOLOGIESAP Library: Introduction to ABAP [SAP NW2004]. Starting and Stopping SAP Systems and Instances [SAP NW2004]. Monitoring and Administration of the SAP Message Server [SAP NW2004]. Updates in the SAP System (BC-CST-UP) [SAP NW2004]. The SAP Lock Concept (BC-CST-EQ) [SAP NW2004]. Background Processing v Getting Started [SAP NW2004]. Background Processing [SAP NW2004]. Programming with the Background Processing System (BC-CCM-BTC) [SAP NW2004]. SAP Communication: CPI-C Programming (BC-CST-GW) [SAP NW2004]. Operating System Collector SAPOSCOL [SAP NW2004]. Functionality of Automatic Adjustment [SAP NW2004].

Tento seznam proces v architektue SAP WAS se tk ABAP technologie (ABAP work procesy) od jdra SAP Basis 46D ve. Jejich monitorovn je zmnno v kapitole 6.4. V i5/OS je kad proces jako dispatcher, pracovn proces nebo message server provdn jako i5/OS job17.

17

Monitoring se provd pkazy Work with Active Job (WRKACTJOB) a Work with Subsystem Jobs (WRKSBSJOB) nebo v nstroji iSeries Navigator.

7/137


SAP GUI SAP GUI SAP GUI DIA

Internet prohle Internet prohle Internet prohle Http/https Internet Communication Manager (ICM)

Internet prohle Internet prohle Internet prohle Http/https WEB Dispatcher

Dispatcher RFC

Extern systmy

Gate way

WP

WP

WP

JCo

Java Dispatcher

ABAP VM JAVA VM

ABAP VM JAVA VM

ABAP VM JAVA VM

JAVA SP Sdlen pam ABAP Central Services Message Server Enqueue server nebo WP typu EN Centrln instance nebo standalone JAVA VM

JAVA SP

SDM

Centrln instance ABAP/JAVA Engine

JAVA VM

Sdlen pam

SAP DB Schema

J2EE Engine

Dispatcher

Central Services

SAP DB Schema

Gate way

Message Server Enqueue server

WP

WP

WP

ABAP VM JAVA VM

ABAP VM JAVA VM

ABAP VM JAVA VM

Sdlen pam

Centrln instance nebo standalone

Dialogov instance ABAP /JAVA Engine

Poznmky: DIA - protokol nad TCP /IP pro komunikaci SAP GUI s aplikanm serverem Dialogov instance - posiluje centrln instanci systmu na dalm serveru Dispatcher - pidluje sti lohy - dialogov kroky - pracovnm procesm . Load balancing ABAP instance Java Dispatcher - load balancing J 2EE instance JCO SAP Java Connector Message server podporuje komunikaci s dispatchery load balancing systmu Enqueue server zajituje v celm systmu zamykn tabulek pu update tabulek , asto se pouv jeden WP RFC - Remote Function Call interface SDM - Software Delivery Manager . Pouze jedne na centrln instanci . SP - server proces . Jejich poet je konfigurovateln . VM - virtuln stroj. Java VM u WP nemus bt pouit. WEB Dispatcher load balancig pro web aplikace WP - pracovn proces typu DIA, BTC, UPD, UP2, ENQ, SPO (dialogov , prce na pozad , updatovac, enqueue , spool). Jejich poet je konfigurovateln .

Ilustrace 1: Principiln schma proces a jejich vazeb

2.1.2.1.SAPSTART A SAPSTARTSRV SERVICE Sapstartsrv service sapstartsrv.exe. Tak SAP service SAP_. Sapstartsrv je specialita Microsoft WINDOWS NT.Na zklad poadavku startsap.exe nebo stopsap.exe nebo ze MMC snapin SAP R3 Systems18 okna nastartuje nebo zastav instanci18

Mono nainstalovat dle instrukc na instalanm CD kernelu.

8/137


R/3. Pi zastaven se po chvli znovu automaticky spust. Databzi spust skriptem strdbs.cmd. V UNIXu b proces sapstart, kter na zklad poadavk skript startsap a stopsap operuje s instanc systmu i DB. Startsap spust saposcol, db instanci a sapstart. Program sapstart spust message server, proces programu rslgcoll zapisujc do centrlnho systmovho logu (co.sap_) a proces programu rslgsend19 poslajc informace do centrlnho systmovho logu (se.sap_)20 21. Message server spust dispatcher. Dispatcher spust gateway, icman a ostatn pracovn procesy. O logovn v poznmce 69. V i5/OS se job jmenuje SAPSTART (funkce PGM-sapstart)22. Proces startu systmu je zen startovacm profilem (START_< INSTANCE_NO>_). Nastaven parametru AUTOSTART na hodnotu 1 umouje atomatick startovn systmu SAP. 2.1.2.2.MESSAGE SERVER Message server program msg_server[.exe]. V UNIXu se proces jmenuje ms.sap_23 a v i5/OS se job jmenuje MSG_SERVER. Zajiuje komunikaci mezi instancemi jednoho systmu. B na R/3 centrln instanci. Je mu piazen port 36 se jmnem sapms. Z bezpenostnch dvod (SPOF Single Point of Failure) me bt pouit standalone na jinm stroji. Spout se ped dispeerem. Umouje zpracovn dialogovho kroku pracovnm procesem jin instance systmu. 2.1.2.3.DISPATCHER Dispatcher program dispeer disp+work[.exe] (nebo i5/OS library objekt DW.PGM v R3OPT.LIB24) v adresi /usr/sap//SYS/exe/run25. V UNIXu se proces jmenuje dw.sap_ a v i5/OS se job jmenuje DISP_WORK26 (funkce PGM-disp +work). Komunikuje se SAP GUI (presentan vrstva R/3), zajiuje pipojen RFC users a d prci pracovnch proces pidlovnm dialogovch kroku pracovnm procesm k zpracovn. Pouv komunikan tabulku pro sprvu spojen. Je mu piazen port 32 se jmnem sapdp. V transakci SM50 meme nahldnout do logu v menu Proces Sledovn Dispeer nebo externm nstrojem dpmon[.exe]27. 2.1.2.4.PRACOVN PROCESY Pracovn procesy program disp+work[.exe] (nebo i5/OS library objekt DW.PGM v R3OPT.LIB) v /usr/sap//SYS/exe/run28. V UNIXu se proces jmenuje dw.sap_ a v i5/OS se job jmenuje WP (funkce PGM-disp+work). Jsou to vlastn procesy R/3 aplikanho serveru, kter vykonvaj ABAP lohy (task) aplikanho serveru.

19 20

SAP note 119827 popisuje nastaven trasovn. Viz poznmka 23). 21 V i5/OS se job s podobnou funkci jmenuj RSLGCOLL a RSLGSEND. 22 Pesnji je to popsno v transakci SSAA v Analze chyb (program RSRRR_ROADMAP). 23 Spust se takto pojmenovan link v adresi [DIR_HOME]. Podobn i pro disp+work. 24 Jmno i5/OS knihovny pro kernel se me liit na rozdl od jmen vlastnch objekt kernelu. 25 Nebo : \usr\sap\\SYS\exe\run\ ve Windows nebo v i5/OS v /QSYS.LIB/R3OPT.LIB/. 26 Zde je mimo pracovnch job Dw jet dal job WATCHDOG te funkce. 27 Viz kapitola 6.4. 28 Nebo : \usr\sap\\SYS\exe\run\ ve Windows nebo v i5/OS v /QSYS.LIB/R3OPT.LIB/.

9/137


Typy loh pracovnho procesu Typy loh jsou: Dialog, Update, Update2 (2), Spool, nkdy uvdn Batch input, Batch, Enqueue, Bufsync (Y), Autoabap, CPIC (C), RFC (R), ALE (L), HTTP (H), HTTPS (T), NNTP (N), SMTP (M), FTP (F). Komponenty pracovnho procesu Obsahuj komponenty pro tyto innosti: task handler, 29 ABAP procesor , screen procesor, sprva rolovn pamti, sprvu blokovn, tisk, bezpenost, ladc systm, batch, databze a DBSL (rozhran pro DB), strnkovn, dialogov procesor, sprva IPC, sprvu extended memory, XSLT procesor (od 6.10), 30 VMC (SAP Virtual Machine Container , od patch level 29 release 7.0). Stavy pracovnho procesu Pracovn procesy nabvaj nkolika stav: waiting (ek na poadavek), running, hold a stopped (kvli chyb). Dvody stavu hold mohou bt rzn31, nap.: DEBUG (pracuje v reimu ladn a ek na zadn), RFC (ek na odpov voln RFC), ARFC (ek asynchronn RFC), ENQ, VB (ek update), SPO, ADM (ek na zsah administrtora), NUM ( ek number range server), GUI (ek na frontend), PRIV (proces je vyhrazen pro jednoho uivatele), VBADM (ek na update server), SLIST (ek na server list), GWMON (ek na gateway), SNC (ek na vytvoen security), LOCK (byl piazen k systmov analze), MS (ek na synchronizaci s message serverem), MSOP (ek na odpov message serveru), OS (ek na operan systm), SLEEP (ek z dvodu nedostatk zdroj), RPC (ek na generovn programu ABAP), JAVA (m lokln Java-stack). Pamov oblasti a zen pamti Kadmu pracovnmu procesu je alokovna pam z virtuln pamt, co je v tomto ppad fyzick pam a OS paging file nebo OS swap file. Virtuln pam (virtual memory) je rozdlen na lokln pam (local memory) a sdlenou pam (shared memory). Lokln pam vyuvaj jednotliv pracovn procesy pro sebe a obsahuje: ABAP load (obsahuje peloen kd program) Data, stack Buffer pro penosy z databze29

Jako zajmavost zde uvedu odkazy na seznam C funkc kernelu, kter se mohou volat z ABAP prosted: Frank Dittrich a frum na SAP Developer Network. 30 SAP Library: SAP Virtual Machine Container [SAP NW2004s]. VMC integruje Java VM do ABAP pracovnho procesu, kde paraleln b ABAP i Java ve svm vlastnm VMC. Monitor je transakce SM52, kter je dosaiteln tak z transakce SM51. O aktivaci SAP note 854170. 31 Aktuln informace o stavech nalezneme v helpu k pslunmu polku transakce SM50.

10/137


Local roll area (obsahuje autorizace, Set/Get parametry, intern tabulky, seznamy vygenerovan reporty) Local paging area (pam pro specifick ABAP pkazy) Heap memory (na vydn pokud je extended memory pln, obsahuje stejn objekty jako extended memory, kter je ale sdlen32) Sdlen pam je alokovan pi startu instance systmu a obsahuje: SAP buffery (objekty pro vechny uivatele a pracovn procesy jakou jsou programy a obsahy nkterch tabulek) Extended memory (obsahuje objekty spojench s neukonenmi transakcemi jako jsou promnn, seznamy a intern tabulky) Roll buffer a SAP roll file (obsahuje inicializan user kontext) SAP paging buffer a SAP paging file (obsahuje ABAP objekty jako extrakty a kontextov nezvisl objekty jako jsou exporty) Pracovn procesy vyuvaj lokln pam, pro kter je v pamovm prostoru pracovnho procesu vyhrazena oblast pro roll memory, paging memory a heap memory a sdlenou pam (shared memory) mezi dalmi procesy s oblastmi extended memory a buffery.

Alokace SAP memory Pokud aplikace poaduje pam, tak se alokuje pam u dialogovho procesu obecn takto: 1) Roll In Z roll bufferu se nakopruje do lokln roll oblasti prvn segment roll area (ztta/roll_first). Ze SAP paging bufferu se nakopruje do lokln paging oblasti data. 2) Alokuje se mapovnm33 pam z extended memory34. (ztta/roll_extension(_dia)) 3) Alokuje se 2. pomocn segment z roll area. (ztta/roll_area - ztta/roll_first) 4) Alokuje se z heap memory a proces se pepn do stavu PRIV. (abap/heap_area_dia) P pepnn kontextu procesu se provd Roll Out, kdy se roll a paging area kopruje do Roll bufferu a SAP paging bufferu. Prce s databz Kad R/3 pracovn proces je obsluhovn vlastnm DB serverovm user procesem35. Pokud je perueno spojen s db, pak se pracovn procesy, pokud je to nastaveno v profilu pokou o

32

Pokud aplikace potebuje tuto lokln pam, tak pracovn proces se pepne do stavu PRIV a potom u tento proces nen mon sdlet pro jin lohy dokud aplikace nen ukonena nebo pracovn proces nen restartovn bu run nebo automaticky dle hodnot nkterch parametr profilu. 33 Implementace extend memory se u rznch OS li. U NT je nap. trochu jinak ne u ostatnch OS (tzv. Zero Administration Memory). Novji je mon v Linuxu pout podobn zpsob. V adresovm prostoru pracovnho procesu je pouze aktuln uivatelsk kontext. Adresy segment uivatelskho kontextu z extended memory se pepotvaj v adresovm prostoru pracovnho procesu tak, aby oblast pro extended memory byla vyplnna od zatku (aspo tak to chpu :-)). Toto zen pamti je ureno parametrem es/implementation=map. Zvis na velikosti parametr PHYS_MEMSIZE, em/address_space_MB a em/max_size_MB. V UNIX a Linux 64bit jsou v adresovm prostoru pracovnho procesu viditeln vechny uivatelsk kontexty. Hodnoty parametr PHYS_MEMSIZE, em/address_space_MB, em/initial_size_MB a em/max_size_MB jsou relevantn. Toto zen pamti je ureno parametrem es/implementation=std. Vce o tom v SAP Library a nap. SAP note 386605 a 941735. 34 U non-dialogovch pracovnch proces v UNIXU se rovnou alokuje z lokln heap memory. Tedy krok 2) Heap memory (abap/heap_area_nondia) a krok 4) Extended Memory (ztta/roll_extension(_nondia)). 35 V transakci ST04, nap. - detail analysis menu, Oracle session, R/3 WPs - je vidt piazen R/3 pracovnch a DB proces.

11/137


reconnect36. Sledovat a monitorovat meme v transakci SM50, SM66 nebo RZ03. Vce je v kapitole 6.4. Typy pracovnch proces Pracovn proces me za bhu zmnit svj typ37 pi zmn operanho mdu. Jsou tyto typy38 pracovnch proces: DIA dialogov, zpracovv dialogov pkazy. Je uren pro interaktivn prci uivatel. Nejmen jednotka prce je dialogov krok. Na konci kadho dialogovho kroku se provede databzov transakce a vymaou se databzov zmky. Minimln mus bt dva tyto procesy v instanci. UPD aktualizan, zpracovv pkazy update typu V1, kter ma vysokou prioritu k aktualizaci. Dal informace jsou v kapitole 2.6. UP2 aktualizan, zpracovv pkazy k aktualizaci typu V2 stejn jako UPD. Update typu V2 m nzkou prioritou a zpracovv se, a kdy jsou zpracovny update typu V1. Na rozdl od typu V1 nepouv enqueue zmky, pouv se napklad pro update statistickch tabulek. Dal informace jsou v kapitole 2.6. ENQ enqueue server. Zajiuje sprvu logickch zmk (tzv. Enqueue zmk) objekt, kter potebuj bt zamknuty po dobu vykonvn vce dialogovch krok. Vtinou jen jeden ENQ proces v systmu39 a to i pro Web AS. Z bezpenostnch dvod (SPOF Single Point of Failure) me bt pouit u platformov nezvisl standalone enqueue server (enssserver[.exe], enrepserver[.exe] a monitor ensmon[.exe]) na jinm stroji a me bt replikovn. Dal informace jsou v kapitole 2.7. BTC zpracovv dvkov pkazy (bez interakce uivatel, joby). Dal informace jsou v kapitole 2.5. 40 SPO spoolov server, zpracovv spoolov poadavky . Vtinou sta jeden v instanci. Poet tchto proces nelze mnit operanmi mdy, protoe maj odlinou strukturu od ostatnch pracovnch proces. Dal informace v kapitole 15. 2.1.2.5.GATEWAY SERVER Gateway server gwrd[.exe], gateway read proces, zajiuje vekerou RFC a CPC komunikaci mezi externmi aplikacemi a systmy mySAP.com a dispeerem. V i5/OS se job jmenuje GWRD (funkce PGM-disp+work). Je mu piazen port 33 se jmnem sapgw. 2.1.2.6.GATEWAY WORK PROCES Gateway work proces gvwp[.exe] zajiuje komunikaci pes LU6.2 nebo DCAM v sov architektue SNA41. 2.1.2.7.ICM INTERNET COMMUNICATION MANAGER ICM Internet Communication Manager icman[.exe] a v i5/OS se job jmenuje ICMAN (funkce PGM-icman). V ppad poteby je startovn dispeerem42. Zajiuje komunikaci36 37

Parametry profilu rsdb/reco. Dle SAP note 98051 a dle v kapitole 3.10. Smysl to m hlavn u typ DIA a BTC, ale me se mnit i poet jinch. Jen nesm tento poet klesnout pod ppustnou mez. 38 Pokud se mn typ nap. pi zmn operanho modu, provede se bez restartu pracovnho procesu. 39 Viz parametr profilu rdisp/wp_no_enq. 40 Vce kapitola: 15. 41 Pro milovnky sov architektury SNA je jet k dispozici program gwhost jako APPC transportn program pro CICS. 42 To je ureno parametrem profilu rdisp/start_icman.

12/137


mezi SAP systmem a ostatnm svtem pomoc HTTP, HTTPS a SMTP protokolu. Komunikuje s dispeerem, pomoc dispatcher queue a pes memory pipes s pracovnmi procesy. Pracuje pomoc nkolika vlken. Z hlediska vkonnosti se lad velikost buffer nastavenm nkterch parametr profilu icm/HTTP/server_cache/*, kter jsou ti: UFO Cache (pro neexistujc sluby), Memory Cache a Disk cache. Tak je mon ladit parametry43 poet vlken, poet spojen atd. Mezi vce systmy s ICM balancuje vkon SAP Web Dispatcher. 2.1.2.8.SAPOSCOL Saposcol saposcol[.exe] a v i5/OS job se jmnem SAPOSCOL (funkce PGM-saposcol) zajiuje shromaovn dat o OS44. Pouv se p monitorovn systmu CCMS. Sprva se provd v transakci ST06, OS06, OS07 a OS07N45 nebo pmo programem saposcol (parametr h). Dal informace jsou v Operating System Collector SAPOSCOL: Properties, Installation, and Operation. 2.1.2.9.AGENTI PRO SAP ADAPTIVE COMPUTING Od SAP systm Landscape Directory (SLD) zskv Adaptive Computing Controler (ACC) informace o existujcch zdrojch server. SLD zskv informace od kadho uzlu poolu pomoc tchto agentu. Vce o tom [Mibach 2005]. saposcol je jeden z agent kadho pool uzlu pi een SAP Adaptive Computing (AC). sapacoscol pedv data ze saposcolu do SLD. sldreg registruje uzel do SLD. sapacosprep nastavuje prosted aplikan sluby aktivace a deaktivace storage, montovn a odmontovn file systm a aktivace a deaktivace virtulnch IP adres. Klientsk knihovny od HW dodavatele. ACC tak kontroluje SAP systm pomoc startsap a stopsap. 2.1.2.10.SAPCPE SAP Library:Local Executables on SAP Instances [SAP NW2004s].

Sapcpe proces, kter automaticky vyrovnv na loklnch instancch provediteln programy v loklnm adresi /usr/sap//exe/run z centrlnho adrese /usr/sap//exe/ctrun. Je vyvoln za splnn uritch podmnek46 programem sapstart, kter je zen parametry profilu instance. Parametr DIR_CT_RUN uruje centrln adres a DIR_EXECUTABLE lokln adres. Funguje pod OS typu UNIX i Windows. Program saposcol, kter v okamiku vyvoln sapcpe u b, by se neml takto aktualizovat. Konfigurace se provd pomoc seznam soubor v souborech jako instance.lst, instancedb.lst, tools.lst, atd. Parametry zjistme pkazem sapcpe help. Log je v [DIR_HOME]/sapcpe.log.

2.1.3.PROCESY V APLIKAN VRSTV JAVA TECHNOLOGIESAP Library: 43 44

Architecture Manual [SAP NW2004s]. J2EE Engine [SAP NW2004s]. Architecture of the Java Startup and Control Framework [SAP NW2004s].

SAP note 737625. SAP note 548699. 45 SAP note 1084019. 46 Viz Functions of the Automatic Adjustment [NW2004].

13/137


Od jdra SAP WAS 6.10 pibyla navc technologie JAVA podporujc Web AS. Java cluster47 architektura sestv z jedn nebo vce instanc Web AS Java a z Central Services, kter tvo instanci a z jedn nebo vce databz. 1) Java Startup a Control Framework: 1.1) Proces programu JControl startuje, zastavuje a monitoruje procesy Java instance a spout procesy programu JLaunch, kter startuj JAVA VM do vlastnho procesu a startuj vlkno, kter kontroluje, zda b Jcontrol a pokud ne, ukon Jlaunch procesy. Postupn nastartuje tyto Jlaunch procesy a potom je nadle kontroluje a d: 1.1.1)JLauch proces, kter spust bootstrap Java program procesy Java clusteru48. Bootstrap program synchronizuje binrn data Java databze s file systmem a pipravuje informace (popis J2EE instance) , kter JControl potebuje ke sputn Java clusteru. 1.1.2)JLaunch dispatcher pro kad Java cluster. Proces jlaunch[.exe] 1.1.3)JLaunch Server proces(y) jlaunch[.exe], kter dle tvo SAP J2EE Engine System Architecture49. 2) Central services, kter mohou slouit pro vce JLaunch dispatchery a tedy pro vce instanc SAP Web AS Java50: 2.1) Message server, proces msg_server.exe. 2.2) Enqueue server, proces enserver.exe. 2.3) Software Deployment Manager (SDM, jlaunch.exe) 3) Load balancing mezi instancemi, kter le mezi Internetem a st s SAP Web AS servery: 3.1) SAP Web Dispatcher 3.2) Jin load balancing device, kter se zaregistruje na serveru a portech

2.1.4.ZEN PAMTI, SDLEN PAM A LOHYSAP Library: Memory Management (BC-CST-MM) v Client/Server Technology (BC-CST) v Basis Components [SAP NW2004]. SAP Buffers v CCMS Monitoring v Computing Center Management System (BC-CCM) v Computing Center Management System (BC-CCM) v Computing Center Management System (BC-CCM) [SAP NW2004].

Zde se pokoum o velice zjednoduen popis51 zen pamti v ABAP AS. Aplikan server zpracovv jednotliv lohy (tasks) v tzv. dialogovch krocch postupn pracovnmi procesy. Kad loha m svj kontext (user context), kter je uloen ve sdlen pamti v roll bufferu a obsahuje roll areu52 (1. roll segment, 2. (pomocn) roll segment), extended memory a private (local) memory (heap). Pepnn kontext m na starosti task handler pracovnho procesu. Dle lohy maj k dispozici sti sdlen pamti zvan SAP buffery: Nametab buffer, NTAB Obsahuje data z tabulek DDNTT (definice tabulek) a DDNTF (popis pol), kter jsou uloena ve tyech bufferech souhrnn zvan Repository buffer nebo ABAP Dictionary buffer. Table definitions, TTAB Obsahuje data z tabulky DDNTT.47 48

Popis v Architecture Manual [SAP NW2004]. Cel proces je popsn nap. v Startup, Operation and Shutdown of a Java Instance [SAP NW2004]. 49 Tato problematika pesahuje skromn cl tto pruky poslouit obyejnm administrtorm. 50 Kontrola na UNIXu pkazem: ps -ef | grep jlaunch i ps -ef | grep java | grep adm 51 Pramenem byla presentace Shared Memory Programming with ABAP od Andrease Blumenthala. 52 Roll area je pamov oblast pevn (konfigurovateln) dlky, kde je uloen kontext sezen (session).

14/137


Field descriptions, FTAB Obsahuje data z tabulky DDNTF. Initial record layouts, IREC Obsahuje zznam layoutu inicializovan v zvislosti na typu pole. Short Nametab, SNTAB Obsahuje krtk souhrny z bufferu TTAB a FTAB. Program Buffer, PXA Obsahuje vykonavateln verze ABAP program zvan loady. Obsah tohoto bufferu je z tabulek D010L (ABAP loads), D010T (texty) a D010Y (tabulka symbol). Zdrojov texty jsou uloeny v tabulce D010S a bhem pekladu (nebo generace) jsou vytvoeny loady a uloeny do ve uvedench tabulek. Obsah PXA je pi shutdownu systmu uloen do souboru pxanew53 a pi startu je obsah naten nejdv z pxastat, potom z pxanew. Pxanew je nakoprovn do pxastat a je smazn. CUA Buffer (Menu buffer) Ukld objekty pouvan SAP GUI jako menu a definice tlatek. Jsou to objekty z tabulek D345T (CUA texty) a D342L (CUA loady). Screen Buffer Obsahu vygenerovan screeny zvan nkdy Dynpro loads. Calendar Buffer Obsahuje definice firemnch a veejnch svtk v kalendch z tabulek TFACS a THOCS. OTR Buffer Online Text Repository obsahuje texty pouvan v BSP, Exception Builderu a http slubch. Generic Table Buffer Ukld ve shod s nastavenm v ABAP dictionary rozsah zznam tabulek z jejich hodnotami. Single Record Table Buffer Ukld jednotliv zznamy tabulek. Export/Import Buffer Jsou v nm data, kter mus bt dostupn nkolika pracovnm procesm. Systm je pln nebo te pomoc ABAP pkaz EXPORT TO/IMPORT FROM SHARED BUFFER. Exp./Imp. SHM Zde jsou ukldan data ABAP pkazem EXPORT TO SHARED MEMORY. Vlastnosti sdlen pamti lze prohlet v transakci ST02 (viz. kapitola 6.1.2). Podrobnou analzu pamti na rovni proces operanho systmu typu NT mono zskat pomoc programu SAP Address Space Viewer, kter zskme v SAP note 129813. Zde uvedu pklady voln pkaz na rovni OS, kter zobraz detaily o sdlen pamti54, sappfpar pf= check #Shared Memory Test Environment for SHARED MEM shmd pf/ echo "1 -1 4 0 10" | shmd pf=/ echo "1 -1 4 1 10" | shmd pf= ipcs -ma

53 54

SAP note 23642. Kde je nap. v bash shellu je uveden v kapitole 5.1.

15/137


2.1.5.SAP SYSTM A INSTANCESAP systm obsahuje vechny komponenty jako jsou aplikan servery a message server, kter maj pm i nepm pstup do databzov instance55. SAP systmy jsou identifikovny temi psmeny . SAP instance je soubor proces a zdroj v SAP systmu pro obslouen poadavk koncovho uivatele. Kad SAP instance m svj SAP profil a sv jmno56. Instance: 1) Centrln instance (CI) message server s disp+work procesy s enqueu nebo gateway serverem. V kadm SAP systmu je vdy jedna centrln instance. 2) Dialogov instance pouze disp+work procesy a gateway server. Instaluje se pi zvtovn dimenze systmu. 3) Separtn SCS instance message server a enqueue server. Potom neb na R/3 centrln instanci. Instaluje se nebo oddluji kvli vysok dostupnosti57. 4) Standalone gateway instance gateway server. 5) Standalone enqueu instance enqueue server, potom neb na R/3 centrln instanci. 6) Standalone message server message server, potom neb na R/3 centrln instanci. 7) DB instance. Pro kad SAP systm je jedna. Podle toho, kde je nainstalovan se bu jedn o tzv. centrln ABAP systm, pokud je DB instance na stejnm hostu jako CI, nebo distribuovan ABAP systm, kdy DB instance je na vyhrazenm hostu.

2.1.6.SYSTMOV KONFIGURACE1) Central system R/3 centrln instance na jednom stroji s DB instanc. 2) Standalone database system R/3 centrln instance a DB instance na rznch strojch.

2.1.7.SAP SYSTEM LANDSCAPE[SAP SMP]: service.sap.com/instguides/ ( hlavn Master Guides). SAP Library:Change and Transport System Overview (BC-CTS) v Change and Transport System (BC-CTS) v Basis Components [SAP NW2004].

Literatura: [Neureither 2004]. Kad SAP implementan projekt prochz rznmi fzemi v uritm poad. Pro projekt implementace se pouv nkolik typ systmu. Zmnov a transportn systm (CTS Change and Transport System) pomh dit a provdt transport zmn konfigurace, upgrade, patches, a nov vyvinutch zmnnch R/3 repository objekt. Typy systmu: Centrln komponenty jako Solution Manager a centrln monitorovac systm CCMS. Cvin, pokusn systmy a systmy s pskoviti. Mou bt mimo CTS. Systmy pro testy (DEV) a ovovn kvality (QAS). 58 Produktivn systm (PRD ). 2.1.7.1.SOLUTION MANAGER Tento server je nyn povinn soust kad instalace u kvli generovn instalanch a upgradovacch kl. Dle slou jako podprn systm pro provozovn SAP landscape dle doporuen ITIL, pro zen implementanch projektu a customizingu.55

V i5/OS instance me SAP instance bet ve vlastnm i5/OS subsystmu. Nebo ve vlastn logick partition LPAR. 56 Viz kap 5.2 a poznmka 57). 57 SAP Central services. SAP note 821904. 58 V etin zn pinejlepm humorn.

16/137


Dleit transakce: SMSY (systm Landscape), SMSY_SETUP, SOLUTION_MANAGER a SOLAR_PROJECT_ADMIN. Dle Roudmap repository RMDEF a prohlen roadmap v RMAUTH. 2.1.7.2.SYSTEM LANDSCAPE DIRECTORY [SAP SMP]: service.sap.com/sld/ ( nap. Planning Guide). SAP Library:System Landscape Directory [SAP NW2004s].

System Landscape Directory SAP Netweaver (SLD) je centrln repository pro provozovan landscape zaloen na Common Information Model (CIM). Je to jedna WAS JAVA aplikace dostupn na adrese http://:/sld. Tam se aktivuje a provede poten naplnn CIM databze. Na WAS ABAP jako dodavatel dat do SLD pouv RFC spojen typu TCP a nastavuje se v transakci RZ70. Vytvoen job SAP_SLD_DATA_COLLECT pro jistotu zkontrolujeme a nastavme periodicitu. V SLD tento systm potom pidme do systmovho landscape. Solution Manager a XI vyuv SLD API. Pomoc Visual Administrtoru dle SAP Library vytvome JCo RFC Provider a jeho jmno pouijeme jako registran program pro RFC spojen typu TCP na stran XI nebo SolMan. O registraci do SLD je SAP note 1018839. O update komponent SAP note 669669.

2.1.8.ADRESE APLIKANHO SERVERU ABAP TECHNOLOGIEPopis je uveden v instalanch prukch dostupnch v SAP Service Marketplace. Viz tak transakce AL11. Uveden parametry v zvorkch [] jsou parametry profilu R/3, krermi meme adrese uspodat jinak.Pklad z praxe (OS WinNT a Oracle 8.1) C:\users\adm\install (program R3setup, konfiguran soubory, logy) C:\users\adm\install\doc (online help k R3setup) D: SAPMNT_ERAEXE (sap, ora home) D:\oracle\ora81 [DIR_ORAHOME] D:\oracle\ora81\network\ADMIN (listener.ora, tnsnames.ora) D:\oracle\ora81\database\init59.dba (konf. sap dba) D:\oracle\ora81\database\init.ora (konf. dba) D:\oracle\ora81\database\init.sap (konf. sap backup) D:\oracle\ora81\database\init.utl (CA backint konf. sap backup) D:\usr\sap\60\ 61\ (jmno instance) [DIR_INSTANCE] data (data pro hodnocen zaten v ST03) [DIR_ATRA] [DIR_DATA] [DIR_EXTRACT] [DIR_PAGING] [DIR_REORG] [DIR_ROLL] log (audit logy ) [DIR_AUDIT] [DIR_LOGGING] [DIR_PROTOKOLLS] sec igs j2ee (pokud je nainstalovan java Add-In) admin cluster JSPM configtool SDM (pokud je nainstalovan java Add-In) sec exe (jen u distribuovanch systmu) work (tracefiles a logy, error logy dispatcheru, work proces apod. viz tr. ST11) [DIR_HOME] sys: [DIR_INSTALL] exe [DIR_EXE_ROOT] [DIR_CT_RUN] dbg opt run (SAP kernel, programy jako napr BR*Tools, tp.exe, R3trans.exe ad.) [DIR_BINARY] [DIR_EXECUTABLE] [DIR_GEN_ROOT] [DIR_GRAPH_EXE] [DIR_GRAPH_LIB] [DIR_LIBRARY] [DIR_RSYN] gen [DIR_GEN]59 60

je jmno instance (mlo by bt uvedeno v provozn pruce). Domnov kontrolr D:\usr\sap\ sdl nap. jako SAPMNT. 61 je slo systmu (mlo by bt uvedeno v provozn pruce).

17/137


global (protokoly map batch input) [DIR_CT_LOGGING] [DIR_GLOBAL] profile (profily instance) [DIR_PROFILE] [DIR_SETUPS] src [DIR_SORTTMP] D:\usr\sap\put\ [DIR_PUT] (adres pro shadow systm pi upgrade) D:\usr\sap\trans\ nebo \\trans (pouze na domnovm kontrolru) [DIR_TRANS] actlog bin (konfiguran soubor na domnovm kontrolru TP_DOMAIN_.pfl) buffer cofiles (transportn soubory dc) data (transportn soubory datov) eps [DIR_EPS_ROOT] in (rozbalen balky car) log out etc log sapnames tmp Pozn.: tablespace sapdata, archivn redolog, zrcadlen redology a sapbackup mohou bt nakonfigurovna jinak. E:\oracle\\: mirrloga (redology, zrcadlo sady a) origlogb (redology, originl sady b) saparch (archivn redo logy) F:\oracle\\: sapbackup (logy z kontrol DB a zlohovn) \ sapcheck (pracovn adres pro kontrolovn DB, logy BR*tools) sapdata1 (datafiles DB, stejn a do sapdataN, zde konkrtn 6) sapdata2 sapdata3 sapdata4 sapdata5 sapdata6 sapreorg (pracovn adres pro reorganizaci DB) saptrace (logy, pi defragmentaci, ora_.trc) background (ALRT.log DLEIT, logy pomocnch proces Oracle) usertrace (logy uivatelskch proces Oracle) Pklad z praxe (OS UNIX a Oracle 9.2): /usr/sap [DIR_INSTANCE] data (data pro hodnocen zaten v ST03) [DIR_ATRA] [DIR_DATA] [DIR_EXTRACT] [DIR_PAGING] [DIR_REORG] [DIR_ROLL] cache igs bin conf data dump lib log test log (audit logy ) [DIR_AUDIT] [DIR_LOGGING] [DIR_PROTOKOLLS] sec work (tracefiles a logy, error logy dispatcheru, work proces apod. viz tr. ST11) [DIR_HOME] SYS [DIR_INSTALL] exe [DIR_EXE_ROOT] dbg > /sapmnt//exe opt run -> /usr/sap//SYS/exe/dbg (SAP kernel, programy jako napr BR*Tools, tp, R3trans ad.) [DIR_BINARY] [DIR_EXECUTABLE] [DIR_GEN_ROOT] [DIR_GRAPH_EXE] [DIR_GRAPH_LIB] [DIR_LIBRARY] [DIR_RSYN] gen [DIR_GEN] dbg opt global -> /sapmnt//global (protokoly map batch input) [DIR_CT_LOGGING] [DIR_GLOBAL] profile -> /sapmnt//profile (profily instance) [DIR_PROFILE] [DIR_SETUPS] src [DIR_SORTTMP] trans (pouze na domnovm kontrolru) [DIR_TRANS] EPS (transportn soubory datov) in (rozbalen balky car) log out bin (konfiguran soubor na domnovm kontrolru TP_DOMAIN_.pfl)

18/137


buffer cofiles (transportn soubory dc) data (transportn soubory datov) etc log sapnames tmp put [DIR_PUT] (adres pro shadow systm pi upgrade) /sapmnt exe (SAP kernel, programy jako napr BR*Tools, tp.exe, R3trans.exe ad) [DIR_BINARY] [DIR_EXECUTABLE] [DIR_GEN_ROOT] [DIR_GRAPH_EXE] [DIR_GRAPH_LIB] [DIR_LIBRARY] [DIR_RSYN] global (protokoly map batch input) [DIR_CT_LOGGING] [DIR_GLOBAL] profile (profily instance) [DIR_PROFILE] [DIR_SETUPS] Pozn.: tablespace sapdata, archivn redology, zrcadlen redology a sapbackup mohou bt nakonfigurovna jinak. /oracle 920_64 [DIR_ORAHOME] bin (binrn soubory jako oracle, sqlplus, exp, imp) network (listener.ora, tnsnames.ora) dbs (init.ora profile pro Oracle, init.sap profile pro BR*Tools) mirrlogA (redology, zrcadlo sady a) mirrlogB (redology, zrcadlo sady b) oraarch origlogA (redology, originl sady a) cntrl origlogB (redology, originl sady b) saparch (archivn redo logy) cntrl sapbackup (detailn logy z kontrol DB a zlohovn, back.log BRBACKUP sumrn log, arch.log BRARCHIVE sumrn log) sapcheck (pracovn adres pro kontrolovn DB, logy BR*tools) sapdata1 (datafiles DB, stejn a do sapdataN, zde konkrtn pouze jeden) sapreorg (pracovn adres pro reorganizaci DB) saptrace (logy, pi defragmentaci, ora_.trc) background (ALRT.log DLEIT, trace soubory Oracle proces) usertrace (trace soubory uivatelskch proces Oracle) client stage (adrese pro instalaci Oracle a patche, jmna adres dle sla release) 9207 920_64

2.2.ZKLADN OPERACEZklady sprvy aplikanho serveru SAP. SAP Library: Computing Center Management System (BC-CCM) [SAP BC]. System Administration Assistant (BC-RRR) [SAP BC]. SAP NetWeaver Tecnical Operations Manual [SAP NW2004]. Solution Life Cycle Management [SAP NW2004]. System Management v Solution Life Cycle Management [SAP NW2004].

Literatura: [Hagerman 2004], [Missbach 2004], [SAP Labs 2002].

2.2.1.OBECN POZNMKY K PIHLEN DO SYSTMUVdy je nutn pihlsit se jako domnov uivatel adm nebo uivatel UNIXu adm k pslun instanci SAPu. V UNIXU se navc pedtm mus spustit listener (kapitola 3.2.5) jak ora. Je teba si uvdomit, e pi restartu aplikanho serveru se ztrat data z vyrovnvac pamti a chvli potrv, ne se vyuije vyrovnvac pam v pln me.

19/137


2.2.2.STARTRun: MMC snapin R/362: Ikona Sap System Management > spustit a kontrolovat, zda procesy jsou v reimu wait. Pkaz startsap: V UNIXu mus bt ped startem DB nastartovn listener pkazem lsnrctl start pod uivatele ora. 63 startsap name= nr= SAPDIAHOST= (MS). startsap [R3]|[J2EE] [] | [DB] [] | []64 (UNIX). Parametr J2EE stejn jako R3 spust ABAP i JAVA server, pokud jsou aoba dva stacky v jednom systmu. startdb (UNIX start databze na db hostu). sapcontrol -host -nr -function Start (od kernelu 7.00). O prbhu operace jsou logy (viz. poznmka 69) v UNIXu uloeny v domovskm adresi uivatele adm. J2EE server meme restartovat i vypnou v transakci SMICM v menu Administrace. SDM server: /usr/sap///SDM/program/startSDM.sh nebo startSDM.bat ve Windows. Ale nejdleitjm nstrojem pro sprvu clusteru je jcmon.

2.2.3.STOPRun: MMC snapin R/3: Ikona Sap System Management. Pkaz stopsap: 65 stopsap name= nr= SAPDIAHOST= (MS). stopsap [R3]|[J2EE] [] | [DB] [] | [] (UNIX). Parametr J2EE stejn jako R3 zastav ABAP i JAVA server, pokud jsou aoba dva stacky v jednom systmu. stopdb (UNIX start databze na db hostu). sapcontrol -host -nr -function Stop (od kernelu 7.00). O prbhu operace jsou logy (viz. poznmka 69) v UNIXu uloeny v domovskm adresi uivatele adm. J2EE server meme restartovat i vypnou v nstroji jcmon nebo v transakci SMICM v menu Administrace. Restart se provede nap. v jcmon takto: 10 - 19. SDM server: /usr/sap///SDM/program/StopServer.sh nebo StopServer.bat ve Windows. POZOR! Ped vypnutm aplikanho serveru zkontrolovat, zda nen nikdo pihlen, zde nen njak aktivn job i neb njak extern aplikace66 pipojen k serveru R/3. Pro ppad neptomnost sprvce BC meme v klientech 000 zaloit et pro uivatele (aby na produktivnm systmu neblokoval licenci), kter bude mt oprvnn pouze pro transakce AL08, SM50, SM51 a SM37, aby mohl ped vypnutm systm zkontrolovat.62

SAP Library: SAP NetWeaver Components - Computing Center Management System (BC-CCM) Computing Center Management System (BC-CCM) - Monitoring in the CCMS - Microsoft Management Console: Windows [SAP NW2004]. 63 Mono pipravit dvkov pkazy nap. se jmnem r3start (ploha). 64 Nap. . Nap. v UNIXu (bash): startsap R3 a obdobn zastaven stoptsap R3 , kde nap. v bash shellu je uveden v kapitole 5.1. 65 Mono pipravit dvkov pkazy nap. se jmnem r3stop (ploha). 66 Nap. zkontrolovat v AL08 uivatele nebo v SM37 aktivn joby. Podrobnosti by mla popisovat provozn pruka.

20/137


2.2.4.START A STOP R/3 V PROSTED MSCSSAP note: 145666.

2.2.5.TEST BHU SERVERU A DATABZOVHO SPOJENPomoc sapinfo.exe i rfcping z RFCSDK lze testovat bh dostupnost systmu. Nap. rfcping ashost= sysnr= [ping_cnt=] nebo sapinfo ashost= sysnr=. Viz SAP note 34998. Navc meme testovat bh jednotlivch instanc dotazem na message server pkazem lgtst[.exe]. V ploze jsou uveden pklady. Databzov spojen meme otestovat takto: tp getdbinfo , tp connect nebo R3trans -d.

2.2.6.ZAMKNUT A ODEMKNUT UIVATELV transakci SU10 hromadn zamkneme. Pozor na zamen systmovch a vlastnch t. Dal monost: tp locksys pf= a tp unlocksys pf=67. Zstanou nezameni uivatel sap* a DDIC68. Viz t v kapitole 7.

2.3.ZKLADN KONTROLYTransakce SSAA. Ne uveden popis minimln kadodenn kontroly je mono vloit do provozn pruky a poppad tam doplnit: Tyto zkladn kontroly doporuuji provdt kad den rno v SAP GUI, nebo kdy si uivatel stuj, e je SAP pomal nebo divn b (zvl. transakce SM50 a ST06). Pro pouit centrlnho monitoringu CCMS uvdm MTE, kter nm pomou nahradit run kontrolu. 1) Transakce SM21. Zkontrolujeme systmov log od pedchozho dne. Mono vynechat, pokud pouijeme MMC. Sledujeme vskyt chybovch hlen (krtk dumpy, rollback, odpojen uivatel, chybn hlen od databze, chybn updatovac zznamy a pod.). MTE: R3Syslog a dal. 2) Transakce DB02. Kontrola, zda nechyb indexy a velikost prostoru tlatkem Space Statistics. Pozornost vyaduje nhl velk zmenen dostupnho prostoru. MTE: CCMS_DB_space_mscl, CCMS_DB_health_mscl, CCMS_DB_perf_mscl, CCMS_DB_dd_mscl. 3) Transakce DB12 tet tlatko od shora, v CZ je neoznaen. Kontrola zloh a msta na disku urenho pro archivn. Po zaplnn se zastav DB a ek, ne se zde uvoln msto z adrese /oracle//saparch/. Potom se mus redology zazlohovat a pesunout nkam jinam. Nemazat! Jsou dleit v ppad obnovy DB. Zrove tm otestujeme, zda b proces saposcol. Pokud neb, tak se nm v transakci DB12 nic neuke a meme pout nap. transakci ST06. MTE: CCMS_DB_backup_mscl. 4) Transakce DB14. Podvme se na vechny logy tlatkem Ve. Sledujeme barevn oznaen dky logu, do kterch se podvme. 5) Transakce SM37. Zkontrolujeme vsledky job vech uivatel od pedchozho dne. Sledujeme vskyt chybovch hlen.

67 68

O profilu v kapitole 5.1. Zkouel jsem v minisapu - 4.6d fungovalo po restartu (Viz SAP note 12946).

21/137


MTE: R3BatchProgramErrors, R3BPServerSpecAbortedJobs, R3BPSystemWideFreeBPWP. 6) Transakce SM50 nebo pro vce instanc SM66 i RZ03 v menu Monitoring. Prohldneme stav pracovnch proces, zda nejsou vskyty chyb nebo nejsou obsazeny vechny procesy BTC. Mono vynechat, pokud pouijeme MMC. Sledujeme vskyt chybovch hlen a podivnch stav proces. Bn stavy procesu jsou: ek, B nebo je zastaven a ek na CPIC. Pokud u se nedostaneme z frontendu, pak pouijeme dpmon. MTE: R3Syslog 7) Transakce RZ20. Pokud nemme definovn vlastn monitor, pak vybereme skupinu Skupiny monitor CCMS SAP CCMS Technical Expert Monitors All Monitoring Contexts. Prohldneme oteven alerty. Je jich vtinou hodn, zvlt zznamy vkonovch piek. Doporuuji setdit podle polka Krtk text. Pouze pro zkuenj (nkter alerty se vyskytuj trvale), ale ukazuje i problmy zobraziteln v pedchozch transakc. Sledujeme vskyt chybovch hlen. Zvlt hlen udvajc kd chyby error, krtk dumpy a jin podezel hlen. 8) Transakce ST22, pokud transakce RZ20 nebo SM21 ukazuje vskyt krtkho dumpu. Zkontrolujeme vskyt krtkch dump, poppad se zeptme sprvce aplikace, jestli o tom m povdomost. MTE: R3AbapShortdumps, R3DialogProgramErrors, R3BPSystemWideFreeBPWP, R3BPServerSpecAbortedJobs, R3BatchProgramErrors, R3AbapErrorInUpdate, R3ErrorsInWpSPO, R3AbapSqlError 9) Transakce SM13, pokud transakce RZ20 nebo SM21 ukazuje vskyt chybnho updatovacho zznamu. Zkontrolujeme chybn updatovac zznamy nap. od roku 2002. Pokud se vyskytne, zavolme uivateli (ml by dostat zprvu od systmu) a sprvci aplikace a zjiujeme, co s tm udlali a vyeme to bu opakovnm update nebo jestlie uivatel ve sv nevdomosti provedl operaci run pak updatovac zznam smaeme. MTE: R3AbapErrorInUpdate. 10)Transakce AL08. Zjistme pihlen uivatele. Hlavn pokud tam nen nkdo dlouho pihlen. CCMS ns upozorn na bezpenostn problmy: MTE R3SyslogSecurity, SecurityUserMasterRecords. 11)Transakce SM35. Zkontrolujeme na produktivnm systmu dvkov vstupy (batch inputy). Vmme se vskytu chybovch hlen.

2.4.RZN PROBLMY2.4.1.OBECNSAP Library:SAP NetWeaver Problem Analysis Guide (PAG) v Solution Life Cycle Management by Key Capability [NW2004s].

Dleit informace v ppad problm jsou v developer tracefiles v [DIR_HOME], dle v systmovm logu a v log souborech databze. Je mono je prohlet i v MMC. Obecn o analze problmu pojednv SAP note 192194. Texty ke vem chybovm zprvm jsou v tabulce T100 (prohldnout lze pomoc SE16). Je mono zkusit SAP NetWeaver Problem Analysis Guide (PAG).

2.4.2.NEMEME SE PIHLSIT DO SYSTMUPokud se nememe pihlsit do systmu, na rovni operanho systmu zkontrolujeme zda b procesy SAP systmu i databze nap. V UNIXu a u Oracle pkazy ps -ef | grep sap22/137


nebo ps -ef | grep ora a podobn. Pokud oboj b, zkusme ne popsan monitory. Pokud ne, zkusme zjistit pinu pro neb server i databze69 a nastartujeme.

2.4.3.MONITORYNkdy jsou uiten monitory sputn z pkazov dky. Ukzka voln70: dpmon pf= msmon pf= gwmon pf= icmon pf= ensmon pf= #Test Program for EM-Layer (extended memory) emmon pf= #Monitor Program for ES-Layer (Extended Memory Segments) esmon pf=

2.4.4.NESTARTUJE APLIKAN SERVE

Documents

Sapr3 Bc Guide