Upgrade: SAP Mobile Platform Server for Linux · PDF fileContent 1 Upgrade: SAP Mobile...

PUBLIC

SAP Mobile Platform 3.0 SP12Document Version: 1.0 – 2016-12-06

Upgrade: SAP Mobile Platform Server for Linux

Content

1 Upgrade: SAP Mobile Platform Server for Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Upgrading SAP Mobile Platform 3.0 Server to SP12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.1 Upgrading an Existing 3.0 Server to SP12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Acquiring the Support Package Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Preparing to Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Running the Support Package Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Verifying the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Upgrading Tomcat Server sslEnabledProtocols Property for Agentry Applications on iOS 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.2 Adding Cluster Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Running the Support Package Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Verifying the Added Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3 Upgrading an SAP Mobile Platform 3.0 Cluster to SP12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.1 Upgrading Each SAP Mobile Platform 3.0 Server to SP12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Acquiring the Support Package Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Preparing to Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Running the Support Package Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Verifying the Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Upgrading Tomcat Server sslEnabledProtocols Property for Agentry Applications on iOS 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.2 Adding Cluster Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Running the Support Package Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Verifying the Added Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

4 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

4.1 Quick Fixes to Simple Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Server Node Does Not Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Server Cannot Start on Newer Version of Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Server Node Does Not Join the Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

SP05 to SP06 Upgrade Fails Because Service Fails to Install. . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4.2 Issues Requiring Product Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Product Support Engagement Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Creating an Incident on SAP Service Marketplace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

2 P U B L I CUpgrade: SAP Mobile Platform Server for Linux

Content

1 Upgrade: SAP Mobile Platform Server for Linux[d1]

Upgrade your single-server SAP Mobile Platform Server 3.0 installation to SP12 and add server nodes to form a cluster.

You can upgrade any single-server SAP Mobile Platform Server 3.0.x installation to SP12.

If the SAP Mobile Platform Server 3.0.x installation you are upgrading was installed with an external production database, you can use the same SAP Mobile Platform Server SP12 installer on additional host systems, connecting to the same external database, to create a cluster of servers.

Related Information

Upgrading SAP Mobile Platform 3.0 Server to SP12 [page 4]Troubleshooting [page 28]

d1 concept id: loio7bd8f97404744cae8df74f3b3fa3b848 - srcFile: /content/authoring/syg1445548763610.xml

Upgrade: SAP Mobile Platform Server for LinuxUpgrade: SAP Mobile Platform Server for Linux P U B L I C 3

2 Upgrading SAP Mobile Platform 3.0 Server to SP12[d2]

Run the SAP Mobile Platform SP12 installer on your single-server 3.0.x installation. Then use the same installer on additional servers to create a cluster and add nodes.

1. Upgrading an Existing 3.0 Server to SP12 [page 4]Upgrade your single-server SAP Mobile Platform 3.0 installation to SP12.

2. Adding Cluster Nodes [page 10]After upgrading a single-server production installation to SP12, you can use the same installer to install additional version 3.0 SP12 SAP Mobile Platform Servers on different computers. When these SAP Mobile Platform Servers share a single, external database, each server acts as a node in a cluster of servers.

2.1 Upgrading an Existing 3.0 Server to SP12[d3]

Upgrade your single-server SAP Mobile Platform 3.0 installation to SP12.

The SP12 upgrade preserves all configuration changes and applications in the 3.0 installation, except for server log levels. Upgrading to SP12 resets any server log levels you have changed to the default values.

Context

To upgrade your current single-server 3.0 production installation to a cluster, complete the tasks in this section to upgrade the original SAP Mobile Platform Server installation to SP12, then see Adding Cluster Nodes [page 10].

NoteYou cannot upgrade a single-server development installation that uses the embedded database to a cluster. A single-server installation must use an external custom database to be upgraded to a cluster.

1. Acquiring the Support Package Installer [page 5]Acquire the SAP Mobile Platform Server SP12 .zip file and extract its contents to create the installer image.

2. Preparing to Upgrade [page 6]

d2 task id: loio72c3794644e84ee490ecb283fedd334f - srcFile: /content/authoring/tss1452795827423.xmld3 task id: loio72c3794644e84ee490ecb283fedd334f loio7c29043a700610148c37c8353e20d5ba - srcFile: /content/authoring/kmn1452795841018.xml


Upgrading SAP Mobile Platform 3.0 Server to SP12

Verify that the host on which you are upgrading SAP Mobile Platform is ready for you to begin the upgrade installation.

3. Running the Support Package Installer [page 7]Run the installation script. There are no installation options to set.

4. Verifying the Upgrade [page 8]Check for errors in the installation log file, then verify that you can start the SAP Mobile Platform Server and log in to Management Cockpit.

5. Upgrading Tomcat Server sslEnabledProtocols Property for Agentry Applications on iOS 7 [page 9]If your SAP Mobile Platform installation supports Agentry applications on iOS 7 devices, upgrade the Tomcat Server sslEnabledProtocols property to avoid slow transmits.

Task overview: Upgrading SAP Mobile Platform 3.0 Server to SP12 [page 4]

Next task: Adding Cluster Nodes [page 10]

2.1.1 Acquiring the Support Package Installer[d4]

Acquire the SAP Mobile Platform Server SP12 .zip file and extract its contents to create the installer image.

Procedure

Use one of these methods:

○ Insert the physical installation media.○ Download from the software distribution center on SAP Service Marketplace:

