Add Sys to Solman 7.0

8/13/2019 Add Sys to Solman 7.0

1/34

Adding SAP System to Solution Manager step by step

This one very long post, request you to follow the steps to add the sytsem in solman.

This Post describes the steps that are required to connect a (new) SAP system to the SAP Solution

Manager, for instance to generate EarlyWatch Alert reports or for including the system on SolutionMonitoring.

This Post describes the various steps that have to be performed, depending on the type of SAP system

and the configuration that exists in Solution Manager. For a fresh installation of Solution Manager, all

steps have to be performed at least once

2. Execution of activities

2.1. Create the system in SAP Solution Manager

Generally, new systems will be available known in the Solution Manager as their data is obtained fromthe System Landscape Directory. Especially for Java based systems, retrieving data from the SLD ensures

that the correct instances are defined.

However, sometimes systems are created under the wrong product in the Solution Manager when they

are retrieved from the SLD. It is recommended to change the assigned product if it is not correct.

Although for monitoring purposes it is not required per se, it is for usage of Maintenance Optimizer.

Way of working in practice:-

For SAP Net weaver 2004 and later systems, an installation key is required upon installation. This key has

to be created using the SAP Solution Manager. To perform this action, the system will need to becreated in Solution Manager. The general approach here is to create a new system (and assign the

correct product), but not adding any data such as the database or server: this data is not required to

generate the installation key. Then installing the system and registering it in the SLD, so the SLD will

have also the technical data of the system. This information will then automatically be replicated to

Solution Manager and enrich the system information there.

Maintain system settings for JAVA systems:-

For JAVA systems, after the data got replicated from the SLD to Solution Manager, some additional

actions are required.

This is required as the relevance field is used by Solution Manager to determine which systems can be

mapped to which logical components. By default, systems have Application Server ABAP as relevant

component. As J2EE only systems do not have this system component, their product is not recognized.

This has to be maintained in the Landscape Components Systems part of the landscape definition

(transaction SMSY).

Choose the system that is to be maintained and choose the Selection of Main Instances tab. Here,


2/34

uncheck the check behind Application Server ABAP.

security reason removed SID name, This is SMSY screen shot

Check the Application Server Java as relevant. Also, choose the System Component checkbox and

enter the (SAP System ID) as system and type Java-System. Choose Save to continue
http://4.bp.blogspot.com/-watCXIWX78w/T7dBoiUllOI/AAAAAAAAJck/oqZUKjS5WQQ/s1600/1.pnghttp://1.bp.blogspot.com/-aEI-GW3iDrk/T7dBeSOlHkI/AAAAAAAAJcc/fvBizomhrnI/s1600/1A.pnghttp://4.bp.blogspot.com/-watCXIWX78w/T7dBoiUllOI/AAAAAAAAJck/oqZUKjS5WQQ/s1600/1.pnghttp://1.bp.blogspot.com/-aEI-GW3iDrk/T7dBeSOlHkI/AAAAAAAAJcc/fvBizomhrnI/s1600/1A.png


3/34

See the Above screen shot i added one of the ABAP + Java system in Solman.

Finally, click the Save button.

The system data for a JAVA system has now been correctly maintained in the Solution Manager

Register system for availability monitoring using CCMSPING

For availability monitoring (i.e. is the system UP) the CCMSPING agent is used. This agent will

periodically, usually once a minute, check to see whether it performs a log on to a system. This section

describes how to add a system to the systems monitored by CCMSPING

Preparation

First, on the host where the CCMSPING agent is running (usually the Solution Manager host itself), add

the following entry to the services file (:\WINDOWS\system32\drivers\etc\services)sapms 36/tcp where

is the monitored systems SAP System ID and is the monitored systems instance number.
http://4.bp.blogspot.com/-9qHnWYhnhkM/T7dCyozPeGI/AAAAAAAAJc0/G4GdQ2NBix0/s1600/3.pnghttp://4.bp.blogspot.com/-jpk8I_l4Q8I/T7dCEie3ISI/AAAAAAAAJcs/mwyZx2yMWxo/s1600/2.pnghttp://4.bp.blogspot.com/-9qHnWYhnhkM/T7dCyozPeGI/AAAAAAAAJc0/G4GdQ2NBix0/s1600/3.pnghttp://4.bp.blogspot.com/-jpk8I_l4Q8I/T7dCEie3ISI/AAAAAAAAJcs/mwyZx2yMWxo/s1600/2.png


