Read part one of this 2-part article
This article explores using MySQL as the database engine where the
application is developed using BEA WebLogic Workshop 8.1 and deployed to BEA
WebLogic Server 8.1. Using an archetypical J2EE architecture, I evaluate the
impact of using MySQL from various aspects such as choosing the correct
version of MySQL, setting-up the server, and making development adjustments.
The information presented here not only enhances the readers' understanding
of the tools and technologies utilized, but also saves countless hours. Even
readers who employ different database technologies will find the information
and material useful.
Last month (WLDJ, Vol. 3, issue 4), I discussed how to select the "right"
version of MySQL and described various changes to the WebLogic Domain
Configuration to support key J2EE technologies such as Java DataBase
Connec... (more)
Read Part 2 of this 2-part article
MySQL is a small, fast, and efficient database. This article discusses
leveraging MySQL as the database with BEA WebLogic Server 8.1.
We will look at using MySQL as the database engine where the application is
developed using BEA WebLogic Workshop 8.1 and deployed to BEA WebLogic Server
8.1. Using an archetypical Java 2 Enterprise Edition (J2EE) architecture, I
will evaluate the impact of using MySQL from various aspects such as choosing
the correct version of MySQL, setting up the server, and making development
adjustments. The impact on develop... (more)
In my previous article (WLDJ, Vol. 3, issue 8), I gave you a detailed
overview of the different strategies available for domain creation and
configuration and evaluated manual and templating options. In this article, I
employ tools like WLShell, WebLogic Scripting Tool, Silent Scripts, and Ant
for domain configuration. These tools leverage simple, high-level scripting
languages.
Note: This article relies heavily on the common steps such as Domain
Creation, Database Configuration, and Verifying the Domain Configu-ration
described in part 1.
Scripting Language
There are many ques... (more)
A portlet is a Web component that generates fragments - pieces of markup
(e.g., HTML, XML) adhering to certain specifications. Fragments are
aggregated to form a complete document.
This article introduces the Java Specification Request (JSR) 168 on Java
Portlets. It illustrates the creation of Java Portlets using BEA WebLogic
Workshop 8.1 SP2 and the deployment of these portlets on BEA WebLogic Portal
8.1 SP2. I'll look at essential concepts such as portal, desktop, and
portlets and describe in detail the various portlet modes and window states.
I'll also look at designing, impl... (more)
A domain contains configuration information for a BEA WebLogic Server
instance. It has configuration information about servers, clusters, and
machines. A domain also contains configuration information about resources
such as Java DataBase Connectivity (JDBC) connection pools, JDBC data
sources, connection factories, and Java Message Service (JMS) queues. In
addition, it contains configuration information about the applications
deployed to the instance. The domain configuration information is persisted
in a config.xml file. In this article, I evaluate various strategies for
WebL... (more)
Prakash Malani has extensive experience in architecting, designing, and developing object-oriented software and has done software development in many application domains such as entertainment, retail, medicine, communications, and interactive television.He practices and mentors leading technologies such as J2EE, UML, and XML. Prakash has published various articles in industry- leading publications.
David Lucas
Shaul Efraim
Terence Martin Breslin
Cory Marchand
David Hughes
James Carlini
John Iffert
Dan Stolts
Joe Zeto
