WAS 7.0 New Features and Functions

WAS 7.0 New Features and Functions
----------------------------------
•IBM WAS V7 is a major release that offers dramatic run time improvements, plus simpler and easier ways to develop and deploy applications.

•WAS V7 provides complete support for the Java EE 5 specification, including the Web services and EJB 3.0 functions.


•WebSphere Application Server V7 also introduces support for Java Platform, Standard Edition (Java SE) 6
•Dependency injection - Developer productivity is further enhanced when it’s time to override the defaults, since this can be accomplished quickly and simply using annotations rather than writing code. Annotations are used in conjunction with a programming pattern known as dependency injection.
•Java Persistence API - Another aspect to the simplification of the programming model in Java EE 5 is the ability to develop EJB components as Plain Old Java Objects (POJOs). Simplifying EJB development even further is the Java Persistence API (JPA), which enables entities to be created using annotated POJOs. Aside from making EJB development and usage even easier, this also enables Java SE developers to quickly learn Java EE and develop enterprise applications.
•Web services - The improvements to the Java EE 5 programming model are not limited to EJB development. Web services development is also greatly simplified via annotations.
•Another important new systems management capability in V7 in the area of Web services, in addition to the programming model improvements, are Web service policy sets that are the mechanisms provided by WebSphere Application Server V7 for centrally defining various quality of service polices that you might want to apply to Web services that are already deployed. There are two types of policy sets: Application policy sets and System policy sets.
•JAX-WS implementation in WebSphere Application Server V7 also provides support for SOAP 1.2, as well as for generic XML or HTTP as a protocol binding, which enables the creation of WS clients and WS providers that do not use SOAP for their wire level message format.
•Another important addition in WebSphere Application Server V7 is its support for Message Transmission Optimization Mechanism (MTOM), an improved method for sending binary attachments. MTOM is the preferred attachment mechanism for non-Java EE-based Web services, so support for MTOM improves the interoperability between Java EE Web services and non-Java EE 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.
•Intelligent provisioning - It selects only the run time function needed for an application, reducing both memory footprint and application server startup time. WebSphere Application Server examines each application at application installation time to generate an activation plan; at run time, the server starts only those components that are required by the activation plan.

•WAS V7 contains support for a Web/JDBC application scenario in which only the Web container and core run time components are started. This is in contrast to V6.1, in which the EJB container, SIP container, and Web services runtime would also have been started.


•The above capability can also help to reduce the memory footprint, and is designed for extension by other WebSphere products that run on top of WebSphere Application Server.

•Additional run time footprint reductions are delivered in the form of the Java SE 6 implementation that ships with WebSphere Application Server V7.


•The shared class cache that was introduced in IBM's Java SE 5 implementation has been improved so that the cache can now be persistent. As a result, the cache can survive a shutdown and restart of all WebSphere processes on a server. This lead to a significantly faster application server startup times.

•Another improvement in IBM's Java SE 6 is the use of compressed references (or pointer compression) in 64-bit WebSphere Application Server JVMs. The use of compressed references can provide a very significant reduction in the process footprint of a 64-bit JVM, when previously compared to a 32-bit JVM. Prior to IBM's Java SE 6 implementation, it wasn’t unusual for a 64-bit heap to be 1.7 to 2 times the size of an equivalent 32-bit heap.


•Flexible management is a new feature in WAS V7 that separate most of the administrative components from the application server runtime. Now, each application server is no longer a single point of management. This is accomplished with a separate administration process for (base) WebSphere Application Servers known as the administrative agent. This help to reduce the cost of administering large deployments in several ways.

•The job manager is another aspect of flexible management that is available in WebSphere Application Server Network Deployment V7. Its feature is for WAS V7 remote administration and scheduling of administrative functions.
•Messaging - Beyond the Web services improvements in WebSphere Application Server V7, there are also improvements to a related SOA component: messaging. New administrative wizards for System Integration Bus (SIBus) configuration are provided for configuring a cluster bus member and a foreign bus connection, as well as new panels for SIBus authorizations, WebSphere MQ JCA Resource Adapter configuration, and for inspecting an application's use of SIBus resources.
•WAS V7 also includes a WebSphere MQ JMS JCA 1.5 resource adapter, as well as associated new panels and administrative commands. Having the JCA 1.5 resource adapter also means that message-driven beans that consume messages from WebSphere MQ can now use activation specifications instead of listener ports.

