最权威经典的SAP系统BASIS培训教材--china-1详细资料.ppt

1：直接登录消息服务器 2：登录至Message Server，通过Loading Balance，找到相应的Dispatcher. 主server 附server * System: 一个系统是由一组例程组成 Instance(例程) 由两种例程组成：中央例程(Central Instance)与附增例程(Additional Instance)。 例程是由一组服务或进程(Process)组成。 Central instance: Instance: Dialog (D): each dispatcher needs at least 2 dialog work processes (not shown above) Spool (S): at least 1 per R/3 System (more than 1 per dispatcher allowed) Update (V): at least 1 per R/3 System (more than 1 per dispatcher allowed) Background (B): at least 2 per R/3 System (more than 1 per dispatcher allowed) Enqueue (E): exactly 1 per R/3 System (only 1 E work process is required and allowed) * * startsap has the following options: startsap r3: Checks if the database is running; if it is, only the instance is started startsap db: Starts only the database startsap all: Default entry; starts both the database and the R/3 instance Script startsap calls program SAPSTART. Program SAPSTART reads the START PROFILE and starts the R/3 components and/or services listed in /usr/sap/SID/SYS/profile/START_instance_hostname. On a central instance, SAPSTART starts the message server, dispatcher, collector, and the sender. On a dialog instance, only the sender and the dispatcher are started. The collector and sender are used to implement the central R/3 System log. The dispatcher forks and creates child processes: The work processes (dialog, background, spool, update, . . .) are created according to the information in the profiles /usr/sap/SID/SYS/profile/SID_instance_hostname and /usr/sap/SID/SYS/profile/DEFAULT.PFL. The gateway reader. This does not depend on the profiles, and it is always started. All the work processes except the gateway reader connect to the database. The process IDs of the various R/3 processes clearly show the R/3 startup procedure. sapstart creates the dispatcher, collector, and sender. saposcol is started directly from the script startsap. The UNIX init process has the process ID 1. Dw进程都是dispatcher fork出来的子进程，不管是d,b,