HOW to check where a system is ABAP stack or dual stack(ABAP + java).

method- 1

 sm51

  under message types, J2EE stands for dual stack

If not

ABAP stack.

Method-2
smicm-->menu bar-->GO TO --> services --> is J2EE server is there then, the system is dual stack
                     

                                                                      else

                                                                      ABAP stack
Method - 3

 if Operating system level access is there then, this method will be applicable, where as for the above 2 methods GUI access is enough.

access

usr/sap/sid/instance/J2EE


is J2EE file is present then, system is dual stack otherwise ABAP stack only.

System monitoring in solution manager 7.2

One of the best ways to think about SAP Solution Manager is as a tool to align business with IT. Most companies still treat ERP like a business facility. You design and layout your SAP landscape with enough space for your team, with offices, conference rooms, storage areas and other functional areas, and you run your business there. Renovations are rare and expensive — the goal is to build something where you won’t have to knock out walls or make new additions anytime soon.

SAP Solution Manager 7.2 has the tools to make your ERP work more like a business plan. You lay out your plan as a strategy based on the state of your company and your market, but you revisit it frequently. If you move into a new market or grow rapidly, you might have to make some major changes, but that’s okay — having that flexibility is what lets you stay so competitive.

Technical Monitoring Benefits of SAP solution manager 7.2 

• system monitoring of solution manager 7.2 makes it easier to keep sap servers healthy, allowing to improve performance, reduce downtime and reduce needless duplication through reusable templates.
• Technical monitoring has always been a focus of Solution Manager, but SolMan 7.2 is the first version designed with SAP HANA single-stack deployment in mind. That improvement has been a big help, allowing HANA customers to simplify their deployment and simplifying migration for SAP ECC users.
• The System Monitoring application provides an overview of the current status of technical systems, including their associated instances, databases, and hosts.

• Advantages of Technical Monitoring of solution manager 7.2.
1. SAP solution manager minimizes Downtime.
2. SAP SolMan 7.2 Provides Application-Specific Monitoring.
3. The Ability to Reuse Templates.

1. SAP solution manager minimizes Downtime: Barring a few scenarios like major natural disasters and attacks, unplanned downtime means someone has screwed up. More often than not, this is the result of insufficient Technical Monitoring, or a disconnect between the team who monitors your ERP, and the people who make decisions about upgrades. But even if you manage to avoid unplanned outages, you’re likely still paying for inadequate monitoring with long-planned downtime. When businesses prioritize the wrong things or put off needed changes, they can’t plan SAP implementations, upgrades and migrations Sooner or later, they have to play catch-up, which increases cost, complexity, and disruptive downtime.SAP Solution Manager 7.2 helps businesses develop a more strategic approach to SAP, with its powerful Technical Monitoring capabilities. Its ongoing monitoring and alerting functionality are complemented by deep reporting on system health and performance through SAP Earlywatch, allowing businesses to take a more strategic approach to SAP and reduce downtime.
2. SAP SolMan 7.2 Provides Application-Specific Monitoring:

                compare to solution manager 7.1 to 7.2. technical monitoring is one of the best advantages.

through Technical monitoring all the solution manager dashboards data can be monitoring.

which includes Application-specific Monitoring.

for any Additional specific Application specific and cross-application dashboards, create new dashboards option will be provided with solution manager 7.2.

by Fiori technology, the monitors will be the same from device to device, so it is easy for the sap end user to report the changes. to achieve this strong technical person required to monitor the system, so to avoid effects to other parts of solution manager.

Practically:System Monitoring is based on automated checks in regular time intervalls in the four categories Availability, Performance, Exceptions, and Configuration. In each of these categories, several metrics and corresponding thresholds can be defined per managed object

System Monitoring is based on automated checks in regular time intervalls in the four categories Availability, Performance, Exceptions, and Configuration. In each of these categories, several metrics and corresponding thresholds can be defined per managed object.

The System Monitoring application provides information about the current status according to the last measurement of each metric. In addition, alerts will be created and can be handled via the Alert Inbox in case thresholds are violated.


SETUP:

1. from the solution manager system, run the T-code: SOLMAN_SETUP.
2.navigate to SAP SOLUTION MANAGER -->CONFIGURATION(All Configurations).

3.navigate to Application operation -->system monitoring.

 4.

5.General Approach:

•     for the first time configuration and any changes to the previous configuration, need to proceed with step 2 and its subprocess.
• To add/remove/changes to monitors can directly proceed with step 4 followed by 5 and 6.
• To activate the monitor to the particular server or several services can proceed directly with step 5.

6.

7.

8.

9.

10.

MY references

https://wiki.scn.sap.com/wiki/display/TechOps/Solution+Manager+7.2+-+System+Monitoring
Extractor framework: https://wiki.scn.sap.com/wiki/display/TechOps/EFWK_Home