IBM Rational Application Developer Version 6.0 for
IBM Rational Deployment Toolkit for WebLogic
feature - release notes
Welcome to the IBM® Rational® Deployment
Toolkit for WebLogic® feature,
powered by Eclipse technology release
3.0.1.
Table of contents
1.0 About this
release
2.0 Installation
information
3.0 Known limitations,
problems, and workarounds
4.0 Documentation updates
5.0 About Eclipse
6.0 Notices and trademarks
1.0 About this release
The IBM Rational Deployment
Toolkit for WebLogic Server feature provides support for the BEA
WebLogic Server®. The feature adds support for BEA WebLogic
Server configuration, deploying and testing J2EE applications on them.
The function is deeply integrated with the existing IBM Rational Application
Developer EJB and Web tools and provides similar function and
usability. This toolkit enables you to deploy EJBs on a BEA WebLogic
Server.
2.0 Installation
information
For information about
installing Rational Application Developer, refer to the product
Installation
Guide.
For information about installing the IBM Rational Deployment Toolkit for WebLogic Server feature, refer to
www3.software.ibm.com/ibmdl/pub/software/rationalsdp/rad/60/install_instruction/WLToolkit60/install.html
2.1 Hardware requirements
Refer to the Rational Application Developer Installation
Guide for product hardware
requirements .
2.2 Supported software
For software supported by Rational Application Developer, refer to the
product Installation Guide for
details.
The following software prerequisites exist for this feature:
- IBM Rational Application Developer for WebSphere®
Software 6.0.0
or IBM Rational Software Architect 6.0.0.
- BEA
WebLogic Server 8.1 SP3, 7.0 SP5, 6.1 SP7 (not supported on Windows
XP). These must be installed locally even if the target deployment
server is not local.
- Windows 2000, Windows XP
3.0 Known limitations,
problems, and workarounds
Release notes cover
release-specific information (such as problems and
limitations) that did not become available until after the product
documentation was finalized. Bug tracking numbers follow in brackets [].
For information about known problems and workarounds in the Eclipse
base, refer to readme_eclipse.html located in the eclipse\readme
subdirectory of the product installation directory. This information is
only available in English.
3.1 Server configurations
- Reusing WebLogic domains for server configurations or
sharing domains among more than one server configuration is not
recommended, as it will cause publishing and deployment problems. [1737]
- Using
the WebLogic administration console to remove applications deployed
with IBM Rational Application Developer will cause publishing and deployment
problems. [1655]
- The WebLogic Domain Configuration Wizard
only runs in GUI mode on some Unix systems. It has been tested using
the TWM window manager with the GNOME desktop on Red Hat LinuxTM
7.2.
[4304]
3.2 Publishing to server
- The server synchronization state will still read
'Synchronized' if a change is made to a project that is associated with
a server configuration. The state only changes if the server
configuration itself needs to be republished. [1156]
- The
server publish preferences should be set to use Publish All or Smart
Publish. Prompt user publishing method does not work. [2670]
- Unable
to deploy application because of FileNotFoundException
META-INF/ejb-jar.xml not found in jar. Actually caused by concurrent
access problem when a deploy, redeploy, or undeploy action is
interrupted by another action or a shutdown. [1639, 1700]
- Unable to redeploy EAR after adding an EJB while the server is
running. [3996]
3.3 Server startup
- WebLogic Server 6.1 is not supported on Windows XP due to issues
with authentication. [7491, 7408, 7382, 7381]
- WebLogic
Server 6.1 stays in "Starting" state and never progresses to "Started"
on Windows NT®. Upgrade to WebLogic Server 6.1 SP4.
- An
UnavailableException may occur when the server is started if a client
attempts to access the web container before it is fully initialized.
May cause problems for Run on Server which causes a server restart. A
subsequent Run on Server should succeed. [2446]
- The error
message 'found no context for "/"' will appear if no web application
was deployed and bound to the default context. [4013]
- WebLogic Server will not start if the PATH system environment
variable is too long (greater than 1024 characters). [2420]
- Restarting
a local WebLogic Server 6.1 while it is running does not work. The
workaround is to check the debug view to ensure the server process is
terminated before restarting the server. [4056]
- An
enterprise application project with a different server runtime version
than the WebLogic server can incorrectly be configured to the server by
"Run on Server". [7475]
3.4 Server editor
- Cannot undo port number changes if the port number is invalid
(must be a positive integer or –1; 0 is not allowed). [1652]
- You
are asked to save changes to the EJB Deployment Descriptor Editor or
the Server Editor after adding/removing an enterprise application to a
server and publishing the server. [6064]
3.5 EJB to RDB mapping
- EJB Deployment Descriptor editors and EJB to RDB Mapping
editors sometimes open in the dirty state. This indicates that the
model loaded in memory has been modified in some way. Save the editor
to avoid any potential model synchronization problems. [1647, 2490]
- The
scenario of generating a top-down map, then using the tables created by
the Mapping Editor's generated DDL to do a bottom-up mapping is
unsupported. The toolkit will incorrectly fill out the
tag in weblogic-cmp-rdbms-jar.xml. [4931]
3.6 EJB management
- An exception occurs when importing an EAR that contains both a
Web project and an EJB project with an EJB. [7486]
- Adding
and removing beans from an EJB module may fail to synchronize the
WebLogic-specific descriptors if the enterprise application has been
recently removed from a server configuration. [3400, 3453, 3454]
- When
removing a CMP field from a CMP 1.1 bean in an EJB 2.0 module, a
weblogic-cmp-rdbms-jar.xml with no beans is incorrectly created and the
CMP field is not removed from weblogic-cmp11-rdbms-jar.xml. [4353, 6061]
- An exception occurs when creating a CMP 1.1 bean in an EJB 2.0
project. [7406]
3.7 Universal Test Client
(UTC)
- Local home interface lookup in WebLogic Server 8.1 and 7.0
does not work in the Universal Test Client due to the way JNDI is
implemented in WebLogic Server. [1631]
- JNDI navigation via
hyperlinks in the JNDI Explorer is not supported due to the difference
in WebLogic Server's implementation of JNDI. To use the JNDI Explorer,
perform a lookup on the fully-qualified JNDI name.
- If the
server is republished while the Web browser is open to the Universal
Test Client, it must be reinitialized by performing a Run on Server or
manually setting the JNDI properties. [2362]
3.8 JSP debugging
- Stepping over JSP lines is limited to JSP scriptlet and JSP
declaration code. [3987]
- Stepping in and out of JSP lines outside of JSP scriptlet and JSP
declaration code is not supported.
- The
debugger will not be able to identify the sources for JSPs when
debugging if a situation causes the server to change state to "needs
republish", such as modifying sources in the deployed application.
[4058]
3.9 EJB validation
- Server projects need to auto-validate in order for the
WebLogic Server Configuration Validator to provide useful warning
messages when applications are not fully enabled for WLS. [1740]
- EJB inheritance is not supported in WebLogic Server but it passes
ejbc validation. [7402]
- After
deleting CMP 1.1 beans from an EJB 2.0 project, a
weblogic-cmp11-rdbms-jar.xml is incorrectly created after validation.
[6062]
3.10 CMR
- WAS EJB 1.1 relationships: Creating WAS EJB 1.1
relationships in a WebLogic-enabled EJB project will cause resource
save problems. [2331]
- EJB 2.0 relationships: Relation with two identical relationship
role names is allowed. [1643]
3.11 Scenario applications
YourCo scenario may have problems with a TLD. To resolve
the problem edit the taglib.tld file in WEB-INF/lib/jspsql.jar,
removing all the empty <teiclass> tags. Re-package and re-deploy
the application. [2347]
3.12 DDConverter
DDConverter is unable to convert an EJB JAR that contains
both CMP and BMP beans. The workaround is to have CMPs and BMPs in
separate EJB modules. [4235]
4.0 Documentation updates
Both the product
home page and IBM
developerWorks have Library
sections that provide updates to tutorial documents and other
documentation.
The IBM Rational zone at www.ibm.com/developerworks/rational
offers technical articles, "how to" information, tutorials, samples,
and previews of new technology.
4.1 Creating a
WebLogic server runtime
After IBM Rational Application Developer has restarted, you can create a runtime
for a BEA WebLogic Server.
- From the menu, go Window > Preferences > Server to
open the Server page.
- Ensure Create server resources in workspace is checked.
This is required so the toolkit has access to the server resources.
- In the left pane, expand Server and select Installed
Runtimes to open the Server Runtimes page.
- Click Add to open the Server Runtime wizard.
- Select the desired version of WebLogic Server, for e.g. BEA
WebLogic Server v7.0, and click Next.
- Enter the appropriate paths and click Finish.
4.2 Creating an EJB project
- Switch to the J2EE perspective.
- Select File > New > EJB Project.
- Click Show Advanced if the advanced details are hidden.
- Enter an EJB project name. Use the default EAR project name
setting or define a new one.
- Set the EJB version to 2.0 and select a WebLogic
Server as the Target server.
- Deselect Create an EJB Client JAR Project as this is not
required.
- Click Finish to complete the EJB project creation.
- After creating an EJB project, it is recommended you turn off
automatic validation due to performance issues (Window >
Preferences > Validation).
4.3 Creating an EJB
- Select File > New > Enterprise Bean to create an
EJB.
- Select your EJB project if not already selected.
4.3.1 Creating a session bean:
- Select Session bean and enter a Bean name.
- Define com.ibm.test as the Default package.
- Click Next. Check the Local client view check box
if required.
- Click Finish to complete the Session Bean creation.
4.3.2 Creating a CMP 2.0 bean:
- Select Entity bean with container-managed persistence (CMP)
fields. Ensure CMP Version is 2.x.
- Enter a Bean name and define com.ibm.test as the
default package.
- Click Next. Check the Remote client view check
box if required. The remote interface defines the business methods that
can be called by a client.
- Create additional persistence fields by clicking the Add
button.
- Click Finish to complete the CMP bean creation.
4.4 Validating the EJB
project
- In the Project Explorer view, expand the EJB project. A folder wls81,
wls70, or wls61 is created containing the
deployment descriptors specific to BEA WebLogic Server.
- Right-click on the EJB project and select Run Validation
to invoke the ejbc tool to validate and generate code. The
console should display ejbc successful.
4.5 Updating
deployment descriptors
- In the Project Explorer view, right-click on the EJB project and
select Open With > Deployment Descriptor Editor.
- View the WebLogic page (e.g. WebLogic 7.0).
- Select the CMP bean and enter the Data Source Name Test.
- Enter
the Bean's JNDI name. The JNDI name field is the value you will use for
lookups in the Universal Test Client. Those values should already be
populated.
- Save the editor.
4.6 Generating EJB to
RDB mapping
- In the Project Explorer view, right-click on the EJB project and
select EJB to RDB Mapping > Generate Map.
- Select Create a new backend folder and click Next.
- Select Top Down and click Next.
- Select your database from the Target Database drop-down
list (e.g. DB2 Universal DatabaseTM V8.1).
- Enter SAMPLE as the Database name and ensure Generate
DDL is checked.
- Click Finish.
4.7 Creating a
database schema and tables
- In the Project Explorer view, the generated DDL script is found
under the EJB project as ejbModule/META-INF/Table.ddl.
- Run the DDL script against your target database to create the
tables and associations.
4.8 Creating a domain
configuration
Note: The following
instructions are specific to WebLogic Server 7.0, however, the overall
steps can also be used for WebLogic Server 6.1 and 8.1. Refer to the
WebLogic documentation for further information.
- Go to Start > Programs > BEA WebLogic Platform 7.0
and select Domain Configuration Wizard.
- Select the template WLS Domain.
- Enter the domain name testdomain and click Next.
- Select Single Server and click Next.
- Specify a domain directory and click Next.
- Enter the server name testserver and click Next.
- Enter a User Name and Password, and then proceed
to create the domain.
4.9 Creating a server
- In the J2EE perspective, open the Servers view.
- Right-click within the view and select New > Server.
- In the Server type field, select WebLogic v7.0 Local
Server (the version of testdomain) (or WebLogic v7.0
Remote Attach Server if you plan to run on a remote server). Click Next.
- Enter the domain name testdomain. The server name testserver
should appear.
- Enter the Server Administrator Username and Password.
- Click Finish to create the server.
4.10
Defining a connection pool and data source
Note: The following
instructions are specific to WebLogic Server 7.0, however, the overall
steps can also be used for WebLogic Server 6.1 and 8.1. Refer to the
WebLogic documentation for further information.
- In the Servers view, double-click WebLogic v7.0 Local Server
@ localhost to open the Server Editor.
- In the Classpath page, click Add External Jars to add
database JARs of the server you are running. For DB2®
users, add C:\Program
Files\IBM\SQLLIB\java\db2java.zip (and C:\Program
Files\IBM\SQLLIB\java\db2jcc.jar for DB2 8.1) to the classpath.
- Save the editor and start the server.
- Once the server is started, click Launch WebLogic Server
console from the Overview page of the Server Editor.
- Enter the Server Administrator username and password defined
previously.
- Under the Services Configurations section, click Connection
Pools to configure a new connection pool.
- Click Create and then select the Targets tab to
enable the connection pool testPool for the target server testserver.
- Navigate back to the homepage by clicking the Home icon in the
top-right corner of the page.
- Under the Services Configurations section, click Tx
Data Sources to configure a new JDBC TX Data Source.
- The Data Source Name field in the EJB project's Deployment
Descriptor editor (previously defined in Updating deployment descriptors)
must match the JNDI name of the data source.
- Click Create and then click the Targets tab to
enable the Tx Data Source Test for the target server testserver.
- Close the WebLogic Server console.
4.11 Adding the
EAR project to the server
- In the Servers view, right-click on WebLogic v7.0 Local
Server @ localhost and select Add and remove projects.
- Select the EAR project and click Add to configure it to
the server.
- Click Finish.
4.12
Running and testing an Enterprise JavaBean
- In the Project Explorer view, right-click on the EJB project and
select Run > Run on Server.
This will start the WLS server and launch the Universal Test Client.
There is no need to generate deploy code in the Run on Server step for
EJB projects since validation already generated the deploy code.
- In
the Universal Test Client, view the JNDI Explorer page and enter the
JNDI name for the session bean and/or CMP bean to perform a JNDI lookup.
5.0 About Eclipse
Eclipse is an open-source project that delivers a framework for
developing plug-ins that
make it easier to create, integrate, and use software tools. By
collaborating and sharing core integration technology, tool producers
can concentrate on their areas of expertise and the creation of new
development technology. The Eclipse platform is written in the JavaTM
language and comes with extensive toolkits and examples for
construction plug-ins. It has already been deployed on a range of
operating system environments including LinuxTM, Mac OS X,
QNX, and
Windows®-based systems. Full details of the Eclipse
community and white
papers documenting the design of the Eclipse platform are available at www.eclipse.org.
Plug-in
tools from other vendors, also built using the open-source Eclipse
platform, integrate with the Rational Application Developer environment to provide
additional value.
6.0 Notices and trademarks
U.S. Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This information was developed for products and services offered in
the U.S.A. IBM may not offer the products, services, or features
discussed in this documentation in other countries. Consult your local
IBM representative for information on the products and services
currently available in your area. Any reference to an IBM product,
program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any IBM
intellectual property right may be used instead. However, it is the
user's responsibility to evaluate and verify the operation of any
non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject
matter described in this documentation. The furnishing of this
documentation does not give you any license to these patents. You can
send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information,
contact the IBM Intellectual Property Department in your country or
send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or
any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or
typographical errors. Changes are periodically made to the information
herein; these changes will be incorporated in new editions of the
publication. IBM may make improvements and/or changes in the product(s)
and/or the program(s) described in this publication at any time without
notice.
Any references in this information to non-IBM Web sites are provided
for convenience only and do not in any manner serve as an endorsement
of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at
your own risk.
IBM may use or distribute any of the information you supply in any
way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for
the purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this one)
and (ii) the mutual use of the information which has been exchanged,
should contact:
Intellectual Property Dept. for Rational Software
IBM Corporation
3600 Steeles Avenue East
Markham, Ontario
Canada L3R 9Z7
Such information may be available, subject to appropriate terms and
conditions, including in some cases, payment of a fee.
The licensed program described in this documentation and all
licensed material available for it are provided by IBM under terms of
the IBM Customer Agreement, IBM International Program License Agreement
or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating
environments may vary significantly. Some measurements may have been
made on development-level systems and there is no guarantee that these
measurements will be the same on generally available systems.
Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should
verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the
suppliers of those products, their published announcements or other
publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other
claims related to non-IBM products. Questions on the capabilities of
non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are
subject to change or withdrawal without notice, and represent goals and
objectives only.
This information contains examples of data and reports used in daily
business operations. To illustrate them as completely as possible, the
examples may include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the
names and addresses used by an actual business enterprise is entirely
coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source
language, which illustrates programming techniques on various operating
platforms. You may copy, modify, and distribute these sample programs
in any form without payment to IBM, for the purposes of developing,
using, marketing or distributing application programs conforming to the
application programming interface for the operating platform for which
the sample programs are written. These examples have not been
thoroughly tested under all conditions. IBM, therefore, cannot
guarantee or imply reliability, serviceability, or function of these
programs. You may copy, modify, and distribute these sample programs in
any form without payment to IBM for the purposes of developing, using,
marketing, or distributing application programs conforming to IBM's
application programming interfaces.
Each copy or any portion of these sample programs or any derivative
work, must include a copyright notice as follows:
(C) (your company name) (year). Portions of this code are derived
from IBM Corp. Sample Programs. (C) Copyright IBM Corp. 2000, 2005. All
rights reserved.
If you are viewing this information softcopy, the photographs and
color illustrations may not appear.
Programming interface information
Programming interface information is intended to help you create
application software using this program.
General-use programming interfaces allow you to write application
software that obtain the services of this program's tools.
However, this information may also contain diagnosis, modification,
and tuning information. Diagnosis, modification and tuning information
is provided to help you debug your application software.
Warning: Do not use this diagnosis, modification, and tuning
information as a programming interface because it is subject to change.
Trademarks and service marks
The following terms are trademarks of International Business
Machines Corporation in the United States, other countries, or both:
- DB2
- DB2 Universal Database
- IBM
- Rational
- WebSphere
Java and all Java-based trademarks are trademarks of Sun
Microsystems, Inc. in the United States, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the
United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United
States and other countries.
Linux is a trademark of Linus Torvalds in the United States, other
countries, or both.
WebLogic and all WebLogic-based trademarks are trademarks of BEA Systems, Inc. in the United States, other countries, or both.
Other company, product or service names, may trademarks or service
marks of others.