Refer to the online help provided with WebSphere Application Server v6.0 for full details on configuring and deploying the default messaging provider when testing Java Messaging Service (JMS) applications against a v6.0 server, and for details on configuring and deploying a Service Integration Bus when testing Web services applications against a V6.0 server
For most Linux systems, the default file descriptor limit per process is 1024. You need to increase it to at least 2048. Please consult with your system administrator to increase the limit.
If you install the product as root and run as a non-root user, you must change the permissions for the Auction database folder. The database is in sdpinstall/rwd/eclipse/plugins/com.ibm.etools.auction.sampledb/db. To set the permissions, execute chmod 777 AUCTION60.
The product supports a different plug-in classloading mechanism which uses JXE files instead of JAR files. The benefits of using JXE files are as follows:
- Improved startup time
- Reduced memory consumption
- Increased memory sharing between multiple product instances
The disadvantages of using JXE files are as follows:
- Line numbers might not appear in plug-in stack traces
- A limited number of third-party plug-ins that function properly in Eclipse v3.0.x might not load in the product
To temporarily disable JXE support to diagnose either issue, start the product with the following additional startup arguments:
-vmargs -Dosgi.adaptor=org.eclipse.core.runtime.adaptor.EclipseAdaptorWindows: Add the above arguments to the Target field of the product shortcut.
If you find a third-party plug-in that functions properly in Eclipse v3.0.x and does not load in the product with JXE enabled, but loads with JXE disabled, contact IBM support and report this problem. Remember to revert to the original startup arguments (i.e. enable JXE) after you report the problem.
A default installation of SLES9 seems to install an /etc/hosts file with a line like the following
to support IPv6 networking. This prevents BeanInfo (a name for JavaBean introspection functionality provided the org.eclipse.jem plugin) from connecting (via a localhost socket) to the JVM which it launches. To enable correct BeanInfo operation, remove 'localhost' from that line, e.g.- ::1 localhost ipv6-localhost ipv6-loopback
Do not remove the required line (which should also be in /etc/hosts by default)+ # ::1 localhost ipv6-localhost ipv6-loopback + ::1 ipv6-localhost ipv6-loopback
127.0.0.1 localhost
You can apply skin manifests to the product, as described in the Eclipse SWT FAQ at http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-swt-home/faq.html#xpthemes. However, the product may not display properly. To avoid this issue, do not apply skin manifests to the product.
IBM Rational 5.x Legacy Integrated Test Environments provides you with a sample response file called responsefile.txt located in the IBM_WAS_LTE\util directory. The following table shows the response file options and their corresponding entries in the response file.
Table 1. List of response file options.
Feature Response file entry Product installation directory installLocation WebSphere Application Server Version 5.1 feature_was51_linux.active
WebSphere Application Server Express 5.1
feature_wasexp51_linux.active
For usage, follow the instructions provided in the "Silently installing additional Rational Software Architect features" section of Chapter 5 in the install guide, "Installing and uninstalling Rational Software Architect for Linux".
Return to the main readme file