Troubleshoot WebSphere Portal installation

 

+
Search Tips   |   Advanced Search

 

  1. Version Information
  2. Receive EJPIC0034E: unexpected service exception message
  3. Java processes continue to run
  4. General steps to perform if the installation fails
  5. Reinstall after a failed installation
  6. Installation fails after uninstalling a previous copy of WebSphere Portal
  7. Receive Permission denied error when attempting to install on UNIX
  8. Search Collections are not removed during an uninstall
  9. Installation fails due to path problem
  10. Non ISO-8859-1 characters not supported in installation path on Windows
  11. Console mode installation not available for bidirectional languages
  12. Installation fails due to insufficient disk space
  13. Desktop display width doubles when running installation program
  14. Some portlets failed to deploy
  15. Receiving errors when installing and uninstalling WebSphere Portal with different users
  16. WebSphere Portal configuration fails
  17. Errors related to XADatasources prevent restarting WAS
  18. WpsHostPort property value not updated during installation
  19. Improper WebSphere Portal file access permissions may exist after installing on AIX or Solaris
  20. Errors are written to SystemOut.log during portal startup
  21. Turkish language does not work with WebSphere Portal install wizard
  22. Portal startup fails with WTRN0016E in logs

  23. Related to HP-UX

  24. Related to Windows

  25. Related to UNIX

  26. Related to AIX

  27. Related to Solaris

  28. Related to Linux

  29. Related to i5/OS

  30. Related to ReleaseBuilder

 

Version Information

The WebSphere Portal information tool can be used to gather information about the WebSphere Portal product.

cd portal_server_root/bin
./WPVersionInfo.sh

To generate a report in html format...


./genVersionReport.sh

 

History Information Tool

The History information tool can be used to gather installation history for the WebSphere Portal product.

cd portal_server_root/bin
./WPHistoryInfo.sh

To generate a report in html format...

./genHistoryReport.sh

 

Receive EJPIC0034E: unexpected service exception message

Installation on a mounted directory fails with a EJPIC0034E: unexpected service exception error.

Solution: If you receive this message, run df -k to see if there are problems with the file systems or we can validate using df-k before installing.

 

Java processes continue to run

When canceling installation during one of the installation steps, there may be some extra Java processes left running in the background.

Solution: Stop any running Java processes before attempting another installation.

 

General steps to perform if the installation fails

  1. If the WebSphere Portal installation fails, check the WebSphere Portal logs for relevant messages.

  2. Verify that WebSphere Application Server has been installed correctly.

  3. Verify that we can start and stop WebSphere Application Server.

  4. Change the time-out request for the SOAP client.

    The default, in seconds, is 180. Edit...

    was_profile_root/properties/soap.client.props

    ...and set... 

        com.ibm.SOAP.requestTimeout=6000

 

Reinstall after a failed installation

Solution: If a product fails to install, do the following steps before you attempt to install again:

  1. If an uninstallation program is available, run it before reinstalling the product.

    If the installation failed before the uninstallation program was created or if the uninstallation program fails, manually delete the installation directory and all of its contents before reinstalling the product.

  2. When you run the installation program, any irregularities in the file...

    vpd.properties

    ...pertaining to WebSphere Portal will be corrected automatically. It is not recommended that you edit this file manually or delete it.

 

Installation fails after uninstalling a previous copy of WebSphere Portal

If the WebSphere Portal installation fails after you have uninstalled a previous copy of WebSphere Portal, ensure that no components of the WebSphere Portal remain before you attempt to install WebSphere Portal again.

Solution:

  1. Open the Administrative Console for WebSphere Application Server. Verify that all of the WebSphere Portal components were removed by the previous uninstallation. Manually remove any of the components that remain. This includes the following elements:

    Enterprise application WebSphere Portal Enterprise Application
    Application server WebSphere Portal
    Data sources wpsdbDS and wmmDS
    JDBC driver wpsdbJDBC

  2. On the portal machine, delete the WebSphere Portal directory manually.

  3. Restart the installation.

 

Receive "Permission denied" error when attempting to install on UNIX

You receive a "Permission denied" error message when attempting to install WebSphere Portal using a non-root user on a UNIX system Solution: Remove the following files and directories from the /tmp directory.

  • installtraces*
  • installmessages*
  • Localize*
  • wp*

