Sap Solution Manager Api

[Orestes Hardy]

Asthe main administrative solution for SAP users, SAP Solution Manager combines a handful of tools alongside content and direct access to SAP to ensure reliability and stability of solutions. Its numerous applications can be categorized into one or more of the defined Information Technology Infrastructure Library (ITIL) stages of service strategy, service design, service transition, service operation, and continual service improvement.

SAP Solution Manager was first released in the mid-2000s and served as a project implementation tool and support system for SAP solutions only. Users found this limiting as its capabilities focused around the IT department and not the business.

SAP remedied this in subsequent releases by opening up SAP Solution Manager to handle not only SAP products, but also integrated systems, partner products, and even non-SAP software. In 2016, version 7.2 was released to the public and continues to be the main release of SAP Solution Manager. It is the only release currently supported by SAP. Intermittent service packs for 7.2 are released regularly, with the latest being SPS 10, which became available in December 2019.

SAP Solution Manager, in short, serves as the central hub through which SAP solutions can be implemented and maintained. System administrators looking to make changes to an IT environment, monitor solutions in real time, integrate new solutions (on-premise or cloud), test updates to solutions, document business processes, control access rights, and more, will utilize this tool.

This incredibly complex tool monitors systems and should be carefully configured in order to provide a report that is actionable. It provides valuable alerts for all sorts of scenarios for both SAP and non-SAP applications, as well as the databases and operating systems they run on.

This is actually three separate tools all focused on the same thing: the connections and flow of data between systems. The three tools are SAP Process Integration monitoring (for both SAP Process Integration and SAP Process Orchestration), interface and connection monitoring (both on-premise and cloud solutions), and message flow monitoring.

SAP Solution Manager provides admins with the ability to integrate disparate systems. This is especially helpful for customers running SAP S/4HANA and looking to utilize SAP cloud solutions such as SAP Ariba, SAP Integrated Business Planning, and SAP SuccessFactors.

The SAP Solution Manager Test Suite allows for manual and automated testing of both SAP and non-SAP solutions. Users can create and customize tests, sign up for emailed result notifications, analyze potential results from a planned changed, and more.

SAP Solution Manager supports detailed documentation of business processes for teams to utilize when onboarding new employees or learning to use a solution themselves. Library functionality allows for reusing existing documentation and customizing it as needed, while the Business Processes area allows IT and business users a chance to define their perspectives.

This branch is a clone of the production branch and stores business process monitoring metrics (such as KPIs) and alerts. Any changes made to the production branch are simultaneously reflected in the operations branch.

Solution Management is the function responsible for defining desirable, viable, feasible, and sustainable large solutions that meet customer needs and for supporting development across the solution life cycle.

I've installed my solution manager server complete with its dual ABAP/JAVA stack and also configured BW on it. I'm using BW only for Solution Manager integration e.g E2E Analysis and Availability Monitoring.

My question is about note 830576 - Parameter recommendations for Oracle 10g. Would Solution Manager qualify as an OLTP or an OLAP system? I could argue the case either way, just wondered what anyone's thoughts were on this?

So my question now is: do i need a Java instance? In what use cases do i need the Java part of Solution Manager? The only thing i can come up with is the need of an ADS (if Adobe is needed), but i can use any Java instance in the landscape for that.

For all data to be collected for EWA reports, you need Solution Manager Diagnostic Agents (SMDAs) to be deployed on all SAP machines as well you need Byte Code Adapters (BCAs) deployed and connected to CA Wily Introscope for collecting data about your JAVA systems.

Anyway, I have asked Marc Thier and Wieland Schreiner a similar question and the response was that SAP is not going to change SAP Solution Manager Architecture in the future, but probably in cooperation with other tools (like Focused Run), it can be imagined to use SAP Solution manager ABAP stack for scenarios and the other tool for EWAs, etc. There should be some news in the future regarding this.

"With the installation of SAP SOLUTION MANAGER 7.2, a JAVA and an ABAP part will be separately installed with two different SIDs. But both stacks are necessary and work together"

