Skip to end of metadata
Go to start of metadata

All scenarios in SAP Solution Manager depend on the correct modelling of system information in the landscape databases. In a typical scenario, the technical system aut. reports information about itself to the productive SLD. As of SAP Solution Manager 7.1, technical system information from ideally one or several SLDs is synchronized with the new Landscape Management Database (LMDB), which replaces TA SMSY, in SAP Solution Manager.
Ususally, the tech. systems report installed product versions and product instances (available with newer SAP NetWeaver installations) to LMDB.
If no product versions and product instances are reported, this page shows you how to model different products in the LMDB of SAP Solution Manager.
Also see the Maintenance Planning Guide for SAP Solution Manager 7.1 SP5 ff.
Some very specific examples of product modeling are described in the guide Special Cases in Installation and Upgrade (adding Portal content to SAP NW, SAP SEM, update to SAP NW 7.3 hub, IDM ...).

Generic Maintenance Information for Technical Systems in SAP Solution Manager 7.1

When talking about system in the context of SAP Solution Manager, you have to distinguish between Technical Systems and Product Systems. The term Technical System describes an entity that is installed standalone or as cluster on one or several hosts in order to get a an application running. It is more or less a technical description of the installation. Whereas a Product System represents the complete product that has been installed. It consists of one or more Technical Systems assigned via the relevant product instances. In LMDB, you product instances are marked as installed on technical systems. Then you can assign technical systems and product systems to product systems. The focus of this Wiki is to provide the information how to maintain Technical Systems correctly.

For more information, see

Use transaction LMDB in the SAP Solution Manager system for a direct access of the technical system or product system editors.

Generic Rules for product assignment

As general rule you should first check in the products section regarding the product you want to set up with your Technical System. Depending on the fact whether the affected Technical System has been created automatically via SLD content synchronization to Solution Manager or manually there are different rules for product assignment. Here is a rough overview by supported system type and how Technical Systems of each type need to be created with or without product information:

  • Application Server ABAP: Technical Systems are created automatically via SLD content synchronization. For Technical Systems running on a Netweaver version prior 7.02 the product version and product instance information is not provided and need to be added with the Managed System Setup. In case the SAP Solution Manager has been upgraded from version 7.0 to 7.1 and the affected ABAP system has been created during the data migration from SMSY the product information need also to be added manually in the Managed System Setup.
  • Application Server Java: Technical Systems of type Application Server Java are also created automatically via SLD content synchronization. Similar to type AS ABAP the product version and product instance information need to be maintained manually for all Technical Systems running on Netweaver prior 7.02.
  • Apache Tomcat Server: For this system type exists an SLD data supplier. Depending on the application and its version the product version, product instance and software component version information is also provided with SLD content synchronization.
  • Business Objects Cluster: All Technical Systems of type Business Objects Cluster are created via SLD data supplier and synchronized to the Solution Manager LMDB containing the complete set of product information.
  • liveCache: For releases 640 SPS23, 700 SPS17, 701, 702, 710 SPS07 and higher the Technical System is created automatically but the product information need to added during the Managed System Setup. For lower releases the complete Technical System has to be created manually with the Technical System Editor.
  • Master Data Management Server: All Technical Systems of type Master Data Management Server need to be created manually including the installed software information.
  • Microsoft Internet Information Services: The Technical System is created automatically in the LMDB but the product information need to be added manually during the Managed System Setup.
  • .Net System: Depending on the application the Technical System is created automatically including the product information or need to be created manually with the Technical System Editor
  • TREX System: For TREX systems a data supplier exists but it is necessary to maintain the product information.
  • Unspecific Standalone Application System: Unspecific Standalone Application System type is used for those Technical Systems which are not described by any of the other types and can exclusively installed on a single host without any clustering. Depending on the application the Technical System is created automatically including the product information or need to be created from scratch with the Technical System Editor.
  • Unspecific Cluster System: Technical Systems which are not described by any of the other system types and could be installed in a cluster need to be created as type Unspecific Cluster System. Similar to the type Unspecific Standalone Application System they are created automatically via SLD data supplier including all product information or need to be created manually.
  • Web Dispatcher: Web Dispatcher systems are created automatically via SLD data supplier but the product information need to be enhanced during the Managed System Setup.
  • IBM WebSphere Cell: The Technical System is created automatically via SLD data supplier and synchronized to the Solution Manager and depending on the application running on WebSphere it is necessary to maintain the product information during the Managed System Setup.

SAP Product and Solutions

SAP Solution Manager

Supported Versions?

SAP SOLUTION MANAGER 7.0, SAP SOLUTION MANAGER 7.0 EHP 1,
SAP SOLUTION MANAGER 7.1

Automatic creation of Technical System?

Yes
Two Technical Systems are created - Application Server
ABAP and Application Server Java

Automatic entry of installed software?

Partly
For both Technical Systems installed software components
are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP SOLUTION MANAGER 7.0

Solution Manager ABAP Stack

AS ABAP

Yes

 

 

Solution Manager JAVA Stack

AS Java

Yes

 

SAP SOLUTION MANAGER 7.0 EHP 1

Solution Manager ABAP Stack

AS ABAP

Yes

 

 

Solution Manager JAVA Stack

AS Java

Yes

 

SAP SOLUTION MANAGER 7.1

Solution Manager ABAP Stack

AS ABAP

Yes

 

 

Solution Manager JAVA Stack

AS Java

Yes

 

SAP SOLUTION MANAGER 7.1 on HANA
(* restricted availability)

Solution Manager ABAP Stack

AS ABAP

Yes

 

 

Solution Manager JAVA Stack

AS Java

Yes

 

Enterprise Portal

Supported Versions?

SAP NETWEAVER 04, SAP NETWEAVER 7.0, SAP EHP1 FOR SAP NETWEAVER 7.0

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server Java

Automatic entry of installed software?

Partly
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER 04

Enterprise Portal

AS Java

Yes

 

SAP NETWEAVER 7.0

Enterprise Portal

AS Java

Yes

 

SAP EHP1 FOR SAP NETWEAVER 7.0

Enterprise Portal

AS Java

Yes

 

CRM

Supported Versions?

SAP CRM 4.0, SAP CRM 5.0, SAP CRM 5.2,
SAP CRM 2007, SAP CRM 7.0, SAP CRM 7.0/NW7.01, EHP1 FOR SAP CRM 7.0

Automatic creation of Technical System?

Yes
Two Technical Systems are created - Application Server
ABAP and Application Server Java

Automatic entry of installed software?

Partly
For both Technical Systems installed software components
are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP CRM 4.0

CRM Application Server ABAP

AS ABAP

Yes

 

 

CRM IC Webclient_640

AS Java

Yes

Produc Instances to be selected on
system type AS Java are dependent on CRM scenario

 

CRM ICS WFM CS_640

AS Java

Yes

 

 

CRM Intelligence Connector_640

AS Java

Yes

 

 

IPC Web Applications_640

AS Java

Yes

 

 

E-Selling_640

AS Java

Yes

 

 

CRM_ICSS_640

AS Java

Yes

 

SAP CRM 5.0

CRM Application Server ABAP

AS ABAP

Yes

 

 

CRM Application Server Java

AS Java

Yes

 

 

Mapbox

AS Java

Yes

 

SAP CRM 5.2

CRM Application Server ABAP

AS ABAP

Yes

 

 

CRM Application Server Java

AS Java

Yes

 

SAP CRM 2007

CRM Application Server ABAP

AS ABAP

Yes

 

 

CRM Application Server Java

AS Java

Yes

 

