This article is the second of two on best practices in building business
processes on BEA WebLogic Integration 8.1. The first installment (WLDJ, Vol.
3, issue 6) focused on team development and maintenance best practices. In
this article, we will focus on best practices in building business processes
with scalability, recovery, exception handling, guaranteed delivery, and high
performance. This article is intended for the developers and architects of
WLI applications. Process VersioningBest Practice
Version the process files.
Reason
It's easy to overlook versioning because the process works without any
version. But it is really important to version the processes, especially for
long-running processes. When a process is upgraded, the in-flight instances
will either be abo... (more)
Working as a BEA consultant, I've helped customers successfully design and
deploy applications on various versions of the WebLogic Server (WLS). BEA has
been supporting container-managed persistence (CMP) entity beans since EJB
1.0, and a few of our customers have used them. Unfortunately, some used them
without understanding the ramifications; others heard about performance
constraints ... (more)
A business process in the real world typically is never done end-to-end by a
single employee. It usually involves multiple employees/back end systems
handing over work, similar to a 4x100 track relay where batons are passed
between the athletes. The employees/back end should be passively notified of
their tasks rather than actively waiting. BEA WebLogic Workshop provides a
great framewor... (more)