Install SAP OCB Retail – 4 – Validation

Let the world know ...Tweet about this on TwitterShare on Google+Share on FacebookEmail this to someoneShare on LinkedIn

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.

Let the world know ...Tweet about this on TwitterShare on Google+Share on FacebookEmail this to someoneShare on LinkedIn

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

Let the world know ...Tweet about this on TwitterShare on Google+Share on FacebookEmail this to someoneShare on LinkedIn

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

Let the world know ...Tweet about this on TwitterShare on Google+Share on FacebookEmail this to someoneShare on LinkedIn

Install SAP OCB Retail – 2 – Start installation

Let the world know ...Tweet about this on TwitterShare on Google+Share on FacebookEmail this to someoneShare on LinkedIn

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/

Let the world know ...Tweet about this on TwitterShare on Google+Share on FacebookEmail this to someoneShare on LinkedIn

Install SAP OCB Retail – 1 – SMP3 configuration

Let the world know ...Tweet about this on TwitterShare on Google+Share on FacebookEmail this to someoneShare on LinkedIn

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/
Let the world know ...Tweet about this on TwitterShare on Google+Share on FacebookEmail this to someoneShare on LinkedIn