SAP CRM 7.0

CRM Application Server ABAP

AS ABAP

Yes

 

 

CRM Application Server Java

AS Java

Yes

 

SAP CRM 7.0/NW7.01

CRM Application Server ABAP

AS ABAP

Yes

 

 

CRM Application Server Java

AS Java

Yes

 

EHP1 FOR SAP CRM 7.0

CRM Application Server ABAP

AS ABAP

Yes

 

 

CRM Application Server Java

AS Java

Yes

 

SAP ERP 6.0 & EhPx for ERP 6.0

Supported Versions?

SAP ERP 6.0 & EhPx for ERP 6.0

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server ABAP

Automatic entry of installed software?

Partly
Installed software components  are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP ERP 6.0

ECC Server

AS ABAP

Yes

 

EhPx for ERP 6.0

ABAP Technology for ERP EHP

AS ABAP

Yes

 

EhP5 for SAP ERP 6.0

EHP5 FOR SAP ERP 6.0: Central Applications

AS ABAP

Yes

 

REMARK:

It is also possible to treat ERP as a typical SAP NetWeaver installation and assign additionally the product instances which are relevant for the installed basis release of SAP NetWeaver. Please refer to the section on SAP NetWeaver ABAP / J2EE

SAP NetWeaver TREX

To publish TREX to the Landscape Directory (SLD), please follow the instructions in SAP Notes:

1147499  "Connection to the System Landscape Directory" → TREX

1018839  "Registering in the System Landscape Directory using sldreg"

http://help.sap.com/saphelp_nw70/helpdata/EN/42/e33ae230ba3ee2e10000000a1553f6/frameset.htm

Supported Versions?

SAP NETWEAVER 7.0, SAP NETWEAVER 7.3

Automatic creation of Technical System?

Yes
Technical Systems are created of type
TREX System

Automatic entry of installed software?

Partly
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually according to the software component of TREX.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER 7.0

Search and Classif. (TREX)

TREX System

Yes

TREX 7.0

SAP NETWEAVER 7.3

Search and Classif. (TREX)

TREX System

Yes

TREX 7.1

SRM

Supported Versions?

SAP SRM 5.0, SAP SRM 6.0, SAP SRM 6.0/NW7.01, SAP SAP SRM 7.0, SAP SRM 7.0/NW7.01

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server ABAP

Automatic entry of installed software?

Partly
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP SRM 5.0

SRM Server

AS ABAP

Yes

 

 

CCM with SRM-MDM Catalog

AS Java

Yes

 

SAP SRM 6.0

SRM Server

AS ABAP

Yes

 

 

CCM with SRM-MDM Catalog

AS Java

Yes

 

SAP SRM 6.0/NW7.01

SRM Server

AS ABAP

Yes

 

 

CCM with SRM-MDM Catalog

AS Java

Yes

 

SAP SAP SRM 7.0

SRM Server

AS ABAP

Yes

 

 

CCM with SRM-MDM Catalog

AS Java

Yes

 

SAP SRM 7.0/NW7.01

SRM Server

AS ABAP

Yes

 

 

CCM with SRM-MDM Catalog

AS Java

Yes

 

SCM

Supported Versions?

SAP SCM 5.0, SAP SCM 2007, SAP SCM 7.0, SAP SCM 7.01

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server ABAP

Automatic entry of installed software?

Partly
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually.
Comment: For SCM Add-On Products like SAP SNC, SAP EM, SAP F&R the
basis component (SAP Netweaver Release) has to be also assigned as relevant
Product Instance

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP SCM 5.0

SCM Server

AS ABAP

Yes

 

SAP SCM 2007

SCM Server

AS ABAP

Yes

 

SAP SCM 7.0

SCM Server

AS ABAP

Yes

 

SAP SCM 7.01

SCM Server

AS ABAP

Yes

 

SAP SCM 7.02

SCM Server

AS ABAP

Yes

 

SAP NetWeaver LiveCache / SAP LiveCache

Currently SAP LiveCache is supported mainly for SCM Systems.

Supported Versions?

SAP LiveCache 7.5 / LCA Build 4.1,
SAP LiveCache 7.6 / LCA Builds 5.0,
SAP LiveCache 7.7 / LCA Builds 6.0,
SAP Livecache 7.7 / LCA Builds 7.0,
|

Automatic creation of Technical System?

Yes
Technical Systems are created of type
SAP_LiveCache

Automatic entry of installed software?

Partly
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually.
Comment: During the SetUp for the LiveCache you have to maintain the RFC
Connection to the corresponding ABAP System

 

SAP NetWeaver Process Integration (PI / XI)

Supported Versions?

SAP NETWEAVER 7.0, SAP NETWEAVER PI 7.1, SAP EHP1 FOR SAP NW PI 7.1, SAP NETWEAVER 7.3, SAP EHP1 FOR SAP NETWEAVER 7.3

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server ABAP and Application Server Java.

Automatic entry of installed software?

Partly
Installed software components are automatically reported for all supported product versions. Since SAP Netweaver 7.3 also product version and
instances are reported automatically.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER 7.0

Process Integration

AS ABAP

Yes

Required for Integration Server

 

Process Integration

AS JAVA

Yes

Required for Integration Server and Adapter Engine

SAP NETWEAVER PI 7.1

Process Integration

AS ABAP

Yes

Required for Integration Server

 

Process Integration

AS JAVA

Yes

Required for Integration Server and Adapter Engine

SAP EHP1 FOR SAP NW PI 7.1

Process Integration

AS ABAP

Yes

Required for Integration Server

 

Process Integration

AS JAVA

Yes

Required for Integration Server and Adapter Engine

SAP NETWEAVER 7.3

Process Integration

AS ABAP

Yes

Required for Integration Server in case of dual stack

 

Process Integration

AS JAVA

Yes

Required for Integration Server and Adapter Engine

SAP EHP1 FOR SAP NETWEAVER 7.3

Process Integration

AS ABAP

Yes

Required for Integration Server in case of dual stack

 

Process Integration

AS JAVA

Yes

Required for Integration Server and Adapter Engine

SAP NetWeaver Business Warehouse (BW / BI)

Supported Versions?

SAP NETWEAVER 04, SAP NETWEAVER 7.0, SAP EHPxx FOR SAP NETWEAVER 7.0,
SAP NETWEAVER 7.3, SAP EHPxx FOR SAP NETWEAVER 7.3

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server ABAP and Application Server Java.

Automatic entry of installed software?

Partly
Installed software components are automatically reported for all supported product versions. Since SAP Netweaver 7.3 also product version and
instances are reported automatically.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER 04

Business Intelligence

AS ABAP

Yes

 

SAP NETWEAVER 7.0

Business Intelligence

AS ABAP

Yes

 

 

BI Java

AS JAVA

Yes

 

SAP EHPxx FOR SAP NETWEAVER 7.0

Business Intelligence

AS ABAP

Yes

 

 

BI Java

AS JAVA

Yes

 

SAP NETWEAVER 7.3

Business Intelligence

AS ABAP

Yes

 

 

BI Java

AS JAVA

Yes

 

SAP EHPxx FOR SAP NETWEAVER 7.3

Business Intelligence

AS ABAP

Yes

 

 

BI Java

AS JAVA

Yes

 

SAP Business Objects Data Services

Supported Versions?

SBOP DATA SERVICES 4.0, SBOP DATA SERVICES 4.1, SBOP DATA SERVICES 4.2

Automatic creation of Technical System?

Yes
Technical Systems are created of type Unspecific Cluster System.