Also, remove all files from...

/var/tmp

These files may exist from a previous installation and be owned such that the installing user cannot overwrite them.

 

Search Collections are not removed during an uninstall

Solution:

  1. Remove the Search Collections before uninstalling.

  2. Manually remove the Search Collections by deleting....

    app_server_root/searchcollectionname

    ...directories after an uninstall is complete.

    The Search Collections directory might not be located under app_server_root since the user can choose to locate Search Collection anywhere on the system

 

Installation fails due to path problem

Installation can sometimes fail if you download installation files to a local hard drive or a network drive and use long directory paths for the directories corresponding to the product CDs.

Solution: Where possible, you should specify short path names that do not contain special characters such as Double Byte Character Sets (DBCS).

 

Non ISO-8859-1 characters not supported in installation path on Windows

Solution: Installing to paths containing non ISO-8859-1 characters does not work and is not currently supported. Installing WebSphere Portal to use an existing WebSphere Application Server whose install path includes non ISO-8859-1 characters also might not work. For example, Chinese characters in the installation path are not supported.

 

Console mode installation not available for bidirectional languages

When installing WebSphere Portal in console mode on machines with bidirectional language support, an error is generated, and the installation exits.

Solution: Console mode installation is not supported for bidirectional languages, such as Hebrew and Arabic. When installing WebSphere Portal in a bidirectional language, we cannot use console mode. Instead, perform the installation using the graphical interface or using a response file.

 

Installation fails due to insufficient disk space

Solution: If you receive a message during installation informing you that there is insufficient disk space to install WebSphere Portal, we can complete one of the following steps:

  • Select a different disk drive or partition on which to perform the installation.

  • Exit the installation program, free up disk space on the partition to which you are attempting to install, and start the installation program again.

  • Solaris : Check that the/var/tmp directory contains 250KB or more free space.

 

Desktop display width doubles when running installation program

When running the WebSphere Portal installation program on a machine with the Windows 2000 operating system, you might encounter an error that causes the desktop to be displayed at twice its normal width, so that only half of the desktop can be viewed. This problem is due to an issue with Java 1.4 and the display settings of the monitor. This problem can occur for any of the ISMP-based wizards, such as the configuration wizard.

Solution 1: Reduce the refresh rate for the monitor.

  1. Exit the installation program (if still running).

  2. Click..

    Start | Settings | Control Panel | Display | Settings | Advanced | Monitor

  3. Change the refresh rate to a lower value. For example, if the refresh rate is set to 85 Hertz, we can change it to 60 Hertz.

  4. Click OK > OK >Yes to save changes.

After you complete the WebSphere Portal installation, restore the display settings to their previous values.

Solution 2: Decrease screen resolution (This solution increases the pixel size on the screen to increase the size of the image.)

  1. Exit the installation program (if still running).

  2. Click Start > Settings > Control Panel.

  3. Double-click Display.

  4. Click Settings.

  5. In the Screen Area section, move the slider to the left (toward "Less"). If the monitor resolution is at its lowest setting, refer to Solution 1 above.

  6. Click OK > OK > Yes to save changes.

After you complete the WebSphere Portal installation, restore the display settings to their previous configuration.

 

Some portlets failed to deploy

If you encounter installation error...

EJPI0021W Some portlets failed to deploy

...we might be able to recover the installation. This error can be caused by some portlets being left on WebSphere Application Server, or caused by WebSphere Portal not running.

Solution:

Verify that WebSphere Portal starts and that users can log in as the portal administrator. If this cannot be verified, something more severe than portlet deployment has gone wrong and manually installing portlets will not work.

If WebSphere Portal login succeeds, you might be able to manually install portlets. To manually uninstall portlets... 

cd portal_server_root/bin 
xmlaccess -in portal_server_root/package/removeallportlets.xml \
          -user portal_admin_id \
          -pwd portal_admin_password \
          -url localhost:port/wps/config

To install all portlets... 

./WPSconfig.sh portlets -DPortalAdminPwd=password

 

WebSphere Portal configuration fails

If the configuration of WebSphere Portal fails with...

