Summary
Solution Manager consists of both methodology and software.
SolMan is intended to be a central repository and user interface for Application Management personnel.
SolMan Java server apps complement tools previously available for ABAP R/3.
Solution Manager is abbreviated "SolMan" or "SOLMAN" — its Java instance name. SolMan adds tools for managing Java components used by SAP NetWeaver:
Solution Manager is the central part of End-to-End (E2E) SAP system scenarios to efficiently implement, operate, monitor, and support SAP solutions.
|
Solution Manager Extensions include the
SAP Solution Manager Adapter for SAP Quality Center by HP and Process Scheduling Adapter for SAP Solution Manager
The Sales Kit for SAP page contains demo scripts for IDES (DL1).
A CD recording the SAP Solution Manager info day 04/27/2006 in Brussels is available in sap.com/shop as Material number 50 079 668.
|
| The "content" offered by SolMan is part of the "RunSAP" methodology for End-to-End (E2E) Operations at
|
|
|
Version | Release | Features | End of Mainstream Maintenance |
---|---|---|---|
4.0 SP11-15 | July 2007 | optimized collaboration with SAP services. | Mar. 2011 |
3.2 SP09 | Sep. 2005 | added change req. mgmt. | Mar. 2009 |
3.1 was | June 2004 | added a service desk upgrade. | Dec. 2006 |
Per SAP Note 628901, Solution Manager software is free to licensed SAP customers. For an additional price, SAP Solution Manager Enterprise Edition add-on enhances Standard SolMan to provide collaboration for SAP Enterprise Support by SAP's Active Global Support (AGS) organization.
- Test Management enhancements include
- Definition of test sequences (successor/predecessor relationships) among test cases and test packages;
- different execution order within each test package;
- email notification at workflow status changes; and
- improved test management from digital signatures protecting progress in the workflow.
- The Traceability Management Package enhances management of documents and process structures by locking of documents for changes with display of signed documents with signatures and links among documents.
- Change Request Management enhancements include the ability to assign solution structure objects to change requests, which enables coordination of parallel development environments.
- Solution Documentation Assistant analyzes systems automatically to create a system usage report and core business process models.
- Process Structure Management Extensions include
Customer defined attributes at objects on tab development;
transaction and configuration including electronic signature;Lock of process substructures in Business Blueprint (only structure not the tabs).
- Management of custom development
For SAP Solution Manager to make full use of business process monitoring (BPM) and other features, the latest support packages need to be installed:
- SAP Basis Release 7.0
- Solution Manager Release 4.0 (ST 400). The installer is mounted as the SAP material numbers for 6 DVDs:
- 51032955 Installation IM_WINDOWS folder, sapinst.exe Centeral System install
- 51032956_1 Export (EXP1 & EXP2)
- 51032956_2 Export (EXP3 & EXP4)
- 51032958 Java
- 51033032 Kernel
- 51032923 MaxDB
- Technical Release ST-SER 700_2006_1
- Add-On Release ST-A/PI 01H_CRM500
Jon Reed notes that Solution Manager is "one of the few bridges between pre-NetWeaver SAP, NetWeaver SAP, and the eSOA and analytics era -- you don't have to be on the latest version of SAP to get access to this tool. You can use Solution Manager to manage your SAP upgrade, and then for performance management and optimization afterward. Solution Manager even contains a comprehensive change management program for handling the cultural and role changes involved in new SAP rollouts.
Solution Manager also positions you to get involved with cutting-edge eSOA projects. You can generate "process objects" with Solution Manager, allowing you to start down the road toward composite application development.
You can also port data from Solution Manager into Master Data Management (MDM) for number-crunching. As SAP continues its push toward a "business process platform," it is also making an effort to automate routine processes and provide a central spot for managing system performance and business processes. More and more, it looks as if Solution Manager will be integral to this vision."
|
The menus are expanded here for you to compare and contrast: |
Diagnostics Administration | Diagnostics Setup | ||
To View Last Diagnostics Logs, at the upper right corner click icon
See SAP Note 896981
Here are the choice of Groups listed in Diagnostics Administration > Diagnostics System > Self Check > Expert Mode: |
The "Scenarios" of version 3 is repacked in version 4 as "Role-Based Work Center Workflows" that map to the ITIL Service Management |
ITIL | Scenario | Work Center |
---|---|---|
Plan (Requirements) | Implementation of SAP Solutions | |
Build | Test Management | |
Deploy | Change Request Management | |
Operate | Solution Monitoring | |
Service Desk | ||
Root Cause Analysis (of incidents and problems) | ||
Administration | ||
Optimize | Delivery of SAP Services | |
Upgrade |
Notice that "System Configuration" is not considered a scenario.
|
|
Planning and executing heterogenuous System Copies
SAP Class TADM70
|
|
|
|
Exceptions | OS and DB | Configuration | Traces | Workload | Availability |
|
|
|
|
|
|
These menus are used during two types of Root Cause Analysis:
The Solution Manager provides several tools for determining the root cause of incidents and problems.
On R/3, to compare differences in settings between two independent client systems (e.g., QAS vs. PRD), use tcode SCU0(Client Compare).
|
3rd-Party Tools provided for Solution Manager root-cause analysis as part of the SAP add-on Solution Enablement Pack (SEP):
|
|
Layer | Units of Work / Metric | Symptom | Root Cause of Bottlenecks |
---|---|---|---|
Client | Requests / Responses | Occassional spikes in response time |
|
Amount of data between client and server | Each transaction > 500 KB either way |
| |
Dispatcher | Requests | - | - |
App. Servers | Transactions | - |
|
Processes | - | - | |
Load Balancers | Highest Percentage of Sessions to each host | Disproportionate load on some machines |
|
Database | SQL Compilation Time | A large proportion of slow response time |
|
Wait Time within DB | A large proportion of slow response time |
| |
Win. Page In to RAM from Disk Unix Page Out to Disk | > 20% of RAM per hour |
| |
DAS/SAN/NAS | Read / Write (I/O) | High |
|
JVM | Thread Utilization | High percentage of available threads are used |
|
Heap Memory Available and Memory Recovered From Each GC | Sudden Out-Of-Memory Fault |
| |
OLD SPACE GROWTH BYTES | Decreasing Trend over time until Out-Of-Memory Fault (Memory Leak) |
| |
Full GC FRACTION (& vs. Regular GC) | Occassional spikes in response time where GC time > 5% of total time |
| |
OS | CPU Utilization | Consistenly > 80% |
|
Memory Utilization | Consistenly > 80% |
| |
Cache space (SAP Note 1041556). | Consistenly > 80% |
| |
Win. Page In to RAM from Disk Unix Page Out to Disk | > 20% of RAM per hour |
| |
Email Out | Files | ||
Email Virus Scanners | Files |
|
|
|
|
|
No comments:
Post a Comment