This is a comparison of the C# programming language with the Java programming language. As the two are both garbage-collected runtime-compiled languages with syntax derived from C and C++, there are many similarities between Java and C#. However, there are also many differences, with C# being described as a hybrid of C++ and Java, with additional new features and changes. This page documents the strong general similarities of the languages and then points out those instances where the languages differ.
Object handling
Both C# and also Java are designed from the ground up as object oriented languages using dynamic dispatch, with a syntax similar to C++. (C++ in turn is derived from C.) Neither language is a superset of C or C++, however. Both use garbage collection as a means of reclaiming memory resources, rather than explicit deallocation of memory. Both include thread synchronization mechanisms as part of their language syntax.
[edit] References
C# allows restricted use of pointers. Pointers and pointer-arithmetic are potentially unsafe in a managed environment as they can be used to bypass the strict rules for object access. C# addresses that concern by requiring that code blocks or methods that use the feature be marked with the unsafe keyword, so that all clients of such code can be aware that the code may be less secure than otherwise. The compiler requires the /unsafe switch to allow compilation of a program that uses such code. Generally, unsafe code is either used to allow better interoperability with unmanaged APIs or system calls (which are inherently "unsafe"), or for performance reasons. Java does not allow pointers or pointer-arithmetic to be used.
[edit] Data types
Both languages support the idea of primitive types (all of which, except for String, are value types in C#/.NET). C# has more primitive types than Java, with unsigned as well as signed integer types being supported, and a decimal type for decimal floating-point calculations. Java lacks unsigned types. In particular, Java lacks a primitive type for an unsigned byte, while C# bytes are unsigned by default. Strings are treated as (immutable) objects in both languages, but support for string literals provides a specialized means of constructing them. C# also allows verbatim strings for quotation without escape sequences, which also allow newlines.
Both allow automatic boxing and unboxing to translate primitive data to and from their object form. Effectively, this makes the primitive types a subtype of the Object type. In C# this also means that primitive types can define methods, such as an override of Object's ToString() method. In Java, separate primitive wrapper classes provide such functionality. In Java primitive values are not implicitly boxed when dereferenced and an explicit cast is required for an instance call on a primitive value ((Integer)42).toString() instead of a C# instance call 42.ToString(). Another difference is that Java makes heavy use of boxed types in generics (see below), and as such allows an implicit unboxing conversion (in C# this requires a cast). As these implicit unboxing conversions can potentially throw null pointer exceptions, modern integrated development environments and compilers can be configured to highlight them.
[edit] Value types
C# allows the programmer to create user-defined value types, using the struct keyword. From the programmer's perspective, they can be seen as lightweight classes. Unlike regular classes, and like the standard primitives, such value types are allocated on the stack rather than on the heap. They can also be part of an object (either as a field or boxed), or stored in an array, without the memory indirection that normally exists for class types. Structs also come with a number of limitations. Because structs have no notion of a null value and can be used in arrays without initialization, they always come with an implicit default constructor that essentially fills the struct memory space with zeroes. The programmer can only define additional constructors with one or more arguments. This also means that structs lack a virtual method table, and because of that (and the fixed memory footprint), they cannot allow inheritance (but can implement interfaces).
[edit] Enumerations
Enumerations in C# are derived from a primitive 8, 16, 32, or 64 bit integer type. Any value of the underlying primitive type is a valid value of the enumeration type, though an explicit cast may be needed to assign it. C# also supports bitmapped enumerations where an actual value may be a combination of enumerated values bitwise or'ed together. Enumerations in Java, on the other hand, are objects. The only valid values in a Java enumeration are the ones listed in the enumeration. As objects, each enumeration can contain its own fields which can be modified. Special enumeration set and map collections provide fully type-safe functionality with minimal overhead. Java enumerations allow differing method implementations for each value in the enumeration. Both C# and Java enumerations can be converted to strings and can be used in a switch statement.
[edit] Arrays
Array and collection types are also given significance in the syntax of both languages, thanks to an iterator-based foreach statement loop. In C# an array corresponds to an object of the Array class, while in Java each array is a direct subclass of the Object class (but can be cast to an array of an element type that is an ancestor of its true element type), and does not implement any of the collection interfaces. C# has true multidimensional arrays, as well as the arrays-of-arrays that are available in Java (and which in C# are commonly called jagged arrays). Multidimensional arrays can in some cases increase performance because of increased locality (as there is a single pointer dereference, instead of one for every dimension of the array as is the case for jagged arrays). Another advantage is that the entire multidimensional array can be allocated with a single application of operator new, while jagged arrays require loops and allocations for every dimension. Note, though, that Java provides a syntactic construct for allocating a multidimensional jagged array with regular lengths (a rectangular array in the C# terminology); the loops and multiple allocations are then performed by the virtual machine and need not be explicit at the source level.
[edit] Inner classes
Both languages allow inner classes, where a class is defined entirely within another class. In Java, these classes have access to both the static and non-static members of the outer class (unless the inner class is declared static, then it only has access to the static members). Local classes can be defined within a method and have access to the method's local variables declared final, and anonymous local classes allow the creation of class instances that override some of their class methods.
C# also provides inner classes, but unlike Java, requires an explicit reference to the outer class to its non-static members. Also, C# provides anonymous delegates as a construct that can provide access to local variables and members (see Event handling). Local classes and anonymous classes are not available.
[edit] Partial classes
C# allows a class definition to be split across several source files using a feature called partial classes. Each part must be marked with the keyword partial. All the parts must be presented to the compiler as part of a single compilation. Parts can reference members from other parts. Parts can implement interfaces and one part can define a base class. The feature is useful in code generation scenarios where a code generator can supply one part and the developer another part to be compiled together. The developer can thus edit their part without the risk of a code generator overwriting that code at some later time. Unlike the class extension mechanism a partial class allows "circular" dependencies amongst its parts as they are guaranteed to be resolved at compile time. Java has no corresponding concept.
Friday, March 27, 2009
Visual Basic .NET
Visual Basic (VB), formerly called Visual Basic .NET (VB.NET), is an object-oriented computer language that can be viewed as an evolution of Microsoft's Visual Basic (VB) implemented on the Microsoft .NET framework. Its introduction has been controversial, as significant changes were made that broke backward compatibility with older versions and caused a rift within the developer community.
Visual Basic .NET (VB 7)
The original Visual Basic .NET was released alongside Visual C# and ASP.NET in 2002. C# — widely touted as Microsoft's answer to Java — received the lion's share of media attention, while VB.NET (sometimes known as VB7) was not as widely covered.[citation needed]
[edit] Visual Basic .NET 2003 (VB 7.1)
Visual Basic .NET 2003 was released with version 1.1 of the .NET Framework. New features included support for the .NET Compact Framework and a better VB upgrade wizard. Improvements were also made to the performance and reliability of the .NET IDE (particularly the background compiler) and runtime.
In addition, Visual Basic .NET 2003 was also available in the Visual Studio .NET 2003 Academic Edition (VS03AE). VS03AE is distributed to a certain number of scholars from each country for free.
[edit] Visual Basic 2005 (VB 8.0)
Visual Basic 2005 is the name used to refer to the update to Visual Basic .NET, Microsoft having decided to drop the .NET portion of the title.
For this release, Microsoft added many features, including:
* Edit and Continue
* Design-time expression evaluation
* The My pseudo-namespace (overview, details), which provides:
o easy access to certain areas of the .NET Framework that otherwise require significant code to access
o dynamically-generated classes (notably My.Forms)
* Improvements to the VB-to-VB.NET converter [2]
* The Using keyword, simplifying the use of objects that require the Dispose pattern to free resources
* Just My Code, which hides boilerplate code written by the Visual Studio .NET IDE
* Data Source binding, easing database client/server development
The above functions (particularly My) are intended to reinforce Visual Basic .NET's focus as a rapid application development platform and further differentiate it from C#.
Visual Basic 2005 introduced features meant to fill in the gaps between itself and other "more powerful" .NET languages, adding:
* .NET 2.0 languages features such as:
o generics [3]
o Partial classes, a method of defining some parts of a class in one file and then adding more definitions later; particularly useful for integrating user code with auto-generated code
o Nullable Types
* XML comments that can be processed by tools like NDoc to produce "automatic" documentation
* Operator overloading [4]
* Support for unsigned integer data types commonly used in other languages
[edit] 'IsNot' operator patented
One other feature of Visual Basic 2005 is the conversion of 'If Not X Is Y' to 'If X IsNot Y' which gained notoriety [5] when it was found to be the subject of a Microsoft patent application [6] [7].
[edit] Visual Basic 2005 Express
As part of the Visual Studio product range, Microsoft created a set of free development environments for hobbyists and novices, the Visual Studio 2005 Express series. One edition in the series is Visual Basic 2005 Express Edition, which was succeeded by Visual Basic 2008 Express Edition in the 2008 edition of Visual Studio Express.[8]
The Express Editions are targeted specifically for people learning a language. They have a streamlined version of the user interface, and lack more advanced features of the standard versions. On the other hand, Visual Basic 2005 Express Edition does contain the Visual Basic 6.0 converter, so it is a way to evaluate feasibility of conversion from older versions of Visual Basic.
[edit] Visual Basic 2008 (VB 9.0)
Visual Basic 9.0 was released together with the Microsoft .NET Framework 3.5 on November 19, 2007.
For this release, Microsoft added many features, including:
* A true conditional operator If (boolean, value, value) to replace the IIF function.
* Anonymous types
* Support for LINQ
* Lambda expressions
* XML Literals
* Type Inference
[edit] Visual Basic 'VBx' (VB 10.0)
Visual Basic 10, also known as VBx, will offer support for the Dynamic Language Runtime (DLR). VB 10 is planned to be part of Silverlight 2.0.[citation needed]
[edit] Relation to older versions of Visual Basic (VB6 and previous)
Whether Visual Basic .NET should be considered as just another version of Visual Basic or a completely different language is a topic of debate. This is not obvious, as once the methods that have been moved around and that can be automatically converted are accounted for, the basic syntax of the language has not seen many "breaking" changes, just additions to support new features like structured exception handling and short-circuited expressions. Two important data type changes occurred with the move to VB.NET. Compared to VB6, the Integer data type has been doubled in length from 16 bits to 32 bits, and the Long data type has been doubled in length from 32 bits to 64 bits. This is true for all versions of VB.NET. A 16-bit integer in all versions of VB.NET is now known as a Short. Similarly, the Windows Forms GUI editor is very similar in style and function to the Visual Basic form editor.
The version numbers used for the new Visual Basic (7, 7.1, 8, 9, ...) clearly imply that it is viewed by Microsoft as still essentially the same product as the old Visual Basic.
The things that have changed significantly are the semantics — from those of an object-based programming language running on a deterministic, reference-counted engine based on COM to a fully object-oriented language backed by the .NET Framework, which consists of a combination of the Common Language Runtime (a virtual machine using generational garbage collection and a just-in-time compilation engine) and a far larger class library. The increased breadth of the latter is also a problem that VB developers have to deal with when coming to the language, although this is somewhat addressed by the My feature in Visual Studio 2005.
The changes have altered many underlying assumptions about the "right" thing to do with respect to performance and maintainability. Some functions and libraries no longer exist; others are available, but not as efficient as the "native" .NET alternatives. Even if they compile, most converted VB6 applications will require some level of refactoring to take full advantage of the new language. Documentation is available to cover changes in the syntax, debugging applications, deployment and terminology.[9]
Visual Basic .NET (VB 7)
The original Visual Basic .NET was released alongside Visual C# and ASP.NET in 2002. C# — widely touted as Microsoft's answer to Java — received the lion's share of media attention, while VB.NET (sometimes known as VB7) was not as widely covered.[citation needed]
[edit] Visual Basic .NET 2003 (VB 7.1)
Visual Basic .NET 2003 was released with version 1.1 of the .NET Framework. New features included support for the .NET Compact Framework and a better VB upgrade wizard. Improvements were also made to the performance and reliability of the .NET IDE (particularly the background compiler) and runtime.
In addition, Visual Basic .NET 2003 was also available in the Visual Studio .NET 2003 Academic Edition (VS03AE). VS03AE is distributed to a certain number of scholars from each country for free.
[edit] Visual Basic 2005 (VB 8.0)
Visual Basic 2005 is the name used to refer to the update to Visual Basic .NET, Microsoft having decided to drop the .NET portion of the title.
For this release, Microsoft added many features, including:
* Edit and Continue
* Design-time expression evaluation
* The My pseudo-namespace (overview, details), which provides:
o easy access to certain areas of the .NET Framework that otherwise require significant code to access
o dynamically-generated classes (notably My.Forms)
* Improvements to the VB-to-VB.NET converter [2]
* The Using keyword, simplifying the use of objects that require the Dispose pattern to free resources
* Just My Code, which hides boilerplate code written by the Visual Studio .NET IDE
* Data Source binding, easing database client/server development
The above functions (particularly My) are intended to reinforce Visual Basic .NET's focus as a rapid application development platform and further differentiate it from C#.
Visual Basic 2005 introduced features meant to fill in the gaps between itself and other "more powerful" .NET languages, adding:
* .NET 2.0 languages features such as:
o generics [3]
o Partial classes, a method of defining some parts of a class in one file and then adding more definitions later; particularly useful for integrating user code with auto-generated code
o Nullable Types
* XML comments that can be processed by tools like NDoc to produce "automatic" documentation
* Operator overloading [4]
* Support for unsigned integer data types commonly used in other languages
[edit] 'IsNot' operator patented
One other feature of Visual Basic 2005 is the conversion of 'If Not X Is Y' to 'If X IsNot Y' which gained notoriety [5] when it was found to be the subject of a Microsoft patent application [6] [7].
[edit] Visual Basic 2005 Express
As part of the Visual Studio product range, Microsoft created a set of free development environments for hobbyists and novices, the Visual Studio 2005 Express series. One edition in the series is Visual Basic 2005 Express Edition, which was succeeded by Visual Basic 2008 Express Edition in the 2008 edition of Visual Studio Express.[8]
The Express Editions are targeted specifically for people learning a language. They have a streamlined version of the user interface, and lack more advanced features of the standard versions. On the other hand, Visual Basic 2005 Express Edition does contain the Visual Basic 6.0 converter, so it is a way to evaluate feasibility of conversion from older versions of Visual Basic.
[edit] Visual Basic 2008 (VB 9.0)
Visual Basic 9.0 was released together with the Microsoft .NET Framework 3.5 on November 19, 2007.
For this release, Microsoft added many features, including:
* A true conditional operator If (boolean, value, value) to replace the IIF function.
* Anonymous types
* Support for LINQ
* Lambda expressions
* XML Literals
* Type Inference
[edit] Visual Basic 'VBx' (VB 10.0)
Visual Basic 10, also known as VBx, will offer support for the Dynamic Language Runtime (DLR). VB 10 is planned to be part of Silverlight 2.0.[citation needed]
[edit] Relation to older versions of Visual Basic (VB6 and previous)
Whether Visual Basic .NET should be considered as just another version of Visual Basic or a completely different language is a topic of debate. This is not obvious, as once the methods that have been moved around and that can be automatically converted are accounted for, the basic syntax of the language has not seen many "breaking" changes, just additions to support new features like structured exception handling and short-circuited expressions. Two important data type changes occurred with the move to VB.NET. Compared to VB6, the Integer data type has been doubled in length from 16 bits to 32 bits, and the Long data type has been doubled in length from 32 bits to 64 bits. This is true for all versions of VB.NET. A 16-bit integer in all versions of VB.NET is now known as a Short. Similarly, the Windows Forms GUI editor is very similar in style and function to the Visual Basic form editor.
The version numbers used for the new Visual Basic (7, 7.1, 8, 9, ...) clearly imply that it is viewed by Microsoft as still essentially the same product as the old Visual Basic.
The things that have changed significantly are the semantics — from those of an object-based programming language running on a deterministic, reference-counted engine based on COM to a fully object-oriented language backed by the .NET Framework, which consists of a combination of the Common Language Runtime (a virtual machine using generational garbage collection and a just-in-time compilation engine) and a far larger class library. The increased breadth of the latter is also a problem that VB developers have to deal with when coming to the language, although this is somewhat addressed by the My feature in Visual Studio 2005.
The changes have altered many underlying assumptions about the "right" thing to do with respect to performance and maintainability. Some functions and libraries no longer exist; others are available, but not as efficient as the "native" .NET alternatives. Even if they compile, most converted VB6 applications will require some level of refactoring to take full advantage of the new language. Documentation is available to cover changes in the syntax, debugging applications, deployment and terminology.[9]
Wednesday, March 25, 2009
Oracle Fusion Middleware for Applications
Market-Leading, Certified, Hot-Pluggable - For a Lower TCO
Oracle Fusion Middleware for Applications applies Oracle's market-leading middleware portfolio to the leading business applications. Extend the business value of your applications across user communities, lines of business, and organizations.
Learn more about Oracle's middleware strategy.
BENEFITS
* Increase your capacity for growth and change—The only comprehensive and integrated middleware foundation certified with Oracle HCM, CRM, financial management, and other business applications
* Enable business insight—Pervasive Business Intelligence delivers insights from across information sources to drive more effective strategies, actions, and processes
* Mitigate risk and ensure compliance—The industry's only hot-pluggable middleware automates information access and document management across applications and business processes
* Empower users for productive interactions—Unified access to processes, information, and services for customers, partners and workers
Oracle is #1 in Middleware
Only Oracle delivers the #1 portfolio of open, world-class middleware products. Three core design principles help drive Oracle Fusion Middleware's leadership position in the market:
* Comprehensive—Provides a complete offering—ranging from Java application servers and business process management to Enterprise 2.0 user interaction and content management
* Preintegrated—Delivers best-in-class middleware products that work together and with Oracle Database and Oracle Applications to lower the cost of ownership
* Hot-pluggable—Allows customers to drop and deploy Oracle middleware into heterogeneous IT environments, providing long-term flexibility, and the ability to optimize existing IT investments
A World-Class Combination
The addition of BEA products to Oracle Fusion Middleware advances Oracle's middleware strategy and further strengthens key areas of the Oracle Fusion Middleware family. Hear from Oracle executives on the strategic direction of Oracle Fusion Middleware in this in-depth Webcast (Presentation PDF). See what customers, partners, and user communities are saying. Learn more about Oracle Fusion Middleware's strategic products in the table below:
PRODUCT AREA STRATEGIC PRODUCTS LISTEN
Middleware Oracle Fusion Middleware Podcast 1
Podcast 2
Application Server Oracle WebLogic Server
Oracle WebLogic Suite
Oracle WebLogic Application Grid
Oracle Coherence
Oracle JRockit Podcast
Podcast
Podcast
Podcast
Podcast
Transaction Processing Oracle Tuxedo Podcast
Service-Oriented Architecture Oracle SOA Suite Podcast
SOA Governance Oracle SOA Governance Podcast
Developer Tools Oracle JDeveloper
Oracle Enterprise Pack for Eclipse Podcast
Podcast
Podcast
Enterprise 2.0 and Portals Oracle WebCenter Suite
Oracle WebCenter Services Podcast
Podcast
Business Process Management Oracle BPM Suite Podcast
Enterprise Content Management Oracle Content Management Podcast
Collaboration Oracle Beehive Podcast
Identity Management Oracle Identity Management Podcast
Business Intelligence Oracle Business Intelligence Enterprise Edition Plus Podcast
Event-Driven Architecture Oracle EDA Suite Podcast
Data Integration Oracle Data Integration Suite Podcast
Service Delivery Platform Oracle Service Delivery Platform
WHAT CUSTOMERS ARE SAYING
* Procter & Gamble
* USi, an AT&T company
* Farmers Insurance Group
* Ingersoll Rand
* Logitech
* First Horizon
* The First American Corporation
* Kabel Deutschland
* PG&E
* BAE Systems Australia
* NetApp
* TIAA-CREF
* INDRA
* CRIS (Indian Railways)
* InterCall
* Habitat
* WebEx Communications
* Intermountain Healthcare
* Synapse Group Inc.
* California State University
* Colorcon
* Novartis Pharma AG
* London Stock Exchange
* Schneider National Inc.
Oracle Fusion Middleware for Applications applies Oracle's market-leading middleware portfolio to the leading business applications. Extend the business value of your applications across user communities, lines of business, and organizations.
Learn more about Oracle's middleware strategy.
BENEFITS
* Increase your capacity for growth and change—The only comprehensive and integrated middleware foundation certified with Oracle HCM, CRM, financial management, and other business applications
* Enable business insight—Pervasive Business Intelligence delivers insights from across information sources to drive more effective strategies, actions, and processes
* Mitigate risk and ensure compliance—The industry's only hot-pluggable middleware automates information access and document management across applications and business processes
* Empower users for productive interactions—Unified access to processes, information, and services for customers, partners and workers
Oracle is #1 in Middleware
Only Oracle delivers the #1 portfolio of open, world-class middleware products. Three core design principles help drive Oracle Fusion Middleware's leadership position in the market:
* Comprehensive—Provides a complete offering—ranging from Java application servers and business process management to Enterprise 2.0 user interaction and content management
* Preintegrated—Delivers best-in-class middleware products that work together and with Oracle Database and Oracle Applications to lower the cost of ownership
* Hot-pluggable—Allows customers to drop and deploy Oracle middleware into heterogeneous IT environments, providing long-term flexibility, and the ability to optimize existing IT investments
A World-Class Combination
The addition of BEA products to Oracle Fusion Middleware advances Oracle's middleware strategy and further strengthens key areas of the Oracle Fusion Middleware family. Hear from Oracle executives on the strategic direction of Oracle Fusion Middleware in this in-depth Webcast (Presentation PDF). See what customers, partners, and user communities are saying. Learn more about Oracle Fusion Middleware's strategic products in the table below:
PRODUCT AREA STRATEGIC PRODUCTS LISTEN
Middleware Oracle Fusion Middleware Podcast 1
Podcast 2
Application Server Oracle WebLogic Server
Oracle WebLogic Suite
Oracle WebLogic Application Grid
Oracle Coherence
Oracle JRockit Podcast
Podcast
Podcast
Podcast
Podcast
Transaction Processing Oracle Tuxedo Podcast
Service-Oriented Architecture Oracle SOA Suite Podcast
SOA Governance Oracle SOA Governance Podcast
Developer Tools Oracle JDeveloper
Oracle Enterprise Pack for Eclipse Podcast
Podcast
Podcast
Enterprise 2.0 and Portals Oracle WebCenter Suite
Oracle WebCenter Services Podcast
Podcast
Business Process Management Oracle BPM Suite Podcast
Enterprise Content Management Oracle Content Management Podcast
Collaboration Oracle Beehive Podcast
Identity Management Oracle Identity Management Podcast
Business Intelligence Oracle Business Intelligence Enterprise Edition Plus Podcast
Event-Driven Architecture Oracle EDA Suite Podcast
Data Integration Oracle Data Integration Suite Podcast
Service Delivery Platform Oracle Service Delivery Platform
WHAT CUSTOMERS ARE SAYING
* Procter & Gamble
* USi, an AT&T company
* Farmers Insurance Group
* Ingersoll Rand
* Logitech
* First Horizon
* The First American Corporation
* Kabel Deutschland
* PG&E
* BAE Systems Australia
* NetApp
* TIAA-CREF
* INDRA
* CRIS (Indian Railways)
* InterCall
* Habitat
* WebEx Communications
* Intermountain Healthcare
* Synapse Group Inc.
* California State University
* Colorcon
* Novartis Pharma AG
* London Stock Exchange
* Schneider National Inc.
WHY ORACLE?
WHY ORACLE?
THE #1 APPLICATION SERVER
The Oracle WebLogic Application Server product line is the industry's most comprehensive platform for developing, deploying, and integrating enterprise applications. At the center of the product line is Oracle WebLogic Server, a powerful and scalable Java EE server. It combines with Oracle Application Server and additional performance enhancing products such as Oracle JRockit and Oracle Coherence to form the Oracle WebLogic Suite. In addition, Oracle WebLogic Application Grid provides the necessary Java infrastructure for extreme transaction processing (XTP).
Oracle WebLogic Suite and Oracle WebLogic Application Grid are Oracle Fusion Middleware's strategic application server products. Learn more about these products and their role in Oracle's middleware strategy. Oracle Application Server customers will benefit from ongoing development and Oracle's commitment to integrate its best capabilities with Oracle WebLogic Server over time.
Oracle Service-Oriented Architecture
eading companies are gaining operational efficiencies and business agility through adaptable, re-usable business processes and services built on a truly flexible Service-Oriented Architecture (SOA) foundation. Oracle SOA products allow you to build, deploy, and manage SOA with integrated, best-in-class technology that provides:
* Comprehensive and Pre-Integrated SOA Platform—Complete set of service and process infrastructure components for building, deploying, and managing SOAs
* Closed-Loop Governance—Comprehensive, end-to-end lifecycle governance of services
* Extreme performance and scalability—In-memory transactions, real-time event processing, and high-volume data transfer on top of a highly scalable application server
* Integrated Security—Centralized policy management, enterprise-grade, end-to-end security
Oracle SOA Suite, which now includes the former BEA AquaLogic Service Bus, is Oracle Fusion Middleware's strategic product for SOA. Oracle plans to continue to develop and support Oracle WebLogic Integration, and expects to converge this product with Oracle's strategic solutions over time. Existing deployments of this product will benefit from complementary products such as Oracle SOA Suite. Learn more about Oracle SOA Suite's role in Oracle's middleware strategy.
THE #1 APPLICATION SERVER
The Oracle WebLogic Application Server product line is the industry's most comprehensive platform for developing, deploying, and integrating enterprise applications. At the center of the product line is Oracle WebLogic Server, a powerful and scalable Java EE server. It combines with Oracle Application Server and additional performance enhancing products such as Oracle JRockit and Oracle Coherence to form the Oracle WebLogic Suite. In addition, Oracle WebLogic Application Grid provides the necessary Java infrastructure for extreme transaction processing (XTP).
Oracle WebLogic Suite and Oracle WebLogic Application Grid are Oracle Fusion Middleware's strategic application server products. Learn more about these products and their role in Oracle's middleware strategy. Oracle Application Server customers will benefit from ongoing development and Oracle's commitment to integrate its best capabilities with Oracle WebLogic Server over time.
Oracle Service-Oriented Architecture
eading companies are gaining operational efficiencies and business agility through adaptable, re-usable business processes and services built on a truly flexible Service-Oriented Architecture (SOA) foundation. Oracle SOA products allow you to build, deploy, and manage SOA with integrated, best-in-class technology that provides:
* Comprehensive and Pre-Integrated SOA Platform—Complete set of service and process infrastructure components for building, deploying, and managing SOAs
* Closed-Loop Governance—Comprehensive, end-to-end lifecycle governance of services
* Extreme performance and scalability—In-memory transactions, real-time event processing, and high-volume data transfer on top of a highly scalable application server
* Integrated Security—Centralized policy management, enterprise-grade, end-to-end security
Oracle SOA Suite, which now includes the former BEA AquaLogic Service Bus, is Oracle Fusion Middleware's strategic product for SOA. Oracle plans to continue to develop and support Oracle WebLogic Integration, and expects to converge this product with Oracle's strategic solutions over time. Existing deployments of this product will benefit from complementary products such as Oracle SOA Suite. Learn more about Oracle SOA Suite's role in Oracle's middleware strategy.
Sunday, March 22, 2009
Brief history of ITIL
Brief history of ITIL
End of the 1980s
Following a series of high profile failed Public Sector IT projects that were reported in the media, resulting in much criticism and debate levied at the government in power, the Central Communications and Telecommunications Agency (CCTA) commissioned and managed the production of the Information Technology Infrastructure Library (ITIL). The production centred on the areas of Service Support and Service Delivery, involving various organizations and experts working in the IT industry sector at the time.
1991
During this period a series of ten books were published covering the areas of ITIL Service Support and ITIL Service Delivery.
1991
The commercial potential of ITIL begins to be realized. A selection of private sector organizations as well as the UK governments Civil Service College are invited to become ITIL training providers. In addition the Information Systems Examination Board (ISEB) part of the British Computer Society (BCS) agree to deliver and administer the first ITIL examination - the ITIL Managers Certificate.
Gradually organizations from all industry sectors both private and public begin to seize upon the benefits of ITIL
1993
In the Netherlands, the Examination Institute for Information Science (EXIN) is established to deliver ad administer the ITIL examination.
1993-1994
The ITIL Foundation course is launched providing a three-day introduction or entry level into ITIL with a multiple-choice examination being provided.
1995
Continued international interest grows with regards ITIL and adoption of the best practice increases.
1998 - 1999
Work commences to update ITIL, leading to the eventual production of version 2.
1999 - 2000
The British standard for IT Service Management, BS15000 is developed with the input from several organisations from various industry sectors.
2000 - 2001
In North America the Loyalist College based in Ontario in Canada becomes an authorised examination board
2000
ITIL Service Support (version 2) book is published by the Office of Government Commerce (OGC). The Central Communications and Telecommunications Agency (CCTA) changes its name to the Office of Government Commerce (OGC).
2001
Microsoft release the Microsoft Operational Framework (MOF) based upon ITIL.
2001
OGC release the ITIL Service Delivery book
2001/02
EXIN introduce the first ITIL Practitioner courses and examinations
2002
With the sudden downturn in the world economy, organizations look internally for ways of reducing costs and becoming more efficient and competitive. ITIL is recognized as a solution and its popularity continues to grow
2003/04
The British Computer Society's ISEB introduces ITIL Practitioner courses and examinations.
2005
OGC announce that work is to commence on the production of ITIL version 3, which is planned for release at the end of 2006 or early 2007.
2005
BS15000 version 2 is released, once again based upon ITIL. Registered Certification Bodies (RCBs) and accredited BS15000 Training organizations are established.
2005
In December BS15000 is superseded by ISO/IEC 20000 version 1, once again based upon ITIL best practices.
2006/07
2007 OGC release ITIL Version 3. The scope of ITIL V3 expands to cover the complete Service Lifecycle. Five core ITIL books are produced covering Service Strategy, Service Design, Service Transition, Service Operation and Continual Service Improvement.
2007 OGC announces that the APM Group (APMG) are awarded contract to become the ITIL Official Accreditor.
2007 ITIL Foundation course is released to the marketplace, although debate continues around the shape of the ITIL Certification Scheme together with the associated 'points' scheme.
2007 November - ITIL Managers Bridge course released to market.
2008 ISO/IEC 20000 Foundation course released to the market.
2008 Plans are announced to update and expand ISO/IEC 20000 over the next twenty-four months.
2008 APMG announces that the 'ITIL Lifecycle and Capability' courses will be released to market in two phases, October 2008 and January 2009.
October 1, 2008
* Service Lifecycle Modules:
o Service Transition
o Service Operation
* Service Capability Modules:
o Service Offerings & Agreements
o Operational Support & Analysis
o Release, Control & Validation
January 1, 2009
* Service Lifecycle Modules:
o Service Strategy
o Service Design
o Continual Service Improvement
o Managing Across the Lifecycle
* Service Capability Modules:
End of the 1980s
Following a series of high profile failed Public Sector IT projects that were reported in the media, resulting in much criticism and debate levied at the government in power, the Central Communications and Telecommunications Agency (CCTA) commissioned and managed the production of the Information Technology Infrastructure Library (ITIL). The production centred on the areas of Service Support and Service Delivery, involving various organizations and experts working in the IT industry sector at the time.
1991
During this period a series of ten books were published covering the areas of ITIL Service Support and ITIL Service Delivery.
1991
The commercial potential of ITIL begins to be realized. A selection of private sector organizations as well as the UK governments Civil Service College are invited to become ITIL training providers. In addition the Information Systems Examination Board (ISEB) part of the British Computer Society (BCS) agree to deliver and administer the first ITIL examination - the ITIL Managers Certificate.
Gradually organizations from all industry sectors both private and public begin to seize upon the benefits of ITIL
1993
In the Netherlands, the Examination Institute for Information Science (EXIN) is established to deliver ad administer the ITIL examination.
1993-1994
The ITIL Foundation course is launched providing a three-day introduction or entry level into ITIL with a multiple-choice examination being provided.
1995
Continued international interest grows with regards ITIL and adoption of the best practice increases.
1998 - 1999
Work commences to update ITIL, leading to the eventual production of version 2.
1999 - 2000
The British standard for IT Service Management, BS15000 is developed with the input from several organisations from various industry sectors.
2000 - 2001
In North America the Loyalist College based in Ontario in Canada becomes an authorised examination board
2000
ITIL Service Support (version 2) book is published by the Office of Government Commerce (OGC). The Central Communications and Telecommunications Agency (CCTA) changes its name to the Office of Government Commerce (OGC).
2001
Microsoft release the Microsoft Operational Framework (MOF) based upon ITIL.
2001
OGC release the ITIL Service Delivery book
2001/02
EXIN introduce the first ITIL Practitioner courses and examinations
2002
With the sudden downturn in the world economy, organizations look internally for ways of reducing costs and becoming more efficient and competitive. ITIL is recognized as a solution and its popularity continues to grow
2003/04
The British Computer Society's ISEB introduces ITIL Practitioner courses and examinations.
2005
OGC announce that work is to commence on the production of ITIL version 3, which is planned for release at the end of 2006 or early 2007.
2005
BS15000 version 2 is released, once again based upon ITIL. Registered Certification Bodies (RCBs) and accredited BS15000 Training organizations are established.
2005
In December BS15000 is superseded by ISO/IEC 20000 version 1, once again based upon ITIL best practices.
2006/07
2007 OGC release ITIL Version 3. The scope of ITIL V3 expands to cover the complete Service Lifecycle. Five core ITIL books are produced covering Service Strategy, Service Design, Service Transition, Service Operation and Continual Service Improvement.
2007 OGC announces that the APM Group (APMG) are awarded contract to become the ITIL Official Accreditor.
2007 ITIL Foundation course is released to the marketplace, although debate continues around the shape of the ITIL Certification Scheme together with the associated 'points' scheme.
2007 November - ITIL Managers Bridge course released to market.
2008 ISO/IEC 20000 Foundation course released to the market.
2008 Plans are announced to update and expand ISO/IEC 20000 over the next twenty-four months.
2008 APMG announces that the 'ITIL Lifecycle and Capability' courses will be released to market in two phases, October 2008 and January 2009.
October 1, 2008
* Service Lifecycle Modules:
o Service Transition
o Service Operation
* Service Capability Modules:
o Service Offerings & Agreements
o Operational Support & Analysis
o Release, Control & Validation
January 1, 2009
* Service Lifecycle Modules:
o Service Strategy
o Service Design
o Continual Service Improvement
o Managing Across the Lifecycle
* Service Capability Modules:
ITIL Refresh Project / ITIL Version 3
A six month project was launched by the 'owners of ITIL', Office of Government Commerce (OGC) based in the UK, on the 8th November 2004, to define the scope of and development plans for a refreshed version of ITIL best practice guidance. The OGC from January through to March 2005 consulted and collected opinions from ITIL users, educationalists and vendors from around the world. Having analysed the feedback the subsequent scope of the ITIL Refresh project was founded based upon areas where high degrees of consensus were found.
The development stages started in August 2005 and are planned to be completed in December 2006, with the publication of the 'core' intended for February 2007.
The 'core' represents the generic principles of ITIL guidance, but has been expanded to incorporate the life-cycle stages of Service Management. In addition to the 'core' publications will be 'complementary guidance' and 'value added products to assist organizations in the context of:
* Business environments
* Economic conditions
* Organizational strategies
Five volumes will comprise of the 'core' publications:
* Service Strategy (SS)
* Service Design (SD)
* Service Transition (ST)
* Service Operation (SO)
* Continual Service Improvement (CSI)
The January to March 2005 consultation identified the following finding, which have moulded and shaped ITIL Version 3:
* Consistent structure and navigation
* Preserve key concepts - no radical changes to Service Support and Service Delivery
* Reflect the service life cycle - strategic to operational as a Service Management framework
* Organizational structures and models for Service Management
* Dealing with cultural issues
* Refer to other best practices
* Business case examples, case studies, templates, implementation work packages
* ITIL in multi-sourced environments
* Alignment to other frameworks
* Scalability
* Remain non prescriptive
* Return on investment
* Quality of authoring
* Improved standard terms and definitions
* Address IT governance
* Executive-level awareness and marketing
* Evaluation guidance for tools
* Key performance metrics
* Improved self-assessment
* Reduce the core and increase ancillary guidance
* Integrated process model
* Quick wins in each process
ITIL Version 2
Service Support
Service Desk
Incident Management
Problem Management
Change Management
Release Management
Configuration Management
Service Delivery
Service Level Management
Availability Management
Capacity Management
Financial Management
IT Service Continuity Management
ITIL Version 3
Core Publications
Service Strategy (SS)
Financial Management
Service Design (SD)
Service Level Management
Capacity Management
Availability Management
IT Service Continuity Management
Service Transition (ST)
Change Management
Configuration Management
Release Management
Incident Management
Problem Management
Service Operation (SO)
Change Management
Configuration Management
Release Management
Service Desk
Incident Management
Problem Management
Capacity Management
Availaibility Management
Financial Management
IT Service Continuity Management
Continual Service Improvement (CSI)
The development stages started in August 2005 and are planned to be completed in December 2006, with the publication of the 'core' intended for February 2007.
The 'core' represents the generic principles of ITIL guidance, but has been expanded to incorporate the life-cycle stages of Service Management. In addition to the 'core' publications will be 'complementary guidance' and 'value added products to assist organizations in the context of:
* Business environments
* Economic conditions
* Organizational strategies
Five volumes will comprise of the 'core' publications:
* Service Strategy (SS)
* Service Design (SD)
* Service Transition (ST)
* Service Operation (SO)
* Continual Service Improvement (CSI)
The January to March 2005 consultation identified the following finding, which have moulded and shaped ITIL Version 3:
* Consistent structure and navigation
* Preserve key concepts - no radical changes to Service Support and Service Delivery
* Reflect the service life cycle - strategic to operational as a Service Management framework
* Organizational structures and models for Service Management
* Dealing with cultural issues
* Refer to other best practices
* Business case examples, case studies, templates, implementation work packages
* ITIL in multi-sourced environments
* Alignment to other frameworks
* Scalability
* Remain non prescriptive
* Return on investment
* Quality of authoring
* Improved standard terms and definitions
* Address IT governance
* Executive-level awareness and marketing
* Evaluation guidance for tools
* Key performance metrics
* Improved self-assessment
* Reduce the core and increase ancillary guidance
* Integrated process model
* Quick wins in each process
ITIL Version 2
Service Support
Service Desk
Incident Management
Problem Management
Change Management
Release Management
Configuration Management
Service Delivery
Service Level Management
Availability Management
Capacity Management
Financial Management
IT Service Continuity Management
ITIL Version 3
Core Publications
Service Strategy (SS)
Financial Management
Service Design (SD)
Service Level Management
Capacity Management
Availability Management
IT Service Continuity Management
Service Transition (ST)
Change Management
Configuration Management
Release Management
Incident Management
Problem Management
Service Operation (SO)
Change Management
Configuration Management
Release Management
Service Desk
Incident Management
Problem Management
Capacity Management
Availaibility Management
Financial Management
IT Service Continuity Management
Continual Service Improvement (CSI)
Friday, March 20, 2009
CCNP Certification
CCNP Certification
Cisco Certified Network Professional (CCNP®) validates knowledge and skills required to install, configure and troubleshoot converged local and wide area networks with 100 to 500 or more nodes. With a CCNP certification, a network professional demonstrates the knowledge and skills required to manage the routers and switches that form the network core, as well as edge applications that integrate voice, wireless, and security into the network. The CCNP curriculum includes building scalable Cisco networks, Cisco multilayer switched networks, securing converged wide area networks, and optimizing converged networks.
CCNP syllabus
Partners: Log in for Partner E-Learning Connection (PEC) learning map
* CCNP Track I Learning Map
* CCNP Track II Learning Map
CCNP Recertification
Cisco professional level certifications (CCDA, CCNP, CCDP, CCSP, CCVP, and CCIP) are valid for three years. To recertify, pass any 642 exam that is part of the professional level curriculum or any CCIE/CCDE written exam before the certification expiration date.
Achieving or recertifying any of the certifications above automatically extends your active Associate and Professional level certification(s) up to the point of expiration of the last certification achieved. For more information, access the Cisco About Recertification page.
Additional Information
The Cisco Learning Network brings you the latest in social networking, certifications content, games, blogs, discussion forums and more!
Click here to be a part of the Cisco Learning Network.
Register to create your own personal account. You will have to create a new account as your current logins will not work. Accessing premium content and participating in the social networking activities requires a Cisco Learning Network registration. Those who already have a Cisco.com account are encouraged to use the same user ID and email address when registering on the Cisco Learning Network site.
Cisco Certified Network Professional (CCNP®) validates knowledge and skills required to install, configure and troubleshoot converged local and wide area networks with 100 to 500 or more nodes. With a CCNP certification, a network professional demonstrates the knowledge and skills required to manage the routers and switches that form the network core, as well as edge applications that integrate voice, wireless, and security into the network. The CCNP curriculum includes building scalable Cisco networks, Cisco multilayer switched networks, securing converged wide area networks, and optimizing converged networks.
CCNP syllabus
Partners: Log in for Partner E-Learning Connection (PEC) learning map
* CCNP Track I Learning Map
* CCNP Track II Learning Map
CCNP Recertification
Cisco professional level certifications (CCDA, CCNP, CCDP, CCSP, CCVP, and CCIP) are valid for three years. To recertify, pass any 642 exam that is part of the professional level curriculum or any CCIE/CCDE written exam before the certification expiration date.
Achieving or recertifying any of the certifications above automatically extends your active Associate and Professional level certification(s) up to the point of expiration of the last certification achieved. For more information, access the Cisco About Recertification page.
Additional Information
The Cisco Learning Network brings you the latest in social networking, certifications content, games, blogs, discussion forums and more!
Click here to be a part of the Cisco Learning Network.
Register to create your own personal account. You will have to create a new account as your current logins will not work. Accessing premium content and participating in the social networking activities requires a Cisco Learning Network registration. Those who already have a Cisco.com account are encouraged to use the same user ID and email address when registering on the Cisco Learning Network site.
Windows Internet Explorer 8
Windows Internet Explorer 8 (abbreviated IE8) is a web browser by Microsoft. It is the successor to the 2006 release of Internet Explorer 7, and will be the default browser for the upcoming Windows 7 and Windows Server 2008 R2 operating systems. The browser was released on March 19, 2009 for Windows XP, Windows Server 2003, Windows Vista and Windows Server 2008.[1]
According to Microsoft, security, ease of use, and improvements in RSS, Cascading Style Sheets, and Ajax support were its priorities for Internet Explorer 8.[2]
History
IE8 has been in development since at least March 2006.[4] In February 2008, Microsoft sent out private invitations for IE8 Beta 1,[5] and on March 5, 2008, released Beta 1 to the general public,[6] although with a focus on web developers.[7] The release launched with a Windows Internet Explorer 8 Readiness Toolkit website promoting IE8 white papers, related software tools, and new features in addition to download links to the Beta.[6][8] The Microsoft Developer Network (MSDN) added new sections detailing new IE8 technology.[6][8][9] Major press focused on a controversy about Version Targeting, and two new features then called WebSlice and Activities. The readiness toolkit was promoted as something "developers can exploit to make Internet Explorer 8 'light up'." [6]
On August 27, 2008, Microsoft made IE8 Beta 2 generally available.[10] PC World noted various Beta 2 features such as InPrivate mode, tab isolation and color coding, and improved standards and compatibility compared to Internet Explorer 7.[11] Two name changes included Activities to Accelerators, and the IE7 Phishing filter renamed Safety Filter in the first Beta to SmartScreen, both accompanied by incremental technical changes as well.[11] By August 2008 the new feature called InPrivate had taken the spotlight.[11]
Final version for Windows XP/Vista/Server 2003 has been released to public at noon EDT on March 19th 2009 , with edition embedded within Windows 7 still being in development along with operating system, due to extra functionality related to the new operating system (touch support, new taskbar features etc.).[citation needed]
[edit] Features
[edit] Overview
The first beta release of IE8, which was demonstrated at the MIX08 conference, contained many new features, including WebSlices and Activities.[12] In the second beta release, Activities were renamed to Accelerators.[13]
[edit] Added features
Some of the features and changes for the Beta 2 compared to Beta 1.[11]
* InPrivate[11]
* Delete Browsing History
* Search Suggestions
* User Preference Protection
* Caret Browsing
* Accelerators (previously known as Activities)
* Web Slices (previously known as WebSlices)[11]
* Suggested Sites
* Tab Color Grouping[11]
* Automatic Crash Recovery
* SmartScreen Filter (Known as Safety Filter in Beta 1)
* Tab isolation (tabs spread over separate operating system processes)
[edit] Removed features
* Inline AutoComplete[14]
* The option to delete files and settings stored by addons or ActiveX controls; rather, it is performed automatically.[15]
* CSS Expressions are no longer supported in Internet Explorer 8 Standards mode[16]
* Support for the proprietary tag is dropped
[edit] Suggested Sites
This feature is described by Microsoft as a tool to suggest websites, which is done by the browser sending information to Microsoft over a secure connection, which keeps the information and a per-session, uniqely-generated identifier for a short time.[17] Suggested Sites is off by default, and disabled when the user is browsing with InPrivate enabled, or is visiting SSL-secured, intranet, IP address, or IDN address sites. Potentially personally-identifiable information such as the user's IP address and browser information is sent to Microsoft as an artifact of the HTTPS protocol. Microsoft has stated that they do not store this information.
The functionality was defended by Microsoft after itworld.com's Gregg Keizer described it as a "phone home" feature.[18]
[edit] InPrivate
Internet Explorer 8 in InPrivate mode.
A new security mode called InPrivate debuted with Beta 2, which consists of three main features: InPrivate Browsing, InPrivate Blocking, and InPrivate Subscription.[11] Like similar privacy protection modes in Safari and Google Chrome, InPrivate Browsing has been described as a "porn mode" in various news outlets.[19][20][21][22][23][24][25][26] Informationweek mentioned it as a "'Stealth' Privacy Mode".[27]
Gregg Keizer of Computerworld says Private Blocking "notifies users of third-party content that can track browsing history", and that InPrivate Subscription allows "subscribing to lists of sites to block".[27] When enabled, IE8 will not save browsing and searching history, cookies, form data and passwords; it also will automatically clear the browser cache.[27]
[edit] Accelerators
Example of a map Accelerator using the IE8 Accelerators Smart tag.
Accelerators are a form of selection-based search which allow a user to invoke an online service from any other page using only the mouse.[28] Actions such as selecting the text or other objects will give users access to the usable Accelerator services (such as blogging with the selected text, or viewing a map of a selected geographical location), which can then be invoked with the selected object. According to Microsoft, Accelerators eliminate the need to copy and paste content between web pages.[12] IE8 specifies an XML-based encoding which allows a web application or web service to be invoked as an Accelerator service. How the service will be invoked and for what categories of content it will show up is specified in the XML file.[29] Similarities have been drawn between Accelerators and the controversial Smart tags, feature experimented with in the IE 6 Beta but withdrawn after criticism (though later included in MS Office)
According to Microsoft, security, ease of use, and improvements in RSS, Cascading Style Sheets, and Ajax support were its priorities for Internet Explorer 8.[2]
History
IE8 has been in development since at least March 2006.[4] In February 2008, Microsoft sent out private invitations for IE8 Beta 1,[5] and on March 5, 2008, released Beta 1 to the general public,[6] although with a focus on web developers.[7] The release launched with a Windows Internet Explorer 8 Readiness Toolkit website promoting IE8 white papers, related software tools, and new features in addition to download links to the Beta.[6][8] The Microsoft Developer Network (MSDN) added new sections detailing new IE8 technology.[6][8][9] Major press focused on a controversy about Version Targeting, and two new features then called WebSlice and Activities. The readiness toolkit was promoted as something "developers can exploit to make Internet Explorer 8 'light up'." [6]
On August 27, 2008, Microsoft made IE8 Beta 2 generally available.[10] PC World noted various Beta 2 features such as InPrivate mode, tab isolation and color coding, and improved standards and compatibility compared to Internet Explorer 7.[11] Two name changes included Activities to Accelerators, and the IE7 Phishing filter renamed Safety Filter in the first Beta to SmartScreen, both accompanied by incremental technical changes as well.[11] By August 2008 the new feature called InPrivate had taken the spotlight.[11]
Final version for Windows XP/Vista/Server 2003 has been released to public at noon EDT on March 19th 2009 , with edition embedded within Windows 7 still being in development along with operating system, due to extra functionality related to the new operating system (touch support, new taskbar features etc.).[citation needed]
[edit] Features
[edit] Overview
The first beta release of IE8, which was demonstrated at the MIX08 conference, contained many new features, including WebSlices and Activities.[12] In the second beta release, Activities were renamed to Accelerators.[13]
[edit] Added features
Some of the features and changes for the Beta 2 compared to Beta 1.[11]
* InPrivate[11]
* Delete Browsing History
* Search Suggestions
* User Preference Protection
* Caret Browsing
* Accelerators (previously known as Activities)
* Web Slices (previously known as WebSlices)[11]
* Suggested Sites
* Tab Color Grouping[11]
* Automatic Crash Recovery
* SmartScreen Filter (Known as Safety Filter in Beta 1)
* Tab isolation (tabs spread over separate operating system processes)
[edit] Removed features
* Inline AutoComplete[14]
* The option to delete files and settings stored by addons or ActiveX controls; rather, it is performed automatically.[15]
* CSS Expressions are no longer supported in Internet Explorer 8 Standards mode[16]
* Support for the proprietary tag is dropped
[edit] Suggested Sites
This feature is described by Microsoft as a tool to suggest websites, which is done by the browser sending information to Microsoft over a secure connection, which keeps the information and a per-session, uniqely-generated identifier for a short time.[17] Suggested Sites is off by default, and disabled when the user is browsing with InPrivate enabled, or is visiting SSL-secured, intranet, IP address, or IDN address sites. Potentially personally-identifiable information such as the user's IP address and browser information is sent to Microsoft as an artifact of the HTTPS protocol. Microsoft has stated that they do not store this information.
The functionality was defended by Microsoft after itworld.com's Gregg Keizer described it as a "phone home" feature.[18]
[edit] InPrivate
Internet Explorer 8 in InPrivate mode.
A new security mode called InPrivate debuted with Beta 2, which consists of three main features: InPrivate Browsing, InPrivate Blocking, and InPrivate Subscription.[11] Like similar privacy protection modes in Safari and Google Chrome, InPrivate Browsing has been described as a "porn mode" in various news outlets.[19][20][21][22][23][24][25][26] Informationweek mentioned it as a "'Stealth' Privacy Mode".[27]
Gregg Keizer of Computerworld says Private Blocking "notifies users of third-party content that can track browsing history", and that InPrivate Subscription allows "subscribing to lists of sites to block".[27] When enabled, IE8 will not save browsing and searching history, cookies, form data and passwords; it also will automatically clear the browser cache.[27]
[edit] Accelerators
Example of a map Accelerator using the IE8 Accelerators Smart tag.
Accelerators are a form of selection-based search which allow a user to invoke an online service from any other page using only the mouse.[28] Actions such as selecting the text or other objects will give users access to the usable Accelerator services (such as blogging with the selected text, or viewing a map of a selected geographical location), which can then be invoked with the selected object. According to Microsoft, Accelerators eliminate the need to copy and paste content between web pages.[12] IE8 specifies an XML-based encoding which allows a web application or web service to be invoked as an Accelerator service. How the service will be invoked and for what categories of content it will show up is specified in the XML file.[29] Similarities have been drawn between Accelerators and the controversial Smart tags, feature experimented with in the IE 6 Beta but withdrawn after criticism (though later included in MS Office)
Wednesday, March 18, 2009
Windows 7
Windows 7 (formerly codenamed Blackcomb and Vienna) will be the next release of Microsoft Windows, an operating system produced by Microsoft for use on personal computers, including home and business desktops, laptops, Tablet PCs, netbooks[1] and media center PCs.[2] Microsoft stated in 2007 they were planning Windows 7 development for a three-year time frame starting after the release of its predecessor, Windows Vista. Microsoft has stated that the final release date would be determined by product quality.[3]
Unlike its predecessor, Windows 7 is intended to be an incremental upgrade from Vista, with the goal of being fully compatible with device drivers, applications, and hardware with which Windows Vista is already compatible.[4] Presentations given by the company in 2008 have focused on multi-touch support, a redesigned Windows Shell with a new taskbar, a home networking system called HomeGroup,[5] and performance improvements. Some applications that have been included with prior releases of Microsoft Windows, most notably Windows Movie Maker, and Windows Photo Gallery, are no longer included with the operating system; they are instead offered separately (free of charge) as part of the Windows Live Essentials suite.[6]
Originally, a version of Windows codenamed Blackcomb was planned as the successor to Windows XP and Windows Server 2003. Major features were planned for Blackcomb, including an emphasis on searching and querying data and an advanced storage system named WinFS to enable such scenarios. Later, Blackcomb was delayed and an interim, minor release, codenamed "Longhorn" was announced for 2003.[7] By the middle of 2003, however, Longhorn had acquired some of the features originally intended for Blackcomb. After three major viruses exploited flaws in Windows operating systems within a short time period in 2003, Microsoft changed its development priorities, putting some of Longhorn's major development work on hold in order to develop new service packs for Windows XP and Windows Server 2003. Development of Longhorn (Windows Vista) was also "reset" in September 2004.
Blackcomb was renamed Vienna in early 2006,[8] and again to Windows 7 in 2007.[3] In 2008, it was announced that Windows 7 would also be the official name of the operating system.[9][10] The first external release to select Microsoft partners came in January 2008 with Milestone 1 (build 6519).[11]
Bill Gates, in an interview with Newsweek, suggested that the next version of Windows would "be more user-centric".[12] Gates later said that Windows 7 will also focus on performance improvements;[13] Steven Sinofsky later expanded on this point, explaining in the Engineering Windows 7 blog that the company was using a variety of new tracing tools to measure the performance of many areas of the operating system on an ongoing basis, to help locate inefficient code paths and to help prevent performance regressions.[14]
Senior Vice President Bill Veghte stated that Windows 7 will not have the kind of compatibility issues with Windows Vista that Vista has with previous versions.[15] Speaking about Windows 7 on 16 October 2008, Microsoft CEO Steve Ballmer confirmed compatibility between Vista and Windows 7.[16] Ballmer also confirmed the relationship between Vista and Windows 7, indicating that Windows 7 will be an improved version of Vista.[16]
On 27 December 2008 Windows 7 Beta was leaked onto the Internet.[17] According to a performance test by ZDNet,[18] Windows 7 Beta has beaten both Windows XP and Vista in several key areas, including boot and shut down time, working with files and loading documents; others, including PC Pro benchmarks for typical office activities and video-editing, remain identical to Vista and slower than XP.[19] On 7 January 2009, the 64-bit version of the Windows 7 Beta (build 7000) was leaked onto the web.[20]
The official beta, announced at the CES 2009, was made available to MSDN and TechNet subscribers on 7 January 2009[21] and was made briefly available for public download on Microsoft TechNet on 9 January 2009 before being withdrawn and replaced with a coming soon message. The servers were experiencing difficulty in dealing with the number of users who wished to download the beta. Microsoft added additional servers to cope with the large volume of interest from the public.[22] Due to the unexpectedly high demand, Microsoft also decided to remove its initial 2.5 million download limit and make it available to the public until January 24 2009[23], and later until February 10, from where it was no longer available to the public, although paused or deferred downloads of the DVD image files still worked until February 12.[24]
Users can still download Windows 7 via the Microsoft Connect program. According to Windows 7 Center, the release candidate is scheduled to be publicly released in the last week of May.[25]
Unlike its predecessor, Windows 7 is intended to be an incremental upgrade from Vista, with the goal of being fully compatible with device drivers, applications, and hardware with which Windows Vista is already compatible.[4] Presentations given by the company in 2008 have focused on multi-touch support, a redesigned Windows Shell with a new taskbar, a home networking system called HomeGroup,[5] and performance improvements. Some applications that have been included with prior releases of Microsoft Windows, most notably Windows Movie Maker, and Windows Photo Gallery, are no longer included with the operating system; they are instead offered separately (free of charge) as part of the Windows Live Essentials suite.[6]
Originally, a version of Windows codenamed Blackcomb was planned as the successor to Windows XP and Windows Server 2003. Major features were planned for Blackcomb, including an emphasis on searching and querying data and an advanced storage system named WinFS to enable such scenarios. Later, Blackcomb was delayed and an interim, minor release, codenamed "Longhorn" was announced for 2003.[7] By the middle of 2003, however, Longhorn had acquired some of the features originally intended for Blackcomb. After three major viruses exploited flaws in Windows operating systems within a short time period in 2003, Microsoft changed its development priorities, putting some of Longhorn's major development work on hold in order to develop new service packs for Windows XP and Windows Server 2003. Development of Longhorn (Windows Vista) was also "reset" in September 2004.
Blackcomb was renamed Vienna in early 2006,[8] and again to Windows 7 in 2007.[3] In 2008, it was announced that Windows 7 would also be the official name of the operating system.[9][10] The first external release to select Microsoft partners came in January 2008 with Milestone 1 (build 6519).[11]
Bill Gates, in an interview with Newsweek, suggested that the next version of Windows would "be more user-centric".[12] Gates later said that Windows 7 will also focus on performance improvements;[13] Steven Sinofsky later expanded on this point, explaining in the Engineering Windows 7 blog that the company was using a variety of new tracing tools to measure the performance of many areas of the operating system on an ongoing basis, to help locate inefficient code paths and to help prevent performance regressions.[14]
Senior Vice President Bill Veghte stated that Windows 7 will not have the kind of compatibility issues with Windows Vista that Vista has with previous versions.[15] Speaking about Windows 7 on 16 October 2008, Microsoft CEO Steve Ballmer confirmed compatibility between Vista and Windows 7.[16] Ballmer also confirmed the relationship between Vista and Windows 7, indicating that Windows 7 will be an improved version of Vista.[16]
On 27 December 2008 Windows 7 Beta was leaked onto the Internet.[17] According to a performance test by ZDNet,[18] Windows 7 Beta has beaten both Windows XP and Vista in several key areas, including boot and shut down time, working with files and loading documents; others, including PC Pro benchmarks for typical office activities and video-editing, remain identical to Vista and slower than XP.[19] On 7 January 2009, the 64-bit version of the Windows 7 Beta (build 7000) was leaked onto the web.[20]
The official beta, announced at the CES 2009, was made available to MSDN and TechNet subscribers on 7 January 2009[21] and was made briefly available for public download on Microsoft TechNet on 9 January 2009 before being withdrawn and replaced with a coming soon message. The servers were experiencing difficulty in dealing with the number of users who wished to download the beta. Microsoft added additional servers to cope with the large volume of interest from the public.[22] Due to the unexpectedly high demand, Microsoft also decided to remove its initial 2.5 million download limit and make it available to the public until January 24 2009[23], and later until February 10, from where it was no longer available to the public, although paused or deferred downloads of the DVD image files still worked until February 12.[24]
Users can still download Windows 7 via the Microsoft Connect program. According to Windows 7 Center, the release candidate is scheduled to be publicly released in the last week of May.[25]
What hardware do you need for VoIP?
What hardware do you need for VoIP?
Basically three things are required:
* High speed broadband internet connection
* Standard home phone (almost anyone will do)
* VoIP adapter of VoIP software
There are a number of various devices out on the market right now to help with the use of VoIP:
* ATA Adapter
* IP-PBX Systems
* SIP & VoIP Gateways
* VoIP Switches
* VoIP Routers
Broadband Internet
A high speed internet connection, otherwise known as a broadband internet connection, is one where you are able to send and receive information on the Internet at a high speed rate. Hence the name, 'high speed internet'.
Your local cable or phone company may already be providing high speed service such as 'cable Internet' or 'DSL' service.
Hot deals on voip+router and vonage
Linksys VOIP Single Port Router 2 Phone SPA2102-PU NEW
US $20.50 (6 Bids)
Monday Mar-16-2009 19:24:30 PDT
Vonage - Linksys Wireless - G Router WRTP54G VOIP
US $22.50 (4 Bids)
Monday Mar-16-2009 19:29:00 PDT
Linksys SPA2102-R VOIP Phone Adapter with Router
US $6.99 (1 Bid)
Monday Mar-16-2009 19:50:31 PDT
Linksys VOIP 2 line Single port Router SPA2102 SAVE$$
US $32.00 (7 Bids)
Monday Mar-16-2009 20:28:41 PDT
Vonage - Linksys Wireless - G Router WRTP54G VOIP
US $22.50 (4 Bids)
Monday Mar-16-2009 19:29:00 PDT
UTStarcom F1000 Vonage Wireless WiFi VOIP Phone Black
US $16.45 (2 Bids)
Monday Mar-16-2009 19:31:16 PDT
Vonage V-Portal Phone Adapter
US $30.00 (0 Bid)
Monday Mar-16-2009 20:21:01 PDT
New D-Link VTA-VR Broadband Telephone Adapter Vonage
US $24.98 (1 Bid)
Monday Mar-16-2009 20:46:41 PDT
Basically three things are required:
* High speed broadband internet connection
* Standard home phone (almost anyone will do)
* VoIP adapter of VoIP software
There are a number of various devices out on the market right now to help with the use of VoIP:
* ATA Adapter
* IP-PBX Systems
* SIP & VoIP Gateways
* VoIP Switches
* VoIP Routers
Broadband Internet
A high speed internet connection, otherwise known as a broadband internet connection, is one where you are able to send and receive information on the Internet at a high speed rate. Hence the name, 'high speed internet'.
Your local cable or phone company may already be providing high speed service such as 'cable Internet' or 'DSL' service.
Hot deals on voip+router and vonage
Linksys VOIP Single Port Router 2 Phone SPA2102-PU NEW
US $20.50 (6 Bids)
Monday Mar-16-2009 19:24:30 PDT
Vonage - Linksys Wireless - G Router WRTP54G VOIP
US $22.50 (4 Bids)
Monday Mar-16-2009 19:29:00 PDT
Linksys SPA2102-R VOIP Phone Adapter with Router
US $6.99 (1 Bid)
Monday Mar-16-2009 19:50:31 PDT
Linksys VOIP 2 line Single port Router SPA2102 SAVE$$
US $32.00 (7 Bids)
Monday Mar-16-2009 20:28:41 PDT
Vonage - Linksys Wireless - G Router WRTP54G VOIP
US $22.50 (4 Bids)
Monday Mar-16-2009 19:29:00 PDT
UTStarcom F1000 Vonage Wireless WiFi VOIP Phone Black
US $16.45 (2 Bids)
Monday Mar-16-2009 19:31:16 PDT
Vonage V-Portal Phone Adapter
US $30.00 (0 Bid)
Monday Mar-16-2009 20:21:01 PDT
New D-Link VTA-VR Broadband Telephone Adapter Vonage
US $24.98 (1 Bid)
Monday Mar-16-2009 20:46:41 PDT
Sunday, March 15, 2009
Voice over Internet Protocol (VoIP)
Voice over Internet Protocol (VoIP) is a general term for a family of transmission technologies for delivery of voice communications over IP networks such as the Internet or other packet-switched networks. Other terms frequently encountered and synonymous with VoIP are IP telephony, Internet telephony, voice over broadband (VoBB), broadband telephony, and broadband phone.
VoIP systems usually interface with the traditional public switched telephone network (PSTN) to allow for transparent phone communications worldwide.[1]
VoIP systems employ session control protocols to control the set-up and tear-down of calls as well as audio codecs which encode speech allowing transmission over an IP network as digital audio via an audio stream. Codec use is varied between different implementations of VoIP (and often a range of codecs are used); some implementations rely on narrowband and compressed speech, while others support high fidelity stereo codecs.
History
* 1974 - The Institute of Electrical and Electronic Engineers (IEEE) published a paper entitled "A Protocol for Packet Network Interconnection."[2]
* 1981 - IPv4 is described in RFC-791.[3]
* 1985 - The National Science Foundation commissions the creation of NSFNET.[4]
* 1995 - VocalTec releases the first commercial Internet phone software.[5][6]
* 1996 -
o ITU-T begins the standardization of VoIP initially with the H.323 standard.[7]
o US telecommunication companies ask the US Congress to ban Internet phone technology.[8]
* 1997 - Level 3 began development of its first softswitch (a term they coined in 1998).[9]
* 1999 -
o The Session Initiation Protocol (SIP) specification RFC-2543 was released.[10]
o The first open source SIP PBX (Asterisk) is created by Mark Spencer of Digium.[11]
* 2004 - Commercial VoIP service providers proliferate.[12]
VoIP systems usually interface with the traditional public switched telephone network (PSTN) to allow for transparent phone communications worldwide.[1]
VoIP systems employ session control protocols to control the set-up and tear-down of calls as well as audio codecs which encode speech allowing transmission over an IP network as digital audio via an audio stream. Codec use is varied between different implementations of VoIP (and often a range of codecs are used); some implementations rely on narrowband and compressed speech, while others support high fidelity stereo codecs.
History
* 1974 - The Institute of Electrical and Electronic Engineers (IEEE) published a paper entitled "A Protocol for Packet Network Interconnection."[2]
* 1981 - IPv4 is described in RFC-791.[3]
* 1985 - The National Science Foundation commissions the creation of NSFNET.[4]
* 1995 - VocalTec releases the first commercial Internet phone software.[5][6]
* 1996 -
o ITU-T begins the standardization of VoIP initially with the H.323 standard.[7]
o US telecommunication companies ask the US Congress to ban Internet phone technology.[8]
* 1997 - Level 3 began development of its first softswitch (a term they coined in 1998).[9]
* 1999 -
o The Session Initiation Protocol (SIP) specification RFC-2543 was released.[10]
o The first open source SIP PBX (Asterisk) is created by Mark Spencer of Digium.[11]
* 2004 - Commercial VoIP service providers proliferate.[12]
IBM Websphere MQ Commands
MQ commands
Command name Purpose
amqccert Check certificate chains
amqoamd Output setmqaut commands
amqmdain Configure or control WebSphere MQ services (Windows® systems only)
amqtcert Transfer certificates
crtmqcvx Convert data
crtmqm Create a local queue manager
dltmqm Delete a queue manager
dmpmqaut Dump authorizations to an object
dmpmqlog Dump a log [url]
dspmq Display queue managers
dspmqaut Display authorizations to an object
dspmqcsv Display the status of a command server
dspmqfls Display file names
dspmqrte Display route application
dspmqtrc Display formatted trace output (UNIX® systems only)
dspmqtrn Display details of transactions [pareja de rsvmqtrn]
dspmqver Display version number
endmqcsv Stop the command server on a queue manager
endmqdnm Stop .NET monitor
endmqlsr Stop the listener process on a queue manager
endmqm Stop a local queue manager
endmqtrc Stop tracing for an entity
mqftapp Run the File Transfer Application
mqftrcv Receive file using the File Transfer Application (server)
mqftrcvc Receive file using the File Transfer Application (client)
mqftsnd Send file using the File Transfer Application (server)
mqftsndc Send file using the File Transfer Application (client)
rcdmqimg Write an image of an object to the log
rcrmqobj Recreate an object from their image in the log
rsvmqtrn Commit or back out a transaction [pareja de dspmqtrn]
runmqchi Start a channel initiator process
runmqchl Start a sender or requester channel
runmqdlq Start the dead-letter queue handler
runmqdnm Run .NET monitor
runmqlsr Start a listener process
runmqsc Issue MQSC commands to a queue manager
runmqtmc Invoke a trigger monitor for a client (AIX® clients only)
runmqtrm Invoke a trigger monitor for a server
setmqaut Change authorizations to an object
setmqcrl Set certificate revocation list (CRL) LDAP server definitions (Windows® systems only)
setmqprd Enroll production license
setmqscp Set service connection points (Windows® systems only)
strmqcsv Start the command server for a queue manager
strmqm Start a local queue manager
strmqtrc Enable tracing
Command name Purpose
amqccert Check certificate chains
amqoamd Output setmqaut commands
amqmdain Configure or control WebSphere MQ services (Windows® systems only)
amqtcert Transfer certificates
crtmqcvx Convert data
crtmqm Create a local queue manager
dltmqm Delete a queue manager
dmpmqaut Dump authorizations to an object
dmpmqlog Dump a log [url]
dspmq Display queue managers
dspmqaut Display authorizations to an object
dspmqcsv Display the status of a command server
dspmqfls Display file names
dspmqrte Display route application
dspmqtrc Display formatted trace output (UNIX® systems only)
dspmqtrn Display details of transactions [pareja de rsvmqtrn]
dspmqver Display version number
endmqcsv Stop the command server on a queue manager
endmqdnm Stop .NET monitor
endmqlsr Stop the listener process on a queue manager
endmqm Stop a local queue manager
endmqtrc Stop tracing for an entity
mqftapp Run the File Transfer Application
mqftrcv Receive file using the File Transfer Application (server)
mqftrcvc Receive file using the File Transfer Application (client)
mqftsnd Send file using the File Transfer Application (server)
mqftsndc Send file using the File Transfer Application (client)
rcdmqimg Write an image of an object to the log
rcrmqobj Recreate an object from their image in the log
rsvmqtrn Commit or back out a transaction [pareja de dspmqtrn]
runmqchi Start a channel initiator process
runmqchl Start a sender or requester channel
runmqdlq Start the dead-letter queue handler
runmqdnm Run .NET monitor
runmqlsr Start a listener process
runmqsc Issue MQSC commands to a queue manager
runmqtmc Invoke a trigger monitor for a client (AIX® clients only)
runmqtrm Invoke a trigger monitor for a server
setmqaut Change authorizations to an object
setmqcrl Set certificate revocation list (CRL) LDAP server definitions (Windows® systems only)
setmqprd Enroll production license
setmqscp Set service connection points (Windows® systems only)
strmqcsv Start the command server for a queue manager
strmqm Start a local queue manager
strmqtrc Enable tracing
What is Webpshere MQ?
IBM WebSphere MQ is a family of network communication software products launched by IBM in March 1992. It was previously known as MQSeries, a trademark that IBM rebranded in 2002 to join the suite of WebSphere products. WebSphere MQ is IBM's Message Oriented Middleware offering. It allows independent and potentially non-concurrent applications on a distributed system to communicate with each other. MQ is available on a large number of platforms (both IBM and non-IBM), including z/OS (mainframe), OS/400 (IBM System i or AS/400), Transaction Processing Facility, UNIX (AIX, HP-UX, Solaris), HP NonStop, OpenVMS, Linux, and Microsoft Windows.
Message-oriented middleware
Main article: Message-oriented middleware
A member of the WebSphere family from IBM, WebSphere MQ (formerly MQSeries) is the most popular[1] system for messaging across multiple platforms, including Windows, Linux, IBM mainframe and midrange, and Unix. WebSphere MQ is often referred to as "MQ" or "MQSeries".
There are two parts to message queuing:
* Messages are collections of binary or character (for instance ASCII or EBCDIC) data that have some meaning to a participating program. As in other communications protocols, storage, routing, and delivery information is added to the message before transmission and stripped from the message prior to delivery to the receiving application.
* Message queues are objects that store messages in an application.
A queue Manager, although not strictly required for message-oriented middleware, is a Websphere MQ prerequisite and system service that provides a logical container for the message queue and is responsible for transferring data to other queue managers via message channels.
There are several advantages to this technology:
* Messages do not depend on pure packet-based transmissions, such as TCP/IP. This allows the sending and receiving ends to be decoupled and potentially operate asynchronously.
* Messages will be delivered once and once only, irrespective of errors and network problems.
[edit] APIs
There are many ways to access WebSphere MQ's facilities. Some of the APIs supported by IBM are:
* IBM Message Queue Interface for C, COBOL, PL/I, and Java
* JMS for Java
* Perl interface (developed and contributed by Morgan Stanley), available from CPAN.[2]
* Windows PowerShell[3]
* XMS for C/C++ and .NET[4]
There are many other APIs (unsupported by IBM).
[edit] Awards
In 2004, WebSphere MQ won the British Royal Academy of Engineering's MacRobert Award for technological and engineering innovation.[5]
[edit] Features
WebSphere MQ provides assured one-time delivery of messages across a wide variety of platforms. The product emphasizes reliability and robustness of message traffic, and ensures that a message should never be lost if MQ is appropriately configured.
It needs to be remembered that a message in the context of MQ has no implication other than a gathering of data. MQ is very generalized and can be used as a robust substitute for many forms of intercommunication. For example, it can be used to implement reliable delivery of large files as a substitute for FTP.
MQ provides application designers a mechanism to achieve non-time-dependent architecture. Messages can be sent from one application to another, regardless of whether the applications are running at the same time. If a message receiver application is not running when a sender sends it a message, the queue manager will hold the message until the receiver asks for it. Ordering of all messages is preserved, by default this is in FIFO order of receipt at the local queue within priority of the message.
It provides a means for transforming data between different architectures and protocols, such as Big Endian to Little Endian, or EBCDIC to ASCII. This is accomplished through the use of message data "exits". Exits are compiled applications which run on the queue manager host, and are executed by the WebSphere MQ software at the time data transformation is needed.
WebSphere MQ allows receipt of messages to "trigger" other applications to run, and thus provides the framework for a message driven architecture.
It implements the JMS standard API, and also has its own proprietary API, known as the Message Queuing Interface.
Unlike email, MQ itself is responsible for determining the destination of messages by the definition of queues, so processing of sent messages can be moved to a different application at a different destination. MQ provides a robust routing architecture, allowing messages to be routed via alternative paths around a network of MQ managers. MQ can be implemented as a cluster, where multiple MQ implementations share the processing of messages to allow higher performance and load balancing.
Posted by karthick at 8:29 PM 0 comments
Labels: IBM Websphere MQ
Websphere MQ Clustering
Clustering Up
Main purpose : workload balancing.
* SC34-6061 : Queue Manager Clusters. [MQ-Clustering.pdf]
* SC34-6061 : Queue Manager Clusters. Online url (v 5.3)
* SC34-6589 : Queue Manager Clusters. url (v 6.0) [T42:\mq\books\]
Distributed queing is when you group queue managers in a cluster : the queue managers can make the queues that they host available to every other queue manager in the cluster. Any queue manager can send a message to any other queue manager in the same cluster without explicit channel definitions, remote-queue definitions, or transmission queues for each destination. Every queue manager in a cluster has a single transmission queue from which it can transmit messages to any other queue manager in the cluster.
Each queue manager in a cluster needs to define only:
* one cluster-receiver channel on which to receive messages
* one cluster-sender channel with which it introduces itself and learns about the cluster
* which own queues it wants to make available to the cluster
As with distributed queuing, an application uses the MQPUT() call to put a message on a cluster queue at any queue manager. An application uses the MQGET() call to retrieve messages from a cluster queue on the local queue manager.
You can only GET from a local cluster queue, but you can PUT to any queue in a cluster. If you open a queue to use the MQGET command, the queue manager will only use the local queue.
Each queue manager has a definition for the receiving end of a channel called TO.qmgr on which it can receive messages. This is a cluster-receiver channel. A cluster-receiver channel is similar to a receiver channel used in distributed queuing, but in addition to carrying messages this channel can also carry information about the cluster.
Each queue manager also has a definition for the sending end of a channel, which connects to the cluster-receiver channel of one of the Full Repository (FR) queue managers. This is a cluster-sender channel. A cluster-sender channel is similar to a sender channel used in distributed queuing, but in addition to carrying messages this channel can also carry information about the cluster.
Once both the cluster-receiver end and the cluster-sender end of a channel have been defined, the channel starts automatically.
In any cluster you need to nominate two queue managers to hold full repositories.
The clusters use the publish/subscribe model for internal messaging (and will Subscribe to only 2 FR)
Queue Manager Repository is kept in SYSTEM.CLUSTER.REPOSITORY.QUEUE queue
Cluster information is carried to repositories (whether full or partial) on a local queue called SYSTEM.CLUSTER.COMMAND.QUEUE.
Few Q&A ;
* how many FR ? 2
* DISCINT=0 ? no
* 2 qmgrs just to be FR ? yes, on a separate server
Good intro : Getting started with queue manager clusters.
Interesting summary :
#1 Regardless of how many FRs you have, each FR should have a manual CLUSSNDR defined to every other FR.
#2 If every FR has a CLUSSNDR to every other FR, each FR will know about every cluster attribute on every QM in the cluster.
#3 A PR will only ever publish info to 2 FRs. A PR will only ever subscribe to 2 FRs. Period. It doesn't matter how many manual CLUSSNDRs you define on that PR. A PR will only ever send its info (publish) to 2 FRs and will only get updates (subscribe) from 2 FRs.
#4 You should only define one CLUSSNDR to one FR from a PR.
#5 If 2 FRs go down in your cluster, your cluster will be able to send messages just fine. But any changes to cluster definitions become a problem. Any PRs that used both of these down FRs will still function for messaging, but they will not be made aware of any changes in the cluster because both of it's FRs are N/A.
#6 If two of your FRs are down, and you still have other FRs, you could go to your PRs and delete the CLUSSNDR to the down FR, define a CLUSSNDR to an available FR and issue REFRESH CLUSTER(*) REPOS(YES). This would cause your PR to register with an available FR and thus pick up cluster changes.
#7 In a properly designed system the liklihood of 2 FRs being down is next to zero, so the need for more than 2 FRs is next to zero. And even if both FRs are down it doesn't mean your cluster will come to a screeching halt.
Just use 2 FRs.
Problem : stuck message(s) @ Xmit Q(s)!
Message-oriented middleware
Main article: Message-oriented middleware
A member of the WebSphere family from IBM, WebSphere MQ (formerly MQSeries) is the most popular[1] system for messaging across multiple platforms, including Windows, Linux, IBM mainframe and midrange, and Unix. WebSphere MQ is often referred to as "MQ" or "MQSeries".
There are two parts to message queuing:
* Messages are collections of binary or character (for instance ASCII or EBCDIC) data that have some meaning to a participating program. As in other communications protocols, storage, routing, and delivery information is added to the message before transmission and stripped from the message prior to delivery to the receiving application.
* Message queues are objects that store messages in an application.
A queue Manager, although not strictly required for message-oriented middleware, is a Websphere MQ prerequisite and system service that provides a logical container for the message queue and is responsible for transferring data to other queue managers via message channels.
There are several advantages to this technology:
* Messages do not depend on pure packet-based transmissions, such as TCP/IP. This allows the sending and receiving ends to be decoupled and potentially operate asynchronously.
* Messages will be delivered once and once only, irrespective of errors and network problems.
[edit] APIs
There are many ways to access WebSphere MQ's facilities. Some of the APIs supported by IBM are:
* IBM Message Queue Interface for C, COBOL, PL/I, and Java
* JMS for Java
* Perl interface (developed and contributed by Morgan Stanley), available from CPAN.[2]
* Windows PowerShell[3]
* XMS for C/C++ and .NET[4]
There are many other APIs (unsupported by IBM).
[edit] Awards
In 2004, WebSphere MQ won the British Royal Academy of Engineering's MacRobert Award for technological and engineering innovation.[5]
[edit] Features
WebSphere MQ provides assured one-time delivery of messages across a wide variety of platforms. The product emphasizes reliability and robustness of message traffic, and ensures that a message should never be lost if MQ is appropriately configured.
It needs to be remembered that a message in the context of MQ has no implication other than a gathering of data. MQ is very generalized and can be used as a robust substitute for many forms of intercommunication. For example, it can be used to implement reliable delivery of large files as a substitute for FTP.
MQ provides application designers a mechanism to achieve non-time-dependent architecture. Messages can be sent from one application to another, regardless of whether the applications are running at the same time. If a message receiver application is not running when a sender sends it a message, the queue manager will hold the message until the receiver asks for it. Ordering of all messages is preserved, by default this is in FIFO order of receipt at the local queue within priority of the message.
It provides a means for transforming data between different architectures and protocols, such as Big Endian to Little Endian, or EBCDIC to ASCII. This is accomplished through the use of message data "exits". Exits are compiled applications which run on the queue manager host, and are executed by the WebSphere MQ software at the time data transformation is needed.
WebSphere MQ allows receipt of messages to "trigger" other applications to run, and thus provides the framework for a message driven architecture.
It implements the JMS standard API, and also has its own proprietary API, known as the Message Queuing Interface.
Unlike email, MQ itself is responsible for determining the destination of messages by the definition of queues, so processing of sent messages can be moved to a different application at a different destination. MQ provides a robust routing architecture, allowing messages to be routed via alternative paths around a network of MQ managers. MQ can be implemented as a cluster, where multiple MQ implementations share the processing of messages to allow higher performance and load balancing.
Posted by karthick at 8:29 PM 0 comments
Labels: IBM Websphere MQ
Websphere MQ Clustering
Clustering Up
Main purpose : workload balancing.
* SC34-6061 : Queue Manager Clusters. [MQ-Clustering.pdf]
* SC34-6061 : Queue Manager Clusters. Online url (v 5.3)
* SC34-6589 : Queue Manager Clusters. url (v 6.0) [T42:\mq\books\]
Distributed queing is when you group queue managers in a cluster : the queue managers can make the queues that they host available to every other queue manager in the cluster. Any queue manager can send a message to any other queue manager in the same cluster without explicit channel definitions, remote-queue definitions, or transmission queues for each destination. Every queue manager in a cluster has a single transmission queue from which it can transmit messages to any other queue manager in the cluster.
Each queue manager in a cluster needs to define only:
* one cluster-receiver channel on which to receive messages
* one cluster-sender channel with which it introduces itself and learns about the cluster
* which own queues it wants to make available to the cluster
As with distributed queuing, an application uses the MQPUT() call to put a message on a cluster queue at any queue manager. An application uses the MQGET() call to retrieve messages from a cluster queue on the local queue manager.
You can only GET from a local cluster queue, but you can PUT to any queue in a cluster. If you open a queue to use the MQGET command, the queue manager will only use the local queue.
Each queue manager has a definition for the receiving end of a channel called TO.qmgr on which it can receive messages. This is a cluster-receiver channel. A cluster-receiver channel is similar to a receiver channel used in distributed queuing, but in addition to carrying messages this channel can also carry information about the cluster.
Each queue manager also has a definition for the sending end of a channel, which connects to the cluster-receiver channel of one of the Full Repository (FR) queue managers. This is a cluster-sender channel. A cluster-sender channel is similar to a sender channel used in distributed queuing, but in addition to carrying messages this channel can also carry information about the cluster.
Once both the cluster-receiver end and the cluster-sender end of a channel have been defined, the channel starts automatically.
In any cluster you need to nominate two queue managers to hold full repositories.
The clusters use the publish/subscribe model for internal messaging (and will Subscribe to only 2 FR)
Queue Manager Repository is kept in SYSTEM.CLUSTER.REPOSITORY.QUEUE queue
Cluster information is carried to repositories (whether full or partial) on a local queue called SYSTEM.CLUSTER.COMMAND.QUEUE.
Few Q&A ;
* how many FR ? 2
* DISCINT=0 ? no
* 2 qmgrs just to be FR ? yes, on a separate server
Good intro : Getting started with queue manager clusters.
Interesting summary :
#1 Regardless of how many FRs you have, each FR should have a manual CLUSSNDR defined to every other FR.
#2 If every FR has a CLUSSNDR to every other FR, each FR will know about every cluster attribute on every QM in the cluster.
#3 A PR will only ever publish info to 2 FRs. A PR will only ever subscribe to 2 FRs. Period. It doesn't matter how many manual CLUSSNDRs you define on that PR. A PR will only ever send its info (publish) to 2 FRs and will only get updates (subscribe) from 2 FRs.
#4 You should only define one CLUSSNDR to one FR from a PR.
#5 If 2 FRs go down in your cluster, your cluster will be able to send messages just fine. But any changes to cluster definitions become a problem. Any PRs that used both of these down FRs will still function for messaging, but they will not be made aware of any changes in the cluster because both of it's FRs are N/A.
#6 If two of your FRs are down, and you still have other FRs, you could go to your PRs and delete the CLUSSNDR to the down FR, define a CLUSSNDR to an available FR and issue REFRESH CLUSTER(*) REPOS(YES). This would cause your PR to register with an available FR and thus pick up cluster changes.
#7 In a properly designed system the liklihood of 2 FRs being down is next to zero, so the need for more than 2 FRs is next to zero. And even if both FRs are down it doesn't mean your cluster will come to a screeching halt.
Just use 2 FRs.
Problem : stuck message(s) @ Xmit Q(s)!
Thursday, March 12, 2009
What is Websphere MQ?
IBM WebSphere MQ is a family of network communication software products launched by IBM in March 1992. It was previously known as MQSeries, a trademark that IBM rebranded in 2002 to join the suite of WebSphere products. WebSphere MQ is IBM's Message Oriented Middleware offering. It allows independent and potentially non-concurrent applications on a distributed system to communicate with each other. MQ is available on a large number of platforms (both IBM and non-IBM), including z/OS (mainframe), OS/400 (IBM System i or AS/400), Transaction Processing Facility, UNIX (AIX, HP-UX, Solaris), HP NonStop, OpenVMS, Linux, and Microsoft Windows.
Message-oriented middleware
Main article: Message-oriented middleware
A member of the WebSphere family from IBM, WebSphere MQ (formerly MQSeries) is the most popular[1] system for messaging across multiple platforms, including Windows, Linux, IBM mainframe and midrange, and Unix. WebSphere MQ is often referred to as "MQ" or "MQSeries".
There are two parts to message queuing:
* Messages are collections of binary or character (for instance ASCII or EBCDIC) data that have some meaning to a participating program. As in other communications protocols, storage, routing, and delivery information is added to the message before transmission and stripped from the message prior to delivery to the receiving application.
* Message queues are objects that store messages in an application.
A queue Manager, although not strictly required for message-oriented middleware, is a Websphere MQ prerequisite and system service that provides a logical container for the message queue and is responsible for transferring data to other queue managers via message channels.
There are several advantages to this technology:
* Messages do not depend on pure packet-based transmissions, such as TCP/IP. This allows the sending and receiving ends to be decoupled and potentially operate asynchronously.
* Messages will be delivered once and once only, irrespective of errors and network problems.
[edit] APIs
There are many ways to access WebSphere MQ's facilities. Some of the APIs supported by IBM are:
* IBM Message Queue Interface for C, COBOL, PL/I, and Java
* JMS for Java
* Perl interface (developed and contributed by Morgan Stanley), available from CPAN.[2]
* Windows PowerShell[3]
* XMS for C/C++ and .NET[4]
There are many other APIs (unsupported by IBM).
[edit] Awards
In 2004, WebSphere MQ won the British Royal Academy of Engineering's MacRobert Award for technological and engineering innovation.[5]
[edit] Features
WebSphere MQ provides assured one-time delivery of messages across a wide variety of platforms. The product emphasizes reliability and robustness of message traffic, and ensures that a message should never be lost if MQ is appropriately configured.
It needs to be remembered that a message in the context of MQ has no implication other than a gathering of data. MQ is very generalized and can be used as a robust substitute for many forms of intercommunication. For example, it can be used to implement reliable delivery of large files as a substitute for FTP.
MQ provides application designers a mechanism to achieve non-time-dependent architecture. Messages can be sent from one application to another, regardless of whether the applications are running at the same time. If a message receiver application is not running when a sender sends it a message, the queue manager will hold the message until the receiver asks for it. Ordering of all messages is preserved, by default this is in FIFO order of receipt at the local queue within priority of the message.
It provides a means for transforming data between different architectures and protocols, such as Big Endian to Little Endian, or EBCDIC to ASCII. This is accomplished through the use of message data "exits". Exits are compiled applications which run on the queue manager host, and are executed by the WebSphere MQ software at the time data transformation is needed.
WebSphere MQ allows receipt of messages to "trigger" other applications to run, and thus provides the framework for a message driven architecture.
It implements the JMS standard API, and also has its own proprietary API, known as the Message Queuing Interface.
Unlike email, MQ itself is responsible for determining the destination of messages by the definition of queues, so processing of sent messages can be moved to a different application at a different destination. MQ provides a robust routing architecture, allowing messages to be routed via alternative paths around a network of MQ managers. MQ can be implemented as a cluster, where multiple MQ implementations share the processing of messages to allow higher performance and load balancing.
Message-oriented middleware
Main article: Message-oriented middleware
A member of the WebSphere family from IBM, WebSphere MQ (formerly MQSeries) is the most popular[1] system for messaging across multiple platforms, including Windows, Linux, IBM mainframe and midrange, and Unix. WebSphere MQ is often referred to as "MQ" or "MQSeries".
There are two parts to message queuing:
* Messages are collections of binary or character (for instance ASCII or EBCDIC) data that have some meaning to a participating program. As in other communications protocols, storage, routing, and delivery information is added to the message before transmission and stripped from the message prior to delivery to the receiving application.
* Message queues are objects that store messages in an application.
A queue Manager, although not strictly required for message-oriented middleware, is a Websphere MQ prerequisite and system service that provides a logical container for the message queue and is responsible for transferring data to other queue managers via message channels.
There are several advantages to this technology:
* Messages do not depend on pure packet-based transmissions, such as TCP/IP. This allows the sending and receiving ends to be decoupled and potentially operate asynchronously.
* Messages will be delivered once and once only, irrespective of errors and network problems.
[edit] APIs
There are many ways to access WebSphere MQ's facilities. Some of the APIs supported by IBM are:
* IBM Message Queue Interface for C, COBOL, PL/I, and Java
* JMS for Java
* Perl interface (developed and contributed by Morgan Stanley), available from CPAN.[2]
* Windows PowerShell[3]
* XMS for C/C++ and .NET[4]
There are many other APIs (unsupported by IBM).
[edit] Awards
In 2004, WebSphere MQ won the British Royal Academy of Engineering's MacRobert Award for technological and engineering innovation.[5]
[edit] Features
WebSphere MQ provides assured one-time delivery of messages across a wide variety of platforms. The product emphasizes reliability and robustness of message traffic, and ensures that a message should never be lost if MQ is appropriately configured.
It needs to be remembered that a message in the context of MQ has no implication other than a gathering of data. MQ is very generalized and can be used as a robust substitute for many forms of intercommunication. For example, it can be used to implement reliable delivery of large files as a substitute for FTP.
MQ provides application designers a mechanism to achieve non-time-dependent architecture. Messages can be sent from one application to another, regardless of whether the applications are running at the same time. If a message receiver application is not running when a sender sends it a message, the queue manager will hold the message until the receiver asks for it. Ordering of all messages is preserved, by default this is in FIFO order of receipt at the local queue within priority of the message.
It provides a means for transforming data between different architectures and protocols, such as Big Endian to Little Endian, or EBCDIC to ASCII. This is accomplished through the use of message data "exits". Exits are compiled applications which run on the queue manager host, and are executed by the WebSphere MQ software at the time data transformation is needed.
WebSphere MQ allows receipt of messages to "trigger" other applications to run, and thus provides the framework for a message driven architecture.
It implements the JMS standard API, and also has its own proprietary API, known as the Message Queuing Interface.
Unlike email, MQ itself is responsible for determining the destination of messages by the definition of queues, so processing of sent messages can be moved to a different application at a different destination. MQ provides a robust routing architecture, allowing messages to be routed via alternative paths around a network of MQ managers. MQ can be implemented as a cluster, where multiple MQ implementations share the processing of messages to allow higher performance and load balancing.
Tuesday, March 10, 2009
Saturday, March 7, 2009
Tuesday, March 3, 2009
Subscribe to:
Posts (Atom)
