【文章內(nèi)容簡(jiǎn)介】 urrent Performance 350Recording Performance Over Time 351Web Server: Troubleshooting 352Troubleshooting: Page Not Displayed 353Web Server: Tuning Parameters 354Connections and Timeout 355Internet Connection Types 356Choosing the Best Connection 357Hardware Resources: Web Load Balancing 358ITS Monitoring 359Three Ways of Monitoring the ITS 360Logs and Troubleshooting 361ITS Logs: Error Analysis 362ITS Trace Example 363Troubleshooting: Wgate = AGate 364Troubleshooting: AGate = SAP System 365Dragamp。Relate Server Logs 366Bottleneck Analysis 367Available Tools 368AGate Sessions 369AGate Threads 370Internal Scalability 371ITS Administration Instance (1) 372ITS Administration Instance (2) 373Dragamp。Relate Servlet 374Workplace Server Monitoring: CCMS 375Monitoring the SAP System Landscape 376CCMS Alert Monitor 377Working with the Alert Monitor 378Defining Monitors 379RuleBased MTE Selection 380CCMS Monitor for Workplace Systems 381Including SAP Systems with Release 382Configuring a Standalone Gateway on AGate 383Including a Standalone Gateway in Central CCMS 384ALE Monitoring and Central CCMS 385ALE: IDoc Administrator 386Workplace Server Error Analysis 387Roles and URL Generation 388Using Authorization Groups 389Transaction Analysis 390Workplace Server Response Time 391SAP Component System Transaction Analysis 392Unit Summary 393Unit Actions 394Monitoring and Troubleshooting: Exercises 395Monitoring and Troubleshooting: Solutions 396Dragamp。Relate 400Dragamp。Relate: Unit Objectives 401Course Overview Diagram (8) 402Supported Scenarios 403Dragamp。Relate Architecture 404Prerequisites 405Maintenance for BOR Objects 406Dragamp。Relate: Unit Summary 407Section: ReadytoRun 408ReadytoRun R/3 409ReadytoRun R/3 410What is ReadytoRun R/3? 411ReadytoRun R/3 412Overview of ReadytoRun R/3 Installation 413ReadyToRun R/3 Configuration Assistant (1) 414ReadyToRun R/3 Configuration Assistant (2) 415ReadytoRun R/3 Configuration Assistant (3) 416ReadytoRun R/3 Configuration Assistant (4) 417ReadytoRun R/3 Configuration Assistant (5) 418ReadytoRun R/3 419ReadytoRun R/3: Network under NT 420The ReadytoRun R/3 Domain Concept for NT 421Preconfigured Basis (1) 422Preconfigured Basis (2) 423ReadytoRun R/3 424Administration and Service Concept 425System Administration Assistant (1) 426System Administration Assistant (2) 427Understanding the Task List 428Administration Concept 429Trouble Shooting Roadmap 430Using the RRR Configuration Reference 431ReadytoRun R/3 432Installation Overview 433Installation of RRR together with Windows NT? 434ReadytoRun R/3 Software Layers 435ReadytoRun R/3: Delivery Process (1) 436ReadytoRun R/3: Delivery Process (2) 437Planning RRR Installation Sequence 438Preparing RRR Installation 439RRR Installation Program Introduction Screen 440Build RRR Installation Image 441Possible RRR Installation Sources 442Start the Installation Process: Program RRRStart 443ReadytoRun R/3 444Handover Workshop Schedule 445ReadytoRun R/3 446ReadytoRun R/3: Information 447n The graphic shows the systems involved in a Workplace environment and the related data.n Every logical system (client in a system) must have a separate virtual ITS installation.n The objects that are most important for software logistics are:? Single roles: These roles are usually created in a development system (DEV) and transported through a quality assurance system (QAS) to a production system (PRD) using the SAP Transport System. Roles are clientdependent objects.? Customerspecific Internet development objects of a virtual ITS residing on either AGate or WGate, such as:173。 MIME files (sounds, graphics, …)173。 HTML template files173。 Language files (*.trc) To transport customerspecific Internet development objects, use the SAP tool SAP@Web Studio and the SAP Transport System.n The Workplace Server (WPS) may be integrated into one of the existing transport domains. Make sure the WPS does not receive any development (customizing) from other ponent systems.n To include the WPS into the transport domain of other systems from a nonconfigured Transport Management System (TMS), on the WPS call transaction STMS and choose Other configuration. Log on to the ponent system, call transaction STMS, choose System Overview, mark the WPS, choose SAP System 174。 Approve, and distribute the TMS configuration.n You need to exchange only a few objects between ponent systems and the WPS:? The definition of roles? The Central User Administration (CUA) ALE distribution model ? The CUA logical system namesn In most cases, WPS Customizing is not transported, as it contains URLs and server names. Transport of posite roles is possible.n Depending on the release level of the interacting SAP Systems, transports may be impossible for either of the following reasons:? The systems are logically different. For example, you cannot transport Customizing for a function that does not exist in the target system.? Some field or table definitions are different in the two systems.n The WPS is used for logon to all other systems, so it should be the most available server in your system landscape. You can use the WPS as the central transport domain controller. Within a transport domain, SAP Systems that share a mon transport directory form a transport group. You need not use just one transport directory. You can form a separate transport group for each set of development, quality assurance, and production systems. n The TMS supports transports between transport groups. After a change request has been released, the request is marked in the mon transport directory for import into the target system. If the source and target systems are in different transport groups, you must adjust the import queue of t