Escolar Documentos
Profissional Documentos
Cultura Documentos
© Copyright 2014, Atos All rights reserved. Reproduction in whole or in part is prohibited without the prior written consent of
the copyright owner. For any questions or remarks on this document, please contact Atos ESO AHS SAP, .
Build Installation Guide SAP Mobile Platform
Contents
1 Introduction ............................................................................................... 4
1.1 Purpose ..................................................................................................... 4
1.2 Audience .................................................................................................... 4
1.3 Scope ........................................................................................................ 4
1.4 Related documents ...................................................................................... 4
2 Package Description .................................................................................... 6
2.1 Package Version .......................................................................................... 6
2.2 Licensing Considerations .............................................................................. 6
2.3 Package Components ................................................................................... 7
2.4 Application Notes ........................................................................................ 8
2.5 Installation Time ......................................................................................... 9
3 Prerequisites ............................................................................................ 11
3.1 Installation Roles / Rights / Skills ................................................................ 11
3.2 Hardware Requirements - including Network and Data Center ......................... 12
3.3 Software Requirements .............................................................................. 13
3.4 Other Requirements (optional) .................................................................... 14
4 Installation Procedure ................................................................................ 15
4.1 Installation Overview ................................................................................. 15
4.2 Initial Hardware Installation and Configuration .............................................. 15
4.3 Initial Software Installation and Configuration ............................................... 17
4.4 Additional Hardware Installation and Configuration ........................................ 18
4.5 Additional Software Installation and Configuration ......................................... 19
5 Post Installation Testing ............................................................................. 20
5.1 Hardware Validation .................................................................................. 20
5.2 Software Validation ................................................................................... 20
6 Removal / Uninstallation / Backout .............................................................. 21
6.2 Customer-specific configuration (opt.) ......................................................... 22
7 Abbreviations and definitions ...................................................................... 23
8 Detailed Configuration ............................................................................... 24
List of changes
Version Date Description Author(s)
1.0 20-12-2017 Initial version Janek
Bakiewicz
Document release
1 Introduction
1.1 Purpose
The purpose of this document is to provide detailed step by step installation instructions and low
level configuration details for specific components that are used to implement a new instance of
SAP Mobile Platform option (as a part of the SAP Basis Operations service) in accordance
with Atos Global Delivery standards and portfolio services.
1.2 Audience
This document is intended for SAP Mobile Platform option as a part of the SAP Basis
Operations service build and development engineers tasked with implementing or migrating to
a new solution. The blueprint assumes that the reader has reasonable grasp of SAP Mobile
Platform, operating systems and databases as well as familiarity with architecture principles
including high availability and multi-tenancy.
SAP Mobile Platform (formerly Sybase Unwired Platform) is a mobile enterprise application
platform designed to simplify the task of creating applications that connect business data to
mobile devices for workflow management and back-office integration. SAP Mobile Platform
provides a layer of middleware between heterogeneous back-end data sources, such as relational
databases, enterprise applications and files, and the mobile devices that need to read and write
back-end data.
1.3 Scope
The scope of SAP Mobile Platform option as a part of the SAP Basis Operations service
covers the following:
1. SAP Mobile Platform management
2. Database management of the SAP Mobile Platform databases and, where applicable
customer specific additional databases.
3. Installation of customer delivered licenses.
A number of vendor best practice documentation has been used in this blueprint as per Table 2.
Vendor Document Name
2 Package Description
This section gives a brief description of the package(s) to install.
Packages that need to be installed should be determined in cooperation with the customer and
SAP AG, based on the other systems in the customer landscape. Mobile Platform is middleware,
that must be connected to handhelds on one side and Netweaver backends on the other side. In
order to make this connection, actions need to be executed in the Netweaver backend also.
SAP work manager and SAP inventory manager are the two most known applications that use SAP
Mobile Platform and also need additional packages in the Netweaver backend. These additional
packages depend on the Netweaver version of the backend.
As Mobile Platform is a product of SAP AG, we can determine with the PAM
(support.sap.com/pam) what the current version of Mobile Platform and available add-ons are.
Guideline 1:
Use the latest version, unless customer requirements make older versions necessary.
Guideline 2:
Apply latest patches if possible, unless customer requirements make older versions necessary.
Guideline 3:
Check and install Java tools like visualvm and sap jvm profiler in the landscape.
Guideline 4:
Connect the system to Solution Manager (SAP Bluebox or customer specific solution manager
system)
Application of licenses in the SAP Mobile Platform application is not required. This is an exception.
However, if you use database like SAP ASE or SAP sqlanywhere, you need to apply database
licenses. However, our preference is using Microsoft sequel server as database on a Microsoft
Windows server.
As stated software needs to be downloaded from the SAP marketplace. As stated, an S-number
must be provided, and the S-number should have sufficient authorizations in order to download
the package.
Component URL/Repository/Directory
SAP Mobile Platform https://support.sap.com/swdc or
https://support.sap.com/en/my-support/software-
downloads.html
A list of optional components to install are listed in the table below. A full list of choices can be
found on SAP Marketplace. This list is for illustration purposes only
Component URL/Repository/Directory
SAP work manager https://support.sap.com/swdc or
https://support.sap.com/en/my-support/software-
downloads.html
http://visualvm.java.net/eclipse-launcher.html
Component URL/Repository/Directory
Java Form the oracle website
Component URL/Repository/Directory
Test have been executed with Mars
SAP JVM profiler https://wiki.scn.sap.com/wiki/display/ASJAVA/Download+the
+SAP+JVM+Profiler+2.2+plug-in
VisualVM https://support.sap.com/swdc or
https://support.sap.com/en/my-support/software-
downloads.html
Documentation https://blogs.sap.com/2015/09/18/step-by-step-to-
use-visualvm-to-do-performance-measurement/
https://wiki.scn.sap.com/wiki/display/ASJAVA/Java+Profiling
Package Information concerning the package history and packages replaced by this.
history Example:
1. This installation package does not replace any other packages.
2. This installation package replaces the following packages: x, y, z
…more… ... (further info if needed - delete table item if not) …
Testing What testing has been performed for this installation, who performed that testing
and Example:
Validation 1. This package has been installed into a small lab environment
2. Testing engineers were x and y, testing co-ordinator was z.
3. The package was tested on Windows 2008 R2 on Dell M620 blades, other
hardware and OS’s were not tested
…more… ... (further info if needed - delete table item if not) …
SAP Blog: Quick Start Guide to install SAP Work Manager 6.3 with SMP 3.0
SAP Note 1990123 - Managed System Configuration for SAP Mobile Platform 3.0 with SAP
Solution Manager 7.1 (including document “Managed System Configuration for SMP3 Root Cause
Analysis.pdf” and “Configuring Technical Availability Monitoring for SAP Mobile Platform 3.pdf”
Rough installations times can be determined if all prerequisites are met. SAP Mobile Platform as
part of SAP Basis operations is depended on a full configuration of the server, and not on the
default installation methods of operating teams.
If all these activities are finalized before the installation is started, the following times are
realistic:
Installation of Microsoft sequel server, based on the script sql4sap.vbs (installation is dropped in
C-drive) in 2-4 hours.
Installation of Microsoft sequel server database patch in 2 hours.
Creation of the SAP Mobile Platform database (SMP3) in 2 hours.
High availability of Microsoft sequel server (for example through always on) is not included.
The SAP Mobile Platform application makes a connection to the database. During the installation
of a second or even third application server, the application sees during the installation that a
server is already present. The application server directly forms an application clusters. Of course
this must be tested
SAP Mobile Platform SDK Application installation (no database required. Needs to be installed on
separate server:
SAP Relay server installation (no database required. Needs to be installed on separate server in
the DMZ:
However, it is possible to connect SAP Mobile Platform to a transport landscape in the SAP
Netweaver environment, if applicable. Reasons for this advice:
1. Developments are being deployed on an identical way as SAP Netweaver developments.
2. As SAP Netweaver transports are usually equipped with quality assurance, transports do not
have to be applied manually.
3. SAP BusinessObjects developments and SAP Netweaver developments can now be deployed
from DEV to QAS to PRD in one group of transport, and can be approved by the same persons.
This means less manual labor, and one point of access for two applications.
This procedure has been described in “Configuring SAP Mobile Platform CTS+ Properties”
https://help.sap.com/saphelp_smp3010svr/helpdata/en/eb/09d5e920fd4210a5f86105300ff26a/fr
ameset.htm
It is valid starting from SMP 3.0 SP10. For earlier SMP 3.0 versions, this was not allowed. For SMP
2.3 versions, this was supported by SAP AG, but only for solution manager systems on windows
(due to programming requirements).
3 Prerequisites
This chapter contains a description of the pre-requisites for the installation required of the
package named above.
In general all required steps for building the solution shall be documented inside this document.
In case these steps are very simple (e.g. create user) it might be only part of the prerequisites. In
case build steps which this document is dependent on are described in other documents it need to
be properly linked with document name, document reference number (i..e MSD-GAD-00xx),
document folder location and chapter name with relevant steps.
Please give some information of where and how passwords are to be stored for the users above.
Passwords can be stored in any password tool being used for the specific customer. However, the
analyst MUST be notified, in order to check the storage in the password tool.
CPU and memory requirements depend on the actual choice and the actual planned usage of the
SAP Mobile Platform application. That is why we propose to install this on virtual building blocks.
Basic sizing can be executed with the SAP quicksizer https://support.sap.com/quicksizing and in
the SAP Mobile Platform 3 sizing guide
Hardware requirements are described in the HLD and LLD. Most important details will be repeated
here.
When two application servers are used, the application servers can be distributed over different
data centers. It should be taken into account that the application servers need to communicate
with the database server, and therefore one of the application servers should be in the same data
center as the database server.
Also, the application servers should be in the same datacenter as the application that deliver the
backend data (SAP Netweaver).
This section should also contain details of network port, firewall rules, VLANS, VLAN
configurations, etc. that should be in place before commencing the install. The section should
also include any cable installations that should be in place.
We start with the network in the datacenter that is currently in place. This should be a standard
10 Gb connection.
The application servers do not need a virtual hostname, as the application does not allow
installation with a logical hostname. With customer DNS, an alias can be created, which allow the
connections to the server to be server independent.
IP address(es) Use case
192.168.x.x/24 Private address range of 256 IP’s for ...
2x IP from customer address space (ASN Cluster node public address
routable)
1x IP from customer address space (ASN Virtual cluster IP
routable)
Firewall rules
Src IP’s FW group Direction Dst IP’s FW group Protocol(s
)
155.45.129.24/29 SAaCon_Admin -> 10.196.5.0/25 DDC_Tooling TCP/22,
Gate_EMEA TCP/443,
TCP/903
161.89.93.32, s0225_ESB_ATF -> 10.196.5.28 DDC_Orchestrato TCP/8080,
161.89.93.33 _PreProd r TCP/8081
10.196.5.0/25 DDC_Tooling <-> 161.89.27.64/27 s0240_MA_AOS TCP/8080,
N_EPO TCP/443,
TCP/8444
Details of hardware devices required for the installation – what hardware platform this installation
should be deployed onto (for example, if this is an NX-OS installation, what hardware devices this
version can be installed onto etc.), also any modules or components that should be added to that
hardware.
As we chose for virtual servers with a windows operating system, we choose for vmware or
esxhosts. Operating team is taking care of the OS requirements.
Where the engineer installing this software should “customize” the OS as part of the install, those
steps should not be included here but should be included in section 4.
Describe other applications that need to be installed including versions in advance to this solution
e.g.
SSH client for Windows: Putty version xyz
Additional components for analysis options:
Notepad++ (better look and feel than notepad)
Fiddler (installing of fiddler is not necessary. Installation software can be unzipped, and the
executable can directly be used).
Configuration parameters required throughout the build shall be listed in the table below and filled
before the build is started in order to prevent disruptions and delays. This chapter shall be linked
inside the detailed build steps further below for reference.
An extensive list of firewall ports is known. That will be added as additional document. This list
does not only describe firewall ports necessary on the local firewall, but also firewall ports
necessary for communication to a netweaver backend and/or the SAP BlueBox backend.
For the connection to the SAP Netweaver backend, message server, dispatcher, gateway and
ICM/http ports need to be open.
For the connection to Solution Manager, solman ICM/http, Java P4 and wily port need to be open.
For the connection to monitoring tools like SCOM or Nagios/UMF, ports need to be open.
If database and application are installed in different network zones, based on customer
requirements, database connection port needs to be open. However, this will probably slow down
the application, as network traffic is slower than internal server communication.
4 Installation Procedure
4.1 Installation Overview
This section should provide an overview of the installation process including all steps required to
complete the install. This should include a flow chart of the steps and the dependencies.
The initial hardware installation and configuration is executed by the server team, based on the
requirements listed in the next steps.
Define connection requirements, based on the ports listening on the applications that need to be
connected to the SAP Mobile Platform application.
Database and log files should be located on separate file systems, as database growth should not
be limited by log files growth. Log files growth can be excessive, and if this growth blocks the file
system, database activity can be seriously influenced. In worst case scenario, this may lead to
database corruption.
Of course, the file systems for ms sql server database files and log files need to be configured
with 64 kb blocksize.
If log files growth blocks the log file systems, application and database will hang, by after the
removal of the blockade, everything will continue to work as usual.
If the application software directly is blocked, a specific configuration file may become corrupted.
However, this was noticed in an older version, and it may not be applicable anymore.
User requirements:
Users should be active directory users, as actions should be executed with identical
authorizations. A user for daily activities (called sidadm) should be used. A user that starts up
services (called sapservicesid) should be used.
Firewall settings;
Open de firewall settings for SMP specific ports and for the communication to the backends.
Define virus scan requirements, based on the directories and the programs that are used by the
application.
... (text) …
Check requirements and go back to step1 if requirements have not been met.
If new requirements are discovered, please mention them to SAP architect.
4.3.1 Step 1 –
Sub- Action
Screenshot
Step
1. Logon to the first
SCREENSHOT / COMMAND HERE
server
2. Click Set time zone SCREENSHOT / COMMAND HERE
3. Click Change time
SCREENSHOT / COMMAND HERE
zone…
4.3.2 Step 2 –
Sub- Action
Screenshot
Step
1. Logon to the first
SCREENSHOT / COMMAND HERE
server
2. Click Set time zone SCREENSHOT / COMMAND HERE
3. Click Change time
SCREENSHOT / COMMAND HERE
zone…
4.3.3 Step 3 –
Sub- Action
Screenshot
Step
1. Logon to the first
SCREENSHOT / COMMAND HERE
server
2. Click Set time zone SCREENSHOT / COMMAND HERE
3. Click Change time
SCREENSHOT / COMMAND HERE
zone…
If required a SAP Mobile Platform SDK can be installed. This installation is necessary for customer
specific developments.
If required a SAP relay server can be installed. This installation should be located in the DMZ and
make connections to the SAP Mobile Platform backend. However, if the customer does need the
SAP Mobile Platform application to be internet facing, this option is not required.
4.4.1 Step 1 –
4.4.2 Step 2 –
4.5.1 Step 1 –
Sub- Action
Screenshot
Step
1. Logon to the first
SCREENSHOT / COMMAND HERE
server
2. Click Set time zone SCREENSHOT / COMMAND HERE
3. Click Change time
SCREENSHOT / COMMAND HERE
zone…
Install the SAP work manager in the SAP mobile Platform application.
Network ports to the Netweaver backend must be opened.
Use program connectTest.bat (delivered by SAP SE) to test network connection.
SAP Netweaver backend ports need to be open (especially dispatcher, gateway and ICM port).
SAP Business Configuration Sets configuration set needs to be activated (SCPR20) Netweaver
development backend only. Changes needed to be added to transports and these transports need
to be applied in non-production environment.
As configuration depends on exact versions, no commonly usable installation document can be
given.
6.1.1 Step 1 –
Sub- Action
Screenshot
Step
1. Logon to the first
SCREENSHOT / COMMAND HERE
server
2. Click Set time zone SCREENSHOT / COMMAND HERE
3. Click Change time
SCREENSHOT / COMMAND HERE
zone…
As these servers are virtual servers and virtual servers can be cloned, a clone should be made for
every major change. It is necessary to stop the application before cloning and start after the clone
has been made.
An installation can be removed. However, not all files are removed from the server. And the
registry is not completely cleaned. A redeployment of the server does also not remove the
complete installation. If required an deinstallation can occur, but the new installation should not
be placed on the same location.
... (text) …
Please state here specific abbreviations and definitions which are not included in related
documents of this specification. (needed for the understanding of this document).
Abbreviation / Explanation
term:
<Further
abbreviations
and definitions>
8 Detailed Configuration
The table below details the detailed configurations for the components that are deployed using
this document:
# Scriptname: SetDellAlertAction.ps1
# Author: xyz
# Version 1.0, 10.09.2015