{"id":11628,"date":"2018-09-01T08:00:22","date_gmt":"2018-09-01T06:00:22","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/"},"modified":"2018-09-01T08:00:22","modified_gmt":"2018-09-01T06:00:22","slug":"documentum-silent-install-remote-docbasesrepositories-ha","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/","title":{"rendered":"Documentum &#8211; Silent Install &#8211; Remote Docbases\/Repositories (HA)"},"content":{"rendered":"<p>In previous blogs, we installed in silent the <a title=\"Documentum \u2013 Silent Install \u2013 Things to know, binaries &amp; JMS installation\" href=\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-things-to-know-binaries-jms-installation\/\" target=\"_blank\" rel=\"noopener\">Documentum binaries<\/a>, a <a title=\"Documentum \u2013 Silent Install \u2013 Docbroker &amp; Licences\" href=\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-docbroker-licences\/\" target=\"_blank\" rel=\"noopener\">docbroker<\/a> (+licence(s) if needed), several <a title=\"Documentum \u2013 Silent Install \u2013 Docbases\/Repositories\" href=\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-docbasesrepositories\/\" target=\"_blank\" rel=\"noopener\">repositories<\/a> and finally <a title=\"Documentum \u2013 Silent Install \u2013 D2\" href=\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-d2\/\" target=\"_blank\" rel=\"noopener\">D2<\/a>. In this one, we will see how to install remote docbases\/repositories to have a High Availability environment with the docbases\/repositories that we already installed in silent.<\/p>\n<p>As mentioned in the first blog of this series, there is a utility under &#8220;$DM_HOME\/install\/silent\/silenttool&#8221; that can be used to generate a skeleton for a CFS\/Remote CS but there are still missing parameters so I will describe them in this blog.<\/p>\n<p>In this blog, I will also configure the Global Repository (GR) in HA so that you have it available even if the first node fails&#8230; This is particularly important if, like me, you prefer to set the GR as the crypto repository (so it is the repository used for encryption\/decryption).<\/p>\n<p>&nbsp;<\/p>\n<h3>1. Documentum Remote Global Registry repository installation<\/h3>\n<p>The properties file for a Remote GR installation is as follow (it supposes that you already have the binaries and a docbroker installed on this Remote CS):<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">[dmadmin@content_server_02 ~]$ vi \/tmp\/dctm_install\/CFS_Docbase_GR.properties\n[dmadmin@content_server_02 ~]$ cat \/tmp\/dctm_install\/CFS_Docbase_GR.properties\n### Silent installation response file for a Remote Docbase (GR)\nINSTALLER_UI=silent\nKEEP_TEMP_FILE=true\n\n### Action to be executed\nSERVER.COMPONENT_ACTION=CREATE\n\n### Docbase parameters\ncommon.aek.passphrase.password=a3kP4ssw0rd\ncommon.aek.key.name=CSaek\ncommon.aek.algorithm=AES_256_CBC\nSERVER.ENABLE_LOCKBOX=true\nSERVER.LOCKBOX_FILE_NAME=lockbox.lb\nSERVER.LOCKBOX_PASSPHRASE.PASSWORD=l0ckb0xP4ssw0rd\n\nSERVER.DOCUMENTUM_DATA=\nSERVER.DOCUMENTUM_SHARE=\nSERVER.FQDN=content_server_02.dbi-services.com\n\nSERVER.DOCBASE_NAME=gr_docbase\nSERVER.PRIMARY_SERVER_CONFIG_NAME=gr_docbase\nCFS_SERVER_CONFIG_NAME=content_server_02_gr_docbase\nSERVER.DOCBASE_SERVICE_NAME=gr_docbase\nSERVER.REPOSITORY_USERNAME=dmadmin\nSERVER.SECURE.REPOSITORY_PASSWORD=dm4dm1nP4ssw0rd\nSERVER.REPOSITORY_USER_DOMAIN=\nSERVER.REPOSITORY_USERNAME_WITH_DOMAIN=dmadmin\nSERVER.REPOSITORY_HOSTNAME=content_server_01.dbi-services.com\n\nSERVER.USE_CERTIFICATES=false\n\nSERVER.PRIMARY_CONNECTION_BROKER_HOST=content_server_01.dbi-services.com\nSERVER.PRIMARY_CONNECTION_BROKER_PORT=1489\nSERVER.PROJECTED_CONNECTION_BROKER_HOST=content_server_02.dbi-services.com\nSERVER.PROJECTED_CONNECTION_BROKER_PORT=1489\n\nSERVER.DFC_BOF_GLOBAL_REGISTRY_VALIDATE_OPTION_IS_SELECTED=true\nSERVER.PROJECTED_DOCBROKER_HOST_OTHER=content_server_01.dbi-services.com\nSERVER.PROJECTED_DOCBROKER_PORT_OTHER=1489\nSERVER.GLOBAL_REGISTRY_REPOSITORY=gr_docbase\nSERVER.BOF_REGISTRY_USER_LOGIN_NAME=dm_bof_registry\nSERVER.SECURE.BOF_REGISTRY_USER_PASSWORD=dm_b0f_reg1s7ryP4ssw0rd\n\n[dmadmin@content_server_02 ~]$\n[dmadmin@content_server_02 ~]$\n[dmadmin@content_server_02 ~]$ sed -i \"s,SERVER.DOCUMENTUM_DATA=.*,SERVER.DOCUMENTUM_DATA=$DOCUMENTUM\/data,\" \/tmp\/dctm_install\/CFS_Docbase_GR.properties\n[dmadmin@content_server_02 ~]$ sed -i \"s,SERVER.DOCUMENTUM_SHARE=.*,SERVER.DOCUMENTUM_SHARE=$DOCUMENTUM\/share,\" \/tmp\/dctm_install\/CFS_Docbase_GR.properties\n[dmadmin@content_server_02 ~]$<\/pre>\n<p>&nbsp;<\/p>\n<p>Just like in previous blog, I will let you set the DATA and SHARE folders as you want to.<\/p>\n<p>A short description of these properties:<\/p>\n<ul>\n<li>INSTALLER_UI: The mode to use for the installation, here it is obviously silent<\/li>\n<li>KEEP_TEMP_FILE: Whether or not you want to keep the temporary files created by the installer. These files are generated under the \/tmp folder. I usually keep them because I want to be able to check them if something went wrong<\/li>\n<li>SERVER.COMPONENT_ACTION: The action to be executed, it can be either CREATE, UPGRADE or DELETE. You can upgrade a Documentum environment in silent even if the source doesn&#8217;t support the silent installation\/upgrade as long as the target version (CS 7.3, CS 16.4, &#8230;) does<\/li>\n<li>common.aek.passphrase.password: The password used for the AEK on the Primary CS<\/li>\n<li>common.aek.key.name: The name of the AEK key used on the Primary CS. This is usually something like &#8220;CSaek&#8221;<\/li>\n<li>common.aek.algorithm: The algorithm used for the AEK key. I would recommend the strongest one, if possible: &#8220;AES_256_CBC&#8221;<\/li>\n<li>SERVER.ENABLE_LOCKBOX: Whether or not you used a Lockbox to protect the AEK key on the Primary CS. If set to true, the lockbox will be downloaded from the Primary CS, that&#8217;s why you don&#8217;t need the &#8220;common.use.existing.aek.lockbox&#8221; property<\/li>\n<li>SERVER.LOCKBOX_FILE_NAME: The name of the Lockbox used on the Primary CS. This is usually something like &#8220;lockbox.lb&#8221;<\/li>\n<li>SERVER.LOCKBOX_PASSPHRASE.PASSWORD: The password used for the Lockbox on the Primary CS<\/li>\n<li>SERVER.DOCUMENTUM_DATA: The path to be used to store the Documentum documents, accessible from all Content Servers which will host this docbase\/repository<\/li>\n<li>SERVER.DOCUMENTUM_SHARE: The path to be used for the share folder<\/li>\n<li>SERVER.FQDN: The Fully Qualified Domain Name of the current host the docbase\/repository is being installed on<\/li>\n<li>SERVER.DOCBASE_NAME: The name of the docbase\/repository created on the Primary CS (dm_docbase_config.object_name)<\/li>\n<li>SERVER.PRIMARY_SERVER_CONFIG_NAME: The name of the dm_server_config object created on the Primary CS<\/li>\n<li>CFS_SERVER_CONFIG_NAME: The name of dm_server_config object to be created for this Remote CS<\/li>\n<li>SERVER.DOCBASE_SERVICE_NAME: The name of the service to be used<\/li>\n<li>SERVER.REPOSITORY_USERNAME: The name of the Installation Owner. I believe it can be any superuser account but I didn&#8217;t test it<\/li>\n<li>SERVER.SECURE.REPOSITORY_PASSWORD: The password of the above account<\/li>\n<li>SERVER.REPOSITORY_USER_DOMAIN: The domain of the above account. If using an inline user like the Installation Owner, you should keep it empty<\/li>\n<li>SERVER.REPOSITORY_USERNAME_WITH_DOMAIN: Same value as the REPOSITORY_USERNAME if the USER_DOMAIN is kept empty<\/li>\n<li>SERVER.REPOSITORY_HOSTNAME: The Fully Qualified Domain Name of the Primary CS<\/li>\n<li>SERVER.USE_CERTIFICATES: Whether or not to use SSL Certificate for the docbase\/repository (it goes with the SERVER.CONNECT_MODE). If you set this to true, you will have to add the usual additional parameters, just like for the Primary CS<\/li>\n<li>SERVER.PRIMARY_CONNECTION_BROKER_HOST: The Fully Qualified Domain Name of the Primary CS<\/li>\n<li>SERVER.PRIMARY_CONNECTION_BROKER_PORT: The port used by the docbroker\/connection broker on the Primary CS<\/li>\n<li>SERVER.PROJECTED_CONNECTION_BROKER_HOST: The hostname to be use for the [DOCBROKER_PROJECTION_TARGET] on the server.ini file, meaning the docbroker\/connection broker the docbase\/repository should project to, by default<\/li>\n<li>SERVER.PROJECTED_CONNECTION_BROKER_PORT: The port to be use for the [DOCBROKER_PROJECTION_TARGET] on the server.ini file, meaning the docbroker\/connection broker the docbase\/repository should project to, by default<\/li>\n<li>SERVER.DFC_BOF_GLOBAL_REGISTRY_VALIDATE_OPTION_IS_SELECTED: Whether or not you want to validate the GR on the Primary CS. I always set this to true for the first docbase\/repository installed on the Remote CS (in other words: for the GR installation). If you set this to true, you will have to provide some additional parameters:\n<ul>\n<li>SERVER.PROJECTED_DOCBROKER_HOST_OTHER: The Fully Qualified Domain Name of the docbroker\/connection broker that the GR on the Primary CS projects to so this is usually the Primary CS&#8230;<\/li>\n<li>SERVER.PROJECTED_DOCBROKER_PORT_OTHER: The port of the docbroker\/connection broker that the GR on the Primary CS projects to<\/li>\n<li>SERVER.GLOBAL_REGISTRY_REPOSITORY: The name of the GR repository<\/li>\n<li>SERVER.BOF_REGISTRY_USER_LOGIN_NAME: The name of the BOF Registry account created on the Primary CS inside the GR repository. This is usually something like &#8220;dm_bof_registry&#8221;<\/li>\n<li>SERVER.SECURE.BOF_REGISTRY_USER_PASSWORD: The password used by the BOF Registry account<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>Once the properties file is ready, first make sure the gr_docbase is running on the &#8220;Primary&#8221; CS (content_server_01) and then start the CFS installer using the following commands:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">[dmadmin@content_server_02 ~]$ dmqdocbroker -t content_server_01.dbi-services.com -p 1489 -c getservermap gr_docbase\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 7.3.0040.0025\nUsing specified port: 1489\n**************************************************\n**     D O C B R O K E R    I N F O             **\n**************************************************\nDocbroker host            : content_server_01.dbi-services.com\nDocbroker port            : 1490\nDocbroker network address : INET_ADDR: 12 123 12345678 content_server_01.dbi-services.com 123.123.123.123\nDocbroker version         : 7.3.0050.0039  Linux64\n**************************************************\n**           S E R V E R     M A P              **\n**************************************************\nDocbase gr_docbase has 1 server:\n--------------------------------------------\n  server name         :  gr_docbase\n  server host         :  content_server_01.dbi-services.com\n  server status       :  Open\n  client proximity    :  1\n  server version      :  7.3.0050.0039  Linux64.Oracle\n  server process id   :  12345\n  last ckpt time      :  6\/12\/2018 14:23:35\n  next ckpt time      :  6\/12\/2018 14:28:35\n  connect protocol    :  TCP_RPC\n  connection addr     :  INET_ADDR: 12 123 12345678 content_server_01.dbi-services.com 123.123.123.123\n  keep entry interval :  1440\n  docbase id          :  1010101\n  server dormancy status :  Active\n--------------------------------------------\n[dmadmin@content_server_02 ~]$\n[dmadmin@content_server_02 ~]$ $DM_HOME\/install\/dm_launch_cfs_server_config_program.sh -f \/tmp\/dctm_install\/CFS_Docbase_GR.properties<\/pre>\n<p>&nbsp;<\/p>\n<p>Don&#8217;t forget to check the logs once done to make sure it went without issue!<\/p>\n<p>&nbsp;<\/p>\n<h3>2. Other Remote repository installation<\/h3>\n<p>Once you have the Remote Global Registry repository installed, you can install the Remote repository that will be used by the end-users (which isn&#8217;t a GR then). The properties file for an additional remote repository is as follow:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">[dmadmin@content_server_02 ~]$ vi \/tmp\/dctm_install\/CFS_Docbase_Other.properties\n[dmadmin@content_server_02 ~]$ cat \/tmp\/dctm_install\/CFS_Docbase_Other.properties\n### Silent installation response file for a Remote Docbase\nINSTALLER_UI=silent\nKEEP_TEMP_FILE=true\n\n### Action to be executed\nSERVER.COMPONENT_ACTION=CREATE\n\n### Docbase parameters\ncommon.aek.passphrase.password=a3kP4ssw0rd\ncommon.aek.key.name=CSaek\ncommon.aek.algorithm=AES_256_CBC\nSERVER.ENABLE_LOCKBOX=true\nSERVER.LOCKBOX_FILE_NAME=lockbox.lb\nSERVER.LOCKBOX_PASSPHRASE.PASSWORD=l0ckb0xP4ssw0rd\n\nSERVER.DOCUMENTUM_DATA=\nSERVER.DOCUMENTUM_SHARE=\nSERVER.FQDN=content_server_02.dbi-services.com\n\nSERVER.DOCBASE_NAME=Docbase1\nSERVER.PRIMARY_SERVER_CONFIG_NAME=Docbase1\nCFS_SERVER_CONFIG_NAME=content_server_02_Docbase1\nSERVER.DOCBASE_SERVICE_NAME=Docbase1\nSERVER.REPOSITORY_USERNAME=dmadmin\nSERVER.SECURE.REPOSITORY_PASSWORD=dm4dm1nP4ssw0rd\nSERVER.REPOSITORY_USER_DOMAIN=\nSERVER.REPOSITORY_USERNAME_WITH_DOMAIN=dmadmin\nSERVER.REPOSITORY_HOSTNAME=content_server_01.dbi-services.com\n\nSERVER.USE_CERTIFICATES=false\n\nSERVER.PRIMARY_CONNECTION_BROKER_HOST=content_server_01.dbi-services.com\nSERVER.PRIMARY_CONNECTION_BROKER_PORT=1489\nSERVER.PROJECTED_CONNECTION_BROKER_HOST=content_server_02.dbi-services.com\nSERVER.PROJECTED_CONNECTION_BROKER_PORT=1489\n\n[dmadmin@content_server_02 ~]$\n[dmadmin@content_server_02 ~]$\n[dmadmin@content_server_02 ~]$ sed -i \"s,SERVER.DOCUMENTUM_DATA=.*,SERVER.DOCUMENTUM_DATA=$DOCUMENTUM\/data,\" \/tmp\/dctm_install\/CFS_Docbase_Other.properties\n[dmadmin@content_server_02 ~]$ sed -i \"s,SERVER.DOCUMENTUM_SHARE=.*,SERVER.DOCUMENTUM_SHARE=$DOCUMENTUM\/share,\" \/tmp\/dctm_install\/CFS_Docbase_Other.properties\n[dmadmin@content_server_02 ~]$<\/pre>\n<p>&nbsp;<\/p>\n<p>I won&#8217;t list all these parameters again because as you can see above, it is exactly the same, except the docbase\/repository name. Only the last section regarding the GR validation isn&#8217;t needed anymore. Once the properties file is ready, you can install the additional remote repository in the same way:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">[dmadmin@content_server_02 ~]$ dmqdocbroker -t content_server_01.dbi-services.com -p 1489 -c getservermap Docbase1\ndmqdocbroker: A DocBroker Query Tool\ndmqdocbroker: Documentum Client Library Version: 7.3.0040.0025\nUsing specified port: 1489\n**************************************************\n**     D O C B R O K E R    I N F O             **\n**************************************************\nDocbroker host            : content_server_01.dbi-services.com\nDocbroker port            : 1490\nDocbroker network address : INET_ADDR: 12 123 12345678 content_server_01.dbi-services.com 123.123.123.123\nDocbroker version         : 7.3.0050.0039  Linux64\n**************************************************\n**           S E R V E R     M A P              **\n**************************************************\nDocbase Docbase1 has 1 server:\n--------------------------------------------\n  server name         :  Docbase1\n  server host         :  content_server_01.dbi-services.com\n  server status       :  Open\n  client proximity    :  1\n  server version      :  7.3.0050.0039  Linux64.Oracle\n  server process id   :  23456\n  last ckpt time      :  6\/12\/2018 14:46:42\n  next ckpt time      :  6\/12\/2018 14:51:42\n  connect protocol    :  TCP_RPC\n  connection addr     :  INET_ADDR: 12 123 12345678 content_server_01.dbi-services.com 123.123.123.123\n  keep entry interval :  1440\n  docbase id          :  1010102\n  server dormancy status :  Active\n--------------------------------------------\n[dmadmin@content_server_02 ~]$\n[dmadmin@content_server_02 ~]$ $DM_HOME\/install\/dm_launch_cfs_server_config_program.sh -f \/tmp\/dctm_install\/CFS_Docbase_Other.properties<\/pre>\n<p>&nbsp;<\/p>\n<p>At this point, you will have the second docbases\/repositories dm_server_config object created but that&#8217;s pretty much all you got&#8230; For a correct\/working HA solution, you will need to configure the jobs for HA support (is_restartable, method_verb, &#8230;), maybe change the checkpoint_interval, configure the projections, trust the needed DFC clients (JMS applications), aso&#8230;<\/p>\n<p>&nbsp;<\/p>\n<p>You now know how to install and configure a Global Registry repository as well as any other docbase\/repository on a &#8220;Remote&#8221; Content Server (CFS) using the silent installation provided by Documentum.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In previous blogs, we installed in silent the Documentum binaries, a docbroker (+licence(s) if needed), several repositories and finally D2. In this one, we will see how to install remote docbases\/repositories to have a High Availability environment with the docbases\/repositories that we already installed in silent. As mentioned in the first blog of this series, [&hellip;]<\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197,525],"tags":[129,101,1417],"type_dbi":[],"class_list":["post-11628","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","category-enterprise-content-management","tag-documentum","tag-installation","tag-silent"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Documentum - Silent Install - Remote Docbases\/Repositories (HA) - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum - Silent Install - Remote Docbases\/Repositories (HA)\" \/>\n<meta property=\"og:description\" content=\"In previous blogs, we installed in silent the Documentum binaries, a docbroker (+licence(s) if needed), several repositories and finally D2. In this one, we will see how to install remote docbases\/repositories to have a High Availability environment with the docbases\/repositories that we already installed in silent. As mentioned in the first blog of this series, [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-09-01T06:00:22+00:00\" \/>\n<meta name=\"author\" content=\"Morgan Patou\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@MorganPatou\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Morgan Patou\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum &#8211; Silent Install &#8211; Remote Docbases\/Repositories (HA)\",\"datePublished\":\"2018-09-01T06:00:22+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/\"},\"wordCount\":1202,\"commentCount\":0,\"keywords\":[\"Documentum\",\"Installation\",\"Silent\"],\"articleSection\":[\"Application integration &amp; Middleware\",\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/\",\"name\":\"Documentum - Silent Install - Remote Docbases\/Repositories (HA) - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2018-09-01T06:00:22+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum &#8211; Silent Install &#8211; Remote Docbases\/Repositories (HA)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\",\"name\":\"Morgan Patou\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"caption\":\"Morgan Patou\"},\"description\":\"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex &amp; critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.\",\"sameAs\":[\"https:\/\/blog.dbi-services.com\/author\/morgan-patou\/\",\"https:\/\/x.com\/MorganPatou\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Documentum - Silent Install - Remote Docbases\/Repositories (HA) - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/","og_locale":"en_US","og_type":"article","og_title":"Documentum - Silent Install - Remote Docbases\/Repositories (HA)","og_description":"In previous blogs, we installed in silent the Documentum binaries, a docbroker (+licence(s) if needed), several repositories and finally D2. In this one, we will see how to install remote docbases\/repositories to have a High Availability environment with the docbases\/repositories that we already installed in silent. As mentioned in the first blog of this series, [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/","og_site_name":"dbi Blog","article_published_time":"2018-09-01T06:00:22+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum &#8211; Silent Install &#8211; Remote Docbases\/Repositories (HA)","datePublished":"2018-09-01T06:00:22+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/"},"wordCount":1202,"commentCount":0,"keywords":["Documentum","Installation","Silent"],"articleSection":["Application integration &amp; Middleware","Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/","name":"Documentum - Silent Install - Remote Docbases\/Repositories (HA) - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-09-01T06:00:22+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-silent-install-remote-docbasesrepositories-ha\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum &#8211; Silent Install &#8211; Remote Docbases\/Repositories (HA)"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8","name":"Morgan Patou","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","caption":"Morgan Patou"},"description":"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex &amp; critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.","sameAs":["https:\/\/blog.dbi-services.com\/author\/morgan-patou\/","https:\/\/x.com\/MorganPatou"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11628","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=11628"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/11628\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=11628"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=11628"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=11628"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=11628"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}