Overview
A cache is a repository of temporary files that a device uses to speed up the user experience. There's a cache in a variety of places, on all sorts of devices, and while every cache holds different information, they're all used for the same purpose. There are occasions where these caches need to be cleared to address a certain issue or to optimize performance.
While there are many types of caches, there are a few specific ones that Jive uses. This article guides users in clearing different types of caches used in Jive.
Process
Application Cache
- Navigate to the Jive Admin Console.
-
From the homepage, click on your avatar on the top right corner of the page.
-
Click on Admin Console
-
Scroll down to the bottom of the page and click Advanced Settings button found on the lower left corner.
-
- Now that you are on the Admin page, navigate to System > Settings > Caches.
- Tick the checkboxes corresponding to the cache that you need to delete. You can also tick the checkbox on top of the column to select all cache options to clear.
- Scroll down to the bottom of the Caches page and click Clear Selected.
- The following confirmation message appears: Cache(s) cleared successfully.
Rendered Content Cache
- Follow the same process as clearing the Application caches but clear only the content caches (anything with the word content listed).
-
Run the following query on the database:
UPDATE jiveRenderedContentVersion SET version = version + 1;
- Navigate back to Admin Console > System > Settings > Cache, and clear the Filtered Values cache.
If you have properly updated the Jive URL system property and restarted your site but you are still seeing that image links in content are referencing your previous URL, then you may need to implement the following workaround:
- From the Admin Console page, navigate to Spaces > Settings > Filters and Macros.
- Click the Save button on the page.
Just the act of saving that page causes the rendered version of those documents to re-render using the new Jive URL.
The jiveRenderedContent
table contains an additional cache for content published through the RTE. It's not uncommon during migrations and other various tasks to see this table become out of sync with the version sitting in the editor. As a result, it's common practice to clear this cache by using the "Save Settings" button under Admin Console > Spaces > Settings > Filters and Macros.
Please note, this only works if the images were uploaded directly in the content through the RTE. This workaround does not address issues with widgets - If you have manually created HTML widgets that reference the old URL then you will need to manually update these widgets.
Akamai Cache
- Log in to Akamai Control Page.
- Choose an account from the Choose an Account dropdown menu.
- JiveCloud jiveon.com is under Jive Software, Inc.
- Click Publish on the top menu bar and select Content Control Utility.
-
If presented with the following screen, select Web Application Accelerator and click continue.
-
You should now be on the Content Control Utility page. From here, you now have several options for what you want to flush. However, it is important we flush the correct site/asset.
Note: In order to validate we're flushing the correct site we need to dig up the CP Code, this only applies when flushing an entire site (URL Specific flush obviously includes the URL). Follow through the article Locating Akamai CP Code for guidelines in obtaining the CP code.
- Flush the Akamai Cache.
- Flushing Individual Asset(s) / URL(s)
- Enter the Full URL path to that assets you want to flush in the URLs/ARLs entered below box.
- Click the Start Refreshing Content button on the bottom of the page.
- Accept any warnings if you trust these instructions.
- Flush ALL content for an entire site / CP Code
Warning! If doing this for JiveCloud / jiveon.com, all sites are under a single account / CP code. This will flush content for ALL jivecloud sites. (This requires CCR approval)
- Select the option [Use with Caution!] Refresh ALL URLs/ARLs Associated with Specific CP Codes>>.
- Choose ONLY the site which matches your CP Code.
- Click the Start Refreshing Content button on the bottom of the page.
- Accept any warnings if you trust these instructions.
- Flush by directory or file extension:
Warning! If doing this for JiveCloud / jiveon.com, all sites are under a single account / CP code. This will flush content for ALL jivecloud sites. (This requires CCR approval)
- Select the option Refresh by Directory & File Extension from the top of the Content Control Utility page.
- Enter a name for the request.
- Enter the directory or extensions you want to flush
- Click Next.
- Review and confirm your request by clicking on submit.
- Flush Akamai cache for ALL combined .js resources for a jivecloud site:
- Determine version specific resource directory by using a web debugger. This will be the same for all current jivecloud sites (currently this is 7.0.0.184c35b for Samurai).
- This means the URL for the combined JS resources are
/7.0.0.184c35b/resources/scripts/gen/<combined>.js
- From the list of generated .js files obtained in the previous step, create a list of the full URL path to those assets:
[root@thunderXXXX sites]# for n in `cd /usr/local/jive/applications/sbs/home/www/resources/scripts/gen/; ls *.js`; do echo
https://mysite.jiveon.com/7.0.0.184c35b/resources/scripts/gen/$n;
done
https://mysite.jiveon.com/7.0.0.184c35b/resources/scripts/gen/02961ed2dca78cc83399a0407133aa29.js
https://mysite.jiveon.com/7.0.0.184c35b/resources/scripts/gen/433ed4ab0eb177e79934e48ebfdb4b80.js
https://mysite.jiveon.com/7.0.0.184c35b/resources/scripts/gen/80ab7c24756b10989e41b2f551e311c2.js
https://mysite.jiveon.com/7.0.0.184c35b/resources/scripts/gen/bff669856b21c9c0e31a0791de32aff8.js
https://mysite.jiveon.com/7.0.0.184c35b/resources/scripts/gen/029ad0f598a8bbb24f3c182863bda48d.js
https://mysite.jiveon.com/7.0.0.184c35b/resources/scripts/gen/437cd2512f3930f3a3736bb6735278ad.js
...... - Use this generated list and follow the instructions above to flush these individual URLs / ARLs.
- Flushing Individual Asset(s) / URL(s)
- Wait for about seven minutes or so for the confirmation email.
Comments
0 comments
Article is closed for comments.