An enterprise development project deploying to the WebLogic platform needs to
maintain several different domain configurations during the project's
development, test, and deployment phases.
Version control and continuous rollout of ever-changing domain configurations
to the different environments can be a challenging task. The Domain
Configuration Wizard can help alleviate these challenges, because there is
more to this Wizard than immediately meets the eye.
The WebLogic domain has grown from a non-existent concept in WebLogic 5.1 to
become the foundation of all enterprise applications running on the latest
version of the WebLogic Platform. A domain defines vital parts of an
application's runtime environment, such as deciding on whether or not the
application will run in a cluster, and which physical databases the
application will use through the connection pool def... (more)
More and more web sites are using portal functionality. Portals are perfect
for building mashups and interactive web sites offering a lot of
functionality in a single web page. Content is a vital part of most portals.
Content management integration in portals has traditionally been treated
different by different vendors and frameworks. Web Content Management System
(CMS) vendors have tried to provide Portal like functionality in their
systems. Portal vendors have been bundling simple Web Content Management
Systems with their Portal products. Those of you who have experience with ... (more)
With the advent of BEA WebLogic Portal 8.1, a host of new technologies was
introduced. These are, among others: Java Page Flow with annotations, Java
Controls, and a new IDE to support it. Online tutorials were also thrown into
the package to show how the new technologies were supposed to be put to work
in the most effective way.
We have used BEA WebLogic Workshop, Java Page Flow, and Java Controls to
create a large portal application that consists of about 200 pages covering
five different functional areas. Before we started we did an evaluation of
the technologies. We aimed to... (more)