This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
niota-docs:niota_system_config_connection [2025/04/24 12:42] admin |
niota-docs:niota_system_config_connection [2025/07/17 14:11] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== Introduction ===== | + | ==== introduction ===== |
| Before you can use niota to edit data in your databases you have to set up connections to these databases. A connections consists of | Before you can use niota to edit data in your databases you have to set up connections to these databases. A connections consists of | ||
| Line 25: | Line 25: | ||
| Microsoft SQL Server needs a comma between host address and port instead of a colon! | Microsoft SQL Server needs a comma between host address and port instead of a colon! | ||
| + | |||
| + | ** MSSQL named instances ** require the instance name instead of the IP address - in case you need native SQL connection. | ||
| + | <code> | ||
| + | const ET_HOST = [ | ||
| + | ET_METADATA_CONNECTION =>'127.0.0.1:3366', | ||
| + | ET_ZAGREUS_CONNECTION =>'http://127.0.0.1:7323', | ||
| + | "SQLSERVER" =>'C9RRELE02\MSSQL_RITCON_E' | ||
| + | ]; | ||
| + | </code> | ||
| ==== configure logins ===== | ==== configure logins ===== | ||
| Line 59: | Line 68: | ||
| ==== configure connections ===== | ==== configure connections ===== | ||
| - | Before you can use niota to edit data in your databases you have to set up connections to this databases. | + | After you have defined your database hosts and the login you can configure the connecion(s). You have to edit the file ''connections.php'' in your client specific conf-folder. |
| - | You have to edit the connections file manually on the server. | + | |
| + | ** To assure that your login has really access rights to the database where you want to setup the connection we recommend to test the login with a standard client for your database ** | ||
| + | |||
| + | If you use MS SQL Server you can connection via Management Studio, if you use Oracle, you can use SQL Developer, ..... | ||
| - | * logon to the server where N-PAPP is installed | ||
| - | * navigate to ''\app\conf'' - folder | ||
| - | * edit file ''connections.php'' | ||
| One connection out of the array of configured connections must be set as the **metadata database connection**. This connection must be a MySQL connection. | One connection out of the array of configured connections must be set as the **metadata database connection**. This connection must be a MySQL connection. | ||
| - | Other database connections can be set to your local database management systems and may be of this types | + | Other database connections can be set to your local database management systems and may be of these types |
| * MySQL Server | * MySQL Server | ||
| * MS SQL Server | * MS SQL Server | ||
| Line 201: | Line 210: | ||
| * test the connection by loading a grid in niota | * test the connection by loading a grid in niota | ||
| + | * | ||
| - | ^"SQL_Server_ODBC"=> array ( ^"SQL_Server_native"=> array (^ | + | ^"SQL_Server_ODBC"=> array ( ^"SQL_Server_native"=> array ( ^"SQL_Server_native_named_instance"=> array ( ^ |
| - | |''PHPGRID_DB_TYPE => DB_TYPE_ODBC_MSSQL''|''PHPGRID_DB_TYPE => DB_TYPE_MSSQL''| | + | |PHPGRID_DB_TYPE => DB_TYPE_ODBC_MSSQL|PHPGRID_DB_TYPE => DB_TYPE_MSSQL|PHPGRID_DB_TYPE => DB_TYPE_MSSQL| |
| - | |''PHPGRID_DB_HOSTNAME => "odbc_connection_resource_name"''|''PHPGRID_DB_HOSTNAME => “myhostname.com,1433”''| | + | |PHPGRID_DB_HOSTNAME => "odbc_connection_resource_name"|PHPGRID_DB_HOSTNAME => “myhostname.com,1433”|PHPGRID_DB_HOSTNAME => “MYSQL\MYINSTANCE”| |
| - | |''PHPGRID_DB_CHARSET => "iso-8859-2"''|''PHPGRID_DB_CHARSET => "UTF-8"'' or ''PHPGRID_DB_CHARSET => SQLSRV_ENC_CHAR''| | + | |PHPGRID_DB_CHARSET => "iso-8859-2"|PHPGRID_DB_CHARSET => "UTF-8" or PHPGRID_DB_CHARSET => SQLSRV_ENC_CHAR|...| |
| ((Table 1 SQL Server connection definitions (ODBC vs. native).)) Only differences are listed. | ((Table 1 SQL Server connection definitions (ODBC vs. native).)) Only differences are listed. | ||
| Line 243: | Line 253: | ||
| ^"SQL_Server_ODBC"=> array ( ^"SQL_Server_native"=> array (^ | ^"SQL_Server_ODBC"=> array ( ^"SQL_Server_native"=> array (^ | ||
| - | |''PHPGRID_DB_TYPE => DB_TYPE_ODBC_MSSQL''|''PHPGRID_DB_TYPE => DB_TYPE_MSSQL''| | + | |PHPGRID_DB_TYPE => DB_TYPE_ODBC_MSSQL|PHPGRID_DB_TYPE => DB_TYPE_MSSQL| |
| - | |''PHPGRID_DB_HOSTNAME => "odbc_connection_resource_name"''|''PHPGRID_DB_HOSTNAME => "SQL-Server-instance-name”''| | + | |PHPGRID_DB_HOSTNAME => "odbc_connection_resource_name"|PHPGRID_DB_HOSTNAME => "SQL-Server-instance-name”| |
| - | |''PHPGRID_DB_USERNAME => "",''|''PHPGRID_DB_USERNAME => "",''| | + | |...|...| |
| - | |''PHPGRID_DB_PASSWORD => "",''|''PHPGRID_DB_PASSWORD => "",''| | + | |
| ((Table 2 SQL Server connection definitions (ODBC vs. native) with Windows Authentication )) Only differences and user authentication settings are listed. | ((Table 2 SQL Server connection definitions (ODBC vs. native) with Windows Authentication )) Only differences and user authentication settings are listed. | ||