50 - integrate new systems into sol

7/31/2019 50 - Integrate New Systems Into Sol

http://slidepdf.com/reader/full/50-integrate-new-systems-into-sol 1/39

Table of Contents

Table of Contents ..........................................................................................................1Tasks in Satellite System ..............................................................................................2

Register satellite system with Solution Manager System Landscape Directory .......2 Assign authorization for admin user in satellite system .............................................3Install and register CCMS agent on satellite system .................................................6

Tasks in the Solution Manager system .........................................................................7Remarks .....................................................................................................................7Special handling for inaccessible message server hosts ..........................................7 Assign RFC ACL to Solution Manager user .............................................................. 7 Add new systems message server ports ...................................................................7Configure CCMSPING for new systems ....................................................................9Integrate systems in CPH ........................................................................................ 11

Do a manual landscape fetch from SLD system .....................................................12Create RFC connections to satellite systems .......................................................... 14Create a descriptive logical component................................................................... 17 Add logical component to system landscape .......................................................... 19Configure Solution Monitoring ................................................................................. 21Configure autoreactions in RZ21 .............................................................................24 Adjust central system administration customizing ...................................................25

Standard configuration ......................................................................................... 25 Adding customer tasks .........................................................................................27

Configure EWA report..............................................................................................29Configure Service Level Reporting ..........................................................................33

One time basis configuration ................................................................................33 Add new satellite systems to SL reporting ...........................................................35



Tasks in Satellite System

Register satellite system with Solution Manager System LandscapeDirectory

Start RZ70

- Enter host and service as shown

-select activate

- then execute

This action schedules a job which updates the system landscape directory (SLD) withthe satellite systems configuration.

This step is also necessary for the SOL system!

Remark: As there is another Solution Manager 4.0 for BT recently installed.BT is maybe using the SLD on that SolMan to register the satellite systems. If this isthe case we will need to replicate that SLDs data via Data Supplier Bridge to our SLDand do no longer configure the RZ70 to our needs.



Assign authorization for admin user in satellite system

Remark: The authorization added here is NOT part of SAP_ALL!

In satellite system client 000:

Create new single role Z_S_RFCACL in PFCG

Via authorization tab open the Export Mode



Manually add the authorization object S_RFCACL

Set all authorizations to * except the last one. This needs to be set to ‘’

Save authorization and generate profile



Assign the user(s) which will later on create the RFC destinations and work withcentral administration from Solution Manager

Save and do a complete user comparison

Save the role and leave transaction



Install and register CCMS agent on satellite system

Install SAPCCMS4X and SAPCCMSR on satellite systems as described in thefollowing document (ensure that recent versions are installed in the kernel directoryelse the case sensitive password authentication as of NW2004s will not work – also

install a new SAPCAR to decompress the recent archive):

Monitoring SetupGuide NW2004s

The password of the CSMREG user is csolap04

Remember CEN is installed in client 000, so the agent config file needs to begenerated and pointing to client 000!!!!

use the “csmconf” configuration file generated in RZ21 for the agents installation:

LET THE CCMS AGENT AUTOSTART BY MEANS OF UNIX / WINDOWS!!!



Tasks in the Solution Manager system

Remarks

All tasks in Solution Manager are done in the Solution Manager production client.That is client 100!

System time zone is UTC

Solution Manager time zone is CET

Special handling for inaccessible message server hosts

Redirect access to message server hostnames which are not directly accessible fromthe Solution Manager system by the use of the hosts file.

For instance:The message server hostname returned from the DWP system via SLD isceas4315i4.This hostname is assigned to a backbone interface and not reachable from theSolution Manager up to now. As workaround this hostname is redirected to the user-LAN interface of the samehost by adding the last line to the Windows hosts file:

In this configuration the Solution Manager takes the user-LAN interface when tryingto access the ceas4315i4.

Use this technique in case other message server hosts are inaccessible too!

Assign RFC ACL to Solution Manager user

Remark: Usernames of a single user need to be the same in the Solution Manager system as well as in the satellite systems

Assign the user in the Solution Manager client 100 to the Z_S_RFCACL too (Thesame way as described earlier for the satellite systems)

Add new systems message server ports

Add satellite systems message server services in Windows services file:



Configure CCMSPING for new systems

Open NetWeaver Administrator: http://bbtsrvfdh96:8001/nwa

Add systems to custom selection:

You need to switch (if not done so already) from “Local System Administration” to“Custom Selection”. With “Custom Selection” it is possible to add systems to themanaged systems. The systems are read from SLD.

In the “Custom Selection” add the new systems with:

Open Sysem Mgmt / Monitoring / AvailabilityEnable Availability monitoring on all new systems:

- Assign the right CCMSPING group for the system, out of the following groups:

- do not select a single CCMSPING instance but usegroups, since with groups it’s possible to add another CCMSPING instance tothat group later on for monitoring systems from different locations, if needed.

Wait a couple of minutes and the application servers and logon groups are added(see below)…



You can now double check the CCMSPING configuration in RZ21:

