Wiki

Scale Your Enterprise

User Tools

Site Tools


versago3:connections

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
versago3:connections [2022/08/30 10:09]
dlee
versago3:connections [2023/08/10 08:43] (current)
dlee
Line 23: Line 23:
 {{ :versago3:connections02.jpg?direct |}} {{ :versago3:connections02.jpg?direct |}}
  
-  - **Server Name** is MSSQL instance name or the HANA server. For HANA connections, the Server Name must include the correct port number.+  - **Server Name** is MSSQL instance name or the HANA server. For HANA connections, the Server Name must include the correct port number (e.i. <hanaserver>:30015).
   - **Database Name** is the name of the database to be used. It is case sensitive for HANA.   - **Database Name** is the name of the database to be used. It is case sensitive for HANA.
   - **Timezone** is used by Data Views that display calendars to determine the correct adjustment between the user and connection timezones.   - **Timezone** is used by Data Views that display calendars to determine the correct adjustment between the user and connection timezones.
Line 29: Line 29:
  
 <WRAP center round important 80% > <WRAP center round important 80% >
-For HANA connections, ensure that the HANA client is installed and the correct port number is defined under the Server Name especially in a multi-tenant environment. +The credentials used for the connections should have the minimum access necessary for the purpose of the connection. We do not recommend the use of a system admin user such as sa.
-We recommend verifying a HANA connection by installing HANA Studio in the Versago server.+
 </WRAP> </WRAP>
 +
 +===== HANA Connection ======
 +
 +===Single Tenant===
 +The standard communications port for a **single tenant** HANA database is **30015**.  This is defined during the HANA database setup. The server name field should be set up as <hanaserver>:30015
 +
 +===Multi-Tenant===
 +In the case where the target database is located in a multi-tenant environment, the actual port to be used must be determined manually.
 +
 +To determine the appropriate port, open a SQL Console on HANA Studio for the **Tenant Database** and run the following query.
 +
 +<code sql>
 +SELECT
 +SERVICE_NAME, PORT, SQL_PORT
 +FROM SYS.M_SERVICES
 +WHERE ((SERVICE_NAME='indexserver' AND COORDINATOR_TYPE='MASTER') or (SERVICE_NAME='xsengine'))
 +</code>
 +
 +The "SQL_Port" value returned by the query should be used as the port in the Server Name.  In the following image, the tenant is DEVTenant.  The query returns port 30047. The connection in Versago is created using this port, rather than the single tenant port 30015 (e.i. <hanaserver>:30047).
 +
 +{{:versago:multitenant_hana_port_determination.png?800|MultiTentant Determination}}
 +
 +===== VGO Configuration DB Credentials ======
 +
 +<WRAP center round important 80% >
 +The connection credentials to the Versago configuration DB (vgoCommon) can be update by editing the file **appsettings.Production.json** under the Versago installation path.
 +</WRAP>
 +----
 +
 +**[[versago3:Home|Home]]**
versago3/connections.1661868549.txt.gz · Last modified: 2022/08/30 10:09 by dlee