Automatic entry of installed software?

Partly
Installed software components are automatically reported for all supported product versions. 
The host OS information need to be added manually.




 

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SBOP DATA SERVICES 4.0

Access Server

Unspecific Cluster System

Yes

 

 

Job Server

Unspecific Cluster System

Yes

 

SAP DATA SERVICES 4.1

Access Server

Unspecific Cluster System

Yes

 

 

Job Server

Unspecific Cluster System

Yes

 

SAP DATA SERVICES 4.2

Access Server

Unspecific Cluster System

Yes

 

 

Job Server

Unspecific Cluster System

Yes

 


Note: 

Please implement the Note 1817324 for known bugs. 

For the Data Services 4.1 extractor before solman 7.1 SP10, please apply note 1851663.

For system monitoring, due to the wily introscope bug, job server CPU and Memory performance alert will not be available until the customer apply the following patch Data Services 4.2 SP1 patch1 or Data Services 4.1 SP2 patch1.

For Data Services CV template before solman 7.1 SP10, please apply note
SP05: 1783884 SP06: 1783885 SP07: 1783886 SP08: 1811700 SP09: 1882778

For Data Services missing RCA extractor, please apply note 1908459 

For Config.xml(effected on workload analysis) in solution manager for Data Services 4.0, 4.1 and 4.2, please implement the latest Config.xml via note 1259109, we will update the Config.xml regularly for every solman SP, and this note is available from solman 7.1 SP5. 

And please implement note 157974 to your Enterprise Manager to deploy the most recently management modules, by which we get most recently Data Services metrics in Enterprise Manager.

Confirm the NCS feature is enabled on every Data Services system that you wanna monitor, it could be enabled via Data Services server manager.

Confirm the Data Services system payload file has been uploaded into SLD.

