Quantcast
Channel: SCN : Document List - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 571

Basic Web-UI Monitoring in HCI

$
0
0

Introduction

 

We can view an overview of two main aspects of HCI that you need to monitor, integration content and messages.We can also access the dedicated message monitor and integration content monitor to view more information on the status of messages and integration content respectively.

 

We can monitor integration flows and check the status messages for a tenant cluster using web-UI and eclipse UI. In this blog I’m going to discuss the monitoring features available in HCI web-UI.

 

For eclipse monitoring please refer the blog  Basic Monitoring and Administration for the Integration Developer (1/3)


To launch web-based monitoring application open the Web- UI URL provided by SAP in a web browser. Click on menu and select monitor as shown in the above screenshot.

test.png

It will take you to the below screenshot. Monitoring start page will show the run time information for Message monitoring and integration content monitoring as below 

test1.png

In web-UI monitoring we can do message monitoring and integration content monitor.


Message monitoring


It provides number and status of processed messages within a specified time window. In message monitoring we can check the following status of messages.


  • Error              : Error occurred during the message processing but message retry not started automatically.
  • Failed            : Message processing failed, re-try not possible
  • Retry             : Error occurred during message processing and retry started automatically.
  • Completed    : message processing completed and the message delivered to the receiver successfully.
  • Cancelled      : we can cancel the messages from the message monitoring editor.
  • Processing    : message is currently being processed.
  • Escalated      : Error occurred during the message processing but message retry not started automatically. For  synchronous interfaces error  messages sent to the sender.

 

In the below screenshot we can see the message monitoring tile’s that points to messages with status “Failed / Error / Completed” that have been processed for all the integration scenarios within the past 24 hrs.Numbers representing the no.of messages in that status.Each tile shows the filter settings in the header and the number of messages and artifacts that corresponding to the filter settings.

test3.png

We can customize the message monitoring start page as per our requirement by add/ delete the tiles. We can also Rearrange start page by dragging and dropping tiles to another location.


Monitoring page will be refreshed automatically for every 5 seconds till 5 mins.


How to add status tiles in message monitoring window

 

Click on the “+” it will take you to the below window. When add / change a tile for the message monitor we can specify the status / Time / integration flow for the messages to be displayed.

test4.png

Status Attribute


It will allows you to filter message by status, in the dropdown list we can select any one of the status as shown in the below screenshot.

test5.png

In this example I’m going to add cancelled messages tile to my message monitoring.


Time Attribute


It allows you to select the status of the messages at predefined intervals as shown in the below screenshot.

 

test7.png

Integration flow Attribute


It allows you to search for messages associated with a specific integration flow. Dropdown list display all integration flows deployed on the tenant. We can also select the message status for a particular integration flow.

test8.png

Here I would like to check the message status of all integration flows, so I selected “All integration Flows” and click Ok. Cancelled message tile added as below.

test9.png

To check the complete details of particular messages click on the number, it will take you to the message status overview window.

test10.png

In this screen we can see the following attributes for each message.


Last Updated at : Display message processing finished time.

 

Status                : indicates the status of end to end message processing. If you click on the status of the message it will display the message processing log.

 

Integration Flow: It provides name of the integration flow, if you click on the integration flow name it will display the graphical representation of the integration flow.


Receiver             : provides receiver of the message.


Processing Time : Display total time of message processing.

 

ID                          : it will allow us to uniquely search for the message based on Message ID.

 

Action                  : It allows us to do the following


Messages with status Successful

 

Choose configure to configure the externalized parameters of the associated integration flow.

 

Messages with status retry

 

Cancel the selected messages.


Message processing Log


--> when you click the status of a message the message processing log will be open.


--> The message processing log displays structured information on the processing of a message.

 

---> In the message processing log, you can search for strings using the Search field above the message processing log.

 

--> If messages have status Error, Failed, or Retry, more information on the cause of the error situation is displayed at the top of the message processing log (in red).

 

--> You can download the message processing log, for example, to share the information with other users.

 

Integration content monitoring

 

It provides overview of the integration artifacts such as integration flows and security related artifacts deployed on the tenant with all statuses.

We can also display the status of individual artifacts.

test11.png

By changing the filter settings we can display the required artifacts.


Filter Settings


Status


We can add the tiles with the status installed / starting / started / stopping / error to the integration content monitor, based on you requirement.

test12.png

When you click the status of an artifact, detailed information is displayed. If artifacts have status Error, the error log is opened.

In the header area, the context information about the artifact is displayed (the attributes displayed in the Integration Content Overview), as well as the VM name of the affected run time node.

 

Run-Time Status

 

The run time status indicates if a component is operational on the run time node.

The following values are possible:

 

  • installed :For a deployable component, this status means: the component has been deployed but not started yet.
  • launching :Component is currently being started.For a deployable component, this status means: the component has been deployed and is currently being started.
  • started   :Component is started on selected run time node.
  • error
  • stopping  :Component is currently being stopped.

 

Type


Allows us to display the one of the following sets of artifacts.


  • All
  • Integration Flow
  • Credentials
  • SSH Known Hosts
  • Keystore
  • OAuth
  • PGP Public Keying
  • PGP Secret Keying
  • Value Mapping.


Artifact


Allows us to search for specific artifact.


If you click a number with in a tile it will take you to integration artifacts overview.

test13.png

test15.png

Attributes of integration content Artifact


For each artifacts the following attributes are displayed.

 

Artifact name : It provides name of the artifact. We can click on the artifact name to view more details.

Version          : It display the integration iflow version.

 

Type               : Type of the integration content [integration flow / Credentials / Value mapping / Key Store]

 

Deploy state  : This attribute displays status of the deployed artifacts on the tenant.It will be any of the following states.

                         Stored /Started / Deploying /Deployed / Error.

 

Deployed by : Indicates the user who deployed this artifact.

 

Deployed      : When the artifact is deployed on the tenant.

 

Status per node: Indicates the status for each runtime node. Possible status can be installed / starting / started / stopped / error.

 

Action            : You can perform the following actions using this option.

                          Un-deploy / download / configure.


Viewing all articles
Browse latest Browse all 571

Trending Articles