Skip to Content

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

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

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

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

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

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

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

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

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

This document is about the managed system configuration of a JAVA stack .

There are three main steps for the configuration. DAA Agent Installation, SLD registration and Managed System configurations.

1. Installation of Diagnostics Agent on all hosts

You must install Diagnostics Agent on the Server.

Detail description of the step can be found in the Installation of SMD Agent with SWPM section of Part 5

2. Connect Managed System to SLD

Create SLD Data Supplier for the solution manager system on SLD of the satellite Java system as seen below.


Use SLD Data Suppliers  function of nwa on satellite system and push the system data to all target SLDs as seen below.


After sending data you can check Solution Manager SLD and LMDB for the managed system.

3. Managed System Configuration of Java System

Run SOLMAN_SETUP and select Managed System Setup node.

Find your Java System as seen below and run Full Configuration Incl. Service Delivery EWA configuration.


There are 9 Steps for configuration.

1- Assign Product

In this step you define the product installed for the technical system.

Diagnostics-relevance is also set with product SAP NETWEAVER 7.4


2- Check Prerequisites

In this step, you check the prerequisites for the configuration of SAP Solution Manager automatically.


3- Assign Diagnostics Agent

In this step, you assign Diagnostics Agent to the server (host) on which managed system is running. You can also check the status and version of the DAA.


4- Enter System Parameters

In this step, you specify the system parameters required to configure the managed system, which depend on the type of the managed system.

You specify the Introscope EM, Managed System Load Balancer Host and port. And enable EWA alert inbox and system recommendations.

You use the created DB user in DB Parameters section and by saving you setup DBA Cockpit and DB extractors.

You also maintain message server host and port and a user for Java Parameters as seen below.


5- Enter Landscape Parameters

In this step, you can verify and add landscape parameters.


6- Maintain Users

In this step you create or update dialog or technical users and assign roles to those users.


7- Finalize Configuration

There are automatic and manual activities that needs to be fulfilled in Final Configuration step. You can leave postponed activities as is. For manual activities go to each transactioon or URL to perform the activity. Click display to get more help.


8- Check Configuration

In this step, you automatically check whether the system is configured correctly, and you update the statuses in the overview of the Managed Systems Configuration.


9- Complete

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


This is the end of the configuration.

Managed System Configuration of PI System (Dual Stack) is coming next.

Thanks for your interests.


You must be Logged on to comment or reply to a post.
  • Hi ,

    In Step 4 : Enter System parameters , in the Java parameters section , Deploy Byte code adapter under managed system step is not required for java based system ?

    In Solution manager 7.1 we performed this step and is it not required for solman 7.2 ? How the java will be monitored ?

    Please advise.


  • Hello Utham,

    The option for deploying byte code adapter is stil valid for 7.2.
    As it is mentioned in page 7 of below document it is necessary to monitor Java system.

    Yuksel AKCINAR

  • Hi Yuksel,

    Nice blog..Thanks

    Is it mandatory to setup DBACOCKPIT connection for JAVA system in the managed system config of solution manager 7.2. Please clarify.

    Database Host:

    Service Name:

    Port Number:

    TNS Name:

    Character Set:

    National Character Set:


    * User Name:

    * Password

    Please let me know the username and password to be maintained and character set ...Can I maintain J2EE_ADMIN?.

    Thanks in advance


    • Hello Daniel,


      İf you want to gather information about DB of the system you should configure DB parts also.


      Check 4 Enter System Parameters - DB parameters tab for needed information.

      You can find which info is required.

      You need DB user not a Java user.


      This config will create a DB connection on DBACOCKPIT of Solution manager system. So you can also monitor Java Systems DB on Solution Managers DBACOCKPIT.




      Yuksel AKCINAR

  • Thanks for the reply.


    Please clarify the credentials to be used for JAVA system for DBACOCKPIT connection set up.

    Character Set:

    National Character Set:


    * User Name:

    * Password


    Thanks in advance

  • Hi Yuksel,

    In the  'Enter System Parameters' step, for 'Java Parameters', Test Logon is failing with error as below:

    SAP Solution Manager Wizard ur_relax(); UCF_DomUtil.attachEvent(window, "load", wdaOnPopupLoad)

    Logon test failed for user 
    Details : Exception while trying to get InitialContext. (Cause: Can't get Socket. Reason:Connection timed out (port 8144 to address (


    I can ping the target server from solution manager host. Also, DB and application are installed on the same server.

    Any idea what might be blocking the connection on Java side.

    Thank you.

    Hari Kiran.