1. Go to http://service.sap.com/swdc .2. In the left pane, under Support Packages and Patches, select A-Z Index.3. Click M.4. Click SAP MOBILE PLATFORM.5. Click the link for SP12.6. Select the platform.7. Choose the file to download.8. Extract the contents of the .zip file to a temporary directory on a local disk on the target host.9. Extract the contents of the SAP Mobile Platform Server installer .zip file to a temporary directory on

a local disk on the target host.Use a short path, preferably a folder directly below the root directory, such as usr/home/temp. The path can include only ASCII alphanumeric characters, underscores, hyphens ), and period (.). Two consecutive period characters are not allowed.

Task overview: Upgrading an Existing 3.0 Server to SP12 [page 4]

d4 task id: loio72c3794644e84ee490ecb283fedd334f loio7c29043a700610148c37c8353e20d5ba loio7c28c4ac70061014ac7ce350bdc98b27 - srcFile: /content/authoring/flt1452804855639.xml

Upgrade: SAP Mobile Platform Server for LinuxUpgrading SAP Mobile Platform 3.0 Server to SP12 P U B L I C 5

http://help.sap.com/disclaimer?site=http://service.sap.com/swdc

Next task: Preparing to Upgrade [page 6]

2.1.2 Preparing to Upgrade[d5]


Context

The system requirements may have changed since you installed the earlier version of SAP Mobile Platform.

Procedure

1. Before proceeding with this upgrade, verify that your existing SAP Mobile Platform installation is version 3.0 SP04 or later.

2. Confirm that the installation target host meets minimum system requirements for SAP Mobile Platform 3.0 SP12.

See the SAP Product Availability Matrix (PAM) https://apps.support.sap.com/sap/support/pam . Search for SAP Mobile Platform 3.0 (search box in the upper-right corner), and select either SAP Mobile Platform 3.0 or SAP Mobile Platform SDK 3.0.

NoteAccess to the PAM requires an SAP Service Marketplace login: http://service.sap.com/request-user

3. Verify that you have Administrator privileges on the installation target host.4. Verify that the database is running.5. Shut down the server. If you are upgrading a cluster of servers, shut down all servers in the cluster.6. Shut down Sybase and SAP services that are running on the installation host (not the database).

7. To accommodate SAP Mobile Platform internal communications, you may need to reconfigure intrusion detection/prevention systems (either hardware- or software-based).

See Intrusion Detection and Protection Requirements in Landscape Planning and Design.8. (Optional) If the database type you will be using after upgrading is different from the current database

type:

Run daemon.sh reinstall.

d5 task id: loio72c3794644e84ee490ecb283fedd334f loio7c29043a700610148c37c8353e20d5ba loio2a556a693c334ec6b1a5df34b202022e - srcFile: /content/authoring/egl1460407434878.xml



http://help.sap.com/disclaimer?site=https://apps.support.sap.com/sap/support/pam

http://help.sap.com/disclaimer?site=http://service.sap.com/request-user


Previous task: Acquiring the Support Package Installer [page 5]

Next task: Running the Support Package Installer [page 7]

2.1.3 Running the Support Package Installer[d6]

Run the installation script. There are no installation options to set.

Prerequisites

Make sure the SAP Mobile Platform installation you are upgrading meets the requirements in Preparing to Upgrade [page 6].

NoteThe installation path was set when you installed version 3.0 and is referred to as <SMP_HOME> in the rest of these instructions.

Procedure

1. Open a terminal window.2. Go to the root directory of your installer image.3. Launch the installer:

sh SilentInstall_Linux.sh

NoteThe installer displays an Initializing wizard... message while it verifies the integrity of the installation image.

The installer then displays progress messages as it completes each step of the installation. Watch for this message when the installer completes:

Installation Successful4. If you modified or added files in the <SMP_HOME>/Server/pickup directory, restore those files now from

the <SMP_HOME>/backup-server-<version>/Server/pickup directory.

d6 task id: loio72c3794644e84ee490ecb283fedd334f loio7c29043a700610148c37c8353e20d5ba loio7c28d72470061014a639df70818aa90f - srcFile: /content/authoring/nds1461247737665.xml


5. If you had enabled strong encryption in your environment by modifying the default encryption on the Java virtual machine installed with the earlier version of SAP Mobile Platform Server, you must reenable that strong encryption after upgrading.


Previous task: Preparing to Upgrade [page 6]

Next task: Verifying the Upgrade [page 8]

2.1.4 Verifying the Upgrade[d7]

Check for errors in the installation log file, then verify that you can start the SAP Mobile Platform Server and log in to Management Cockpit.

Procedure

1. Check the latest installation log at <SMP_HOME>/InstallLogs/SMPInstall<date-time>.log.

<SMP_HOME> is the installation location you specified in the initial 3.0 installation (the default is <$HOME>/SAP/MobilePlatform3/).

A quick way to do this is to run:

grep -i error SMP*log

2. Verify that you can start SAP Mobile Platform Server.1. Open a terminal window.2. Go to <SMP_HOME>/Server/.3. Execute sh go.sh.

Server start-up is complete when you see:The SMP server has initialized and is ready.

3. Verify that you can log in to Management Cockpit.○ In a browser on any computer on the network, enter:

https://<host_name>.<domain>:<https_admin_port>/Admin/

○ In a browser on the system where SAP Mobile Platform Server is installed, enter:

https://localhost:<https_admin_port>/Admin/

d7 task id: loio72c3794644e84ee490ecb283fedd334f loio7c29043a700610148c37c8353e20d5ba loio7c28d06970061014b0e69209da95d96a - srcFile: /content/authoring/jnk1452799180925.xml



Next Steps

If you are upgrading a single-server production installation to a cluster, continue with Adding Cluster Nodes [page 10]