BUILD FAILED file:../config/actions/was_cfg.xml:592:
Execute failed: java.io.IOException: Not enough space

Total time: 44 minutes 10 seconds

...there is not enough swap space.

Solution: Increase the swap space to a minimum of 2.5 GB. 3.0 GB is preferred.

 

Errors related to XADatasources prevent restarting WebSphere Application Server

If WebSphere Application Server is stopped improperly or unexpectedly, you might see errors similar to the one below when you try to restart: 

J2CA0061W: Error creating XA Connection and Resource com.ibm.ws.exception.WsException: 
DSRA8100E: Unable to get a XAConnection from the DataSource.

When this happens, you will be unable to restart WebSphere Application Server. This is because there are XA transactions still pending in the tranlog directory.

Solution: Delete the transaction logs in...

was_profile_root/tranlog/WebSphere_Portal

...then restart WebSphere Application Server.

 

WpsHostPort property value not updated during installation

If the wpconfig.properties file is locked during installation, such as when it is open in a text editor, this can prevent the WpsHostPort property value from being updated properly. Although this is unlikely to occur during most installation scenarios, it could happen if you are installing on an existing WebSphere Application Server with security enabled, because this installation scenario requires us to perform the installation in a series of manual steps.

If the WpsHostPort property value is not set correctly, you will encounter problems if you perform a task that refers to the wpconfig.properties file for the WpsHostPort property, such using the xmlaccess command to deploy security credentials or portlets. Because the command will attempt to use the default value of 80 for WpsHostPort instead of the port number set at installation (which is what the xmlaccess command expects), the command will fail.

Solution: Edit the wpconfig.properties file with a text editor, and change the value of the WpsHostPort property to the value set during installation.

 

Improper WebSphere Portal file access permissions may exist after installing on AIX or Solaris

After installing WebSphere Portal on some AIX and Solaris platforms, some files are left that have improper permission settings. These permission settings may allow Trojan horse type attacks from users with access to the system.

Solution: Use the following steps to correct the permission settings:

  1. Backup the existing file permission.

  2. Executes once to secure the existing WebSphere Portal server files: 

        cd /usr/WebSphere/AppServer/bin    ./stopServer.sh WebSphere_Portal -user username -password password     cd /usr/WebSphere/PortalServer     chmod -R o-r,o-w,o-x

  3. Enter the following commands to restore the original WebSphere Portal file settings: 

        cd /usr/WebSphere/AppServer/bin    ./stopServer.sh WebSphere_Portal -user username -password password     cd /usr/WebSphere/PortalServer/uninstall/fix1
    uncompress undo_chmod     cd../..
    uninstall/fix1/undo_chmod

    If any errors occur, we can run the undo_chmod command multiple times.

 

Receiving errors when installing and uninstalling WebSphere Portal with different users

Solution: You must install and uninstall WebSphere Portal with the same user.

 

Errors are written to SystemOut.log during portal startup

During portal startup, error(s) similar to the following might be written to the SystemOut.log: 

0000000a ArtifactLoade W com.ibm.ws.al.locator.TargetNamespaceSAXParser parseDocument(URL) 
CWLAG0450W:unableto parse document file:
    /opt/IBM/WebSphere/PortalServer/shared/app/oiexport/SearchML.xsd;
Reason: org.xml.sax.SAXParseException: The element type "complexType" 
        must be terminated  by the matching end-tag.

Solution: The error does not indicate a problem with WebSphere Portal nor with XML conversion and can be ignored.

 

Turkish language does not work with WebSphere Portal install wizard

Using Turkish as the install wizard language when installing WebSphere Portal on HP-UX causes errors.

Solution: When installing WebSphere Portal on HP-UX, use English as the install wizard language regardless of operating system locale.

 

Related to Windows

 

Error starting servers when servers running as Windows services

You receive an error such as ADMU7711E: Unexpected exception associated with WASService.exe: exitCode = -1 during processing of a server with the name: WebSphere_Portal. However, the server and associated Windows service start.

