installing the smp 3.0 server overview

Installing the SMP 3.0

Server Overview

October, 2013

© 2013 SAP AG. All rights reserved. 2

This is the current state of planning and may be changed by SAP at any time.

Legal Disclaimer

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without

the permission of SAP. This presentation is not subject to your license agreement or any other service or

subscription agreement with SAP. SAP has 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's strategy and possible future developments, products and

or platforms directions and functionality are all subject to change and may be changed by SAP 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. This document is provided without a warranty of any

kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness

for a particular purpose, or non-infringement. This document is for informational purposes and may not be

incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except

if such damages were caused by SAP´s willful misconduct or gross negligence.

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.



At the end of this module, you will be able to:

Describe the two installation types of SMP 3.0 platform server

Describe the three databases that can be used for the custom

installation

Know how to configure a third party database before installation

Explain the options available for each installation option

Know how to run the installer

Verify that the installation completed correctly

Start and stop the SMP 3.0 platform server

Uninstall the SMP 3.0 platform server

Objectives



Agenda

Introduction

Installation Preparation

Custom Database Preparation

SMP 3.0 Installation

Developer installation

Custom Installation

Verifying the installation

Starting and stopping the SMP 3.0 server

Uninstalling the SMP 3.0 Server

Introduction



SMP 3.0 Installation Options

Installation Type Description

Developer installation Installs SAP Mobile Platform Server components with default

settings, using embedded Derby database. No additional

installation options can be specified.

Note: For a developer installation that uses ASE, DB2, or

Oracle as the database, select the Production installation,

Standard option, then accept the defaults for everything

except the database.

Production installation Allows you to specify various settings for your SAP Mobile

Platform Server installation, including which database system

you are going to be using

Installation Preparation



Info needed prior to installation

Host Information – Name of server where SAP Mobile Platform Server is to be

installed

Installer Directions

Installation Directory

Default: C:\SAP\MobilePlatform3

Custom

Installation Type

Developer installation

Production installation



Additional Installation Decisions

Options for Custom Installation

Configure SAP Mobile Platform Server communication port: Use this option if you want to

change default communication port numbers.

Set SAP Mobile Platform Server services to start automatically: This is selected by default.

Unselect this option if you wish to start up SAP Mobile Platform Server services manually.

HTTP port (Default: 8080)

HTTPS port (Default: 8081)

SAP Mobile Platform Server Administrator User & Password: These credentials are used by

the SMP administrator to access the SMP Cockpit.



Additional Installation Options to be Specified

Master Key and Keystore Password: This is the seed key to be used by server to

generate private key for encrypting sensitive information.

Database to use - select one:

• Derby database (default)

• Existing database:

• ASE

• DB2

• Oracle



If Installing a custom database

You need this information about the database server:

• Database host name:

• Database login:

• Database password:

• Database port:

• Database name:

• (Oracle only) Database service name:

Custom Database

Preparation ASE

DB2

Oracle



ASE Database Preparation

Step 1 – Install ASE

Install the ASE database software you plan to use with SAP Mobile Platform Server. You can install the database software anywhere on the same network where you will be

installing SAP Mobile Platform.

Record the values for these parameters:

Host name – the name of the host system on which the database software is installed.

Login – the admin login for the database software.

Port number – the port number the database software uses.

Note: In the following steps, <installer_root> is the root directory in the installer

image.




Step 2 – Enter the path for your SMP database

Edit the 001_SMP3_drop_and_create_user.DDL script.

1. Open this script in a text editor: <installer_root>\db_tools\db\ase\smp3\sql\001_SMP3_drop_and_create_user.DDL

2. In the following two lines, replace c:\Sybase\data\ with the path to the location

where you want your SAP Mobile Platform Server database to be created.

– physname = "c:\Sybase\data\smp3.dat"

– physname = "c:\Sybase\data\smp3.log“

Note: The path for your SAP Mobile Platform Server data is independent of the path that you set for

your SAP Mobile Platform Server installation directory. If you locate your database files within the SAP

Mobile Platform Server installation directory tree, the SAP Mobile Platform Server uninstaller will not

remove them.

3. Save and close the file.




Step 3 – Set the path for your SMP database

Run the 001_SMP3_drop_and_create_user.DDL script.

1. Open a Windows command prompt.

2. Navigate to this location in the SAP Mobile Platform Server installer image: <installer_root>\db_utils\db\ase\smp3\sql

