Live Cache Administration SAP
January 15, 2017 | Author: Chandramouli Konduru | Category: N/A
Short Description
Download Live Cache Administration SAP...
Description
BC555 liveCache Administration
liveCache Administration
R/3 R/3 Release Release 4.6C 4.6C SAP AG 1999
R/3 Release 4.6 C Material Number 5004 0750
50040750 50040750
Copyright
Copyright 2002 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. All rights reserved.
SAP AG 2002
Trademarks: Some
software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft
, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.
IBM
®
®
, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.
ORACLE
®
is a registered trademark of ORACLE Corporation.
INFORMIX
-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.
UNIX
®
®
, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
HTML,
DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
JAVA
®
is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT
®
is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP,
SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.
6$3%DVLV$GPLQLVWUDWLRQ7UDLQLQJ ([SHUW&RPSHWHQFH
&RUH&RPSHWHQFH
))% $%
3 days Database Administration Oracle
&' ("$
2 days R/3-Technical Implementation and Operation Management
)+*, ,
Technical Core Competence
)#" - %
))%/..
!#" $%
3 days Advanced R/3 System Administration
5 days
3 days
Workplace
3 days
Workload Analysis
Software Logistics
j @=`=_e/:7CII4 ))" %$=
!#"/. %
3 days
TCC Workplace
WYX I3 MEZ797; M=C8H[012 3/0 1\]6835N 3E98MI3^ 3E2 4E; 1T984 AD0 @E_[`ba#; 9=:T1=G4Uc X ?Ed2 CIM=H 3 AD0 @E_[eba#; 9=:T1=G4Uc X ?EOEPJ(fA AD0 @E_hgia#; 9=:T1=G4Uc Xkj O!OTlnmUO382 o83E2 AD0 @E_[prq a; 97:817G4sc X ?7t c u vKw8?7f AKe AD0 @=xI`ytcDu vR?8d2 C=M8H 3 AD0 @=x8_ztcDu vR?7u 98{ 12\]; S AD0 @=xIeytcDu vR?8OPJ(fDA AD0 @=pI`yu A j POg=`I` AD0 @=|I`yu A j ? @I|=` W}W AD0 @=~I`ba!1T2YVI6EH C=MI3n
DTI
5 days Database Administration Informix ))%/. % 2 days Database Administration SAP DB ))% -$ 3 days Database Administration MS SQL Server ))% -% 3 days Database Administration DB2/400 ))% "$ 5 days Database Administration DB2/390 ))% "% 3 days Database Administration DB2 UDB
))% %%
0122 354768198:; 9= ? @BADC54E; 4 F 9818G/H 3I:7 ÑÒÓ : Ô
Õ Ö × Ô \ £ ¡ ¬ ¡ ² ¯ ° ° É £ Ê ¡ ¬ Ë ¯ ¡ ¢ ¡ ¦ ± ± ¡ ¤ L ` a b c d ` e f g e h i j Z K k c g c ¥ ¤ £ l e ` m nb f h b o a ` fp qr ¥ § ¡ ¦ ¥ ® ¯ ° ¥ ¬ ¥ ¡ ¡ ©¨ ¥ ¥ Ì ª ¡ ¢ ¥ ª « ¢ ¦ ¡ 2 days R /3-Techni cal I mp lementa tion and O pe rati on M an agem ent
Techni cal C ore Com petence
3 days D atabase Administrat ion O RAC LE
3 days Advanced R /3 System Admi nis tratio n
5 days
2 days D atabase Administrat ion SA P DB 3 days D atabase Administrat ion M S SQ L S erver
3 days
Soft wa re L ogis tics
3 days D atabase Administrat ion D B2 UD B
(SD)
2 d a ys
( PP)
2 da y s
( C O)
2 da ys
Techn i cal C or e Co mp ete nce Ve rsi o ns (SD) 2 d a ys
B C3 10 W in do ws NT / Oracl e BC3 14 Wi n dow s NT MS SQL Se rv er BC3 17 (W ind ow s N T / U N IX ) / D B2 (SD) 2 d a ys BC3 60 UNI X / Ora cle BC3 62 UNI X / SAP DB
SAP AG 1999 fi lena me (autho2r)da / 2y s ( SD)
( SD)
1 day
( SD)
1 day
( SD)
SAP AG
1 day
( PP)
2 da y s
( SD/ PP )
2 da y s
(PP/ CO) 2 da ys
; > < =%#) .?@ A! #%$&# BC *DFEG#4)5 #70
> HI J
( SD/ PP ) 2 da ys
( SD)
2 da ys
KTM mySAP.com for Techn. Imp l., IT Cons. ,Sys. I ntegration UH / 7
E>ÚÛ(ÝÜF G5 %&*Þ45 ß%# 8 3/# - D
> à Ô
áâ Ô × ã7 J
E>ÚÛ(ä;6):! å/Ïæ6/.+-43çE*#4)Íß'5 -/#
> Ñ Ö è éêë
E>ÚÛ(ä;6):! å/Ïæ6/.+-43Úì! #)Í.
> Ñ ê@í
E>ÚÛ(
8 G%04,'! .5 &ÎEG#) ß>5 -7#I0
2'#/6 îAE'ÚÛ(ÎE ,'==% G)1.
> ã7 Ó è Ô á Õ Ö × Ô
> >Õí Ù Ó Ö
' HI Ô ØI ÙÖ Ò "! #%$'& # (*)+ $*,%-/.10
2'#%-434'5 -764! 8 #4)1.5 95 -/67.5 */0 :
SAP AG 1999
© SAP AG
BC555
2-1
&RXUVH3UHUHTXLVLWHV7DUJHW*URXS'XUDWLRQ
l &RXUVH3UHUHTXLVLWHV
%&RUVLPLODU6$3V\VWHPDGPLQLVWUDWLRQFRXUVH DOWHUQDWLYHO\'DWDEDVH$GPLQLVWUDWLRQFRXUVHOLNH%& %&«
l 5HOHDVHGHSHQGHQF\
$325HOHDVH$DQGOLYH&DFKHUHOHDVH
l 7DUJHW*URXS
3URMHFWWHDPPHPEHUVUHVSRQVLEOHIRUWKHLQVWDOODWLRQDQG PDLQWHQDQFHRIDOLYH&DFKH
l 'XUDWLRQ GD\V
SAP AG 1999
© SAP AG
BC555
3-1
&RXUVH*RDO
7KLVFRXUVHZLOOHQDEOH\RXWR
l 'HILQH$32V\VWHPUHTXLUHPHQWV
l ,GHQWLI\WKHVSHFLILFOLYH&DFKH FRQILJXUDWLRQLQWKH6$3HQYLURQPHQW l 3HUIRUPOLYH&DFKHPRQLWRULQJDQG PDLQWHQDQFH
l /LVWDQGSHUIRUPZRUNZLWK'%0*8,DQG 6$3DGPLQLVWUDWLRQWRROV l 8QGHUVWDQGEDFNXSDQGUHFRYHU\ FRQFHSWVRIOLYH&DFKHLQWKH$32 V\VWHP
SAP AG 1999
© SAP AG
BC555
3-2
&RXUVH&RQWHQWV
&RXUVH2YHUYLHZ
Unit 1
OLYH&DFKH&RQFHSWV
Unit 4
OLYH&DFKH0RQLWRULQJ
Unit 2
OLYH&DFKH$UFKLWHFWXUH DQG5HTXLUHPHQWV
Unit 5
OLYH&DFKH%DFNXSDQG 5HVWRUH7HFKQLTXHV
OLYH&DFKH $GPLQLVWUDWLRQ
Unit 3
Unit 6
OLYH&DFKH%DFNXSDQG 5HVWRUHIRU$32
&RQFOXVLRQ
SAP AG 1999
© SAP AG
BC555
3-3
OLYH&DFKH&RQFHSWV
OLYH&DFKH&RQFHSWV OLYH&DFKH$UFKLWHFWXUH DQG5HTXLUHPHQWV OLYH&DFKH$GPLQLVWUDWLRQ OLYH&DFKH0RQLWRULQJ OLYH&DFKH%DFNXSDQG 5HVWRUH7HFKQLTXHV OLYH&DFKH%DFNXSDQG 5HVWRUHIRU$32 SAP AG 1999
© SAP AG
BC555
4-1
OLYH&DFKH&RQFHSWV
$WWKHFRQFOXVLRQRIWKLVXQLW \RXZLOOEHDEOHWR l 'HVFULEHWKHSXUSRVHRIOLYH&DFKH
l 'HVFULEHWKHDUFKLWHFWXUHRI6$3V\VWHPV
XVLQJOLYH&DFKHWHFKQRORJ\
l 'HVFULEHKRZOLYH&DFKHLQWHUIDFHVZLWK
6$3EDVLVWHFKQRORJ\
l ([SODLQZKLFKGDWDDUHVWRUHGLQOLYH&DFKH
DQGKRZWKH\JHWWKHUH
SAP AG 1999
© SAP AG
BC555
4-2
$SSOLFDWLRQDQG%DVLV&RPSRQHQWVRI6$3$32 6XSSO\&KDLQ $YDLODEOH 'HPDQG 7R 3ODQQLQJ &RFNSLW 3URPLVH XVHV%:
9HQGRU 0DQDJHG ,QYHQWRU\
6XSSO\ 1HWZRUN 3ODQQLQJ
&DSDEOH 3URGXFWLRQ 7R 3ODQQLQJ 0DWFK 'HWDLOHG 6FKHGXOLQJ
'DWDEDVH ZLWK%:WHFKQLTXHV DYDLODEOH
OLYH&DFKH
$32 2SWLPL]HUV
4XHXHG5)& T5)& 6\QFKURQRXV5)& V5)& %$3, Model Generator, mapping, connectivity
5 53,
6$3 %:
/HJDF\ 2/73
1RQ6$3 2/73
1RQ6$3 2/73
SAP AG 1999
n
liveCache is a component of the SAP New Dimension Product APO (Advanced Planner and Optimizer).
n
As of Release 4.5A, the SAP system can connect to multiple databases. The APO system utilizes this functionality and connects to two database systems: é the liveCache system which uses object-oriented and memory-based computing
é the APO relational database management system (RDBMS), which contains persistent data and is comparable to the RDBMS of a standard SAP system. It provides Business Information Warehouse (BW) functionality that is mainly used by the application module Demand Planning.
n
APO modules SNP, CTM and PP/DS use additional standalone programs called optimizers which also communicate with the liveCache. These programs provide sophisticated optimization algorithms.
n
SAP R/3 uses the APO-CIF interface to handle data transfer to APO. APO-CIF is part of R/3 Plug In, a collection of interfaces to the different components of the mySAP.com system landscape. The APO system and APO-CIF communicate through qRFC (asynchronous RFC call with secure transfer (tRFC) and guaranteed sequence as defined in the OUT-queue) and sRFC (synchronous RFC, used by ATP) calls with SAP systems. This allows for a seamless integration of APO functions into the customer’s SAP system landscape.
n
APO can also communicate with legacy systems that may include Online Transaction Processing (OLTP) systems and non-OLTP systems (for example, batch processing systems).
© SAP AG
BC555
4-3
OLYH&DFKH7HFKQRORJ\ OLYH&DFKH7HFKQRORJ\ OLYH&DFKH6HUYHU
$SSOLFDWLRQ6HUYHU
$%$3 $%$3
&
!PV
µV
5'%06 5'%06 OLYH&DFKH OLYH&DFKH
'DWDEDVH6HUYHU
l OLYH&DFKHLVDQREMHFWRULHQWHGGDWDEDVHPDQDJHPHQWV\VWHP GHYHORSHGE\6$3WKDWUHVLGHVLQDYHU\ODUJHPHPRU\
l 2SWLPL]HG&SURJUDPVUXQRQWKHOLYH&DFKHVHUYHUDQGKDYH DFFHVVWROLYH&DFKHGDWD l 7KHPDLQREMHFWLYHLVWRRSWLPL]HSHUIRUPDQFH
OLYH&DFKHUHVLGHVLQPDLQPHPRU\DQGWKHUHIRUHDYRLGVGLVN,2
2EMHFWRULHQWDWLRQHQDEOHVHIILFLHQWSURJUDPPLQJWHFKQLTXHV
OLYH&DFKH &DFKHSURFHVVHVSURYLGHVVFDODELOLW\
SAP AG 1999
n
In a standard SAP system, typical database request times are above 1 ms. For data intensive applications, a new technology is required in order to achieve better response times. liveCache has been developed to reduce typical database request times to below 10 µs. Key factors in achieving these response times are: é Accesses to liveCache data usually do not involve any disk I/O
é The processes accessing the data are optimized C++ routines that run in the process context of the liveCache on the liveCache server é Object orientation enables the use of efficient and versatile programming techniques
n
APO is the first product to use liveCache technology.
n
In principle, multiple liveCache instances can be used in parallel to increase performance for various applications. APO does not yet use this possibility. Currently two logical connections to liveCache are used by APO. Both connections point to the same physical liveCache. é Logical connection LCA is used by all APO application modules but GATP. é Logical connection LDA is used by GATP only.
© SAP AG
BC555
4-4
&RPPDQGDQDO\]HU
1DWLYH64/
1DWLYH64/
2SWLPL]HUV613&70DQG33'6
'DWDEDVHLQWHUIDFHRI6$3NHUQHO
$FFHVVLQJOLYH&DFKH
O L Y H & D F K H
64/ FODVV 64/ 64/EDVLV % WUHHV
)UDPHZRUN IRUPHWKRG HPEHGGLQJ
206
206EDVLV
SDJHFKDLQV
7\SHOLEUDU\ &20REMHFWV '//
5HJLVWU\
'DWD&DFKH
64/GDWD 2EMHFWGDWD
64//RJ
SAP AG 1999
n
ABAP Programs and the APO optimizers use native SQL for communicating through the standard SAP database interface to liveCache. liveCache has an SQL interface that is used to communicate with the SAP instances. With native SQL, ABAP programs call stored procedures in the liveCache that point to Component Object Model (COM) routines written in C++. An SQL class provides access from the COM routine to the SQL data.
n
In an SQL trace of an APO application, the statements for calls to COM routines contain the string DBPROC SAPR3."SAPAPO_.
n
The COM routines are part of a dynamic link library that runs in the process context of the liveCache instance. In the Windows NT implementation of liveCache, COM routines and their interface are registered in the NT Registry. For the Unix implementation, a registry file is provided by liveCache. A persistent C++ class provides the COM routines with access to the corresponding Object Management System (OMS) data that is stored in the liveCache.
n
All liveCache data are stored in the caches as well as, if necessary, on disk in 8 Kbyte blocks called pages.
n
liveCache stores the OMS objects in page chains, the pages in the chain linked by pointers. SQL table data are stored in the form of B* trees. SQL and OMS data reside together in the data cache of the liveCache. Each page in liveCache is marked as an SQL page or an OMS page.
© SAP AG
BC555
4-5
OLYH&DFKH3URJUDPPLQJ&RQFHSWV l 7UDQVDFWLRQ&RQFHSW /RFNLQJ
5ROOEDFN
&RPPLW
OLYH&DFKH OLYH&DFKH
5HDGFRQVLVWHQF\
l OLYH&DFKHVXSSRUWVWKHIROORZLQJREMHFWRULHQWHGFRQFHSWV (QFDSVXODWLRQ
8QLTXHREMHFWLGHQWLW\
0HWKRGVVXFKDVLQVWDQFHDQGFODVVOHYHO
l 7KHIROORZLQJFRQFHSWVDUHLPSOHPHQWHGLQWKH& DSSOLFDWLRQOD\HU $EVWUDFWFODVVHV
,QKHULWDQFH
3RO\PRUSKLVP
$JJUHJDWLRQ
SAP AG 1999
n
The transaction concept common to relational database systems is also available for liveCache objects. liveCache supports read-consistency, that is, the data returned by liveCache represent the state of the data at the time, when the transaction that issued the read operation was started, even if some of these data have changed during retrieval by liveCache.
n
The liveCache concept incorporates both SQL data access and object orientation. The COM routines have direct access to the objects stored in the liveCache and can manipulate them. This manipulation includes creation and deletion of objects in the liveCache .
n
On the liveCache level, the following object-oriented features are implemented:
é Encapsulation: keeping together data structures and the methods which act on them
é Unique object identity: each object has its own set of variables belonging to its class é Methods: procedures or routines associated with one or more classes
n
The following object-oriented features can be implemented on the C++ routine level:
é Abstract classes: parent classes from which sub-classes may be derived (cannot be instantiated) é Inheritance: derived subclasses inherit instance variables and methods of the superclass é Polymorphism: variables may refer at run-time to objects of different classes
é Aggregation: a technique for building a new object from one or more existing objects
© SAP AG
BC555
4-6
$32'DWDLQOLYH&DFKH $32
OLYH&DFKH6HUYHU
$SS6HUYHU 6HUYHU $SS
)URQWHQG
$SSOLFDWLRQ OLYH&DFKH OLYH&DFKH 'DWDPXVWEH FRQVLVWHQW
0DVWHUGDWD
7UDQVDFWLRQ GDWD
OLYH&DFKH GHYVSDFHV
$32'DWDEDVH SAP AG 1999
n
Some APO data only exist in the APO DB, others only in liveCache, some data are stored in APO database and liveCache. Data in APO DB and liveCache have to be in a consistent state. It is not acceptable, if redundant data are only present in liveCache and not in APO DB or vice versa.
é The APO DB contains master data like resources, materials, PPMs (Production Process Models), setup matrices, location definitions, transportation lanes, planning books and customizing data. é The APO DB also contains some transaction data including texts
é As of APO release 3.0A, liveCache contains time series of current planning data from Demand Planning.
é liveCache stores master data in compressed form (information like material texts is not required by COM routines). Transaction data (e. g. sales order, confirmed shipments, purchase orders including items and schedule lines and stock) is stored only in liveCache to improve performance. For planned and production orders, this is almost all data which is generated during BOM explosion and routing (PPM and PPU, Production Planning Unit). é SQL tables /SAPAPO/ORDKEY and /SAPAPO/ORDMAP are stored in liveCache as well.
© SAP AG
BC555
4-7
/RDGLQJ'DWDLQWROLYH&DFKH $32
OLYH&DFKH6HUYHU
$SS6HUYHU 6HUYHU $SS
)URQWHQG
,QLWLDOL]H OLYH&DFKH
5HORDGPDVWHUDQG WUDQVDFWLRQGDWDIURP$32 $SSOLFDWLRQ '%WROLYH&DFKH 5HORDG '3GDWD
OLYH&DFKH OLYH&DFKH
0DVWHUGDWD
7UDQVDFWLRQDO GDWD 'HOHWHGHUHIHUHQFHG GDWDLQ$32'%
$32'DWDEDVH
OLYH&DFKH GHYVSDFHV
SAP AG 1999
n
liveCache can be re-initialized. As a result, all data in liveCache are deleted. This is, e.g., required if a new version of COM routines with a modified interface to the objects in liveCache is installed. After such an initialization, report /SAPAPO/DELETE_LC_ANCHORS synchronizes APO database and liveCache. é SQL tables /SAPAPO/ORDKEY and /SAPAPO/ORDMAP are re-created in liveCache é Data in the APO database is deleted, which refers to orders stored in the liveCache
é All required data must be transferred from APO database into liveCache. These include resources (biggest part of data, can be loaded in parallel), setup matrices and product-location combinations. é You can use the Copy Management of Demand Planning to copy one or more key figures from planning areas in liveCache into a pre-defined backup info cube. If you have backed up Demand Planning data into such a backup infocube, reload these data into liveCache.
© SAP AG
BC555
4-8
OLYH&DFKH$GPLQLVWUDWLRQ '%0*8,DQG/&
SAP AG 1999
n
liveCache, like the standard SAP RDBMS, can be administered from within the SAP system. You can use the administration tools DBMGUI, dbmcli and the SAP transaction LC10 to monitor, configure and administer liveCache. As the basic functionalities of an SAP system are still available without liveCache, LC10 allows for additional actions like starting and stopping the liveCache.
n
DBMGUI is a graphical user interface to the liveCache management client interface dbmcli. Both DBMGUI and dbmcli can be used for all liveCache administration tasks including backup and restore.
n
From the initial screen of transaction LC10, you can access the:
é “liveCache administration” menu (for liveCache administration) é “liveCache configuration” menu (for liveCache administration)
é “liveCache console” menu (for liveCache monitoring using calls to x_cons) é “liveCache monitor” (for statistics about calls to database procedures)
é “liveCache performance” menu (for monitoring the performance of the liveCache)
© SAP AG
BC555
4-9
OLYH&DFKH&RQFHSWV 8QLW6XPPDU\
View more...
Comments