Solution:

  1. Stop the server using the stopserver command; then start it again using the startserver command.

  2. If Step 1 does not fix the problem, manually add the services using the following commands from the WebSphere bin directory:

    <websphere_dir>\appserver\bin\wasservice -add <servicename> -serverName <servicename> -profilePath <quotedProfilePath> -wasHome <quotedWasHome> -userid <windowsadminuser> -password <windowsadminpw>
    For example, using default installation values for the portal server:

    C:\Program Files\IBM \WebSphere\AppServer\bin\wasservice -add WebSphere_Portal_myNode -serverName WebSphere_Portal -profilePath "c:\ibm\WebSphere\profiles\wp_profile" -wasHome "c:\Program Files\IBM \WebSphere\AppServer" -userid myAdmin -password myAdmin
    See the wpinstalllog.txt file in the portal server log directory for the commands used for the installation.

  3. Restart the server using the startserver command.

 

Installation fails with the message "Please make sure you have at least 100MB free space in %TEMP% directory."

This message may be displayed even if the %TEMP% directory has more than 100MB of free space. If you have more than 100MB of free space, it is likely the install.bat (or install.sh) had problems copying some files to the %TEMP% directory. Refer to the file...

%TEMP%\wplaunchlog.txt

There are several reasons this might happen:

  • You are installing from a network drive, and lost the connection in the middle of the installation.

  • You copied the cd images to the local machine but the permissions of the files in cdSetup are preventing the files from being copied.

  • Our %TEMP% directory contains some files used by the previous WebSphere Portal installation.

Solutions:

  • Copy the install image to a local harddisk drive, set the correct file permissions, and run install.bat (or install.sh) from the local hard disk.

  • Remove files in the %TEMP% directory and rerun install.bat (or install.sh).

 

WebSphere Application Server silent installation fails on Windows

On Windows, the silent installation fails if the user lacks permissions. In interactive mode, the install will catch the error and display a message. The GUI installer will not let the installation continue until the permissions are set by the System Administrator.

Solution: You must have the permissions set as stated in Preparing the Windows machine.

 

Installation program incorrectly identifies Windows 2003 operating system

When installing WebSphere Portal on Windows 2003, an error similar to the following error might be displayed in the installation log file:

EJPC1517I The Discovered specific Operating System type and version Is winxp(5.0,2.0,0.0,0.0,0.0)

Solution: Due to how different levels of Java report Windows 2003, the installation program might identify the operating system incorrectly as either Windows 2000 or Windows XP. This error does not affect the WebSphere Portal installation and can be ignored.

 

WebSphere Application Server installation stalls on Windows 2003 when installing from a network drive

When installing WebSphere Application Server on a Windows 2003 machine, the installation can stall if you are attempting to perform the installation from a network file system.

Solution: Windows 2003 includes security policy settings that can prevent some programs from being run from a network file system without permission. In this case, the WebSphere Application Server installation program is being denied access and is unable to complete. To allow such programs to run, update the security settings, as described in the following steps:

  1. Update the list of trusted sites on the Windows 2003 machine by adding the network file system containing the program you want to run.

    1. Open the Control Panel.

    2. Double-click Internet Options, and select the Security tab.

    3. Click Trusted sites, and then click Sites.

    4. Enter the network share, and click Add. Note that URL syntax is required for this information. For example, if you are connecting to share myshare on machine myhost, you would enter file://myhost/myshare.

    5. Click OK.

  2. Change the security level for the Trusted sites zone.

    1. On the Trusted sites page, click Custom Level.

    2. Locate Launching applications and unsafe files in the list of settings and click Enable.

    3. Click OK.

  3. Click OK to save the changes.

After completing these changes, you should be able to run the WebSphere Application Server installation program from a network file system.

 

Installation program displays a dialog for amqicsdn.exe file when installing on Windows 2003

When installing WebSphere Portal on a Windows 2003 machine from a network file system, the installation might display a dialog asking whether you want to open the amqicsdn.exe file.

