Welcome!


Vol: 2 Iss: 11

Read Back Issues

This month's article is again inspired by an interesting design discussion posted on the weblogic.developer.transaction newsgroup. (Ever get the feeling I'm running short of inspiration? Ideas for new articles always welcome!)
I currently find myself on a consulting engagement for a large, multimillion-dollar, enterprise- wide Web services project for a major Fortune 500 firm. It's a golden opportunity to see first-hand the development of a bleedingedge enterprise service bus (ESB), complete with hundreds of...
Once your BEA WebLogic Server domain is configured, you need to deploy your application. This is the second in a series of articles on BEA WebLogic Server administration and management for developers.
BEA WebLogic Server domains in largescale enterprises satisfy a broad range of requirements, including highly scalable application deployments, integration of various boundary systems, and high availability setups. As a natural consequence the level of the domain's complexity rises.
When independent business components must be executed simultaneously, the parallel processing of application business logic has a direct impact on the performance of the system; however, parallel processing at the application level historically has been challenging to implement.
BEA WebLogic Workshop 8.1 provides a wide range of tools for creating Web server applications. Components integrated using Workshop's extensible component model include Java controls, page flows, and source and design views that are available to any software vendor or Web application d...
While security is a concern throughout an application, it is especially important for Web application components. An insecure Web application leaves a Web site vulnerable to many attacks, some that require nothing more than an Internet browser and a small amount of knowledge.
The need for a server-side JVM is evident. The increase in the number of Java applications on the servers, and the exponential rise in the number of clients accessing these Java applications, brings forth the shortcomings in the traditional Java VMs, which are more tuned towards client...
Suppose you've developed your suite of applications, standardized to J2EE, and are now awaiting the J2EE benefits for monitoring these applications. You have a consistent series of applications, so adding advanced monitoring capability should be fairly straightforward.
So you've been told to diagnose a performance problem in a WebLogic J2EE application. Because Java systems are so complex, this can be a bit like diagnosing a rare illness.