If you are upgrading a single-server installation to SP12, continue with Postinstallation Landscape Setup in Administrator.


Previous task: Running the Support Package Installer [page 7]

Next: Upgrading Tomcat Server sslEnabledProtocols Property for Agentry Applications on iOS 7 [page 9]

2.1.5 Upgrading Tomcat Server sslEnabledProtocols Property for Agentry Applications on iOS 7[d8]

If your SAP Mobile Platform installation supports Agentry applications on iOS 7 devices, upgrade the Tomcat Server sslEnabledProtocols property to avoid slow transmits.

The sslEnabledProtocols properties for Tomcat HTTP listener ports are located in <SMP_HOME>\Server\config_master\org.eclispe.gemini.web.tomcat\default-server.xml. Create a backup copy of this file before making any changes.

NoteIn a clustered server environment, you must update the file on each server node.

1. In a text editor, open the default-server.xml file.2. In each of the lines below, replace sslEnabledProtocols="TLSv1" with

sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2":

... <Connector smpConnectorName="oneWaySSL" ...

... clientAuth="false" sslProtocol="TLS" sslEnabledProtocols="TLSv1" /> ...<Connector smpConnectorName="AdminSSL" ...... clientAuth="false" sslProtocol="TLS" sslEnabledProtocols="TLSv1" smpServiceType="admin" ... ...<Connector smpConnectorName="mutualSSL" ...... keyAlias="smp_crt" clientAuth="true" sslProtocol="TLS" sslEnabledProtocols="TLSv1"/> ...

d8 reference id: loio72c3794644e84ee490ecb283fedd334f loio7c29043a700610148c37c8353e20d5ba loio8cbe2795a3fe47d5a6373fe7548ca38c - srcFile: /content/authoring/qgu1452799196926.xml


3. Save the file and restart SAP Mobile Platform Server.

Parent topic: Upgrading an Existing 3.0 Server to SP12 [page 4]

Previous task: Verifying the Upgrade [page 8]

2.2 Adding Cluster Nodes[d9]

After upgrading a single-server production installation to SP12, you can use the same installer to install additional version 3.0 SP12 SAP Mobile Platform Servers on different computers. When these SAP Mobile Platform Servers share a single, external database, each server acts as a node in a cluster of servers.

Context

NoteAll nodes added to a cluster use the same communication port numbers specified for the first server that was installed in the cluster. Make sure these port numbers are available on the node where your are installing the additional SAP Mobile Platform Server for the cluster.

1. Running the Support Package Installer [page 11]To add nodes to a cluster formed around the single-server production installation that you have upgraded to SP12, repeat this procedure for each additional node.

2. Verifying the Added Node [page 14]Check for errors in the installation log file, then verify that you can start SAP Mobile Platform Server, log in to Management Cockpit, and see the SAP Mobile Platform Server properties.

Task overview: Upgrading SAP Mobile Platform 3.0 Server to SP12 [page 4]

Previous task: Upgrading an Existing 3.0 Server to SP12 [page 4]

d9 task id: loio72c3794644e84ee490ecb283fedd334f loiob9e11989c36b40aaa4a0f7bda9e57720 - srcFile: /content/authoring/mfx1452803708027.xml




To add nodes to a cluster formed around the single-server production installation that you have upgraded to SP12, repeat this procedure for each additional node.

Prerequisites

Have the SilentInstall_Linux.txt file that was used in the original SAP Mobile Platform Server single-server installation available, or be able to specify the same values when you edit that file for the cluster node installation. You must match exactly the settings from that fist installation in each cluster node installation.

Procedure

1. Open a terminal window.2. Go to the root directory of your installer image.3. Use a text editor to open the SilentInstall_Linux.txt file.

4. Make changes as needed to customize installation options. There are three changes you must make:○ Change AgreeToSAPLicense from false to true in the line below, to indicate your acceptance of the

end user license agreement:

-V AgreeToSAPLicense="false"

○ Uncomment AdminPassword in the line below, and assign a non-null value:

#-V AdminPassword=""

○ Uncomment keyStorePassword in the line below, and assign a non-null value:

#-V KeystorePassword=""

NoteFor both the admin password and the keystore password, only alphabetic and numeric characters, spaces, periods, colons, dashes, and hyphens are allowed.

If you have installed a custom database and you want to install SAP Mobile Platform to work with it, you must set the parameters as indicated in the table below. Other parameters you can change are documented in comments in the SilentInstall_Linux.txt file.

d10 task id: loio72c3794644e84ee490ecb283fedd334f loiob9e11989c36b40aaa4a0f7bda9e57720 loio2343a0b0f6ee4fccb128c3ddf50b47ac - srcFile: /content/authoring/omh1452803819660.xml


Parameter Explanation

-V developerInstall="false"

The default setting is true, which specifies a developer installation, with no options, using the Derby database.

Change to false to enable a production installation, which allows you to set all other parameters, including a custom database.

NoteWhenever you change the developerInstall setting, you must change the productionInstall to be the opposite.

-V productionInstall="true"

The default setting is false, which specifies a developer installation, with no options, using the Derby database.

Change to true to enable a production installation, which allows you to set all other parameters, including a custom database.

NoteWhenever you change the productionInstall setting, you must change the developerInstall to be the opposite.

-V derbyDB="false"

The default setting is true, which specifies the default Derby database.

Change to false to enable selection of another database.

-V existDB="true"

The default setting is false, which disables selection of a database other than Derby.

Change to true to enable selection of another database.

-V existDBType="<database_choice>"

