SAP MII - Application Operations Guide

PUBLICDocument Version: 15.2.0 – 2018-03-25

SAP MII - Application Operations Guide

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

Content

1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Important SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Technical System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4 Monitoring SAP MII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

5 Detailed Monitoring and Tools for Problem and Performance Analysis. . . . . . . . . . . . . . . . . . . . 9

6 Managing SAP MII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

7 High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

8 Software Change Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

9 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

10 Support Desk Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

11 Categories of System Components for Backup and Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2 PUBLICSAP MII - Application Operations Guide

Content

1 Getting Started

Designing, implementing, and running your SAP applications at peak performance, 24 hours a day, has never been more vital for your business success than now.

This guide provides a starting point for managing, maintaining, and running your SAP applications optimally. It contains specific information for various tasks and lists the tools to implement them. This guide provides references to the documentation required for these tasks, such as Master Guide and SAP Library.

Naming Conventions

In this document, apply the following:

Variable Description

NW750 NetWeaver Java Application Server

SAP MII - Application Operations GuideGetting Started PUBLIC 3

2 Important SAP Notes

SAP Note Number Title

1107033 How to display Java monitoring data of NW7.1 in CCMS (NW7.0)

617547 Sending alerts as mail and SMS

508140 Customer messages–Customer logon data

1014381 OutOfMemoryError with Java applets

1759717 Transactions in PENDING state for long duration

2355285 Transaction Threading and Interrupts


Important SAP Notes

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/1107033






3 Technical System Landscape

A typical SAP MII landscape is shown below:

NoteIt is not necessary that your landscape must contain all the systems as shown below.

SAP MII Landscape

SAP MII - Application Operations GuideTechnical System Landscape PUBLIC 5

Scenario/Component Matrix

This section provides an overview of MII business scenario:

Business ScenarioMandatory Software Units Other Components Optional Components Clients

Integrating Shop Floor with Enterprise Resource Planning (ERP) System

● SAPNW● AS JAVA● XMII MII_ADMIN

SAP ECC Plant Connectivity (PCo)

Data Historians like Aspentech IP21 or OSISoft PI

-

Plant Information Catalog


Plant Connectivity (Pco)

Data Historians like Aspentech IP21 or OSISoft PI

-

Developing MII Content using Manufacturing Data Objects, KPI Framework, Alert Framework, Query and Display Templates etc


- - -

MII Content using Business Objects Dashboards


- - Business Objects Dashboards

MII Content using Business Objects Crystal Reports


- Crystal Enterprise Server

Crystal Reports

Change Management of MII Configurations using Solution Manager


Solution Manager - -

Transport MII Configurations using CTS


ABAP CTS System - -


Technical System Landscape

4 Monitoring SAP MII

Within the management of SAP Technology, monitoring is an essential task. You can find more information about the underlying technology in the SAP Netweaver Administrator’s Guide - Technical Operations Manual in the SAP Library under SAP Netweaver Library.

Alert Monitoring

Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system environment. SAP provides you with the infrastructure and recommendations needed to set up your alert monitoring to recognize critical situations for SAP MII as quickly as possible.

OEE does not offer specific data in the Computer Center Management System (CCMS) for alert monitoring. Nevertheless general monitoring options can be used. In order to enable the auto-alert mechanism of CCMS, see SAP Note 617547 .

GRMG Monitoring

You use the Generic Request and Message Generator (GRMG) to monitor the availability of SAP MII. You need to specify the required configuration settings in a GRMG customizing file, which is transferred to CEN by a CCMS agent. For more information about the GRMG, see SAP Note 1758117 and 1826307 .

SAP MII provides the following Monitoring Tree Elements (MTE) under the scenario SAP xMII Monitor Templates SAP xMII Monitor Templates.

Expired Data Buffer Entry Count

Tracks the number of data buffer entries that expired and could not be sent to the remote servers. This count indicates to the administrator when the buffer needs to be cleaned.

Message Stats

Tracks the errors that occur while the system is processing incoming data messages and displays the associated name-value pairs.

Name Value

Server name Name of server

Number Received Number of message received

Process With Error Number of processing error

SAP MII - Application Operations GuideMonitoring SAP MII PUBLIC 7




Name Value