3. Enter this command: isql -S<servername> -U<username> -P<password> -i001_SMP3_drop_and_create_user.DDL

Where:

o <servername> is the name of the server where ASE is installed.

o <username> is an admin user, such as sa.

o <password> is the password for <username>.




Step 4 – Configure Quartz

Edit the quartz.properties file.

1. Navigate to : <installer_root>\db_tools\config_master\com.sybase365.mobiliser.framework.event.schedul

er.quartz

2. Open these files in a text editor: o quartz.properties

o quartz.properties.ase

3. Copy the entire contents of quartz.properties.ase and paste it over the entire

contents of the quartz.properties file.

4. Save quartz.properties and close both files. (Preserve the quartz.properties.ase

file as a template for future use.)




Step 5 – Configure SessionFactory

Edit the sessionfactory.properties file.

1. Navigate to : <installer_root>\db_tools\config_master\com.sybase365.mobiliser.framework.persistence.hi

bernate.sessionfactory

2. Open these files in a text editor: o sessionfactory.properties

o sessionfactory.properties.ase

3. Copy the entire contents of sessionfactory.properties.ase and paste it over the

entire contents of the sessionfactory.properties file.

4. Save sessionfactory.properties and close both files. (Preserve the

sessionfactory.properties.ase file as a template for future use.)




Step 6 – Configure the Database Connection Pool

Edit the pool.properties file.

1. Navigate to : <installer_root>\db_tools\config_master\com.sybase365.mobiliser.framework.persistence.jd

bc.bonecp.pool

2. Open these files in a text editor: o pool.properties

o pool.properties.ase

3. Copy the entire contents of pool.properties.ase and paste it over the entire

contents of the pool.properties file.

4. In the pool.properties file, in the lines below, replace the terms in braces with the

appropriate values for your system: o jdbcUrl=jdbc:sybase:Tds:{HOST}:{PORT}/{DBNAME}?APPLICATIONNAME={DBNAME}

o username={USER}

o password={PASSWORD}

5. Save pool.properties and close both files. (Preserve the pool.properties.ase file

as a template for future use.)




Step 7 – Configure the Connection Properties

Edit the connection.properties file.

1. Navigate to : <installer_root>\db_tools\config_master\connection_data

2. Open these files in a text editor: o connection.properties

o connection.properties.ase

3. Copy the entire contents of connection.properties.ase and paste it over the entire

contents of the connection.properties file.

4. In the connection.properties file, in the lines below, replace the terms in braces

with the appropriate values for your system: o javax.persistence.jdbc.url=jdbc:sybase:Tds:{HOST}:{PORT}/{DBNAME}?APPLICATIONNAME={DBNA

ME}&CACHE_COLUMN_METADATA=true

o javax.persistence.jdbc.user={USER}

o javax.persistence.jdbc.password={PASSWORD}

5. Save connection.properties and close both files. (Preserve the

pool.properties.ase file as a template for future use.)




Step 8 – Configure DbMaintain

Edit the dbmaintain script.

1. Make a backup copy of: <installer_root>\db_tools\db\ase\smp3\sql\dbmaintain.properties.ase

2. Open this file in a text editor: <installer_root>\db_tools\db\ase\smp3\sql\dbmaintain.properties.ase

3. Edit the following lines: o database.url=jdbc:sybase:Tds:{HOST}:{PORT}/{DBNAME} database.userName={USER}

o database.schemaNames={USER}

o database.password={PASSWORD}

Replace: o (HOST) with the host name for your database

o (PORT) with the port number for your database

o (DBNAME) with smp3

o (USER) with gomobile (two replacements)

o (PASSWORD) with secret





Step 9 – Run DbMaintain

Run the dbmaintain script against your database.

1. At the Windows command prompt, navigate to the location of the

dbmaintain.properties.ase file: <installer_root>\db_tools\db\ase\smp3\sql

2. Enter: java -jar com.sap.mobile.platform.server.db.ase.dbmaintain-*-scriptarchive-ase.jar -c

dbmaintain.properties.ase

3. Respond to the “Are you sure you want to continue?” prompt.

4. When the dbmaintain script connects to your database, if the

dbMaintainer.fromScratch.enabled parameter is set to true, the script warns you

that any existing objects in the database will be dropped if you continue. Indicate

whether you want to drop existing objects in your database: o If this is a fresh install on a new system, you may safely answer Yes, and the script continues.

o If you want to preserve existing objects in your database:

1. Answer No to the prompt.

