A Portal to a Portal: November 2009

Sunday, 22 November 2009

IBM HTTP Server installation wizard - not very wizardly

Whilst trying to install IBM HTTP Server 6.1 on Orac, I was getting very frustrated with my inability to get the installation running. Regardless of what I did, I wasn't able to get the normal installation wizard to run, either via a normal X11 GUI or via VNC. In all cases, the wizard "whinged" about the browser, even though I had the latest version of Firefox installed.

Realising that the installation wizard was actually trying to run a Java JAR file ( setup.jar ), I tried running it by hand using the command: -

java -jar setup.jar

from the IHS directory which is generated when one expands the installation package, supplied by: -

C87PSML.tar.gz WebSphere Application Server V6.1 Supplements for Linux on x86Series, 32-bit Support

C87XSML .tar.gz WebSphere Application Server V6.1 Supplements for Linux on x86Series, 64-bit Support

but I then got the error: -

The wizard cannot continue because of the following error: could not load wizard specified in /wizard.inf (104)

which is particularly useful :-(

However, thinking laterally, I thought that the installer MIGHT be looking for the WAS JVM, so I ran: -

. /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin/setupCmdLine.sh

java -jar setup.jar

which did the trick :-)

# posted by Dave Hay : 09:36 0 Comments

Wednesday, 18 November 2009

WSWS7007E and WSVR0501E Conflict between Lotus Connections 2.5 and Feature Pack for Web Services for WebSphere Application Server V6.1

This is the first of two posts documenting some fun n' games that I've recently seen with LC 2.5 on a WAS environment that also included this Feature Pack: -

Utility: Feature Pack for Web Services for WebSphere Application Server V6.1

http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21264563

I'll document the more pressing issue in the next day or so, but wanted to mention that, on my own environment ( aka Orac ), I hit the following exceptions when trying to start Connections: -

WSWS7007E: The peoplepages.war application module cannot be loaded correctly because of the following error: com.ibm.ws.metadata.annotations.AnnotationException: Annotation processing failed for class: com/ibm/lconn/profiles/internal/service/AbstractCodesService.class

and: -

WSVR0501E: Error creating component null [class com.ibm.ws.runtime.component.ApplicationServerImpl]
com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.metadata.annotations.AnnotationException: Annotation processing failed for class: com/ibm/lconn/profiles/internal/service/AbstractCodesService.class

In essence, I was installing the Feature Pack onto an existing node ( the first, and currently only, node within a WAS 6.1 cell/cluster ) that was running WebSphere Application Server Network Deployment 6.1.0.23.

The Feature Pack ( downloaded as 6.1.0-WS-WAS-WSFEP-LinuxX32.tar.gz ) went in without problems, but I was then unable to start Connections.

The Annotation Exception problem is/was well known in earlier versions of WAS, as a Google search will show.

In the end, I had to do the following: -

a) Remove the Feature Pack

b) Remove the 6.1.0.23 fixpack for WAS ND ( and its corresponding SDK fix pack 23 )

c) Install the Feature Pack ( which in turns upgrades WAS and the SDK to fix pack 9 )

d) Install 6.1.0.9-WS-WASWebSvc-IFPK53084.pak and 6.1.0-WS-WASWebSvc-LinuxX32-FP0000023.pak for the Feature Pack

e) Install 6.1.0-WS-WASSDK-LinuxX32-FP0000023.pak and 6.1.0-WS-WAS-LinuxX32-FP0000023.pak

Having done all of the above, versionInfo.sh now returns: -

WVER0010I: Copyright (c) IBM Corporation 2002, 2005; All rights reserved.
WVER0012I: VersionInfo reporter version 1.15.4.3, dated 11/12/08

--------------------------------------------------------------------------------
IBM WebSphere Application Server Product Installation Status Report
--------------------------------------------------------------------------------

Report at date and time November 17, 2009 9:35:40 PM GMT

Installation
--------------------------------------------------------------------------------
Product Directory /opt/IBM/WebSphere/AppServer
Version Directory /opt/IBM/WebSphere/AppServer/properties/version
DTD Directory /opt/IBM/WebSphere/AppServer/properties/version/dtd
Log Directory /opt/IBM/WebSphere/AppServer/logs
Backup Directory /opt/IBM/WebSphere/AppServer/properties/version/nif/backup
TMP Directory /tmp

Product List
--------------------------------------------------------------------------------
ND installed
WEBSERVICES installed

Installed Product
--------------------------------------------------------------------------------
Name IBM WebSphere Application Server - ND
Version 6.1.0.23
ID ND
Build Level cf230910.10
Build Date 3/10/09

Installed Product
--------------------------------------------------------------------------------
Name WebServices Feature Pack
Version 6.1.0.23
ID WEBSERVICES
Build Level cf230907.03
Build Date 2/21/09

--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------

and, perhaps MORE importantly, Connections 2.5 now starts, and then I hit the next problem ...

