{"id":8990,"date":"2016-10-19T09:55:14","date_gmt":"2016-10-19T07:55:14","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/"},"modified":"2016-10-19T09:55:14","modified_gmt":"2016-10-19T07:55:14","slug":"documentum-story-jobs-in-a-high-availability-installation","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/","title":{"rendered":"Documentum story &#8211; Jobs in a high availability installation"},"content":{"rendered":"<p>When you have an installation with one Content Server (CS) you do not take care where the job will be running. It&#8217;s always on your single CS.<br \/>\nBut how should you configure the jobs in case you have several CS? Which jobs have to be executed and which one not? Let&#8217;s see that in this post.<\/p>\n<p>When you have to run your jobs in a high availability installation you have to\u00a0configure some files and objects.<\/p>\n<p>Update the method_verb of the dm_agent_exec method:<\/p>\n<pre class=\"brush: actionscript3; gutter: false; first-line: 1\">API&gt; retrieve,c,dm_method where object_name = 'agent_exec_method'\nAPI&gt; get,c,l,method_verb\nAPI&gt; set,c,l,method_verb\nSET&gt; .\/dm_agent_exec -enable_ha_setup 1\nAPI&gt; get,c,l,method_verb\nAPI&gt; save,c,l\nAPI&gt; reinit,c\n<\/pre>\n<p>&nbsp;<\/p>\n<p>The java methods have been updated to\u00a0be restartable:<\/p>\n<pre class=\"brush: actionscript3; gutter: false; first-line: 1\">update dm_method object set is_restartable=1 where method_type='java';\n<\/pre>\n<p>&nbsp;<\/p>\n<p>On our installation we use jms_max_wait_time_on_failures = 300 instead the default one (3000).<br \/>\nIn server.ini (Primary Content Server) and server_HOSTNAME2_REPO01.ini (Remote Content Server), we have:<\/p>\n<pre class=\"brush: actionscript3; gutter: false; first-line: 1\">incremental_jms_wait_time_on_failure=30\njms_max_wait_time_on_failures=300\n<\/pre>\n<p>&nbsp;<\/p>\n<p>Based on some issues we faced, for instance with the dce_clean job that ran twice when we had both JMS projected to each CS, EMC advised us to each JMS with its local CS only. With this configuration, in case the JMS is down on the primary CS, the job (using a java method)\u00a0is started on the\u00a0remote JMS via the remote CS.<\/p>\n<p>Regarding which jobs have to be executed &#8211;\u00a0I am describing only the one which are used for the housekeeping.<br \/>\nSo the question to answer is which job does what and what is &#8220;touched&#8221;, either metadata or\/and content.<\/p>\n<p>To verify that, check how many CS are used and where they are installed:<\/p>\n<pre class=\"brush: actionscript3; gutter: false; first-line: 1\">select object_name, r_host_name from dm_server_config\nREPO1               HOSTNAME1.DOMAIN\nHOSTNAME2_REPO1     HOSTNAME2.DOMAIN<\/pre>\n<p>&nbsp;<\/p>\n<p>Verify on which CS the jobs will run and &#8220;classify&#8221; them.<br \/>\nCheck the job settings:<\/p>\n<pre class=\"brush: actionscript3; gutter: false; first-line: 1\">select object_name, target_server, is_inactive from dm_job<\/pre>\n<h4><\/h4>\n<h4>Metadata<\/h4>\n<p>The following jobs\u00a0work only on metadata, they can run anywhere so the target_server has to be empty<\/p>\n<table style=\"height: 179px\" width=\"686\">\n<tbody>\n<tr>\n<td>\u00a0object_name<\/td>\n<td>target_server<\/td>\n<td>is_inactive<\/td>\n<\/tr>\n<tr>\n<td>dm_ConsistencyChecker<\/td>\n<td><\/td>\n<td>False<\/td>\n<\/tr>\n<tr>\n<td>dm_DBWarning<\/td>\n<td><\/td>\n<td>False<\/td>\n<\/tr>\n<tr>\n<td>dm_FileReport<\/td>\n<td><\/td>\n<td>False<\/td>\n<\/tr>\n<tr>\n<td>dm_QueueMgt<\/td>\n<td><\/td>\n<td>False<\/td>\n<\/tr>\n<tr>\n<td>dm_StateOfDocbase<\/td>\n<td><\/td>\n<td>False<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<h4>Content<\/h4>\n<p>The following\u00a0jobs work only on content.<\/p>\n<table style=\"height: 94px\" width=\"685\">\n<tbody>\n<tr>\n<td>\u00a0\u00a0object_name<\/td>\n<td>\u00a0target_server<\/td>\n<\/tr>\n<tr>\n<td>dm_ContentWarning<\/td>\n<td>\u00a0REPO1.REPO1@HOSTNAME1.DOMAIN<\/td>\n<\/tr>\n<tr>\n<td>dm_ContentWarningHOSTNAME2_REPO1<\/td>\n<td>\u00a0REPO1.HOSTNAME2_REPO1@HOSTNAME2.DOMAIN<\/td>\n<\/tr>\n<tr>\n<td>dm_DMClean<\/td>\n<td>REPO1.REPO1@HOSTNAME1.DOMAIN<\/td>\n<\/tr>\n<tr>\n<td>dm_DMCleanHOSTNAME2_REPO1<\/td>\n<td>\u00a0REPO1.HOSTNAME2_REPO1@HOSTNAME2.DOMAIN<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>As we are using a NAS for the Data directory which is shared for both servers, only one of the two jobs has to run. Per default the target_server is defined. So for the one which has to run, target_server has to be empty.<\/p>\n<table style=\"height: 94px\" width=\"685\">\n<tbody>\n<tr>\n<td>\u00a0\u00a0object_name<\/td>\n<td>\u00a0target_server<\/td>\n<td>\u00a0is_inactive<\/td>\n<\/tr>\n<tr>\n<td>dm_ContentWarning<\/td>\n<td><\/td>\n<td>False<\/td>\n<\/tr>\n<tr>\n<td>dm_ContentWarningHOSTNAME2_REPO1<\/td>\n<td>\u00a0REPO1.HOSTNAME2_REPO1@HOSTNAME2.DOMAIN<\/td>\n<td>True<\/td>\n<\/tr>\n<tr>\n<td>dm_DMClean<\/td>\n<td><\/td>\n<td>False<\/td>\n<\/tr>\n<tr>\n<td>dm_DMCleanHOSTNAME2_REPO1<\/td>\n<td>\u00a0REPO1.HOSTNAME2_REPO1@HOSTNAME2.DOMAIN<\/td>\n<td>True<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h4>Metadata and Content<\/h4>\n<p>These following\u00a0jobs are working on metadata and content.<\/p>\n<table style=\"height: 214px\" width=\"831\">\n<tbody>\n<tr>\n<td>\u00a0\u00a0\u00a0object_name<\/td>\n<td>\u00a0\u00a0target_server<\/td>\n<\/tr>\n<tr>\n<td>dm_DMFilescan<\/td>\n<td>\u00a0REPO1.REPO1@HOSTNAME1.DOMAIN<\/td>\n<\/tr>\n<tr>\n<td>dm_DMFilescanHOSTNAME2_REPO1<\/td>\n<td>\u00a0REPO1.HOSTNAME2_REPO1@HOSTNAME2.DOMAIN<\/td>\n<\/tr>\n<tr>\n<td>dm_LogPurge<\/td>\n<td>\u00a0REPO1.REPO1@HOSTNAME1.DOMAIN<\/td>\n<\/tr>\n<tr>\n<td>dm_LogPurgeHOSTNAME2_REPO1<\/td>\n<td>\u00a0REPO1.HOSTNAME2_REPO1@HOSTNAME2.DOMAIN<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Filescan\u00a0scans the NAS content storage. As said above, it is shared and therefore the job only need to be execute once: the\u00a0target_server has to be empty to be run everywhere.<\/p>\n<p>LogPurge is also cleaning files under $DOCUMENTUM\/dba\/log and subfolders which are obviously not shared and therefore both dm_LogPurge jobs have to run. You just have to use another start time to avoid an overlap when objects are removed from the repository.<\/p>\n<table style=\"height: 214px\" width=\"831\">\n<tbody>\n<tr>\n<td>\u00a0\u00a0\u00a0object_name<\/td>\n<td>\u00a0\u00a0target_server<\/td>\n<td>\u00a0\u00a0is_inactive<\/td>\n<\/tr>\n<tr>\n<td>dm_DMFilescan<\/td>\n<td><\/td>\n<td>False<\/td>\n<\/tr>\n<tr>\n<td>dm_DMFilescanHOSTNAME2_REPO1<\/td>\n<td>\u00a0REPO1.HOSTNAME2_REPO1@HOSTNAME2.DOMAIN<\/td>\n<td>True<\/td>\n<\/tr>\n<tr>\n<td>dm_LogPurge<\/td>\n<td>\u00a0REPO1.REPO1@HOSTNAME1.DOMAIN<\/td>\n<td>False<\/td>\n<\/tr>\n<tr>\n<td>dm_LogPurgeHOSTNAME2_REPO1<\/td>\n<td>\u00a0REPO1.HOSTNAME2_REPO1@HOSTNAME2.DOMAIN<\/td>\n<td>False<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Normally with this configuration your housekeeping jobs should be well configured.<\/p>\n<p>One point you have to take care is when you use DA to configure your jobs. Once you open the job properties, the &#8220;Designated Server&#8221; is set to one of your server and not to &#8220;Any Running Server&#8221; which means target_server = &#8216; &#8216;. If you click the OK button, you will set the target server and in case this CS is down, the job will fail because it cannot use the second CS.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When you have an installation with one Content Server (CS) you do not take care where the job will be running. It&#8217;s always on your single CS. But how should you configure the jobs in case you have several CS? Which jobs have to be executed and which one not? Let&#8217;s see that in this [&hellip;]<\/p>\n","protected":false},"author":24,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[525],"tags":[129,101],"type_dbi":[],"class_list":["post-8990","post","type-post","status-publish","format-standard","hentry","category-enterprise-content-management","tag-documentum","tag-installation"],"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 story - Jobs in a high availability installation - 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-story-jobs-in-a-high-availability-installation\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum story - Jobs in a high availability installation\" \/>\n<meta property=\"og:description\" content=\"When you have an installation with one Content Server (CS) you do not take care where the job will be running. It&#8217;s always on your single CS. But how should you configure the jobs in case you have several CS? Which jobs have to be executed and which one not? Let&#8217;s see that in this [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-10-19T07:55:14+00:00\" \/>\n<meta name=\"author\" content=\"G\u00e9rard Wisson\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"G\u00e9rard Wisson\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 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-story-jobs-in-a-high-availability-installation\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/\"},\"author\":{\"name\":\"G\u00e9rard Wisson\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/ad54b5e621903122c00c6b7921c6ab85\"},\"headline\":\"Documentum story &#8211; Jobs in a high availability installation\",\"datePublished\":\"2016-10-19T07:55:14+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/\"},\"wordCount\":670,\"commentCount\":0,\"keywords\":[\"Documentum\",\"Installation\"],\"articleSection\":[\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/\",\"name\":\"Documentum story - Jobs in a high availability installation - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2016-10-19T07:55:14+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/ad54b5e621903122c00c6b7921c6ab85\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum story &#8211; Jobs in a high availability installation\"}]},{\"@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\/ad54b5e621903122c00c6b7921c6ab85\",\"name\":\"G\u00e9rard Wisson\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/1eb607e2c436690f1f57c55db47a3fabb0d11955ea9a2510605d5e5813632408?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/1eb607e2c436690f1f57c55db47a3fabb0d11955ea9a2510605d5e5813632408?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/1eb607e2c436690f1f57c55db47a3fabb0d11955ea9a2510605d5e5813632408?s=96&d=mm&r=g\",\"caption\":\"G\u00e9rard Wisson\"},\"description\":\"G\u00e9rard Wisson has more than ten years of experience in Enterprise Content Management (ECM) with Documentum as well as in Oracle WebLogic and Java EE \/ J2EE infrastructures. He is specialized in ECM infrastructure services such as installation, upgrade, high availability, and administration as well as in Oracle WebLogic services such as installation, configuration, and management. He is very experienced in the monitoring and optimization of Java EE \/ J2EE infrastructures with Grid\/Cloud Control and JVMD. G\u00e9rard Wisson is certified Oracle Weblogic Server 11g System Administrator and Oracle Certified Associate. Prior to joining dbi services, G\u00e9rard Wisson was Senior Consultant at Solfit in Basel. He holds a diploma in Electrical Engineering from the University of Strasbourg (F). His branch-related experience covers Financial Services \/ Banking, Chemicals &amp; Pharmaceuticals, etc.\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/gerard-wisson\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Documentum story - Jobs in a high availability installation - 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-story-jobs-in-a-high-availability-installation\/","og_locale":"en_US","og_type":"article","og_title":"Documentum story - Jobs in a high availability installation","og_description":"When you have an installation with one Content Server (CS) you do not take care where the job will be running. It&#8217;s always on your single CS. But how should you configure the jobs in case you have several CS? Which jobs have to be executed and which one not? Let&#8217;s see that in this [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/","og_site_name":"dbi Blog","article_published_time":"2016-10-19T07:55:14+00:00","author":"G\u00e9rard Wisson","twitter_card":"summary_large_image","twitter_misc":{"Written by":"G\u00e9rard Wisson","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/"},"author":{"name":"G\u00e9rard Wisson","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/ad54b5e621903122c00c6b7921c6ab85"},"headline":"Documentum story &#8211; Jobs in a high availability installation","datePublished":"2016-10-19T07:55:14+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/"},"wordCount":670,"commentCount":0,"keywords":["Documentum","Installation"],"articleSection":["Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/","name":"Documentum story - Jobs in a high availability installation - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2016-10-19T07:55:14+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/ad54b5e621903122c00c6b7921c6ab85"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-story-jobs-in-a-high-availability-installation\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum story &#8211; Jobs in a high availability installation"}]},{"@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\/ad54b5e621903122c00c6b7921c6ab85","name":"G\u00e9rard Wisson","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/1eb607e2c436690f1f57c55db47a3fabb0d11955ea9a2510605d5e5813632408?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/1eb607e2c436690f1f57c55db47a3fabb0d11955ea9a2510605d5e5813632408?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1eb607e2c436690f1f57c55db47a3fabb0d11955ea9a2510605d5e5813632408?s=96&d=mm&r=g","caption":"G\u00e9rard Wisson"},"description":"G\u00e9rard Wisson has more than ten years of experience in Enterprise Content Management (ECM) with Documentum as well as in Oracle WebLogic and Java EE \/ J2EE infrastructures. He is specialized in ECM infrastructure services such as installation, upgrade, high availability, and administration as well as in Oracle WebLogic services such as installation, configuration, and management. He is very experienced in the monitoring and optimization of Java EE \/ J2EE infrastructures with Grid\/Cloud Control and JVMD. G\u00e9rard Wisson is certified Oracle Weblogic Server 11g System Administrator and Oracle Certified Associate. Prior to joining dbi services, G\u00e9rard Wisson was Senior Consultant at Solfit in Basel. He holds a diploma in Electrical Engineering from the University of Strasbourg (F). His branch-related experience covers Financial Services \/ Banking, Chemicals &amp; Pharmaceuticals, etc.","url":"https:\/\/www.dbi-services.com\/blog\/author\/gerard-wisson\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8990","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\/24"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=8990"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/8990\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=8990"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=8990"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=8990"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=8990"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}