Delete the "#" at the start of the line to enable the parameter.

Set the value to select the database you have installed to use with SAP Mobile Platform:○ ase○ db2○ oracle-sid or oracle-svc

-V dbHostName="<database_host_name>"


Set the value to the name of the host on which you have installed the database to use with SAP Mobile Platform:

-V dbPortNumber="<database_port>"


Set the value to the port number your database uses.




-V dbLogin="gomobile"


Set the value to gomobile, or the new user name if you changed it from the default. This value was set for the administrator's ID for the SAP Mobile Platform database by the scripts that you ran.

-V dbPassword="secret"


Set the value to secret, or the new user password if you changed it from the default. This value was set for the administrator's password for the SAP Mobile Platform database by the scripts that you ran.

-V dbDBName="smp3"


Set the value to smp3, or the new database name, if you changed it from the default. This value was set for the SAP Mobile Platform database name by the scripts that you ran.

NoteIf you are using Oracle, dbDBName is either the service name or the SID, depending on how you access Oracle.

-V ignorePingError="false"


CautionLeave the value as false (recommended) to stop the installer if it cannot successfully ping your database, using the values that you have specified. If this option is true and the database ping fails, the installation completes, but the server will not start.

-V oracleJdbcDriver="<jdbc_path>"

(Oracle only) Delete the "#" at the start of the line to enable the parameter.

Set the value to the path to your Oracle JDBC driver, ojdbc6.jar or ojdbc6_g.jar.

NoteIf you wish to change the installation directory, uncomment the line below and replace "{User home directory}" with a valid path to the desired installation directory:

#-P installLocation="<{User home directory}>/SAP/MobilePlatform3"

If you uncomment this line without changing "{User home directory}" the installation will fail.

5. Save and close the SilentInstall_Linux.txt file.

6. Launch the installer:





Installation Successful

Task overview: Adding Cluster Nodes [page 10]

Next task: Verifying the Added Node [page 14]

2.2.2 Verifying the Added Node[d11]

Check for errors in the installation log file, then verify that you can start SAP Mobile Platform Server, log in to Management Cockpit, and see the SAP Mobile Platform Server properties.

Procedure



A quick way to do this is:








d11 task id: loio72c3794644e84ee490ecb283fedd334f loiob9e11989c36b40aaa4a0f7bda9e57720 loio4adbc641cadb4030aae4f3dcf063f161 - srcFile: /content/authoring/iti1452803839161.xml



4. Verify that this server has been added to the cluster.a. Navigate to the Cluster tab.b. Verify that the node you just installed appears.

Nodes are identified by host name.c. Click the node to see additional information.

Next Steps

To install additional nodes in a cluster, repeat this procedure, beginning with Adding Cluster Nodes [page 10], until you have installed all cluster nodes.

If this was the last node in your cluster, continue with Postinstallation Landscape Setup in Administrator.




3 Upgrading an SAP Mobile Platform 3.0 Cluster to SP12[d12]

Upgrade your SAP Mobile Platform 3.0 cluster installation to SP12.

Context

This section guides you through the process of upgrading an existing SAP Mobile Platform 3.0 cluster installation with SP12. The SP12 upgrade installation preserves all configuration changes and applications in the 3.0 installation, except for server log levels. Upgrading to SP12 resets any server log levels you have changed to the default values.

1. Upgrading Each SAP Mobile Platform 3.0 Server to SP12 [page 16]Upgrade each server in your SAP Mobile Platform 3.0 cluster installation to SP12.

2. Adding Cluster Nodes [page 22]After upgrading an existing cluster installation to SP12, you can use the same installer to install additional nodes in the cluster.

3.1 Upgrading Each SAP Mobile Platform 3.0 Server to SP12[d13]

Upgrade each server in your SAP Mobile Platform 3.0 cluster installation to SP12.

1. Acquiring the Support Package Installer [page 17]Acquire the SAP Mobile Platform Server SP12 .zip file and extract its contents to create the installer image.

2. Preparing to Upgrade [page 18]Verify that the host on which you are upgrading SAP Mobile Platform is ready for you to begin the upgrade installation.

3. Running the Support Package Installer [page 19]Run the installation script. There are no installation options to set.

4. Verifying the Upgrade [page 20]Check for errors in the installation log file, then verify that you can start the SAP Mobile Platform Server and log in to Management Cockpit.

5. Upgrading Tomcat Server sslEnabledProtocols Property for Agentry Applications on iOS 7 [page 21]

d12 task id: loioea6a873f8f99402db89927b7cd0716ed - srcFile: /content/authoring/har1452805010040.xmld13 task id: loioea6a873f8f99402db89927b7cd0716ed loio9c99875f526149cd8e1a9a6c9f7c44cc - srcFile: /content/authoring/uft1452804968319.xml


Upgrading an SAP Mobile Platform 3.0 Cluster to SP12


Task overview: Upgrading an SAP Mobile Platform 3.0 Cluster to SP12 [page 16]

Next task: Adding Cluster Nodes [page 22]

3.1.1 Acquiring the Support Package Installer[d14]

Acquire the SAP Mobile Platform Server SP12 .zip file and extract its contents to create the installer image.

Procedure

Use one of these methods:

○ Insert the physical installation media.○ Download from the software distribution center on SAP Service Marketplace:

1. Go to http://service.sap.com/swdc .2. In the left pane, under Support Packages and Patches, select A-Z Index.3. Click M.4. Click SAP MOBILE PLATFORM.5. Click the link for SP12.6. Select the platform.7. Choose the file to download.8. Extract the contents of the .zip file to a temporary directory on a local disk on the target host.9. Extract the contents of the SAP Mobile Platform Server installer .zip file to a temporary directory on

