Posts
I was getting some weird error (only in) weblogic when I try to load home page(applet) of web application. Home page was nothing but index.jsp which uses tag to load an applet. This applet needs a lot of libraries as part of archive values.
<jsp:plugin type="applet" name="CDApplet" code="com.cd.applet.Applet.class" codebase="." width="100" height="100" align="middle" jreversion="1.5">
<jsp:param name="id" value="CDApplet"/>
<jsp:param name="code" value="com.cd.applet.Applet"/>
<jsp:param name="codebase" value="."/>
<jsp:param name="archive" value="crimson.jar,commons-lang-2.3.jar,jdom.jar,jfreechart-0.9.16.jar,picocontainer-1.0-beta-5.jar,commons-collections-3.2.jar,jaxen-core.jar,saxpath.jar,jaxen-jdom.jar" />
</jsp:plugin>
The above code was NOT working as you see the archive values are sent as parameter. This seems to be okay with Tomcat but somehow weblogic 10.3 could not recognize that. It was throwing Applet Class Not Found Exception. It was really freaking me out. Then I tried this, instead of passing as an argument, I set archive values as part of the tag itself. Example given below:
<jsp:plugin type="applet" name="CDApplet" code="com.cd.applet.Applet.class" codebase="." width="100" height="100" align="middle" jreversion="1.5" archive="cd-applet.jar, commons-collections-3.2.jar,jaxen-core.jar,saxpath.jar,jaxen-jdom.jar">
<jsp:param name="id" value="CDApplet"/>
<jsp:param name="code" value="com.cd.applet.Applet"/>
<jsp:param name="codebase" value="."/>
</jsp:plugin>
This worked. What a relief! By the way, this code change worked in Tomcat as well.
Adios.
Xdoclet on Maven2 NOT generating Struts Config XML
I have recently involved in a migrating existing projects from maven1.2 to maven2. We used maven-xdoclet-plugin for generating struts config xml file. This plug-in used to work OK in maven1.x but failed in maven2. It was not generating those actions & forms properly in struts config xml file.
I recently found a fix (thanks to Google) for this (and it is working) in the form of maven antrun plug-in.
For more info or to see the actual code snippet, please do visit this blog
I recently found a fix (thanks to Google) for this (and it is working) in the form of maven antrun plug-in.
For more info or to see the actual code snippet, please do visit this blog
Difference between DEV and PROD mode in Weblogic 10.3
Development mode:
The default JDK for development domain is Sun Hotspot
You can use the demo certificates for SSL
Auto deployment is enabled
Server instances rotate their log files on startup
Admin Server uses an automatically created boot.properties during startup
The default maximum capacity for JDBC Datasource is 15
The debugFlag which is used to start the WebLogic Workshop Debugger is enabled
Production mode:
The default JDK for production domain is JRockit
If you use the demo certificates for SSL a warning is displayed
Auto deployment is disabled
Server instances rotate their log files when it reaches 5MB
Admin Server prompts for username and password during startup
The default maximum capacity for JDBC Datasource is 25
The debugFlag which is used to start the WebLogic Workshop Debugger is disabled.
If you would like to know how to change to weblogic start up mode from DEV to PROD or vice versa. please visit this entry.
The default JDK for development domain is Sun Hotspot
You can use the demo certificates for SSL
Auto deployment is enabled
Server instances rotate their log files on startup
Admin Server uses an automatically created boot.properties during startup
The default maximum capacity for JDBC Datasource is 15
The debugFlag which is used to start the WebLogic Workshop Debugger is enabled
Production mode:
The default JDK for production domain is JRockit
If you use the demo certificates for SSL a warning is displayed
Auto deployment is disabled
Server instances rotate their log files when it reaches 5MB
Admin Server prompts for username and password during startup
The default maximum capacity for JDBC Datasource is 25
The debugFlag which is used to start the WebLogic Workshop Debugger is disabled.
If you would like to know how to change to weblogic start up mode from DEV to PROD or vice versa. please visit this entry.
Weblogic Clustering Advantages
WebLogic clustering offers three important benefits:
1. 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.
2. Load balancing:
The ability to distribute requests across all members of the cluster, according tothe workload on each server.
3. High availability:
A mix of features that ensure applications and services are available even if aserver or machine fails. Clients can continue to work with little or no disruption ina highly available environment. WebLogic achieves high availability using acombination of features: replication, failover, and migratable services.
1. 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.
2. Load balancing:
The ability to distribute requests across all members of the cluster, according tothe workload on each server.
3. High availability:
A mix of features that ensure applications and services are available even if aserver or machine fails. Clients can continue to work with little or no disruption ina highly available environment. WebLogic achieves high availability using acombination of features: replication, failover, and migratable services.
Weblogic Server Basic Components
Domain:
A Weblogic server domain is an administrative grouping of servers and/or clusters. You configure, manage, monitor the domain from central location; this central location is the administration (admin) server.
Admin Server:
Admin server is just a Weblogic Server instance which maintains a repository of configuration information for the domain. Admin server acts as a centralized application deployment server which provides browser based admin console for configure, manage and monitor all aspects of the domain.
Managed Server:
A Managed server is a term for any other server in the domain other than the admin server. Managed Servers host the components and associated resources that constitute your applications - for example, JSPs and EJBs. When a Managed Server starts up, it connects to the domain's Administration Server to obtain configuration and deployment settings.
Two or more Managed Servers can be configured as a WebLogic Server cluster (more about this in next blog) to increase application scalability and availability. In a WebLogic Server cluster, most resources and services are deployed to each Managed Server (as opposed to a single Managed Server,) enabling failover and load balancing.
Node Manager:
Node Manager is a Java utility that runs as separate process from WebLogic Server and allows you to perform common operations tasks for a Managed Server, regardless of its location with respect to its Administration Server. While use of Node Manager is optional, it provides valuable benefits if your WebLogic Server environment hosts applications with high availability requirements.
If you run Node Manager on a machine that hosts Managed Servers, you can start and stop the Managed Servers remotely using the Administration Console or from the command line. Node Manager can also automatically restart a Managed Server after an unexpected failure.
WebLogic Server Cluster:
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. 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.
Useful links:
More articles on Weblogic
More articles on Weblogic Portal
Weblogic Portal Interview questions
A Weblogic server domain is an administrative grouping of servers and/or clusters. You configure, manage, monitor the domain from central location; this central location is the administration (admin) server.
Admin Server:
Admin server is just a Weblogic Server instance which maintains a repository of configuration information for the domain. Admin server acts as a centralized application deployment server which provides browser based admin console for configure, manage and monitor all aspects of the domain.
Managed Server:
A Managed server is a term for any other server in the domain other than the admin server. Managed Servers host the components and associated resources that constitute your applications - for example, JSPs and EJBs. When a Managed Server starts up, it connects to the domain's Administration Server to obtain configuration and deployment settings.
Two or more Managed Servers can be configured as a WebLogic Server cluster (more about this in next blog) to increase application scalability and availability. In a WebLogic Server cluster, most resources and services are deployed to each Managed Server (as opposed to a single Managed Server,) enabling failover and load balancing.
Node Manager:
Node Manager is a Java utility that runs as separate process from WebLogic Server and allows you to perform common operations tasks for a Managed Server, regardless of its location with respect to its Administration Server. While use of Node Manager is optional, it provides valuable benefits if your WebLogic Server environment hosts applications with high availability requirements.
If you run Node Manager on a machine that hosts Managed Servers, you can start and stop the Managed Servers remotely using the Administration Console or from the command line. Node Manager can also automatically restart a Managed Server after an unexpected failure.
WebLogic Server Cluster:
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. 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.
Useful links:
More articles on Weblogic
More articles on Weblogic Portal
Weblogic Portal Interview questions
Subscribe to:
Posts (Atom)