Process with Exception Number of processing Exception

No Rule Defined Number of message for which no rules defined

Mapped to Category Number of messages which are mapped to category

Number of Duplicate Number of duplicate messages

Server Stats

Tracks the request for a particular server and displays the associated name-value pairs.

Name Value

Server name Name of server

Number of hits Number of times the server was accessed

Rows returned Number of rows returned

Time to run Number of milliseconds the server took to process the request

Error count Number of errors encountered during the request

Communication error count Number of errors encountered while the system is trying to communicate with the server.

User Stats

Tracks the requests by a particular user and displays the associated name-value pairs. You can use this information to determine if a user is causing system instability by running large queries.

Name Value

Username Name of user

Number of requests Number of requests the server processed

Rows returned Number of items the user’s request returned

Component Specific Monitoring

The technology of SAP MII is based on SAP NetWeaver Java Application Server. This guide covers only the differences and additional information specific to this solution.


Monitoring SAP MII

5 Detailed Monitoring and Tools for Problem and Performance Analysis

Trace and Log Files

Trace files and log files are essential for analyzing problems.

The technology of SAP MII is based on SAP NetWeaver Java Application Server. This guide covers only the differences and additional information specific to this solution.

Trace files and log files are essential for analyzing problems. SAP MII uses the standard SAP NetWeaver CE logging infrastructure. SAP MII log and trace information is written to the following files:

● Application● DefaultTrace

The logging level is controlled by SAP NetWeaver CE. To view these files, use the standard SAP NetWeaver CE logging utilities. If you show logging categories, the SAP MII files are written to the base category /Applications/XMII and include subcategories.

Following are the Logging categories available in SAP MII:

● /Applications/XMII/Illuminator● /Applications/XMII/Connector● /Applications/XMII/Service● /Applications/XMII/Template● /Applications/XMII/Content● /Applications/XMII/Configuration● /Applications/XMII/SPC● /Applications/XMII/ActivePortal● /Applications/XMII/Scheduler● /Applications/XMII/Import_Export● /Applications/XMII/MessageListener● /Applications/XMII/Monitoring● /Applications/XMII/PermissionCheck● /Applications/XMII/Xacute● /Applications/XMII/Xacute/Event● /Applications/XMII/Xacute/Runner● /Applications/XMII/Xacute/SOAPRunner● /Applications/XMII/ContentManagement● /Applications/XMII/ContentManagementPerformance● /Applications/XMII/TAG_CATALOG● /Applications/XMII/ALERT● /Applications/XMII/PlantInformationCatalog● /Applications/XMII/PlantInformationMaintenance

SAP MII - Application Operations GuideDetailed Monitoring and Tools for Problem and Performance Analysis PUBLIC 9

If you show tracing locations, the SAP MII files are written to com.sap.xmii.*.

For OEE, the logging locations in SAP NetWeaver are:

● General logging category: /Applications/OEE/Common● Log security related category: /System/Security/Audit/OEE/SecurityLog● Tracing location: com.sap.xapps.mpm

If you show logging categories, the OEE files are written to the base category /Applications/OEE and include subcategories.

If you show tracing locations, the OEE files are written to com.sap.xapps.mpm.*.

Other Important Problem Analysis and Monitoring Tools

Transaction Manager can be used to analyze problems related to BLS transactions in SAP MII. You can view transaction logs in Transaction Manager. Choose System Management Transaction Manager.

Interface Monitors

Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP.

Interface Detailed Description Technology Used

Message Listener Message Listener servers are used for communication between plant and SAP ERP systems.

RFC. IDOC, HTTP,Webservice.

Monitor tools for these Interfaces:

Interface Monitor Detailed Description Prerequisites

Message Listener Message Monitor Message Monitor is used to monitor all incoming messages to SAP MII 15.5

SAP xMII Administrator can create a number of Message Listener Servers for RFCs and IDocs. All incoming message can be monitored

Data Retention

OEE retains data for the duration you specify. You can specify the retention time on the Customization Configuration tab in the OEE User Assignment screen. To do this, on the SAP MII main menu screen, choose

Worker UI Management General Configuration. .


Detailed Monitoring and Tools for Problem and Performance Analysis

