With software architecture evolving toward SOA, many projects in this space have encountered challenges associated with accessing data. As has been said, 'The way an organization thinks about applications and data must evolve - it must stop thinking about data as a second-class citizen that only supports specific applications and begin to recognize data as a standalone asset that has both value and utility.'

Database locking strategies is one of the most complex areas of application development -- and one of the most critical for reliable application performance and behavior. The basic issues, common strategies, and general recommendations on when and how to use different locking strategies are outlined in this article.

This article shows you how to connect non-SOAP HTTP service requesters and providers to the IBM® WebSphere® Application Server V6 Service Integration Bus. This lets requesters and providers leverage the integration capabilities of an enterprise service bus.

Running applications in WAS for z/OS lets you take advantage of the z/OS built-in Quality of Service features such as reliability, availability, scalability, and serviceability. However, the solution could be very expensive.

Large session objects decrease the JVM memory available for creating and executing application objects. As a result, performance can degrade as the decreased available heap memory leads to more frequent garbage collection.

Mixed-mode deployments where the data center has a mixture of different technology platforms, hardware, and software and where those platforms interoperate together to deliver software applications is the norm rather than an exception.

When people talk about scalability, they are usually referring to how well an application performs with an ever-increasing load. Another type of scalability that needs attention during an application's life cycle is build scalability, or how well an application's build and deployment scales with ever-increasing complexity and components.

Enterprises need to think about a performance management solution that will give them real-time end-to-end visibility into the entire Web application environment from browser to back-end systems, including messaging middleware such as WebSphere MQ. By providing an application-centric view of MQ-connected environments, such a tool allows application administrators to work collaboratively with MQ administrators without displacing existing MQ monitoring tools. The result is an effective, seamless process for detecting, triaging, and diagnosing application performance issues in complex interconnected environments.

This two-part article discusses application deployment, particularly automated updates, to IBM WebSphere Application Server in a large-scale enterprise environment. It applies to Application Server versions 5.0, 5.1, and 6.0, and also includes an introduction to a few version 6.0 enhancements. This article is not intended to be used as a reference for all the details of Application Server administration, but it does describe the key concepts used and contains a list of references.

In an enterprise WebSphere 5.1 deployment, the application business logic is developed as Enterprise JavaBeans (EJB). In many situations, there exists a need to execute standalone Java programs that run outside the container. To reuse the business logic present in the EJBs, the application client can use the EJB resources that are provided by the application server.

This two-part article discusses application deployment, particularly automated updates, to IBM WebSphere Application Servers in a large-scale enterprise environment. It applies to versions 5.0, 5.1, and 6.0, and also includes an introduction to a few version 6.0 enhancements.

As your company makes more of its applications available on the Web, you will need to determine the level of accessibility for each of those applications. The term accessibility describes how IT hardware, software, and services address and/or neglect the needs of a user community, including users with disabilities.

WebSphere applications often rely on property files to contain environment-specific values. These files usually contain any settings that change between environments, and the files can be in a variety of formats ­Java properties (key/value pairs), XML, or a custom format.

One of the major architectural themes for WebSphere Application Server Version 6 is its support for service-oriented architecture (SOA). IBM has supported Web services in various products for over four years, such as earlier versions of the application server as well as the WebSphere Business Integration Server Foundation, announced in April 2004.

SYS-CON Media today announced further details of the 'Application Server Shoot-Out' due to take place at its upcoming cross-platform technology event, Web Services Edge 2005 East - International Web Services Conference & Expo (www.sys-con.com/edge) - in which leading application server providers are expected to participate. The Shoot-Out, with a particular focus on interoperability, resiliency, security, and ease-of-use in terms of development, deployment, and management, will be staged under the auspices of Burton Group; Web Services Edge 2005 East is to be held in Boston at the Hynes Convention Center, February 15-17, 2005.

These days Calvin Austin is one of the busiest people in the Java world: J2SE 5.0, that was also known as the 'Tiger' project, is being officially released today! JDJ's Yakov Fain was able to catch Austin, spec lead for Java 5.0, right before the plane from San Francisco to New York where he'll today be presenting the new features of the Java language to the New York Java Users Group.

With better technologies, new architectures, and innovative ways of thinking about old problems, there are new applications for business intelligence and data analysis. I am talking about the power of the intelligent portal.

Look at it this way, saying 'surfacing' is an improvement over saying 'portalizing'! Just in case this is your first time hearing either term, they have identical definitions: bringing the data to the top most layer of the system. If you think about your development experience, you've probably been surfacing applications for years now.

The Internet has no doubt become the most popular source of information today. More and more businesses have adopted the Internet as the vehicle to display their business information, advertise their products, and maintain customer interactions. The activity of developing Web applications occupies a fair amount of resources, time, and effort.

Business services provider Winholesale chose Bowstreet Portlet Factory, and IBM WebSphere Portal, to provide portlet development providing role-based access to the company's financial information.

This article is intended to help you understand what support the Sony-Ericsson P800/P900 has for Java and to show you how to install the necessary Symbian software required for developing Java solutions for these platforms. It will discuss how WebSphere Studio Application Developer can be used to develop the Java code, how this code can then be packaged using the Symbian development kit utilities, and how to deploy it to the Symbian P800/P900 emulator.

Reality check: your code likely exists beyond the confines of your cubicle. In today's world - made smaller via the marvels of modern society - it is likely that your code will transcend borders or be seen by individuals who might not necessarily understand English. Not catering to these individuals can close the doors on a huge untapped market.

When there are problems with a mission-critical application, playing the blame game can stall progress and destroy your team's morale. How do you put an end to chaos and get your team back on track?

Managing the software application development life cycle is more challenging than ever. With the introduction of e-business technologies such as IBM's WebSphere solutions architecture, organizations face inherent complexities. Many more issues must be considered before launching any type of e-business application.