Solution: Windows 2003 includes security policy settings that can prevent some programs from being run from a network file system without permission. In this case, the amqicsdn.exe file cannot run unless you perform one of the following steps:

  • Open the file during installation. If you are performing an interactive installation with the graphical installation program, click Open to allow the amqicsdn.exe file to run. The WebSphere Portal installation will continue.

  • Change the security settings. If you do not want to be prompted when the amqicsdn.exe file is run or if you intend to perform a silent installation, update the security settings, as described in the following steps:

    1. Update the list of trusted sites on the Windows 2003 machine by adding the network file system containing the program you want to run.

      1. Open the Control Panel.

      2. Double-click Internet Options, and select the Security tab.

      3. Click Trusted sites, and then click Sites.

      4. Enter the network share, and click Add. Note that URL syntax is required for this information. For example, if you are connecting to share myshare on machine myhost, you would enter file://myhost/myshare.

      5. Click OK.

    2. Change the security level for the Trusted sites zone.

      1. On the Trusted sites page, click Custom Level.

      2. Locate Launching applications and unsafe files in the list of settings, and click Enable.

      3. Click OK.

    3. Click OK to save the changes.

 

During uninstall, an exception is found in wpuninstalllog.txt

On Windows, we may see the following exception in the wpuninstalllog.txt:

ServiceException: (error code = -90001; message = "The configuration registry key is invalid. (1010)"; severity = 0)

Solution: This exception can be ignored. Uninstall will still complete successfully.

 

(HP-UX only) Non-root user receives warning that operating system is not supported

Non-root user does not have access to the /usr/sbin directory

Solution: To correct this problem, add /usr/sbin to PATH by typing on the command line PATH=$PATH:/usr/sbin/.

 

Related to UNIX

 

(Linux and UNIX only) Some Double Byte Character Sets (DBCS) fonts may be corrupted when installing from console or GUI interface

On some versions of UNIX and Linux, certain double-byte character sets can be corrupted during installation. When installing from the console, Korean, Traditional Chinese, and Simplified Chinese character sets are affected. Using the GUI installation, Traditional Chinese and Simplified Chinese character sets are affected.

Solution:

  • When installing, use the locales listed below to prevent corruption of the DBCS character sets.

  • The Korean character set locale only needs to be changed for console installation.

  • To change the system locale, enter:

    • On HP-UX and Red Hat, for example export LANG=zh_CN.utf8

    • On SuSE, for example 

      export LANG=zh_CN.utf8
export LC_CTYPE=zh_CN.utf8

Table 1. Correct character sets for console installation.
Console Install Simplified Chinese Traditional Chinese Korean
HP-UX 11v zh_CN.hp15CN zh_TW.big5 ko_KR.eucKR
SuSE SLES 8 zh_CN.gb18030 zh_TW ko_KR.euckr
  zh_CN.gbk    
  zh_CN    
Red Hat AS 3 Update 1 zh_CN.gb18030 zh_TW ko_KR.euckr
  zh_CN.gbk    
  zh_CN    

Table 2. Correct character sets for GUI installation.
GUI Install Simplified Chinese Traditional Chinese
HP-UX 11v zh_CN.hp15CN zh_TW.big5
    zh_TW.eucTW
SuSE SLES 8 zh_CN.gb18030 zh_TW
  zh_CN.utf8  
Red Hat AS 3 Update 1 zh_CN.gb18030 zh_TW
  zh_CN.utf8 zh_TW.euctw
    zh_TW.utf8

 

Related to AIX

 

Portal JVM exits with an error message on AIX

When you use large Java heaps for applications under AIX, you have to set an environment parameter to a specific value. Otherwise portal JVM exits with an error message.

Cause: The cause for this message is that you tried to allocate a Java heap for the Portal application that is larger than 1GB.

Solution: On 32-bit AIX systems the JVM has eight 256MB memory segments that it can use. With large heaps it may happen that this total of 2GB is not sufficient, as the real process size is not only determined by the Java heap but also by the system heap. In this case portal JVM exits with the following message:

Unable to map Java heap of requested size, perhaps the maxdata value is too large - see Java README.HTML for more information.
Unable to allocate an initial java heap of XXXXXXXXX bytes.
**Out of memory, aborting**
*** panic: JVMST016: Cannot allocate memory for initial java heap

In order to be able to have heaps larger than 2 GB, change the memory allocation scheme that the JVM uses. In the shell or the script that starts the portal enter the following line:

export LDR_CNTRL=MAXDATA=0x40000000

Where, the first digit after the x (in the example 4) determines the number of 256MB blocks available to the JVM. If the requested Java heap size is already larger, for example 1536MB, the JVM does no longer allocate the Java heap from those blocks but from free memory provided by the operating system.

