Deploy the MariaDB service

complete the following steps to deploy the mariadb service in {{ch}} log in to the {{ch}} under dual control by using your administrator identities select the service you intend to deploy and select \[ deploy ] configure the following service setup settings service name the name of the application leave as default service category the category the service falls under leave as default select \[ next ] configure the following access control settings authorized resources the role you are logged in with has access to the service by default add additional resources optional select \[ next ] configure the authentication settings to determine how users authenticate to access encrypted files the two options are kerberos or local authentication local authentication uses local windows accounts to manage access to encrypted files users are authenticated by using their local windows credentials kerberos authentication uses windows active directory to manage access to encrypted files users are authenticated by using their domain credentials active directory configuration is required for kerberos authentication go to identity & access management , then select the active directory tab to set this up select local or kerberos authentication and select \[ next ] configure the path rules select \[ add path rule ] enter role or group names from active directory for broad access enter active directory or individual usernames to grant access choose basic setup to encrypt a specific directory and file type, or select advanced setup to use wildcards like for subdirectories and for pattern matching select \[ add ] based on the mariadb directory structure on windows, the following components within the main data directory (often referred to as datadir , the location of which can be found through the sql command show variables like 'datadir'; ) relate to database storage database subdirectories mariadb typically creates a subdirectory directly within the datadir for each database, using the actual name of the database for example, if a database was named testdb , its files would typically be located in a path like c \program files\mariadb 11 4\data\testdb\ (assuming datadir is c \program files\mariadb 11 4\data\ ) inside this directory ( datadir\testdb\ ), you can see files representing the tables belonging to that database (such as frm files for table structure, and ibd files for innodb tables' data and indexes when innodb file per table is enabled, or frm , myd , myi files for aria/myisam tables) mysql database directory ( datadir\mysql\ ) this directory is crucial, containing system tables that store metadata, user accounts, privileges, server help information, and more it plays a critical operational role for the mariadb server innodb system tablespace ( ibdata1 , etc ) if you are not using the default setting innodb file per table=on , much of your innodb table data and index information might reside in a shared system tablespace file (commonly ibdata1 ) located directly within the datadir even with innodb file per table=on , some shared metadata is still stored here innodb redo logs ( ib logfile ) usually located directly within the datadir , these files (such as ib logfile0 , ib logfile1 ) are the mariadb write ahead logs for the innodb storage engine they are essential for transaction durability (acid compliance) and crash recovery binary logs ( binlog ) if binary logging is enabled (often used for replication or point in time recovery), these log files (e g , binlog 000001 ) and their corresponding index file ( binlog index ) are also typically stored within the datadir by default, although their location can be configured in my ini other storage engine files depending on the storage engines being used (such as aria, myisam, columnstore), other engine specific control files, temporary files, or log files might reside within the datadir or its subdirectories in summary, on a windows system, the data for individual user databases is primarily located within their respective named subdirectories inside the main datadir (such as c \program files\mariadb 11 4\data\testdb\ ) system wide information resides in the datadir\mysql\ directory, and crucial recovery logs (like innodb redo logs and potentially binary logs) are typically found in the root of the datadir if you're considering encryption strategies, understanding this structure helps you decide whether to encrypt the entire datadir , specific database subdirectories like datadir\testdb\ , or specific critical files like innodb redo logs ( ib logfile ) or shared tablespace files ( ibdata1 ) select \[ deploy ]