a local disk on the target host.Use a short path, preferably a folder directly below the root directory, such as usr/home/temp. The path can include only ASCII alphanumeric characters, underscores, hyphens ), and period (.). Two consecutive period characters are not allowed.

Task overview: Upgrading Each SAP Mobile Platform 3.0 Server to SP12 [page 16]

Next task: Preparing to Upgrade [page 18]

d14 task id: loioea6a873f8f99402db89927b7cd0716ed loio9c99875f526149cd8e1a9a6c9f7c44cc copydd641a6655a149089d4c04ec37592c43 - srcFile: /content/authoring/flt1452804855639.xml

Upgrade: SAP Mobile Platform Server for LinuxUpgrading an SAP Mobile Platform 3.0 Cluster to SP12 P U B L I C 17

http://help.sap.com/disclaimer?site=http://service.sap.com/swdc

3.1.2 Preparing to Upgrade[d15]


Context

The system requirements may have changed since you installed the earlier version of SAP Mobile Platform.

Procedure

1. Before proceeding with this upgrade, verify that your existing SAP Mobile Platform installation is version 3.0 SP04 or later.

2. Confirm that the installation target host meets minimum system requirements for SAP Mobile Platform 3.0 SP12.

See the SAP Product Availability Matrix (PAM) https://apps.support.sap.com/sap/support/pam . Search for SAP Mobile Platform 3.0 (search box in the upper-right corner), and select either SAP Mobile Platform 3.0 or SAP Mobile Platform SDK 3.0.

NoteAccess to the PAM requires an SAP Service Marketplace login: http://service.sap.com/request-user

3. Verify that you have Administrator privileges on the installation target host.4. Verify that the database is running.5. Shut down the server. If you are upgrading a cluster of servers, shut down all servers in the cluster.6. Shut down Sybase and SAP services that are running on the installation host (not the database).

7. To accommodate SAP Mobile Platform internal communications, you may need to reconfigure intrusion detection/prevention systems (either hardware- or software-based).

See Intrusion Detection and Protection Requirements in Landscape Planning and Design.8. (Optional) If the database type you will be using after upgrading is different from the current database

type:

Run daemon.sh reinstall.


Previous task: Acquiring the Support Package Installer [page 17]

d15 task id: loioea6a873f8f99402db89927b7cd0716ed loio9c99875f526149cd8e1a9a6c9f7c44cc copy094cd03233eb4d038ca53c4be152a03b - srcFile: /content/authoring/egl1460407434878.xml



http://help.sap.com/disclaimer?site=https://apps.support.sap.com/sap/support/pam

http://help.sap.com/disclaimer?site=http://service.sap.com/request-user

Next task: Running the Support Package Installer [page 19]


Run the installation script. There are no installation options to set.

Prerequisites

Make sure the SAP Mobile Platform installation you are upgrading meets the requirements in Preparing to Upgrade [page 6].

NoteThe installation path was set when you installed version 3.0 and is referred to as <SMP_HOME> in the rest of these instructions.

Procedure

1. Open a terminal window.2. Go to the root directory of your installer image.3. Launch the installer:




Installation Successful4. If you modified or added files in the <SMP_HOME>/Server/pickup directory, restore those files now from

the <SMP_HOME>/backup-server-<version>/Server/pickup directory.

5. If you had enabled strong encryption in your environment by modifying the default encryption on the Java virtual machine installed with the earlier version of SAP Mobile Platform Server, you must reenable that strong encryption after upgrading.

d16 task id: loioea6a873f8f99402db89927b7cd0716ed loio9c99875f526149cd8e1a9a6c9f7c44cc copy07af9669e53f4d96a7ec7c6b27cba9c2 - srcFile: /content/authoring/nds1461247737665.xml



Previous task: Preparing to Upgrade [page 18]

Next task: Verifying the Upgrade [page 20]

3.1.4 Verifying the Upgrade[d17]

Check for errors in the installation log file, then verify that you can start the SAP Mobile Platform Server and log in to Management Cockpit.

Procedure



A quick way to do this is to run:








Next Steps

If you are upgrading a single-server production installation to a cluster, continue with Adding Cluster Nodes [page 10]

d17 task id: loioea6a873f8f99402db89927b7cd0716ed loio9c99875f526149cd8e1a9a6c9f7c44cc copy801c4054b94149b8bd1c2bc3c010c4d9 - srcFile: /content/authoring/jnk1452799180925.xml



If you are upgrading a single-server installation to SP12, continue with Postinstallation Landscape Setup in Administrator.



Next: Upgrading Tomcat Server sslEnabledProtocols Property for Agentry Applications on iOS 7 [page 21]

3.1.5 Upgrading Tomcat Server sslEnabledProtocols Property for Agentry Applications on iOS 7[d18]


The sslEnabledProtocols properties for Tomcat HTTP listener ports are located in <SMP_HOME>\Server\config_master\org.eclispe.gemini.web.tomcat\default-server.xml. Create a backup copy of this file before making any changes.

NoteIn a clustered server environment, you must update the file on each server node.

1. In a text editor, open the default-server.xml file.2. In each of the lines below, replace sslEnabledProtocols="TLSv1" with

sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2":

... <Connector smpConnectorName="oneWaySSL" ...