2. Edit the following line in the dbmaintain script, replacing true with false:

dbMaintainer.fromScratch.enabled=true

3. Run the dbmaintain script again.




Step 9 – Run DbMaintain, cont’d

5. Review the Dry Run Results.

– If there are issues, respond “No” to cancel the script.

– If there are no issues, respond “Yes” to the prompt.

If you respond Yes, the script takes several minutes to complete, then ends with “The database has been

updated successfully.”



DB2 Database Preparation

Step 1 – Install DB2

Install the ASE database software you plan to use with SAP Mobile Platform. You can install the database software anywhere on the same network where you will be






Note: In the following steps <installer_root> is the root directory in the installer

image.





Edit the 001_SMP3_drop_and_create_user.DDL script.

1. Open this script in a text editor:

<installer_root>\db_utils\db\db2\smp3\sql

2. In the following two lines, replace c:\Sybase\data\ with the path to the location

where you want your SAP Mobile Platform Server database to be created.

– physname = "c:\Sybase\data\smp3.dat "

– physname = "c:\Sybase\data\smp3.log “

Note: The path for your SAP Mobile Platform Server data is independent of the path that you set for

your SAP Mobile Platform Server installation directory. If you locate your database files within the SAP

Mobile Platform Server installation directory tree, the SAP Mobile Platform Server uninstaller will not

remove them.






Run the 001_SMP3_drop_and_create_user.DDL script.


2. Navigate to this location in the SAP Mobile Platform Server installer image: <installer_root>\db_utils\db\db2\smp3\sql

3. Enter this command: db2 -tvsf 001_SMP3_drop_and_create_user.DDL






1. Navigate to : <installer_root>\db_tools\config_master\com.sybase365.mobiliser.framework.event.schedul

er.quartz


o quartz.properties.db2

3. Copy the entire contents of quartz.properties.db2 and paste it over the entire


4. Save quartz.properties and close both files. (Preserve the quartz.properties.db2

file as a template for future use.)






1. Navigate to : <installer_root>\db_tools\config_master\com.sybase365.mobiliser.framework.persistence.hi



o sessionfactory.properties.db2

3. Copy the entire contents of sessionfactory.properties.db2 and paste it over the



sessionfactory.properties.db2 file as a template for future use.)






1. Navigate to : <installer_root>\db_tools\config_master\com.sybase365.mobiliser.framework.persistence.jd

bc.bonecp.pool


o pool.properties.db2

3. Copy the entire contents of pool.properties.db2 and paste it over the entire


4. Save pool.properties and close both files. (Preserve the pool.properties.db2 file

as a template for future use.)






1. Navigate to : <installer_root>\db_tools\config_master\connection_data


o connection.properties.db2

3. Copy the entire contents of connection.properties.db2 and paste it over the entire


4. In the connection.properties file, in the lines below, replace the terms in braces

with the appropriate values for your system: o javax.persistence.jdbc.url=jdbc:db2://{HOST}:{PORT}/{DBNAME}\:useJDBC4ColumnNameAndLabelS

emantics\=2;

o javax.persistence.jdbc.user={USER};

o javax.persistence.jdbc.password={PASSWORD};


pool.properties.db2 file as a template for future use.)






1. Make a backup copy of: <installer_root>\db_tools\db\db2\smp3\sql\dbmaintain.properties.db2

2. Use a text editor to open: <installer_root>\db_tools\db\db2\smp3\sql\dbmaintain.properties.db2

3. Edit the following lines: o database.url=jdbc:db2://{HOST}:{PORT}/{DBNAME}

o database.userName={USER}

o database.schemaNames={USER}

o database.password={PASSWORD}

Replace: o (HOST) with the host name for your database


o (DBNAME) with smp3










dbmaintain.properties.db2 file <installer_root>\db_tools\db\db2\smp3\sql

2. Enter: java -jar com.sap.mobile.platform.server.db.db2.dbmaintain-*-

scriptarchive-db2.jar -c dbmaintain.properties.db2

3. Respond to the Are you sure you want to continue? prompt.





o If you want to preserve existing objects in your database:










• If there are issues, respond “No” to cancel the script.

• If there are no issues, respond “Yes” to the prompt.





Oracle Database Preparation

Step 1 – Install Oracle

Install the Oracle database software you plan to use with SAP Mobile Platform

Server. You can install the database software anywhere on the same network where you will be






Note: In the following steps <installer_root> is the root directory in the installer

