Running the Installer

Start the SAP Mobile Platform Server installer, accept the end-user license agreement and specify installation options, then launch and complete the installation process.

1. Browse to the root directory of the SAP Mobile Platform installer, right-click the setupAMD64.exe file and select Run as Administrator.
   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 appear.
2. On the installer welcome page, click Next.
3. On the end-user license agreement page, select your country, accept the terms of the license agreement and click Next.
4. Specify the absolute path to the installation location, which must be on a local drive on the target host.

   The total length of the path must be 38 characters or less.

   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.
5. Select the type of installation you want to perform, then click Next.

   Installation Type	Description
   Developer installation	Installs the SAP Mobile Platform components with default settings, using the default Derby database for development. You cannot specify any additional installation options. For a developer installation that uses ASE, DB2, or Oracle as the database, select the Production installation , then accept the defaults for everything except the database.
   Production installation	Allows you to specify various settings for your SAP Mobile Platform installation, including the production database manager.

6. Enter admin user credentials for your SAP Mobile Platform installation.

   All these entries are case-sensitive.

   • Admin user name – the admin user who will manage SAP Mobile Platform through the Management Cockpit.
   • Admin password – the password for the admin user.
   • Keystore password – the password that will be required to access the keystore, where SAP Mobile Platform Server stores certificates and private keys.

   For both the admin password and the keystore password, only alphabetic and numeric characters, space, period, colon, dash, and hyphen are allowed. The following characters are not allowed: ! ? , ; " ' ` + * ^ / \ | = ~ < > @ # $ % & ( ) [ ] { }

7. (Optional) If you selected Production installation, specify the port numbers to use for the SAP Mobile Platform Server HTTP and HTTPS communication ports and click Next.
8. (Optional) If you selected Production installation, on the database server configuration panel, specify your database information:
   • Use the default Derby database – select this for a development installation of SAP Mobile Platform.
     Note: Derby is supported only for developer and proof-of-concept installations; Derby is not supported in production installations.
   • Use another database you have already installed – select this for a production installation of SAP Mobile Platform, where you have installed your own database management software.
     • Select database type – select the specific database type you have installed: ASE, DB2, Oracle (Service Name), or Oracle (SID).
     • Host name – the fully qualified domain name or static IP address of the database server.
     • Port number – the listening port of the database server. Default values:
       • ASE – 5000
       • DB2 – 50000
       • Oracle – 1521
     • Login – enter gomobile, or the new user name if you changed it from the default.
     • Password – enter secret, or the new user password if you changed it from the default.
     • Database name (ASE or DB2), Service name (Oracle accessed by service name), or SID (Oracle accessed by SID) – enter smp3, or the new database name, if you changed it from the default.
       • Oracle service name is the TNS alias used for a remote connection.
       • Oracle SID is a name that uniquely identifies the database instance on the database server.
     • Path to Oracle JDBC driver – (Oracle only) enter the fully qualified path, including the JAR file name, to the type 4 Oracle JDBC driver.

   If the installer displays a Cannot connect to database error:

   1. Verify that the database server is running.

      If it is not running, start it, then click Retry in the message box.

   2. If the database server is running, check all the values entered on the database server configuration panel.

      If any are incorrect, click Cancel in the message box, correct the entries, and click Next on the database server configuration panel.

   3. If the database server is running and all entries on the database server configuration panel appear to be correct, check the log at SMP_HOME\InstallLogs\SMPInstall<date-time>.log.
      1. Examine the messages in the log file, starting at the end and working backward, to find more information about the database connection failure.
      2. Correct any problems logged.
      3. Return to the database server configuration panel and click Retry in the message box.
9. On the summary information page, click Install.
10. Click Finish.