MII

Application Operations GuideDocument version: 1.1 2015-01-27

SAP Manufacturing Integration and Intelligence 15.0

PUBLIC

Document History

CautionBefore you start the implementation, make sure you have the latest version of this document. You can find the latest version at service.sap.com/instguides.

The following table provides an overview of the most important document changes.

Table 1Version Date Description1.0 2014-05-16 Initial installation1.1 2015-01-27 Updated Versions

2PUBLIC&FP_Copyright;

SAP Manufacturing Integration and Intelligence 15.0Document History

Content

1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Technical System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 Monitoring SAP MII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

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

6 Managing SAP MII . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

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

A Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27A.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

SAP Manufacturing Integration and Intelligence 15.0Content

PUBLIC&FP_Copyright; 3

4PUBLIC&FP_Copyright; SAP Manufacturing Integration and Intelligence 15.0

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 ConventionsIn this document, apply the following:Table 2Variable Description

NW 731 SP11 NW740 SP06

NetWeaver Java Application Server

SAP Manufacturing Integration and Intelligence 15.0Getting Started


2 Important SAP Notes

Table 3SAP 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 messagesCustomer logon data

1014381 OutOfMemoryError with Java applets

1759717 Transactions in PENDING state for long duration


SAP Manufacturing Integration and Intelligence 15.0Important SAP Notes

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.

Figure 1: SAP MII Landscape

Scenario/Component MatrixThis section provides an overview of MII business scenario:Table 4Business Scenario Mandatory Software

UnitsOther 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

-

SAP Manufacturing Integration and Intelligence 15.0Technical System Landscape


Business Scenario Mandatory Software Units

Other Components Optional Components Clients

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 - -


SAP Manufacturing Integration and Intelligence 15.0Technical 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 Administrators Guide - Technical Operations Manual in the SAP Library under SAP Netweaver Library.

Alert MonitoringProactive, 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 MonitoringYou 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 CountTracks 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 StatsTracks the errors that occur while the system is processing incoming data messages and displays the associated name-value pairs.Table 5Name Value

Server name Name of server

Number Received Number of message received

Process With Error Number of processing error

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 StatsTracks the request for a particular server and displays the associated name-value pairs.

SAP Manufacturing Integration and Intelligence 15.0Monitoring SAP MII


Table 6Name 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 StatsTracks 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.Table 7Name Value

Username Name of user

Number of requests Number of requests the server processed

Rows returned Number of items the users request returned

Component Specific MonitoringThe 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.


SAP Manufacturing Integration and Intelligence 15.0Monitoring SAP MII

5 Detailed Monitoring and Tools for Problem and Performance Analysis

Trace and Log FilesTrace 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 Manufacturing Integration and Intelligence 15.0Detailed Monitoring and Tools for Problem and Performance Analysis


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 ToolsTransaction 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 MonitorsInterface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP.Table 8Interface 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:Table 9Interface Monitor Detailed Description Prerequisites

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

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

Data RetentionOEE 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. .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 Manufacturing Integration and Intelligence 15.0Detailed Monitoring and Tools for Problem and Performance Analysis

6 Managing SAP MII

Administrative tools for SAP MII are configured using SAP NetWeaver.SAP MII administration screens are available at :/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:Table 10Property 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

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

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

SAP Manufacturing Integration and Intelligence 15.0Managing SAP MII


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

EncodeSOAPResponse Encodes SOAP response

TemplateCaching Enables query template caching within SAP MII for faster execution

Starting and StoppingTo 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



Table 11Software 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

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 on the SAP Service Marketplace at service.sap.com/instguides SAP Business Suite Applications SAP Manufacturing SAP Manufacturing Integration and Intelligence SAP MII 15.0 .

For the OEE_ERP component:The Stop Sequence is in reverse order to the Start Sequence.Start and Stop Sequences and ToolsTable 12Software Component Start and Stop Sequences and Tools

Sequence Tool Detailed Description

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

For more information, see the SAP NetWeaver Technical

Operation Manual General Administration TasksStarting 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 TasksStarting and Stopping SAP NetWeaver ABAP and Java

Software Configuration for OEE_ERP componentThis 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 Tools CustomizingIMG 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 ToolsTable 13Software Component Transaction/Tool Detailed Description