Specify a suitable value for the system to avoid JVM startup problems caused by memory allocation requirements that are too high.

For more information on the JVM refer to IBM 's JVM diagnostics guide

 

Related to Linux

 

WebSphere Portal installation message states that the libraries for Motif and LessTif are missing when they are installed on the target system

Solution: Ignore this message and continue installation if you know the Motif or LessTif libraries are installed.

 

Related to Solaris

 

WebSphere Portal installation fails with an I/O error when installing from CD-ROM made from CD ISO image file

On Solaris, installation may fail if the CD-ROM created from a downloaded ISO image contains nearly 700 MB of data.

Solution: On the machine where you are installing WebSphere Application Server, copy the ISO image file to the hard disk, mount the ISO image, and run the installation program from the mounted image.

 

Errors indicating missing libraries are generated during installation on Solaris 9

During installation on Solaris 9, errors similar to the following errors might be generated in the installmessages.txt file:

EJPCA1514W: Discovery processing did not locate the X11R6 libraries
EJPCA1516W: Discovery processing did not locate all required libraries needed by the Productivity Components.
If these libraries are not installed, the Productivity Components may not function properly.
Discovery get_disc_ODCLibs_installed_is_current
EJPCA1516W: Discovery processing did not locate all required libraries needed by the Productivity Components. If these libraries are not installed, the Productivity Components may not function properly.

Solution: These errors do not affect the WebSphere Portal installation and can be ignored. The ODC (Productivity Components) libraries are required for ODC but are not necessary for WebSphere Portal to run.

 

Installer can fail to locate installed WAS on Solaris 9 (Solaris only)

Solution: If the installed WebSphere Application Server is not displayed in the list of existing WebSphere Application Server profiles, manually enter the directory path of the installed WebSphere Application Server in the entry field.

 

Related to i5/OS

 

iSeries login prompt freezes when installing remotely from Windows 2000 (i5/OS only)

When installing WebSphere Portal remotely from a Windows 2000 workstation, the iSeries login prompt might freeze and not allow the user to enter anything in the fields.

Solution: Click on the Windows desktop, then click an input area in the login prompt. If the problem persists, cancel the installation and try again.

 

Parallel Portlet Rendering gets pipe timed out error (i5/OS only)

There is a timer value for the pipes reading the portlets content. Our iSeries might require a higher rendering time frame. "PEEX0110E: The underlying pipe timed out while reading" is logged and "This portlet is temporarily disabled" is shown on the Portal page.

Solution: Run...

WPSconfig.sh -profileName profile_root action-update-portletcontainersevice -DparallelRenderingTimeOut=xxxxx

...from a Qshell prompt, where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile, parallelRenderingTimeOut is the property that specifies the timeout value in milliseconds, and xxxxx is the new value. The default is 4000ms. The parallelRenderingTimeOut property is not specified in the wpconfig.properties file and must be specified on the command line to change the value.

 

addNode fails with timeout exception (i5/OS only)

On some machine configurations, WebSphere Portal components can cause a timeout exception when a node is being added to the Network Deployment in a cluster environment.

Solution: The problem can be avoided by increasing the Network Deployment's ConnectionIOTimeOut value before running the addNode command. However, if addNode has already been run, remove the node and uninstall the applications associated with that node from the Network Deployment profile using the Network Deployment administration console. For instructions on removing a node, refer to the Remove nodes from a Network Deployment instance topic of the iSeries information center.

Once we have removed the node, add a new node by following the instructions in the Clustering and WebSphere Portal topic, making sure to follow the directions for increasing the Network Deployment's ConnectionIOTimeOut value.

 

Installation program does not start (i5/OS only)

The WebSphere Portal installation program might not start if host servers are not running on the iSeries system.

Solution: Start host servers by entering the following on an OS/400 command line: 

STRHOSTSVR SERVER(*SIGNON *RMTCMD)

After host servers have been started, try running the WebSphere Portal installation program again.

 

Deployment into a cluster fails with FTP errors (i5/OS only)

Deployment of WebSphere Portal into a cluster might fail with a variety of FTP errors due to a problematic entry in the resources.xml file.