... clientAuth="false" sslProtocol="TLS" sslEnabledProtocols="TLSv1" /> ...<Connector smpConnectorName="AdminSSL" ...... clientAuth="false" sslProtocol="TLS" sslEnabledProtocols="TLSv1" smpServiceType="admin" ... ...<Connector smpConnectorName="mutualSSL" ...... keyAlias="smp_crt" clientAuth="true" sslProtocol="TLS" sslEnabledProtocols="TLSv1"/> ...

3. Save the file and restart SAP Mobile Platform Server.

Parent topic: Upgrading Each SAP Mobile Platform 3.0 Server to SP12 [page 16]

Previous task: Verifying the Upgrade [page 20]

d18 reference id: loioea6a873f8f99402db89927b7cd0716ed loio9c99875f526149cd8e1a9a6c9f7c44cc loio38f4f8a040c748ccb2bbbfef3ce2ac9e - srcFile: /content/authoring/uza1452799394972.xml


3.2 Adding Cluster Nodes[d19]

After upgrading an existing cluster installation to SP12, you can use the same installer to install additional nodes in the cluster.

1. Running the Support Package Installer [page 22]To add nodes to a cluster formed around the single-server production installation that you have upgraded to SP12, repeat this procedure for each additional node.

2. Verifying the Added Node [page 26]Check for errors in the installation log file, then verify that you can start SAP Mobile Platform Server, log in to Management Cockpit, and see the SAP Mobile Platform Server properties.

Task overview: Upgrading an SAP Mobile Platform 3.0 Cluster to SP12 [page 16]

Previous task: Upgrading Each SAP Mobile Platform 3.0 Server to SP12 [page 16]


To add nodes to a cluster formed around the single-server production installation that you have upgraded to SP12, repeat this procedure for each additional node.

Prerequisites

Have the SilentInstall_Linux.txt file that was used in the original SAP Mobile Platform Server single-server installation available, or be able to specify the same values when you edit that file for the cluster node installation. You must match exactly the settings from that fist installation in each cluster node installation.

Procedure

1. Open a terminal window.2. Go to the root directory of your installer image.3. Use a text editor to open the SilentInstall_Linux.txt file.

4. Make changes as needed to customize installation options. There are three changes you must make:

d19 task id: loioea6a873f8f99402db89927b7cd0716ed loio28929f86523b4c8486b070c327428d21 - srcFile: /content/authoring/nlr1452803799189.xmld20 task id: loioea6a873f8f99402db89927b7cd0716ed loio28929f86523b4c8486b070c327428d21 copya31f326508374e4a978402bb8c176654 - srcFile: /

content/authoring/omh1452803819660.xml



○ Change AgreeToSAPLicense from false to true in the line below, to indicate your acceptance of the end user license agreement:

-V AgreeToSAPLicense="false"

○ Uncomment AdminPassword in the line below, and assign a non-null value:

#-V AdminPassword=""

○ Uncomment keyStorePassword in the line below, and assign a non-null value:

#-V KeystorePassword=""

NoteFor both the admin password and the keystore password, only alphabetic and numeric characters, spaces, periods, colons, dashes, and hyphens are allowed.

If you have installed a custom database and you want to install SAP Mobile Platform to work with it, you must set the parameters as indicated in the table below. Other parameters you can change are documented in comments in the SilentInstall_Linux.txt file.


-V developerInstall="false"

The default setting is true, which specifies a developer installation, with no options, using the Derby database.

Change to false to enable a production installation, which allows you to set all other parameters, including a custom database.

NoteWhenever you change the developerInstall setting, you must change the productionInstall to be the opposite.

-V productionInstall="true"

The default setting is false, which specifies a developer installation, with no options, using the Derby database.

Change to true to enable a production installation, which allows you to set all other parameters, including a custom database.

NoteWhenever you change the productionInstall setting, you must change the developerInstall to be the opposite.

-V derbyDB="false"

The default setting is true, which specifies the default Derby database.

Change to false to enable selection of another database.



-V existDB="true"

The default setting is false, which disables selection of a database other than Derby.

Change to true to enable selection of another database.

-V existDBType="<database_choice>"


Set the value to select the database you have installed to use with SAP Mobile Platform:○ ase○ db2○ oracle-sid or oracle-svc

-V dbHostName="<database_host_name>"


Set the value to the name of the host on which you have installed the database to use with SAP Mobile Platform:

-V dbPortNumber="<database_port>"


Set the value to the port number your database uses.

-V dbLogin="gomobile"


Set the value to gomobile, or the new user name if you changed it from the default. This value was set for the administrator's ID for the SAP Mobile Platform database by the scripts that you ran.

-V dbPassword="secret"


Set the value to secret, or the new user password if you changed it from the default. This value was set for the administrator's password for the SAP Mobile Platform database by the scripts that you ran.

-V dbDBName="smp3"


Set the value to smp3, or the new database name, if you changed it from the default. This value was set for the SAP Mobile Platform database name by the scripts that you ran.

NoteIf you are using Oracle, dbDBName is either the service name or the SID, depending on how you access Oracle.

-V ignorePingError="false"





CautionLeave the value as false (recommended) to stop the installer if it cannot successfully ping your database, using the values that you have specified. If this option is true and the database ping fails, the installation completes, but the server will not start.

-V oracleJdbcDriver="<jdbc_path>"

(Oracle only) Delete the "#" at the start of the line to enable the parameter.

Set the value to the path to your Oracle JDBC driver, ojdbc6.jar or ojdbc6_g.jar.

NoteIf you wish to change the installation directory, uncomment the line below and replace "{User home directory}" with a valid path to the desired installation directory:

#-P installLocation="<{User home directory}>/SAP/MobilePlatform3"