You maintain the retention time for data of an entire plant.

The file path to the two transactions used to delete data are:

● SAPMPM/apps/DataArchive/ArchiveHANAReplicatedTables: This deletes data already replicated to SAP HANA

● SAPMPM/apps/DataArchive/ArchiveNonHANAReplicatedTables: This deletes data not replicated to SAP HANA.

All transactional data is deleted after the retention period. Master data is not deleted.

You can either create schedulers for these transactions or run the transactions manually.

SAP MII - Application Operations GuideDetailed Monitoring and Tools for Problem and Performance Analysis PUBLIC 11

6 Managing SAP MII

Administrative tools for SAP MII are configured using SAP NetWeaver.

SAP MII administration screens are available at http://<server>:<port>/XMII/Menu.jsp.

To maintain the general SAP MII configuration, on the SAP MII administration menu, choose System Management System Administration . You can set the following system properties:

Property Description

BinarySizeLimit Specifies the maximum number of kilobytes that can be posted to a transaction

Description Defines the system configuration

JobHistoryCleanup Defines the amount of time a scheduled job is maintained before being purged

Language Sets the default system language; logon accounts have a language setting that overrides the system setting

Disable Indexing Disables indexing of deployed content.

MDODataSource JNDI name for MDO configuration; used to store the persistent information for defined objects

CleanupInterval Defines the interval in which the message processing rule and Alert processing rule history is maintained

MonitoringRetentionDuration Defines the setting for purging the usage statistics table

Name Identifies the base system configuration

ProxyBypassList Defines a comma-separated list of servers and URLs that bypass the proxy server; you can include a wildcard character such as wdf.sap.*

ProxyHost Defines the local proxy server; the system uses this value to access virtual servers in other locations

ProxyPort Identifies the port that the system uses to communicate with the local proxy server

ProxyUserName Identifies the user name for authentication

ProxyUserPassword Defines the password for authentication; the password value is encoded


Managing SAP MII


RegisterSystemLandscapeDirectory Defines the flag indicating that SAP MII is registered in SAP NetWeaver CE SLD

ResolveMachineName Enhances the logging information; If you select this checkbox, the system finds the source machine name using the configured machine's domain name system for each request to the server. If you deselect the checkbox, the system records the IP address of the request machine.

RetentionTimeUsageStatistics Defines the amount of time to store the content usage statistics

SessionTimeOut Defines the amount of time in minutes the system takes to automatically close inactive sessions

TransactionCacheDuration Defines how many hours a transaction is included in the system cache

TransactionPersistenceLifetime Defines the amount of time to store a transaction record before purging

WSDLGenSecurityEnabled If this checkbox is selected, the system requires you to log on before you can access the WSDLGen servlet; if this checkbox is not selected, any user can call the servlet to generate WSDL for a transaction; however, you must still have permission to run the transaction

ExpressionCacheDuration Defines the duration for which expression are cached in MII for faster execution

CatalogLogsCleanupIntervals Defines the interval in which the Catalog logs get cleaned up

FTPFileTransferTimeout Defines the amount of time in minutes the system takes to timeout a FTP file transfer

MDOBatchProcessing Enables MDO database operations in batches if the selected database supports batch operations

NetWeaverDataSourceCaching Defines the duration for which NetWeaver data source will be cached

UsageStatusMonitoring Enables the monitoring of transactions and query usage when value is set to true

TransactionCaching Enables the caching of transaction for faster execution if value is set to true

MaxRowCount Defines the query limit of 1,20,000 rows

SAP MII - Application Operations GuideManaging SAP MII PUBLIC 13


EncodeSOAPResponse Encodes SOAP response

TemplateCaching Enables query template caching within SAP MII for faster execution

Use Transaction Threading Configures the transaction engine to use the new threading model

Use Basic Threading Configuration Uses a simple cached thread pool, unable to be configured further

Use Action Threading Configures the transaction engine to use threading for action

Trx Engine Core Threads Sets the amount of core threads for the transaction threading pool

Trx Engine Max Threads Sets the amount of maximum allowed threads for the transaction threading pool

Trx Engine Keepalive Sets the amount of time a thread is kept alive while inactive before destroying the thread

