Comparing WebSphere Application Server configurations
Over the time one question being asked again and again namely - how can I compare two existing WebSphere Application Server configurations. Although this is a very valid questions - especially for environments with little or no automation - it is quite difficult to answer as most (if not to say all) comparison tools are not of a big help as most WebSphere configuration items are tagged with an ID number making it impossible to compare the configuration file on a text and / or XML basis. While doing some research on this I stepped over urban{... [More]
Tags: was websphere deploy application server urban code udeploy config compare configuration |
WebSphere WCM automatic syndicatin does not start
If you configured a syndicator / subscriber pair for automatic syndication but the automatic syndication does not start and instead of syndicating the content the syndicator goes to pending state then check the property " connect.moduleconfig.syndication.update.subscribers.on.start " in the WebSphere Application Server WAS Admin console ( Resource environment providers > WCM WCMConfigService > Custom properties ). If this property is set to " connect.moduleconfig.syndication.update.subscribers.on.start=false " on... [More]
Tags: automatic syndication websphere wcm portal |
Apache Wink REST Client Applications with WebSphere Portal v9
In a customer project we were migrating from IBM WebSphere Portal v8 to IBM WebSphere Portal Version 9. After the migration log messages like com.ibm.ws.exception.RuntimeWarning: com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeError: java.lang.RuntimeException: com.ibm.ws.cdi.CDIRuntimeException: com.ibm.ws.cdi.CDIDeploymentRuntimeExcep tion: org.jboss.weld.exceptions.DeploymentException: org.apache.wink.client.ClientConfig ... Caused by: org.jboss.weld.exceptions.DeploymentException: org.apache.wink.client.ClientConfig ...... [More]
Tags: wink jaxrs v9 apache 1.1 |
Digital Experience - WebSphere Portal CF14 enhancements
Starting with Digital Experience - WebSphere Portal v8.5 IBM switched to a continuous delivery model providing new features with every new Combined Cumulative Fix. The currently latest available CF14 is no exception to that. The following new features and improvements are available via CF14 : IBM WebSphere Portal Version 8.5 and 9.0 Integration with IBM Watson Content Hub (requires IBM WebSphere Portal Version 9.0) Performance improvements for IBM Web Content Manager Rich Media Edition Server support Web Application Bridge improvement IBM... [More]
Tags: portal cf websphere dx pack fix |
Mapping thread IDs in the SystemOut.log to threads in the javacore file
Analyzing a problem in WebSphere Application Server often requires looking at the javacore file. Once you are identifying an interesting thread there it often requires to look at the SystemOut/SystemErr log for entries originated from that thread. But how to find those? Well in WAS v8.5.5 it is quite easy as you can see in the the below example. Looking at the javacore file locate the 3XMJAVALTHREAD eye-catcher line for the thread and take the value shown next to the getId: which is 0x7CB in our example. ... [More]
|
WebSphere Application Server Performance Tuning Toolkit on RHEL7
Just downloaded the WebSphere Application Server Performance Tuning Toolkit and tried to start it on my RHEL7 workstation. However the start of ./PerfTuningToolkit failed with the following error: (PerfTuningToolkit:26327): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (PerfTuningToolkit:26327): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", Gtk-Message: Failed to load module "pk-gtk-module" 27 PerfDB INFO [main]... [More]
|
Monitoring the progress of a WCM library export
Recently we got an inquiry from a customer how he can monitor the progress of the " ./ConfigEngine.sh export-wcm-data " task. Unfortunately there is no progress information available during the export. However I learned from development that the progress can be monitored if all (and only if all ) libraries are exported namely by comparing the number of *.node file in the export directory with result of the following SQL query: " SELECT COUNT(1) FROM jcrSchema.ICMSTJCRLINKS WHERE WSID = 1 "
Tags: progress library websphere export portal wcm |
HTTP Server plugin does not fall back to HTTP anymore
Since I can think of using the WebSphere Application Server plug-in (and that's for a while now ) the plug-in running in the HTTP server was falling back from HTTPS to HTTP protocol if an HTTPS request was received but no SSL communication could be established to the WebSphere Application Server web-container. This changed in WebSphere Application server v8.5. See http://www-01.ibm.com/support/docview.wss?uid=nas8N1019946 for details.
|
Finally ... WAS v9.0 supports Jython v2.7 while providing compatibility option with v2.1
After years of supporting only Jython v2.1 in the wsadmin scripts with the latest version of WebSphere Application Server namely v9.0 the wsadmin scripting framework supports Jython v2.7 now! At the same time the old Jython v2.1 can still be used in case you are facing compatibility issues with the new Jython version. To run your wsadmin scripts with Jython v2.1 library either specify " -usejython21 true " at the command line at invocation time or set the properity " com.ibm.ws.scripting.usejython21=true " in "... [More]
|
Using Dialog Definitions in xmlaccess import fails
In a project we were using the IBM UX Screen Flow Manager to implement portlet based dialogs. After migrating from WebSphere Portal 8.0 to WebSphere Portal 8.5 the following error occurred when importing the xmlaccess script which defines the access control on the virtual resource. EJPXA0067E: The following configuration data is needed to create a virtual-resource resource: resource-parentref. [virtual-resource name=DIALOG_DEFINITIONS] Solution: Replace the name of the virtual-resource DIALOG_DEFINITONS with the name PCM_DIALOGS. ... [More]
Tags: pcm screen manager flow definitions dialog xmlaccess |
Listing the content of an SPNEGO keytab |
SPNEGO authentication not working
Today we were working on an SPNEGO SSO authentication problem which did not work. We had actually two "flavours" of the problem. In one environment SPNEGO SSO did not work at all and in the other environment SPNEGO worked fine at the primary node but did not work on the second cluster member. In first problem scenario we always got the login page prompted asking for user-id and password but all setup seemed correct. We enabled the following trace on WebSphere Application Server: " com.ibm.ws.security.spnego.*=all " and... [More]
Tags: spnego websphere |
Fallback of Localize Plugin is documented wrong
The fallback of the Localize-Plugin that is documented here is wrong: http://www.ibm.com/support/knowledgecenter/SSYJ99_8.5.0/wcm/wcm_dev_storing_translated_text.html In there it says: "At render time, if the requested language does not exist in the list of elements, the first element is used as the default language." Instead the following fallback is valid: a) locale is determined by the user-profile -> fallback is the portal default language b) locale is determined by the state -> fallback is the portal default language c)... [More]
|
WCM import-wcm-data fails due to invalid characters
A WCM library exported on a WebSphere Portal v7 system using export-wcm-data might fail during the import with the following error: --- snip --- org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x3) was found in the element content of the document --- snip --- The reason for this exception is that low hex characters are in the exported ".node" file(s). These characters are usually shows as ^A, ^B etc. For this problem there is actually a fix included in WebSphere Portal v7.0.0.2 CF24 (was back-ported from v8)... [More]
Tags: wcm import invalid charachter library |
IBM HTTP Server v9.0 is based on Apache 2.4
As last week I wanted to use the " no-cache " environment variable in the IBM HTTP Server configuration for a more fine grained caching configuration I learned that this one is only available in Apache 2.2.12 and later. As the IBM HTTP Server 8.5 is based on Apache 2.2.8 I failed to configure caching for specific mime types only. Just checked the IBM HTTP Server v9.0 documentation and found that IBM HTTP Server is based on Apache HTTP Server 2.4.12. This should allow us to make use of the "no-cache"... [More]
|
This community intended to be be used to share technical information, samples, tips and tricks gathered by the WebSphere Portal ( Digital Experience ) Services team.
Archive
Tags
