|
|
|
|
|
|
|
|
|
|
|
|
|
|
WebSphere Application Server 6: what's it all mean? (continued)
Some of the new changes you'll see in WebSphere 6 is that the default product installation is itself a profile, support for creating new profiles, commands that support profiles, profile exchange between environments which can serve as backup and restore, and updates to the PTF installation process to support profiles.
Default profiles
There are three profiles that ship with WAS 6.0: Standalone Server, this is your base default configuration similar to the WAS 5 editions, Managed Node, this is an empty node for the initial installation versus the previous automatic creation of a WAS base server1 installation, and Deployment Manager, a profile for creating the Deployment Manager for a cell. Figure A below shows the installation setup and the launching of the Profile creation wizard.
FIGURE A
 
Server Profiles makes configuration management of WebSphere environments easier to create, manipulate and share. Roll over picture for a larger image.
An added benefit with Server Profiles is you can now recreate configurations if, by chance, your configuration was corrupted.
Standards
Beginning with version 4 of WebSphere Application Server, IBM has been continuing its efforts to focus on standards-based architectures. Let's take a look at some of the new standards-based additions to WebSphere 6.
J2EE 1.4
WebSphere 6 supports the J2EE 1.4 programming model and extensions including Servlets, JSPs (Java Server Pages), EJBs (Enterprise Java Beans), and Web services. Included are additional programming model enhancements that provide a secure foundation for an SOA (Service-Oriented Architecture).
With WebSphere 6 you can now leverage SDK 1.4.2 and new features such as SDO (Service Data Objects) and JSF (Java Server Faces). I'll go into more detail about these a little later. Table B provides you with the standards and point release that are a part of WebSphere 6.
| Web services and XML support |
Messaging |
ISV Enablement |
Other |
| Standards/Portability -- XML Schema definitions for ALL deployment descriptors |
EJB 2.1 |
JMX 1.2/JSR-077 (J2EE Management) |
Servlet 2.4 |
| JAX-P 1.2 |
JMS 1.1 |
JSR-088 (J2EE Deployment) |
JSP 2.0 |
| JAX-R |
-- |
JACC 1.0 |
EJB 2.1 |
| JAX-RPC |
-- |
-- |
JDBC 3.0 |
| JSR 109 |
-- |
-- |
JavaMail 1.3 |
| SAAJ 1.1 |
-- |
-- |
J2CA 1.5 |
Web services changes in WebSphere 6
Many of the Web services standards listed above were introduced in WebSphere 5.0.2 and 5.1. In WebSphere 6 upgrades, the Web services standards are basically updated with point level releases. Below, you'll see some of the key features/support added with these releases.
- JAX-RPC (JSR-101) 1.1 -- Fault support, Name collision rules, new APIs, additional type support.
- JSR 109-WSEE 1.1 -- utilizes J2EE 1.4 schema types, Handlers support for EJBs
- SAAJ 1.2 -- additional APIs for manipulating SOAP XML messages, SAAJ infrastructure now extends DOM
- WS-Security -- applying WS-I Security Profile, OASIS draft 17
- WS-I Basic Profile 1.1 -- Attachment support
- JAXR support -- access capability to UDDI registry
- UDDI V3 support -- includes registry implementation and client API library
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-- Advertisement --
SECURE YOUR SITE WITH AN IRONCLAD SSL CERTIFICATE
An IronClad SSL Certificate helps you build an impenetrable fortress around your customer's credit card information. IronClad SSL Certificates are:
- Fully validated
- Up to 256-bit encryption
- One, two, or three year validity (our Turbo SSL Certificates are valid up to 10 years)
- 99% browser recognition
- Stringent authentication
- Around-the-clock customer support
Build trust. Protect your customers. Grow your online business.
Tap here now and be IronClad with SSL tonight. |
|
|
|
|
|
|
|
|
|
|
|