Trx Engine Direct Handoff Flag Determines if the threading pool uses a blocking queue or performs a direct handoff to the thread pool

Trx Engine Blocking Queue Size Determines the size of the blocking queue. Not used if the direct handoff flag is enabled.

Starting and Stopping

To start or stop SAP MII, do the following:

1. Choose SAP NetWeaver Administrator Operation Management Systems Start & Stop .2. Choose the Java EE Applications tab page and search for xapps~xmii~ear and xapps~xmii~jraapp.3. Start or stop the applications.

Start and Stop Sequences and Tools

Software Component Start and Stop Sequences and Tools

Sequence Tool Detailed Description

xapps~xmii~ear 1 SAP NetWeaver Administrator

Start & Stop

see the SAP MII Installation Guide


Managing SAP MII



xapps~xmii~jraapp 2 SAP NetWeaver Administrator

Start & Stop

see the SAP MII Installation Guide

For information on starting SAP MII, see the SAP MII Installation Guide.

For the OEE_ERP component:

The Stop Sequence is in reverse order to the Start Sequence.

Start and Stop Sequences and Tools



SAP ERP 1 STARTSAP/STOPSAP (Unix) Microsoft Management Console (Windows)

For more information, see

the SAP NetWeaver Technical Operation Manual

General Administration

Tasks Starting and Stopping SAP NetWeaver

ABAP and Java .

SAP Overall Equipment Effectiveness Management Add-On

2 STARTSAP/ STOPSAP (Unix) Microsoft Management Console (Windows)

For more information, see

the SAP NetWeaver Technical Operation Manual

General Administration

Tasks Starting and Stopping SAP NetWeaver

ABAP and Java

Software Configuration for OEE_ERP component

This chapter explains which components or scenarios used by this application are configurable and which tools are available for adjusting. The Implementation Guide (IMG) is the standard SAP tool for component Customizing. To display the Implementation Guide (IMG) on the SAP Easy Access screen choose ToolsCustomizing IMG Execute Project (transaction SPRO) . Customizing settings for SAP Overall Equipment Effectiveness can be found under Production Overall Equipment Effectiveness .

The appearance of the frontend component is configured via the frontend administration tool.


Administration Tools

Software Component Transaction/Tool Detailed Description

MII 15.5 System Management System Management can be used to administer various MII Objects like transaction manager, Schedulers, Active sessions and content usage.

OEE Management is based on SAP NetWeaver. For more information, see the Technical Operations Manual for SAP NetWeaver in SAP Library at help.sap.com SAP NetWeaver SAP NetWeaver 7.5 SAP NetWeaver Library Administrator’s Guide Technical Operations for SAP NetWeaver.

Backup and Restore

You need to back up your system landscape regularly to ensure that you can restore and recover it in case of failure.

The backup and restore strategy for SAP MII consists of the following:

● Backup and restore coverage for each component● Cross-system data dependencies and handling

The backup and restore strategy for your system landscape should not only consider SAP systems but should also be embedded in overall business requirements and incorporate your company’s entire process flow.

In addition, the backup and restore strategy must cover disaster recovery processes, such as the loss of a data center through fire. It is most important in this context that you ensure that backup devices are not lost together with normal data storage (separation of storage locations).

Based on the type of application data contained in a component, we have introduced a categorization scheme for system components that can be used to analyze the backup requirements of any system component and to easily determine an appropriate backup method for this component.

SAP MII data is stored in the SAP NetWeaver database; therefore, you can use the SAP NetWeaver Java Application Server backup process to back up SAP MII.


Managing SAP MII

For OEE_ERP component, the following table lists the components used by OEE Management and how to back them up:

Component Data to be backed up Backup Method / Tool Recommended Backup Frequency

Backup Sequence (if required)

SAP ERP (including Overall Equipment Effectiveness Add-on)

Database and log backup, application log backup (such as job logs in file system), data consistency with other systems must be considered. Backup of software, configuration, log files.

See SAP ERP Application Operations Guide.



The user settings of the frontend component are stored in the local user application data directory of the windows operating system. It is recommended to backup this data within the windows backup.

Periodic Tasks