CLFRO0002E: Failed to post the bookmark to Bookmarks. java.lang.ClassCastException: org.apache.abdera.parser.stax.FOMText incompatible with org.apache.axiom.om.impl.OMContainerEx

This is definitely a conflict between the Web Services Feature Pack and Lotus Connections, but I'm not yet sure how to resolve it .....

WATCH THIS SPACE ->>>> <<<<--

# posted by Dave Hay : 21:27 2 Comments

SECJ0375E: Mismatch of realms during token validation

More notes from the front-line. Whilst trying to get WebSphere Portal <-> Lotus Connections <-> Lotus Quickr to place nicely using the Lightweight Third Party Authentication (LTPA) mechanism to achieve Single Sign-On, we were hitting these two messages: -

SECJ0375E: Mismatch of realms during token validation

SECJ0373E: Cannot create credential for the user <null> due to failed validation of the LTPA token. The exception is com.ibm.websphere.security.CustomRegistryException: The realm in the token: domino.uk.ibm.com:389 does not match the current realm: defaultWIMFileBasedRealm

This was being displayed in SystemOut.log on the Connections server. The second message really says it all.

When we configured the underlying WebSphere Application Server 6.1.0.23 instance for security, using a Federated Repository, Domino LDAP etc., we failed to change the realm name, but left it at the default of defaultWIMFileBasedRealm.

Interestingly, the LC25 Information Centre does imply that it's OK to leave it as-is: -

On the Federated Repositories page, enter an administrative user ID (for example, wasadmin) in the Primary administrative user name field. You can leave the other default settings, such as Realm name, unchanged.
Note: The administrative user ID must be unique, and must not exist in the LDAP repository to be federated.

http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/topic/com.ibm.connections.25.help/t_inst_federated_repositories.html

However, the LTPA token that had been generated on the portal server ( WebSphere Portal Server 6.1.0.2 running on WebSphere Application Server 6.1.0.25 ), and contained the line: -

com.ibm.websphere.ltpa.Realm=domino.uk.ibm.com\:389

The solution ?

We simply changed the Realm Name from defaultWIMFileBasedRealm to domino.uk.ibm.com:389 and then restarted Connections.

Job done, next .....

# posted by Dave Hay : 21:10 0 Comments

CLFRN1152E: Unable to contact the global search service. Please start the Search application if it is not started. If the service is started, please check the network connection.

Working through my various notes relating to a recent Lotus Connections 2.5 clustered installation, we did see this error: -

CLFRN1152E: Unable to contact the global search service. Please start the Search application if it is not started. If the service is started, please check the network connection

This occurred despite the Search application ( actually installed onto the same WAS instance that hosts Home Page and News, as per the recommended practice ) being started.

The problem was due to my having failed to completely update LotusConnections-config.xml after the cluster.

This wiki article: -

http://www-10.lotus.com/ldd/lcwiki.nsf/dx/S1_Editing_the_configuration_file

directs you to update the config. file ( using the wasadmin scripts to check it out and back in again ) to reflect the fact that all of the services are now accessed via an HTTP server ( actually a load balancer in front of TWO HTTP servers, in my case ).

I'd missed this crucial line: -

All entries in this file should be updated to the Web server URL with the exception of the three bootstrap entries – two of which should not be modified at all. The only bootstrap entry which must be modified is that for search. Leave the host and port blank as shown:

In essence, I had to change: -

<sloc:serviceReference bootstrapHost="dm.uk.ibm.com" bootstrapPort="2811" clusterName="Homepage" enabled="true" serviceName="search" ssl_enabled="false">

to: -

<sloc:serviceReference bootstrapHost="" bootstrapPort="" clusterName="Homepage" enabled="true" serviceName="search" ssl_enabled="false">

In other words, I removed the host name and port number for the bootstrapHost and bootstrapPort parameters, but *ONLY* for the Search service.

Prior to this error, we had been seeing: -

[09/11/09 15:01:12:978 GMT] 00000037 WsnInitCtxFac W NMSV0602E: Naming Service unavailable. A communications error occurred.
[09/11/09 15:01:12:979 GMT] 00000037 TagCloudServi E com.ibm.lconn.comm.internal.service.TagCloudServiceImpl getEJBSearchHandlerFromSearchEjbDefault Caught naming exception!
javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: "corbaloc:iiop:dm.uk.ibm.com:2811". Make sure that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused:host=dm.demo.ibm,port=2811 vmcid: IBM minor code: E02 completed: No]

   at com.ibm.ws.naming.util.WsnInitCtxFactory.mapInitialReferenceFailure(WsnInitCtxFactory.java:2226)
   at com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInitCtxFactory.java:1386)

This particular problem was, in my simple world, was that the Deployment Manager node (DM) was being contacted by the WAS instance on which Connections was installed, but that the hostname / IP address was being incorrectly resolved; note that the FQ hostname differs within the error message.

