Most CWSCJ0371W warning messages are harmless. The majority of these messages are logged as a result of an expired LTPAToken which are cached in browsers. By default, the LTPA token will timeout after 2 hours.
An example of the warning message:
[23/6/16 11:14:24:482 SGT] 000001ba LTPAServerObj W CWSCJ0371W: Validation of the LTPA token failed because the token expired with the following info: Token expiration Date: Wed Jun 22 19:26:00 SGT 2016, current Date: Thu Jun 23 11:14:2 4 SGT 2016 Token attributes: port=xxx, username=user:xxx/xxx.. This warning might indicate expected behavior. Please refer to technote at http://www-01.ibm.com/support/docview.wss?uid=swg21594981.
How to resolve the problem?
As advised by IBM, you may either ignore these warning messages or suppress them by adding “com.ibm.ws.security.ltpa.LTPAServerObject=severe” in IBM Console (Troubleshooting > Logs and trace > <server> > Diagnostic Trace > Change log detail levels).
We have raised a PMR with IBM (#72365,000,834). IBM has confirmed that the fix will be out in WebSphere Portal 8.5 CF12.
Users are unable to switch to projects that contain spaces in their name after they have access an anonymous page (without “myportal”). The behavior will persists until he/she has log out. Do take note that this behavior is only observed in WebSphere Portal CF 10.
Why would a user remove “myportal” from the url (in case L2 asking for use-case scenario again..)?
This is to simulate editors clicking on one of the relative links in the contents (for example a relative link (/contact-us) in “About Us” page that links to a “Contact Us” page).
An editor might click on “contact us” link to verify the link before switching to a project.
How to replicate:
- *IMPORTANT* Ensure you have follow the instruction in “Changing the site URL after an installation” article to remove the context root and you are using WebSphere Portal CF 10.
- Login to WebSphere Portal.
- Create a new project by clicking on the “New Project” link.
- Use the default project name which comes with a space. Click on “Create” button.
- Switch back to Published Site.
- Close the Project dialog.
- Remove “myportal” from the url and press Enter.
- Now switch to the project that you have created earlier.
- You will realize that it will remain as “Published Site” even if you tried to insert “myportal” back.
We have raised a PMR with IBM (#72284,000,834).
A better feedback message is needed to inform the user that he/she need to be in a project in order to create a page from a workflow page template in Manage Pages portlet.
How to replicate:
- Before proceed, ensure that you are using WebSphere Portal CF 9 and above and there is a workflow page template.
- Login to Portal Administration page (http://<hostname>/myportal/Administration).
- Go to Manage Pages (Portal User Interface > Manage Pages).
- Click on “New Page from…” button.
- Select the workflow page template *IMPORTANT* and click on the “OK” button.
- A “EJPAS0017E: Unable to create <page title>” will be displayed, leaving the user trying to figure where he/she went wrong.
9 Feb 2016: We have raised a PMR with IBM (#63843,000,834).
9 March 2016 - IBM L2 replied:
"This seems to be an environmental issue. We tried to recreate the same on several local environments; but it's working absolutely fine everywhere! Will try on other environments; you may also meanwhile retry on other environments and update us."
We immediately replied that we are able to replicate the issue in all of our environments (including local).
11 May 2016: IBM L2 finally acknowledge that they are able to replicate the issue after 3 month of "ding dong". #AmazingJourney #L3WillKnowImmediately #StopHogging
27 May 2016: IBM has come back with a fix (IFPI63085).
How to replicate:
- Follow “Changing the site URL after an installation” article to remove the context root.
- Attach a content with a workflow that requires user’s comment on approval.
- Click on the “Ok” button without keying anything in the comment box and the error will appear.
It is always a good practice (but not necessary) to prepare a seperate production profile to remove modules that are not needed in the production (delivery) environment. The profile will also calls custom module that are built specially for production environment. An idea of what the custom module will contains:
- Google Analytics (for production)
Below shows a list of IBM default modules that we will usually remove from our production profile:
||The getting started module is a pre-defined module that you can use as starting place to quickly inject your own resources into the current theme.
||Module that groups all theme modules that are needed to make a page interoperable with the site toolbar. Add this module to the theme profile of your page if you want to edit the page by using the site toolbar. This module contains all contributions that are needed for view mode. This module must be added to the non-deferred section of the theme profile.
||Earlier portlet CSS support.
||Contains advanced utilities like Promises, IO, DOM helpers, events, and the deferred module loading code.
||The theme status bar that relays information, warning, and error messages to the user.
||The menu framework that was introduced in 2002.
||Provides accessibility support
||Maximize or Minimize portlet support that is implemented as a server-side data source.
||Inserts the reference to the analytics aggregator and its dependencies into the page.
||Styles for default web content samples.
||Provides resources to enable Connections integration with WAI (Web Application Integrator).
||Automatically loads the MobileFirst Client and Cordova APIs for you so you can add native device capabilities in your hybrid applications.
||New Sametime proxy support.
||Adds Draft Page in text that appears along the sides of a page that has a draft in the current project.
Updates: module has been remove in WebSphere Portal 8.5 CF10
||Contribution that is loaded when edit mode is turned on. Separates view mode from edit mode.
||Public module that provides the analytics tag and site promotion functions. This module also provides the dynamic content spots that produce the analytics micro-formats.
||Provides Live Object Framework service to handle Component Action menu instances on a page.
||Provides resources that are required for the Content Targeting dialog that is started from the Component Action menu.
||Allows the Component Action Menu to be opened by clicking an icon in the portlet skin.
In case you are wondering how much does this exercise really save. It only managed to save 2 http requests and 54KB. The difference isn’t significant but we did it anyway for all of our clients.
Still working on this article
Command Prompt for deploying PAA (Portal Application Archive) File