Solution: Open the resources.xml file located in the directory...

portal_server_root/config/cells/cellname/nodes/nodename/servers/servername

...where cellname is the cell name, nodename is the node name, and servername is the application server name. Comment out the Samples URL Provider entry (last entry in the file). Save the file and attempt deployment again.

 

User ID no longer works (i5/OS only)

If we specify the wrong password for the user ID while running WPSconfig.sh i5/OS will render that user ID useless. See a system administrator in order to reactivate the user ID.

 

Related to ReleaseBuilder

 

ReleaseBuilder ignores deletion of attributes

If we delete values of fields in the portal administrative user interface, this might result in empty attributes in an XML export file. If you then use ReleaseBuilder to extract the changes between the configurations before and after the deletion of attributes, the difference file does not reflect the deletion of the attributes.

Cause: This is a known limitation. The ReleaseBuilder does not recognize the deletion of attributes. Refer also to We cannot delete attributes by using the XML configuration interface.

Solution: After we have completed the staging process with ReleaseBuilder, delete the attributes on the target portal system by using the same steps as you performed on your source system. Sample scenario and files: An example scenario and sample scripts are given in the following.

  1. Create configuration status export1 of your source portal by using the XML configuration interface.

  2. You modify the source portal by deleting the contents of fields in the portal administrative user interface that lead to attributes without a value in an XML export file.

  3. Create configuration status export2 of your source portal by using the XML configuration interface.

  4. Use ReleaseBuilder to extract the changes between export1 and export2.

The resulting differential file does not contain the deleted attributes. Sample XML script file snippet export1: 

<client action="update" domain="rel" manufacturer="dilbert" markup="html" markup-version="1.1" 
          name="puppy" objectid="M_CEENUPA000O7002A6CJO0Q1200" ordinal="250" version="1.0">
     <useragent-pattern>dogert</useragent-pattern>
     <client-capability update="set">dish</client-capability>
     <client-capability update="set">html</client-capability>
</client>
Sample XML script file snippet export2: 

<client action="update" domain="rel" manufacturer="dilbert" markup="html" markup-version="1.1" 
          name="" objectid="M_CEENUPA000O7002A6CJO0Q1200" ordinal="287" version="">
     <useragent-pattern>dogert</useragent-pattern>
     <client-capability update="set">dish</client-capability>
     <client-capability update="set">html</client-capability>
</client>
From the two exports above, ReleaseBuilder generates the following differential file: 

<?xml version="1.0" encoding="UTF-8"?>
<!-- IBM WebSphere Portal/6.0 build wp600_154 exported on Wed Apr 05 14:24:19 
     EDT 2006 from xyz -->
<request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" build="wp600_154" type="update" 
          version="6.0.0.0" xsi:noNamespaceSchemaLocation="PortalConfig_1.4.xsd">
     <portal action="locate">
          <client action="update" objectid="M_CEENUPA000O7002A6CJO0Q1200" ordinal="287"/>
     </portal>
</request>

If you use this ReleaseBuilder differential file to update the target portal, the name and version attributes of the client tag are not deleted on the target portal. To complete the update, you have to delete the attributes manually by using the same steps by which you deleted the attributes on the source portal.

 

Portal startup fails with WTRN0016E in logs

Problem:

After attempting to start IBM® WebSphere® Portal and access it in a browser, you get a "404 Initialization of services failed" message in the browser.

Cause:

In the SystemOut.log, you see the following cause of the startup failure:

[date/time] 1905742 TxServiceImpl E WTRN0016E: Exception caught during transaction service recovery!
com.ibm.ws.recoverylog.spi.LogCorruptedException
at com.ibm.ws.recoverylog.spi.LogHandle.openLog(LogHandle.java:399)
at com.ibm.ws.recoverylog.spi.RecoveryLogImpl.openLog(RecoveryLogImpl.java:471) at com.ibm.ws.Transaction.JTA.RecoveryManager.initialise(RecoveryManager.java:226)

Resolving the problem:

  1. Stop the WebSphere_Portal process

  2. Navigate to the following location and remove the WebSphere_Portal directory:

    <wp_profile root>/tranlog/cellname/nodename/WebSphere_Portal

  3. Restart the WebSphere_Portal server