Tomorrow, I'm seeing a customer who is having an issue with a missing Administration link in their Virtual Portal, using WebSphere Portal 6.1.
I've reproduced the problem ( or so I hope ) using WebSphere Portal 6.1 on openSuSE 11 ( it may or may not important, but I've recreated the customer's environment by installing two instances on the same application server, and securing both against OpenLDAP ).
After some digging around, I've resolved my problem ( and, I hope, my customer's problem ), thanks to the nice people who maintain the WebSphere Portal Family Wiki here.
The specific article ( WebSphere Portal 6.1 Admin Installation Virtual Portal Initialization ) describes how the problem occurs ( on instances where one installs WebSphere Portal in (ironically) administration mode ( a slimmed down installation with far far fewer applications and portlets ).
I, and (I'm hoping) my customer, have used this lightweight installation - it's a good way of creating a development or demonstration environment. I usually install WebSphere Portal Express 6.1 which can take 2-3 hours depending on the hardware ( bearing in mind that DB2 UDB and WCM are installed, along with a host of portlets and services ), whereas the slimmed down installation took 30-40 minutes ( on an openSuSE 11 VMware image running under my beloved Ubuntu ).
It highlighted how little I know about Virtual Portal creation - under the covers, an XMLAccess script is executed ( whereas I thought it was Harry Potter at work ). It transpires that the XMLAccess script neglects to add the Administration link to the theme of the newly created VP ). The article provides an updated script which fixes the problem.
More for me to learn ..... and to find out whether this does, in fact, help my customer tomorrow ...
Cross my fingers :-)
Geeking in technology since 1985, with IBM Development, focused upon Docker and Kubernetes on the IBM Z LinuxONE platform In the words of Dr Cathy Ryan, "If you don't write it down, it never happened". To paraphrase one of my clients, "Every day is a school day". I do, I learn, I share. The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions. Remember, YMMV https://infosec.exchange/@davehay
Subscribe to:
Post Comments (Atom)
Note to self - use kubectl to query images in a pod or deployment
In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...
-
Why oh why do I forget this ? Running this command : - ldapsearch -h ad2012.uk.ibm.com -p 389 -D CN=bpmbind,CN=Users,DC=uk,DC=ibm,DC=com -w...
-
Error "ldap_sasl_interactive_bind_s: Unknown authentication method (-6)" on a LDAPSearch command ...Whilst building my mega Connections / Domino / Portal / Quickr / Sametime / WCM environment recently, I was using the LDAPSearch command tha...
-
Whilst building a new "vanilla" Kubernetes 1.25.4 cluster, I'd started the kubelet service via: - systemctl start kubelet.se...
2 comments:
Yay, fixed it, as I'd hoped. My customer had implemented the fix almost before I got my coat off this AM. One of the shortest visits ever :-)
Dave,
Thanks for your informative info. I've downloaded the VMware WebSphere Portal V6.1.0.1 Beta on WAS 7.0 and have misplaced the login credentials. Please help?
Thanks
Post a Comment