All application servers and logon groups are added automatically!!!

Select the whole line of the added systemSelect “Create Monitoring Pause” to enter the backup windows timeframe!

After some more waiting the systems show up in the NWA (NetWeaver Admin)

availability monitoring



Integrate systems in CPH

The Central Performance History (CPH) aggregates performance data from MTEclasses into the CPH storage. This means that the data is longer archived then if it

would be in CCMS. However it is aggregated and thus smaller. This data can then beused for SL reporting and BI reporting.

This step here can normally be omitted since the assignment is already correctlyconfigured for all systems (*). Only use this procedure if you want to add additionalMTE aggregates into CPH.

In the main menu of RZ23N select assign procedure

Add MTE classes for all systems (*) or for a special system to Z_BT_CPH_SCHEMAdepending on the needs. Do not remove the existing assignments as they are usedfor SL reporting and BI reporting.



Do a manual landscape fetch from SLD system

This transaction configures landscape fetches from the system landscape directory.They are already scheduled once a day (see Initial Solution Landscape setup.doc).

However since we have added new satellite systems to the systems landscape wewill now need an immediate transfer:

Start TA SMSY_SETUP

Schedule a new landscape fetch with

Say Y

Schedule immediate

Use printer DUM for output



Watch your landscape fetch in SM37



Create RFC connections to satellite systems

Open transaction SMSY

Select the system via Landscape Components / Systems / Product / SID / Product

Remember: The user for adding the RFC connection has to have Z_S_RFCACL role

in satellite system client 000. ALSO YOUR USER IN SOLUTION MANAGER CLIENT100 NEEDS TO BE ASSIGNED TO THE Z_S_RFCACL IN SOL:100!!!

Go into change mode

Select ONLY client 000

Select generate RFC



A popup shows upUse default settings but check “Assign RFC Dest.for System Monitoring” additionally

Press generate

Logon a couple of times with your satellite systems user (THEN BACKWARDS AUTHENTICATION IS NEEDED, BACK TO SOLUTION MANAGER, SEE NEXTSLIDE)



Then logon back with your SOL user (needs to be assigned to Z_S_RFCACL)

Evaluate the log

In this case the remoteconnection was setup correct. Except that an old ST-PI isinstalled on the satellite system. After the new ST-PI is installed the RFC needs to beregenerated.

If you need to regenerate the RFC connections (e.g. because of a system copy), use

the button and delete the user and RFC’s, then delete the user SOLMANSOL100 and SOLTWMSOL100 and the RFC connectionsSM_SOLCLNT100_BACK and SM_SOLCLNT100_TRUSTED in client 000 of thesatellite system and then regenerate the RFCs again (select “RFC destination withuser” and “assign for monitoring”). After a system refresh a reconfiguration of RZ70 isalso needed in the client system.



Create a descriptive logical component

In this example we will integrate the DWT, DWI and DWP systems into a logical

component. In other words a single systems landscape.

A descriptive logical component name is Z_GE_VCM_DWA.Z for customer logical components, GE for the country and the last part for thelandscape name (VCM/DWA).

To create the logical component open transaction SMSY

Open the tab “System Groups and Logical Components”

Select create new logical components

Add correct product version (in case of VCM/DWA: SAP R/3 Enterprise 47x200) Add logical component nameUse the proposed logical component name



Assign the development, QA and production systems

In the popup all systems with clients which fit to the product version are shown.

NORMALLY THE DEFAULT CLIENT WOULD BE USED! SINCE WE ONLYCONNECT TO CLIENT 000 FOR SYSTEM MONITORING WE WILL ASSIGN ONLYCLIENT 000 TO THE LOGICAL COMPONENTS!

The assignment is now finished and the logical component needs to be saved



Add logical component to system landscape

Transaction: SOLUTION_MANAGER

In solution “BOMBARDIER MONITORING” open “Solution Landscape Maintenance”

Add logical component Z_GE_VCM_DWA

Save



To add other systems to the solution landscape which are no leading role systems,right click the system and select “Put in Solution”and save



Configure Solution Monitoring

TA SOLUTION_MANAGER

Select “Setup System Monitoring”

Select “Setup System Monitoring”

Now check the active flag on “Activate Monitoring” and save

You can use “copy customizing” to copy existing systems thresholds and activeMTE’s to the new satellite system



To activate availability monitoring check the active flag for “Instance status” on thenode “Instance Availability of <SAP instance>” and saveRepeat this for each instance

For each server activate “OS_Collector” and “Filesystems” and save



For the database activate all checks which status is green (MTE is available) belowperformance and administrating and save

You should adjust thresholds as appropriate!

Solution manager monitoring setup – thresholds are distributed to satellite systems!!!

When you adjust thresholds for a satellite system in the monitoring setup the MTEproperties will be changed in the satellite system!!! This means that you canconfigure all MTE properties centrally in the Solution Manager monitoring setup!!!

Automatic changes on the satellite system:

Solution Manager automatically assigns the MTE to the customer variant “*” on thesatellite system and changes the value within!