MII 15.0 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.31 SAP NetWeaver Library Administrators Guide Technical Operations for SAP NetWeaver.

Backup and RestoreYou 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 companys 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. For more information about backing up and restoring your SAP NetWeaver Java Application Server system, see the SAP Help Portal at help.sap.com/nwce SAP Business Suite SAP Manufacturing SAP Manufacturing Integration and Intelligence .For OEE_ERP component, the following table lists the components used by OEE Management and how to back them up:Table 14Component Data to be backed up Backup Method / Tool Recommended

Backup FrequencyBackup 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 TasksThis 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:Table 15Name 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

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



Name Description Frequency (Min)

Transaction Cache Cleaner Clean transactions from memory 5,0

Load BalancingLogging 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 730, see Server Selection and Load Balancing Using the SAP Web Dispatcher in the SAP NetWeaver Library on the SAP Help Portal at help.sap.com/nwce SAP NetWeaver Composition Environment Library .For more information in NW CE 730 EHP1, see SAP Application Server List for HTTP Load Balancing in the SAP NetWeaver Library on the SAP Help Portal at help.sap.com/nwce SAP NetWeaver Composition Environment Library .For more information on load balancing, see SAP Service Marketplace at help.sap.com SAP NetWeaver SAP NetWeaver 7.0 including Enhancement Package 3 System Administration and Maintenance InformationTechnical Operation Guide General Administration Tasks High Availability Network High Availability Web Server Networks and DMZs .



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 SAP High Availability [external document].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 Manufacturing Integration and Intelligence 15.0High Availability


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 customer-specific 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 ManagementSAP MII 15.0 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 15.0 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 Time Period Schedules Message Listeners Message Listener Rules


SAP Manufacturing Integration and Intelligence 15.0Software Change Management

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 DevelopmentSAP MII 15.0 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 MIINWDI 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 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 help.sap.com/nwce.You must integrate SAP MII 15.0 with the SAP NWDI to leverage NWDI capabilities. For more information about the NWDI integration, see the SAP MII 15.0 Installation Guide on the SAP Service Marketplace at service.sap.com

SAP Business Suite Applications SAP Manufacturing SAP Manufacturing Integration and Intelligence SAP MII 15.0 .



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 ManagementThe standard procedures of SAP NetWeaver Java Application Server apply. See the Library for SAP NetWeaver 7.1, SAP NetWeaver 730 and NW 730 EHP1 on the SAP Help Portal at help.sap.com/nwce.

Quality Management and Test ManagementYou can use NWDI to learn about the various possibilities to test your software changes.

Support Packages and Patch ImplementationWe 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 Service Marketplace at service.sap.com/sp-stacks.For more information about the implementation of support packages and possible issues, see service.sap.com/patches SAP Support Packages in Detail .For information about the tools necessary for implementing patches, see the SAP Help Portal: NW 730: help.sap.com/nwce SAP NetWeaver Composition Environment Software Life Cycle

Management. NW730 EHP1help.sap.com/nwce Administration of SAP NetWeaver CE General System Administration

Software Life Cycle Management.



9 Troubleshooting

To troubleshoot SAP MII 15.0, 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: NW 730: See the SAP Technology Troubleshooting guide on wiki.sdn.sap.com/wiki/display/TechTSG. SAP NetWeaver Composition Environment (SAP NetWeaver CE) 7.1 EHP1 SP05:help.sap.com/nwce

Administration of SAP NetWeaver CE Troubleshooting SAP NetWeaver CE/

SAP Manufacturing Integration and Intelligence 15.0Troubleshooting


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 SetupFor 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 HandoverTo 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-MII-SFC-UDS (Universal data services) MFG-MPM (Manufacturing Performance Management)

You should provide the release number in your message.


SAP Manufacturing Integration and Intelligence 15.0Support Desk Management

11 Categories of System Components for Backup and Restore

Table 16Categories 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 filesII 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

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

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

SAP Manufacturing Integration and Intelligence 15.0Categories of System Components for Backup and Restore


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

log files

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



SAP Manufacturing Integration and Intelligence 15.0Categories of System Components for Backup and Restore

A Reference

A.1 The Main SAP Documentation TypesThe following is an overview of the most important documentation types that you need in the various phases in the life cycle of SAP software.

