{"id":16801,"date":"2021-11-15T08:11:34","date_gmt":"2021-11-15T07:11:34","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/"},"modified":"2021-11-15T08:11:34","modified_gmt":"2021-11-15T07:11:34","slug":"ansible-uri-module-and-weblogic-rest-api","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/","title":{"rendered":"Ansible URI module and WebLogic REST API"},"content":{"rendered":"<p>I recently experienced REST API from WebLogic Server as I was trying to find a way to make configuration changes and metrics gatherings multi-servers and even multi-domains.<br \/>\nwlst can be used to achieve that, but from my point of view it has a big drawback: It is slow to initiate and connect to server.<\/p>\n<h3>Build Query URL<\/h3>\n<p>The difficult part of REST is to find the right URL you have to access via GET, POST or DELETE (&#8230;) to achieve your goal.<\/p>\n<p>My first need was to update the Maximum Capacity of a JDBC DataSource.<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">curl \n-H X-Requested-By:MyClient \n-H Accept:application\/json \n-u ${WL_USER}:${WL_ADMPWD} \n-X GET https:\/\/hostname:port\/management\/weblogic\/latest\/edit\/JDBCSystemResources\/MyJDBCDataSource\/JDBCResource\/JDBCConnectionPoolParams<\/pre>\n<p>I am using two headers:<\/p>\n<ul>\n<li>X-Requested-By: Mandatory field for security reason (Cross Site Request Forgery)<\/li>\n<li>Accept: Format of the result<\/li>\n<\/ul>\n<p>Result example:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">{\n    \"links\": [\n        {\n            \"rel\": \"parent\",\n            \"href\": \"http:\/\/vm01:7001\/management\/weblogic\/latest\/edit\/JDBCSystemResources\/MyDBDatasource\/JDBCResource\"\n        },\n        {\n            \"rel\": \"self\",\n            \"href\": \"http:\/\/vm01:7001\/management\/weblogic\/latest\/edit\/JDBCSystemResources\/MyDBDatasource\/JDBCResource\/JDBCConnectionPoolParams\"\n        },\n        {\n            \"rel\": \"canonical\",\n            \"href\": \"http:\/\/vm01:7001\/management\/weblogic\/latest\/edit\/JDBCSystemResources\/MyDBDatasource\/JDBCResource\/JDBCConnectionPoolParams\"\n        }\n    ],\n    \"identity\": [\n        \"JDBCSystemResources\",\n        \"MyDBDatasource\",\n        \"JDBCResource\",\n        \"JDBCConnectionPoolParams\"\n    ],\n    \"inactiveConnectionTimeoutSeconds\": 0,\n    \"testConnectionsOnReserve\": false,\n    \"wrapTypes\": true,\n    \"fatalErrorCodes\": null,\n    \"initialCapacity\": 1,\n    \"pinnedToThread\": false,\n    \"highestNumWaiters\": 2147483647,\n    \"statementTimeout\": -1,\n    \"countOfRefreshFailuresTillDisable\": 2,\n    \"connectionHarvestMaxCount\": 1,\n    \"profileHarvestFrequencySeconds\": 300,\n    \"profileType\": 0,\n    \"loginDelaySeconds\": 0,\n    \"minCapacity\": 10,\n    \"identityBasedConnectionPoolingEnabled\": false,\n    \"connectionLabelingCallback\": null,\n    \"countOfTestFailuresTillFlush\": 2,\n    \"secondsToTrustAnIdlePoolConnection\": 10,\n    \"shrinkFrequencySeconds\": 900,\n    \"wrapJdbc\": true,\n    \"connectionHarvestTriggerCount\": -1,\n    \"credentialMappingEnabled\": false,\n    \"connectionReserveTimeoutSeconds\": 10,\n    \"removeInfectedConnections\": true,\n    \"statementCacheSize\": 10,\n    \"testTableName\": \"SQL SELECT 1 FROM DUAL\",\n    \"JDBCXADebugLevel\": 10,\n    \"maxCapacity\": 100,\n    \"ignoreInUseConnectionsEnabled\": true,\n    \"connectionCreationRetryFrequencySeconds\": 0,\n    \"driverInterceptor\": null,\n    \"testFrequencySeconds\": 120,\n    \"profileConnectionLeakTimeoutSeconds\": 0,\n    \"statementCacheType\": \"LRU\",\n    \"initSql\": null\n}\n<\/pre>\n<p>As you can see the result is long and verbose, so to limit output to the interesting field (MaxCapacity), I modify the URL as follow:<br \/>\nhttps:\/\/serverhostname:port\/management\/weblogic\/latest\/edit\/JDBCSystemResources\/MyJDBCDataSource\/JDBCResource\/JDBCConnectionPoolParams?fields=maxCapacity&#038;links=no<br \/>\nThen, new result is:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">{\"maxCapacity\": 100}<\/pre>\n<h3>Settings Modification<\/h3>\n<p>Modify the parameter with a simple curl:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">curl\n-H X-Requested-By:MyClient \n-H Accept:application\/json \n-H Content-Type:application\/json \n-d \"{ maxCapacity: 50}\" \n-u ${WL_USER}:${WL_ADMPWD} \n-X POST https:\/\/hostname:port\/management\/weblogic\/latest\/JDBCSystemResources\/MyJDBCDataSource\/JDBCResource\/JDBCConnectionPoolParams<\/pre>\n<p>Line 5 is the modified settings name (maxCapacity) with the new value (50).<br \/>\nAn advantage of REST, as well as a &#8220;risk&#8221;, is that you don&#8217;t need to &#8220;lock and edit&#8221; configuration as we are used to with the web console.<\/p>\n<p>As I am lately doing lots of Ansible coding, I told myself &#8220;Why not trying Ansible for this ?&#8221;. Luckily, a module named uri perfectly fit.<\/p>\n<h3>Ansible URI Module<\/h3>\n<p>As as first attempts, I want to proceed as follow keeping <a href=\"https:\/\/en.wikipedia.org\/wiki\/Idempotence\">idempotency<\/a> in focus:<\/p>\n<ol>\n<li>Call URL to check current value<\/li>\n<li>Display it<\/li>\n<li>Update if different<\/li>\n<\/ol>\n<p>Playbook will look like this:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">---\n  - name: WebLogic REST playbook\n    hosts: all\n    gather_facts: no\n    tasks:\n\n      - name: 1. Check maxCapacity value\n        uri:\n          url: https:\/\/{{ inventory_hostname }}:7002\/management\/weblogic\/latest\/edit\/JDBCSystemResources\/MyJDBCDataSource\/JDBCResource\/JDBCConnectionPoolParams?fields=maxCapacity\n          return_content: yes\n          user: \"{{ weblogic_adm_user }}\"\n          password: \"{{ weblogic_adm_pwd }}\"\n          headers:\n            Accept: application\/json\n            X-Requested-By: MyAnsibleClient\n        register: getResult\n\n      - name: 2. Display Content Result\n        ansible.builtin.debug:\n          var: getResult.json.maxCapacity\n\n      - name: 3. Set maxCapacity value if changed\n        when: getResult.json.maxCapacity != newMaxCapacity\n        uri:\n          url: https:\/\/{{ inventory_hostname }}:7002\/management\/weblogic\/latest\/edit\/JDBCSystemResources\/MyJDBCDataSource\/JDBCResource\/JDBCConnectionPoolParams\n          user: \"{{ weblogic_adm_user }}\"\n          password: \"{{ weblogic_adm_pwd }}\"\n          method: POST\n          body_format: json\n          body: \n            maxCapacity: \"{{ newMaxCapacity }}\"\n          headers:\n            Content-Type: application\/json\n            Accept: application\/json\n            X-Requested-By: MyAnsibleClient\n        when: newMaxCapacity is defined\n<\/pre>\n<p>Line 9: The requested URL<br \/>\nLine 10: return_content is the option to return result of the requested URL. register option will store it (line 13).<br \/>\n<strong>Line 20<\/strong>: This is the line which will modify maxCapacity only if it is different from current value.<br \/>\nLine 25: I have to specify the HTTP method and the format of the text body (line 26). URI module will do the conversion.<br \/>\nLine 29 to 32: HTTP headers definitions<br \/>\nThen, we need to run and see how this behave:<br \/>\nRESULT<\/p>\n<p>Let&#8217;s try also with &#8211;check option:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">PLAY [WebLogic REST playbook] *********************************************************************************************************************************************************************\n\nTASK [Check maxCapacity value] ********************************************************************************************************************************************************************\nskipping: [vm1]\n\nTASK [Display Content Result] *********************************************************************************************************************************************************************\nok: [vm1] =&gt; {\n    \"changed\": false,\n    \"getResult.json.maxCapacity\": \"VARIABLE IS NOT DEFINED!\"\n}\n\nTASK [Set maxCapacity value] **********************************************************************************************************************************************************************\nfatal: [vm1]: FAILED! =&gt; {\"msg\": \"The conditional check 'getResult.json.maxCapacity != newMaxCapacity' failed. The error was: error while evaluating conditional (getResult.json.maxCapacity|int != {{ newMaxCapacity|int }}): 'dict object' has no attribute 'json'nnThe error appears to be in '\/home\/spiesser\/updateJDBCMaxCapacity.yml': line 23, column 9, but maynbe elsewhere in the file depending on the exact syntax problem.nnThe offending line appears to be:nnn      - name: Set maxCapacity valuen        ^ heren\"}\n\nPLAY RECAP ****************************************************************************************************************************************************************************************\nvm1                  : ok=1    changed=0    unreachable=0    failed=1    skipped=1    rescued=0    ignored=0   \n<\/pre>\n<p>As you can see, there are two errors. Why is that ? Because URI request of step 1 is skipped and a result, result is not populated. Then, step 2 fails to display unset variable and step 3 when condition evaluation fails as well.<br \/>\nTo avoid that, I need to force step 1 to be run even when &#8211;check option is used. To achieve that, I need to add &#8220;check_mode: no&#8221; to step 1.<br \/>\nThe output looks like that:<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">PLAY [WebLogic REST playbook] *********************************************************************************************************************************************************************\n\nTASK [Check maxCapacity value] ********************************************************************************************************************************************************************\nok: [vm1]\n\nTASK [Display Content Result] *********************************************************************************************************************************************************************\nok: [vm1] =&gt; {\n    \"changed\": false,\n    \"getResult.json.maxCapacity\": \"50\"\n}\n\nTASK [Set maxCapacity value] **********************************************************************************************************************************************************************\nskipping: [vm1]\n\nPLAY RECAP ****************************************************************************************************************************************************************************************\nvm1                  : ok=2    changed=0    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   \n<\/pre>\n<p>I can also display current value (step 2) only when running in check mode. then, I need to add a condition to the corresponding task<\/p>\n<pre class=\"brush: bash; gutter: true; first-line: 1\">when: ansible_check_mode<\/pre>\n<h3>Conclusion<\/h3>\n<p>It might look a bit overkill to use Ansible for that, but it makes REST API request easy to write and idempotency comes natively with Ansible.<br \/>\nAlso, using REST remove the need of creating wlst scripts and thus managing these with Ansible templates.<br \/>\nRegarding performances, Ansible playbook takes 3 seconds whereas wlst takes 6 seconds (at second run, once libraries are cached).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>How to use WebLogic REST API with Ansible URI module.<\/p>\n","protected":false},"author":40,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"neve_meta_sidebar":"","neve_meta_container":"","neve_meta_enable_content_width":"","neve_meta_content_width":0,"neve_meta_title_alignment":"","neve_meta_author_avatar":"","neve_post_elements_order":"","neve_meta_disable_header":"","neve_meta_disable_footer":"","neve_meta_disable_title":"","neve_meta_reading_time":"","_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[1321,1320],"tags":[1521,647],"class_list":["post-16801","post","type-post","status-publish","format-standard","category-ansible","category-devops","tag-rest","tag-weblogic"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.8 (Yoast SEO v28.8) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Ansible URI module and WebLogic REST API - dbi services 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\/ansible-uri-module-and-weblogic-rest-api\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Ansible URI module and WebLogic REST API\" \/>\n<meta property=\"og:description\" content=\"How to use WebLogic REST API with Ansible URI module.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi services Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/dbiservices\/\" \/>\n<meta property=\"article:published_time\" content=\"2021-11-15T07:11:34+00:00\" \/>\n<meta name=\"author\" content=\"Middleware Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:site\" content=\"@dbiservices\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Middleware Team\" \/>\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\\\/ansible-uri-module-and-weblogic-rest-api\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/ansible-uri-module-and-weblogic-rest-api\\\/\"},\"author\":{\"name\":\"Middleware Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8a0bfec3c3bd1f27d3d452eaa592bfb8\"},\"headline\":\"Ansible URI module and WebLogic REST API\",\"datePublished\":\"2021-11-15T07:11:34+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/ansible-uri-module-and-weblogic-rest-api\\\/\"},\"wordCount\":519,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"keywords\":[\"rest\",\"WebLogic\"],\"articleSection\":[\"Ansible\",\"DevOps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/ansible-uri-module-and-weblogic-rest-api\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/ansible-uri-module-and-weblogic-rest-api\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/ansible-uri-module-and-weblogic-rest-api\\\/\",\"name\":\"Ansible URI module and WebLogic REST API - dbi services Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2021-11-15T07:11:34+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/ansible-uri-module-and-weblogic-rest-api\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/ansible-uri-module-and-weblogic-rest-api\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/ansible-uri-module-and-weblogic-rest-api\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Ansible URI module and WebLogic REST API\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi services Blog\",\"description\":\"#BeSharing\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\"},\"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\":\"Organization\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/#organization\",\"name\":\"dbi services\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"contentUrl\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/dbi-services-logo.png\",\"width\":512,\"height\":512,\"caption\":\"dbi services\"},\"image\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/dbiservices\\\/\",\"https:\\\/\\\/x.com\\\/dbiservices\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/dbi-services\\\/\",\"https:\\\/\\\/www.youtube.com\\\/user\\\/dbiservices\"],\"description\":\"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.\",\"email\":\"info@dbi-services.com\",\"telephone\":\"+41 32 422 96 00\",\"legalName\":\"dbi services SA\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/8a0bfec3c3bd1f27d3d452eaa592bfb8\",\"name\":\"Middleware Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g\",\"caption\":\"Middleware Team\"},\"description\":\"Posts published under the Middleware Team account are collective contributions by the dbi services middleware and enterprise content management consultants. The practice covers ECM platforms such as OpenText Documentum, Alfresco, and M-Files, as well as application servers and integration technologies including WebLogic, JBoss, Tomcat, and the Elastic Stack, from architecture and deployment to operations under service level agreements.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/middleware-team\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Ansible URI module and WebLogic REST API - dbi services 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\/ansible-uri-module-and-weblogic-rest-api\/","og_locale":"en_US","og_type":"article","og_title":"Ansible URI module and WebLogic REST API","og_description":"How to use WebLogic REST API with Ansible URI module.","og_url":"https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/","og_site_name":"dbi services Blog","article_publisher":"https:\/\/www.facebook.com\/dbiservices\/","article_published_time":"2021-11-15T07:11:34+00:00","author":"Middleware Team","twitter_card":"summary_large_image","twitter_creator":"@dbiservices","twitter_site":"@dbiservices","twitter_misc":{"Written by":"Middleware Team","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/"},"author":{"name":"Middleware Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8a0bfec3c3bd1f27d3d452eaa592bfb8"},"headline":"Ansible URI module and WebLogic REST API","datePublished":"2021-11-15T07:11:34+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/"},"wordCount":519,"commentCount":0,"publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"keywords":["rest","WebLogic"],"articleSection":["Ansible","DevOps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/","url":"https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/","name":"Ansible URI module and WebLogic REST API - dbi services Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2021-11-15T07:11:34+00:00","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/ansible-uri-module-and-weblogic-rest-api\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Ansible URI module and WebLogic REST API"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi services Blog","description":"#BeSharing","publisher":{"@id":"https:\/\/www.dbi-services.com\/#organization"},"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":"Organization","@id":"https:\/\/www.dbi-services.com\/#organization","name":"dbi services","url":"https:\/\/www.dbi-services.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/2026\/09\/dbi-services-logo.png","width":512,"height":512,"caption":"dbi services"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/dbiservices\/","https:\/\/x.com\/dbiservices","https:\/\/www.linkedin.com\/company\/dbi-services\/","https:\/\/www.youtube.com\/user\/dbiservices"],"description":"Swiss IT consulting and services company specialized in efficient data infrastructures and platforms: databases, application servers, cloud, DevOps, digitalization, analytics, data quality and monitoring. Headquartered in Del\u00e9mont with offices in Nyon, Basel, Bern and Zurich.","email":"info@dbi-services.com","telephone":"+41 32 422 96 00","legalName":"dbi services SA"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/8a0bfec3c3bd1f27d3d452eaa592bfb8","name":"Middleware Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ddcae7ba0f9d1a0e7ae707f0e689e4a9c95bb48ec49c8e6d9cc86d43f4121cb6?s=96&d=mm&r=g","caption":"Middleware Team"},"description":"Posts published under the Middleware Team account are collective contributions by the dbi services middleware and enterprise content management consultants. The practice covers ECM platforms such as OpenText Documentum, Alfresco, and M-Files, as well as application servers and integration technologies including WebLogic, JBoss, Tomcat, and the Elastic Stack, from architecture and deployment to operations under service level agreements.","url":"https:\/\/www.dbi-services.com\/blog\/author\/middleware-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/16801","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\/40"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=16801"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/16801\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=16801"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=16801"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=16801"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}