Files Contained Only in Sun SDK; Not Supported by BEA JRockit
Component | ||
|---|---|---|
Saturday, 6 November 2010
Differences Between BEA JRockit SDK and Sun HotSpot SDK
BEA JRockit SDK is very similar to the Sun JDK, except that it includes a new JRE with the BEA JRockit JVM and some changes to the Java class libraries (however, all of the class libraries have the same behavior in BEA JRockit as in the Sun JDK).
Oracle JRockit & JDK Release Numbering Scheme
Oracle JRockit JVM
The Oracle JRockit JVM is the industry's highest performing Java Virtual Machine now built into Oracle Fusion Middleware. It brings industry leading real time infrastructure capabilities with JRockit Real Time and unparallelled JVM diagnostics with JRockit Mission Control.
What Is the JRockit JVM?
The JRockit JVM is a high-performance JVM developed to ensure reliability, scalability, manageability, and flexibility for Java applications. The JRockit JVM provides improved performance for Java applications deployed on Intel 32-bit (Xeon) and 64-bit (Xeon and SPARC) architectures at significantly lower costs to the enterprise. Further, it is the only enterprise-class JVM optimized for Intel architectures, providing seamless interoperability across multiple hardware and operating system configurations. The JRockit JVM enables your Java applications to run optimally on Windows and Linux operating systems (both 32-bit and 64-bit architectures). The JRockit JVM is especially well-suited for running Oracle WebLogic Server.About the Oracle JRockit JDK
JROCKIT PRODUCTS
- Oracle JRockit Real Time
- Oracle WebLogic Real Time
- Oracle JRockit Mission Control
Oracle JRockit Mission Control
Oracle JRockit Real Time also includes Oracle JRockit Mission Control.
The JRockit Mission Control tools suite includes tools to monitor, manage, profile, and eliminate memory leaks in your Java application without introducing the performance overhead normally associated with tools of this type.
Oracle WebLogic Real Time
Oracle WebLogic Real Time is the version of Oracle JRockit Real Time offered exclusively with Oracle WebLogic Suite. It is targeted specifically toward Java Platform, Enterprise Edition applications demanding predictable latency performance on the order of milliseconds.
JRockit JDK Release Numbering Scheme
Every JRockit JVM release comes with several Java versions. For example, JRockit JVM R28.0 comes with Java SE versions 5.0 and 6. A Java version can be compatible with multiple JRockit JVM releases.
The JRockit JDK release number consists of the following elements:
- The JRockit JVM release number (Rnn.nn.nn)
- The Java version (J2SE 5.0 or Java SE 6)
Oracle JRockit JDK 6 R28.0.0 indicates the 28.0.0 release of JRockit JVM used with Java SE 6; similarly, Oracle JRockit JDK 5.0 R28.0.0 indicates the 28.0.0 release of the JRockit JVM used with J2SE 5.0.
The following is an example of a complete release number:
R28.0.0-637-126675-1.6.0_17-20100111-2121-windows-ia32
In this example,
R28.0.0 is the JRockit JVM release, 1.6.0_01 is the Java version, and windows-ia32 is the platform on which the release runs.Download Link for Jrockit - http://www.oracle.com/technetwork/middleware/jrockit/downloads/index.html
Monday, 1 November 2010
Weblogic Server Installation Console mode
Here are the screenshot of weblogic server installation on console mode
Tag : weblogic server installation on linux, weblogic installation, weblogic server installation on console mode, weblogic server installation screenshot, install weblogic server on linux, install weblogic server on console mode
Weblogic Server Clustering
Weblogic Server Clustering
A WebLogic Server cluster consists of multiple WebLogic Server server instances running simultaneously and working together to provide increased scalability and reliability.
A cluster appears to clients to be a single WebLogic Server instance.
The server instances that constitute a cluster can run on the same machine, or be located on different machines.
You can increase a cluster’s capacity by adding additional server instances to the cluster on an existing machine, or you can add machines to the cluster to host the incremental server instances.
Each server instance in a cluster must run the same version of WebLogic Server.
How Does a Cluster Relate to a Domain?
A cluster is part of a particular WebLogic Server domain.
A domain is an interrelated set of WebLogic Server resources that are managed as a unit.
A domain includes one or more WebLogic Server instances, which can be clustered, non-clustered, or a combination of clustered and non-clustered instances.
A domain can include multiple clusters.
Benefits of Clustering?
The capacity of an application deployed on a WebLogic Server cluster can be increased dynamically to meet demand. You can add server instances to a cluster without interruption of service—the application continues to run without impact to clients and end users.
In a WebLogic Server cluster, application processing can continue when a server instance fails. You “cluster” application components by deploying them on multiple server instances in the cluster—so, if a server instance on which a component is running fails, another server instance on which that component is deployed can continue application processing.
WebLogic Server Communication In a Cluster
WebLogic Server instances in a cluster communicate with one another using two basic network technologies:
IP sockets, which are the conduits for peer-to-peer communication between clustered server instances.
IP unicast or multicast, which server instances use to broadcast availability of services and heartbeats that indicate continued availability.
Note :
When creating a new cluster, it is recommended that you use unicast for messaging within a cluster. For backward compatibility with previous versions, WebLogic Server you must use multicast for communications between clusters.
Key Capabilities of a Cluster
The following sections define, in non-technical terms, the key clustering capabilities that enable scalability and high availability.
Application Failover
Simply put, failover means that when an application component (typically referred to as an "object" in the following sections) doing a particular "job"—some set of processing tasks—becomes unavailable for any reason, a copy of the failed object finishes the job.
For the new object to be able to take over for the failed object:
Simply put, failover means that when an application component (typically referred to as an "object" in the following sections) doing a particular "job"—some set of processing tasks—becomes unavailable for any reason, a copy of the failed object finishes the job.
For the new object to be able to take over for the failed object:
- There must be a copy of the failed object available to take over the job.
- There must be information, available to other objects and the program that manages failover, defining the location and operational status of all objects—so that it can be determined that the first object failed before finishing its job.
- There must be information, available to other objects and the program that manages failover, about the progress of jobs in process—so that an object taking over an interrupted job knows how much of the job was completed before the first object failed, for example, what data has been changed, and what steps in the process were completed.
WebLogic Server uses standards-based communication techniques and facilities— including IP sockets and the Java Naming and Directory Interface (JNDI)—to share and maintain information about the availability of objects in a cluster. These techniques allow WebLogic Server to determine that an object stopped before finishing its job, and where there is a copy of the object to complete the job that was interrupted.
Information about what has been done on a job is called state.
Migration
WebLogic Server supports automatic and manual migration of a clustered server instance from one machine to another. A Managed Server that can be migrated is referred to as a migratable server. This feature is designed for environments with requirements for high availability. The server migration capability is useful for:
- Ensuring uninterrupted availability of singleton services—services that must run on only a single server instance at any given time, such as JMS and the JTA transaction recovery system, when the hosting server instance fails. A Managed Server configured for automatic migration will be automatically migrated to another machine in the event of failure.
- Easing the process of relocating a Managed Server, and all the services it hosts, as part of a planned system administration process. An administrator can initiate the migration of a Managed Server from the Administration Console or command line.
Load Balancing
Load balancing is the even distribution of jobs and associated communications across the computing and networking resources in your environment. For load balancing to occur:
- There must be multiple copies of an object that can do a particular job.
- Information about the location and operational status of all objects must be available.
WebLogic Server allows objects to be clustered—deployed on multiple server instances—so that there are alternative objects to do the same job. WebLogic Server shares and maintains the availability and location of deployed objects using unicast, IP sockets, and JNDI.Reference :
Subscribe to:
Posts (Atom)