This chapter describes all automatable tasks required to run periodically in order to keep the application running smoothly over time. Such tasks may be required on component level and are therefore relevant in each scenario that uses the component. You can find the mapping in the chapter Scenario / Component Matrix above. Other tasks may be relevant for certain business scenarios only. It is important that you monitor the successful execution of these tasks on a regular basis.

SAP MII has following system jobs which runs periodically:

Name Description Frequency (Min)

Activation Request Cleaner Clean activation request IDs that are older than 7 days

1440,0

Alert Expiration Job Job for checking expired alerts 60,0

Catalog Delete Old Logs Delete old tag catalog logs 1440,0

Catalog Scan Inactive Tags Check for deleted tags in plant historians

1440,0

Data Buffer Job Scanner Process items in the data buffer queue 1,0

Indexing Cleaner Clean bad file references from indexing 1440,0

JCO Connection Monitor Clean JCo connections whose timeout has been reached

0,0


Name Description Frequency (Min)

Job History Cleaner Clean job history table 30,0

MDO Data Source Watcher MDO Data Source Watcher 360,0

MDO Log Cleanup MDO Log Cleanup 720,0

Message Sequence Cleaner Remove message sequences that have no messages under them

1440,0

Monitor Data Cleaner Remove monitoring data older than the specified number of days

1440,0

Query Cache Scanner Process items in the query cache 1440,0

SQL Connection Timeout Monitor Clean SQL connections for connections that exceeded timeout

0,2

Security Object Reference Cleaner Clean obsolete references to users and roles

10080,0

Session Logger Log session information 30,0

Shared Property Cleanup Remove expired properties 1,0

Temp File Cleaner Clean Temp file table 60,0

Template Cache Cleaner Clean the in memory templates 5,0

Transaction Cache Cleaner Clean transactions from memory 5,0

Load Balancing

Logging on and load balancing for SAP MII is handled by SAP NetWeaver Java Application Server. SAP MII data is stored in the SAP NetWeaver Java Application Server database.

For more information in NW 750, see Server Selection and Load Balancing Using the SAP Web Dispatcher in the SAP NetWeaver Library on the SAP Help Portal at http://help.sap.com/nwce SAP NetWeaver Composition Environment Library .

For more information on load balancing, see help.sap.com SAP NetWeaver SAP NetWeaver 7.0 including Enhancement Package 3 System Administration and Maintenance Information Technical Operation GuideGeneral Administration Tasks High Availability Network High Availability Web Server Networks and DMZs .


Managing SAP MII

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnwce

7 High Availability

SAP MII does not include a recovery mechanism for a system crash. When the SAP NetWeaver server is restarted, the SAP MII application is restarted. For more information on disaster recovery steps in SAP NetWeaver, see topic SAP High Availability in SAP NetWeaver guides.

In a clustered environment, SAP NetWeaver may handle machine failover. However, running status of the machine that crashed is lost.

OEE_ERP is part of SAP ERP, which means that all high availability measures for SAP ERP also apply for SAP Overall Equipment Effectiveness Management. In particular, you can protect OEE from downtimes using redundancy approaches such as installations on at least two different runtime environments or physical machines. A load balancing or dispatching mechanism ensures that in case of a downtime of one runtime or physical machine the remaining ones can handle all requests.

When a machine running SAP ERP crashes, users who are logged on to the SAP Overall Equipment Effectiveness Management user interface get error messages that the connection to SAP ERP has been lost.

For more information, see SAP Help Portal at http://help.sap.com SAP NetWeaver SAP NetWeaver 7.0 including Enhancement Package 3 System Administration and Maintenance Information Technical Operation Guide General Administration Tasks High Availability SAP NetWeaver AS ABAP: High Availability .

SAP MII - Application Operations GuideHigh Availability PUBLIC 19

8 Software Change Management

Software Change Management standardizes and automates software distribution, maintenance, and testing procedures for complex software landscapes and multiple software development platforms. These functions support your project teams, development teams, and application support teams.

The goal of Software Change Management is to establish consistent, solution-wide change management that allows for specific maintenance procedures, global rollouts (including localizations), and open integration with third-party products.

The following topics are covered:

● Transport and Change Management: Enables and secures the distribution of software changes from the development environment to the quality assurance and production environment.

● Development Request and Development Release Management: Enables customerspecific maintenance procedures and open integration with third-party products.