Once we fixed the DNS name resolution ( by hacking the /etc/hosts file ), that particular error message went away, and was replaced by the aforementioned CLFRN1152E.

# posted by Dave Hay : 21:00 0 Comments

Wednesday, 11 November 2009

IBM WebSphere eXtreme Scale 6 - Review to come

Although it has not yet come up on one of my Portal projects, it's been a fact for some time that WebSphere Portal can be clustered to extremes via the WebSphere Extended Deployment. Therefore, it's timely that I am awaiting a copy of Anthony Chaves' book IBM WebSphere eXtreme Scale 6 from Packt Publishing.

From Packt's site, here's a brief synopsis: -

Build scalable, high-performance software with IBM's data grid

• Get hands-on experience with eXtreme Scale APIs, and understand the different approaches to using data grids

• Introduction to new design patterns for both eXtreme Scale and data grids in general

• Tutorial-style guide through the major data grid features and libraries

• Start working with a data grid through code samples and clear walkthroughs

Not sure that I'll completely understand all of the content (!) but it should prove to be a useful reference, and will help me grow my understanding, especially as to how eXtreme Scale infrastructure works.

Watch this space ...

# posted by Dave Hay : 09:02 0 Comments

Thursday, 5 November 2009

Lotus Connections 2.5 - All clustering together ...

Will write this up more fully as time allows, but had a frightening moment yesterday - after 1+ hours, my Connections 2.5 installation ( the first node of a two-node cluster ) failed :-(

The LC product had successfully installed onto the node, but failed to "ripple" across to the cell that was managed by a WebSphere Application Server 6.1 Network Deployment DM node. The error message being displayed was CLFRP1261E.

The lcinstalllog.txt wasn't particularly useful, in terms of providing further details.

As is always the way, I couldn't find owt about this message in the Information Centre or on't'internet etc. so had to rely upon native wit and intelligence ( OK, I guessed ).

I took a look at /tmp using the df -km command and - c'est voila - it was showing at 100% used.

I cleared /tmp down and re-ran the installation ( the second time around, one chooses to add a standalone installation to a cell/cluster ) and it just worked.

Therefore, I'm assuming that CLFRP1261E actually means "Hey dude, you've like got no frikking disk space in /tmp, man" or something.

Don't take my word for it, but it did work :-)

# posted by Dave Hay : 20:11 1 Comments

Sunday, 1 November 2009

Fun and Games with Windows 7

No, before anyone asks, I haven't gone over to the dark side and "upgraded" my Mac or Ubuntu boxen to Windows 7 ....

However, whilst staying with friends, I volunteered to help resolve an issue whereby he was getting no audio from his Windows Media Centre PC. The PC ( a Sony VAIO VGX-TP1 ) connects via a HDMI cable to a monster LG 42" LCD HD telly.

Having worked OK whilst running Vista, all appeared to be well following an upgrade to Windows 7; however, something seemed to change, potentially due to a pesky Windows update.

The symptoms were quite simple - no sound, anywhere, from anything, zip, nada, nowt, nuffink.

The plumbing is quite straight-forward; a nice chunky HDMI cable from the the back of the Sony, plugged directly into one of the two HDMI ports on the telly. We tried the normal problem determination techniques; swapping HD cables, powering on/off PC and TV etc. but nothing appeared to help.

To cut a very long ( 3 hours last night, 3 hours this morning ) story short, having upgraded/downgraded/regraded the audio drivers ( provided by Realtek ), I'd completely failed to realise that, in this brave new world, HD audio comes from the video card as much as from the sound card; the sound card only drives a so-called optical output on the rear-side of the PC. Once I downloaded and installed the latest drivers (15.12.75.4.1930) for the graphics card, an Intel Graphics Media Accelerator 950 from: -

http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18231&lang=eng

and rebooted, all was well.

For reference, we also used the most up-to-date Realtek driver (R2.35) from here: -

http://www.realtek.com.tw/DOWNLOADS/downloadsView.aspx?Langid=1&PNid=24&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false

but this made no difference; I switched to/from the stock Windows 7 drivers, but to no avail. The "killer blow" was the Intel drivers :-)

Apart from trial and error ( and coffee ), credit must be given to this posting: -

Good news! I talked to a friend that worked in the Windows 7 development at Microsoft and he had the same prob with 2 of his computers and figured out the solution. While it doesn't make a whole lot of sense, the HDMI Audio comes from the video card drivers. I went to Intel's website and chose my video card, and they had Windows 7 RC drivers up, I downloaded those and installed, rebooted and my HDMI audio is now back in the soundcard list and I tested it, worked great! So to all of you above, go get the latest video card drivers and try again. Worked for me!

http://social.answers.microsoft.com/Forums/en-US/w7music/thread/a494af37-9780-4b4a-895c-b2c1fce17fe6

which provided me with the clue to upgrade the frikkin' Intel drivers :-)

# posted by Dave Hay : 08:46 0 Comments

Subscribe to Posts [Atom]

A Portal to a Portal