A WebLogic Server cluster consists of multiple WebLogic 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.

A cluster is part of a particular WebLogic Server domain that is a 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. A domain also contains the application components deployed in the domain, and the resources and services required by those application components and the server instances in the domain. You can use a variety of criteria for organizing WebLogic Server instances into domains.

In each domain, one WebLogic Server instance acts as the Administration Server—the server instance which configures, manages, and monitors all other server instances and resources in the domain. Each Administration Server manages one domain only. If a domain contains multiple clusters, each cluster in the domain has the same Administration Server.

Clustered WebLogic Server instances behave similarly to non-clustered instances, except that they provide failover and load balancing. The process and tools used to configure clustered WebLogic Server instances are the same as those used to configure non-clustered instances.

The choice to cluster WebLogic Server instances is transparent to application developers and clients. However, understanding the technical infrastructure that enables clustering will help programmers and administrators maximize the scalability and availability of their applications.

A WebLogic Server cluster provides benefits such as:

Scalability: 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.

High-Availability: 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.

Web applications can consist of different types of objects, including Enterprise Java Beans (EJBs), servlets, and Java Server Pages (JSPs). Each object type has a unique set of behaviors related to control, invocation, and how it functions within an application. For this reason, the methods that WebLogic Server uses to support clustering—and hence to provide load balancing and failover—can vary for different types of objects.

WebLogic Server can cluster the objects as Servlets, JSPs, EJBs, Remote Method Invocation (RMI) objects, Java Messaging Service (JMS) destinations and Java Database Connectivity (JDBC) connections.

WebLogic Server cannot cluster objects such as File services, Time services, WebLogic Events and Workspaces.

Job oriented Weblogic Server Training in Ameerpet, Hyderabad please visit http://www.revanthtechnologies.com

The plug-and-play environment of WebLogic Server makes it an ideal choice for integration with your product. To distribute WebLogic Server, you must obtain and install a special license called an ISV license. (You do not need an ISV license to develop your application or to configure WebLogic Server.) Installing an ISV license for a WebLogic Server modifies the server and inextricably links files. Your distribution must include these modified WebLogic Server files.

To set up a WebLogic Server that you can distribute, complete the following tasks:

Enroll in the BEA Star Partner Program:

The WebLogic Server package available from BEA normally includes a license that prohibits the buyer from redistributing the software. However, for partners—Independent Software Vendors (ISVs) in the business of redistributing WebLogic Server—BEA provides a mechanism for creating a redistribution license. Although the purpose of all ISV redistribution licenses is the same (to give an ISV’s customers the right to run the WebLogic Server software that has been redistributed by the ISV), each ISV redistribution license is unique, linked specifically to a particular partner.

If you intend to redistribute WebLogic Server, you need to sign a BEA standard Channel License Agreement (CLA), available from your BEA partner account representative.

Install the Partner Development Kit:

After you enroll in the program, BEA ships a CD collection of all major BEA products. When the Partner Development Kit arrives, install the software from the CDs.you can download BEA software from the BEA Systems Download Center,

Install the ISV License:

After verifying your eligibility for the Star Partner Program, BEA sends an email that includes your customized ISV license in an attached file named isv.jar. This section describes how to install the ISV license file for WebLogic Server version 7.0 only.

The ISV redistribution licenses that you create and distribute enable your customers to use WebLogic Server functionality as follows:

* The specific set of BEA components to which your customers can have access—for example, WebLogic Server—is specified in your license distribution agreement with BEA and is enforced by the ISV redistribution license. This mechanism ensures that run-time support is restricted to the BEA components specified in that agreement.

* If your license distribution agreement is for WebLogic Server only, the ISV redistribution license prevents the run-time use of BEA products that are not included with WebLogic Server, such as WebLogic Portal.

* There is no enforced limit on the number of IP or database connections that can be made by an installation of the WebLogic Server software distributed by the ISV.

* There is no expiration date on the use of the BEA software distributed by the ISV.

* The ISV redistribution license is not tied to any specific IP address. Therefore, the BEA software that you distribute with an ISV redistribution license can be used on any machine.

Distribute Files:

When you are ready to distribute WebLogic Server with your application, you must make sure that your installer includes the BEA license file (BEA_HOME\license.bea) and the WL_HOME\lib\weblogic.jar file.

Job oriented Weblogic Server Training in Ameerpet, Hyderabad please visit http://www.revanthtechnologies.com

WebLogic Server provides several ways to start and stop server instances. The method that you choose depends on whether you prefer using the Administration Console or a command-line interface, and on whether you are using Node Manager to manage the server’s life cycle. The server instance runs within the JVM, and the JVM can host only one server instance.

An Administration Server is a WebLogic Server instance that maintains configuration data for a domain. In a development environment, it is usually sufficient to start an Administration Server and deploy your applications directly onto the Administration Server. In a production environment, you create Managed Servers to run applications.

Depending on the method you choose to manage server start up and what setup tasks you need to complete the following procedures before you can start server instances:

* Meet version requirements for a Domain
* Create a domain for Your Administrative Tasks to Oracle WebLogic Server
* Provide user credentials to Start and Stop Servers
* Set up Node Manager Configuration
* Configure Managed Server connections to the Administration Server
* Specify Java start up options for a WebLogic Server Instance

If you use a Configuration Wizard template that is provided by WebLogic Server, your domain directory includes a start script named start WebLogic. If you use a domain template from another source, the wizard might not create a start script, or it might create a script with a different name. The template designer determines whether the wizard creates a start script and the name of the script.

