{"id":1823,"date":"2019-06-18T15:45:36","date_gmt":"2019-06-18T10:15:36","guid":{"rendered":"http:\/\/blog.tenthplanet.in\/?p=1823"},"modified":"2026-07-03T14:48:58","modified_gmt":"2026-07-03T09:18:58","slug":"clustering-and-loadbalancing-pba-with-standalone-postgres-and-apache-web-service","status":"publish","type":"post","link":"https:\/\/tenthplanet.in\/blogs\/clustering-and-loadbalancing-pba-with-standalone-postgres-and-apache-web-service\/","title":{"rendered":"Clustering and Loadbalancing PBA with standalone postgres and Apache web service"},"content":{"rendered":"

Clustering and Load balancing in Pentaho+ BA server<\/strong><\/p>\n

Prerequisite:<\/strong><\/p>\n

Multiple pentaho+ server
\nStanalone postgres
\nApache web server<\/p>\n

Initialize Postgres Database For Both the Pentaho Plus Servers<\/strong><\/p>\n

Change Default Passwords:<\/strong>
\nTo change the passwords, go to the pentaho\/server\/pentaho-server\/data\/postgresql directory and use any text editor to change the passwords in these SQL scripts:
\ncreate_quartz_postgresql.sql
\ncreate_jcr_postgresql.sql
\ncreate_repository_postgresql.sql
\npentaho_mart_postgresql.sql
\nRun SQL Scripts:
\nRun these scripts from the PSQL Console window in the pgAdminIII tool:
\n\\i <your filepath>\/create_quartz_postgresql.sql
\n\\i <your filepath>\/create_repository_postgresql.sql
\n\\i <your filepath>\/create_jcr_postgresql.sql
\n\\i <your filepath>\/pentaho_mart_postgresql.sql
\nCheck the postgres schema whether the components are present. (Quartz, Hibernate, JCR, Pentaho Operations Mart)<\/p>\n

Specify Data Connection Between Pentaho+ BA server and Tomcat web server
\nSet Up JNDI Connections for the Pentaho+ Server
\nStop the Tomcat and Pentaho Plus servers.
\nConsult your database documentation to determine the class name and connection string for your database.
\nEdit the \/tomcat\/webapps\/pentaho\/WEB-INF\/web.xml file.
\nAt the end of the <web-app> element, in the same part of the file where you see <!– insert additional resource-refs –>, add the following XML snippet:
\n<resource-ref>
\n<description>postgres<\/description>
\n<res-ref-name>jdbc\/postgres<\/res-ref-name>
\n<res-type>javax.sql.DataSource<\/res-type>
\n<res-auth>Container<\/res-auth>
\n<\/resource-ref>
\nSave and close the web.xml file.
\nEdit the \/tomcat\/conf\/context.xml with a text editor. Alternatively, you can modify the \/tomcat\/webapps\/pentaho\/META-INF\/context.xml file if you want this data connection to be available only to the Pentaho+ Server. Adding JNDI connections to the context.xml makes them available to all of the webapps deployed to this Tomcat instance.
\nAnywhere inside of the Context element, add the following XML snippet:
\n<Resource name=”jdbc\/postgres”
\nauth=”Container” type=”javax.sql.DataSource”
\nfactory=”org.apache.tomcat.jdbc.pool.DataSourceFactory”
\nmaxActive=”20″
\nmaxIdle=”5″
\nmaxWait=”10000″
\nusername=”postgres”
\npassword=”password”
\ndriverClassName=”org.postgresql.Driver”
\nurl=”jdbc:postgresql:\/\/ip:port\/myDataSource”
\n\/>
\nThe example above shows a simple PostgreSQL configuration. Replace the Resource name, username, password, driverClassName, and url parameters, or any relevant connection settings, to match your database connection information and the details you supplied in the web.xml file earlier.
\nSave and close the context.xml file.
\nDelete the pentaho.xml filed located in the \/tomcat\/conf\/catalina\/directory. The pentaho.xml is a cached copy of the context.xml file you modified. Since the cache is not usually configured to update frequently, you have to delete the pentaho.xml file and let Tomcat recreate it when it starts up. (If you could not find pentaho.xml in specified path, skip to next step. It is because of pentaho repository have not cached.)
\nStart the Tomcat and Pentaho+ servers. Tomcat can now properly connect to your data.<\/p>\n

Configure PostgreSQL Pentaho+ Repository Database<\/strong>
\n1. Set Up Quartz on PostgreSQL Pentaho+ Repository Database:<\/strong>
\nOpen the pentaho\/server\/pentaho-server\/pentaho-solutions\/system\/quartz\/quartz.properties file in any text editor.
\nLocate the #_replace_jobstore_properties section and set the org.quartz.jobStore.driverDelegateClass as shown here.
\norg.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.PostgreSQLDelegate
\nLocate the # Configure Datasources section and set the org.quartz.dataSource.myDS.jndiURL equal to Quartz. For example, on Tomcat, this setting should be:
\norg.quartz.dataSource.myDS.jndiURL = Quartz
\nSave the file and close the text editor.
\n2. Set Hibernate Settings for PostgreSQL:<\/strong>
\nOpen the hibernate-settings.xml file in a text editor. Find the <config-file> tags and confirm that it is configured for PostgreSQL.
\n<config-file>system\/hibernate\/postgresql.hibernate.cfg.xml<\/config-file>
\nSave the file if you made changes, then close the file.
\nOpen the postgresql.hibernate.cfg.xml file in a text editor.
\nMake sure that the password and port number match the ones you specified in your configuration. Make changes if necessary, then save and close the file.
\n3. Modify Jackrabbit Repository Information for PostgreSQL:<\/strong>
\nNavigate to the pentaho\/server\/pentaho-server\/pentaho-solutions\/system\/jackrabbit and open the repository.xml file with any text editor.
\nFollowing the table below, locate and verify or change the code so that the PostgreSQL lines are not commented out, but the MySQL, Oracle, and MS SQL Server lines are commented out.<\/p>\n\n\n\n<\/colgroup>\n\n\n\n\n\n\n\n\n\n
Item<\/td>\nCode Section<\/td>\n<\/tr>\n
Repository<\/td>\n<FileSystem class=”org.apache.jackrabbit.core.fs.db.DbFileSystem”><\/p>\n

<param name=”driver” value=”org.postgresql.Driver”\/><\/p>\n

<param name=”url” value=”jdbc:postgresql:\/\/ip:port\/jackrabbit”\/><\/p>\n

…<\/p>\n

<\/FileSystem><\/td>\n<\/tr>\n

DataStore<\/td>\n<DataStore class=”org.apache.jackrabbit.core.data.db.DbDataStore”><\/p>\n

<param name=”url” value=”jdbc:postgresql:\/\/ip:port\/jackrabbit”\/><\/p>\n

…<\/p>\n

<\/DataStore><\/td>\n<\/tr>\n

Workspaces<\/td>\n<FileSystem class=”org.apache.jackrabbit.core.fs.db.DbFileSystem”><\/p>\n

<param name=”driver” value=”org.postgresql.Driver”\/><\/p>\n

<param name=”url” value=”jdbc:postgresql:\/\/ip:port\/jackrabbit”\/><\/p>\n

…<\/p>\n

<\/FileSystem><\/td>\n<\/tr>\n

Persistence Manager (1)<\/td>\n<PersistenceManager class=”org.apache.jackrabbit.core.persistence.bundle.PostgreSQLPersistenceManager”><\/p>\n

<param name=”url” value=”jdbc:postgresql:\/\/ip:port\/jackrabbit”\/><\/p>\n

…<\/p>\n

<\/PersistenceManager><\/td>\n<\/tr>\n

Versioning<\/td>\n<FileSystem class=”org.apache.jackrabbit.core.fs.db.DbFileSystem”><\/p>\n

<param name=”driver” value=”org.postgresql.Driver”\/><\/p>\n

<param name=”url” value=”jdbc:postgresql:\/\/ip:port\/jackrabbit”\/><\/p>\n

…<\/p>\n

<\/FileSystem><\/td>\n<\/tr>\n

Persistence Manager (2)<\/td>\n<PersistenceManager class=”org.apache.jackrabbit.core.persistence.bundle.PostgreSQLPersistenceManager”><\/p>\n

<param name=”url” value=”jdbc:postgresql:\/\/ip:port\/jackrabbit”\/><\/p>\n

…<\/p>\n

<\/PersistenceManager><\/td>\n<\/tr>\n

Database Journal<\/td>\n<Journal class=”org.apache.jackrabbit.core.journal.DatabaseJournal”><\/p>\n

<param name=”revision” value=”${rep.home}\/revision.log”\/><\/p>\n

<param name=”url” value=”jdbc:postgresql:\/\/ip:port\/jackrabbit”\/><\/p>\n

<param name=”driver” value=”org.postgresql.Driver”\/><\/p>\n

<param name=”user” value=”jcr_user”\/><\/p>\n

<param name=”password” value=”password”\/><\/p>\n

<param name=”schema” value=”postgresql”\/><\/p>\n

<param name=”schemaObjectPrefix” value=”cl_j_”\/><\/p>\n

<param name=”janitorEnabled” value=”true”\/><\/p>\n

<param name=”janitorSleep” value=”86400″\/><\/p>\n

<param name=”janitorFirstRunHourOfDay” value=”3″\/><\/p>\n

<\/Journal><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Note: If you have a different port or different password, make sure that you change the password and port number in these examples to match the ones in your configuration.<\/p>\n

Perform Tomcat-Specific Connection Tasks<\/strong>
\n1. Download Driver and Apply to the Pentaho+ Server:
\nDownload a JDBC driver JAR from your database vendor or a third-party driver developer.
\nCopy the JDBC driver JAR you just downloaded to the pentaho\/server\/pentaho-server\/tomcat\/lib folder.
\nCopy the hsqldb-2.3.2.jar file to pentaho-server\/tomcat\/lib if you want to retain the sample provided by Pentaho Plus.
\n2. Modify JDBC Connection Information in the Tomcat Context XML File:
\nGo to the pentaho-server\/tomcat\/webapps\/pentaho\/META-INF directory and open the context.xml file with any file editor.
\nComment out the resource references that refer to databases other than PostgreSQL, such as MySQL, MS SQL Server, and Oracle. Then, add the following code to the file if it does not already exist. Be sure to adjust the port numbers and passwords to reflect your environment, if necessary.
\n<Resource name=”jdbc\/Hibernate” auth=”Container” type=”javax.sql.DataSource” factory=”org.apache.tomcat.jdbc.pool.DataSourceFactory” initialSize=”0″ maxActive=”20″ maxIdle=”10″ maxWait=”10000″ username=”hibuser” password=”password” driverClassName=”org.postgresql.Driver” url=”jdbc:postgresql:\/\/ip:port\/hibernate” validationQuery=”select 1″\/>
\n<Resource name=”jdbc\/Audit” auth=”Container” type=”javax.sql.DataSource” factory=”org.apache.tomcat.jdbc.pool.DataSourceFactory” initialSize=”0″ maxActive=”20″ maxIdle=”10″ maxWait=”10000″ username=”hibuser” password=”password” driverClassName=”org.postgresql.Driver” url=”jdbc:postgresql:\/\/ip:port\/hibernate” validationQuery=”select 1″\/>
\n<Resource name=”jdbc\/Quartz” auth=”Container” type=”javax.sql.DataSource” factory=”org.apache.tomcat.jdbc.pool.DataSourceFactory” initialSize=”0″ maxActive=”20″ maxIdle=”10″ maxWait=”10000″ username=”pentaho_user” password=”password” driverClassName=”org.postgresql.Driver” url=”jdbc:postgresql:\/\/ip:port\/quartz” validationQuery=”select 1″\/>
\n<Resource name=”jdbc\/pentaho_operations_mart” auth=”Container” type=”javax.sql.DataSource” factory=”org.apache.tomcat.jdbc.pool.DataSourceFactory” initialSize=”0″ maxActive=”20″ maxIdle=”10″ maxWait=”10000″ username=”hibuser” password=”password” driverClassName=”org.postgresql.Driver” url=”jdbc:postgresql:\/\/ip:port\/pentaho_operations_mart” validationQuery=”select 1″\/>
\n<Resource name=”jdbc\/PDI_Operations_Mart” auth=”Container” type=”javax.sql.DataSource” factory=”org.apache.tomcat.jdbc.pool.DataSourceFactory” initialSize=”0″ maxActive=”20″ maxIdle=”10″ maxWait=”10000″ username=”hibuser” password=”password” driverClassName=”org.postgresql.Driver” url=”jdbc:postgresql:\/\/ip:port\/hibernate” validationQuery=”select 1″\/>
\nMake sure that the validationQuery variable for your database is set as follows: validationQuery=”select 1″
\nSave the context.xml file, then close it.
\nClear the tomcat\/work and tomcat\/temp directories.
\nStart the tomcat and pentaho servers.<\/p>\n

Initialize and Configure Pentaho Plus Repository<\/strong>
\n1)Clean Up Pentaho Plus Repository:
\nAfter you have initialized and configured your repository, you should clean up these files by following these steps.
\nLocate the …pentaho-server\/tomcat directory and remove all files and folders from the temp folder.
\nLocate the …pentaho-server\/tomcat directory and remove all files and folders from the work folder.
\nLocate the …pentaho-server\/pentaho-solutions\/system\/jackrabbit\/repository directory and remove all files and folders from the final repository folder.
\nLocate the …pentaho-server\/pentaho-solutions\/system\/jackrabbit\/repository directory and remove all files and folders from the workspaces folder.
\nYou now have a configured repository and are ready to move to the next step for clustering.
\nConfigure Jackrabbit Journal
\n1. Locate the repository.xml file in the …\/pentaho-server\/pentaho-solutions\/system\/jackrabbit directory and open it with any text editor.
\n2. Scroll to the bottom of the file and replace the section that begins with <!– Run with a cluster journal –> with the correct code for your type of database repository.
\nChange in the 1st pentaho server \u2013 Node1 \/Server 1
\n<!–
\nRun with a cluster journal
\n–>
\n<Cluster id=”node1″>
\n<Journal class=”org.apache.jackrabbit.core.journal.DatabaseJournal”>
\n<param name=”revision” value=”${rep.home}\/revision.log”\/>
\n<param name=”url” value=”jdbc:postgresql:\/\/ip:port\/jackrabbit”\/>
\n<param name=”driver” value=”org.postgresql.Driver”\/>
\n<param name=”user” value=”jcr_user”\/>
\n<param name=”password” value=”password”\/>
\n<param name=”databaseType” value=”postgresql”\/>
\n<param name=”janitorEnabled” value=”true”\/>
\n<param name=”janitorSleep” value=”86400″\/>
\n<param name=”janitorFirstRunHourOfDay” value=”3″\/>
\n<\/Journal>
\n<\/Cluster>
\nChange in the 2nd pentaho server \u2013 Node 2 \/Server 2
\n<!–
\nRun with a cluster journal
\n–>
\n<Cluster id=”node2″>
\n<Journal class=”org.apache.jackrabbit.core.journal.DatabaseJournal”>
\n<param name=”revision” value=”${rep.home}\/revision.log”\/>
\n<param name=”url” value=”jdbc:postgresql:\/\/ip:port\/jackrabbit”\/>
\n<param name=”driver” value=”org.postgresql.Driver”\/>
\n<param name=”user” value=”jcr_user”\/>
\n<param name=”password” value=”password”\/>
\n<param name=”databaseType” value=”postgresql”\/>
\n<param name=”janitorEnabled” value=”true”\/>
\n<param name=”janitorSleep” value=”86400″\/>
\n<param name=”janitorFirstRunHourOfDay” value=”3″\/>
\n<\/Journal>
\n<\/Cluster><\/p>\n

3. Save and close the file. Jackrabbit journaling is now set up for your cluster. Next, you need to cluster the quartz tables to avoid duplicate scheduling on each node.<\/p>\n

Configure Quartz<\/strong>
\n1. Locate the quartz.properties file in the …\/pentaho-server\/pentaho-solutions\/system\/quartz directory and open it with any text editor.
\n2. Find the org.quartz.scheduler.instanceId = INSTANCE_ID line and change INSTANCE_ID to AUTO.
\norg.quartz.scheduler.instanceId = AUTO
\n3. Find the #_replace_jobstore_properties section and change the default value of org.quartz.jobStore.isClustered to true as shown.
\n#_replace_jobstore_properties
\norg.quartz.jobStore.misfireThreshold = 60000
\norg.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.PostgreSQLDelegate
\norg.quartz.jobStore.useProperties = false
\norg.quartz.jobStore.dataSource = myDS
\norg.quartz.jobStore.tablePrefix = QRTZ5_
\norg.quartz.jobStore.isClustered = true
\n4. Add this line just after the org.quartz.jobStore.isClustered = true line.
\norg.quartz.jobStore.clusterCheckinInterval = 20000
\n5. Save the Editor. Quartz is now configured for your cluster.
\n6. Restart the postgresql, tomcat and pentaho server. And the clustering of two servers is working properly.<\/p>\n

Tomcat Configuration for Load Balancer in High Availability<\/strong>
\n1. Shut down the Tomcat server on each node in the cluster.
\n2. Open the tomcat\/conf\/server.xml file in a text editor.
\n3. Locate the following line <Engine name=”Catalina” defaultHost=”localhost”>.
\n4. The jvmRoute value will need to be unique for each node. This value will map to the
\nBalancerMember setup in the following section when configuring Apache. Add the
\njvmRoute attribute like this:
\nChange in Pentaho Server 1
\n<Engine name=”Catalina” defaultHost=”localhost” jvmRoute=”server1″><\/p>\n

Change in Pentaho Server 2
\n<Engine name=”Catalina” defaultHost=”localhost” jvmRoute=”server2″>
\n5. To close connections so they do not become orphaned and cause errors, locate the
\nfollowing line:
\n<Connector URIEncoding=”UTF-8″ port=”8009″ protocol=”AJP\/1.3″
\nredirectPort=”8443″ \/>
\nChange it to:
\n<Connector port=”8009″ protocol=”AJP\/1.3″ redirectPort=”8443″
\nconnectionTimeout=”10000″ keepAliveTimeout=”10000″ \/>
\n6. Edit the pentaho-solutions\/system\/server.properties and change the fully-qualified-server-url param-value to the load balancer\u2019s URL.
\nfully-qualified-server-url=http:\/\/ip:port\/pentaho\/
\n7. Start the Tomcat service back up after configuring this file.
\n8. Repeat this process throughout all nodes within the cluster.
\nApache Configuration
\nLocate and edit the Apache configuration file. For Debian-based distributions, this is located by default in \/etc\/apache2\/sites-available\/000-default.conf.
\nWithin this configuration file, you will need to edit the existing (or add a new) VirtualHost directive. Make sure to reflect the BalancerMember hostname with your Pentaho cluster nodes:
\n<VirtualHost *:80>
\n# The ServerName directive sets the request scheme, hostname and port that
\n# the server uses to identify itself. This is used when creating
\n# redirection URLs. In the context of virtual hosts, the ServerName
\n# specifies what hostname must appear in the request’s Host: header to
\n# match this virtual host. For the default virtual host (this file) this
\n# value is not decisive as it is used as a last resort host regardless.
\n# However, you must set it for any further virtual host explicitly.
\nServerName master-server
\nServerAdmin webmaster@localhost
\nDocumentRoot \/var\/www\/html
\n# Available loglevels: trace8, …, trace1, debug, info, notice, warn,
\n# error, crit, alert, emerg.
\n# It is also possible to configure the loglevel for particular
\n# modules, e.g.
\n#LogLevel info ssl:warn
\nErrorLog ${APACHE_LOG_DIR}\/error.log
\nCustomLog ${APACHE_LOG_DIR}\/access.log combined
\n# For most configuration files from conf-available\/, which are
\n# enabled or disabled at a global level, it is possible to
\n# include a line for only one particular virtual host. For example the
\n# following line enables the CGI configuration for this host only
\n# after it has been globally disabled with “a2disconf”.
\n#Include conf-available\/serve-cgi-bin.conf
\n<Location “\/pentaho”>
\nProxyPass balancer:\/\/reportingcluster
\nProxyPassReverseCookiePath \/ \/pentaho
\n<\/Location>
\n<Location “\/pentaho-style”>
\nProxyPass balancer:\/\/reportingcluster-style
\nProxyPassReverseCookiePath \/ \/pentaho
\n<\/Location>
\n<\/VirtualHost>
\nProxyPreserveHost On
\nProxyPass \/pentaho balancer:\/\/reportingcluster
\nProxyPassReverseCookiePath \/ \/pentaho
\nProxyPass \/pentaho-style balancer:\/\/reportingcluster-style
\nProxyPassReverseCookiePath \/ \/pentaho
\nTimeout 600
\nProxyTimeout 600
\n<Proxy balancer:\/\/reportingcluster>
\nProxySet stickysession=JSESSIONID timeout=360 scolonpathdelim=On failonstatus=502,503
\nBalancerMember http:\/\/ip:port\/pentaho connectiontimeout=10 loadfactor=10 route=server1 max=20 ttl=120 retry=1
\nBalancerMember http:\/\/ip:port\/pentaho connectiontimeout=10 loadfactor=10 route=server2 max=20 ttl=120 retry=1
\nBalancerMember http:\/\/ip:port\/pentaho route=server3 retry=1 connectiontimeout=10 loadfactor=10 max=20 ttl=120 status=+H
\nProxySet lbmethod=bytraffic
\n<\/Proxy>
\n<Proxy balancer:\/\/reportingcluster-style>
\nProxySet stickysession=JSESSIONID timeout=360 scolonpathdelim=On failonstatus=502,503
\nBalancerMember http:\/\/ip:port\/pentaho-sytle connectiontimeout=10 loadfactor=10 route=server1 max=20 ttl=120 retry=1
\nBalancerMember http:\/\/ip:port\/pentaho-sytle connectiontimeout=10 loadfactor=10 route=server2 max=20 ttl=120 retry=1
\nBalancerMember http:\/\/ip:port\/pentaho-sytle route=server3 retry=1 connectiontimeout=10 loadfactor=10 max=20 ttl=120 status=+H
\nProxySet lbmethod=bytraffic
\n<\/Proxy>
\n# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
\nAfter adding the above code, save the file and restart the Apache service.
\nYou should now be able to browse to your load balancer and see the Pentaho User
\nConsole, for example:<\/p>\n

Screenshot of Load Balancing:<\/strong><\/p>\n

\"\"
\n\"\"<\/p>\n","protected":false},"excerpt":{"rendered":"

Clustering and Loadbalancing PBA with standalone postgres and Apache web service<\/p>\n","protected":false},"author":23,"featured_media":1870,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[424],"tags":[527,528,447,529],"class_list":["post-1823","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pentaho","tag-high-availability-and-pentaho","tag-loadbalancing","tag-pentaho-clustering","tag-pentaho-load-balancing"],"_links":{"self":[{"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/posts\/1823","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/users\/23"}],"replies":[{"embeddable":true,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/comments?post=1823"}],"version-history":[{"count":1,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/posts\/1823\/revisions"}],"predecessor-version":[{"id":11436,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/posts\/1823\/revisions\/11436"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/media\/1870"}],"wp:attachment":[{"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/media?parent=1823"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/categories?post=1823"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tenthplanet.in\/blogs\/wp-json\/wp\/v2\/tags?post=1823"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}