•Improved management of activation specifications -- stop, start, message retry limits (or "poison" message filtering) -- is also included in WebSphere Application Server V7.
•Centralized installation - Network Deployment also adds the capability to perform centralized installation from the deployment manager to remote nodes. This enables a single installation to the deployment manager to be pushed out as an installation package from the deployment manager to a series of endpoints. The endpoint can be either a node that is not part of a Network Deployment cell.
•Business level applications - Another new function in WebSphere Application Server V7 is the notion of an "application" beyond J2EE™, or a business level application (BLA). This is a new administration concept that expands upon what was previously provided by J2EE.
•Security - Security management and auditing improvements are also a significant portion of what’s new in WebSphere Application Server V7. Perhaps the most prominent change is the capability to create multiple security domains within a single WebSphere Application Server cell. Each security domain can have its own user population (and underlying repository), and, additionally, the application domain can be separated from the administrative domain. Not only can each domain have its own separate user population, but each domain can also be customized with a separate security configuration -- for example, JAAS login configuration, TAI, authorization provider, JCA authentication data, and auditing -- in addition to the current application server level security configuration options.
•Further, the fine-grained administrative security function that was introduced in WebSphere Application Server V6.1 but limited to wsadmin is now expanded in V7 to include the administrative console. Within the administrative security domain for a cell, this enables administrative roles to be restricted to specific components, such as a cluster, node, application server, or application.
•Auditing - Another security enhancement is the option to generate security-auditing records of WebSphere Application Server administrative actions. These actions can be security configuration changes, key and certificate management, access control policy changes, bus and other system resources management, and so on. This feature enables you to hold administrative users accountable for configuration and run time changes.
•Further, the review and control of audit records and audit configurations is entrusted to a new auditor role, which enables the separation of administrative user privileges, in that an administrator cannot change audit policy and cannot view audit records, nor can an auditor change WebSphere configuration and run time state.
•Kerberos - WebSphere Application Server V7 provides support for Kerberos Authentication, which can be used in a variety of single sign-on scenarios. The Kerberos support in V7 expands on the SPNEGO TAI support in V6.1 to provide better interoperability and identity propagation with other applications that support Kerberos authentication (such as IBM DB2®, .NET®, and others).
•Application development and management - WebSphere Application Server V7 includes two tooling options for application development that let you leverage the standards supported in this new release:
•IBM Rational® Application Developer Assembly and Deploy V7.5 replaces the Application Server Toolkit (AST) function provided with WebSphere Application Server V6.1. This development tool expands on the functions provided in the AST with Java EE 5 XML-form based DD editors, Java EE 5 application support, and more.
• IBM Rational Application Developer V7.5 for WebSphere adds functions to Rational Application Developer Assembly and Deploy, including EJB 3 application development productivity features, visual editing domain modeling and Web development; Web services productivity features, and relational data tools.

WAS 6.1 New Features and Functions Updated

WAS 6.1 New Features and Functions Updated
------------------------------------------

•Multiple installations of any WAS 6.1 edition are now allowed. Just specify a unique installation directory and default profile location.
•The products require Java* Developer Kit (JDK) 5.0 to install and run.
•By default, the ND installer creates a deployment manager profile and a federated node profile, which are part of the deployment manager cell.
•Administrative security is enabled by default when you install. You only need to specify the user name and password to use administrative security when installing, and the default profile is created with administrative security enabled.
•Portlet programming model.
•Installation factory to create customized installation packages (CIPs) from the installation image for a version or release of a WebSphere software product with applicable maintenance packages.
•High-availability (HA), scalability and Web services improvements.
•Ability to run your application server using either of the two supported i5/OS JDK 5 JVMs.
•Ability to install with CDs or DVDs.
•6.1 has a new way of configuring SSL
•6.1 is 64 bit enabled for better performance
•6.1 has a partitioned "profile" architecture that gives more flexibility for backups and updates
•6.1 come with better Admin Console - 6.1 now features a standalone thin admin client that can be used to administer application servers remotely.
•The IBM HTTP Server can also now be managed from the admin console.
•6.1 includes WebSphere Identity Manager (WIM)
•6.1 introduced SIP support (Session Initiation Protocol) - This is a key technology for IP Telephony like VOIP, IPTV, Internet chat etc.
•6.1 has small footprint of Portlet container
•It has future support for EJB 3.0 (Enterprise Java Beans)
•RAD 7 works with 6.1 not lower than RAD7
•For WAS 6.1, the TPV is running under the deployment manager, so it is recommended to get a more powerful server due to the PMI and GUI.
•In 6.1, it is recommended to code your own java client to get the PMI reading or install ITCAM.
•There is no problem found with 6.0 and 6.1 co-existing in the same cell, the same Node or machine.
•The JSR 168 portlet-programming model is supported - meaning portlets can be accessed like servlets via a URL without a full portal server. It is JSR 168 compliant.
•Integration (Service) between WebSphere MQ for z/OS and the default-messaging provider in WebSphere Application Server has been enhanced in Version 6.1, enabling you to add a queue manager or queue sharing group as a member of a service integration bus.
•The IBM Support Assistant is now bundled with WebSphere Application Server V6.1 for more effective and faster self-help and problem reporting. (PMR) submission
•Java Server Faces (JSF) support has been enhanced for you to easily build web applications
•Edge Components like Dynamic Cache Support, Cache identification and management capabilities has been enhanced.
•6.1 supports IPv6 at the node level; both IPv4 and IPv6 nodes can be federated into the same cluster. A node can also be configured in "dual mode" to support both protocols.
•The Packaging structure is supplied with only platform specific images
•In 6.1 - WebSphere Application Server can now be installed by a non-root user -In 6.0 IHS require root
•Application Server Toolkit (AST) in V6.1 reaches a key milestone because it includes a J2EE perspective and a Web perspective, Eclipse 3.1, and Version 1.0 of the Eclipse Web Tools Platform (WTP).
• In 6.1 AST is a complete J2EE development environment, thus you can use it to construct, debug, and deploy new applications directly to WebSphere Application Server V6.1.
•Web Services has been enhanced for better performance - e.g SAAJ changes, SOAP/JMS, WS-I BSP(Basic Security Profile 1.0) and W3C WS-Addressing.

