• Share
  • ?
  • Profiles ▼
  • Communities ▼
  • Apps ▼

Blogs

  • My Blogs
  • Public Blogs
  • My Updates
  • Administration
  • Log in to participate

▼ Tags

 

▼ Similar Entries

SOA BOD - Rest Respo...

Blog: Websphere Com...
Jacky Yan 50JTYSWH2S
Updated
0 people like thisLikes 0
No CommentsComments 0

▼ Archive

  • December 2018
  • November 2018
  • September 2018
  • March 2018
  • December 2017
  • October 2017
  • September 2017
  • February 2017
  • January 2017
  • October 2016
  • September 2016
  • July 2016
  • May 2016
  • March 2016
  • February 2016
  • November 2015
  • October 2015
  • September 2015
  • June 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • November 2014
  • September 2014
  • July 2014
  • June 2014
  • April 2014
  • March 2014
  • October 2013
  • August 2013
  • June 2013
  • May 2013
  • March 2013
  • February 2013
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • March 2012
  • November 2011
  • September 2011
  • August 2011
  • June 2011
  • May 2011
  • February 2011
  • October 2010
  • September 2010
  • August 2010
  • July 2009
  • June 2009
  • March 2009
  • February 2009
  • August 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008

▼ Links

  • Portal L2 Blog
  • Thoughts on Web Content Manage...
  • Web Content Manager Forum
  • WebSphere Portal Forum
  • WebSphere Portal Security, Por...
  • WebSphere Portal zone

▼ Blog Authors

Portal administration and performance

View All Entries
Clicking the button causes a full page refresh. The user could go to the "Entry list" region to view the new content.) Entry list

Administration Tips and Tricks

Thomas_Hurek 110000ADUU | | Tags:  jdk8 ‎ | 8,540 Views

In this blog I will lay out some Administration Tips and Tricks around Digital Experience, WebSphere Portal and Web Content Manager:

 

IBM JDK 8 can be used with version 8.5

With version 8.5 of Digital Experience during install WebSphere Application Server 8.5.5.x and JDK 7.0.0.x are deployed as prerequisites for Digital Experience.

Starting with WebSphere Application Server 8.5.5.2 Java 7.1.0.x was provided with the Application Server fix pack. Starting with WebSphere Application Server 8.5.5.9 Java 8 was provided with the Application Server fix pack.

Starting with 8.5 CF12 Digital Experience supports Java 8.

Java version 8 can be installed via the Installation Manager. After installing the JDK the command managesdk can be leveraged to switch the JDK used with the Digital Experience profile to 8.

E.g. for Linux the process is described here in the InfoCenter: http://www.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/install/sdk_upgrade-Linux.html

 

Publishing a project on a subscriber

By default, syndicated projects can be published only on the server the project is created on, and cannot be published on downstream servers. In case a Preview server is part of the topology it can be difficult to preview projects within the project context. This new option allows to publish the project on e.g. a preview environment, test it and then publish it on Authoring. This also requires leveraging mirror syndication to reset the target environment to the right state.

Additional details can be found here: http://www.ibm.com/support/knowledgecenter/SSDK36_8.5.0/wcm/wcm_dev_projects_syndication.html

 

How to add WCM to a Portal 8.5 server install

Multiple Editions of the Digital Experience software exist. The Portal server offering does not include the WCM license and so some functionalities like creating content are disabled. It is possible to add WCM to a Portal server offering if needed. This can be done via the Installation Manager. The detailed steps are described here: http://www.ibm.com/support/knowledgecenter/en/SSHRKX_8.5.0/mp/install/inst_upsell.html

 

Disable Caching for WCM servlet URLs

In case caching of results of a server side WCM servlet URL is not desired the following URL parameters can be added:

&CACHE=NONE&CONTENTCACHE=NONE&CONNECTORCACHE=NONE

CACHE=NONE disables WCM basic caching.

CONTENTCACHE=NONE disables WCM advanced caching.

CONNECTORCACHE=NONE disables WCM caching of static responses.

Note though that this will have a performance impact as more database calls will be triggered.

 

Escaping rich text for JSON for WCM servlet URLs

If delivering content in form of JSON from WCM, rich text can be escaped to allow JSON formatting via the Plugin:CopyText tag with escape set to json.

The following example escapes the "Body" element of a piece of content for JSON:

"richtext":"[Plugin:CopyText count="1" format="trim" escape="json" text="[Element context='current' type='content' key='Body']"]"

 

Enabling fragment caching for IBM API portlets via XMLAccess

It is possible to enable fragment caching for existing IBM API portlets via XMLAccess tag portlet.

In the example below a public cache scope and timeout of 300 seconds is configured:

<portlet action="update" active="true" defaultlocale="en" domain="rel" name="Welcome to WebSphere Portal" objectid="Z3_00000000000000A0BR2B300S64" provided="false" servletref="ZV_00000000000000A0BR2B300SK0" uniquename="wps.p.Welcome To WebSphere Portal" remote-cache-scope-private="false" cache-expiration="300">
<access-control externalized="false" owner="undefined" private="false">
<role actionset="Editor" update="set">
<mapping subjectid="cn=wpsadmins,o=defaultwimfilebasedrealm" subjecttype="user_group" update="set"/>
</role>
</access-control>
</portlet>

Modified on by Thomas_Hurek 110000ADUU
  • Add a Comment Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry
Notify Other People
notification

Send Email Notification

+

Quarantine this entry

deleteEntry
duplicateEntry

Mark as Duplicate

  • Previous Entry
  • Main
  • Next Entry
Feed for Blog Entries | Feed for Blog Comments | Feed for Comments for this Entry