Differences

This shows you the differences between two versions of the page.

--- cobi.wms:hana_proxy [2023/08/09 16:26] – tkammer
+++ cobi.wms:hana_proxy [2023/11/21 19:55] (current) – tkammer
@@ Line 14: / Line 14: @@
 <code bash>
-version=1.6.0  # Don't forget to set this variable! It's used in the following commands.
+version=1.7.0  # Don't forget to set this variable! It's used in the following commands.
 cd /root
 wget https://docs.cobisoft.de/wiki/_media/cobi.wms/hanaproxy-$version.tar
@@ Line 49: / Line 49: @@
 <code bash>
-version=1.6.0
+version=1.7.0
 cd /root
 wget https://docs.cobisoft.de/wiki/_media/cobi.wms/hanaproxy-$version.tar
@@ Line 59: / Line 59: @@
 </code>
-===== Troubleshoot =====
+===== Troubleshooting =====
-If you suspect that HANA Proxy may not be working properly even though it is running, you can test a few things.
+If you suspect that HANA Proxy may not be working properly even though it is running, you can test a few things.  Note that some of these instructions are quite technical and require some IT knowledge.
-First of all see if it's reachable from another machine.  Let's say the IP Address of the HANA server is ''192.168.16.30''.  The port used by HANA Proxy is ''30075''.  Using [[https://nmap.org/|Nmap]], we can try:
+==== TCP Port Probing ====
+First of all, test if HANA Proxy is reachable from another machine.  Let's say the IP Address of the HANA server is ''192.168.16.30''.  The port used by HANA Proxy by default is ''30075''.  Using [[https://nmap.org/|Nmap]], we can try:
 <code bash>
@@ Line 69: / Line 71: @@
 </code>
-On MS Windows you could also use ''Test-NetConnection'' aka ''tnc'' instead of Nmap:
+On MS Windows, you could also use ''Test-NetConnection'' aka ''tnc'' instead of Nmap:
 <code powershell>
@@ Line 77: / Line 79: @@
 If the port doesn't seem open, a firewall could be blocking the connection.
-Once you've made sure that the port itself is reachable, you can test if HANA Proxy can execute queries.  This can be done with a ''netcat'' utility.  If you have Nmap installed, you should have the ''ncat'' command which can do this, otherwise if you're on a GNU/Linux distro you should also have a simple ''nc'' tool that is capable enough.
+==== Test Query ====
-First copy the following HANA Proxy command into a text file, let's say ''hptest.json'', with the correct password in place of "secret":
+Once you've made sure that the port itself is reachable, you can test if HANA Proxy can execute queries.  This can be done with a ''netcat''-style program.  If you have Nmap installed, you should have the ''ncat'' command.  Otherwise, if you're on a GNU/Linux distro, you should have an ''nc'' command that is capable enough.
+**Note:** It's important that the ''netcat'' implementation you're using executes a TCP shutdown command after it's done sending data.  The ''nc'' command which is available on SuSE Linux Enterprise Server by default doesn't do this, unless you provide the ''-N'' command-line switch.
+First, copy the following HANA Proxy command into a text file, let's say ''hptest.json'', with the correct password in place of "secret":
 <code json>
@@ Line 91: / Line 97: @@
 </code>
-The host can be "localhost" when the HANA Proxy is running on the same server as the HANA database; otherwise, it will have to be the IP address or hostname of the HANA server.  Port ''30015'' is default for HANA.  The ''SYSTEM'' user should have permissions to query any database.  Note that this example queries ''SBOCOMMON'' for testing purposes, but COBI.wms never actually queries the ''SBOCOMMON'' database.
+The host can be "localhost" when the HANA Proxy is running on the same server as the HANA database; otherwise, it will have to be the IP address or hostname of the HANA server.  Port ''30015'' is default for HANA.  Note that this example queries ''SBOCOMMON'' for testing purposes; COBI.wms never actually queries the ''SBOCOMMON'' database.
-Now you can send the command to HANA Proxy with the following command:
+Now you can send the command to HANA Proxy with the following command, assuming that ''192.168.16.30'' is the IP address of the server on which HANA Proxy is installed:
 <code bash>
-ncat localhost 30075 < hptest.json
+ncat 192.168.16.30 30075 < hptest.json
 </code>
-The example assumes that you're running this command on the same server as HANA Proxy, which is why it uses ''localhost''.  If you're running this command from a different machine, make sure to use the IP address or hostname of the server on which you've installed HANA Proxy.
+Alternatively, if you're running this command directly on the SLES/HANA server, and using the default ''nc'' tool found on it, you can run this command instead:
+<code bash>
+nc -N localhost 30075 < hptest.json
+</code>
-When you execute the command, the results of the query (or at least an error message) should be returned in JSON format.  If you're not receiving any JSON response at all, make sure that HANA Proxy is running, that the IP address or hostname you've used is correct, and that port 30075 is open and not blocked by any firewall.
+When you execute the command, the results of the query (or at least an error message) should be returned in JSON format.