● Template Management: Enables and secures the rollout of global templates, including localizations.● Quality Management and Test Management: Reduce the time, cost, and risk associated with software

changes.● Support Packages and SAP Notes Implementation: Provide standardized software distribution and

maintenance procedures.● Release and Upgrade Management: Reduces the time, cost, and risk associated with upgrades.

Transport and Change Management

SAP MII 15.5 has lot of configurations for different functionalities such as data servers, time periods and so on. The configurations in one MII instance can be imported on other MII instances in the system landscape. The import/export functionality is available in the Configurations screen. You can transport your configurations from SAP MII system to another system using Enhanced Change and Transport System (CTS+). Enhanced Change and Transport System (CTS+) is a tool to execute and monitor the transports from SAP MII system to different systems. CTS+ is an extension of the existing Change and Transport system (CTS). You use this tool to organize, monitor and transport changes between SAP systems in your system landscape. You have to create objects on the development system, attach them to a transport request which is distributed in your landscape using CTS+.

The integration of Solution Manager system with SAP MII enables you to view all the configurations present in SAP MII system from the Solution Manager system. You can perform the standard analyses, Root-cause Analysis and Change Analysis that are available in the Solution Manager system.

On configuring the solution manager system with SAP MII system, the following configurations are available:

● System Properties● Scheduled Jobs● Data Server Permissions● Data Servers● Time Periods


Software Change Management

● Time Period Schedules● Message Listeners● Message Listener Rules● Message Listener Cleanup Rules● Localization● Links● Navigation● Globals● Unit Conversions● Custom Attributes● Credential Store● Connection Store● NWDI Properties● Alert Cleanup Rules● File Usage Statistics● Project details● Plant Information Catalog● OEE_MII component has three configuration objects, for example, status, activity and production operator

dashboard (POD). As of now there is no way to transport these configurations. OEE CTC template takes care of creation of default data for these entries. OEE also supports extension possibilities where in customer can write an SAP MII transaction and plugin to a list of extension points. Change management for the same is handled by SAP MII workbench with NWDI integration.Other than the above mentioned scenarios there is no need of transport and change management.OEE_ERP component is an ERP Add-on is client-enabled. For transport and change management issues, the procedures of SAP NetWeaver apply.For more information, see SAP NetWeaver documentation.OEE frontend component is installed locally using SAPsetup. If you want to change the installation, you can rerun SAPsetup from Start Control Panel Add or Remove Programs to add or remove the program .

SAP MII Content Development

SAP MII 15.5 enables you to use NetWeaver Development Infrastructure (NWDI) capabilities for SAP MII content development. This covers all software development lifecycle steps like definition of your software structure, content versioning, content packaging, and content transportation within system landscape.

Before working with SAP MII Content management, you must decide to use simple content versioning or more advanced features such as content packaging and distribution. You should configure the SAP MII–NWDI integration in accordance.

Simple content versioning extends SAP MII Workbench functionality with content check-out and check-in functionality and synchronize to version capabilities. For more information, see http://help.sap.com SAP Business Suite SAP Manufacturing Integration and Intelligence .

In extended content development, you can build, activate, and transport SAP MII Content as described in the NWDI development process. For more information, see Software Components and Software Change Management at http://help.sap.com/nwce .

SAP MII - Application Operations GuideSoftware Change Management PUBLIC 21

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com


You must integrate SAP MII 15.5 with the SAP NWDI to leverage NWDI capabilities. For more information about the NWDI integration, see the SAP MII 15.5 Installation Guide.

You do not need NWDI installed in your system landscape if you want to deploy and run SAP MII Content delivered by SAP. This content is deployed to your SAP MII system with standard SAP deployment tools.

Development Requests and Development Release Management

The standard procedures of SAP NetWeaver Java Application Server apply. See the Library for SAP NetWeaver 7.50 on the SAP Help Portal at http://help.sap.com/nwce .

Quality Management and Test Management

You can use NWDI to learn about the various possibilities to test your software changes.

Support Packages and Patch Implementation

We recommend implementing Support Package Stacks (SP-Stacks), which are sets of Support Packages and patches for the respective product version that must be used in the given combination.