4/34

Note: the applies to the instance number of the ABAP message server. If no ABAP message server exists

for the SAP system (i.e. in case of JAVA only systems, no service has to be maintained in the services file.

By connecting to the message server, the CCMSPING agent will retrieve data about the various instances

of the SAP system, including their availability and response time.

Note: to save time, it might be a good idea to add as many known s to the services file in one go.

Configuration in Solution Manager

After the action in the last step, the CCMSPING agent is able to retrieve the port on which an SAP
http://2.bp.blogspot.com/-QL3t3AnegZw/T7dDvg32udI/AAAAAAAAJc8/4J05zYGtJj0/s1600/4.png


5/34

systems message server is listening. Next step is to configure the agent in Solution Manager itself.

Log on to the Solution Manager and call transaction RZ21.

From the menu choose Technical Infrastructure --> Availability Monitoring --> Configure CCMSPING

Availability mon. This shows a list of monitoring systems.

From this screen, choose Monitoring --> Create system.

Configuration here depends on the type of SAP system that is to be monitored.
http://1.bp.blogspot.com/-F5zfRum9i4A/T7dGo0yg5tI/AAAAAAAAJdU/3pH_WyWVB4U/s1600/5A.PNGhttp://1.bp.blogspot.com/-2XrtTgOMVRI/T7dFvhpT41I/AAAAAAAAJdM/BCkuWAMwJZ4/s1600/5.pnghttp://1.bp.blogspot.com/-F5zfRum9i4A/T7dGo0yg5tI/AAAAAAAAJdU/3pH_WyWVB4U/s1600/5A.PNGhttp://1.bp.blogspot.com/-2XrtTgOMVRI/T7dFvhpT41I/AAAAAAAAJdM/BCkuWAMwJZ4/s1600/5.png


6/34

Enter the required data in the screen:

Choose Copy Connection Data and Options. Note: it might take some time before the CCMSPING agent

will get its first data.

To check whether CCMSPING is correctly retrieving data from the monitored system, call transaction

RZ20. Choose template: SAP CCMS Monitor Templates Availability and Performance Overview.
http://2.bp.blogspot.com/-S99mFtfhjI4/T7dHFZNmZMI/AAAAAAAAJdc/mNKgzRGPqCs/s1600/6.png


7/34

The system should now be visible in the monitoring tree.

Create RFC connections

Note: this step is only required for ABAP (and ABAP+JAVA) systems.

For the Solution Manager to retrieve data from a monitored system, RFC connections are required. To

create the RFC connections to a monitored system (and back) two steps have to be performed. Also, an

administrator user is required in the monitored system.

At the end of these steps, three RFC connections from Solution Manager to the monitored system will

have been created:

an RFC calledSM_CLNT_READ that is used for automatic data capture for monitoring purposes

an RFC called SM_CLNT_TMW that is used when Change Request Management is configured in

Solution Manager

an RFC called SM_CLNT_TRUSTED that is used for interactive logon to the monitored system. This is a

form of a SSO solution where users logon to the Solution Manager once and can then jump to themonitored systems.

Add authorization object to administrative user

The Solution Manager can use trusted RFC connections for SSO type logon options. The setup of trusted

RFC connections requires an authorization object assigned to the administrator that will
http://4.bp.blogspot.com/-ytPOJopYvmI/T7dHyPM5zKI/AAAAAAAAJds/qa9pLrVfkFI/s1600/7.png


8/34

create the RFC connection in the monitored system that is not a part of SAP_ALL or SAP_NEW. This step

adds this authorization object. Add the S_RFCACL authorization object to the administrative user. In the

system to be monitored, call the profile generator (transaction PFCG).

Enter a name for the role and choose Create.
http://1.bp.blogspot.com/-1rdqU8TYNs8/T7dJaXZAlSI/AAAAAAAAJd8/4fvN9E8V_p4/s1600/9.pnghttp://3.bp.blogspot.com/-c_x3Wv8QQCg/T7dInok4iuI/AAAAAAAAJd0/8Lm0gaWyVHg/s1600/8.pnghttp://1.bp.blogspot.com/-1rdqU8TYNs8/T7dJaXZAlSI/AAAAAAAAJd8/4fvN9E8V_p4/s1600/9.pnghttp://3.bp.blogspot.com/-c_x3Wv8QQCg/T7dInok4iuI/AAAAAAAAJd0/8Lm0gaWyVHg/s1600/8.png


9/34

Enter a description for the role and choose the Authorizations tab. SAP will ask to save the role. Do so.

Click the Propose Profile name button and then choose the Change Authorization Data button
http://3.bp.blogspot.com/-72N9AzqIgZs/T7dJmOT0I4I/AAAAAAAAJeE/mKtyHS3ljRU/s1600/10.png


10/34

Choose not to use a template (Don not select templates). Choose the theabove button manually.
http://2.bp.blogspot.com/-8SiN7QSLUU8/T7dKWrL4SDI/AAAAAAAAJec/yi7ZQmPfLU4/s1600/13.pnghttp://1.bp.blogspot.com/-W5pYPGlM5yE/T7dKGKoQNvI/AAAAAAAAJeU/nT0XKEOW014/s1600/12.pnghttp://4.bp.blogspot.com/-rR8szipuzQM/T7dJ4cFtl2I/AAAAAAAAJeM/wPhpWCmiQL4/s1600/11.pnghttp://2.bp.blogspot.com/-8SiN7QSLUU8/T7dKWrL4SDI/AAAAAAAAJec/yi7ZQmPfLU4/s1600/13.pnghttp://1.bp.blogspot.com/-W5pYPGlM5yE/T7dKGKoQNvI/AAAAAAAAJeU/nT0XKEOW014/s1600/12.pnghttp://4.bp.blogspot.com/-rR8szipuzQM/T7dJ4cFtl2I/AAAAAAAAJeM/wPhpWCmiQL4/s1600/11.pnghttp://2.bp.blogspot.com/-8SiN7QSLUU8/T7dKWrL4SDI/AAAAAAAAJec/yi7ZQmPfLU4/s1600/13.pnghttp://1.bp.blogspot.com/-W5pYPGlM5yE/T7dKGKoQNvI/AAAAAAAAJeU/nT0XKEOW014/s1600/12.pnghttp://4.bp.blogspot.com/-rR8szipuzQM/T7dJ4cFtl2I/AAAAAAAAJeM/wPhpWCmiQL4/s1600/11.png


11/34

Check Agent Registration

In CEN, call transaction RZ21 and in the Topology section, choose Agents for Local System. Choose

Display Overview.

Enter the authorization object. Choose Enter to continue.

Choose OK to continue.

Choose Save. Choose Generate. Choose Back to go to role definition.

Back in the role maintenance screen, choose the User tab. This makes it very quick to update the roles

assign to users or assign the new role to a user. Enter the name of the user the role is to be assigned toand choose User comparison.
http://4.bp.blogspot.com/-QgSF6I8zTCk/T7dKot4tBJI/AAAAAAAAJek/f7yGeZN3Bk8/s1600/14.png


12/34

Choose Complete comparison.

The administrative user (in this case called SAP-TI) now has authorizations to use and configure trusted

RFCs.

Note that every user in Solution Manager that is to use trusted RFC connections to log on to monitored

systems, require these authorizations.

Create the actual RFC connections

Be careful: the system that is to be connected to should have the latest ST-PI and ST-A/PI installed! Also,

an administrative user is required on the system to be connected with authorization for object
http://2.bp.blogspot.com/-rySRqQFiG7o/T7dLSwMgSYI/AAAAAAAAJe8/cPEgSrkRbLQ/s1600/17.pnghttp://4.bp.blogspot.com/-t6pC0pHBk14/T7dLGIq-QCI/AAAAAAAAJe0/zdEjREf7d_g/s1600/16.pnghttp://2.bp.blogspot.com/-rySRqQFiG7o/T7dLSwMgSYI/AAAAAAAAJe8/cPEgSrkRbLQ/s1600/17.pnghttp://4.bp.blogspot.com/-t6pC0pHBk14/T7dLGIq-QCI/AAAAAAAAJe0/zdEjREf7d_g/s1600/16.png


13/34

S_RFCACL. Note that this object is NOT in SAP_ALL. See the previous section for instructions on how to

assign this role to the user.

In the Solution Manager system, call transaction SMSY. Expand the Systems tree to the system that

should be connected. Then, select the row with the client that should be used for communication with

Solution Manager (generally the productive client or customizing client

Note: be sure to be in change mode!
http://4.bp.blogspot.com/-DOdepB0OfC0/T7dR11RhGoI/AAAAAAAAJfI/19KQ1Ssx-OE/s1600/18.png


14/34

As can be seen, no RFC connections have been defined (these are used for Solution Manager

configuration). Choose the Generate RFC Destinations button.
http://4.bp.blogspot.com/-8qtVYcu7JZQ/T7dSYb6kBtI/AAAAAAAAJfQ/hc3RYvE8Cyc/s1600/19.png


15/34

Generally, all the default settings can be kept. Make sure that the AssignRFC dest. For System

Monitoring checkbox is checked. This will automatically add the system to CCMS for monitoring. Choose

the button. The system will now require you to log on to the system with an administrative user with

execute privileges for authorization object S_RFCACL.

The result is an ABAP system that is now connected through RFC to the Solution Manager.

Register SAPCCMSR agent
http://3.bp.blogspot.com/-4apqV5tjfJA/T7dSuKECXGI/AAAAAAAAJfY/sPo8jjYQG8I/s1600/20.png


16/34


17/34

Register the agent:-

On the Java system to be monitored, start the Visual Administrator and choose Cluster
http://1.bp.blogspot.com/-2l9godWjaZs/T7dU18muheI/AAAAAAAAJf4/v_4WXywuo4U/s1600/22.pnghttp://1.bp.blogspot.com/-2l9godWjaZs/T7dU18muheI/AAAAAAAAJf4/v_4WXywuo4U/s1600/22.png


18/34

Dispatcher Services Monitoring. Choose the CCMS Agent Configuration tab. Choose the file on

local filesystem and enter required passwords. Finally, click register

Click the yellow triangle to automatically assign all authorizations.
http://1.bp.blogspot.com/-EP7IhbUW4N8/T7dVu-LRcoI/AAAAAAAAJgA/QU2wp5fkCNw/s1600/23.png


19/34

The agent is shown and has status Online.

System Group Entry
http://3.bp.blogspot.com/-egnSTrriCms/T7dWFF5NlNI/AAAAAAAAJgI/2aHSm8N8ADQ/s1600/24.pnghttp://4.bp.blogspot.com/-VRwCcutaqk8/T7dK1PEjvJI/AAAAAAAAJes/35JAc-GGdiY/s1600/15.pnghttp://3.bp.blogspot.com/-egnSTrriCms/T7dWFF5NlNI/AAAAAAAAJgI/2aHSm8N8ADQ/s1600/24.pnghttp://4.bp.blogspot.com/-VRwCcutaqk8/T7dK1PEjvJI/AAAAAAAAJes/35JAc-GGdiY/s1600/15.png


20/34

Call transaction RZ21. Technical Infrastructure Configure Central System Maintain System

Groups. Check if the of the J2EE system is added to the group J2EE_Systems.

Display the J2EE Engine Monitoring Data

Call transaction RZ20. Choose the monitor set All Systems from SAP J2EE Monitoring Templates. There

should be an entry for the J2EE system.

Appendix: create csmreg user and csmconf file
http://2.bp.blogspot.com/-NpO3xse3wkY/T7dXxY8x8ZI/AAAAAAAAJgg/vFPYV1b7_bQ/s1600/26.pnghttp://4.bp.blogspot.com/-SLTxs6YtIY8/T7dXUwEOmoI/AAAAAAAAJgY/0BHEAC1KD5g/s1600/25.pnghttp://2.bp.blogspot.com/-NpO3xse3wkY/T7dXxY8x8ZI/AAAAAAAAJgg/vFPYV1b7_bQ/s1600/26.pnghttp://4.bp.blogspot.com/-SLTxs6YtIY8/T7dXUwEOmoI/AAAAAAAAJgY/0BHEAC1KD5g/s1600/25.png


21/34

This appendix describes how to create a csmreg user and csmconf file in an monitored ABAP+JAVA

system to which an SAPCCMSR agent should register.

In the monitored system, call transaction RZ21. Choose Technical Infrastructure Configure

Central System Create CSMREG User

Creating the CSMREG user only requires a password to be entered. Hit Enter to create the user
http://2.bp.blogspot.com/-wx4AHth7gD0/T7dYEOnk41I/AAAAAAAAJgo/mg8B7BnJgyk/s1600/27.png


22/34

Choose the New button
http://2.bp.blogspot.com/-uZrREUMRgr8/T7dolSRwRHI/AAAAAAAAJhk/LAXwZAyUHwk/s1600/32.pnghttp://3.bp.blogspot.com/-TPc29cOCoYw/T7dYplWxAWI/AAAAAAAAJg4/dtnhBFRIac8/s1600/28.pnghttp://2.bp.blogspot.com/-uZrREUMRgr8/T7dolSRwRHI/AAAAAAAAJhk/LAXwZAyUHwk/s1600/32.pnghttp://3.bp.blogspot.com/-TPc29cOCoYw/T7dYplWxAWI/AAAAAAAAJg4/dtnhBFRIac8/s1600/28.png


23/34

Enter a name for the solution and your customer number. Choose Continue. The Solution has now

been created.

Create a new Logical Component

Note: this step is only applicable if no existing Logical Component is available to which the new

monitored system can be added.

SAP Solution Manager uses Logical Components to group the role sof systems of a specific product and

version into a business function. For instance, multiple productive R/3 systems might exist in an

organization for various business units. The concept of logical components support the option of

creating different logical components for the general SAP product R/3 for various business units.

It is recommended to use only your own (custom) logical components, instead of the SAP delivered

ones.

Creation of the Logical Component

To create a new Logical component, proceed as follows: In the Solution Manager, call transaction SMSY.


24/34

In the transaction SMSY, click on Solution Groups and Logical Components. Expand the Logical

Components tree.

Expand the product and component to which the monitored system should be assigned and right click

the entry. Choose Create Logical Component.
http://1.bp.blogspot.com/-rHOBhBETjZs/T7dpLhO4HZI/AAAAAAAAJhs/cmLAQVD066I/s1600/34.png


25/34

Choose the Product and Product version of the new system and name the Logical Component. It is

recommended to use Z_ as a prefix for customer defined logical components.

The new Logical Component has now been created.

Assign the Logical Component to a Solution
http://2.bp.blogspot.com/-kZEfxKZn9cY/T7dpnlYGsaI/AAAAAAAAJh0/QNUyS56w2qM/s1600/35.pnghttp://1.bp.blogspot.com/-w78FP7u9QtM/T7dseP44eSI/AAAAAAAAJic/tGvHUJv30UM/s1600/45.PNGhttp://2.bp.blogspot.com/-kZEfxKZn9cY/T7dpnlYGsaI/AAAAAAAAJh0/QNUyS56w2qM/s1600/35.pnghttp://1.bp.blogspot.com/-w78FP7u9QtM/T7dseP44eSI/AAAAAAAAJic/tGvHUJv30UM/s1600/45.PNG


26/34

Now the Logical Component has been defined, it should be assigned to the Solution to which the

monitored system should be added.

In the Solution Manager, call transaction SOLUTION_MANAGER.

This shows the landscape definition in relation to the logical components that are used to define the

landscape. If no logical component exists for the new system, choose a new logical component from the

input help
http://4.bp.blogspot.com/-nhH5Pgj_9RA/T7drK24jYBI/AAAAAAAAJiU/a38z0qP7dog/s1600/36.png


27/34

Expand the Logical Component tree to the one created in the previous chapted. Put a check before it

and choose Transfer. Note that the one used in this example has a different name from the one

created in the previous section

.

Choose Save to save the changes to the Solution.
http://1.bp.blogspot.com/-sApomgE6Q4U/T7dqQOWlpAI/AAAAAAAAJiM/oGz6bsDRJno/s1600/38.pnghttp://4.bp.blogspot.com/-jPwGandsiNY/T7dp-U-tcUI/AAAAAAAAJiE/AjurrFGQAiU/s1600/37.pnghttp://1.bp.blogspot.com/-sApomgE6Q4U/T7dqQOWlpAI/AAAAAAAAJiM/oGz6bsDRJno/s1600/38.pnghttp://4.bp.blogspot.com/-jPwGandsiNY/T7dp-U-tcUI/AAAAAAAAJiE/AjurrFGQAiU/s1600/37.png


28/34

The new Logical Component has now been assigned to the Solution.

Add the system to a Solution by assigning it to a Logical Component

As now both a Solution and a Logical Component exist to which the monitored system can be

assigned, and the Solution and Logical Component have already been linked, assigning the

monitored system to the Solution is a matter of assigning it to the Logical Component. This section

describes how to perform this action.

In transaction SMSY, open the System Groups and Logical Components

Solution Landscapes

section. Choose the Solution where the system is to be added. From previous step, a Logical

Component should already be assigned. Now, these logical components are assigned systems.

First, right click under each System Role field and choose Put in Solution. Dothis for instance for

Development System, Quality Assurance System and Production System. This determines that

systems for these logical components will be assigned

Now, select the row containing the Logical Component and choose Change Logical Component.
http://1.bp.blogspot.com/-TrOoYzn_-Uw/T7dtLf_2oqI/AAAAAAAAJik/DGwGeVpymsA/s1600/39.png


29/34

This shows the definition for the logical component and in particular the current system assignments.

It is here that using input help that for each of the System Roles a system can be assigned
http://2.bp.blogspot.com/-EPu43W5quzY/T7dttx4eBfI/AAAAAAAAJi0/fsL9avbK040/s1600/41.pnghttp://3.bp.blogspot.com/-Mqq2fzT861k/T7dtjeHTjqI/AAAAAAAAJis/zORtu8JuiIs/s1600/40.pnghttp://2.bp.blogspot.com/-EPu43W5quzY/T7dttx4eBfI/AAAAAAAAJi0/fsL9avbK040/s1600/41.pnghttp://3.bp.blogspot.com/-Mqq2fzT861k/T7dtjeHTjqI/AAAAAAAAJis/zORtu8JuiIs/s1600/40.png


30/34

Choose Save to have the Solution landscape altered to the new assignment. Logs will be displayed

about the progress.

The new system is added to the Solution Landscape
http://1.bp.blogspot.com/-jHBuVCzi-xk/T7dt_yNiNZI/AAAAAAAAJjE/edfAAeQBcoM/s1600/43.pnghttp://3.bp.blogspot.com/-iVtVKXdsNm0/T7dt47kvS1I/AAAAAAAAJi8/ZwnnWoAU_9o/s1600/42.pnghttp://1.bp.blogspot.com/-jHBuVCzi-xk/T7dt_yNiNZI/AAAAAAAAJjE/edfAAeQBcoM/s1600/43.pnghttp://3.bp.blogspot.com/-iVtVKXdsNm0/T7dt47kvS1I/AAAAAAAAJi8/ZwnnWoAU_9o/s1600/42.png


31/34


32/34

Note: its wise to delete this file once it is no longer required.

Create a Solution

Note: this step is only required if no Solution exists that the monitored system can be assigned to.

SAP Solution Manager organizer systems into Solutions. Various strategies for system organization exist:

i.e. based on status (productive/non-productive), component (CRM/ERP/BW/etc) or Business unit (i.e.

Poort, Commerce, etc.). This sections describes how to create a Solution, not define a strategy for the

types of Solutions that should be defined (see for that the Solution Manager architecture document).

On the Solution Manager, call transaction SOLUTION_MANAGER.

A list of available Solutions is shown. Note: the list can be empty if no prior Solutions exist.

Adding SAP System to Solution Manager step by step

This one very long post, request you to fallow the steps to add the sytsem in solman. This Post describes

the steps that are required to...
http://sapbasistechnical.blogspot.in/2012/05/attach-sap-system-to-solution-manager.htmlhttp://1.bp.blogspot.com/-06bnluYkrCE/T7doI7lSJVI/AAAAAAAAJhc/JLftN4-86m4/s1600/31.pnghttp://1.bp.blogspot.com/-hYHNe2rjajg/T7dZeHY7VQI/AAAAAAAAJhQ/lbGnXCOlG-M/s1600/30.pnghttp://1.bp.blogspot.com/-06bnluYkrCE/T7doI7lSJVI/AAAAAAAAJhc/JLftN4-86m4/s1600/31.pnghttp://1.bp.blogspot.com/-hYHNe2rjajg/T7dZeHY7VQI/AAAAAAAAJhQ/lbGnXCOlG-M/s1600/30.pnghttp://sapbasistechnical.blogspot.in/2012/05/attach-sap-system-to-solution-manager.html


33/34

SAP Kernal upgrade on Linux Step by Step

I am doing SAP Kernel upgrade on Net weaver 7.3 version. Login to sap system and click on system

status button will show the below scr...

Solution Manager EarlyWatch Alert Setup for ABAP Systems

EarlyWatch Alert generation is a service provided by the SAP Solution Manager that provides technicalinsight in the operation of SAP syste...

BW ABAP upgrade to EHP Step by Step

Enhancement Pack 1 Installation on Netweaver 7.0 Systems BW ABAP 1 Introduction This Procedure

describes the steps to apply the Enhan...

PI SXMB_MONI Monitoring Workinstructions

Message monitoring in the IE Use transaction SXMB_MONI to monitor the messages. Monitor for

Processed XML Messages Tr...

Language installation on SAP systems - Step by Step
http://sapbasistechnical.blogspot.in/2012/05/sap-kernal-upgrade-on-linux-step-by.htmlhttp://sapbasistechnical.blogspot.in/2012/05/solution-manager-earlywatch-alert-setup.htmlhttp://sapbasistechnical.blogspot.in/2011/11/bw-abap-upgrade-to-ehp-step-by-step.htmlhttp://sapbasistechnical.blogspot.in/2011/12/pi-sxmbmoni-monitoring-workinstructions.htmlhttp://sapbasistechnical.blogspot.in/2012/04/sap-language-installation.htmlhttp://sapbasistechnical.blogspot.in/2012/04/sap-language-installation.htmlhttp://sapbasistechnical.blogspot.in/2011/12/pi-sxmbmoni-monitoring-workinstructions.htmlhttp://sapbasistechnical.blogspot.in/2011/11/bw-abap-upgrade-to-ehp-step-by-step.htmlhttp://sapbasistechnical.blogspot.in/2012/05/solution-manager-earlywatch-alert-setup.htmlhttp://sapbasistechnical.blogspot.in/2012/05/sap-kernal-upgrade-on-linux-step-by.htmlhttp://sapbasistechnical.blogspot.in/2012/04/sap-language-installation.htmlhttp://sapbasistechnical.blogspot.in/2011/12/pi-sxmbmoni-monitoring-workinstructions.htmlhttp://sapbasistechnical.blogspot.in/2011/11/bw-abap-upgrade-to-ehp-step-by-step.htmlhttp://sapbasistechnical.blogspot.in/2012/05/solution-manager-earlywatch-alert-setup.htmlhttp://sapbasistechnical.blogspot.in/2012/05/sap-kernal-upgrade-on-linux-step-by.htmlhttp://sapbasistechnical.blogspot.in/2012/04/sap-language-installation.htmlhttp://sapbasistechnical.blogspot.in/2011/12/pi-sxmbmoni-monitoring-workinstructions.htmlhttp://sapbasistechnical.blogspot.in/2011/11/bw-abap-upgrade-to-ehp-step-by-step.htmlhttp://sapbasistechnical.blogspot.in/2012/05/solution-manager-earlywatch-alert-setup.htmlhttp://sapbasistechnical.blogspot.in/2012/05/sap-kernal-upgrade-on-linux-step-by.htmlhttp://sapbasistechnical.blogspot.in/2012/04/sap-language-installation.htmlhttp://sapbasistechnical.blogspot.in/2011/12/pi-sxmbmoni-monitoring-workinstructions.htmlhttp://sapbasistechnical.blogspot.in/2011/11/bw-abap-upgrade-to-ehp-step-by-step.htmlhttp://sapbasistechnical.blogspot.in/2012/05/solution-manager-earlywatch-alert-setup.htmlhttp://sapbasistechnical.blogspot.in/2012/05/sap-kernal-upgrade-on-linux-step-by.htmlhttp://sapbasistechnical.blogspot.in/2012/04/sap-language-installation.htmlhttp://sapbasistechnical.blogspot.in/2011/12/pi-sxmbmoni-monitoring-workinstructions.htmlhttp://sapbasistechnical.blogspot.in/2011/11/bw-abap-upgrade-to-ehp-step-by-step.htmlhttp://sapbasistechnical.blogspot.in/2012/05/solution-manager-earlywatch-alert-setup.htmlhttp://sapbasistechnical.blogspot.in/2012/05/sap-kernal-upgrade-on-linux-step-by.htmlhttp://sapbasistechnical.blogspot.in/2012/04/sap-language-installation.htmlhttp://sapbasistechnical.blogspot.in/2011/12/pi-sxmbmoni-monitoring-workinstructions.htmlhttp://sapbasistechnical.blogspot.in/2011/11/bw-abap-upgrade-to-ehp-step-by-step.htmlhttp://sapbasistechnical.blogspot.in/2012/05/solution-manager-earlywatch-alert-setup.htmlhttp://sapbasistechnical.blogspot.in/2012/05/sap-kernal-upgrade-on-linux-step-by.html


34/34

The language environment that comes with the standard SAP installation includes German and English.

To use SAP with other languages, you mu...

Using DPMON: Work Process Monitoring

At times when you are unable to login to R/3 system for various reasons, a tool named dpmon is used to

get the process overview of an insta...

JSPMJava Support Pack Manager

Check whether the used JDK version and the Java VM settings of the Java runtime system comply

with the requirements in the SAP Note 7239...

TRFC Hanging queues in SMQ1 and SMQ2

To monitor the outbound queues start SMQ1 , the inbound queues can be monitored using SMQ2 SMQ1

SMQ2 1. Select all appearing queue...

Monitor background job status centrally using SOLMAN...without an external scheduling tool

Monitor background job status centrally using SOLMAN. No external scheduling tool requiredOpen Solution Manager, You call the Work ...
http://sapbasistechnical.blogspot.in/2012/04/using-dpmon-work-process-monitoring.htmlhttp://sapbasistechnical.blogspot.in/2012/06/jspm-java-support-pack-manager.htmlhttp://sapbasistechnical.blogspot.in/2012/06/jspm-java-support-pack-manager.htmlhttp://sapbasistechnical.blogspot.in/2012/06/jspm-java-support-pack-manager.htmlhttp://sapbasistechnical.blogspot.in/2012/08/hanging-queues-in-smq1-and-smq2.htmlhttp://sapbasistechnical.blogspot.in/2011/11/monitor-background-job-status-centrally.htmlhttp://sapbasistechnical.blogspot.in/2011/11/monitor-background-job-status-centrally.htmlhttp://sapbasistechnical.blogspot.in/2012/08/hanging-queues-in-smq1-and-smq2.htmlhttp://sapbasistechnical.blogspot.in/2012/06/jspm-java-support-pack-manager.htmlhttp://sapbasistechnical.blogspot.in/2012/04/using-dpmon-work-process-monitoring.htmlhttp://sapbasistechnical.blogspot.in/2011/11/monitor-background-job-status-centrally.htmlhttp://sapbasistechnical.blogspot.in/2012/08/hanging-queues-in-smq1-and-smq2.htmlhttp://sapbasistechnical.blogspot.in/2012/06/jspm-java-support-pack-manager.htmlhttp://sapbasistechnical.blogspot.in/2012/04/using-dpmon-work-process-monitoring.htmlhttp://sapbasistechnical.blogspot.in/2011/11/monitor-background-job-status-centrally.htmlhttp://sapbasistechnical.blogspot.in/2012/08/hanging-queues-in-smq1-and-smq2.htmlhttp://sapbasistechnical.blogspot.in/2012/06/jspm-java-support-pack-manager.htmlhttp://sapbasistechnical.blogspot.in/2012/04/using-dpmon-work-process-monitoring.htmlhttp://sapbasistechnical.blogspot.in/2011/11/monitor-background-job-status-centrally.htmlhttp://sapbasistechnical.blogspot.in/2012/08/hanging-queues-in-smq1-and-smq2.htmlhttp://sapbasistechnical.blogspot.in/2012/06/jspm-java-support-pack-manager.htmlhttp://sapbasistechnical.blogspot.in/2012/04/using-dpmon-work-process-monitoring.htmlhttp://sapbasistechnical.blogspot.in/2011/11/monitor-background-job-status-centrally.htmlhttp://sapbasistechnical.blogspot.in/2012/08/hanging-queues-in-smq1-and-smq2.htmlhttp://sapbasistechnical.blogspot.in/2012/06/jspm-java-support-pack-manager.htmlhttp://sapbasistechnical.blogspot.in/2012/04/using-dpmon-work-process-monitoring.html

Date post:	04-Jun-2018
Category:	Documents
Upload:	rampyks
View:	217 times
Download:	0 times

Add Sys to Solman 7.0

Documents