-
Technical Assistance
Request product support from SAP
-
Non-Technical Assistance
Request non-product support or provide feedback on SAP Support Portal site
Technical Assistance
Request product support from SAP
Non-Technical Assistance
Request non-product support or provide feedback on SAP Support Portal site
Among others, SAP Manufacturing Integration and Intelligence (MII) is used to integrate plants and enterprise systems. SAP MII is able to integrate with various system types, communicating via RFC, HTTP or SOAP calls (depending on the communication partner).
The following entities are important:
SAP MII that sense it plays an important role in various business processes and integration scenarios and hence should be subject to monitoring. Monitoring tools exist locally in SAP MII, but several customers requested to have monitoring functions available centrally in SAP Solution Manager.
The following minimum system requirements apply:
Note that metrics "Number of failed JCo messages", "Number of intermediate JCo messages", "Number of successful JCo messages", and "Average time to process JCo messages" require to have at least:
See also SAP note 2377889 - System requirements for SAP MII monitoring via Interface & Connection Monitoring.
| Metric Name | Description | MAI Category | Since SP |
|---|---|---|---|
Number of schedulers in critical status |
This metric calculates the number of MII schedulers in a critical status (PENDING or STOPPED). |
Availability | 7.2 SP03 |
| Number of unavailable data servers | This metric measures the number of MII data servers which are currently unavailable. | Availability | 7.2 SP03 |
| Number of failed JCo messages | This metric calculates the number of JCo messages which are currently in a failed status (Failed, NoRuleDefine, Duplicate, Undefined). |
Exceptions | 7.2 SP03 |
| Number of failed MII transactions | This metric calculates the number of MII transactions which are currently in a failed status (Invalid, Failed, Terminated, Exception). |
Exceptions | 7.2 SP03 |
| Number of intermediate JCo messages | This metric calculates the number of JCo messages which are currently in an intermediate status (Received, Running). |
Exceptions | 7.2 SP03 |
| Number of intermediate MII transactions | This metric calculates the number of MII transactions which are currently in an intermediate status (Pending, Running). |
Exceptions | 7.2 SP03 |
| Average time to process JCo messages | This metric calculates the average processing time of all successfully processed JCo messages (measured in ms). The processing time is the time between creation of the JCo message until it reached a final (successful) status. The average processing time is calculated as the mean average processing time of all JCo messages. | Performance | 7.2 SP03 |
| Average time to process MII transactions | This metric calculates the average processing time of all successfully processed MII transactions (measured in ms). The processing time is the time between creation of the MII transaction until it reached a final (successful) status. The average processing time is calculated as the mean average processing time of all MII transactions. | Performance | 7.2 SP03 |
| Number of successful JCo messages | This metric calculates the number of JCo messages which are currently in a successful status (Processed, Categorized). |
Performance | 7.2 SP03 |
| Number of successful MII transactions | This metric calculates the number of MII transactions which are currently in a successful status (Succeeded). | Performance | 7.2 SP03 |
The Interface and Connection Monitoring setup can be accessed via SAP Solution Manager Configuration (SOLMAN_SETUP).
To access the Integration Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Integration Monitoring → Interface and Connections.
Note: If you didn't perform the infrastructure configuration yet, follow the steps in Interface and Connection Monitoring Setup with SAP Solution Manager 7.2.
To enable the Interface and Connection Monitoring data provider to access the (J2EE-based) SAP MII server, an additional RFC destination of type G must be maintained in SAP Solution Manager.
Create HTTP RFC Destination to SAP MII:
In the Technical Settings tab, provide the host and the port of the MII server.
In the Logon & Security tab, select Logon with User / Basic Authentication.
Provide the name and the password of a suitable user existing in the SAP MII system. The user must have the XMII_ADMINISTRATOR authorization on the SAP MII side.
For details see SAP Note 2288124.
Navigate to Interface and Connection Monitoring and switch to the Define Scope step. You can create a new scenario or use an existing one. Make sure the sender and the receiver system are part of the Interface and Connection Monitoring scenario.
Create the Interface Channel:
Maintain the Interface:
Select Metrics:
On the Metrics tab, select the metrics you want to monitor. Note that the selected metrics are collected for each interface entered above.
Enter Metric Parameters:
Metric: Number of schedulers in critical status
Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
Scheduler Name: Name of the scheduler
Scheduler Class Name: Type of the scheduler
Scheduler Status: STOPPED or PENDING. Per default all critical statuses are taken into account, but you can overrule the default by explicitly setting the status to be monitored in this parameter.
Metric: Number of unavailable data servers
Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
Data Server name: Name of the data server/p>
Data Server connector type: Use the input help to find the correct connector type
Metrics: Number of failed JCo messages, Average time to process JCo messages, Number of successful JCo messages
Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
JCo message name: JCo connection name
JCo message type: RFC, IDOC or WebService.
Message listener name: Name of the message listener
JCo message status: Per default all failed/successful statuses are taken into account. You can overwrite the standard statuses here. Use the input help to see which statuses are available for each metric.
Selected time frame (mandatory): This parameter defines the starting point for data collection. Refer to Further Information for available parameters.
4) MII Server Time Zone: To provide the time zone of the MII server. Use the value help to select the right time zone. If no value is provided it is assumed that the MII server runs in the same time zone as the SAP Solution Manager system.
Metric: Number of intermediate JCo messages
Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
JCo message name: JCo connection name
JCo message type: RFC, IDOC or WebSer
vice.
M
essage listener name: name of the message listener
JCo message status: Per default all intermediate statuses are taken into account. You can overwrite the standard statuses here. Please use the input help to see which statuses are available for each metric.
Status age (minutes): This defines the minimum age a JCo message in intermediate status may have before it is taken into account by the data collector.
Selected time frame (mandatory): This parameter defines the starting point for data collection. Refer to Further Information for available parameters.
4) MII Server Time Zone: To provide the time zone of the SAP MII server. Use the value help to select the right time zone. If no value is provided it is assumed that the MII server runs in the same time zone as the SAP Solution Manager system.
Metric: Number of failed MII transactions
Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
Transaction Name: Name of the transaction
Server Name: Name of the server the transaction is running on
Running User: Name of the user running the transaction
Transaction Status: Per default all failed/successful statuses are taken into account. You can overwrite the standard statuses here. Please use the input help to see which statuses are available for each metric.
4) Selected time frame: This parameter defines the starting point for data collection. Refer to Further Information for available parameters.
4) MII Server Time Zone: To provide the time zone of the SAP MII server. Use the value help to select the right time zone. If no value is provided it is assumed that the MII server runs in the same time zone as the SAP Solution Manager system.
Metrics: Average time to process MII transactions
Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
Transaction Name: Name of the transaction
Server Name: Name of the server the transaction is running on
Running User: Name of the user running the transaction
4) Selected time frame: This parameter defines the starting point for data collection. Refer to Further Information for available parameters.
4) MII Server Time Zone: To provide the time zone of the SAP MII server. Use the value help to select the right time zone. If no value is provided it is assumed that the MII server runs in the same time zone as the SAP Solution Manager system.
Metric: Number of intermediate MII transactions
Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
Transaction Name: Name of the transaction
Server Name: Name of the server the transaction is running on
Running User: Name of the user running the transaction
Transaction Status: Per default all intermediate statuses are taken into account. You can overwrite the standard statuses here. Please use the input help to see which statuses are available for each metric.
Status Age (minutes): This defines the minimum age a MII transaction in intermediate status may have before it is taken into account by the data collector.
4) Selected time frame: This parameter defines the starting point for data collection. Refer to Further Information for available parameters.
4) MII Server Time Zone: To provide the time zone of the SAP MII server. Use the value help to select the right time zone. If no value is provided it is assumed that the MII server runs in the same time zone as the SAP Solution Manager system.
Metric: Number of successful MII transactions
Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
Transaction Name: Name of the transaction
Server Name: Name of the server the transaction is running on
Running User: Name of the user running the transaction
4) Selected time frame: This parameter defines the starting point for data collection. Refer to Further Information for available parameters.
4) MII Server Time Zone: To provide the time zone of the SAP MII server. Use the value help to select the right time zone. If no value is provided it is assumed that the MII server runs in the same time zone as the SAP Solution Manager system.
4) These parameters are only fully available as of SAP Solution Manager 7.2 SP07. However, you can implement SAP Note 2586900 to downport these parameters to earlier versions (SP03 - SP06).
You can maintain attributes as described in the Interface and Connection Monitoring Setup with SAP Solution Manager 7.2 on the Attributes tab.
Thresholds and the collection schedule are maintained in the next step of the guided procedure. Once you have maintained all your channels, click Next in the main guided procedure to move to the step Activation.
Maintain Thresholds and Schedule:
| Severity | Statuses Considered |
|---|---|
| Successful | Processed, Categorized |
| Intermediate | Received, Running |
| Failed | Failed, NoRuleDefined, Duplicate, Undefined |
| Severity | Statuses Considered |
|---|---|
| Failed | Invalid, Failed, Terminated, ExceptionInvalid |
| Intermediate | Pending, Running |
| Successful | Succeeded |
The Selected time frame parameter defines the starting point for data collection, by making use of dynamic placeholders. The end point for data collection is always the current point in time. The data collector evaluates the placeholders at runtime, and the data collection is restricted to this time frame accordingly.
The syntax for these parameters is as follows:
Syntax = {Placeholder}{Operator}{Offset}
The {Placeholder} has to be prefixed by a "$" sign. The optional {Offset} is entered as an integer value after the {Operator}. For {Operator}, you can choose the following signs:
Example: $TODAY-2 = day before yesterday
For the placeholder, the following keywords are available: