Install SAP OCB Retail – 4 – Validation

After enabling OCB features, you should check if folders and files are correctly available in SMP3. In theory, the enablement worked, when OCB files are available in the features, plugins and webapp folder of SMP3.

Features

ls /SAP/MobilePlatform3/Server/features/ | grep "com.sap.banking.omnichannel*"

You should get a list of 5 folders.

  • com.sap.banking.omnichannel.bpw.web_8.3.1.1-v201512150916
  • com.sap.banking.omnichannel.businesscentral.web_8.3.1.1-v201512150916
  • com.sap.banking.omnichannel.onlinebanking.web_8.3.1.1-v201512150916
  • com.sap.banking.omnichannel.platform_8.3.1.1-v201512150916
  • com.sap.banking.omnichannel.provisioning_8.3.1.1-v201512150916

Plugins

ls /SAP/MobilePlatform3/Server/plugins | grep "com.sap.banking"

You should get a huge list of folders

  • […]
  • com.sap.banking.banking-applications_8.3.1.1.jar
  • com.sap.banking.banking-approvalconfig_8.3.1.1.jar
  • com.sap.banking.banking-approvalpluginconfig_8.3.1.1.jar
  • com.sap.banking.banking-bankconfig_8.3.1.1.jar
  • com.sap.banking.banking-bankingconfig_8.3.1.1.jar
  • com.sap.banking.banking-bankingreport-api_8.3.1.1.jar
  • com.sap.banking.banking-bankreport_8.3.1.1.jar
  • com.sap.banking.banking-billpay_8.3.1.1.jar
  • com.sap.banking.banking-billpay-api_8.3.1.1.jar
  • com.sap.banking.banking-billpayconfig_8.3.1.1.jar
  • com.sap.banking.banking-bptw_8.3.1.1.jar
  • […]

Webapps

ls /SAP/MobilePlatform3/Server/webapps/

Three banking-* folders must exist.

Install SAP OCB Retail – 3 – Enable SAP Omnichannel Retail Banking

While installing OCB, SMP3 had to be stopped. During the installation, the database was prepared and files that represent the OCB application were copied to SMP3. Those bundles are now available in SMP3 (OSGI bundles), but are not activated. To be able to use OCB, the features must be activated by SMP3 administration in the Admin web interface. First, start SMP3.

Add OCB p2 repository

Log on to the SMP3 admin interface and navigate to settings -> repositories

Add the repository created above by the installer

file://SAP/MobilePlatform3/Server/p2/com.sap.banking.omnichannel.repository

Enable OCB features

After adding the p2 repository containing the OCB features, you can enable them. Navigate to Settings -> Features & Components.

The screen shows the available features for SMP3. With adding the OCB p2 repository, the OCB features are listed. You have to follow a specific order when activating the features.

  1. com.sap.banking.omnichannel.provisioning.feature.group
  2. com.sap.banking.omnichannel.platform.feature.group
  3. com.sap.banking.omnichannel.bpw.web.feature.group
  4. com.sap.banking.omnichannel.businesscentral.web.feature.group
  5. com.sap.banking.omnichannel.onlinebanking.web.feature.group

1 Enable com.sap.banking.omnichannel.provisioning.feature.group

2 Enable com.sap.banking.omnichannel.platform.feature.group

SMP3 server will restart. You can see this on the console.

New bundles and new features are being started.

SMP3 server must start successfully. If not, you have a problem.

Result

3 Enable com.sap.banking.omnichannel.bpw.web.feature.group

4 Enable com.sap.banking.omnichannel.businesscentral.web.feature.group

5 Enable com.sap.banking.omnichannel.onlinebanking.web.feature.group

Start scheduler bundle

cd /SAP/MobilePlatform3/Server/tools/cmdclient/
./ljsc.sh ss banking-core-scheduleruntime

Install SAP OCB Retail – 2 – Start installation

Download

Download the installation file from SAP Market place and copy it on the SMP3 server.

tar zxvf ONLRETBANK83001P_1-81000501.TGZ
cd ebf25660/
unzip RetailBanking_8.3_SP01_PL01_LINUX64.zip

This will give you the installation files in the folder.

Start installation

The installer is the folder SAPOnlineRetailBanking8.3.1.1.

cd SAPOnlineRetailBanking8.3.1.1/
sh ./install.sh

Press enter to start the wizard. You’ll have to inform several paramters, like SMP3, Database, etc.

SMP3 configuration

Oracle Database configuration

Inform the path on your system where Oracle is installed. The path contains the DB tools. For Oracle XE, the path is: /u01/app/oracle/product/11.2.0/xe/

Load sample data into database

Installation starts

Database is being created

After a while, the installer should finish

Validation

The folder com.sap.banking.omnichannel.repository must have been created as a p2 repository. Check for it via

ls /SAP/MobilePlatform3/Server/p2/com.sap.banking.omnichannel.repository/

Install SAP OCB Retail – 1 – SMP3 configuration

To be able to install SAP Omnichannel retail banking on SMP3 SP8, some adjustments must be done on the SMP3 server configuration.

Avoid memory leak

Add a new parameter in the props.ini file of SMP3 server.

vim /SAP/MobilePlatform3/Server/props.ini

Parameter to add: -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true

DTD validation

Looking at the installation guide from SAP, this configuration is somewhat against SAP’s own security recommendations, but is needed as OCB uses struts, and for those the validation must be done via DTD and not by XSD. Edit the file fixed-sys.properties located at /SAP/MobilePlatform3/Server/configuration/com.sap.mobile.server.launcher.

vim /SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.launcher/fixed-sys.properties

Comment out the last two properties.

Weak Diffie-Hellman ciphers

New browser don’t like anymore the SMP3 SP8 standard TLS ciphers, therefore these must be changed to be more aligned with latest security expectations.

vim /SAP/MobilePlatform3/Server/config_master/org.eclipse.gemini.web.tomcat/default-server.xml

For each TLS connector, substitute the ciphers by TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA.

JAVA_HOME

Set JAVA_HOME variable to the one used by SMP3.

export JAVA_HOME=/SAP/MobilePlatform3/sapjvm_7/

Install SMP3 with Oracle DB

The following procedure for installing SMP3 with an Oracle DB is for Linux. For tests, you can use Oracle Express. Check your environment/company if you can use that version.

Prerequisites

Ensure that Oracle XE is up and running. It is important that the tnslistener is working! Run the listener and check the status:

/u01/app/oracle/product/11.2.0/xe/bin/lsnrctl status

Configure installation parameters

The steps are documented at SAP Help. You’ll have to edit the SilentInstall_Linux.txt file and adjust the installation parameters.

vim SilentInstall_Linux.txt

For Oracle, you’ll need to change these parameters (at the end, you’ll find a complete example file):

Activate that SMP3 uses an external DB

-V developerInstall="false"
-V productionInstall="true"
-V sqlaEmbeddedDB="false"
-V existDB="true"

Inform the Oracle XE connection parameters

-V existDBType="oracle-sid"
-V dbHostName="localhost"
-V dbPortNumber="1521"
-V dbLogin="gomobile"
-V dbPassword="secret"
-V dbDBName="XE"

Inform the JDBC driver location

-V jdbcDriver="/u01/app/oracle/product/11.2.0/xe/jdbc/lib/ojdbc6.jar"

Prepare Oracle DB

Form the above connection parameters you can see that SMP3 is going to use the user gomobile with the password secret to connect itself to Oracle XE. This means that the user with the password and a schema must be created in the DB. SMP3 comes with a SQL script for Oracle that does exactly that. The script is located at /db_tools/db/oracle/smp3/sql. The file is 001_SMP3_drop_and_create_user.DDL The file contains the SQL statements to create the user with the right permissions:

CREATE ROLE SY365_OBJOWNER;
GRANT CREATE SEQUENCE TO SY365_OBJOWNER;
GRANT CREATE SESSION TO SY365_OBJOWNER;
GRANT CREATE SYNONYM to SY365_OBJOWNER;
GRANT CREATE TABLE TO SY365_OBJOWNER;
GRANT CREATE VIEW TO SY365_OBJOWNER;
GRANT CREATE PROCEDURE TO SY365_OBJOWNER;
GRANT CREATE SEQUENCE TO SY365_OBJOWNER;
GRANT CREATE TRIGGER TO SY365_OBJOWNER;
GRANT CREATE INDEXTYPE TO SY365_OBJOWNER;
DROP USER GOMOBILE CASCADE;
CREATE USER GOMOBILE
IDENTIFIED BY secret
DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
-- 2 Roles for GOMOBILE
GRANT SY365_OBJOWNER TO GOMOBILE;
GRANT CREATE SESSION TO GOMOBILE;
GRANT CONNECT TO GOMOBILE;
ALTER USER GOMOBILE DEFAULT ROLE ALL;
-- 1 Tablespace Quota for GOMOBILE
ALTER USER GOMOBILE QUOTA UNLIMITED ON USERS;

You’ll have to add the command EXIT; at the end of the file

To run the SQL script, run:

sqlplus system/Sap123 @001_SMP3_drop_and_create_user.DDL > smp3.log
  • Note: Sap123 is the password for the user system.

Output is written to smp3.log

SQL*Plus: Release 11.2.0.2.0 Production on Wed Aug 24 21:37:08 2016
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production
Role created.
Grant succeeded.
[…]
DROP USER GOMOBILE CASCADE
ERROR at line 1:
ORA-01918: user 'GOMOBILE' does not exist
User created.
Grant succeeded.
[…]
User altered.
User altered.

The error regarding DROP user is normal, as the user gomobile hasn’t been created before, so there is no user to drop.

Run installer

With the above steps done, SMP3 installer is ready to be run.

./SilentInstall_Linux.sh

The output will contain information regarding the Oracle DB:

dbg, existDBType:oracle-sid
WARNING: Selecting this option confirms SMP database is already created
dbg, jdbcDriver: /u01/app/oracle/product/11.2.0/xe/jdbc/lib/ojdbc6.jar
dbg, jdbcDriver fullFileName: /u01/app/oracle/product/11.2.0/xe/jdbc/lib/ojdbc6.jar
dbg, jdbcDriverFile: /sap/SAP/MobilePlatform3/Util/ojdbc6.jar
dbg, ojdbc6.jar will be renamed to ojdbc.jar in the installation
dbg, queryExit:oracle-sid localhost gomobile [pwd entered] 1521 XE
dbg, Ping succcesful: 0
dbg, smpDataExists:false
dbg, New node install

If everything works fine, you’ll get a confirmation message at the end of the installation.

Installation Successful

Validation

SAP Help contains some information on how to validate the installation. You can search for error message in the installation log, but when an error occurs, normally the installer stops. My preferred way to check SMP3 is to start the server and see if I can log on, create apps, etc. Base test is therefore to start SMP3 and to log on.

Afaria – Test NDES certificate template

Easiest way to test SCEP with Afaria is to make use of the delivered ServerSCEPtest application. This application comes with Afaria`s PackageServer component. It can be found in the bin directory of the package server.

The test application is a Windows executable that executes the SCEP process through Afaria. You have two options available for the test:

  1. Provisioning Server
  2. Package Server

I am going to execute the SCEP/NDES test using the package server. This is the Afaria component used by all clients to receive a client certificate for apps.

To run the test, at least the common name value must be filled in. This is the CN= part of the certificate. Normally, this is your user id. Unfortunately, the test tool is limited to 2048 bit key (Afaria SP8) and does not select you higher or custom values. To run the test, just select perform test button. The additional CSR informations like city, org, etc are taken from the package server configuration. These values are given by the Afaria admin.

The status of the SCEP process is shown in the log area. You can see that the CSR is created and send to the package server CA. After the test ran without errors, the returned certificate is saved to: C:\ProgramData\SAP\Afaria.

The see and validate the value of the new certificate, you can use the Crypto Shell Extensions of Windows Server.

The certificate was issued by the CA: CA. Lifetime is one year. And the template is AfariaUser. This matches exactly how the NDES template was configured.

To be 100% sure, the CA can be consulted. Normally, all issued certificates are stored there and can be consulted. Taking a look into the issued certificate list, I can see that a new certificate by the NDES user was issued using as a template AfariaUser. Therefore, the new NDES configuration is validated and working.

Afaria – Define certificate template for SCEP on Windows CA

When you work with Afaria, you`ll sooner (iOS) or later (Android, WP) come in contact with certificates. To be more specific, with device (iOS) and user (all platforms) certificates. To make it as easy as possible to get those certificates available to the devices and users, an MDM solution makes use of SCEP. SCPE in the Microsoft world is called NDES, and is available with their CA. If you install everything following the official documentation, you`ll end up having

  1. A working environment (yeah)
  2. Most probably a certificate issue, as your users and devices get a certificate named IPSec (Offline request).

This default certificate is what Microsoft thinks fulfills most use cases of SCEP (sorry, NDES) and basically they are right. A device or user can use this certificate without problems for most of the scenarios. Most importantly, users can use it to authenticate themselves against services. It may be that

  • your security area does not like the name
  • the lifetime does not meet the requirement: its 2 years as given by Microsoft
  • it is missing some functionality
  • wrong algorithm or key length
  • or something else

All of the above points are valid and can invalidate the use of the default configuration. Which leaves you to the question: how to solve this?

To make Afaria get back from the CA a valid certificate based on a custom template, it only takes two steps:

  1. Create a template
  2. Assign template to NDES (SCEP)

With SCEP, Afaria is only consuming a service offered by CA. How the CA is treating the request, depends 100% on the CA. Therefore, no additional configuration is needed on the consuming service: Afaria. As a result of this, three steps are necessary to make Afaria get back a custom certificate:

  1. Create a certificate template
  2. Assign template to NDES (SCEP)
  3. Test

SAP Mobile Platform 3 Software Development Kit version management

Scenario

SAP releases a software development kit (SDK) for its SAP Mobile Platform 3 (SMP3) to enable developers to efficiently create apps. The SDK is not a static product but is actively developed and supported by SAP. This means that a SDK receives constant updates and patches.

Problem

The above screenshot shows that only for SDK SP10 7 patch levels were released, in a little more than 1 month. The installation of a SDK is always done in the same location. Therefore, only one SDK version can be used at a time be a developer. While this assures that only the latest version is going to be used, it creates a problem in regards to maintainability and ongoing development. A new development project may use SP10, while a current one may still depend on SP9. To overcome this, a developer may create local copies of the SDK and manually switch between the different versions, an approach is going to be presented in this document that allows the developer to have different versions of the SDK available.

Solution

The approach consists of using git to manage the individual versions of the SDK. Of course, a different revision control system may be used, but git offers normally a superior handling and speed. The overall process is as followed:

  1. Create an initial version of the SDK.
  2. Add this version to git and tag it correspondently
  3. Install a newer version of the SDK to the same location
  4. Use git to add this version and tag it correspondently
  5. The work with a specific SDK version, the developer checks out the needed version
  6. If necessary, remove/add the Kapsel plugins / libraries to a project
  7. Repeat step 2 to 4 for future versions

Process

Download initial version of the SDK from SAP Market Place: https://support.sap.com/swdc

Path: Sybase products -> SAP Mobile Platform SDK -> SAP MOBILE PLATFORM SDK 3.0 -> Support Packages -> SAP MOBILE PLATFORM SDK 3.0 -> [OS]

Install the initial version of the SDK

Go the the installation folder. Either opt to version the whole installation folder or just a part of the SDK, like Kapsel. The following example will only version Kapsel.

Note: by default, Fiori Mobile Client apps are stored inside the Kapsel SDK folder. As each FMC app adds a few thousands files, it is a good idea to not have these included into the git versioning. Consider using .gitignore for those folders.

Initial commit and tag

  • Initialize the folder: git init


  • Add all content: git add –A –v


  • Commit files: git commit



  • Tag commit: git tag –a SPnPLm –m “SDK SPnPLm”

Updating the SDK

Download a newer version of the SDK and install it. Ensure that KapseSDK is going to be upgrade (which should be the default).

Go the installation folder to add the new files to git.

Note: it is important to know that with git a folder .git is created which stores all the git relevant information. In case this folder is deleted, so will also the files and versions added to git. Normally the SDK installer is only overwriting and adding files and not removing. The .git folder should therefore not be impacted by the SDK installation / upgrade process.

Subsequent commit and tag

  • Add all content: git add –A –v
  • Commit files: git commit
  • Tag commit: git tag –a SPn+1PLm+1 –m “SDK SPn+1PLm+1

Add files

Files that were part of the previous SDK version but not of the current one will be shown as remove.

Commit

Tag version

See available SDK versions

Use a specific version of the SDK

To use a specific version of the SDK, it must first be stored in git and tagged. To use the version, a simple checkout is sufficient to update the whole KapselSDK folder to the specified version. To make use of this version, the Kapsel plugins must be updated in an already used project. For a new project, the usual process of adding a plugin is to be used.

  • List available versions: git tag
  • Checkout version: git checkout

To complete the installation, install the Kapsel dependencies as described in README.md.

Use a specific Cordova version for hybrid app development

Scenario

Cordova is used as the de-facto standard software for creating hybrid mobile apps. To keep up with mobile platforms, a new version of Cordova is released constantly. This creates a certain challenge for mobile app developers that have to not only create new apps, but also have to maintain older versions. Specifically in enterprise environments, it is not always possible to simply update to a new Cordova version. One reason can be an upcoming go-live. You do not want to change your SDK days before a go-live as this increases drastically your testing efforts. For instance, SAP releases a software development kit (SDK) for its SAP Mobile Platform 3 (SMP3) to enable developers to efficiently create apps. The SDK is not a static product but is actively developed and supported by SAP. This means that a SDK receives constant updates and patches. Each SDK SP version comes with a minimum and recommended Cordova version. A developer that has to create new apps and at the same time maintain older versions may come into the situation where it is necessary to have not only different version of a SDK SP installed, but also of the Cordova tool. Given a normal workload, the developer may have to change between the new project and the maintenance several time per day.

Problem

The above scenario creates the following problem for the developer: by default, Cordova is installed via npm globally. With this, only one version of Cordova is available at a given time. For the developer this means that he cannot simply have several versions for each SDK SP and project available. A manual remove of the current version of Cordova and install of the needed version is necessary. As the npm install is globally done, one version of Cordova is activated for all users of the computer.

Solution

The root cause of the problem is how Cordova is installed. Cordova is delivered and maintained via npm. The default way of installing Cordova is to issue the command:

npm –g install cordova[@{version}]

Install locally

npm offers alternatives to the above shown installation option. Without the –g flag, a npm module will be installed into the nodes_module folder of the current path. To install Cordova locally to the project folder, the command is:

npm install cordova[@{version}]

With this, Cordova executable is available at node_modules/cordova/bin/cordova

A cordova –v run against the newly installed version shows that the right version is installed.

To create a Cordova project with that version, this newly installed version must be used and not the globally available version. The command line parameters are not affected by this.

node_modules/cordova/bin/cordova create hello com.sap.hello HelloWorld

To add Cordova platforms or plugins, the Cordova version inside the local nodes_modules folder must be invoked.

node_modules/cordova/bin/cordova platform add android

node_modules/cordova/bin/cordova plugins add cordova-plugin-console

The same rule applies for compilation, build or run of a Cordova app.

node_modules/cordova/bin/cordova compile

Install locally (advanced)

Installing Cordova locally as shown above still means that the Cordova package must be installed before a Cordova/Kapsel project is created. To have several version of Cordova available in that way, several folders must be created, preferably containing a version tag of the installed Cordova. This implies that inside the actual hybrid project, no reference to the needed Cordova version is maintained, despite the SDK SP dependency.

To have the Cordova version tight into the project, any Cordova version can be used to create the project folder structure. Inside the folder the needed Cordova version can be installed locally. That way, the Cordova version is made available inside the project, making it easier to share the project or to onboard new team members. On the contrary, instead of having one single repository for each Cordova version, the executable must be provided for each project.

NPM link

NPM comes with a link tool. This tool links a package globally. This makes a local package globally available. The local package will appear as it was installed using npm install –g <package>. The link tool is handy when the npm package is available via its source code (like GitHub) and is therefore not needed to be installed from the npm repository.

In combination with Cordova, npm link allows to make a checked out version of Cordova globally available. A local available versoin of Cordova downloaded via git can be checked out and activated by npm link. To activate a specific version, this version is checked out via git and then activated by npm link.

The installation procedure is as given by Cordova.

git clone https://git-wip-us.apache.org/repos/asf/cordova-cli.git
cd cordova-cli
npm install
sudo npm link
npm link plugman

To go through each step:

git clone https://git-wip-us.apache.org/repos/asf/cordova-cli.git

npm install

npm link

To check the currently activated version of Cordova: cordova –v


To switch to another version of Crodova, git is to be used. The following example shows how to switch to Cordova 4.0.0 globally. First, get a list of tags from git: git tag

Checkout version 4.0.0.

git checkout 4.0.0

npm install

npm link

The check that version 4.0.0 is now available globally, issue cordova –v from the command line.

To test that Cordova 4.0.0 is now being used, create a new project: cordova create TestSAP com.sap.hello TestSAP

Add android as a platform: cordova platforms add android

Please note that android platform version 3.6.4 is used, and not 4.1.1 as it was with Cordova 5.4.1

Installing SMP3 SP9 in CentOS

Installing SMP3 came with an OS pre-requisite check in previous versions. This means that you could not simply install SMP3 in a not-supported OS. The installer refused to continue the installation. Makes sense when installing it in a landscape, less sense when you want to install it on your laptop / VM to try thinks out. Good news that (at least) with SP9 the installer lets you setup SMP3 even in a not supported OS.

Start installation: ./SilentInstall.sh

You will get informed by the installer that you are doing it wrong, aka using a not supported platform, but compared to previous SPs, the installer executes. I recommend to make use of the silent installation, and put all parameters into the txt file. In that case, it’s just running the silent installer instead of the setupLinux binary.

Output

[root@smp3 ebf25288]# ./SilentInstall_Linux.sh

Initializing Wizard……..

Launching InstallShield Wizard……..

setupLinux.bin: line 1952: warning: here-document at line 1952 delimited by end-of-file (wanted `/dev/null’)

ERROR: Your operating system is not officially supported by SAP Mobile Platform 3.0 SP09. See the SAP Product Availability Matrix (PAM) for information on supported platforms.

Welcome to the SAP® Mobile Platform 3.0 SP09 installer. SAP Mobile Platform 3.0 SP09 will be installed on your computer.

SAP Mobile Platform Server 3.0 SP09

SAP SE

http://www.sap.com

ERROR: Your operating system is not officially supported by SAP Mobile Platform 3.0 SP09. See the SAP Product Availability Matrix (PAM) for information on supported platforms.

(Nov 12, 2015 10:03:54 AM), , com.installshield.smpserver.event.dialog.silent.PanelProductEditionOptionSilentImpl, dbg, productInstallOption: Developer Installation

(Nov 12, 2015 10:03:54 AM), , com.installshield.smpserver.event.dialog.silent.PanelProductEditionOptionSilentImpl, err, ERROR: Your operating system is not officially supported by SAP Mobile Platform 3.0 SP09. See the SAP Product Availability Matrix (PAM) for information on supported platforms.

(Nov 12, 2015 10:03:55 AM), , com.sybase.englwd.wizardbean.GetHostNameIP, dbg, GetHostNameIP:execute method

(Nov 12, 2015 10:03:55 AM), , com.sybase.englwd.wizardbean.GetHostNameIP, dbg, GetHostNameIP:The hostname is [smp3.tobias.de] and the IP is [192.168.15.133]

(Nov 12, 2015 10:03:55 AM), , com.sybase.englwd.wizardbean.GetHostNameIP, dbg, GetHostNameIP:getCanonicalHostName does not start with getHostName()

(Nov 12, 2015 10:03:55 AM), , com.sybase.englwd.wizardbean.GetHostNameIP, dbg, GetHostNameIP:Setting domain name to getHostName()

(Nov 12, 2015 10:03:55 AM), , com.sybase.englwd.wizardbean.GetHostNameIP, dbg, GetHostNameIP:The domain name is [smp3.tobias.de]

(Nov 12, 2015 10:03:55 AM), , com.sybase.englwd.wizardbean.GetHostNameIP, dbg, GetHostNameIP:The fully qualified domain name is [smp3.tobias.de]

(Nov 12, 2015 10:03:55 AM), , com.installshield.smpserver.event.dialog.silent.PanelAdminCredentialsSilentImpl, dbg, adminUsername: smpAdmin

(Nov 12, 2015 10:03:57 AM), , com.ibm.wizard.platform.linux.LinuxJVMServiceImpl, dbg.jvm, calculating size from directory /sap/ebf25288/sapjvm_7_jre/

(Nov 12, 2015 10:03:57 AM), , com.installshield.product.actions.AddRequiredBytes, dbg, Adding 364431509 bytes to /sap/MobilePlatform3/sapjvm_8

(Nov 12, 2015 10:03:57 AM), , com.installshield.product.actions.AddRequiredBytes, dbg, Adding 1100718777 bytes to /sap/MobilePlatform3

(Nov 12, 2015 10:03:57 AM), , com.installshield.product.actions.AddRequiredBytes, dbg, Adding 0 bytes to /sap/MobilePlatform3/Server

(Nov 12, 2015 10:03:57 AM), , com.installshield.product.actions.AddRequiredBytes, dbg, Adding 0 bytes to /sap/MobilePlatform3

(Nov 12, 2015 10:03:58 AM), , com.sap.install.smp.wizardaction.ExtractZipFile, dbg, ExtractZipFile: execute()

(Nov 12, 2015 10:04:05 AM), , com.sap.install.smp.wizardaction.ExtractZipFile, dbg, /sap/ebf25288/modules/common/SAPJDK-81.8.8-linux.zip is extracted to /sap/MobilePlatform3

(Nov 12, 2015 10:04:06 AM), , com.sap.install.smp.wizardaction.ExtractZipFile, dbg, ExtractZipFile: execute()

(Nov 12, 2015 10:04:44 AM), , com.sap.install.smp.wizardaction.ExtractZipFile, dbg, /sap/ebf25288/modules/server/com.sap.mobile.platform.server.build.dist.onpremise-linux.gtk.amd64.zip is extracted to /sap/MobilePlatform3/Server

(Nov 12, 2015 10:04:44 AM), , com.sybase.englwd.wizardbean.FilesActionWizard, dbg, Deleting File: /sap/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.security/csikeystore.jceks

(Nov 12, 2015 10:04:44 AM), , com.sybase.englwd.wizardbean.FilesActionWizard, dbg, Deleting File: /sap/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.security/csibootstrap.properties

(Nov 12, 2015 10:04:44 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, genCSIBootStrap: command: /sap/MobilePlatform3/Util/genCSIBootStrap.sh

(Nov 12, 2015 10:04:44 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, genCSIBootStrap: arguments: developer /sap/MobilePlatform3

(Nov 12, 2015 10:04:49 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, return value: 0

(Nov 12, 2015 10:04:51 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, encryptAdminPwd: command: /sap/MobilePlatform3/Util/encryptAdminPwd.sh

(Nov 12, 2015 10:04:51 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, encryptAdminPwd: arguments: [admin password] [CSI keyStore password] [CSI keyStoreAlias password] /sap/MobilePlatform3

(Nov 12, 2015 10:04:56 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, return value: 0

(Nov 12, 2015 10:04:58 AM), , com.sybase.englwd.wizardbean.FilesActionWizard, dbg, Copying File: /sap/ebf25288/modules/server/masterKeyRandom.sh to /sap/MobilePlatform3/Util/masterKeyRandom.sh

(Nov 12, 2015 10:04:59 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, masterKeyRandom: command: /sap/MobilePlatform3/Util/masterKeyRandom.sh

(Nov 12, 2015 10:04:59 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, masterKeyRandom: arguments: [masterKey password] ENosSxFLOr ENosSxFLOr /sap/MobilePlatform3

(Nov 12, 2015 10:05:00 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, return value: 0

(Nov 12, 2015 10:05:02 AM), , com.sybase.englwd.wizardbean.FilesActionWizard, dbg, Copying File: /sap/ebf25288/modules/server/keystoreEncryption.sh to /sap/MobilePlatform3/Util/keystoreEncryption.sh

(Nov 12, 2015 10:05:03 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, keystoreEncryption: command: /sap/MobilePlatform3/Util/keystoreEncryption.sh

(Nov 12, 2015 10:05:03 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, keystoreEncryption: arguments: [master key] [password to encrypt]

(Nov 12, 2015 10:05:06 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, return value: 0

(Nov 12, 2015 10:05:08 AM), , com.sybase.englwd.wizardbean.FilesActionWizard, dbg, Copying File: /sap/ebf25288/modules/server/setKeystorePassword.sh to /sap/MobilePlatform3/Util/setKeystorePassword.sh

(Nov 12, 2015 10:05:09 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, setKeystorePassword: command: /sap/MobilePlatform3/Util/setKeystorePassword.sh

(Nov 12, 2015 10:05:09 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, setKeystorePassword: arguments: [keyStore password] /sap/MobilePlatform3 smp3.tobias.de /sap/MobilePlatform3/sapjvm_8

(Nov 12, 2015 10:05:22 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, return value: 0

(Nov 12, 2015 10:05:24 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, dbEncryption: command: /sap/MobilePlatform3/Util/keystoreEncryption.sh

(Nov 12, 2015 10:05:24 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, dbEncryption: arguments: [master key] [password to encrypt]

(Nov 12, 2015 10:05:27 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, return value: 0

(Nov 12, 2015 10:05:27 AM), , com.sap.install.smp.wizardaction.ExecSilentInstall, dbg, reading the line1/sap/MobilePlatform3/InstallLogs/silentInstall/dbEncryption.log

(Nov 12, 2015 10:05:29 AM), , com.sybase.englwd.wizardbean.FilesActionWizard, dbg, Copying File: /sap/ebf25288/modules/server/serverBuildInfo.txt to /sap/MobilePlatform3/Server/config_master/dist.name

(Nov 12, 2015 10:05:29 AM), , com.installshield.product.actions.UninstallerJVMResolution, dbg.jvm, attempting to use the current JVM

(Nov 12, 2015 10:05:29 AM), , com.installshield.product.actions.UninstallerJVMResolution, dbg.jvm, copying the current JVM

(Nov 12, 2015 10:05:29 AM), , com.ibm.wizard.platform.linux.LinuxJVMServiceImpl, dbg.jvm, copying directory /sap/ebf25288/sapjvm_7_jre/ to /sap/MobilePlatform3/_smpjvm

(Nov 12, 2015 10:05:52 AM), , com.ibm.wizard.platform.linux.LinuxJVMServiceImpl, dbg.jvm, JVM_HOME = /sap/MobilePlatform3/_smpjvm

(Nov 12, 2015 10:05:52 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory before installing Add Required Bytes (jdkSize): free=13854736 total=40587264

(Nov 12, 2015 10:05:52 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, msg1, installing Add Required Bytes (jdkSize)

(Nov 12, 2015 10:05:52 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory after installing Add Required Bytes (jdkSize): free=13403696 total=40587264

(Nov 12, 2015 10:05:52 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory before installing Files (bean157): free=13178200 total=40587264

(Nov 12, 2015 10:05:52 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, msg1, installing Files (bean157)

(Nov 12, 2015 10:05:52 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory after installing Files (bean157): free=12614416 total=40587264

(Nov 12, 2015 10:05:52 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory before installing Exec Action (chmodJDK): free=12388832 total=40587264

(Nov 12, 2015 10:05:52 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, msg1, installing Exec Action (chmodJDK)

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory after installing Exec Action (chmodJDK): free=11586480 total=40587264

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory before installing Files (bean1): free=11360928 total=40587264

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, msg1, installing Files (bean1)

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory after installing Files (bean1): free=21373168 total=40587264

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory before installing Add Required Bytes (connSize): free=21055248 total=40587264

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, msg1, installing Add Required Bytes (connSize)

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory after installing Add Required Bytes (connSize): free=20578272 total=40587264

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory before installing Exec Action (chmodServer): free=20419272 total=40587264

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, msg1, installing Exec Action (chmodServer)

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory after installing Exec Action (chmodServer): free=19721992 total=40587264

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory before installing Files (bean106): free=19404048 total=40587264

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, msg1, installing Files (bean106)

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory after installing Files (bean106): free=19086056 total=40587264

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory before installing Add Required Bytes (mobiliserSize): free=18768040 total=40587264

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, msg1, installing Add Required Bytes (mobiliserSize)

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory after installing Add Required Bytes (mobiliserSize): free=18291136 total=40587264

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory before installing Add Required Bytes (agentrySize): free=18132184 total=40587264

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, msg1, installing Add Required Bytes (agentrySize)

(Nov 12, 2015 10:05:53 AM), , com.ibm.wizard.platform.linux.LinuxProductServiceImpl, dbg.install, JVM memory after installing Add Required Bytes (agentrySize): free=17655240 total=40587264

(Nov 12, 2015 10:05:57 AM), , com.sybase.stf.install.uep.wizardaction.InstallStatus, dbg, status: 3

(Nov 12, 2015 10:05:57 AM), , com.sybase.englwd.wizardbean.FilesActionWizard, dbg, Creating directory: /sap/MobilePlatform3/ThirdParty/Legal

(Nov 12, 2015 10:05:57 AM), , com.sybase.englwd.wizardbean.FilesActionWizard, dbg, Copying File: /sap/ebf25288/3rdPartyLicenses/OSSNotices-SAPMobilePlatform3_0.pdf to /sap/MobilePlatform3/ThirdParty/Legal/OSSNotices-SAPMobilePlatform3_0.pdf

(Nov 12, 2015 10:05:57 AM), , com.sybase.englwd.wizardbean.FilesActionWizard, dbg, Copying File: /sap/ebf25288/SilentUninstall_Linux.sh to /sap/MobilePlatform3/SilentUninstall_Linux.sh

(Nov 12, 2015 10:05:58 AM), , com.sybase.englwd.wizardbean.FilesActionWizard, dbg, Copying File: /sap/ebf25288/SilentUninstall_Linux.txt to /sap/MobilePlatform3/Uninstaller/Server/SilentUninstall_Linux.txt

(Nov 12, 2015 10:05:58 AM), , com.sybase.englwd.wizardbean.FilesActionWizard, dbg, Deleting File: /sap/MobilePlatform3/InstallLogs/silentInstall/encryptpwd.log

(Nov 12, 2015 10:05:58 AM), , com.sap.install.smp.wizardaction.InstallProductInfoFile, dbg, New product info file: /sap/ebf25288/smp_product_info.xml

(Nov 12, 2015 10:05:58 AM), , com.sap.install.smp.wizardaction.InstallProductInfoFile, dbg, Copied File: /sap/ebf25288/smp_product_info.xml to /sap/MobilePlatform3/smp_product_info.xml

(Nov 12, 2015 10:05:58 AM), , com.installshield.sybaseuep.event.dialog.silent.PanelLastSilentImpl, dbg, SAP Mobile Platform 3.0 SP09 has been installed successfully.

Installation Successful