SAP Mobile Platform: Enterprise Readiness Built-Ins

The SAP Mobile Platform (SMP) is a one-of-a kind solution for enterprises that take mobility seriously. SMP provides you with state of the art technology guaranteeing enterprise ready operations, with built in features including Security, Performance, Supportability, Lifecycle Management and more.

In this series of SCN pages, we drill down into Enterprise Readiness.You'll find links to White Papers, How-To Guides, recorded presentations and demos, Blogs and other resources that dive deep into any of the five selected topics.

SMP Enterprise Readiness: Webinar Series

In addition to the assets that you find on below SCN pages, we - the SAP Mobile Rapid Innovation Group (RIG) - host a series of webinars around Enterprise Grade Mobility with SMP.

The webinars will be presented by mobility experts from within SAP: Every week, every Thursday, and they are free to attend! And yes, we'll post recordings a few days after the sessions.

SMP on Topic: Supportability

Use these tabs to browse to the additional pages:

The IT world of SAP customers has grown much more challenging. Instead of one single SAP R/3 system, there are now multiple systems, integrated by the flow of business processes involving different SAP Suite products and middleware, including mobility. Data and process consistency is not provided by one integrated database design but by means of messaging, data, and UI unification.
It has become much more challenging to keep track of the entire, integrated system landscape. If there is an incident or a problem, it is more difficult to judge the relevance of certain activities.

This situation has made it essential that SAP customers and SAP Support can rely on a central source of current information on the customer solution and system landscape.

Supportability is the capability to monitor the SAP Mobile Platform to find errors or exceptions, trace or debug to identify the errors, and provide hardware and/or software solutions to resolve the issue or error.

Once a system or application is running in a production mode, it becomes important to make sure that it stays running efficiently. The day to day operation, configuration, monitoring can be found under the Life Cycle Management topic (see tabs). Once you identify an anomaly in the system you can make use of the resources below to help, identify, trace and resolve the issue.

SAP's Solution Manager is the central, integrated end-to-end orchestration platform to accelerate innovation, manage the application lifecycle and run SAP centric solutions like a factory. The current release of SAP Solution Manager is SAP Solution Manager 7.1.

Solution Manager started support of SUP/SMP with release of 2.1, and added significant capabilities with the introduction of SMP 2.2. Moving on.

Details on supported scenarios and in-depth resources can be found on the Solution Manager Manager section (see tab).

Resources available on SCN

For any resources related to SAP Solution Manger, Wily Introscope or Applications Operations, please see Solution Manager Manager.

• Troubleshooting SMP Device Notifications (DCN, WF-DCN, TCN and Native Push Notification services)
  SMP supports different mechanisms for transmitting notifications from the enterprise information system (EIS) to device client applications.
  This document provides information about how the Data Change Notification process works, and how to troubleshoot it.
• Efficient SUP log collection
  Productive SUP environments produce a multitude of interesting logs in a multitude of places. The important process of collecting these logs can become quite tedious, so Former Member wrote a short and hopefully universally adaptable batch script that simplifies and streamlines this task.
• Monitoring SUP's virtual machine
  An overwhelming amount of SUP's codebase is written in Java and must therefore run on a Java virtual machine (JVM).
  Since Java takes over some very fundamental responsibilities of the code it executes, e.g., memory management, it can be worthwhile to have a closer look at this JVM. Former Member did exactly that! (note: content of the blog should only be applied to proof-of-concepts, prototyping, or other trail-phase activities, but never in productive environments.
• Less memory for cache refreshes
  Designing a good data layer is one of the most far-reaching challenges that an app developer faces.
  In the context of SUP, the data layer is modeled with mobile business objects (MBOs), and best practices for this modeling have been published in a White Paper.
  Former Member discusses one trap that does not appear in the best practices, but which can have quite devastating repercussions
• Efficient SMP Log Analysis
  This blog addresses questions like "How many warnings and errors occurred today and yesterday and in which component?" or "Which warnings or errors were most frequent today?"
• SUP/SMP 2.x 'Advanced Logging and Statistics
  Short guide describing how to enable logging features which assist in researching and troubleshooting some aspects of the server
  Security Monitoring and Issue Detection
  Part of official SUP Documentation. If you log in, you can post comments for the Documentation Team: suggestions for improvements, additional content etc.
• Troubleshooting Security, Logins and Authentication
  Part of official SUP Documentation. If you log in, you can post comments for the Documentation Team: suggestions for improvements, additional content etc.
• How to capture Memory Usage and statistics in SUP 2.x
  This technical document explains the steps needed to enable memory and statistics logging in the Sybase Unwired Server.
• How to setup JStack tracing for SUP 2.x
  JStack prints stack traces of Java threads for a given process, core file or a remotedebug server. For each Java frame, the full class name, method name, 'bci' (byte code index) and line number, if available, are printed.
• Configuring MobiLink Monitor and connect to SUP 2.x
  This technical document explains how to configure and connect to the SUP server using MobiLink Monitor with and without a certificate.
• How to force SUP to run the configuration batch files (SUP 2.x)
  Sometimes the admin is required to force SUP to run its configuration files in order to update all the property files for the SUP environment manually.
• How to alter the SUP Mobilink Command Line
• Debugging Guide on How to Debug a Performance Communication in SUP 1.5.x or 2.x
  This document discuses how to debug the performance of a session in an SUP environment and what component to look at.
• When to Reclaim CDB space in SUP 2.x
  This technical document explains how to figure out if the CDB in SUP needs to be rebuild to reclaim the space.
• How to improve sync time in SUP 2.1 or higher using HTTP
• How to manually uninstall SUP Installation - SUP 2.1
  If SUP got installed without the uninstall directory or if the Uninstall did not get created in the Uninstall Programs under Windows, you need manually clean up the system and re-do the installation.
• Configuring MobiLink Monitor and connect to SUP... | SCN
• Sybase Control Center Postinstallation Checklist
• Configuring Logs in Sybase Control Center NEW
  Logs are essential for trouble shooting. For every request that is being done from the client , corresponding logs are be generated in the SMP server.
  The logs can be fetched at various log levels depending upon the configurations that can be made In the SAP Control Center. @Sharvari . explains how upi could configure the SMP server to generate the logs.

Additional Enablement Resources

• SAP Partner Edge - Training for Support Consultants - free, short eBooks
  • Understanding and Configuring SUP Logs
  • Cluster License
  • Data Access Recovering
  • Relay Server Outbound Enabler (RSOE) Configuration on SUP 2.0
  • Relay Server
  • Cluster Installation
  • Introduction to SQL Anywhere Within SUP
  • Lightweight Directory Access Protocol (LDAP) Authentication
  • Sybase Software Asset Management (SySAM)

People to follow

@John Polus,       @Ali Chalhoub,       Former Member,      Former Member,       @Marvin Hoffmann,      @Sergey Volodin,      @Wayne Smith,      @ Kevin Bates