Cross-Phase DocumentationSAPterm is SAPs terminology database. It contains SAP-specific vocabulary in over 30 languages, as well as many glossary entries in English and German. Target group:

Relevant for all target groups Current version:

On SAP Help Portal at help.sap.com Glossary In the SAP system in transaction STERM

SAP Library is a collection of documentation for SAP software covering functions and processes. Target group:

Consultants System administrators Project teams for implementations or upgrades

Current version: On SAP Help Portal at help.sap.com (also available as documentation DVD)

The security guide describes the settings for a medium security level and offers suggestions for raising security levels. A collective security guide is available for SAP NetWeaver. This document contains general guidelines and suggestions. SAP applications have a security guide of their own. Target group:

System administrators Technology consultants Solution consultants

Current version: On SAP Service Marketplace at service.sap.com/securityguide

ImplementationThe master guide is the starting point for implementing an SAP solution. It lists the required installable units for each business or IT scenario. It provides scenario-specific descriptions of preparation, execution, and follow-up of an implementation. It also provides references to other documents, such as installation guides, the technical infrastructure guide and SAP Notes. Target group:

Technology consultants

SAP Manufacturing Integration and Intelligence 15.0Reference


Project teams for implementations Current version:

On SAP Service Marketplace at service.sap.com/instguidesThe installation guide describes the technical implementation of an installable unit, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. Target group:

Technology consultants Project teams for implementations

Current version: On SAP Service Marketplace at service.sap.com/instguides

Configuration Documentation in SAP Solution Manager SAP Solution Manager is a life-cycle platform. One of its main functions is the configuration of business scenarios, business processes, and implementable steps. It contains Customizing activities, transactions, and so on, as well as documentation. Target group:

Technology consultants Solution consultants Project teams for implementations

Current version: In SAP Solution Manager

The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The Customizing activities and their documentation are structured from a functional perspective. (In order to configure a whole system landscape from a process-oriented perspective, SAP Solution Manager, which refers to the relevant Customizing activities in the individual SAP systems, is used.) Target group:

Solution consultants Project teams for implementations or upgrades

Current version: In the SAP menu of the SAP system under Tools Customizing IMG

Production OperationThe technical operations manual is the starting point for operating a system that runs on SAP NetWeaver, and precedes the application operations guides of SAP Business Suite. The manual refers users to the tools and documentation that are needed to carry out various tasks, such as monitoring, backup/ restore, master data maintenance, transports, and tests. Target group:

System administrators Current version:

On SAP Service Marketplace at service.sap.com/instguidesThe application operations guide is used for operating an SAP application once all tasks in the technical operations manual have been completed. It refers users to the tools and documentation that are needed to carry out the various operations-related tasks. Target group:

System administrators



Technology consultants Solution consultants


UpgradeThe upgrade master guide is the starting point for upgrading the business scenarios and processes of an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an upgrade. It also refers to other documents, such as upgrade guides and SAP Notes. Target group:

Technology consultants Project teams for upgrades


The upgrade guide describes the technical upgrade of an installable unit, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. Target group:

Technology consultants Project teams for upgrades


Release notes are documents that contain short descriptions of new features in a particular release or changes to existing features since the previous release. Release notes about ABAP developments are the technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide (IMG). Target group:

Consultants Project teams for upgrades

Current version: On SAP Service Marketplace at service.sap.com/releasenotes In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)



Typographic Conventions

Table 17Example Description Angle brackets indicate that you replace these words or characters with appropriate entries

to make entries in the system, for example, Enter your .

Example Example Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

Cross-references to other documentation or published worksExample Output on the screen following a user action, for example, messages

Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard


SAP Manufacturing Integration and Intelligence 15.0Typographic Conventions

www.sap.com

&FP_Copyright;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. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.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 SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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.In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE's or its affiliated companies' strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

SAP Manufacturing Integration and Intelligence 15.0Table of Contents1 Getting Started2 Important SAP Notes3 Technical System Landscape4 Monitoring SAP MII5 Detailed Monitoring and Tools for Problem and Performance Analysis6 Managing SAP MII7 High Availability8 Software Change Management9 Troubleshooting10 Support Desk Management11 Categories of System Components for Backup and RestoreA ReferenceA.1 The Main SAP Documentation Types

Copyright and Trademarks

MII

Documents

Transcript of MII