Shulou(Shulou.com)06/03 Report--

1.4 Portal 6.1.0.3 installation or upgrade failed on Windows platform 1.4.1 problem description

Portal 6.1.0.1 or 6.1.0.2 has been installed and an attempt to upgrade to 6.1.0.3 was found to fail on the Windows platform.

Check the upgrade log, such as the 20100122_135338_WP_PTF_6103_selective-install.log file, and find that it is related to PeopleFinder and is caused by an error occurred by the system during the installation of peoplefinder_portlet, which has occurred in almost every version of portal, as shown in figure 1-19.

Figure 1-19 PeopleFinder caused the installation to fail

Check the people_finder portlet install log, such as the people. Implied. _ peoplefinder_._portlet_install.log file, people. Implied. _ peoplefinder_._portlet_install.log file, which is carried by the FilenotFound exception, because PeopleFinder has fewer properties configured. Although this problem was only discovered in 2011, we can see from the historical log that it appeared as early as 2009, as shown in figure 1-20.

The exception in figure 1-20 shows that there are missing attributes in PeopleFinder.

This is due to the fact that the properties of the two files are defined as read-only properties during installation and cannot be replaced. To be sure, after the system installation is completed, the attributes of the two files have not been changed manually. It is suspected that the upgrade program tampered with the file properties during the system upgrade. 6.1.0.3 the upgrade program has just been launched, and it is normal for such a possible error to occur.

1.4.2 solution

Log in to the Portal 6.1.0.3 system, find the path: d:\ IBM\ WebSphere\ PortalServer\ pcc.impl\ people.impl\ peoplefinder\ portlet\ lwp_peoplefinder_war.ear\ lwp.peoplefinder.jsr168.war\ html\, check the permissions of the help folder, and find that it is read-only, as shown in figure 1-21.

Figure 1-21 the help folder has read-only properties

Modify the folder properties to ensure that the folder and its subfiles and subfolders do not have read-only properties.

Reinstall the patch pack, the installation is successful, and the system is successfully upgraded to 6.1.0.3.

1.5 using WAS 6 dynamic caching mechanism to improve WCM Content View Portlet performance and response speed 1.5.1 problem description

The speed of the WCM module is notoriously slow. In addition to ensuring business logic coherence, the use of Cache technology is also a good idea to improve WCM content presentation.

Suppose we use WCM authory to build a site with more than 100 site areas, and then develop our own Content View Portlet, showing the more than 100 site areas to more than 100 columns according to the parameters.

Next, we will use the appropriate WAS 6 dynamic cache (WAS 6 Dynomic Cache) mechanism to improve the performance and response speed of WCM Content View, which is an excellent way to take full advantage of the JSR286 container used by Portal 6.1.

1.5.2 WAS 6 dynamic caching solution

Create a cachespec.xml file in the developed Portlet to define the dynamic cache, as shown in figure 1-22.

Figure 1-22 enabling technology based on WAS dynamic caching in Portlet configuration files to improve performance

Create a JavaBean to generate a reasonable CacheID, as shown in figure 1-23.

Figure 1-23 JavaBean code for dynamic cache implementation

Install the Portlet and retest to verify that the cache works.

1.5.3 using the same user ID to log in on the same machine or multiple machines at the same time will cause a system error

In system testing, especially when performing stress tests, users are often unable to provide the required number of real usernames and passwords. For example, in the above example, we need users to provide the usernames and passwords of 936 real users, which is usually unrealistic. Many project teams decided to use 50 or 100 of these user names / passwords to simulate the real 936 users, which is essentially not allowed.

IBM WebSphere Portal strictly forbids multiple logins of the same ID to the system at the same time, whether on the same machine or simulating multiple IP addresses, which will lead to unpredictable consequences and even system crashes, as shown in figure 1-24.

Figure 1-24 Portal Information Center explicitly forbids multiple logins of the same ID

The corresponding Chinese information center also has a clear definition of the problem, as shown in figure 1-25.

Figure 1-25 the corresponding Chinese information center also has a clear definition of prohibiting multiple logins of the same-ID.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.