image.





Create the smp3.sql script:


2. Navigate to this location in the SAP Mobile Platform Server installer image: <installer_root>\db_utils\db\oracle\smp3\sqlc

3. Use a text editor to create a smp3.sql file in this location.

4. Use a text editor to open 001_SMP3_drop_and_create_user.DDL from this

location and copy its entire contents into the smp3.sql file.

5. As the last line in the smp3.sql file, enter: EXIT;

6. Save and close the smp3.sql file.





Run the smp3.sql script.


2. Navigate to this location in the SAP Mobile Platform Server installer image: <installer_root>\db_utils\db\oracle\smp3\sql

3. Enter this command: sqlplus <username>/<password>@<servername> @smp3.sql > smp3.log

Where:

o <servername> is the name of the server where Oracle is installed.

o <username> is an admin user, such as sa.

o <password> is the password for <username>.






1. Navigate to: <installer_root>\db_tools\config_master\com.sybase365.mobiliser.framework.event.schedul

er.quartz


o quartz.properties.oracle

3. Copy the entire contents of quartz.properties.oracle and paste it over the entire


4. Save quartz.properties and close both files. (Preserve the

quartz.properties.oracle file as a template for future use.)






1. Navigate to: <installer_root>\db_tools\config_master\com.sybase365.mobiliser.framework.persistence.hi



o sessionfactory.properties.oracle

3. Copy the entire contents of sessionfactory.properties.oracle and paste it over the



sessionfactory.properties.oracle file as a template for future use.)






1. Navigate to: <installer_root>\db_tools\config_master\com.sybase365.mobiliser.framework.persistence.jd

bc.bonecp.pool


o pool.properties.oracle-xxx

where xxx indicates the way you access your Oracle database instance:

o sid if you use the system ID (SID)

o svc if you use the service name

3. Copy the entire contents of pool.properties.oracle-xxx and paste it over the entire





Step 6 – Configure the Database Connection Pool, cont’d

5. In the pool.properties file, in the lines below, replace the terms in braces with the

appropriate values for your system: o (HOST) with the host name for your database


o (SERVICE) or (SID) with smp3

o (USER) with gomobile


6. Save pool.properties and close both files. (Preserve the pool.properties.oracle-

xxx file as a template for future use.)






1. Navigate to: <installer_root>\db_tools\config_master\connection_data


o connection.properties.oracle-xxx


o sid if you use the system ID (SID)

o svc if you use the service name

3. Copy the entire contents of connection.properties.oracle-xxx and paste it over the entire





Step 7 – Configure the Connection Properties, cont’d

4. In the connection.properties file, replace terms in parentheses with appropriate

values for your system: o (HOST) with the host name for your database



o (USER) with gomobile



connection.properties.oracle-xxx file as a template for future use.)






1. Make a backup copy of: <installer_root>\db_tools\db\oracle\smp3\sql\dbmaintain.properties.oracle-xxx


– sid if you use the system ID (SID)

– svc if you use the service name

2. Open this file in a text editor: <installer_root>\db_tools\db\oracle\smp3\sql\dbmaintain.properties.oracle-xxx.

3. Replace the terms in parentheses with appropriate values for your system: o (HOST) with the host name for your database












dbmaintain.properties.oracle-xxx file: <installer_root>\db_tools\db\oracle\smp3\sql

2. Enter: java -jar com.sap.mobile.platform.server.db.oracle.dbmaintain-*-

scriptarchive-oracle.jar -c dbmaintain.properties.oracle

3. Respond to the “Are you sure you want to continue?” prompt.





o If you wish to preserve existing objects in your database:










• If there are issues, respond “No” to cancel the script.

• If there are no issues, respond “Yes” to the prompt.



SMP 3.0 Installation Developer

Custom



Run the SMP 3.0 Installer on Windows

Browse to the root directory of the SAP Mobile Platform Server installer,

and:

On Windows 7 and Windows Server 2008 R2, right-click the setupAMD64.exe file and

select Run as Administrator.

On earlier supported versions of Windows, double-click the setupAMD64.exe file.

Note: The installer displays an "Initializing wizard..." message while it verifies the

integrity of the installation image. It may take a few minutes for the first installer panel to

display.



SMP 3.0 Installer

On the installer welcome page, click

Next.

Note: the first steps of the installer are

the same for all three installations



SMP 3.0 Installer

On the end-user license agreement

page:

• Select your country

• Accept the terms of the license