Note : For Data Services cluster situation:

  1. Rule of thumb, use the unique Job Server and Access Server name in your cluster.
    For Job Server, we would recommend you to use the name format like <hostname>_<jobservername>
    For Access Server, please make sure all Access Servers in your landscape are using unique service communication port even they are on different host.
  2. Before Data Services version 14.1.2.475 and 14.2.1.141, you have to change and upload the payload file to SLD on all related servers (more details please refer to the note 1852508),  or you can choose to upgrade your Data Services to the versions 14.1.2.475 and 14.2.1.141 or above;
  3. While your Data Services version is or above 14.1.2.475 and 14.2.1.141, without changing the content of DS auto-generated payload file manually, you just need to update the DSConfig.txt on both servers of this Data Services cluster which you can find in the folder <DS_COMMON_DIR>\conf or <DS_USER_DIR>\conf, such as "C:\ProgramData\SAP BusinessObjects\Data Services\conf", before upload payload file to the SLD, the details is as follows:
     

    e.g. While you have a Data Services cluster, and the server names are A(Host server name) and B, and we assume the A is the main instance, then you need to find the DSConfig.txt file on both A and B and update them by adding the AL_JobService option:

     

     

     

                 Server A insert the option:

     

                 [AL_JobService]

     

                 CentralHostForSLD = localhost (or A)

     

                 SystemIDForSLD = DSX (the cluster's SID in managing system)

     

     

     

                 Server B insert the option:

     

                 [AL_JobService]

     

                 CentralHostForSLD = A (host server name)

     

                 SystemIDForSLD = DSX (the cluster's SID in managing system)

     
    • After update the DSConfig.txt file, you need to confirm whether your change has taken effect, the methods :
     
      1. On server B, add a job server (named "jobserver_clustertest" for example) that connect to A's one existing repository (named "Repo_Cluster" for example), and then close and restart in the Data Services server manager, go to check the new auto-generated payload file to check whether the host name in the payload file has been changed into A and the property "merge_properties" = false has been changed to "true", more details please refer to the note 1852508, if not redo and recheck your update DSConfig.txt file and your DS version, if yes then you can add an AccessServer, the AccessServer's  directory can be aimed to B's local folder, after finish, close and restart in the Data Services Server manager;
      2. After the restart, on server A, log on the repository "Repo_Cluster", use the job server "jobserver_clustertest" to run a job, all are succeed, go to the server B, Logon the same repository and run a job with the same job server, if still succeed, after confirm the payload file's correctness(refering to note 1817324 <bug1 and bug3>), you can upload the payload file and check the unique SID in solman of this server cluser A&B.

  4. More details, please refer to note 1852508. 

           

For SLD detail, please refer to note 1018839. Here are some Data Services specific parts:

1. You could find the sldreg.exe under Host Agent 'exe' folder.

2. After generating slddest.cfg and slddest.cfg.key file, please copy the 2 files to <LINK_DIR>\sldreg\ folder, and run sld_ds.bat/sld_ds.sh in the folder, the payload flle will be uploaded into SLD automatically everytime landscape changed in Data Services system.

3. If you want to disable the automatically upload function, remove the slddest.cfg and slddest.cfg.key file from <LINK_DIR>\sldreg\ folder after running sld_ds.bat/sld_ds.sh.

Confirm that you have installed SMD agent and Host Agent on Data Services server that you want to monitor, if in cluster situation, you  have to install the agents on all related servers. For installing SMD agent and Host Agent, please refer to note: 1031096 and 1365123.

Confirm installation path and instance log path for every Data Services instance in Manager System Setup step 5 Enter Landscape Parameter.

Here there are two metrics for Job Server need to be maintained, one is the "Installation Path" and the other is "Instance Log Path" as the picture shows:

       Installation Path: shall enter the value of <DS_COMMON_DIR> or <DS_USER_DIR> which represent the default or user specified Data Services configuration directory.

       Instance Log Path: shall enter the value of <DS_COMMON_DIR>/log/<JobServerName> or <DS_USER_DIR>/log/<JobServerName> or other directory you specified to store the job server's logs. 

For example:

By default, the instance log path of SBOP DS JOB SERVER 4.0 is C:\Program Files (x86)\SAP BusinessObjects\Data Services\log\JobServer\, in case the customer install Data Services in other directory rather than  C:\Program Files (x86)\SAP BusinessObjects\Data Services\, please change the path accordingly. The “JobServer” is Data Service Job Server instance name which is defined by customer. Usually Data Services 4.0 has more than one Job Server instance with different names, which means you need to type each Job Server instance name manually in instance log path.

For SBOP DS JOB SERVER 4.1, the default instance log path will be C:\ProgramData\SAP BuinessObject\Data Services\JobServer.

As all the configuration directory of Data Services or logs' store directory can be specified by users, so you need to check the directory before set up the parameters.

By default, the instance log path of SBOP DS ACCESS SERVER 4.0 is C:\Program Files (x86)\SAP BusinessObjects\Data Services\bin\AccessServer_X, in case the customer install Data Services in other directory rather than  C:\Program Files (x86)\SAP BusinessObjects\Data Services\, please change the path accordingly. While the "AccessServer_X” is Access Server instance name which is defined by customer, also one Data Services could have more than one Access Server. And what’s more, the whole log path is defined by customer, so you need to type each Access Server instance log path manually in instance log path.

In Agent Application panel, choose com.sap.smd.agent.application.remoteos, select the agent in Scope. Add the value of the variable: 

ENV_SID_'extend SID' _BOE_DIR with the right path of <BOE_DIR> in the agent setup, by default, it should be C:\Program Files (x86)\SAP BusinessObjects.

ENV_SID_'extend SID' _BOE_AUTH_TYPE with 'secEnterprise'.

ENV_SID_'extend SID' _BOE_CMS with BOE CMS server and port that the DS is registered in.

ENV_SID_'extend SID' _BOE_CMS_USR with BOE CMS user.

ENV_SID_'extend SID' _BOE_CMS_PWD with BOE CMS user password.

ENV_SID_'extend SID' _BOE_WEB_PORT with BOE web server port.

ENV_SID_'extend SID' _BOE_WEB_HOST (optional) with the host name of the web server installed, this is only added while the web server and BOE /DS not installed on the same server.

ENV_SID_'extend SID' _DS_CONFIG_DIR with the Data Services configuration directory <DS_COMMON_DIR> or <DS_USER_DIR>.
   
In Agent Application panel, choose com.sap.smd.agent.application.wilyhost, select the SapAgentConfig.xml and agent in Scope. Upload the xml file with following content.

<?xml version="1.0" encoding="UTF-8" ?>

<sapagent>

  <destination class="com.sap.smd.wily.hostagent.destination.SocketDestination" name="Port59818">

  <property name="port" value="59818"/>

  </destination>

  <pool>

  <action prefix="" name="TCP_59818" destination="Port59818" template="SapMDM"/>

  <action prefix="BODS|SAP_DS" name="ds_workload" class="com.sap.smd.wily.hostagent.action.RemoteOsCommandAction" period="3600000">

  <property name="commandkey" value="ds.cat" />

  <property name="longsid" value="DSS" />

  </action>

  </pool>

</sapagent>

Note that the port 59818 is the default NCS port number, you could change the port in ncs.conf file on Data Services server, and "DSS" is the extend SID of Data Services in Solution Manager, you have to change it accordingly. 
Please also implement SAP Note 1618486 for additional Workload metrics in Wily Introscope and Solution manager.

Moreover, if you still want to do BI Monitoring, you should also need to change the Data Services Application Settings in CMC, the details is as follows, find "Settings" : BOE\CMC -> Application -> Data Services Application -> Settings, change the value of History Retention Period to a small number, maybe "1" or "2". The followin picture shows the content:

SAP BusinessObjects Enterprise

Supported Versions?

BOBJ ENTERPRISE XI 3.0, BOBJ ENTERPRISE XI 3.1, SBOP BI PLATFORM 4.0

Automatic creation of Technical System?

Partly
Technical Systems for SBOP BI PLATFORM 4.0 are created automatically of type Business Objects Cluster.
Technical Systems for BOBJ ENTERPRISE XI 3.0 and 3.1 are created manually of type Unspecific Cluster System.

Automatic entry of installed software?

Partly
Installed software components are automatically reported for SBOP BI PLATFORM 4.0. 
For BOBJ ENTERPRISE XI 3.0 and 3.1, both product version, product instance and installed software components
are created manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

BOBJ ENTERPRISE XI 3.0

JOB SERVER

Unspecific Cluster System

Yes

 

 

REPORT APPLICATION SERVER

Unspecific Cluster System

Yes

 

 

MULTIDIMENSIONAL ANALY. SERVER

Unspecific Cluster System

Yes

 

 

CENTRAL MANAGEMENT SERVER

Unspecific Cluster System

Yes

 

 

CRYSTAL REPORTS SERVER

Unspecific Cluster System

Yes

 

 

DESKTOP INTELLIGENCE SERVER

Unspecific Cluster System

Yes

 

 

WEB INTELLIGENCE SERVER

Unspecific Cluster System

Yes

 

 

INPUT FILE REPOSITORY SERVER

Unspecific Cluster System

Yes

 

 

EVENT SERVER

Unspecific Cluster System

Yes

 

 

OUTPUT FILE REPOSITORY SERVER

Unspecific Cluster System

Yes

 

 

WEB APP CONTAINER SERVER

Unspecific Cluster System

 

 

 

ADAPTIVE PROCESSING SERVER

Unspecific Cluster System

Yes

 

 

ADAPTIVE JOB SERVER

Unspecific Cluster System

Yes

 

 

SERVER INTELLIGENCE AGENT

Unspecific Cluster System

Yes

 

 

CONNECTION SERVER

Unspecific Cluster System

Yes

 

BOBJ ENTERPRISE XI 3.1

JOB SERVER

Unspecific Cluster System

Yes

 

 

REPORT APPLICATION SERVER

Unspecific Cluster System

Yes

 

 

MULTIDIMENSIONAL ANALY. SERVER

Unspecific Cluster System

Yes

 

 

CENTRAL MANAGEMENT SERVER

Unspecific Cluster System

Yes

 

 

CRYSTAL REPORTS SERVER

Unspecific Cluster System

Yes

 

 

DESKTOP INTELLIGENCE SERVER

Unspecific Cluster System

Yes

 

 

WEB INTELLIGENCE SERVER

Unspecific Cluster System

Yes

 

 

INPUT FILE REPOSITORY SERVER

Unspecific Cluster System

Yes

 

 

EVENT SERVER

Unspecific Cluster System

Yes

 

 

OUTPUT FILE REPOSITORY SERVER

Unspecific Cluster System

Yes

 

 

WEB APP CONTAINER SERVER

Unspecific Cluster System

 

 

 

ADAPTIVE PROCESSING SERVER

Unspecific Cluster System

Yes

 

 

ADAPTIVE JOB SERVER

Unspecific Cluster System

Yes

 

 

SERVER INTELLIGENCE AGENT

Unspecific Cluster System

Yes

 

 

CONNECTION SERVER

Unspecific Cluster System

Yes

 

SBOP BI PLATFORM 4.0

BOE WEB APPLICATION JAVA

Business Objects Cluster

Yes

 

 

Central Mgmt. Service

Business Objects Cluster

Yes

 

 

File Repository Service

Business Objects Cluster

Yes

 

 

Event Service

Business Objects Cluster

Yes

 

 

Multidimensional Analy. Serv.

Business Objects Cluster

Yes

 

 

Data Federator Services

Business Objects Cluster

Yes

 

 

Connectivity Services

Business Objects Cluster

Yes

 

 

CR Processing Services

Business Objects Cluster

Yes

 

 

CR Scheduling Services

Business Objects Cluster

Yes

 

 

CR 2011 Processing Services

Business Objects Cluster

Yes

 

 

CR 2011 Scheduling Services

Business Objects Cluster

Yes

 

 

WebI Processing Services

Business Objects Cluster

Yes

 

 

WebI Scheduling Services

Business Objects Cluster

Yes

 

 

BI Workspace Services

Business Objects Cluster

Yes

 

 

Platform Processing Services

Business Objects Cluster

Yes

 

 

Platform Scheduling Services

Business Objects Cluster

Yes

 

 

Dashboard Design Services

Business Objects Cluster

Yes

 

 

SERVER INTELLIGENCE AGENT

Business Objects Cluster

Yes

 

 For complete steps of configuring the managed system for BOE 3.x and BOE 4.0, please refer to the attached docs.

 Managed system setup of BOE 3.x system in Solman 7.1

 Managed System Setup of BOE 4.0 system in Solman 7.1

Apache Tomcat

Supported Versions?

Apache Tomcat 5.5,  6.0, 7.0

Automatic creation of Technical System?

Yes
Technical Systems for Apache Tomcat 5.5 / 6.0 are created automatically of type Apache Tomcat Server.

Automatic entry of installed software?

Yes
Installed software components are automatically reported with SLD Data Supplier.

 For complete steps of configuring the managed system for Apache Tomcat , please refer to the attached docs.

 Managed System Setup of Apache Tomcat System in Solman 7.1

IBM WebSphere

Supported Versions?

WebSphere 6.0, 6.1, 7.0, 8.0

Automatic creation of Technical System?

Yes Technical Systems for WebSphere are created automatically of type IBM WebSphere Application Server.

Automatic entry of installed software?

Yes Installed software components are automatically reported with SLD Data Supplier.

 For complete steps of configuring the managed system for IBM WebSphere, please refer to the attached docs.

 Managed System Setup of IBM WebSphere in Solman 7.1

Microsoft Internet Information Service (include ASP.NET)

Supported Versions?

MS IIS 6.0, MS IIS 7.0, MS IIS 7.5

Automatic creation of Technical System?

Yes Technical Systems for MS IIS are created automatically of type MSIISINST via Outside Discovery in LMDB

Automatic entry of installed software?

Yes Installed software components including .NET Framework versions are automatically reported

Outside Discovery will report all installed .NET Framework versions to LMDB, please use the following rules to select which one to be marked as the diagnsotic relevant.

1. If interested IIS Application pools only use ASP.NET 2.0, please select the one highest product version among MSFT .NET 3.5, MSFT .NET 3.0 and MSFT .NET 2.0

2. If interested IIS Application pools only use ASP.NET 4.0, please select the product version MSFT .NET 4.0 

3. If interested IIS Application pools use both, please select the one highest product version among MSFT .NET 3.5, MSFT .NET 3.0 and MSFT .NET 2.0 and MSFT .NET 4.0

Microsoft SharePoint (as Technical Scenario)

Supported Versions?

SharePoint by Microsoft 2010, SharePoint by Microsoft 2013

Automatic creation of Technical System?

Yes, each SharePoint server is modeled as a MSIISINST Technical System via Outside Discovery.  SharePoint Farm cluster is modeled as the Techncial Scenario via SLD Data Supplier. See SAP note 1683706

Automatic entry of installed software?

Yes Installed software components including Duet Enterprise versions are automatically reported

 

For complete steps of configuring the managed scenario for Microsoft SharePoint, please refer to the attached docs.

 Managed System Setup of SharePoint in Solman 7.1 

Oracle WebLogic

Supported Versions?

WebSphere 9.0, 10.0, 10.3

Automatic creation of Technical System?

No Technical Systems for WebLogic are created manually of type Unspecific Cluster System.

Automatic entry of installed software?

No Both product version, product instance and installed software components
are created manually.

 For complete steps of configuring the managed system for Oracle WebLogic, please refer to the attached docs.

 Managed System Setup of Oracle WebLogic in Solman 7.1

 

SAP BusinessObjects Information Steward

Supported Versions?

SAP BusinessObjects Planning and Consolidation, version for SAP NetWeaver

Automatic creation of Technical System?

Yes 
Technical Systems are created automatically of type Business Objects Cluster.

Automatic entry of installed software?

Yes
Installed software components are automatically reported.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SBOP INFORMATION STEWARD 4.0

Metadata Integrators

Business Objects Cluster

Yes

 

 

Service

Business Objects Cluster

Yes

 

 

Task Server

Business Objects Cluster

Yes

 


Note: During Step 4 of Managed System Setup (Enter System Parameters), please enter the CMS Logon Parameters for the respective host

SAP BusinessObjects Planning and Consolidation

Supported Versions?

SBOP PC 10.0 FOR SAP NW
SBOP PC 7.5 FOR SAP NW
SBOP PC 10.0 FOR MICROSOFT
SBOP PC 7.5 FOR MICROSOFT

Automatic creation of Technical System?

Partly,
Technical systems of Type AS ABAP are created automatically. The ones of Type Unspecific Cluster System are not.

Automatic entry of installed software?

Partly,
Entries of installed software for Type AS ABAP are created automatically. The ones for Type Unspecific Cluster System are not.

Product Version

Product Instance

System Type

Diagnostics Relevant

SBOP PC 10.0 FOR SAP NW

Application Server ABAP

AS ABAP

Yes

 

Business Intelligence     

AS ABAP

Yes

 

Business Plan.and Cons. ABAP

AS ABAP

Yes

SBOP PC 7.5 FOR SAP NW

Application Server ABAP

AS ABAP

Yes

 

Business Intelligence     

AS ABAP

Yes

 

Business Plan.and Cons. ABAP

AS ABAP

Yes

 

BPC .NET Server

Unspecific Cluster System

Yes

SBOP PC 10.0 FOR MICROSOFT

Business Plan.and Cons.

Unspecific Cluster System

Yes

SBOP PC 7.5 FOR MICROSOFT

Business Plan.and Cons.

Unspecific Cluster System

Yes

 

MS SQL Server Analysis Service    

Unspecific Cluster System

Yes

 

MS SQL Server Reporting Service    

Unspecific Cluster System

Yes

 

MS SQL Server Integration Service    

Unspecific Cluster System

Yes

 

For more detailed information, please refer to SAP Note 1461749 - E2E Root Cause Analysis for SBOP PC (BPC) and

Solution Manager Diagnostics Managed System Setup and Configuration Guide for SBOP PC 7.5/10 with SAP Solution Manager:

SAP BusinessObjects Financial Consolidation

Supported Versions?

SBOP Financial Cons. 10.0
BOBJ Financial Cons. 10.5
BOBJ Financial Cons. 7.5
BOBJ Financial Cons. 7.0

Automatic Creation of Technical System?

No

Automatic Entry of Installed Software?

No

Product Version

Product Instance

System Type

Diagnostics Relevant

SBOP Financial Cons. 10.0

BOBJ Fin Cons Web Site 10.0
BOBJ FINANCIAL CONS. 10.0

MS_IIS
Unspecific Cluster System

Yes
Yes

BOBJ Financial Cons. 10.5

BOBJ Fin Cons Web Site 10.5
BOBJ FINANCIAL CONS. 10.5

MS_IIS
Unspecific Cluster System

Yes
Yes

BOBJ Financial Cons. 7.5

BOBJ Fin Cons Web Site 7.5
BOBJ FINANCIAL CONS. 7.5

MS_IIS
Unspecific Cluster System

Yes
Yes

BOBJ Financial Cons. 7.0

BOBJ Fin Cons Web Site 7.0
BOBJ FINANCIAL CONS. 7.0

Unspecific Cluster System
Unspecific Cluster System

Yes
Yes

SAP Note 1365266 - RCA: Managed System Setup for BOBJ Financial Cons.

SAP BW Accelerator

To publish SAP BI Accelerator to the Landscape Directory (SLD), please follow the instructions in SAP Notes:

1147499  "Connection to the System Landscape Directory" → TREX

1018839  "Registering in the System Landscape Directory using sldreg"

http://help.sap.com/saphelp_nw70/helpdata/EN/42/e33ae230ba3ee2e10000000a1553f6/frameset.htm

Supported Versions?

SAP BI Accelerator 7.0, SAP BW Accelerator 7.2

Automatic creation of Technical System?

Yes
Technical Systems are created of type
TREX System

Automatic entry of installed software?

Partly
Installed Software components are automatically reported for all supported product versions but
product versions and instances need to be added manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP BI Accelerator 7.0

BI Accelerator

TREX System

Yes

 

SAP BW Accelerator 7.2

BI Accelerrator

TREX System

Yes

 

Please check alsoSAP Note:  1264540   "Workload Data Collection for BWA (BIA) in Solution Manager"

SAP NetWeaver ABAP / J2EE

For a generic SAP NetWeaver ABAP or J2EE system you need at least to select the following product instances as installed and diagnostics relevant. Depending on the installed SAP NetWeaver release or enhancement Package, it could be one the following:

Supported Versions?

SAP NETWEAVER 7.0, SAP EHPX FOR SAP NETWEAVER 7.0, SAP NETWEAVER 7.1, SAP NETWEAVER 7.2, SAP NETWEAVER 7.3, SAP EHPX FOR SAP NETWEAVER 7.3, SAP NETWEAVER 7.4

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server ABAP and Application Server Java.

Automatic entry of installed software?

Partly
Installed software components are automatically reported for all supported product versions. Since SAP Netweaver 7.3 also product version and
instances are reported automatically.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER 7.0

Application Server ABAP

AS ABAP

Yes

 

 

Application Server Java

AS JAVA

Yes

 

SAP EHPX FOR SAP NETWEAVER 7.0

Application Server ABAP

AS ABAP

Yes

 

 

Application Server Java

AS JAVA

Yes

 

SAP NETWEAVER 7.11

Application Server Java

AS JAVA

Yes

 

SAP NETWEAVER 7.2

Application Server Java

AS JAVA

Yes

 

SAP NETWEAVER 7.3

Application Server ABAP

AS ABAP

Yes

 

 

Application Server Java

AS JAVA

Yes

 

SAP EHPxx FOR SAP NETWEAVER 7.3

Application Server ABAP

AS ABAP

Yes

 

 

Application Server Java

AS JAVA

Yes

 

SAP NETWEAVER 7.4

Application Server ABAP

AS ABAP

Yes

 
 

Application Server Java

AS JAVA

Yes

 

Adobe Document Services

Supported Versions?

SAP NETWEAVER 7.0, EHPX for SAP Netweaver 7.0

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server Java

Automatic entry of installed software?

Partly 
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER 7.0

Adobe Document Services

AS Java

Yes

 

EHPX FOR SAP NETWEAVER 7.0

Adobe Document Services

AS Java

Yes

 

SAP HANA

Supported Versions?

SAP HANA 1.0 >= SP2

Automatic creation of Technical System?

yes
Technical System will be created automatically by outside discovery
When using SAP HANA 1.0 >= SP4 and Solution Manager >= SP5
the technical system is delivered via SLD

Automatic entry of installed software?

No
Installed software must be assigned manually

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP HANA ENTERPRISE EDIT. 1.0

SAP HANA database

 

Yes

 

SAP HANA ENTERPRISE EXT. 1.0

SAP HANA database

 

Yes

 

Managed System Setup of SAP HANA in Solution Manager 7.1

SAP NetWeaver Composition Environment (CE)

Supported Versions?

SAP NETWEAVER CE 7.1, SAP NETWEAVER CE 7.2

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server Java

Automatic entry of installed software?

Partly 
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER CE 7.1

Composite Applications

AS Java

Yes

 

SAP NETWEAVER CE 7.2

Application Server Java

AS Java

Yes

 

Duet

Web Dispatcher

Supported Versions?

SAP WebDispatcher 7.0, SAP WebDispatcher 7.10, SAP WebDispatcher 7.11, SAP WebDispatcher 7.20

Automatic creation of Technical System?

Yes
Technical Systems are created of type
SAP Web Dispatcher

Automatic entry of installed software?

Partly 
Installed software components might be provided automatically by the SLD data supplier, but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP EHP2 FOR SAP NETWEAVER 7.0

SAP Web Dispatcher

SAP Web Dispatcher

Yes

 

To add missing software component/product information open the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), choose Managed Systems Configuration > Technical Systems > System Operations > Maintain System. Then select the node “Software” in the navigation tree and open the “Product Instances (Details)” on the right tab panel. Add the appropriate product version, product instance and, if missing, software component information. For example,  the software component version SAP WEB DISPATCHER 7.20, product version SAP EHP2 FOR SAP NETWEAVER 7.0 in the product instance SAP Web Dispatcher.

Note:

  • Please also refer to this link for registering the Web Dispatcher in SLD
  • And also this link in case problem arises

SAP Netweaver MDM 7.1

 

Supported Versions?

SAP NETWEAVER MDM 7.1

Automatic creation of Technical System?

Yes
Technical Systems are created of type
MDM

Automatic entry of installed software?

Yes  

Prerequisites:
Ensure that you installed diagnostics agents on all hosts of the MDM system.
Execute the  activities described in SAP Solution Manager Work Center -> System Preparation -> Step 5.5 Prepare Outside Discovery and Connect Diagnostics Agent for the MDM Server database hosts.

SLD registration

For SAP Netweaver MDM 7.1SP 01 - SP 09 please register the System to SLD as explained in SAP Note 1798643. Do not use the SLD registration mechanism that is part of the MDM system.
As of SAP Netweaver MDM 7.1SP 10 please register the MDM system using the MDM specific SLD registration mechanism. Please see note 1018839 - Registering in the System Landscape Directory using sldreg.

After successful SLD registration the database systems used by the MDM system need to be added manually to the system definition in SAP Solution Manager.
Please proceed as follows:

1. Call the “SAP Solution Manager Configuration Work Center”.
2. Select “Managed System Configuration”.
3. Select the MDM System in Question.
4. Select System Operations --> Maintain System.
5. Select Assigned DB systems.
6. Select Add and add the databases used by the MDM system.

Please consider the following for SRM/MDM Catalog:

If you installed an SRM/MDM Catalog you have installed in fact two different technical systems:
One MDM Server storing the catalog data and
one Application Server Java to display the  catalog UI.
The defintion of the MDM Server in is explained in this chapter.
Additionally the Application Server Java needs to be registered to SLD. Please refer to the relevant section.

 Managed System Setup

Perform the managed system configuration as follows:'
1. Call the “SAP Solution Manager Configuration Work Center”.
2. Select “Managed System Configuration”.
3. Select the MDM System in Question.
4. Select Configure System.
4. Select Configure System.
5. Execute all activities in the guided procedure.

 

Sybase Unwired Platform 2.1

Managed System Setup for Sybase Unwired Platform 2.1

How to use this document

Diagnostics in SAP Solution Manager depends on the definition of technical system inside SAP Solution Manager. This document describes the steps needed to perform managed system setup for Sybase Unwired Platform (SUP)2.1 technical systems with SAP Solution Manager.

Setting up Managed System Configuration consists of two sections as mentioned below:

  1. Prerequisites
  2. Setup Managed System configuration in Solution Manager

1. Prerequisites

Before starting the configuration of a technical system for diagnostics in SAP Solution Manager, you have to ensure that the following prerequisites are all fulfilled:

  1. Please refer to SAP Note 1634219 to check whether Solution Manager and Sybase Unwired System Platform prerequisites are met.
  2. Please refer to SAP Note 1634219 for installation of Diagnostics and Java Agents on the system.
  3. Register the Sybase Unwired Platform in the System Landscape Directory (SLD), SLD is a central repository of system landscape information used to manage the software lifecycle. The SLD describes the systems and software components that are currently installed. SLD data suppliers register the systems on the SLD server, and keep the information up-to-date. Sybase Unwired Platform is a third-party system that must be registered with the SLD. Please follow the steps below to register SLD.
  4. Create a Sybase Unwired Platform Cluster Admin User, which will be used by SAP Solution Manager to connect to Sybase Unwired Platform.

Register the System Landscape Directory(SLD) or Configuring the SLD Desitination:

Prerequisites

You have installed the Sybase Unwired Platform.

Task

  1. Navigate to the installation path <UnwiredPlatform_InstallDir>\Servers\UnwiredServer\SLD\ to locate the files corresponding to the Data Supplier.
  2. From the command prompt, run the batch file runSLDReg.bat.
  3. Enter the following details:

Option
Description

UserName

User name of the SLD system.

Password

Password used to authenticate the SLD system.

ServerHost

IP Address of the SLD Server.

Port

HTTP(S) port on which the SLD server is running.

Use https

Indicate if you want a secure connection or not.

Write this information to secure file

If you want to store the encrypted HTTP connection information, enter y.

  1. The configuration (.cfg) and key (.cfg.key) files are created in the location: <UnwiredPlatform_InstallDir>\Servers\UnwiredServer\SLD\SLDREG.

Generating the Payload:

Generate the payload that contains all details of the installed Sybase Unwired Platform system, and upload the payload to System Landscape Directory (SLD).

Prerequisites

Ensure all Sybase Unwired Platform services are currently running before you generate the payload.

Task

  1. From the command prompt, run the batch file runXMLgenerator.bat.
  2. Enter the following details:

Option
Description

Port on which server is listening

Port number of the server which listens to the authentication request .
(SUP Management Port by default 2000)

Login name

Sybase Unwired Platform administrator's login name

Login password

Sybase Unwired Platform administrator's login password

            3. If the payload generation is successful, the payload file SUP_PayLoad.xml is created in the location <UnwiredPlatform_InstallDir>\Servers\UnwiredServer\SLD\SLDREG\.

           4. To upload the payload to SLD, run the batch file sendPayLoad.bat.

4.   To Create a Sybase Unwired Platform Cluster Admin User in SUP 2.1, please follow the steps below:

a. Login to Sybase Control Center with supAdmin/Password
b. browse through Security-Admin and right Panel Click on Authentication-->New
c. Authentication Provider-->Choose com.sybase.security.core.PreconfiguredUserloginmode
d. Define username/password
e. Ensure that you copy the role(SUP Administrator similar to SupAdmin)
f. Click "OK" as shown below:
 

2. Final Step to Setup Managed System Configuration in Solution Manager:

Open the SAP Solution Manager Configuration Workcenter

Select Managed system configuration.

Now Filter to System Type “Sybase Unwired Platform”.

After choosing “Sybase Unwired Platform” now Select Technical System that you wish to do Manage System Setup and Click on “Configure System “as shown below:
 

Once after Selecting “Configure System, you will get list of steps before proceeding with steps, you will need to Click on “Display Technical System Software”-->Click on “Edit”.

This will open new Technical System Editor window as shown in the screen below , now select “Software”--> Set flag Diagnsotics-Relevant Sybase Unwired Platform 2.1  product version, then Save and Close.

  
 
Now select Technical System to Configure System as shown below and Click on Edit.

 Here select the product and ensure flag Diagnsotics relevant for product version is enabled as shown below:

Select the product and assign Diagnostic Agent:
 
Note: If there is no any Diagnostic agent assigned then you need to select the SLD Agent candidates Tab and bind the Agents from SLD to Solution Manager before assigning.

Next proceed to “Enter the System Parameters” as shown below:

Here you need to enter the following information, which can be found from Sybase Unwired Platform 2.1 installation.

  1. Sybase Control Center host(by default hostname of SUP 2.1 installation)
  2. Sybase Control Center port(default port:8283)
  3. SUP Cluster Admin user/password(created under prerequisites step 4)
  4. Sybase Unwired Server Management port(default:2000)
  5. Unified Management port(default:9999)
     
    Next move to Enter Landscape Parameters step. Here you need ensure that Landscape parameter for Sybase Unwired Server is pointing to correct installation path as shown in below.

Sybase Control Center Path=<$Install Location of SUP$>\Sybase\SSC-3_2

Sybase Unwired Server Instance Path=<$Install Location of SUP$>\Sybase\UnwiredPlatform
 
Next proceed further with Automatic configuration and Manual Configuration steps and complete Manage System Configuration set without any errors.

Sybase Unwired Platform 2.2

How to use this document

Diagnostics in SAP Solution Manager depends on the definition of technical system inside SAP Solution Manager. This document describes the steps needed to perform managed system setup for Sybase Unwired Platform (SUP)2.2 technical systems with SAP Solution Manager.

Setting up Managed System Configuration consists of two sections as mentioned below:

  1. Prerequisites
  2. Setup Managed System configuration in Solution Manager

Prerequisites

Before starting the configuration of a technical system for diagnostics in SAP Solution Manager, you have to ensure that the following prerequisites are all fulfilled:

  1. Please refer to SAP Note 1762741 to check whether Solution Manager and Sybase Unwired System Platform prerequisites are met.
  2. Please ensure Byte code Agents are configured aganist Introscope Enterprise Manager.
  3. Register the Sybase Unwired Platform in the System Landscape Directory (SLD), SLD is a central repository of system landscape information used to manage the software lifecycle. The SLD describes the systems and software components that are currently installed. SLD data suppliers register the systems on the SLD server, and keep the information up-to-date. Sybase Unwired Platform is a third-party system that must be registered with the SLD. Please follow the steps below to register SLD.
  4. Upload CV Templates to Solution Manager, please refer SAP Note 1762741 for more information.
  5. Upload Config.xml to Solution Manager, please refer SAP Note 1762741 for more information.

Configure Introscope Agents

Byte Code Agent installation is now a part of the SUP 2.2, So you need to configure this against your Introscope Enterprise Manager

To Configure Byte Code Agents please follow the steps below:

  •  Ensure SUP 2.2 installation is successful without any errors and you are able to run SUP servers. 
  • Now go to “<$Install Directory$>:\Sybase\UnwiredPlatform\Servers\UnwiredServer\bin\” location via Command Prompt and execute the following
  • <$Install Directory$>:\Sybase\UnwiredPlatform\Servers\UnwiredServer\bin\configure-introscope-agents.bat -host:<EM-host> -port:<EM-port> 

Example:

D:\Sybase\UnwiredPlatform\Servers\UnwiredServer\bin\configure-introscope-agents.bat -host: ld8184.wdf.sap.corp -port:6001

Note:

  • If Byte Code Agents is partially installed then you might have to run “uninstall-agents.bat” then follow above steps again.
  • Once after successful installation of Byte Code Agents you need to restart SUP servers so that changes can be viewed in Introscope Enterprise Manager.

Refer the screenshot as shown below:

Register SUP 2.2 with System Landscape Directory(SLD)

SLD data suppliers register the systems on the SLD server and keep the information up-to-date.  Sybase Unwired Platform must be registered with the SLD following the steps below.

Prerequisites

 You have installed the Sybase Unwired Platform 2.2.

Task

  1. Login to Sybase Unwired Platform Control Center(SSC) as an administrator
  2. Select Servers--->Then Select System Landscape Directory (SLD) Tab
  3. Now Click on New and Enter the SLD connection information analog to the information given in the screenshot below:

Generating The PayLoad to SLD

Generate the payload that contains all details of the installed Sybase Unwired Platform 2.2 System, and upload the payload to System Landscape Directory (SLD).

 Prerequisites

Ensure all Sybase Unwired Platform services are running before you generate the payload.

Task

  1. Login to Sybase Unwired Platform Control Center (SSC) as an administrator.
  2. Select Servers  --->Then Select System Landscape Directory (SLD) Tab
  3. Now Select Schedule-->Run Now this will generate Manual Payload upload the payload to SLD as shown in the screen below:

Final Step to Setup Managed System Configuration in Solution Manager

Open the SAP Solution Manager Configuration Workcenter

Select Managed system configuration.

Now Filter to System Type “Sybase Unwired Platform”.

After choosing “Sybase Unwired Platform” now Select Technical System that you wish to do Manage System Setup and Click on “Configure System “as shown below:
Once after Selecting “Configure System, you will get list of steps before proceeding with steps, you will need to Click on “Display Technical System Software”--->Click on “Edit”.

 This will open new Technical System Editor window as shown in the screen below , now select “Software”---> Set flag Diagnsotics-Relevant Sybase Unwired Platform 2.2  product version, then Save and Close.

Now select Technical System to Configure System as shown below and Click on Edit.

Here select the product and ensure the flag Diagnostics relevant for product version is enabled as shown below:

 

Select the product and assign Diagnostic Agent:


Note: If there is no any Diagnostic agent assigned then you need to select the SLD Agent candidates Tab and bind the Agents from SLD to Solution Manager before assigning.

Next proceed to “Enter the System Parameters” as shown below:

 Here you need to enter the following information, which can be found from Sybase Unwired Platform 2.2 installation.

  1. Sybase Control Center host(by default hostname of SUP 2.2 installation)
  2. Sybase Control Center port(default port:8283)
  3. SUP Cluster Admin user/password(created under prerequisites step 4)
  4. Sybase Unwired Server Management port(default:2000)
  5. Unified Management port(default:9999)

Next move to Enter Landscape Parameters step. Here you need ensure that Landscape parameter for Sybase Unwired Server is pointing to correct installation path as shown in below.

Sybase Control Center Path=<$Install Location of SUP$>\Sybase\SSC-3_2

Sybase Unwired Server Instance Path=<$Install Location of SUP$>\Sybase\UnwiredPlatform

 Next proceed further with Automatic configuration and Manual Configuration steps and complete Managed System Configuration set without any errors. 


SAP Router

Supported Versions?

SAP ROUTER 7.2

Automatic creation of Technical System?

No, Technical Systems for SAP Router are created manually of type Unspecific Standalone Application System.

Automatic entry of installed software?

No, Both product version, product instance and installed software components are created manually

For complete steps of configuring the managed system for SAP ROUTER, please refer to the following page.

Managed System Setup of SAP Router in SAP Solution Manager 7.1


SAP Business Connector System 

Supported Versions?

SAP Business Connector 4.8

Automatic creation of Technical System?

No, Technical Systems for Business Connector are created manually of type Unspecific Standalone Application System.

Automatic entry of installed software?

No, Both product version, product instance and installed software components are created manually

For complete steps of configuring the managed system for SAP Business Connector System, please refer to the following page.

Managed System Setup of SAP Business Connector in SAP Solution Manager 7.1


SAP Convergent Charging

Supported Versions?

SAP Convergent Charging 3.0

Automatic creation of Technical System?

Yes, SAP Solution Manager 7.1 relies on the landscape information in the Solution Landscape Directory (SLD) and in its landscape management database (LMDB). SAP Convergent Charging provides an automatic registration procedure to the SAP System Landscape Directory (SLD)..

Automatic entry of installed software?

Yes, The SAP Solution Manager will automatically import the SAP CC 3.0 system from the SLD into the LMDB. However, due to issues with the SLD Data Supplier in SAP CC 3.0, it is necessary to review resp. correct the SAP CC system data in the SAP Solution Manager.

For complete steps of configuring the managed system for SAP Convergent Charging System, please refer to the following page.

Managed System Setup of SAP Convergent Charging System in SAP Solution Manager 7.1


Sybase Afaria System

Supported Versions?

Sybase Afaria 7.0

Automatic creation of Technical System?

No, Technical Systems for SAP Afaria are created manually of type Unspecific Cluster System.

Automatic entry of installed software?

No, Both product version, product instance and installed software components are created manually

 For complete steps of configuring the managed system for Sybase Afaria System, please refer to the following page.

Managed System Setup of Sybase Afaria in SAP Solution Manager 7.1


SAP Partner Products

For detailed information about which Partner Products are currently supported by the Right to View version of Introscope that comes with SAP Solution Manager, please refer to SAP Note 1852015.

SAP Productivity Pak by Ancile

Supported Versions?

SAP Productivity Pak 4.5, SAP Productivity Pak 5.0

Automatic creation of Technical System?

Yes
Technical Systems are created of type Apache Tomcat Server

Automatic entry of installed software?

Yes
Installed software components product versions and product instances are provided automatically, but product versions and product instances need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP Productivity Pak by Ancile 4.5

Productivity Pak Server

Apache Tomcat

Yes

 

SAP Productivity Pak by Ancile 5.0

Productivity Pak Server

Apache Tomcat

Yes

 

Refer to  SAP Note 1864308 for further instructions on running Managed System Setup 

Refer to  SAP Note 1779892  for further instructions on integrating of SAP Productivity Pak by Ancile with CA Introscope 

 

SAP Product Engine (MSG.PM), part of SAP Insurance Policy Management (FS-PM)

SAP Product Engine (MSG.PM) is a partner solution from MSG Systems AG which is part of SAP Insurance Policy Management.

MSG.PM component can be monitored using Introscope. This is C/C++ based component and Introscope integration has specific configuration steps related to MSG.PM.

Refer to SAP Note 1840351 for further instructions to monitor MSG.PM component.


Vertex O-Series

SAP Central Process Scheduling by Redwood


SAP Talent Visualization and SAP Org Visualization by Nakisa

Supported Versions?

SAP NETWEAVER 7.1X, , SAP NETWEAVER 7.3X, SAP NETWEAVER 7.4X

Automatic creation of Technical System?

Yes 
Technical Systems are created of type 
Application Server Java

Automatic entry of installed software?

Partly 
Installed software components 
are provided automatically but product versions and product instances 
need to be assigned manually.

 

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP Org Visualization 3.x

Org Chart Java, OrgModeler_Java

AS Java

Yes

 

SAP Org Visualization 4.x

Org Chart, OrgModeler,OrgAudit

AS Java

Yes

 

SAP Talent Visualization 3.x

Succession Planning Java, CareerPlanning_Java,TalentFramework_Java

AS Java

Yes

 

SAP Talent Visualization 4.xTalentHubEmployee,TalentHubManager,TalentHubHRExecAS JavaYes 


SAP Portal Site Management by OpenText and SAP Portal Content Management by OpenText

Automatic creation of Technical System?

Yes 

Technical Systems are created of type Application Server Java

Automatic entry of installed software?

Partly 

Installed software components are provided automatically.

Product versions and product instances needs to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP PSM BY OPEN TEXT 10.0 (add-on)

OT WSM Portal Mgr-SAP NW Portl

AS Java

No

 

SAP PCM BY OPEN TEXT 10.0 (add-on)

Portal Content Management

AS Java

No

 

 

 

 

  • No labels
  1. Guest

    Hi Michael,

    Thanks for the info, I'll keep struggling with SLD/LMDB/SMSY but this helps. Is the section for "SAP ERP 6.0 & EhPx for ERP 6.0" intentionally left blank or an oversight? I assume that's what most people have and would like to set up correctly. Thank you,

    David

  2. Guest

    Hi Michael, thanks for the useful info, but how can we connect Content Server to Solution Manager 7.1?

    Yohanes

  3.  

    Do we also have info on the SMP 2.3 setup and is there an update to SAP Note 1762741: Setup for SUP 2.2 with SolutionManager 7.1 SP05) available that

    would have an updated SMP 2.3 XML in the template zip ? (CVTemplates71SP05.zip)

    1. Hello Klaus,

      The template for SMP 2.3 has not been released yet, if you have further question please send me a mail.

       

      BR,

      Kobe