The Copy function allows the creation of a new connection group using the reference group from which we have made the request as a reference model. That is, they will have the same options, databases and permissions (except for the password, which automatically changes and needs to be modified).
This change can only be made using the menu option Database server/Database server.
|Code||Database connection group code|
|Access||If access to the secondary server is allowed, read-only objects (which do not allow transactions) are automatically redirected to the secondary server defined in the main server specification.
The closure of a connection can be synchronous or asynchronous (thread independent)
|Protocol||Indicates allowed access protocols:
|Show secondary||In case the group allows access to the secondary servers, enabling this option, databases of the secondary servers (mirror) will be displayed in the Applications menu to facilitate direct selection by user.
|Minimum number of active connections||If this number is greater than 0, the system will keep in the connection pool, for this user, as many connections as indicated.
When the activity goes down and they expire due to time, the system will close the available connections until reaching this minimum.
|Maximum number of active connections||
Maximum number of simultaneous connections allowed to all users who belong to this group. When the user requires a new connection, if there is no free one, the system will create it, but this maximum will never be exceeded.
|Minimum number of active connections for TX||Si este número es mayor de 0, el sistema mantendrá en el pool de conexiones para este usuario, tantas conexiones como se indique para operaciones transaccionales.
|Maximum number of active connections for TX||Este número indica el número máximo de conexiones permitidas para operaciones transaccionales. 0 indica que las operaciones transaccionales utilizan las mismas conexiones que las no transaccionales.
|Time in seconds that can wait to acquire a connection||When the server has to take a new connection for this group,
if there is no free connection, it will wait for this time indicated in seconds.
In case of exceeding the time without having finished successfully, an exception will be generated.
|Maximum number of rows displayed in query||This number sets a limit to the number of maximum records displayed when making a system query.
If the value 0 is reported, we are indicating that for this connection group there is no limit in this regard.
It is advisable to set a limit based on the volume of information required for each group or category of users. This parameter can be adjusted to the extent necessary.
The fact of establishing a limit in this regard, avoids overloads of queries to the system, especially when they are unnecessary or have been made by mistake.
This limit will also be used during printing of unformatted lists using Ascii production.
|Maximum number of rows displayed in an auxiliary query.||Maximum number of rows returned in an auxiliary query (Helpers, Soft-Reference, Pick-List).
|Maximum number of rows displayed by a channel (portal)||Maximum number of rows displayed by a channel in the Desktop portal.
|Maximum number of rows printed in lists (FOP)||
It sets a limit to the maximum number of records returned in the issuance of formless documents using XSL Formatting Objects transformers. If a negative value (-1) is reported, we are indicating that for this connection group there is no limit in this regard.
List without form
These documents are lists of record by record, balance sheet reports, etc. In definitive, they are all the reports that do not require specific submission form.
XSL Formatting Objects (FO)
Using the FO language, the application server will perform the relevant transformations for each type of producer.
Some of the most usual producers that can be used to issue documents without form are:
It is very important to set a reasonable limit to the number of records that can be processed in a single request, so we avoid overloading application server. This parameter can be adjusted to the extent necessary.If the number of rows to be printed exceeds this limit a warning will be issued.
For the issuance of larger lists, users must use production printers Ascii - PCL . This type of production will only be limited by the value reported in Max read (group_maxqrows) field because they do not require transformation of type FO .
|Maximum number of documents printed in PDF||
It sets a limit to the maximum number of registers returned in form-based issues, using transformers XSL Formatting Objects .
Documents with form
Most of the
Each selected record will usually generate a printing form of one or more pages.
Forms can be used, however, for the issuance of simple relationship listings. In that case, the limit of emission volume control that would be applied would be the one reported in FO Print Listed (usr_maxfrows) .
XSL Formatting Objects (FO)
Using the language FO the application server will perform the relevant transformations for each type of producer.
The types of producers that can be used for the issuance of pages of documents with form are:
It is very important to establish a reasonable limit to the number of records that can be processed in a single request, so we avoid overloading the application server. This parameter can be adjusted to the extent necessary.
|Maximum number of ResultSets in cache||Maximum number of ResultSets stored in cache
|Maximum number of rows cached per ResultSet||Maximum number of rows cached per ResultSet
|Store cached ResultSets on disk||Stores cached ResultSets on disk instead of, by default, on memory.
|Time (seconds) of life of an object in memory||Expiration time (seconds). (DEPRECATED)
|Maximum number of cursors stored in cache||Maximum number of cursors (main SQL Objects) stored in cache
|Cursor persistence (sec)||Maximum time in seconds for a cursor to remain in cache memory
|Maximum number of alive objects in memory||Max number of dictionary lisits. (DEPRECATED)
|Life time (seconds) of an object in memory||Expiry time of a list (seconds)
|Maximum query time in seconds before cancel||Maximum number of seconds that a statement can be run before being canceled
|Time (seconds) of delay pre-closure socket||Permite especificar un tiempo de protección para la cancelación de un socket de lectura. Si se indica 0 no hay límite de tiempo.
Este valor permite proteger el sistema contra fallos esporádicos en las comunicaciones entre el servidor de aplicaciones y el
agente de base de datos, debidos al layer de más bajo nivel (adaptadores de red, sistema operativo, etc). Si el valor es
positivo, indica el número de segundos tras los cuales, el socket se dará por cerrado. Nunca ponga este valor inferior al valor
de tiempo de cancelación de una consulta dado que esto provocará un ruptura del "hilo" en el tiempo especificado. Un valor
recomendable para el caso en que fuera necesario sería el valor del intervalo de cancelación de consultas (usr_qtimeout) + 30.
|Maximum time in seconds to pass query to background||If the execution time of an object exceeds that indicated in this field, it would be run in the background.
This implies that its result will no longer be displayed on the screen, but that a control record will be created in JREP Jobs
of the task monitor.
A zero value in this field will prevent execution control from transferring to the background.
|Minimum time (seconds) to execute a query to be reported||Tiempo (segundos) de espera de una consulta para ser reportada en la salida estándar o en el fichero catalina.out|
|Maximum idle time in seconds before closing connection||For performance purposes, idle connections exceeding this limit will be automatically closed
|Maximum number of check-outs before closing connection||For performance purposes connections are automatically closed after a predefined number of utilizations.
If required new connections will be opened automatically.
Minimum value is 100.
|Maximum number of historic data records||Maximum number of SQL sentences during the connection lifetime (FIFO)|
|Test on borrow connection||Indicates if it performs a test on each reused connection
|Number of rows in init fetch||Number of rows load in the buffer in init fetch. (DEPRECATED)
|Rows in buffer||
Size of the "buffer" where the query logs are loaded.
The intermediate storage files facilitate the paging of the information generated by the database query cursors.
The size of each file (buffer) will correspond to the product between the number of records specified in this field and the size of the record returned by the query cursor, being this variable depending of its characteristics. In addition, special records of totals for breakout groups and global totals, required in most reports, should also be considered.
Buffer file size
It is very important to ensure that the number of records in the intermediate files (buffer) is a multiple value of the number of display records of our users plus a reduced number of records for prospecting continuity.
The 5 records reserved for consultation continuity prospecting should allow the application server to know a priori the existence of extra information beyond the page that the user is viewing at a given time.
Clob type columns are serialized in intermediate files (chunks). However, blob type columns are not.
Clob type columns are serialized in intermediate files (chunks). However, blob type columns are not.
|Time in seconds to delay before reload row||Minimum time, in seconds, that has to pass from the completion of the query for row reload on transactional objects.
Recommended values are between 30 and 60 seconds. Lower values should be for special cases in which it is considered that lower performance may occur.
|Verify integrity before updating||This indicator, if active, causes the server to check that the record data displayed
and those in the database are the same before modifying this record.
It checks that the data displayed from the client (browser) are the same as in the database, to avoid modifying a record that has been modified by a second user, after the the first one had made the query.
This is useful, for instance, in forms where an operation can be done only once, such as making payment, closings ...
|Counter||It shows in the header of each SQL object, the number of rows of each of table involved in the selection SQL statement
|Queries||This flag establishes if queries made in the system will be saved for this database connection group.
Queries are stored in the wic_user_qrylogs table of the wic_conf configuration database.
If the indicator is enabled, users belonging to this group will be allowed to retrieve queries previously made from the
input screen to the documents. Additionally, the historical display of the last used objects will also be activated.
|Transactions||This indicator establishes, in case of this connection group, transactions (insert, delete, update) that are made in the system will be recorded.
The transaction logs are stored in the table wic_user_trxlogs of the configuration database wic_conf.
|XSQL-Scripts||This field indicates if XSQL-Scripts executions that are made to the system will be recordered for this database connection group.
The XSQL-Scripts execution logs will be recorded in the table wic_user_xsqllogs of the configuration database wic_conf.
|SOAP request||This field indicates if for this database connection group the requests that are made via SOAP will be recorded.
Logs are saved in the table wic_user_soaplogs of the configuration database wic_conf.
|Tables of Database configuration available for SELECTs||Regular expression that determines which are the available tables for SELECT's operations on wic_conf database for this group.
This field allows this group to make SELECTs on the wic_conf database via XSQL-Script programs, using the tag select
with the attribute config='true, as for example:
|Description||Description of the connection group|
|BUT_COPY||Copy||Realiza la copia de un grupo de conexión a base de datos tomando de referencia a otro grupo de conexión.|
|BUT_CHECK_CONNECTIONS||Check connections||Invoca un objeto con xsql embebido y devuelve una tabla virtual con el resultado de los test de conexión.|
List of Databases managed by this group. For each Data Base the group defines:
- Transactional authorizations
- Available SOAP services
- Global security roles
|Group||BD connection group|
|Access from DBStudio||Indicator that allows access from the DBStudio tool to this database.
|Insert||It indicates if the user can insert rows in this Data Base
It doesn't override the global database Insert flag.
|Delete||Enable / disable authorization to delete rows.
It doesn't override the global database Delete flag.
|Update||It indicates if the user can update rows in this Data Base
It doesn't override the global database Update flag.
|Processes||Enable / disable execution of process on this Data Base.
It doesn't override the global database Process flag.
|APP||Access authorization from mobile clients via SOAP
|OBJ||Authorization to execute SQL Objects via SOAP
|XML||It indicates if the Data Base allows execution of XML code
|SQL||Authorization to execute SQL statements via SOAP
|Cataloged SQL||Preferred option to execute SQL statements (more secure)
|Functional||Code of the Role used to define the list of allowed or denied objects / Channels
|Security||Code of the Role used to define semantical security restriction. (through a piece of SQL statement to be injected)
|Transaction||Code of the Role used to define transaction authorizations at Table level.
|Default values||Code of the Role used to define the default values to be used in forms.
|Lock objects||Code of the Role used to define temporarily blocks for objects.
|OLAP||The indicated code must be the same used in OLAP XML Schema|
|API||REST functional role|
|DB user||User for whom the home URL is established (NULL->All)|
|Browser panel||Browser panel|
|Mobile panel||Mobile panel|
|Home URL||Home URL for the database|