COBISOFT Documentation

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Service Layer Configuration ======

To ensure that COBI.time runs stable and performs efficiently, the Service Layer must be properly configured. \\
Unfortunately, the default Service Layer configuration delivered by SAP is insufficient and may cause performance issues.

===== Configuration =====

The configuration must be changed directly on the HANA server with root privileges. \\
First, stop the Service Layer using the following command:  
''systemctl stop b1s''

Then navigate to the directory:  
''/usr/sap/SAPBusinessOne/ServiceLayer/conf/'' \\  
Remove all existing Node Member configuration files, except for a single one:  
''httpd-b1s-lb-member-50001.conf''

{{:de:cobi.time:koomandozeile1.png?800|}}

Edit the file ''httpd-b1s-lb.conf'' and remove all additional Balancer Members from the proxy balancer so that only one Node remains in the balancer:

<code>
<Proxy balancer://myCluster>
   BalancerMember http://localhost:50001/b1s route=node1
   ProxySet stickysession=ROUTEID
</Proxy>
</code>

Additionally, check if there are any Rewrite Rules defined under the RewriteEngine section.  
These rules may still point to old nodes. A typical entry may look like this:

<code>
RewriteEngine on
RewriteRule "^/ping/node$" "/b1s/ping/node?ROUTEID=.node1&target=localhost:50001" [PT]
RewriteRule "^/ping/node/1$" "/b1s/ping/node?ROUTEID=.node1&target=localhost:50001" [PT]
RewriteRule "^/ping/node/2$" "/b1s/ping/node?ROUTEID=.node2&target=localhost:50002" [PT]
RewriteRule "^/ping/node/3$" "/b1s/ping/node?ROUTEID=.node3&target=localhost:50003" [PT]
RewriteRule "^/ping/node/4$" "/b1s/ping/node?ROUTEID=.node4&target=localhost:50004" [PT]
RewriteRule "^/ping/node/(.*)$" "/b1s/ping/load-balancer?ROUTEID=.node$1" [PT]
</code>

Replace this entire block with the following configuration:

<code>
RewriteEngine on
RewriteRule "^/ping/node$" "/b1s/ping/node?ROUTEID=.node1&nodecount=1" [PT]
RewriteRule "^/ping/node/$" "/b1s/ping/node?ROUTEID=.node1&nodecount=1" [PT]
RewriteRule "^/ping/node$(.*)$" "/b1s/ping/node?ROUTEID=.node$1&nodecount=1" [PT]
</code>

Next, open the file ''httpd-b1s-lb-member-common.conf'' and adjust the IfModule mpm_prefork_module section as follows:

<code>
<IfModule mpm_prefork_module>
   ServerLimit              10
   StartServers             10
   MaxSpareServers          10
   MinSpareServers          9
   MaxConnectionsPerChild   20
   MaxRequestsWorkers       48
</IfModule>
</code>

You can now restart the Service Layer using:  
''systemctl start b1s''

In the Service Layer Control Center (`https://sap-server-ip:40000/ServiceLayerController`), only one Node Member should now be visible.

Example Service Layer configuration files (Do not copy or import directly to your HANA server):  \\
{{ :de:cobi.time:example_service_layer_config_files.zip |}}

====== Service Layer Konfiguration ======

Damit COBI.time stabil und performant läuft, muss das Service Layer ordentlich konfiguriert sein. \\
Leider ist die standardmäßig ausgelieferte Service Layer Konfiguration von SAP mangelhaft.  

===== Konfiguration =====

Die Konfiguration muss als root direkt auf dem HANA Server geändert werden. \\
Zuerst sollte das Service Layer mit dem Befehl  
''systemctl stop b1s'' gestoppt werden.  

Danach in das Verzeichnis  
''/usr/sap/SAPBusinessOne/ServiceLayer/conf/'' \\
navigieren und sämtliche Node Member Konfiguration entfernen bis auf eine einzelne Node Konfiguration ''httpd-b1s-lb-member-50001.conf'':  

{{:de:cobi.time:koomandozeile1.png?800|}}

Die Datei ''httpd-b1s-lb.conf'' editieren und sämtliche Balancer Member aus dem Proxy balancer entfernen, sodass nur noch eine Node im Proxy balancer angegeben ist:  

<code>
<Proxy balancer://myCluster>
   BalancerMember http://localhost:50001/b1s route=node1
   ProxySet stickysession=ROUTEID
</Proxy>
</code>

Außerdem prüfen, ob es unter der RewriteEngine noch Rewrite Rules eventuell gibt. Die Rewrite Rules könnten auf alte Nodes zeigen. Der Log Eintrag sieht vermutlich so aus:  

<code>
RewriteEngine on
RewriteRule "^/ping/node$" "/b1s/ping/node?ROUTEID=.node1&target=localhost:50001" [PT]
RewriteRule "^/ping/node/1$" "/b1s/ping/node?ROUTEID=.node1&target=localhost:50001" [PT]
RewriteRule "^/ping/node/2$" "/b1s/ping/node?ROUTEID=.node2&target=localhost:50002" [PT]
RewriteRule "^/ping/node/3$" "/b1s/ping/node?ROUTEID=.node3&target=localhost:50003" [PT]
RewriteRule "^/ping/node/4$" "/b1s/ping/node?ROUTEID=.node4&target=localhost:50004" [PT]
RewriteRule "^/ping/node/(.*)$" "/b1s/ping/load-balancer?ROUTEID=.node$1" [PT]
</code>

Diesen Block muss man hiermit ersetzen:  

<code>
RewriteEngine on
RewriteRule "^/ping/node$" "/b1s/ping/node?ROUTEID=.node1&nodecount=1" [PT]
RewriteRule "^/ping/node/$" "/b1s/ping/node?ROUTEID=.node1&nodecount=1" [PT]
RewriteRule "^/ping/node$(.*)$" "/b1s/ping/node?ROUTEID=.node$1&nodecount=1" [PT]
</code>

Danach die Datei ''httpd-b1s-lb-member-common.conf'' öffnen und den Eintrag **IfModule mpm_prefork_module** wie folgt bearbeiten:  

<code>
<IfModule mpm_prefork_module>
   ServerLimit              10
   StartServers             10
   MaxSpareServers          10
   MinSpareServers          9
   MaxConnectionsPerChild   20
   MaxRequestsWorkers       48
</IfModule>
</code>

Nun kann das Service Layer wieder gestartet werden mit dem Befehl:  
''systemctl start b1s''  

Im Service Layer Control Center (`https://sap-server-ip:40000/ServiceLayerController`) sollte nun nur noch ein Node Member sichtbar sein.  

Beispiel Service Layer Dateien (Nicht einfach kopieren und auf den HANA Server importieren):  \\
{{ :de:cobi.time:example_service_layer_config_files.zip |}}