Username:
Password:
Log me on automatically each visit
 

 
It is currently Tue Sep 30, 2014 7:52 pm


Post a new topic Post a reply  [ 3 posts ]   
Author Message
PostPosted: Sun Sep 12, 2010 7:43 am 
Site Admin
User avatar

Joined: Sat Aug 02, 2008 8:00 am
Posts: 154
Hi Guys I'm writing a new article about what is new in Websphere application Server 7 I'll post it to you and need you openion please

Thanks

_________________
Muhammad Safwat
The Java Code Admin

Top
OfflineProfileSend private message
 
PostPosted: Sun Sep 12, 2010 7:49 am 
Site Admin
User avatar

Joined: Sat Aug 02, 2008 8:00 am
Posts: 154
Websphere 7 what’s new?
IBM Corporation released the new version on its websphere Application Server family. Websphere 7 provides more powerful features for the family of websphere servers. With support to Java EE5 and Java Standard Edition 1.6 Websphere 7 transforms the websphere family from the old Java 1.4 to the new trends in technology and provides new advancement to the server management, installation and security. With all these additions Websphere application Server 7 makes it as the perfect environment to host Service Oriented Architecture based applications with reduced cost.
Key Features
New Standards Supported
Websphere Application Server version 7 now supports the following new standards:
Java EE5
The most important advancement in Websphere Application Server version 7 is its support for the Java Enterprise Edition (Java EE) 5. Websphere Application Server 7 provides complete support for the Java EE 5 standards making it easier to build deploy and run Java Enterprise Applications containing new Enterprise Java Beans version 3 and Web services.
Java EE 5 provides magnificent improvement in the development of Java Applications and makes it much easier for developers to create applications and to focus on the business requirements rather than technical issues. Taking advantage of standards such as annotations Java EE 5 removes the pain of many development tasks such as deployment descriptors and configuration from the developers and makes them handled by the application server itself increasing the reliability and maintainability of Java EE Applications.
In addition Websphere Application Server 7 provides support for Java Standard Edition (Java SE) version 6.
Dependency Injection
Dependency Injection or Inversion of Control (IoC) is the programming pattern when the developer declares application variables and annotate them with standard annotations for the application container to inject required code to handle what this variable is intended to be. Examples of Dependency Injection are the declaration EJB references and JPA objects.




The following code shows the declaration of EJB reference in EJB 2.1
Code:
Object object=Context.lookup("java:comp/env/ejb/myejb");
MyEjbHome home = (MyEjbHome) PortableRemoteObject.narrow(object, MyEjbHome.class);
MyEjb myejb= home.create();
myejb.dosomething();


And the following is the same example using dependency Injection in EJB3
Code:
@EJB
   MyEjb myejb;
Myejb.dosomething();


Java Persistence API
Beside the advancement of the Java EE 5 environment to develop Enterprise Java Bean as Plain Old Java Objects using annotations Java EE 5 also makes it easier by providing the Java Persistence API which makes the creation of Java Entity beans easier as POJO classes and that makes it easy for any java developer to create entity beans using Java EE 5 with minimal learning effort. Also JPA introduces the concept of Object Relational Model (ORM) where Objects are mapped to relations (Database Tables) and variables in the object classes are mapped to fields in the database tables. By providing such technologies Websphere Application server 7 makes it much easier for new developers to create and use EJBs with much less learning effort.

The following is an example of creating an entity bean in Websphere Application Server 7
Code:
@Entity
@Table(name="BOOKS")

public class Book implements Serializable {
   private static final long serialVersionUID = 1L;

   @Id
   @GeneratedValue(generator="idgen") 
   @SequenceGenerator( name="idgen", sequenceName="BOOKSSEQ")
   private int bookID;
   private int copiesonshelf;

    public Book() {
       }
Some getters and setters…

}


JAX-WS
Web services are another major area of improvement in websphere Application Server 7 java EE 5. The development of web services is improved by using annotations.
The following example shows the difference between creating a web service using JAX-RPC and using JAX-WS in Java EE 5
Code:
public interface MyWebService extends Remote
    {
    public void doSomething(String name) throws RemoteException;   
    }

The following is the same example using JAX-WS
Code:
@WebService public interface MyWebService
    {
    public void doSomething(String name);   
    }