Configure autoreactions in RZ21

Use transaction RZ21 and open the Assign Central Autoreactions program

Autoreactions should be assigned as committed in the Bombardier team.

Depending on the needs assign central autoreactions to send alerts to

the ALM in RZ21.Keep in mind that the threshold values for the satellites MTE are configured centrally in Solution Manager Monitoring Setup!!!



Adjust central system administration customizing

Standard configuration

Set System Type

Set Involved Components as appropriate (In case of DW* and SOL select ALE andBI backend monitoring) – In case other components are connected to this backendsystem select tasks appropriately.

Save



Then select “Load Default Frequencies” or adjust values as appropriate to ownvalues

You can deactivate tasks by opening a task and changing its frequency to “notactive”. Vice versa you can activate tasks by assigning another frequency to them.

Save

Remark: It is also possible to copy the customizing by using “Customizing Copy” below the “General Session Customizing” node. This is useful if a customized systemalready exists and the central system tasks customizing should be copied to the new systems.



Adding customer tasks

You can add customer tasks as well.In our scenario RSPCM and RSMO where added for BI monitoring for the SOLinstance.

This was done as follows (and can be used as template for other customer taskswhich should be added to other systems):

Select the instance

Select “Defining User Task Area”

Add new user task area

And save

Goto next tab Add two times the recently defined user task area with the two transactions in charge

(RSMO and RSPCM). As “action type” select transaction.



And save

Goto next tab Add the two User Task Groups and assign each a User Task Description

And save

User tasks now show up in the tasks tree

Now the frequency of the new customer tasks needs to be adjusted:

Open each tasksSet the frequency to every 1 week (since the load and process chains only ran oncea week on Sundays)

And save



Configure EWA report

Setup central SDCCN (yet only done for SOL, DWT, DWI and TST not DWP!!!):

Prerequisite: Newest ST-PI and ST-A/PI is installed on satellite system

Transaction SMSY

Environment / SolMan Operations / Administration SDCCN

Select add

Select new systems and confirm

In systems overview select the new systems and select assign as master system.

Therewith SOL becomes the master system of the new satellite systems.



If you have used the old Service Data Control Center (transaction SDCC), it must bedeactivated before you activate the new Service Data Control Center (transactionSDCCN). To do this, delete any scheduled background jobs that are connected with

SDCC. For example, AUTO_SESSION_MANAGER, SESS* , SASM* in the satellitesystem.

If you have never used transaction SDCC just go on.

For more information please see:http://help.sap.com/saphelp_sm40/helpdata/en/6e/6135418ac8d92be10000000a1550b0/frameset.htm

Select activate the newly assigned satellite systems

Call SDCCN in satellite system by double clicking

The GUI switched to the satellite system into transaction SDCCN:

Create new task

http://help.sap.com/saphelp_sm40/helpdata/en/6e/6135418ac8d92be10000000a1550b0/frameset.htm






Select refresh sessions

Select now and SM_SOLCLNT100_BACK as RFC destination

Wait until task is finished (wait until the active sign has disappeared

)



Select start now on the newly created “refresh sessions” tasks

Now execute Service Preparation Check

Implement recommendations for the service preparations as proposed by the checkin the satellite system!



Configure Service Level Reporting

Start Setup Service Level Reporting

One time basis configuration

(This configuration needs to be only done before adding the first system)

Select “Standard” report

Save+next open check



Set Customer Address

Set scheduling




Add new satellite systems to SL reporting

Select new satellite systems(EWA needs to be configured for these systems!!!)


Set System availability to CCMS-ping based

Save + next



Edit Template downtimes and/or template Critical uptimes (downtime window shouldbe the same timeframe than defined before for CCMSPING monitoring pauses!)

Select done

Save+next

Select availability CCMS-ping availability types fitting to the system

For satellite systems go to tab “Monitoring System” and set “Monitoring System Type”to “Solution Manager System” and select “SOL”



Set template reporting format. This can be reused for the single availabilityconfigurations later on.

DoneSave+next

Select MTE for Instance availability and select for reporting

Load the templates report format configuration with

DoneSave+next



In the instance availabilities timetable goto planned downtimes and select “Planned

downtimes” from the menu bar . This loads the TimetableTemplates.

Select DoneSave+next

Redo last two steps (nodes) for other availability types

Take care to select the right CCMSPING (00 = Canada; 01= Germany; 02= Others –same as they are assigned in CCMSPING configuration) in case a dedicated

CCMSPING is asked in the MTE assignment (this dedicated CCMSPING is onlyneeded for ABAP or JAVA availability checks)



Setup and adjust KPI’s for SL report

Check and adjust KPIs accoding to SLA specifications!

DoneSave+next

Redo the last steps for the other added systems

when done so: save setting and leave SL configuration

KEEP IN MIND: Every planned downtime must be inserted into thisconfiguration!! Else the SL report would report an unplanned one, thusviolating the SLA!

50 - integrate new systems into sol

Documents