agreement radio button

Click Next.



SMP 3.0 Installer

Specify the absolute path to the

installation location, which must be on a

local drive on the target host.

Directory names in the path can contain

only:

ASCII alphanumeric characters

Underscore ( _ ), hyphen ( - ), and period (.)

characters (two consecutive period

characters are not allowed and none of

these characters may appear as the first

character in a folder name)

No characters between "Mobile Platform"

and the preceding "\" character.

Note: The total length of the path must

be 38 characters or less.



SMP 3.0 Installer

If the path specified does not exit on the

file system, you will get a message

telling you it will be created.

Click Yes to continue.

Click No to go back.



SMP 3.0 Installer

Notification that a prerequisite C++

Runtime is being installed.

No action necessary.



SMP 3.0 Installer

Select the type of installation you want to

perform:

Developer Installation

Production Installation

Click Next.

SMP 3.0 Developer

Installation



Developer Install

Specify the SUP 3.0 administration user

id and password.

Also specify the password for encrypting

the keystore.

Note: The password must be a

minimum length of 8 characters.



Developer Install

Confirmation prior to starting the

installation.

When you are ready, click the Install

button.



Developer Install

The developer installation is

complete.

You can view the Release Bulletin when

you exit the installation screens, or exit

and view the Release Bulletin later from

the SAP Help Portal.

To view the Release Bulletin, click the

View Release Bulletin checkbox and

click the Finish button.

To simply exit the installation screens,


SMP 3.0 Production

Installation




Select the Custom Installation radio

button.

Select the Next button to continue.




Specify the SUP 3.0 administration user

ID and password.

Also specify the password for encrypting

the keystore.

Note: The password must be a

minimum length of 8 characters.




You have the option of changing the

following ports at installation time:

HTTP Port

HTTPS Port

HTTPS Mutual SSL Port

HTTPS Administration Port

Click Next.




Preliminary subcomponent installation.




You still have the option of using the

Tomcat Derby database, but for this

example choose another database

option radio button.

Select the database for the drop down

list.

Fill in the following information:

Host name

Port number

User Login

User Pasword

Database name

Service Name (Oracle only)

Press the Next Button.




Confirmation prior to starting the

installation.

When you are ready, click the Install

button.



Production Installation Running




The custom installation is complete.

You can view the Release Bulletin when

you exit the installation screens, or exit

and view the Release Bulletin later from

the SAP Help Portal.

To view the Release Bulletin, click the

View Release Bulletin checkbox and


To simply exit the installation screens,


SMP 3.0 Linux Installation



Setting up the Linux Silent Installer

Open a terminal window.

Go to the root directory of your installer image.

Use a text editor to open the SilentInstall_Linux.txt file.

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 AgreeToSybaseLicense="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=""



Other Custom Install Options (1)

Parameter Explanation

-V

developerInstall="fal

se"

The default setting is true, which specifies a developer installation, with no options,

using the Derby database.

Change to false to enable custom installation, which allows you to set all other

parameters, including a custom database.

-V

customInstall="true"

The default setting is false, which disables custom installation

Change to true to specify a custom installation.

-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="<data

base_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

-V

dbHostName="<data

base_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="<dat

abase_port>"


Set the value to the port number your database uses.



Other Custom Install Options (2)

Parameter Explanation

-V dbLogin="gomobile" Delete the "#" at the start of the line to enable the parameter.

Set the value to gomobile. This value was set for the administrator's ID

for the SAP Mobile Platform Server database by the scripts that you

ran.

-V dbPassword="secret" Delete the "#" at the start of the line to enable the parameter.

Set the value to secret. This value was set for the administrator's

password for the SAP Mobile Platform database by the scripts that you

ran.

-V dbDBName="smp3" Delete the "#" at the start of the line to enable the parameter.

Set the value to smp3. This value was set for the SAP Mobile Platform

database name by the scripts that you ran.

Note: If you are using Oracle, dbDBName is either the service name or

the SID, depending on how you access Oracle.

-V

ignorePingError="<boolean>"


Warning! Leave 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.



Running the Linux Silent Installer

If 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}“

Note: If you uncomment this line without changing "{User home directory}" the installation

will fail.

Save and close the SilentInstall_Linux.txt file.

Launch the installer: sh SilentInstall_Linux.sh

Note: The 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 Successful

Validating the Installation



Check Installation Log on Windows

Check the installation log at SMP_HOME\InstallLogs\SMPInstall<date-time>.log.

