Interwoven Turbo 2.0 for IBM - Release Notes for Windows.
Limitation
If you receive inconsistent results when running JSP pages from within a WORKAREA, ensure that the temp directory used by the JSP compiler (
The reason for this behavior is that the same sandbox web application may be connected to different workareas at different times. The content in each workarea could be the same, but if the JSP contains any page-relative URIs, the JSP compiler will prepend the web application URI to create a full URL in the compiled code and store the compiled JSP in this "temp" directory. In this circumstance, the JSP compiler may not recompile the JSP, even though it is rooted in a different WORKAREA. Therefore the full URL in the previously-compiled JSP code is no longer valid.
- Reminder
. Before installing Turbo for WebSphere Personalization on a TeamXpress (or TeamSite) server host, ensure that the metadata capture feature and TeamXpress Templating are configured properly. For detailed information on how to configure metadata capture feature, refer to the "Configuring Metadata Capture" section in the "Interwoven TeamXpress for Multiplatforms V1.1, WebSphere Edition Administration Guide" that matches your platform. For detailed information on how to configure TeamXpress Templating, refer to the "TeamXpress Templating" section in the "Interwoven TeamXpress for Multiplatforms V1.1, WebSphere Edition Templating and Deployment Guide".. - Limitation
The JAR file containing the contentContributionServlet.class file must be set up manually with the Turbo component. This is a required configuration procedure. - After the Turbo installation is complete, modify both of the
following properties in the
/properties/iww.properties fil
iwws.wpsUploadJar - Instead of the "none" value enter the full
path to the JAR file. On the Windows platform,
remember to use double back-slashes in the path.
iwws.pznClassPath - Instead of the "none" value enter the paths to
the personalization.jar, abrServer.jar and
abrClient.jar files separated by OS-specific path
separators. On the Windows platform, remember to
use double back-slashes in the path. Use OS-specifi
c path separators - colon (:) for Solaris and semi-colon
(;) for Windows. - Restart the IWWS web app after you have modified the iwws.properties file for the changes to take effect
- Modify the example pzn_config.xml files located in the
/iwws/example directory and in the root of the initial workarea to correctly register the Content Contribution Servlet. - Provide any value for the servlet web path. Make sure you record the same
value as "SERVLET_ALIAS" key in
/wpe/cfg/iwwpe.cfg file.
For example, for this servlet web path in the pzn_config.xml file:
- Record this "SERVLET_ALIAS" key in the iwwpe.cfg file if Auto-Invoker is used:
/servlet/contentContribution
Record this "SERVLET_ALIAS" key in the iwwpe.cfg file if Auto-Invoker is not used:
/contentContribution
- To propagate pzn_config.xml file modification to workareas other than the initial one, either copy the modified pzn_config.xml file to other workareas using OS commands or the GUI, or submit the modified file to the Staging area and then instruct the users to execute a "Get Latest" command to get the pzn_config.xml file from Staging
- If you have any sandbox pools created before you completed all of the above modifications (for example created as a part of Enterprise Information Portal 7.12 and Content Manager 7.11 Turbo install) - destroy them. Such sandboxes will not support WebSphere Personalization Turbo component.
- Using the "sandBoxAdmin" utility, create lightweight or heavyweight sandbox pools after you have completed the above modifications
- When creating a lightweight sandbox pool, provide the pzn_config.xml file
from
/iwws/example directory as the "-configFile" parameter.
Workarea owners should use the pzn_config.xml in the root of their workarea when allocating a heavyweight sandbox for the workarea. - Limitation.
If your TeamXpress (or TeamSite) server is on the Windows platform, you must configure the "iwatsub" command trigger to run as a service. For detailes on how to configure command triggers, refer to the "Interwoven TeamXpress for Multiplatforms V1.1, WebSphere Edition, Command-Line Tools Reference Guide".
For detailes on how to configure "iwatsub" command trigger for WebSphere Personalization Turbo, refer to "Interwoven Turbo Product Guide for IBM WebSphere Personalization" - Issue.
The "Interwoven Turbo Product Guide for WebSphere Personalization" references the sample application called "YourCo Toys" which is supplied with WebSphere Studio version 3.5.2.
Instead of the "Personalization.wsr" archive from the WebSphere Studio distribution, obtain the archive from the following link:
http://www.ibm.com/software/webservers/teamxpress/download/
You must use this "YourCo Toys" sample instead of the original in order for WebSphere Personalization Turbo to work. - Bug #15890
If your TeamXpress (or TeamSite) server is on a Solaris platform, after installing Turbo for WebSphere Personalization, the first line of/wpe/bin/iwwpe_submit.ipl script does not contain the correct path to the iwperl binary.
Remedy:
Modify the first line of the script manually, as in the example below:
Original line: #!__IW_HOME__/iw-perl/bin/iwperl -w
Modify to (assuming theis /usr/local/iw-home):
#!/usr/local/iw-home/iw-perl/bin/iwperl -
- Reminder
This Turbo product is for use on the Windows platform only. Do not attempt to install any components for this Turbo product on a Solaris platform. - Instructions for using EIP with data stores other than IBM Conent
Manager with this Turbo product
The Interwoven Turbo 2.0 Product Guide for EIP and Content Manager specifies to include a list of required JAR files in the servlet classpath for the "retrieveDoc" servlet ("Customizing RetrieveDoc Servlet" section in Chapter 4). Customers will also need to include these jar files in the TeamXpress Templating Client configuration file named "tst.lax", located in the root directory of the TeamXpress Templating Client installation.
Below are the the paths to JAR files where %CMBROOT% is the root directory of the EIP Server installation:
%CMBROOT%\lib\ics.jar
%CMBROOT%\lib\xerces.jar
%CMBROOT%\lib\lotuskms.jar
%CMBROOT%\lib\essrv.jar
%CMBROOT%\lib\esclisrv.jar
%CMBROOT%\lib\db2java.zip - Bug #15886
The Interwoven Turbo 2.0 for IBM Enterprise Information Portal 7.12 and IBM Content Manager 7.11 installation on a WebSphere Application Server host clears the classpath added by WebSphere Personalization into "Default Server", "Command line arguments" parameter and replaces it with "-Xmx156".
Remedy:
After you install the Interwoven Turbo 2.0 for IBM Enterprise Information Portal 7.12 and IBM Content Manager 7.11 on a WebSphere Application Server host, do the following:
- Open the WebSphere Advanced Adminstrative Console.
- Expand the node.
- Click on "Default Server".
- In the right panel of the console find the "Command line arguments:" text box.
- f you're on the Windows platform, type the following, starting at
the beginning of the text field, leaving "-Xmx156" intact (also leave
a space between the classpath and "-Xmx156"):
-classpath\lib\personalization.jar; \lib\abrServer.jar; \lib\abrClient.jar
If you're on the Solaris platform, type the following, starting at the beginning of the text field, leaving "-Xmx156" intact (also leave a space between the classpath and "-Xmx156"):
-classpath/lib/personalization.jar: /lib/abrServer.jar: /lib/abrClient.jar - Click the "Apply" button at the bottom of the right panel.
- Restart the "Default Server", so the changes can take effect.