Solution Manager 7.2 – Installation and Configuration – II – Configurations

Part 1: Solution Manager 7.2 – Installation and Configuration – I – Installations

Part 2: Solution Manager 7.2 – Installation and Configuration – II – Configurations

Part 3: Solution Manager 7.2 – Installation and Configuration – III – Changes from 7.1 to 7.2

Part 4: Solution Manager 7.2 – Installation and Configuration – IV – Managed System Config – General Info

Part 5: Solution Manager 7.2 – Installation and Configuration – V – Managed System Config – ABAP System

Part 6: Solution Manager 7.2 – Installation and Configuration – VI – Managed System Config – HANA DB

Part 7: Solution Manager 7.2 – Installation and Configuration – VII – Managed System Config – Busines Objects

Part 8: Solution Manager 7.2 – Installation and Configuration – VIII – Managed System Config – Java System

You will find the configuration details of Solution Manager 7.2 on this blog.

Solution Manager 7.2 Configurations

I- CA Introscope Enterprise Manager Strategy

From Master Guide;

CA Introscope Enterprise Manager must be installed on the SAP Solution Manager host or on a separate host.

For more information, see service.sap.com/instguides –> Installation & Upgrade Guides –> SAP ComponentsSAP Solution ManagerRelease 7.2 –> 6 Additional Guides – Introscope –> Introscope Setup Guide 9.7.

Useful SAP Notes about Introscope Enterprise Manager

1565954 – Introscope 9 Release Notes

797147 – Introscope Installation for SAP Customers

2138309 – Introscope 9.7 Release Notes for changes and open issues

1579474 – Management Modules for Introscope delivered by SAP

Follow the Setup Guide for downloading and installing the Interescope Enterprise Manager current version 9.7.

Install java package, Modify installer.properties first and run the OS independent installer.

You can verify the successful installation checking the installation logs from wily log directories.

You should carry on the post installation steps like adapting java parameters, isntallaing sap modules etc.

After successfull installation you can reach the IEM webview or workstation using the urls like http://emhost:8081/webview or http://emhost:8081/workstation.

Or you can use Solution Manager Root Cause Analysis work_center.

Sample workstation screen;

Sample webview screen;

II- SOLMAN_SETUP – Mandatory Configurations

These notes should be read carefully and applied before configuring the system.

2236044 – SAP Solution Manager 7.2 Support Package 01: Dump in transaction SOLMAN_SETUP

2229953 – Solution Manager 7.2 SP Stack 01: recommended corrections

2154957 – Unified Rendering for SAP_UI 740

2212887 – Corrections for unified rendering up to SAP_UI 740/14 Ia

1411980 – Comments about the implementation of unified rendering corrections

There are 3 mandatory configuration scenarios; System Preperation, Infrastructure Preperation and Basic Configuration.

Here are the detail steps for all these configuration scenarios.

1- System Preperation

Define the System’s Role in the firts step.

There are manual and automatic activities to perform in Check Prerequisites Step. Each step  has its documentation. You can Display the documentation and follow the instructions carefully.

There is a navigation link also for the related transaction or web dynpro or related urls.

On Setup Connections to SAP step you have RFC Connectivity part for creating SAPOSS and SAP-OSS-LIST-O01.

And there is Support Hub Connectivity part for below functioanalities;

• • Configure SOAP Runtime  : User SRT_ADMIN to configure SOAP according to the documentation.
  • Register new S-User in SAP’s PI System : You create a technical user on SMP according to the notes “2174416 – Technical User for Data Transfer with SAP Backbone System and 2174416 – Technical User for Data Transfer with SAP Backbone System”
  • Specify Configuration parameters

There are automatic activities Configure SSL Store, Configure Consumer Proxies and Log. Port and Check Channel Configuration.

The help screen for this step explains us about the new  communication channel of SAP with below paragraph.

“SAP will introduce a new infrastructure and data communication channels, starting with SAP Solution Manager 7.2. This new framework builds the foundation for all future applications exchanging data between SAP Solution Manager and the SAP Support Portal in a secure, reliable, and controlled way. Existing applications will not be affected by this change and they will be migrated to the new platform gradually within the next few years without business disruption.”

In Apply Recent Corrections step, you apply recent ABAP and Java corrections to your SAP Solution Manager system

In Maintain Technical Users step you create or update dialog users, technical users, or BW users, and assign roles to users, depending on the scenario.

In the last Complete step you can see overall configuration of system preperation steps. In need you can jump to the required step back.

2- Infrastructure Preperation

In this scenario you configure the infrastructure to run SAP Solution Manager. There are 8 steps to succeed the configuration of the scenario.

In the “1- Set Up Landscape Management” step you set up the synchronization of the system landscape directories (SLDs) and SAP Solution Manager, to keep the information about the system landscape up-to-date. Each substep screens can be seen below.

In substep SLD Connnections you create a new connection like below.

“2- Set Up Java Connectivity” step consists of Define HTTP Connectivity, Enable Connectivity and Diagnostics Agent Authentication substeps. You provide required field values accordingly and execute automatic configurations as seen below.

Solution Manager is using SAP BW for reporting purposes. You can use either the currnet client of Solution Manager or you can define another SAP BW system. In “3- Set Up SAP BW” step you firstly confirm the BW system, then create BW users and in the last substep you execute automatic acitivities.

You must have defined the logical system name for your BW client.

In “4- Define CA Interescope” Step you discover and define your Interescope Enterprise Manager. You must have installed Diagnostic Agent (DAA) Instance on your Solution Manager System. You can manage Interescope EM users in this step also.

In “5. Set up E-Mail Communication“  step you set up the infrastructure that enables SAP Solution Manager to send notifications using e-mail and text messaging (short message service, SMS).

Some scenarios in SAP Solution Manager needs CRM infrastructure. In “6- Configure CRM Basics” step you configure these infrastructure in manual and automatic steps.

In “7- Enable Gateway Services” you activate OData services in SAP Gateway for SAP UI5 applications and mobile applications. With this activation you can use SAP Fiori applications for Solution Manager services. For SAP Solution Manager, the SAP Gateway and SAP Solution Manager share the same system.

As a prerequisite the user who performs this step has a task in the customizing transport request. Activation of the services uses this task.

After selecting the required services you prepare activation and then with the help of the help text you Start Transaction and activate OData services.

And in the final “8 – Complete” step you see the statuses of all steps. If you have any red status steps you could go back and correct the configuration.

Now you can pass the Basic Configuration Scenarios.

3- Basic Configuration

There are five steps to fulfill in this scenario as you can see below picture. In the first “1- Configure Basic Functions” step you execute automatic configurations for creating logical ports, activating services, enabling Solution Manager applications.

In “2- Schedule Jobs” step many important Solution Manager Jobs are scheduled.

In “3- Configure Manually” step, you configure the following:

• Content update (SAP Solution Manager Content, service content)

• Connection from SAP to the SAP Solution Manager system

• Session housekeeping

In “4- Create Basic Dialog Users” step, you create or update dialog users for root cause analysis (SAPSUPPORT) and service delivery (SAPSERVICE).

This final “5- Complete” step provides an overview of the steps that have been performed in this scenario, including information about the users who made the changes, and the status of each step.

This is the end of Solution Manager 7.2 configurations.

Next topic will be about the changes from Solution Manager 7.1 to Solution Manager 7.2 in terms of System Administration.

Thanks for your interests.