If you uncomment this line without changing "{User home directory}" the installation will fail.

5. Save and close the SilentInstall_Linux.txt file.

6. Launch the installer:




Installation Successful


Next task: Verifying the Added Node [page 26]


3.2.2 Verifying the Added Node[d21]

Check for errors in the installation log file, then verify that you can start SAP Mobile Platform Server, log in to Management Cockpit, and see the SAP Mobile Platform Server properties.

Procedure



A quick way to do this is:








4. Verify that this server has been added to the cluster.a. Navigate to the Cluster tab.b. Verify that the node you just installed appears.

Nodes are identified by host name.c. Click the node to see additional information.

Next Steps

To install additional nodes in a cluster, repeat this procedure, beginning with Adding Cluster Nodes [page 10], until you have installed all cluster nodes.

If this was the last node in your cluster, continue with Postinstallation Landscape Setup in Administrator.

d21 task id: loioea6a873f8f99402db89927b7cd0716ed loio28929f86523b4c8486b070c327428d21 copy9a2b7b9525c64f7d9a94be782d52539b - srcFile: /content/authoring/iti1452803839161.xml






4 Troubleshooting[d22]

Review information about common problems that arise in the SAP Mobile Platform Server upgrade process.

For information about contacting SAP Technical Support, see Issues Requiring Product Support [page 32].

4.1 Quick Fixes to Simple Problems[d23]

Quick fixes are usually common, single-cause problems that you can solve with minimal overhead or additional support.

4.1.1 Server Node Does Not Start[d24]

Problem[d24]

After installing or upgrading a node in the cluster, one or more server nodes do not start.

Assess and Correct[d24]

Assess the root cause and take the appropriate corrective action.

Root Cause Assessment Correction

The version of the server node is incompatible with the rest of the cluster.

On a server node that is not starting, review the <SMP_HOME>\Server\log\osgi.log for the following message:

Upgrade the server node to a compatible version, then start the server.

d22 concept id: loio7c28f21370061014bb19c03c070dda34 - srcFile: /content/authoring/mig1392468963918.xmld23 reference id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 - srcFile: /content/authoring/i841435856484373.xmld24 reference id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 loiof4d08c849b4f42e599958bdf2940d76c - srcFile: /

content/authoring/pvp1480969475210.xmld24 section id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 loiof4d08c849b4f42e599958bdf2940d76c - srcFile: /

content/authoring/pvp1480969475210.xmld24 section id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 loiof4d08c849b4f42e599958bdf2940d76c - srcFile: /

content/authoring/pvp1480969475210.xml


Troubleshooting


The version of this server node (<version number>) is not compatible with the cluster you are attempting to connect to. It must be one of [<compatible version numbers>].

The server node did not connect to the database.


Failed to connect to the database on startup. The following error was returned: <error message>.

Verify that the database is running and the server node can connect to it. The error message may provide more specific information about the source of the problem, such as a network outage. You can use the database logs to determine database-specific errors.

The server node key does not match the key used for the rest of the cluster.

NoteThis problem may occur when you install a second node before the first node has been started.


The key of this server node does not match the cluster you are attempting to connect to it.

Uninstall SAP Mobile Platform Server from the node, then reinstall it.

4.1.2 Server Cannot Start on Newer Version of Windows[d25]

Problem[d25]

On certain newer versions of Windows, the SAP Mobile Platform Server fails to start.

d25 reference id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 loiob5ce16ebe5c543f795c9dfc5b84b194f - srcFile: /content/authoring/tpj1454107171341.xml

d25 section id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 loiob5ce16ebe5c543f795c9dfc5b84b194f - srcFile: /content/authoring/tpj1454107171341.xml

Upgrade: SAP Mobile Platform Server for LinuxTroubleshooting P U B L I C 29

Solution[d25]

This may indicate that the org.osgi.framework.os.name=win32 entry is missing from the config.ini file. To fix:

1. Navigate to: <SMP_HOME>.2. Open config.ini in a text editor, and search for the following line:

org.osgi.framework.os.name=win323. If the line does not exist, add it and save the file.4. Restart SAP Mobile Platform Server.

4.1.3 Server Node Does Not Join the Cluster[d26]

Problem[d26]

While viewing the server log on a working node in the cluster, you see that the number of current addresses in the cluster is incorrect. For example, after adding a second node, the log says the number of current addresses in the cluster is 1:

Cluster node channel name: 'SERVERNAME-27525(bind_addr=192.168.1.100:55450)' SMP Cluster: Current Addresses in cluster: 1. Addresses previously in cluster: 0

NoteYou can view the log in Management Cockpit connected to a working node, or in <SMP_HOME>\Server\log on the file system of a working node.



d25 section id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 loiob5ce16ebe5c543f795c9dfc5b84b194f - srcFile: /content/authoring/tpj1454107171341.xml

d26 reference id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 loio8ffd129ee2194d729df18a7ac4ebdb36 - srcFile: /content/authoring/yqd1480969526574.xml

d26 section id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 loio8ffd129ee2194d729df18a7ac4ebdb36 - srcFile: /content/authoring/yqd1480969526574.xml

d26 section id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 loio8ffd129ee2194d729df18a7ac4ebdb36 - srcFile: /content/authoring/yqd1480969526574.xml


Troubleshooting


The node cannot be reached using the IPv4 network interface, which is the default for SAP Mobile Platform Server.

The node can be reached using IPv6 instead of IPv4.

In <SMP_HOME>\Server\configuration\com.sap.mobile.platform.server.launcher\fixed-sys.properties, remove the following line:

-Djava.net.preferIPv4Stack=true

