Posts Tagged ‘configuration’

Publisher Settings Gone But Not Forgotten

Tuesday, May 1st, 2012

Even though ALUI Publisher didn’t get a refresh with WebCenter Interaction 10gR4 and is still at version 6.5, that doesn’t mean it’s not still a large part of your (aging) portal infrastructure.

Hat tip to Andrew Foster for this one – it seems that some of the pre-6.5 Publisher settings still work in Publisher 6.5. Specifically, if you’re having problems getting Publisher to load your custom styles from community-themes.txt when you create a new header portlet, or you see an error like the one below in Publisher Diagnostics, then you can use the old setting CommunityStyleSheetListURL to get Publisher to properly load it.

In other words, if you’re getting this:

… then you should create a line in content.properties to fix that error:

CommunityStyleSheetListURL= http://machine_name /imageserver/plumtree/common/public/css/community-themes.txt

… and your custom styles will then be available when creating Header portlets in WCI:

Turn off SSL for WCI Configuration Manager

Friday, November 18th, 2011

Not happy with that extra click accepting the busted SSL certificate in the ALUI/WCI Configuration Manager? Yeah, me too – that’s like, 47 milliseconds a day of wasted time each day that I’ll never get back:

So, spend 47 seconds to activate HTTP by editing this value in %PT_HOME%\configmgr\2.0\settings\config\private.xml:

<setting name="EAS:httpEnabled">
<value xsi:type="xsd:boolean">true</value>
</setting>

Viola! You now don’t have to use SSL to access the configuration manager. In 1,000 days, your 47 second time investment of time will have paid off:

BTW, you should probably just set the “BEA AL Configuration Manager” service to manual to save a couple megamajigs of RAM – once things are set up you shouldn’t bother leaving the service running anyway.

Oh, and don’t bother wasting the additional 5 minutes trying to turn on Basic Authentication because you think all the cool kids are doing it. That janx don’t work:

<!-- Authentication type. Should be blank for none, and set to either "JAAS" or "BASIC" if enabled. -->
<setting name="EAS:authType">
<value xsi:type="xsd:string">BASIC</value>
</setting>
<!-- EAS:basicAuthUser = username of the sole user allowed to access this server. Note: This user is given the role EAS:name iff authtype == "BASIC" then this setting takes effect -->
<setting name="EAS:basicAuthUser">
<value xsi:type="xsd:string">user</value>
</setting>
<!-- EAS:basicAuthUser = password of the sole user allowed to access this server. Note: This user is given the role EAS:name iff authtype == "BASIC" then this setting takes effect -->
<setting name="EAS:basicAuthPassword">
<value xsi:type="xsd:string">password</value>
</setting>

Add SSL Certificate to Plumtree Publisher JRE

Tuesday, November 15th, 2011

Publisher has a configuration setting in content.properties that allows it to connect directly to the imageserver. Why? Well, the comment in the file describes it appropriately enough:


# JSComponents need to directly access the imageserver from the Publisher
# machine in order to obtain some configuration information. By default it uses
# the image server URL which is provided by the portal for portal end-users,
# but you may also specify an alternate image server URL to be tried first instead,
# such as in the case where the system topography prevents the Publisher
# from accessing that end-user URL.
#JSComponents.AlternateImageServerUrl=http://machinehost:port/imageserver

Problem is, it doesn’t seem to work for the diagnostic tool, and may not work when Publisher needs to load community-themes.txt (which it needs in order to provide the style sheet drop-down for header portlets). So Publisher still needs to connect to the image server – but if the image server is configured to only use SSL, you’re likely going to see an error like this:



Exception Message: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

The solution – import the SSL certificate from the imageserver – is after the break.
(more…)

Configure Publisher To Use A Network Share

Thursday, January 6th, 2011

In many larger Plumtree / WCI Publisher installations, you will have 1 “full” instance of Publisher used for authoring content, and one or more “zombie” (really, that’s what they call it in the configs!) instances serving up that content. 

See Bill Benac’s excellent diagram on this type of configuration.  Often, you’d have the publishing component of Publisher write to a network share, then use the zombie instances to proxy the content itself, or have the zombie instances redirect to a different web server configured to serve up the files.  Why two different approaches?  See this article I wrote back in ’08 for why proxying isn’t always ideal after an upgrade.

Anyway, in some instances, even with just one Publisher instance, you may want to publish to a network share, and don’t want to bother with configuring an additional Web Server to serve up that content.  In those cases, you can easily change Publisher’s own embedded Web Server (technically, it’s JBoss) to serve up this content.  Just perform the following steps:

  1. Set the Publisher Service to run as a user that has full access to the network share.
  2. Update your Publishing and Browsing targets in Publisher Explorer to use the correct paths.
  3. Update the %ALUI_HOME%\ptcs\6.5\container\deploy\jbossweb-tomcat50.sar\server.xml file, specifying your network share here:

That way, when the portal attempts to load published content via http://wci-publisher:7087/publishedcontent/, the portal will be connecting to the JBoss instance running Publisher, but the files will be coming from the network share.

Update: WCI Search Configuration through Configuration Manager

Sunday, November 7th, 2010

A couple months ago, I wrote a post about using the old nodes.ini or cluster.ini files to change your WebCenter Interaction Search Service settings through the deprecated nodes.ini or cluster.ini files.  Since then, I’ve found you can achieve the same effect through the portal’s Configuration Manager:

Now you know.

Analytics – SAML2Keystore value

Saturday, July 17th, 2010

Look, I’ll make this quick and profess my ignorance:  I’m not really sure what the whole “Key Service” thing is in WebCenter Analytics; it’s obviously a security token that needs to be set in multiple places (the Configuration Manager and Java Keystore) to work properly.  A little while ago, I had a client accidentally change the value, and Analytics wouldn’t work.  The keystore passphrase no doubt exists somewhere in the Analytics JRE, but I couldn’t find out where to reset it.  So, I couldn’t find out where to change it in the JRE, and didn’t know what it was suppose to be, so Analytics was DOA.

I got lucky on this one, and hopefully if you found this post through a Google Search, you’ll have saved yourself the headache of trying to figure out what value should be in there.  The answer is in the Analytics Configuration Worksheet (PDF link):

That’s right: it’s “saml2keystore“.  Anyone know how to reset the actual value in Java’s Keystore for Analytics?