Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Blue statuses in the Monitoring UI.

Symtom

In the monitoring UI, you can see the scripts you deployed on the robots, but their status are all Blue ()

Reason

In UXMon, this status indicates that the script is deployed on the robot, but no metric was received during the considered time range (by default the last hour).

Procedure

The root cause could be multiple. Below are some way of investigation.
  • Check the scripts scheduling

In the UXMon Configuration, step 4 - Monitoring, ensure that the script scheduling (ex: schedule.xxx parameters) planned executions during the considered time range.

 

  • Check the status mapping

In the Status Mapping table - in the Monitoring Application settings - ensure that the 2**, 4**, 5** are not configured to be reported in blue.

  • Check the Notification Web Service activation

Ensure that the Notification (data push from the Robots to Solution Manager) is active.

 In the UXMon Configuration, step 2.2. The Notification Service should be ticked.

  • Ensure that the Notification WebService user is valid and not Locked and its password properly defined.

In the UXMon Configuration, step 2.2. Ensure the connection user is the expected one.

 In case the configuration indicates to user SM_EXTERN_WS (recommended setting):

  1. in the Mandatory Configuration > Infrastructure preparation > Step XX,
    Test the SM_EXTERN_WS user (i.e. verify the connection works)


  2. in the UXMon configuration, Step 4 Monitoring, ensure the wsnotify.user parameter indicates the correct user.
    If the value is not valid or missing, go to step 2.4 and re-execute the 3 first Automatic activities:
        • Create Endpoints for communication
        • Create Logical Ports
        • Create Web Service Notification User
  • Ensure the WebService notification URL is valid

In the UXMon Configuration, Step 4 Monitoring, verify the wsnotify.url parameter.

If the value is not valid or missing, go to step 2.4 and reexecute the 3 first Automatic activities:

        • Create Endpoints for communication
        • Create Logical Ports
        • Create Web Service Notification User

In the SOAMANAGER transaction, identify the Web Service named AI_EEM_BULK_NOTIFICATION_ST and check it (it's active, bound, ...)

  • Verify that the robots have to appropriate global configuration

In the Agent Administration UI, in the Application Configuration tab:

  1. Identify the com.sap.smd.agent.application.eem configuration.
  2. Expand the node and select the ConfigGlobal.xml node.
  3. Download the custom resource for the "Global scope"
  4. In the retrieved file, and ensure the wsnotify.xxx parameters match the settings in the configuraiton UI.
    If the values are not valid or missing, go to step 2.4 and re-execute the 3 first Automatic activities:
        • Create Endpoints for communication
        • Create Logical Ports
        • Create Web Service Notification User

Still in the Config.Global.xml node of the com.sap.smd.agent.application.eem configuration in the Agent Administration UI:

  1. Select the Agent corresponding to the faulty robot.
  2. Download the customer resource
  3. In the retrieved file, ensure the wsnotify.xxx parameters are identical to the one retrieved at the Global Scope.
    If the values are not valid, ensure that the agent file was not manually customized.

 

  • Verify the global configuration on the robot host

Connect on the Robot host and verify the ConfigGlobal.xml stored locally.
(<Agent home directory>/SMDAgent/applications.config/com.sap.smd.agent.application.eem/ConfigGlobal.xml).

Note, the file is usually encrypted.
In this case:

        • Check that the file modification time is consistent with the latest changes (last time the step 2.4 automatic activity was executed).
        • Check the file size. It should be the same than the one retrieved from the Agent Administration UI (c.f. previous step)

 

  • Check the Robots status

In the UXMon configuration, Step 2.6, refresh the robots table and check the statuses in the Notification column.
In case of red status, a message will give indication on the root cause of the problem.

 

  • Check the Robot logs

In the Agent Administration UI:

  1. Identify the robot agent and open its logs.
  2. Filter the location column on "*eem*"
  3. Potentially, filter the thread column on "*wsnotify*"

Check the potential errors.

Description of the flow

The Robot publishes the Scripts execution metrics to Solution Manager (ABAP Stack) via the AI_EEM_BULK_NOTIFICATION_ST web service.
Note: this communication uses a channel different than for the configuration (which communicates with the Solution Manager Java Stack - via P4).
So, it's possible that an Agent displayed "disconnected" in the Agent Administration, continues to publish UXMon metrics.

In case the communication with the Solution Manager ABAP stack is interrupted, the Robot will continue to execute the scripts.
The execution metrics will be temporarily stored on the robot host, in dedicated queues (in memory and on disk).
The queues are automatically flushed when the communication is restored.

 

  • No labels