NoteYou must delete this line; you cannot simply comment it out.

SAP Mobile Platform Server is bound to an IP address that is not routed to a node in the cluster.

The address that SAP Mobile Platform Server is bound to is shown in the log (bind_addr).

In some situations, such as when the node is connected to two or more networks that do not allow routing, you must specify the IP address that the cluster should bind to.

In <SMP_HOME>\Server\props.ini, add a -Djgroups.bind_addr line to specify the node address. For example:

-Djgroups.bind_addr=192.168.0.2

On each node in the cluster:

1. Correct the appropriate property file.2. Restart the server for the changes to take effect.

4.1.4 SP05 to SP06 Upgrade Fails Because Service Fails to Install[d27]

Problem[d27]

Upgrading SAP Mobile Platform from SP05 to SP06 fails because the SAPSMP3Service fails to install.



d27 reference id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 loio084dd65954644e3e9b5cee5a9726c235 - srcFile: /content/authoring/qsm1452814903559.xml

d27 section id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 loio084dd65954644e3e9b5cee5a9726c235 - srcFile: /content/authoring/qsm1452814903559.xml

d27 section id: loio7c28f21370061014bb19c03c070dda34 loio7c28a22b70061014a0f8bc9e7a817854 loio084dd65954644e3e9b5cee5a9726c235 - srcFile: /content/authoring/qsm1452814903559.xml



Any of these tools are open:

● Microsoft Management Console (MMC)

● Services console● Event viewer

Visual inspection To close all instances, run: taskkill /F /IM mmc.exe

Either of these tools are open:

● SysInternals Process Explorer● Task Manager

Visual inspection Close the tool

4.2 Issues Requiring Product Support[d28]

Your SAP support ID gives you access to enterprise-level incident support as part of your support plan on SAP Service Marketplace.

Product Support can help you resolve new undocumented incidents with software installation, start-up, and overall use, as well as provide diagnostic and troubleshooting assistance for known problems with a new or undocumented cause.

4.2.1 Product Support Engagement Requirements[d29]

If you use SAP Service Marketplace to engage with Product Support, you must meet certain requirements.

Service Marketplace Case Creation Requirements[d29]

Be prepared to provide:

● A valid installation number for SAP Mobile Platform● A valid service contract with SAP● A valid system ID (S-User ID)● An enabled NetViewer connection.

d28 reference id: loio7c28f21370061014bb19c03c070dda34 loio7bff348c7006101488ed8ec1d3a80ce9 - srcFile: /content/authoring/wnx1452716358952.xmld29 reference id: loio7c28f21370061014bb19c03c070dda34 loio7bff348c7006101488ed8ec1d3a80ce9 loio7bff302270061014ad4a81202b223fb5 - srcFile: /

content/authoring/oee1452716680866.xmld29 section id: loio7c28f21370061014bb19c03c070dda34 loio7bff348c7006101488ed8ec1d3a80ce9 loio7bff302270061014ad4a81202b223fb5 - srcFile: /

content/authoring/oee1452716680866.xml


Troubleshooting

SAP Mobile Platform Incident Requirements[d29]

● Configure all logs to an appropriate level for your issue. Product Support requires details from one or more of the system logs.

● Capture these basic incident details to help Product Support analyze the problem, and determine any next steps:○ Environment summary: product version, back end, client type (device and OS), proxy connections.

These details help isolate component that is causing the failure. If you have an architecture diagram, share it with SAP.

○ Problem description: what were the actions preceded the incident. Capture all details that allow Product Support to reproduce the issue.

● Locate the server version in the SMP_HOME\Server\version.properties file.

4.2.2 Creating an Incident on SAP Service Marketplace[d30]

If you cannot resolve problems with the troubleshooting documentation for SAP Mobile Platform, go to SAP Service Marketplace for additional help.

Use SAP Service Marketplace to create an incident message for Product Support. Keywords from this message return related articles from the Knowledge Base. Before you submit a message, review these articles to see if they resolve your problem.

1. Go to http://support.sap.com/incident .2. Create a message using the wizard.

NoteYou must know the component ID for SAP Mobile Platform to return the correct scope of Knowledge Base Articles and to correctly route the message to Product Support. On-premise installations of SAP Mobile Platform use a different ID than cloud instances. See Knowledge Base Article 1915061- How to Choose a Component for SAP Mobile Platform 3.x in Service Marketplace .

3. Once the message is processed, you receive an e-mail notification of the solution.

d29 section id: loio7c28f21370061014bb19c03c070dda34 loio7bff348c7006101488ed8ec1d3a80ce9 loio7bff302270061014ad4a81202b223fb5 - srcFile: /content/authoring/oee1452716680866.xml

d30 reference id: loio7c28f21370061014bb19c03c070dda34 loio7bff348c7006101488ed8ec1d3a80ce9 loio7bff2ab970061014b817861fd924b9f9 - srcFile: /content/authoring/tly1452716463288.xml


http://help.sap.com/disclaimer?site=https://support.sap.com/incident

http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/1915061

http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/1915061

Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).


Important Disclaimers and Legal Information

http://help.sap.com/disclaimer/

Upgrade: SAP Mobile Platform Server for LinuxImportant Disclaimers and Legal Information P U B L I C 35

go.sap.com/registration/contact.html

© 2016 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 http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

Date post:	17-Mar-2018
Category:	Documents
Upload:	phungtruc
View:	234 times
Download:	3 times

Upgrade: SAP Mobile Platform Server for Linux · PDF fileContent 1 Upgrade: SAP Mobile...

Documents