Web services in Java EE 5 and Websphere Application Server 7 also provides support for SOAP protocol version 1.2 and support for XML/ HTTP protocol binding, which enables the creation of web service clients that does not rely on SOAP as the binding protocol for the web services messages.
Another aspect of development in web services in Websphere Application Server 7 is its support for Message Transmission Optimization Mechanism (MTOM) which enables web services to receive attachments such as binary files in the SOAP messages. In JAX-RPC the only way to send binary content in the SOAP messages was by extending the SOAP envelope body and attaching and attachment which was not accepted by some web service providers such as Microsoft, which adopted the MTOM mechanism for binary content sending. Supporting MTOM enables Java Web services to be compliant an able to communicate with the other vendors’ implementation to web services.
Portlet 2.0 API
WebSphere Application Server V7 also introduces support for the Portlet 2.0 API, also known as the Portlet JSR 286 specification.
Advanced System Management
Websphere Application Server 7 introduces advanced system administration with scalable and asynchronous management topology to make you able to manage Websphere with effectiveness.
Intelligent Provisioning
Intelligent Provisioning is a new concept in Websphere Application Server 7 that helps the application server to reduce the footprint of the runtimes included and loaded to run the applications. It simply means that the application server first examines the needs and the type of each application it serves and based on the needs of the applications it loads the runtimes required for such applications. This is instead of loading all the runtimes at the server startup time as earlier versions of Websphere Application Server does and this reduces the server startup time and increases the performance of the serve and reduces the server footprint for servers that host simple applications. This action is done using something called activation plan in Websphere Application Server 7.

Websphere Application Server contains a defined scenario in which applications will only use web container capability and JDBC capabilities. Opposite to earlier versions of websphere the application server would load only the web container and the JDBC runtime and leave the EJB and Web Services runtimes unloaded.

Additional footprint reduction is also introduced in Websphere Application Server 7 by using the Java SE 6. As introduced in IBM implementation to Java SE 5 IBM provides class cashing and even more in Java SE 6 class cashing now enables cashing persistence which makes the cash survives even server restarts. This is addition to the intelligent provisioning makes the Websphere Application Server 7 runtime much faster that earlier versions. In case the server is used as a development or test server the class cash can always be refreshed on server restarts to reflect changes.

Another addition to the reduction of footprint is the use of compressed references which dramatically reduces the heap size on 64bit systems. Before that 64bit systems used to have 2 times heap size than 32bit systems due to long memory references.



Administrative Agent
In versions earlier to websphere application server 7 each server would have its own administrative console which is a source of administrative overhead on the server with the websphere administrative scripts are run against the application server itself. And also this means that every profile needs to be managed independently.

Websphere Application Server removes this restriction by providing the administrative agent which is a separate process than the application server that gathers all the administrative functionality away from the application server. The Administrative Agent can manage different servers.

The administrative agent can manage several application server instances on the same machine an as the number of application servers increase on the same machine that makes the use of administrative agent more valuable because all of those server instance will not have the overhead of the management console and will not need to be managed independently
Job Manager
The Job Manager adds another kind of flexibility to the Administrative Agent management. In a pre websphere application server 7 environment the network deployment will basically consist of deployment manager which controls servers using the node agents on remote machines. The problem with this topology is that the application servers are tightly coupled with the node agents and the deployment manager is tightly coupled with the node agents which makes it difficult for creating topology for environment that are separated with large geographical distance as it has o rely on the WAN robustness which is far less than the LAN robustness. The solution provided for this is using the job manager which is an asynchronous way to perform remote administrative tasks either using the administrative agent or the admin console the administrator can run the administrative tasks using the job manager and the job manager will asynchronously execute such jobs on the deployment managers on remote machines.

Notice that the job manager is not a replacement to the deployment manager. It is just another way to send management jobs asynchronously to be executed by the deployment managers or the administrative agents on remote machines.

You can use the following table to identify the differences between the deployment manager and the job manager

Web Services
Another advancement provided by Websphere Application Server 7 regarding Web Services aside from the development advancements mentioned earlier, is the web services policy sets which enables assigning quality of service policies to web services that are deployed already.
Web services policy sets can assign policies to all the web services deployed on the application server rather than assigning the policies individually to each and every web service and this ensures consistent behavior and policy setting on the entire server regardless which web service is used.

Messaging
Beside the improvements to the web services Websphere application server provides improvement to the communicant between SOA components.
Centralized Installation
Websphere Application Server 7 brings the concept of centralize installation where a deployment manager can be installed and be pushed outside as an installment package to the external nodes which might be a new node to be installed or a node that needs to be fixed of updated.
Business Level Applications
Business Level Applications is a new concept in WebSphere Application server 7 identifying the applications that are related to business rather than the application server and applications that contains component that run on other environment that websphere and also applications that contain other applications.
Security
Version 7 provides improvements o the security used in the Application server by providing the ability to have multiple security domains on the same server and each domain can have its own population and configuration.
Auditing

Kerberos
Websphere now provides Kerberos security support to communicate with other platforms such as .NET

_________________
Muhammad Safwat
The Java Code Admin

Top
OfflineProfileSend private message
 
PostPosted: Mon Dec 27, 2010 7:38 am 
Hi,

Thanks for the useful topic.

I have a question related to WAS 7.1

Like, in my wsdl, I have datatype of array complextype. While generating client using the WAS 7.1 in myEclipse with JAX-RPC, I don't get any class which are of array.

So my question is "Is Array supported in the WAS 7.1 web service for JAC RPC?"


Thanks in advance,
Ranjita

Top
 
Display posts from previous:  Sort by  
Post a new topic Post a reply  [ 3 posts ] 

Who is online

Registered users: No registered users

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum
Jump to:  
cron