You can find detailed information about the availability of SP-Stacks for SAP MII on the SAP Support Portal.

For information about the tools necessary for implementing patches, see the SAP Help Portal at http://help.sap.com/nwce SAP NetWeaver Composition Environment Software Life Cycle Management.


Software Change Management




9 Troubleshooting

To troubleshoot SAP MII 15.5, check the logs by setting the logging level to ALL and viewing the tracing locations for errors.

For general troubleshooting information, see the SAP NetWeaver Java Application Server on the SAP Help Portal. See the SAP Technology Troubleshooting guide on http://wiki.sdn.sap.com/wiki/display/TechTSG .

SAP MII - Application Operations GuideTroubleshooting PUBLIC 23

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwiki.sdn.sap.com%2Fwiki%2Fdisplay%2FTechTSG

10 Support Desk Management

Support Desk Management enables you to set up an efficient internal support desk for your support organization that integrates your users, internal support employees, partners, and SAP Active Global Support specialists with an efficient problem resolution procedure.

For support desk management, you need the methodology, management procedures, and tools infrastructure to run your internal support organization efficiently.

Remote Support Setup

For information about SAP support requests for access to your SAP MII data, see SAP Note 508140 .

A support user with an SAP MII read-only role, SAP_XMII_Read_Only, is used to log into the SAP MII administration tool.

Problem Message Handover

To send SAP MII problem messages or tickets to SAP support, use the appropriate component from the following SAP MII component hierarchy in the SAP Customer Support System:

● MFG○ MFG-MII (SAP Manufacturing Integration and Intelligence)

○ MFG-MII-CON (SAP MII Content)○ MFG-MII-CORE (SAP MII Core Development)

○ MFG-MII-CORE-BSC (Business Suite connectivity)○ MFG-MII-CORE-DTE (SAP MII Design Time Environment)○ MFG-MII-CORE-RTE (SAP MII Runtime Environment)

○ MFG-MII-SFC (Shop floor connectivity)○ MFG-MII-SFC-PCO (Plant connectivity)○ MFG-MPM (Manufacturing Performance Management) This is the component for OEE.

You should provide the release number in your message.


Support Desk Management


11 Categories of System Components for Backup and Restore

Categories of System Components Category Properties Suggested Methods for Backup and Restore

I Only software, no configuration, or application data

● No backup, new installation in case of a recovery

● Initial software backup after installation and upgrade

● Backup of log files

II Only software and configuration information, no application data

● Backup after changes have been applied

● No backup, new installation, and configuration in case of a recovery

● Backup of log files

III Only replicated application data, replication time is sufficiently small for a recovery

● No data backup needed● Backup of software, configuration,

log files

IV Only replicated application data, backup recommended because replication time is too long, data not managed by a DBMS

● Application specific file system backup

● Multiple instances● Backup of software, configuration,

log files

V Only replicated application data, backup recommended because replication time is too long, data managed by a DBMS

● Database and log backup● Multiple instances● Backup of software, configuration,

log files

VI Original application data, standalone system, data not managed by a DBMS

● Application specific file system backup

● Backup of software, configuration, log files

VII Original application data, standalone system, data managed by a DBMS, not based on SAP WebAS

● Database and log backup● Backup of software, configuration,

log files

SAP MII - Application Operations GuideCategories of System Components for Backup and Restore PUBLIC 25

Categories of System Components Category Properties Suggested Methods for Backup and Restore

VIII Original application data, standalone system, based on SAP WebAS

● Database and log backup, application log backup (such as job logs in file system)


IX Original application data, data exchange with other systems, data not managed by a DBMS

● Application specific file system backup, data consistency with other systems must be considered


X Original application data, data exchange with other systems, data managed by a DBMS, not based on SAP WebAS

● Database and log backup, data consistency with other systems must be considered


XI Original application data, data exchange with other systems, based on SAP WebAS

● Database and log backup, application log backup (such as job logs in file system), data consistency with other systems must be considered



Categories of System Components for Backup and Restore

Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External PlatformsSome videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free LanguageSAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders, and abilities.

SAP MII - Application Operations GuideImportant Disclaimers and Legal Information PUBLIC 27

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html

Documents

SAP MII - Application Operations Guide