Weblogic Interview Questions – 2
1)Can I refresh static components of a deployed application without having to
redeploy the entire application?
Yes. You can use weblogic.Deployer to specify a component and target a server,
using the following syntax:
java weblogic.Deployer -adminurl http://admin:7001 -name appname -targets
server1,server2 -deploy jsps/*.jsp
2)When should I use the -nostage option?
Set the staging mode to -nostage (using weblogic.Deployer or the Administration
Console) if you don’t want to copy deployment files but want to deploy an
application from its present location. All target servers must be able to access
the same set of deployment files.
3)When should I use the external_stage option?
Set -external_stage using weblogic.Deployer if you want to stage the application
yourself, and prefer to copy it to its target by your own means.
4)Can I set the deployment order for application modules? For standalone
The Load Order attribute controls the deployment order of standalone modules and
applications relative to other modules and applications of the same type. For
example, standalone EJBs with smaller Load Order values are deployed before
those with higher values.
Modules that are deployed as part of an Enterprise Application (EAR file or
directory) are deployed in the order in which they are specified in the
application.xml deployment descriptor.
What is the difference between the WL_HOME/config/examples/applications folder
and the WL_HOME/config/examples/stage folder?
The applications folder is intended for applications that are not yet ready for
a production environment. WebLogic Server dynamically deploys the contents of
the applications folder. The stage folder (or a folder that you create for the
same purpose) is for storing copies of deployment files that are ready for
deployment in a production environment (deployments that use the stage or
external_stage deployment modes).
5)How do I turn the auto-deployment feature off?
The auto-deployment feature checks the applications folder every three seconds
to determine whether there are any new applications or any changes to existing
applications and then dynamically deploys these changes.
The auto-deployment feature is enabled for servers that run in development mode.
To disable auto-deployment feature, use one of the following methods to place
servers in production mode:
* In the Administration Console, click the name of the domain
in the left pane, then select the Production Mode checkbox in the right pane.
* At the command line, include the following argument when
starting the domain’s Administration Server:
Production mode is set for all WebLogic Server instances in a given domain.
6)Must EJBs be homogeneously deployed across a cluster? Why?
Yes. In WebLogic Server 6.0 and later, EJBs must be homogeneously deployed
across a cluster for the following reasons:
* To keep clustering EJBs simple
* To improve performance by avoiding cross-server calls. If
EJBs are not deployed on all servers, cross-server calls are more likely.
* To ensure that every EJB is available locall.y
* To ensure that all classes are loaded in an undeployable
way. Every server must have access to each EJB’s classes so that it can be bound
into the local JNDI tree. If only a subset of the servers deploys the bean, the
other servers will have to load the bean’s classes in their respective system
classpaths which makes it impossible to undeploy the beans.