{"id":13462,"date":"2020-02-23T22:54:30","date_gmt":"2020-02-23T21:54:30","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/"},"modified":"2020-02-23T22:54:30","modified_gmt":"2020-02-23T21:54:30","slug":"control-m-agent-upgrade-communication-issue","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/","title":{"rendered":"Control-M &#8211; Agent Upgrade &#8211; Communication Issue"},"content":{"rendered":"<p>At a customer, we are upgrading Control-M Agents running on Windows\/Unix from 9.0.00.400 to 9.0.19.200 using Agent Deployment, an upgrade of one agent fails with error talking about communication issue between Control-M\/server and Control-M agent:<br \/>\n<!--more--><strong>Testing Communication with Control-M\/Server using new Control-M\/Agent binaries failed, Control-M\/Agent Upgrade aborted, please check Log and agent installation requirements<\/strong><br \/>\n<img decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Blog-upg-agt-nok.png\" \/><\/p>\n<p>On the other hand, the agent seems to be Available as shown in the above screenshot &#8220;Connected&#8221;, and all jobs running on it are executing and Ended OK. So why this communication fails? I found the response \ud83d\ude09<\/p>\n<h1>Analysis<\/h1>\n<p>As said above, I made a check on this agent on CCM and it was Available:<br \/>\n<img decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Blog-upg-agt-nok-v.png\" \/><\/p>\n<p>Humm, maybe the CCM is not saying the truth, let&#8217;s ask ctm_diag_comm:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1 highlight: [26,27]\">\nlds00% ctm_diag_comm\n\nEnter Agent platform node ID: lds10.dbi\n\nThis procedure runs for about 30 seconds. Please wait\n\nTime Stamp :\n-------------\nFri Feb 21 18:54:18 CET 2020\n\nExecuting ctmping lds10.dbi as Regular Agent .\n\nCONTROL-M\/Server to CONTROL-M\/Agent Communication Diagnostic Report\n-------------------------------------------------------------------\n\n CTMS User Name                    : cmsv\n CTMS Directory                    : \/pk\/cntrlm\/server\/ctm_server\n CTMS Platform Architecture        : Linux-x86_64\n CTMS Installed Version            : PACTV.9.0.19.200\n CTMS Local IP Host Interface Name : ctlm9.dbi\n Server-to-Agent Port Number       : 7008\n Agent-to-Server Port Number       : 7005\n Server-Agent Comm. Protocol       : SSL\n Server-Agent Protocol Version     : 11\n Server-Agent Connection mode      : Transient\n Agent Platform Name               : lds10.dbi\n Agent Status                      : Available\n Agent known Type                  : Regular\n UNIX ping to Agent or Remote host : Succeeded\n CTMS ping to Agent or Remote host : Succeeded\n Agent IP Address                  : 10.25.35.1\n\n CTMS Ping lds10.dbi as Regular Agent\n ================================================\n Agent [lds10.dbi] is available\n<\/pre>\n<p>So, it is available&#8230; But why the communication fails during the upgrade.<\/p>\n<p>Let&#8217;s check on the agent side, I execute ctmagcfg then choose 7 (Advanced parameters)<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1 highlight: [12,25] \">\n cmag@lds10[~]&gt; ctmagcfg\n\n                Agent Configuration Utility\n\n1)      Agent-to-Server Port Number . . . : [7005]\n2)      Server-to-Agent Port Number . . . : [7008]\n        For items 3 and 4 do not use IP address\n3)      Primary Control-M\/Server Host . . : [ctlm9.dbi]\n4)      Authorized Control-M\/Server Hosts : [ctlm9.dbi]\n5)      Diagnostic Level. . . . . . . . . : [0]\n6)      Comm Trace. . . . . .(0-OFF|1-ON) : [0]\n7)      Advanced parameters\n\ns)      Save\nq)      Quit\n\nPlease enter your choice:7\n\n\n                Agent Configuration Utility - advanced menu\n\n1)      Days To Retain Log Files. . . . . : [1]\n2)      Daily Log File Enabled. . .  (Y|N): [Y]\n3)      Tracker Event Port. . . . . . . . : [29204]\n4)      Logical Agent Name. . . . . . . . : [lds10]\n5)      Persistent Connection . . . . . . : [N]\n6)      Allow Comm Init. . .  . . . . . . : [Y]\n7)      Foreign Language Support. . . . . : [LATIN-1]\n8)      Locale (LATIN-1 mode only) . . .. : [C]\n9)      Protocol Version. . . . . . . . . : [11]\n10)     AutoEdit Inline. . . . . . . (Y|N): [Y]\n11)     Listen to Network Interface . . . : [*ANY]\n12)     CTMS Address Mode . . . . . (IP|) : []\n13)     Timeout for Agent utilities . . . : [120]\n14)     TCP\/IP Timeout. . . . . . . . . . : [60]\n15)     Tracker Polling Interval. . . . . : [60]\n\nr)      Return to main menu\n<\/pre>\n<p>Ok ok ok, the Logical Agent Name seems to be not exactly the same as configured in CONTROL-M\/Server, try to change that: <\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1 highlight: [10] \">\nPlease enter your choice:4\n\nPlease enter the value:lds10.dbi\n\n                Agent Configuration Utility - advanced menu\n\n1)      Days To Retain Log Files. . . . . : [1]\n2)      Daily Log File Enabled. . .  (Y|N): [Y]\n3)      Tracker Event Port. . . . . . . . : [29204]\n4)      Logical Agent Name. . . . . . . . : [lds10.dbi]\n5)      Persistent Connection . . . . . . : [N]\n6)      Allow Comm Init. . .  . . . . . . : [Y]\n7)      Foreign Language Support. . . . . : [LATIN-1]\n8)      Locale (LATIN-1 mode only) . . .. : [C]\n9)      Protocol Version. . . . . . . . . : [11]\n10)     AutoEdit Inline. . . . . . . (Y|N): [Y]\n11)     Listen to Network Interface . . . : [*ANY]\n12)     CTMS Address Mode . . . . . (IP|) : []\n13)     Timeout for Agent utilities . . . : [120]\n14)     TCP\/IP Timeout. . . . . . . . . . : [60]\n15)     Tracker Polling Interval. . . . . : [60]\n<\/pre>\n<p>Return to menu and save the change!<\/p>\n<p>Retried the upgrade of this agent, and it has been completed successfully:<br \/>\n<img decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Blog-upg-agt-ok.png\" \/><\/p>\n<p>The agent is still Available in the CCM with the new version after upgrade:<br \/>\n<img decoding=\"async\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Blog-upg-agt-ok-v.png\" \/><\/p>\n<h1>Summary<\/h1>\n<h2>Issue description<\/h2>\n<p>Upgrading Control-M\/Agent running on Windows\/Unix using Agent Deployment fails with error: &#8220;Testing Communication with Control-M\/Server using new Control-M\/Agent binaries failed, Control-M\/Agent Upgrade aborted, please check Log and agent installation requirements&#8221;.<\/p>\n<h2>Cause<\/h2>\n<p>The agent&#8217;s Logical Agent Name parameter are not exactly the same as the Control-M\/Agent&#8217;s host name that appears in the Control-M CCM.<\/p>\n<h2>Solution<\/h2>\n<p>Set the Control-M\/Agent&#8217;s &#8220;Logical Agent Name&#8221; parameter to EXACTLY the same host name that appears in the Control-M Configuration Manager for this agent (follow above steps).<\/p>\n<p>I hope that this blog help you to solve quickly this issue, if you have any question or doubt don&#8217;t hesitate to comment, also you can share other issue encountered during upgrade \ud83d\ude09<\/p>\n","protected":false},"excerpt":{"rendered":"<p>At a customer, we are upgrading Control-M Agents running on Windows\/Unix from 9.0.00.400 to 9.0.19.200 using Agent Deployment, an upgrade of one agent fails with error talking about communication issue between Control-M\/server and Control-M agent:<\/p>\n","protected":false},"author":46,"featured_media":13463,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1256],"tags":[1193,717,219],"type_dbi":[],"class_list":["post-13462","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-control-m","tag-agent","tag-control-m","tag-upgrade"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Control-M - Agent Upgrade - Communication Issue - 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\/control-m-agent-upgrade-communication-issue\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Control-M - Agent Upgrade - Communication Issue\" \/>\n<meta property=\"og:description\" content=\"At a customer, we are upgrading Control-M Agents running on Windows\/Unix from 9.0.00.400 to 9.0.19.200 using Agent Deployment, an upgrade of one agent fails with error talking about communication issue between Control-M\/server and Control-M agent:\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2020-02-23T21:54:30+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Blog-upg-agt-nok.png\" \/>\n\t<meta property=\"og:image:width\" content=\"418\" \/>\n\t<meta property=\"og:image:height\" content=\"496\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"David Diab\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"David Diab\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 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\\\/control-m-agent-upgrade-communication-issue\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-agent-upgrade-communication-issue\\\/\"},\"author\":{\"name\":\"David Diab\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/deb907c3360cacdc6c7df54b4bac3c86\"},\"headline\":\"Control-M &#8211; Agent Upgrade &#8211; Communication Issue\",\"datePublished\":\"2020-02-23T21:54:30+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-agent-upgrade-communication-issue\\\/\"},\"wordCount\":341,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-agent-upgrade-communication-issue\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/Blog-upg-agt-nok.png\",\"keywords\":[\"agent\",\"Control-M\",\"Upgrade\"],\"articleSection\":[\"Control-M\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-agent-upgrade-communication-issue\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-agent-upgrade-communication-issue\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-agent-upgrade-communication-issue\\\/\",\"name\":\"Control-M - Agent Upgrade - Communication Issue - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-agent-upgrade-communication-issue\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-agent-upgrade-communication-issue\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/Blog-upg-agt-nok.png\",\"datePublished\":\"2020-02-23T21:54:30+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/deb907c3360cacdc6c7df54b4bac3c86\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-agent-upgrade-communication-issue\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-agent-upgrade-communication-issue\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-agent-upgrade-communication-issue\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/Blog-upg-agt-nok.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/sites\\\/2\\\/2022\\\/04\\\/Blog-upg-agt-nok.png\",\"width\":418,\"height\":496},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/control-m-agent-upgrade-communication-issue\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Control-M &#8211; Agent Upgrade &#8211; Communication Issue\"}]},{\"@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\\\/deb907c3360cacdc6c7df54b4bac3c86\",\"name\":\"David Diab\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/212b1b2e4650bad3116f644ab4fb4663786d94195d7685d0704c8426da088e60?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/212b1b2e4650bad3116f644ab4fb4663786d94195d7685d0704c8426da088e60?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/212b1b2e4650bad3116f644ab4fb4663786d94195d7685d0704c8426da088e60?s=96&d=mm&r=g\",\"caption\":\"David Diab\"},\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/david-diab\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Control-M - Agent Upgrade - Communication Issue - 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\/control-m-agent-upgrade-communication-issue\/","og_locale":"en_US","og_type":"article","og_title":"Control-M - Agent Upgrade - Communication Issue","og_description":"At a customer, we are upgrading Control-M Agents running on Windows\/Unix from 9.0.00.400 to 9.0.19.200 using Agent Deployment, an upgrade of one agent fails with error talking about communication issue between Control-M\/server and Control-M agent:","og_url":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/","og_site_name":"dbi Blog","article_published_time":"2020-02-23T21:54:30+00:00","og_image":[{"width":418,"height":496,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Blog-upg-agt-nok.png","type":"image\/png"}],"author":"David Diab","twitter_card":"summary_large_image","twitter_misc":{"Written by":"David Diab","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/"},"author":{"name":"David Diab","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/deb907c3360cacdc6c7df54b4bac3c86"},"headline":"Control-M &#8211; Agent Upgrade &#8211; Communication Issue","datePublished":"2020-02-23T21:54:30+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/"},"wordCount":341,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Blog-upg-agt-nok.png","keywords":["agent","Control-M","Upgrade"],"articleSection":["Control-M"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/","url":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/","name":"Control-M - Agent Upgrade - Communication Issue - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Blog-upg-agt-nok.png","datePublished":"2020-02-23T21:54:30+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/deb907c3360cacdc6c7df54b4bac3c86"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Blog-upg-agt-nok.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/Blog-upg-agt-nok.png","width":418,"height":496},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/control-m-agent-upgrade-communication-issue\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Control-M &#8211; Agent Upgrade &#8211; Communication Issue"}]},{"@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\/deb907c3360cacdc6c7df54b4bac3c86","name":"David Diab","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/212b1b2e4650bad3116f644ab4fb4663786d94195d7685d0704c8426da088e60?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/212b1b2e4650bad3116f644ab4fb4663786d94195d7685d0704c8426da088e60?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/212b1b2e4650bad3116f644ab4fb4663786d94195d7685d0704c8426da088e60?s=96&d=mm&r=g","caption":"David Diab"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/david-diab\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13462","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\/46"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=13462"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/13462\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/13463"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=13462"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=13462"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=13462"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=13462"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}