But i would like to know what the Java stack is used for? Currently i have closed my Java Stack and have not yet found any issues with that.

I installed it on another machine it worked fine. However that machine is no longer available for me to use and I'm now installing it on a NUC. I've installed the version you provided (2.0.0.20), however now there is no KVM Remote Control icon available for me to use.

The issue with Intel AMT KVM and the discreet third party video card is a expected behavior. Basically what s occurring is that the OEM Implementation of the BIOS is shutting down the on Board GPU, hence when you try to connect via Intel AMT KVM, the onboard GPU is not going to be available.

Hey guys, I'm having the same issue using the KVM Remote Control, even tough the VNC plugin inside vPro PSM Manager does actually works fine. I'm trying to Access an Optiplex 7050 Core i5 6th Gen Intel Core vPro with Windows 10. Have you guys considered if there's a bug with the SW? btw I'm using Intel vPro PSM v. 2.0.038 and it works fine under an Optiplex 7040 same processor different OS Windows 7

Before to go any more further I'm gonna put in you in context. I have two vPro platforms, One is an Optiplex 7050 Windows 10 and the other one is a Latitude E7270 Windows 10. I use an Ethernet cable to connect the two computers, and I'm using static IPv4 so they can hear each other. When I do so the communication from the Optiplex to the Latitude I'm able to connect to using the KVM Remote Control and The VNC when the PC is in the BIOS. However, when I try to do so on the other way. I'm getting the error under the KVM Remote Control (If I reboot the Latitude to access the BIOS I can use VNC to connect the machine). I follow your steps and Below you'll find the info. regarding the Latitude and the errors.

PD: Not The Optiplex nor the Latitude have discrete video card just off course the Intel graphics, and also, let me know if the parameters that we need to verify are the ones on the Optiplex.

This is the info. regarding the Optiplex 7050, I see that there are two values set in true. The CCM and the HBP I dig into it and I think it is related with consent to KVM the machine, am I right? If I am how can I change it? If not let me know if this info. can tell you more about this matter

It looks like a consent issue to me as well. When a device is in CCM mode, KVM will always require a user consent code. I havent used this generation of PSM, so I havent experienced the issue. I would switch to KVM view+ for making the KVM connection. I have used KVM view+ a lot and it handles the user consent component just fine

Well it seems that the problem was related with the I/O rules, I allow ports from 5900-59100 to support multiple communications through VNC and also, I gave permissions to ports 16992-16995 to let Intel AMT to be able to listen between components. At the end I was able to access from a non-vpro platform (Console) to the other two vPro platforms (Optiplex & Latitude) using the VNC plug-in on Intel AMT, however it allows to connect just one device using the KVM plug-in on Intel AMT (Either the Latitude or the Optiplex whoever I click first the other one doesn't work).

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

But for me as a nebiw, the posts starts very dep. So i am wondering if somebody could help me with my question.

We are searching a small solution to push the alerts, which are generated by the solman, towards Jira Servicedesk, so that there will be aticket generated and filled with specific data.

what exactley is needed for this? Do we have to code on our own? Which integration is also needed in the solman? is there anything, that need to be installed? Any AddOn? I read something about the OST Plugin.

The point is, i want that emails, which are created by the solman, when an alert happens, for example the diskpace went over 90% for a specific filesystem, to be created as an issue in jira. Which means, i need to put the information from the email into the jira issue. So i need to link specific types. I dont want to do any more.

I'm known for doing this with bash scripts, literally calling "curl" to send a batch of data to Jira for it to create the issue I want. If it were me, I'd simply have solman run one of my scripts. But I don't know what solman supports - it might be able to do a rest call via a dialog, it might have an internal scripting thing it can do, it might have a dedicated "poke jira" function, etc. I just don't know what solman supports.

sap can trigger scipts, yes, but they will be time triggerred. And i need the Alerts, which are generated by sap to not only be send via email, they also need to be pushed into jira. so curl is no option for me.

3a8082e126