There are two type of WebLogic Server instance in a domain, Administration Server and Managed Server.

–You can start Managed Server without Administration Server with exception for first time. If you are starting Managed Server for first time, then Administration Server should be Up. Managed Server can cache config files locally(in its local config directory) and later Managed Server can start on its own.

-To start Managed Server using script, supply Admin Server protocol, Server Name and Listen Port(check start up command for more information).

– If start up mode of domain is “production” then start up will prompt you for username & password to start services.

- If you create domain and start up mode is “development” then start up will not prompt for username/password as username password are stored in boot identity file in security directory of Domain at BEA_HOME / user projects / domains / <domain Name> / servers/ <server Name>/ security / boot. properties

A boot identity file is a text file that contains user credentials for starting and stopping an instance of WebLogic Server.

To start and stop a WebLogic Server instance, you must provide the credentials of a user who is permitted to start and stop servers for the domain.

Job oriented Weblogic Server Training in Ameerpet, Hyderabad please visit http://www.revanthtechnologies.com

WebLogic Server System administration includes a wide range of tasks like creating WebLogic Server domains; deploying applications; migrating domains from development environments to production environments; monitoring and managing the performance of the run-time system; and diagnosing and troubleshooting problems.

The WebLogic Server management system is based on Java EE and other standards, it integrates with systems that are frequently used to manage other software and hardware components.

WebLogic Server system administration tools allow you to install, configure, monitor, and manage one or more WebLogic Server installations. You also use the tools to manage and monitor the applications hosted on WebLogic Server. Many system administration tasks are associated with a WebLogic Server, they are grouped into the following categories:

* Creation of WebLogic domains and their associated WebLogic Servers.

* The management of the WebLogic domains and their associated hosted Web or Enterprise Java (J2EE) applications.

* The management and monitoring of WebLogic Server instances that constitute a WebLogic domain.

* The management of the resources and J2EE services that the domains and deployed applications utilize.

* WebLogic domain security.

There are three very important administration tools for the entire spectrum of administration tasks to perform with respect to the WebLogic Server are:

WebLogic Administration Console,
Weblogic.Admin command-line utility, and
Domain Configuration Wizard.

WebLogic Administration Console:

The Administration Console is the recommended tool for performing all system administration tasks related to the WebLogic Server. This Administration Console provides an intuitive Web browser-based interface to a multitude of system administration tasks related to a WebLogic domain and its associated WebLogic Servers and applications. The Administration Console exists as a JSP-based application that is hosted by an Administration Server assigned to a specific WebLogic domain.

The Administration Console can be used to manage only that active domain. If you need to manage multiple WebLogic Domains, you need to open separate instances of the Administration Console, with each console connecting to a different Administration Server managing a specific WebLogic domain. Through the Administration Console, you have full administrative control of an entire WebLogic domain and the associated WebLogic Servers.

Weblogic.Admin Command-Line Utility

The weblogic.Admin command-line utility provides a suite of useful functions that can be used toward the system administration of a WebLogic Server domain. It is an alternative to using the Administration Console, especially if you prefer to use the command line as opposed to a Web browser interface, or the Web browser is just not available. The weblogic.Admin utility comes with several useful functions for managing the WebLogic Servers in a domain.

However, to achieve the administration capabilities provided by the Administration Console, you need to understand the internal administration infrastructure of the WebLogic Server

Before you select the weblogic.Admin utility as your primary administration tool, the machine from which you use the weblogic.Admin utility must have the WebLogic Server software installed to be able to execute the weblogic.Admin class.

Domain Configuration Wizard is a Java client program for creating and configuring WebLogic Server domains based on predefined domain templates.

Job oriented Weblogic Server Training in Ameerpet, Hyderabad please visit http://www.revanthtechnologies.com

BEA System’s WebLogic is a server software application that runs on a middle tier, between back-end databases and related applications and browser-based thin clients. WebLogic is a leading e-commerce online transaction processing (OLTP) platform, developed to connect users in a distributed computing environment and to facilitate the integration of mainframe applications with distributed corporate data and applications.

WebLogic server is based on Java 2 Platform, Enterprise Edition (J2EE), the standard platform used to create Java based multi-tier enterprise applications. J2EE platform technologies were developed through the efforts of BEA Systems and other vendors in collaboration with the main developer, Sun Microsystems. Because J2EE applications are standardized modules, WebLogic can automate many system level tasks that would otherwise have demanded programming time. Oracle acquired BEA in 2008, following which it became Oracle WebLogic.

The main features of WebLogic server include connectors that make it possible for any legacy application on any client to interoperate with server applications, Enterprise JavaBean (EJB) components, resource pooling, and connection sharing that make applications very scalable. An administration console with a user interface makes management tasks more efficient and features such as Secure Sockets Layer (SSL) support for the encryption of data transmissions, as well as authentication and authorization mechanisms, make applications and transactions secure.

It gives you many built-in capabilities, which makes it much easier to integrate your application into existing infrastructure and reduce your “Time2Market”.  For example, JMS (messaging), tools to communicate to Microsoft clients (COM/DCOM), CORBA support, database drivers and connection pooling, JNDI (Naming & Directory), built in security. Clustering (to handle mission critical high-availability applications).  EJB container and transactional support. Support for wireless applications,  solutions for large e-commerce deployments.

The most important thing is Weblogic is a well tested solution, favorite among ISVs, ASPs, and SIs (Independent Software Vendors, Application Service Providers, & System Integrators).

For Weblogic Server Administration Online training please log on to http://www.revanthtechnologies.com