cheat sheets for Linux,AIX,Solaries...............

http://www.scottklarr.com/topic/115/linux-unix-cheat-sheets---the-ultimate-collection/

AIX:
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.doc/doc/base/commandsreference.htm

About JVM logs

JVM logs(SystemOut and SystemErr logs)

SystemOut and SystemErr logs are created for every WebSphere Application
Server process (application server, cluster member, node agent, and
deployment manager). These logs are known as JVM logs.

Your applications can also write to them by using the print(), println(), and
printStackTrace() methods.

Location:
WAS_install_root/profiles/profile/logs/process

To configure the properties of these logs from the administrative console, select
1.) Troubleshooting → Logs and Trace.
2.) Select the process (application server, cluster member, node agent, and
deployment manager) whose logs you want to configure,
3.) and then click JVM Logs

The SystemOut and SystemErr logs are self-managing. They write to the
specified file until either the maximum file size or a certain time is reached.
When that happens, the current log file is renamed as the current file name
plus the current time stamp. Then a new SystemOut or SystemErr file is
created for further logging. The older log files are called historical log files.

Example– SystemOut.log, the current log file
SystemOut_05.06.07_10.28.48.log, the historical log file


Example that tells us the format of the message that comes in the systemout.log

[7/12/05 14:46:00:264 EDT] 0000001a ApplicationMg A WSVR0221I: Application
started: adminconsole

Each entry can be deciphered as follows:
Time stamp
In the example, the time stamp is [7/12/05 14:46:00:264 EDT].
The time stamp is formatted using the locale of the process where it is
formatted. It includes a fully qualified date (for example MM/DD/YY), 24-hour
time with millisecond precision, and a time zone.

Thread ID
In the example, the thread ID is 0000001a.
The thread ID is an eight-character hexadecimal value that is generated from
the hash code of the thread that issued the message.

Short name
In the example, the short name is ApplicationMg.
The short name is the abbreviated name of the component that issued the
message. This name is typically the class name of a WebSphere Application
Server component and would be some other identifier for applications.

Event type
In the example, the event type is A.
The event type is a one character field that indicates the type of the message.
The possible values are:
– F - fatal message
– E - error message
– W - warning message
– A - audit message
– I - informational message
– C - configuration message
– D - detail message
– O - message that was written directly to System.out by an application or
internal components
– R - message that was written directly to System.err by the user application
or internal components
– Z - a placeholder to indicate that the type was not recognized
_ Message Identifier

In the example, the message identifier is WSVR0221I.

The message identifier is a string that is nine characters in length and is in the
form CCCC1234X. The first four characters (CCCC) indicate the WebSphere
Application Server component that issued the message. The next four
characters (1234) indicate the specific message that the component is
issuing. The last character (X) indicates the severity of the message. Its value
is either I (informational), W (warning), or E (error).

Interview Question

How do u connect to Linux(GUI mode) ?

Nxclient for Windows is the tool, we use to connect to Linux box(GUI mode).

What is the difference between fix pack and Refresh pack?

Fix pack contains fixes for APAR(Authorized program analysis report).
Refresh pack contains some new features and functionality apart from fixes for APAR.

How to install gems and update them

go to the command prompt and give :

c:\> gem update --system

c:\> gem install watir

c:\> gem uninstall watir

if ur having any problem .....then delete the folders in the Ruby....
and copy the folders of someone who installation is success(i.e all scripts are
running successfully) ..........this is the cheat cote