You can translate the question and the replies:

Question about external database

In my project, we are planning to use external cache database and external metadata database. I know how to setting it by using vdp admin tool or web gui, cause it is written on manual. There will be has no problem if the environment is windows or linux. But we are using k8s now and i need to deploy denodo in k8s. As everbody know that we should put all configurations in configmap rather than settting by Web-UI manually everytime. Im searching the location(path) of below configuration file, but didnt found any info in Manual and documents. does anybody could tell me where is the location? * SolutionManager: the config file's location about external metadata database * VDPserver: the config file's location about external metadata database * Datacatalog: the config file's location about external metadata database * VDPserver: the config file's location about external cache database BTW, i will be appriciate if denodo side could add more contents in manuals about k8s. There are several document about how to deploy denodo in k8s. but that is just for test, not enough for production environment. Although maybe most of denodo users are windows or linux user, It would be save lot of time for k8s users if some production level sample manual or document could be find on community site.
user
23-07-2021 04:18:15 -0400

8 Answers

Hi, Please find the response below inline, 1) SolutionManager: the config file’s location about external metadata database - SMConfigurationParameters.properties file located in <DENODO-HOME>\conf\solution-manager 2) VDPserver: the config file’s location about external metadata database - VDBConfiguration.properties.properties file located in <DENODO-HOME>\conf\vdp 3) Data Catalog: the config file’s location about external metadata database - datasource.properties file located in <DENODO-HOME>\conf\data-catalog 4) VDPserver: the config file’s location about external cache database - VDBConfiguration.properties.properties file located in <DENODO-HOME>\conf\vdp The script [“regenerateMetadata”](https://community.denodo.com/docs/html/browse/8.0/en/vdp/administration/server_configuration/storing_catalog_on_external_database/storing_catalog_on_external_database#using-a-script-to-enable-this-feature) located in the directory <DENODO_HOME>/bin can be used to enable an external metadata database. Hope this helps!
Denodo Team
26-07-2021 18:45:34 -0400
Thank you for your reply. 2,3,4 were sloved. but 1 is not yet. i didnt found any configurations about external metadata database were written on SMConfigurationParameters.properties even after i configured external database successfully via web-gui. i attached my SMConfigurationPara meters.properties file, could you tell me which part is it? ``` ############################################################################### # SOLUTION MANAGER SERVER CONFIGURATION # ############################################################################### server.port=10090 # HTTPS #server.ssl.key-store= #server.ssl.key-store-password= #server.ssl.key-store-password.encrypted= #com.denodo.security.ssl.trustStore= #com.denodo.security.ssl.trustStorePassword= #com.denodo.security.ssl.trustStorePassword.encrypted= # Spring configuration spring.hateoas.use-hal-as-default-json-media-type=false spring.data.rest.defaultMediaType=application/json # Timezone com.denodo.solutionmanager.timezone=UTC # Block size in batch inserts com.denodo.solutionmanager.jpaFlushSize=50 com.denodo.solutionmanager.userAgent=Denodo-Solution-Manager # JVM options java.env.DENODO_OPTS_START=-Xmx1024m com.denodo.solutionmanager.rmi.host=localhost com.denodo.solutionmanager.utils.LicenseManager.iconRoute=/opt/denodo/resources/solution-manager/ico com.denodo.vdb.install=/opt/denodo ############################################################################### # CONNECTION PARAMETERS # ############################################################################### # RMI Connection Parameters rmi.queryTimeout=90000 rmi.chunkTimeout=90000 rmi.chunkSize=100 rmi.maxActive=4 rmi.minIdle=0 rmi.maxIdle=-1 rmi.maxWait=30000 rmi.whenExhaustedAction=1 rmi.testOnBorrow=true rmi.testOnReturn=false rmi.testWhileIdle=false rmi.timeBetweenEviction=-1 rmi.numTestsPerEviction=3 rmi.minEvictableIdleTime=1800000 rmi.softMinEvictableIdleTime=-1 rmi.lifo=true # JDBC Connection Parameters jdbc.local.queryTimeout=900000 jdbc.local.chunkTimeout=900000 jdbc.local.maxActive=30 jdbc.remote.queryTimeout=90000 jdbc.remote.chunkTimeout=90000 jdbc.remote.maxActive=4 jdbc.chunkSize=100 jdbc.validationQuery=SELECT 1 jdbc.minIdle=0 jdbc.maxIdle=-1 jdbc.maxWait=30000 jdbc.whenExhaustedAction=1 jdbc.testOnBorrow=true jdbc.testOnReturn=false jdbc.testWhileIdle=false jdbc.timeBetweenEviction=-1 jdbc.numTestsPerEviction=3 jdbc.minEvictableIdleTime=1800000 jdbc.kerberosTokenTimeout=30000 ############################################################################### # VIRTUAL DATA PORT CONFIGURATION # ############################################################################### # VDP Configuration File com.denodo.solutionmanager.vdp.confFile=/opt/denodo/conf/vdp/VDBConfiguration.properties # VDP authentication database com.denodo.solutionmanager.vdp.database=admin com.denodo.solutionmanager.vdp.hostname=localhost ############################################################################### # SCHEDULER CONFIGURATION # ############################################################################### # Waiting time until scheduler finish required actions, in miliseconds com.denodo.solutionmanager.scheduler.waitingTime=10000 com.denodo.solutionmanager.scheduler.maxTryWaiting=10 # Job execution timeout, in seconds com.denodo.solutionmanager.scheduler.jobsExecutionTimeout=21600 ############################################################################### # VERSION CONTROL SYSTEM CONFIGURATION # ############################################################################### # VCS options com.denodo.solutionmanager.vcs.user= com.denodo.solutionmanager.vcs.system= com.denodo.solutionmanager.vcs.url= com.denodo.solutionmanager.vcs.useDefaultBranch=true com.denodo.solutionmanager.vcs.branch=default com.denodo.solutionmanager.vcs.password= com.denodo.solutionmanager.vcs.useUserAndPassword=true com.denodo.solutionmanager.vcs.encryptedPassword=true com.denodo.solutionmanager.vcs.localRepositoriesHome=/opt/denodo/work/solution-manager/repository com.denodo.solutionmanager.vcs.tempSVNRepository=tempSolutionManagerSvnRepo com.denodo.solutionmanager.vcs.maxTryWaiting=5 com.denodo.solutionmanager.vcs.waitingTime=10000 ############################################################################### # DEPLOYMENTS CONFIGURATION # ############################################################################### # Number of retries for vql execution in delete revisions deployments com.denodo.solutionmanager.deployments.deleteRetries=50 # Directory for scripts execution com.denodo.solutionmanagerserver.deployments.workDir=/opt/denodo/work/solution-manager # Timeout in seconds of the script to execute com.denodo.solutionmanager.scripts.timeoutInSeconds=600 ############################################################################### # MONITORING CONFIGURATION # ############################################################################### # Directory for monitoring com.denodo.solutionmanagerserver.monitoring.resourcesDir=/opt/denodo/resources/solution-manager-monitor com.denodo.solutionmanagerserver.monitoring.workDir=/opt/denodo/resources/solution-manager-monitor/work com.denodo.solutionmanagerserver.monitoring.stopRunningMonitorsOnShutdown=false com.denodo.solutionmanagerserver.monitoring.checkRunningMonitorsOnStartup.timeoutInSecs=60 ############################################################################### # CLOUD CONFIGURATION # ############################################################################### # URL of the authentication server com.denodo.solutionmanagerserver.authentication.oauth2.serverAccessTokenGeneratorUrl=https://auth.denodo.com/oauth2.0/accessToken # Base URL to get the available patches list from the Resources Server com.denodo.solutionmanagerserver.resourceServerAvailableUpdatesUrl=https://support.denodo.com/repository/items # Base URL to get the list of the available AMIs provided by Denodo from the Resources Server com.denodo.solutionmanagerserver.cloud.aws.resourceServerAvailableAmisProvidedUrl=https://support.denodo.com/repository/aws/list com.denodo.solutionmanagerserver.cloud.aws.resourceServerShareAmiUrl=https://support.denodo.com/repository/aws/share ############################################################################### # SSO CONFIGURATION # ############################################################################### sso.confFile=/opt/denodo/conf/SSOConfiguration.properties sso.server.confFile=/opt/denodo/conf/denodo-sso/SSOTokenConfiguration.properties ############################################################################### # AWS CONFIGURATION # ############################################################################### com.denodo.solutionmanager.cloud.aws.supportedInstanceTypes=^(t2\\.medium|(t2|m4|m5|m5d|m5a|m5ad|m5n|m5dn|c3|c4|c5|c5d|c5a|c5ad|c5n|r4|r5|r5d|r5a|r5ad|r5n|r5dn)\\.(large|xlarge|2xlarge|4xlarge|8xlarge|9xlarge|10xlarge|12xlarge|16xlarge)|r3\\.(large|xlarge|2xlarge))$ ```
user
01-08-2021 08:01:39 -0400
Hi, In order to have those metadata configuration, you will need to add the below properties to SMConfigurationParameters.properties file located in <DENODO-HOME>\conf\solution-manager, * com.denodo.solutionmanager.storage.GenericStorageManager.connectionURI = <ConnectionURI format of the Database> * com.denodo.solutionmanager.storage.GenericStorageManager.driverClassName = <Driver Class> * com.denodo.solutionmanager.storage.GenericStorageManager.username = <user_name> * com.denodo.solutionmanager.storage.GenericStorageManager.password = <password> * com.denodo.solutionmanager.storage.GenericStorageManager.password.encrypted= <ENCRYPTED|NULL, depending on the password> Hope this helps!
Denodo Team
10-08-2021 18:22:27 -0400
Hi denodo team Thankyou for your reply. I have 2 futher question about solution manager external metadata DB. You know from solution manager web-ui, there has a 「solution manager database」 in the list of Cofiguration menu . After i set external database in 「solution manager database」, i found that the below properties was added in LMConfigurationParameters.properties file. I think the below properties should be write into SMConfigurationParameters.properties automatically at the same time with LMConfigurationParameters.properties. Was there any reason why the external metadadb info only written into LMConfigurationParameters.properties file? Also i found license info will be write into external metadb, but rolemanagement info will be not write into external metadb. so my another question is whether the rolemanagement info wiil be write into external metadb if i add below properties to SMConfigurationParameters.properties file? * com.denodo.solutionmanager.storage.GenericStorageManager.connectionURI = <ConnectionURI format of the Database> * com.denodo.solutionmanager.storage.GenericStorageManager.driverClassName = <Driver Class> * com.denodo.solutionmanager.storage.GenericStorageManager.username = <user_name> * com.denodo.solutionmanager.storage.GenericStorageManager.password = <password> * com.denodo.solutionmanager.storage.GenericStorageManager.password.encrypted= <ENCRYPTED|NULL, depending on the password>
user
11-08-2021 06:34:43 -0400
Hi Denodo team Sorry to disturb you guys again. I have one additional question. > whether the rolemanagement info wiil be write into external metadb if i add below properties to SMConfigurationParameters.properties file? If the above question is yes. And you know these table will be created when you use external metada database. could you tell me which table will store the data of role management?
user
12-08-2021 04:33:08 -0400
sorry i forgot to add the tables list. | Tables_in_solutionmanager | +-------------------------------+ | acl_class | | acl_entry | | acl_object_identity | | acl_sid | | aws_cloud_cluster_dnd | | aws_cloud_environment_dnd | | certificate_dnd | | cloud_cluster_elements | | cluster_dnd | | cluster_operations_summary | | cluster_update | | configuration | | custom_action | | custom_validation | | custom_validation_result | | denodo_product_cluster_update | | deployment | | deployment_execution | | element_custom_action | | env_custom_validation | | environment_dcserver | | environment_dnd | | global_license | | hibernate_sequences | | license | | license_lock | | load_balancing_variable | | load_balancing_variable_value | | monitoring | | monitoring_config_parameter | | param_action | | param_val | | promotion_script | | revision | | revision_deploy | | s3_dnd_product_cluster_update | | sch_element | | sch_property | | script_parameter | | server_dnd | | support_dnd_prd_clustr_update | | usage | | user_config_dnd | | validation | | vdp_element | | vdp_property
user
12-08-2021 09:22:54 -0400
I tried add below parameters in to SMConfigurationParameters.properties file. but solution manager start failed. could you tell me how to store role management data to external metadataDB? ``` com.denodo.solutionmanager.storage.GenericStorageManager.connectionURI = <ConnectionURI format of the Database> com.denodo.solutionmanager.storage.GenericStorageManager.driverClassName = <Driver Class> com.denodo.solutionmanager.storage.GenericStorageManager.username = <user_name> com.denodo.solutionmanager.storage.GenericStorageManager.password = <password> com.denodo.solutionmanager.storage.GenericStorageManager.password.encrypted= <ENCRYPTED|NULL, depending on the password> ```
user
12-08-2021 10:14:33 -0400
Hi, I would like to inform you that in Solution Manager, when you configure an external database for storing metadata, the role/user information is not stored in that external database, but stored in the embedded Derby, which is the current specification and the expected behavior of the Denodo Platform. Hope this helps!
Denodo Team
13-09-2021 18:21:51 -0400
You must sign in to add an answer. If you do not have an account, you can register here