A search for "error" should not find anything.

Also look for the message “SAP Mobile Platform 3.0 has been installed

successfully.”



Desktop Icons in Windows

Upon successful installation you will get 3

desktop icons. They are:

Start SAP Mobile Platform Server

Stop SAP Mobile Platform Server

SAP Management Cockpit



Check Installation Log on Linux

Check the installation log at

SMP_HOME/InstallLogs/SMPInstall<timestamp>.log.

SMP_HOME is the installation location you specified (the default is

$HOME/SAP/MobilePlatform3/).

A quick way to do this is: grep -i error SMP*log

Starting and Stopping the

SMP 3.0 Platform



Start the SMP 3.0 Server on Windows

Click On the Start SAP Mobile Platform

Server icon on desktop.

A window pops up with log information.



Starting the SMP 3.0 Windows Service



Start the SMP 3.0 Server on Linux

In a terminal window,

enter:> cd SMP_HOME/Server

> ./go.sh

.



Launching the Administration Cockpit

You can launch the administration

cockpit by:

• Clicking on the desktop icon

• Entering the URL in your browser: https://<servername>:8083/Admin/

• Using the Windows start menu: Start > (All) Programs > SAP > SAP

Mobile Platform Management Cockpit

Log on using the administration

credentials specified during installation.



Stop the SMP 3.0 Server on Windows

Click On the Stop SAP Mobile Platform

Server icon on the desktop.

A window pops up with log information:



Stopping the SMP 3.0 Windows Service



Stop the SMP 3.0 Server on Linux

In a terminal window,

enter:> cd SMP_HOME/Server

> ./stop.sh

Uninstalling the SMP 3.0

Platform



Planning for Reinstallation

If you plan to reinstall SAP Mobile Platform Server in the same location after

you have uninstalled it, follow these guidelines.

To avoid problems with reinstallation after you have uninstalled SAP Mobile

Platform:

When you have finished uninstalling SAP Mobile Platform Server on a particular server,

manually remove any folders and files that remain.



Preparing to Uninstall

1. While SAP Mobile Platform Server is running, uninstall any other SAP products

that require SAP Mobile Platform Server to be installed first. This includes products such as SAP Mobile Sales for SAP CRM and SAP Mobile Workflow

for SAP Business Suite. See the product-specific Installation Guide for instructions.

2. Shut down all SAP software, SAP processes, and associated third-party

processes running on the host. Open the Windows Services panel to confirm services are stopped. You may need to

manually stop any SAP Mobile Platform Server services that are still running.

3. Move or copy any user-created files and log files that you want to keep from the

SAP Mobile Platform Server installation directories to another location. If you have been using the embedded Darby database and you plan to reinstall SAP

Mobile Platform, preserve data by backing up the SAP Mobile Platform Server databases.

Note: If you have been using an external database, uninstalling SAP Mobile

Platform Server leaves that SAP Mobile Platform Server database intact.



SMP 3.0 Uninstalling on Windows

1. Open the Windows Uninstall program and double click on SAP Mobile

Platform Server 3.0 to start the uninstall wizard.




2. Click on the Next button to continue.




3. Verify the uninstall information and press the Uninstall button.




You will get messages and progress bar to show you the status on the

uninstallation.




4. When you get a “successful uninstallation” message, press the Finish

button to complete the wizard.




5. Go to the Installation Directory and Delete it.



Running the Uninstaller on Linux

Run a shell script to uninstall SAP Mobile Platform Server components.

1. Open a terminal window.

2. Go to SMP_HOME.

3. 3.Launch the uninstaller:

sh SilentUninstall_Linux.sh –console

4. 4.When you see the message that SAP Mobile Platform was successfully

uninstalled, enter exit to close the terminal window.

5. Delete any folders and files remaining in the SAP Mobile Platform Server

installation directory.



You should now be able to

Describe the two installation types of SMP 3.0 platform server

Describe the three database that can be used for the custom

installation

Know how to configure a third party database before installation

Explain the options available for each installation option

Know how to run the installer

Verify that the installation completed correctly

Start and Stop the SMP 3.0 platform server

Uninstall the SMP 3.0 platform server

Summary



© 2013 SAP AG. 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 AG.

The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or

warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group

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

Germany and other countries.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

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



installing the smp 3.0 server overview

Documents

sap ag

production installation

installation types of

permission of sap

server introduction

platform server objectives

server overview

current state of planning