Search results

| -D,--destination-database-id <integer> ...nal database identifier to which the context gets assigned; if missing the database gets auto-detected

# Initialize and configure MySQL database

# Initialize and configure MySQL database

...ipt will get only configured if the Open-Xchange server is running and the database pools initialized when installing the open-xchange-munin-scripts package. T

To import that key into the RPM database, use the following command (as root):

...d. The mailResolver should not provide userid/contextid information for a database that Guard doesn't have access to.

...ul full-text search, hit highlighting, faceted search, dynamic clustering, database integration, rich document (e.g., Word, PDF) handling, and geospatial searc ...can be forgotten about. Often the send to the warehouse system, update in database and acknowledgement will be completed in a single transaction to ensure ACI

...here is nothing to change in the configuration of the backend servers, the database, mail, or such. It is only required to adjust the apache web server configu

database. Other examples are included in the development documentation.

...retrieved from its configuration file during startup of the service, to a database to be discovered by Middleware nodes. ...e configured database prior to starting up the DCS for the first time. The database connection properties to be used by the DCS need to be set at the configura

...or, for example OX nodes or Galera nodes, are called ''server nodes'' or ''database nodes''. ...it lacks the functionality to health-check the loadbalancing targets (i.e. database servers) and adjust the loadbalancer tables accordingly. To do this, a sepa

* To use the database service on the existing Open-Xchange installation for Guard, no replication ...any installations, domains may extend across multiple context and multiple database shards. In these cases, the default MailResolver won't work. In addition,

* To use the database service on the existing Open-Xchange installation for Guard, no replication ...any installations, domains may extend across multiple context and multiple database shards. In these cases, the default MailResolver won't work. In addition, i

* To use the database service on the existing Open-Xchange installation for Guard, no replication ...any installations, domains may extend across multiple context and multiple database shards. In these cases, the default MailResolver won't work. In addition, i

* The only supported "Database as a service" solution is AWS RDS for MariaDB as defined by belows compatib ...rs between '''App Suite 7.8.4 and 7.10.x''' and also between the different database systems in terms of SQL modes. See [[My.cnf]] for details.

...here is nothing to change in the configuration of the backend servers, the database, mail, or such. It is only required to adjust the apache web server configu

...es, USM works as an client to the Open-Xchange HTTP API. It also uses some database tables which are accessed through the Open-Xchange SQL interface to store m On the first login after the restart, all required database tables will be created. -->

...here is nothing to change in the configuration of the backend servers, the database, mail, or such. It is only required to adjust the apache web server configu

...readerengine open-xchange open-xchange-grizzly open-xchange-authentication-database The package open-xchange-authentication-database is just needed to fulfill the dependencies.

...o delete contexts and all data stored that belong to it. This includes all database entries and files in the infostore but no Returns the name of the database schema in which a specified context is located.