Fails to start weblogic instances maintenance of Admin server as well as all managed servers etc. Troubleshooting in weblogic is found out the cause(Server fail, Server shutdown, SSL issue, Thread stuck, etc…) of WebLogic server failure if it occurs by servers logs
You can do several things to help prevent problems before you boot the cluster.
Your WebLogic Server license must include the clustering feature. If you try to start a cluster without a clustering license, you will see the error message Unable to find a license for clustering.
All Managed Servers in a cluster and the cluster's Administration Server should run under the same version of WebLogic Server. The major and minor version numbers (e.g 9.1), service packs, and attached patch levels should be the same across the cluster.
a) A problem with the multicast address is one of the most common reasons a cluster does not start or a server fails to join a cluster.
b) A multicast address is required for each cluster. The multicast address can be an IP number between 224.0.0.0 and 239.255.255.255, or a hostname with an IP address within that range.
c) You can check a cluster's multicast address and port on its Configuration-->Multicast tab in the Administration Console.
d) For each cluster on a network, the combination of a multicast address and port must be unique. If two clusters on a network use the same multicast address, they should use different ports. If the clusters use different multicast addresses, they can use the same port or accept the default port, 7001.
e) Before booting the cluster, make sure the cluster's multicast address and port are correct and do not conflict with the multicast address and port of any other clusters on the network.
f) The errors you are most likely to see if the multicast address is bad are:
Inclined to build a profession as Weblogic Developer? Then here is the blog post on, explore Weblogic Training
Make sure the value of CLASSPATH is the same on all managed servers in the cluster. CLASSPATH is set by the setEnv script, which you run before you run startManagedWebLogic to start the managed servers.
By default, setEnv sets this value for CLASSPATH (as represented on Windows systems):
set WL_HOME=C:beaweblogic700
set JAVA_HOME=C:beajdk131
.
.
set CLASSPATH=%JAVA_HOME%libtools.jar;
%WL_HOME%serverlibweblogic_sp.jar;
%WL_HOME%serverlibweblogic.jar;
%CLASSPATH%
If you change the value of CLASSPATH on one managed server or change how setEnv sets CLASSPATH, you must change it on all managed servers in the cluster.
Each server instance in the cluster has a default execute queue, configured with a fixed number of executing threads. To view the thread count for the default execute queue, choose the Configure Execute Queue command on the Advanced Options portion of the Configuration> General tab for the server. The default thread count for the default queue is 15, and the minimum value is 5. If the value of Thread Count is below 5, change it to a higher value so that the Managed Server does not hang on startup.
This section describes the first troubleshooting steps to perform if you have problems trying to start a cluster.
If the cluster fails to start, or a server fails to join the cluster, the first step is to check any commands you have entered, such as startManagedWebLogic or a java interpreter command, for errors and misspellings.
If you use the JRockit JVM under Linux, use one of the following methods to generate a thread dump.
To obtain the root PID, perform a: ps -efHl | grep 'java' **. **
Using a grep argument that is a string that will be found in the process stack that matches the server startup command. The first PID reported will be the root process, assuming that the ps command has not been piped to another routine.
Under Linux, each executing thread appears as a separate process under the Linux process stack. To use Kill -3 on Linux you supply must match the PID of the main WebLogic execute thread, otherwise, no thread dump will be produced.
If you are experiencing cluster problems, you should also check the garbage collection on the managed servers. If garbage collection is taking too long, the servers will not be able to make the frequent heartbeat signals that tell the other cluster members they are running and available.
If garbage collection (either first or second-generation) is taking 10 or more seconds, you need to tune heap allocation (the ms mx parameter) on your system.
Everything visible through the Weblogic admin console (http://localhost:7001/console) can be accessed through a command line java tool. This tool can be used to gather data about the weblogic servers via scripting. There are at least two ways to get runtime monitoring data about Weblogic processes. This document covers the use of the java classes that get information from management beans (mbeans). There is also a java tool that allows for browsing the mbean tree like an ftp client: Weblogic Scripting Tool (WLST).
There is a script for setting the CLASSPATH and PATH so that this tool can work. On pitblade (WL Server), the setWLSEnv script is /dsk2/local/bea81/weblogic81/server/bin/setWLSEnv.sh
pitblade:II:root: > source setWLSEnv.sh
CLASSPATH=/dsk2/local/bea81/jdk141_02/lib/tools.jar:/dsk2/local/bea81/weblogic81/server/lib/weblogic_sp.jar:
/dsk2/local/bea81/weblogic81/server/lib/weblogic.jar:/dsk2/local/bea81/weblogic81/server/lib/ojdbc14.jar:
:/dsk1/AdvIngres/ing26/ingres/lib/edbc.jar:/dsk1/AdvIngres/ing26/ingres/lib/edbc.jar
PATH=/dsk2/local/bea81/weblogic81/server/bin:/dsk2/local/bea81/jdk141_02/jre/bin:/dsk2/local/bea81/jdk141_02/bin:
/dsk1/AdvIngres/ing26/ingres/bin:/dsk1/AdvIngres/ing26/ingres/utility:/dsk1/AdvIngres/ing26/ingres/files:
/dsk1/AdvIngres/ing26/ingres/lib:/dsk1/AdvIngres/ing26/ingres/SUNWspro/bin:/sbin:/usr/sbin:/bin:/usr/bin:
/usr/ucb:/etc:/usr/etc:/opt/fw/bin:/var/adm/psmfc/bin:/usr/openwin/bin:/usr/local/bin:/usr/psmfc/bin:
/usr/ccs/bin:/usr/lib/nis:/opt/gnu/bin:/usr/local/bin
Your environment has been set.
pitblade:II:root: > java weblogic.Admin
weblogic.Admin is a command-line utility for managing WebLogic Server. Try:
weblogic.Admin help LIFECYCLE Starting, stopping, discovering servers
weblogic.Admin help INFO Retrieving info about WebLogic Server
weblogic.Admin help JDBC Working with JDBC connection pools
weblogic.Admin help MBEAN Working with WebLogic Server MBeans
weblogic.Admin help CLUSTER Working with clusters
weblogic.Admin help ALL Help for all commands
Usage: java [<SSL trust options>] weblogic.Admin
[ [-url | -adminurl] [<protocol>://]<listen-address>:<port>]
-username <username> -password <password>
<COMMAND> <ARGUMENTS>
More info available at: http://e-docs.bea.com/wls/docs81/admin_ref/cli.html
pitblade:II:root: > java weblogic.Admin
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/Admin
pitblade:II:root: > java weblogic.Admin -username user -password pass GETSTATE myserver
Current state of "myserver" : RUNNING
pitblade:II:root: > java weblogic.Admin -username user -password pass GET -pretty -type Server
---------------------------
MBeanName: "mydomain:Name=myserver,Type=Server"
AcceptBacklog: 50
AdministrationPort: 0
AutoKillIfFailed: false
AutoRestart: true
COM: myserver
COMEnabled: false
CachingDisabled: true
On command prompt issue this command:
ps -if | grep java
You should get a response like this:
reedi.psmfc.org:C1:root: > ps -eaf | grep java
root 6233 6221 0 Jan 31 ? 2:50 /usr/local/bea81/jdk141_02/bin/java -server -Xms32m -Xmx200m -XX:MaxPermSize=12
root 6273 6261 0 Jan 31 ? 361:59 /usr/local/bea81/jdk141_02/bin/java -server -Xms256m -Xmx512m -Djava.awt.headle
root 1121 6273 0 Feb 08 ? 15:29 /usr/local/bea81/jdk141_02/jre/bin/java -Xms256m -Xmx1024m -cp /global/ds1/pitw
root 2087 20643 0 13:44:11 pts/1 0:00 grep java
cd /usr/local/bea81/user_projects/mydomain2
nohup ./startManagedWebLogic.sh &
cd /dsk2/local/bea81/user_projects/mydomain
nohup ./startWeblogic.sh &
On pitblade(server), the file /tmp/wlproxy.log is filling the filesystem and crashing the server. Apparently, this file is debugged information generated by apache about the weblogic proxy plug-in. It probably causes a severe drain on resources and should not be generally active. Here is the relevant stanza from httpd.conf:
Note: The specified location of the log file seems to be ignored. There would not have been a problem if the log file was actually located where it was directed in the configuration.
<IfModule mod_weblogic.c>
WebLogicHost pitblade
WebLogicPort 7001
MatchExpression *.jsp
#MatchExpression /ptagis/home/regTagAction
WebLogicHost=pitblade|WebLogicPort=7001|Idempotent=OFF
Debug ON
WLLogFile /var/log/bea/wlproxy.log
HungServerRecoverSecs 30000
</IfModule>
After changing this setting, apache needs a restart like this:
apache2/bin/apachectl restart
Turned off this debugging output on pitblade and bay. The response time seems better as a result.
While there are many possible causes of performance degradation or hangs, this article can't possibly cover them all. Instead, we'll look at three common mistakes in WebLogic Server applications that can deadlock the server or bring your performance to a screeching halt.
The best Java tool for diagnosing deadlocks is a Java virtual machine thread dump. A thread dump is a snapshot of the virtual machine's current state, including stack traces for each Java thread. Many virtual machines also include information about the Java monitors held by each thread. Monitor information is especially useful for diagnosing deadlocks and performance problems in your application. On Windows platforms, you can generate a thread dump by pressing Ctrl-Break in the virtual machine's window. On Unix systems, a SIGQUIT signal must be sent to the Java virtual machine process. This can be done with a kill -3 <process id>.
Another common way to deadlock an application is what I call the "out of threads" deadlock. Unfortunately, this deadlock often doesn't show up until a load test or, in the worst case, when your production application receives a lot of traffic. In this scenario, your WebLogic Server is running with a fixed number of threads. The application includes logic where a given request or action performs work in one thread and then blocks on work that must be done in another thread.
d:T40fc,
At the end of this chapter you will be able to:
The key capabilities of a WebLogic cluster are:
When an object in an application is performing a task becomes unavailable, another object will take over and finish the job.
When all the services and applications in a single site fail they can switch to a separate site and continue processing.
When a server fails, pinned services can be migrated to another server in a cluster.
The even distribution of tasks and communications across multiple servers.
Inclined to build a profession as Weblogic Developer? Then here is the blog post on, explore Weblogic Training
Good architecture is somewhat subjective but there are a few global considerations:
1. Performance
2. Efficient replication
3. Optimal load balancing
4. Effective failover
5. Reliable communication
Basic cluster architecture combines static HTTP, presentation logic, business logic, and objects into one cluster.
The Web tier and the business logic with services can be separated into two clusters.
Similar to the basic cluster architecture, except for static content, is hosted on non-clustered HTTP servers.
Similar to the multi-tier cluster architecture, except for static content, is hosted on non-clustered HTTP servers.
A cluster can be located in different LANs within a MAN or within a WAN
In this chapter we discussed:
At the end of this chapter you will be able to:
Performance tuning WebLogic Server and your WebLogic Server application is a complex and iterative process. These tuning techniques are applicable to nearly all WebLogic applications. Although we highly recommend performing these tasks in the sequence they are presented, this isn't a requirement. Gather information about the level of activity expected on your server, the anticipated number of users, the number of requests, acceptable response time, and an optimal hardware configuration (e.g., fast CPU, disk size vs. speed, sufficient memory, and so on.). There is no single formula for determining your hardware requirements. The process of determining what type of hardware and software configuration is required to meet application needs adequately is called capacity planning. Capacity planning requires an assessment of your system performance goals and an understanding of your application. Capacity planning for server hardware should focus on maximum performance requirements.
Each operating system sets default tuning parameters differently. For Windows platforms, the default settings are usually sufficient. However, the UNIX and Linux operating systems usually need to be tuned appropriately.
Use the following guidelines when tuning UNIX operating systems supported by WebLogic Server.
For better TCP (transmission control protocol) socket performance, set the tcp_time_wait_interval parameter as follows: ndd -set /dev/tcp tcp_time_wait_interval 60000 This parameter determines the time interval that a TCP socket is kept alive after issuing a close call. The default value of this parameter on Solaris is four minutes. When a large number of clients connect for a short amount of time, holding these socket resources can have a significant negative impact on performance. Setting this parameter to a value of 60000 (60 seconds) has shown a significant throughput enhancement when running benchmark JSP tests on Solaris. You might want to reduce this setting further if the server gets backed up with a queue of half-opened connections.
Note:
Prior to Solaris 2.7, the tcp_time_wait_interval parameter was called tcp_close_wait_interval.
Inclined to build a profession as Weblogic Developer? Then here is the blog post on, explore Weblogic Training
Your database can be a major enterprise-level bottleneck. Configure your database for optimal performance by following the tuning guidelines.
Here are some general database tuning suggestions:
Inclined to build a profession as Weblogic Developer? Then here is the blog post on, explore Weblogic Training
Here are some basic tuning suggestions for Oracle, SQL Server, and Sybase. Again, you should also check the tuning guidelines in your database-specific vendor documentation.
Establishing a JDBC connection with a DBMS can be very slow. If your application requires database connections that are repeatedly opened and closed, this can become a significant performance issue. WebLogic connection pools offer an efficient solution to the problem. When WebLogic Server starts, connections from the connection pools are opened and are available to all clients. When a client closes a connection from a connection pool, the connection is returned to the pool and becomes available for other clients; the connection itself is not closed. There is little cost to opening and closing pool connections. How many connections should you create in the pool? A connection pool can grow and shrink according to configured parameters, between a minimum and a maximum number of connections. The best performance occurs when the connection pool has as many connections as there are concurrent client sessions.
The initial capacity attribute of the JDBCConnectionPool element enables you to set the number of physical database connections to create when configuring the pool. If the server cannot create this number of connections, the creation of this connection pool will fail. During development, it may be convenient to set the value of the InitialCapacity attribute to a low number to help the server startup faster. In production systems, consider setting the InitialCapacity value equal to the MaxCapacity attribute's default production mode setting of 25. This way, all database connections are acquired during server start-up. And if you need to tune the MaxCapacity value, make sure to set the InitialCapacity so that it equals the MaxCapacity value. If InitialCapacity is less than MaxCapacity, the server needs to create additional database connections when its load is increased. When the server is under load, all resources should be working to complete requests as fast as possible, rather than creating new database connections.
The max capacity attribute of the JDBCConnectionPool element allows you to set the maximum number of physical database connections that a connection pool can contain. Different JDBC drivers and database servers might limit the number of possible physical connections. The default settings for development and production mode are equal to the default number of executing threads: 15 for development mode; 25 for production mode. However, in production, it is advisable that the number of connections in the pool equal the number of concurrent client sessions that require JDBC connections. The pool capacity is independent of the number of executing threads in the server. There may be many more ongoing user sessions than there are execute threads.
When you use a prepared statement or callable statement in an application or EJB, there is considerable processing overhead for the communication between the application server and the database server and on the database server itself. To minimize the processing costs, WebLogic Server can cache prepared and callable statements used in your applications. When an application or EJB calls any of the statements stored in the cache, WebLogic Server reuses the statement stored in the cache. Reusing prepared and callable statements reduce CPU usage on the database server, improving performance for the current statement and leaving CPU cycles for other tasks. Using the statement cache can dramatically increase performance, but you must consider its limitations before you decide to use it.
The WebLogic Server configuration file (config.xml) contains a number of OOTB (out-of-the-box) performance-related parameters that can be fine-tuned depending on your environment and applications. Tuning these parameters based on your system requirements (rather than running with default settings) can greatly improve both single-node performance and the scalability characteristics of an application. Try experimenting with the following WebLogic Server configuration tuning parameters to determine your system's "sweet spot" for optimal performance:
After following the previous steps, run your application under a high load while monitoring the:
To check your disk utilization on Solaris or Linux, use the iostat -D <interval> command, where the interval value determines how many seconds you want to elapse between monitoring cycles. To check your CPU utilization, simply leave off the -D flag (iostat <interval>). For Windows, use the Performance Monitor tool (perfmon), to monitor both your disk and CPU utilization. The goal is to get to a point where the application server becomes 100 percent utilized. If you find that the application server CPU is not close to 100 percent, confirm whether the database is bottlenecked. If the database CPU is 100 percent utilized, then check your application SQL calls query plans. For example, are your SQL calls using indexes or doing linear searches? Also, confirm whether there is too many ORDER BY clauses used in your application that are affecting the database CPU.
Check the amount of data transferred between the application and the application server, and between the application server and the database server. This amount should not exceed your network bandwidth; otherwise, your network becomes the bottleneck. To verify this, monitor the network statistics for retransmission and duplicate packets. This can be done using the following command: netstat -s -P tcp
If you determine that neither the network nor the database server is the bottleneck, start looking at your WebLogic Server applications. Most importantly, is the machine running WebLogic Server able to get 100 percent CPU utilization with a high client load? If the answer is no, then check if there is any locking taking place in the application. You should profile your application using a commercially available tool (for example, JProbe or OptimizeIt) to pinpoint bottlenecks and improve application performance.
This section contains recommended application-specific tuning suggestions for performance improvement.
The Java virtual machine (JVM) is a virtual "execution engine" instance that executes the byte codes in Java class files on a microprocessor. How you tune your JVM affects the performance of WebLogic Server and your applications.
Tune your JVM's heap garbage collection and heap size parameters to get the best performance out of your JVM. The Sun HotSpot and WebLogic JRockit JVM parameters that most significantly affect performance are listed below.
When using the HotSpot VM option (-server or -client), experiment with the following garbage collection parameters:
When using JRockit's JVM, experiment with the following garbage collection parameters:
The following sections discuss JVM tuning options for WebLogic Server:
Although this section focuses on Sun Microsystems' J2SE 1.4 JVM for the Windows, UNIX, and Linux platforms, the BEA WebLogic JRockit JVM was developed expressly for server-side applications and optimized for Intel architectures to ensure reliability, scalability, manageability, and flexibility for Java applications.
Garbage collection is the JVM's process of freeing up unused Java objects in the Java heap. The Java heap is where the objects of a Java program live. It is a repository for live objects, dead objects, and free memory. When an object can no longer be reached from any pointer in the running program, it is considered "garbage" and ready for collection. The JVM heap size determines how often and how long the VM spends collecting garbage. An acceptable rate for garbage collection is application-specific and should be adjusted after analyzing the actual time and frequency of garbage collections. If you set a large heap size, full garbage collection is slower, but it occurs less frequently. If you set your heap size in accordance with your memory needs, full garbage collection is faster but occurs more frequently. The goal of tuning your heap size is to minimize the time that your JVM spends doing garbage collection while maximizing the number of clients that WebLogic Server can handle at a given time. To ensure maximum performance during benchmarking, you might set high heap size values to ensure that garbage collection does not occur during the entire run of the benchmark. You might see the following Java error if you are running out of heap space: java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> Exception in thread "main"
The HotSpot VM's verbose garbage collection option (verbosegc) enables you to measure exactly how much time and resources are put into garbage collection. To determine the most effective heap size, turn on verbose garbage collection and redirect the output to a log file for diagnostic purposes. The following steps outline this procedure:
This place thread dump information in the proper context with WebLogic Server informational and error messages, and provides a more useful log for diagnostic purposes. For example, on Windows and Solaris, enter the following: % java -ms32m -mx200m -verbosegc -classpath $CLASSPATH -Dweblogic.Name=%SERVER_NAME% -Dbea.home="C:bea" -Dweblogic.management.username=%WLS_USER% -Dweblogic.management.password=%WLS_PW% -Dweblogic.management.server=%ADMIN_URL% -Dweblogic.ProductionModeEnabled=%STARTMODE% -Djava.security.policy="%WL_HOME%serverlibweblogic.policy" weblogic.Server >> logfile.txt 2>&1 Where the logfile.txt 2>&1 command redirects both the standard error and standard output to a log file. On HPUX, use the following option to redirect stderr stdout to a single file: -Xverbosegc:file=/tmp/gc$$.out where $$ maps to the process ID (PID) of the Java process. Because the output includes timestamps for when garbage collection ran, you can infer how often garbage collection occurs.
1. How often is garbage collection taking place? In the log file, compare the timestamps around the garbage collection.
2. How long is garbage collection taking? Full garbage collection should not take longer than 3 to 5 seconds.
3. What is your average memory footprint? In other words, what does the heap settle back down to after each full garbage collection? If the heap always settles to 85 percent free, you might set the heap size smaller.
Use as large a heap size as possible without causing your system to "swap" pages to disk. The amount of free RAM on your system depends on your hardware configuration and the memory requirements of running processes on your machine. See your system administrator for help in determining the amount of free RAM on your system.
Typically, you should use 80 percent of the available RAM (not taken by the operating system or other processes) for your JVM.
Remember, the goal of tuning your heap size is to minimize the time that your JVM spends doing garbage collection while maximizing the number of clients that WebLogic Server can handle at a given time.
You must specify Java heap size values each time you start an instance of WebLogic Server. This can be done either from the java command line or by modifying the default values in the sample startup scripts that are provided with the WebLogic distribution for starting WebLogic Server. For example, when you start a WebLogic Server instance from a java command line, you could specify the HotSpot VM heap size values as follows: $ java -XX: NewSize=128m -XX: MaxNewSize=128m -XX: SurvivorRatio=8 -Xms512m -Xmx512m The default size for these values is measured in bytes. Append the letter `k' or `K' to the value to indicate kilobytes, `m' or `M' to indicate megabytes, and `g' or `G' to indicate gigabytes. The example above allocates 128 megabytes of memory to the New generation and maximum New generation heap sizes, and 512 megabytes of memory to the minimum and maximum heap sizes for the WebLogic Server instance running in the JVM.
Sample startup scripts are provided with the WebLogic Server distribution for starting the server and for setting the environment to build and run the server:
You achieve the best performance by individually tuning each application. However, configuring the Java HotSpot VM heap size options listed in the table when starting WebLogic Server increases performance for most applications. These options may differ depending on your architecture and operating system. See your vendor's documentation for platform-specific JVM tuning options.
| Table 3-2 Java Heap Size Options Task | Option | Recommended Value |
| Setting the New generation heap size | -XX:NewSize | Set this value to a multiple of 1024 that is greater than 1MB. As a general rule, set -XX: NewSize to be one-fourth the size of the maximum heap size. Increase the value of this option for larger numbers of short-lived objects. Be sure to increase the New generation as you increase the number of processors. Memory allocation can be parallel, but garbage collection is not parallel. |
| Setting the maximum New generation heap size | -XX:MaxNewSize | Set this value to a multiple of 1024 that is greater than 1MB. |
| Setting New heap size ratios | -XX: SurvivorRatio | The New generation area is divided into three sub-areas: Eden, and two survivor spaces that are equal in size. Configure the ratio of the Eden/survivor space size. Try setting this value to 8, and then monitor your garbage collection. |
| Setting minimum heap size | -Xms | Set the minimum size of the memory allocation pool. Set this value to a multiple of 1024 that is greater than 1MB. As a general rule, set minimum heap size (-Xms) equal to the maximum heap size (-Xmx) to minimize garbage collections. |
| Setting maximum heap size | -Xmx | Set the maximum size of the memory allocation pool. Set this value to a multiple of 1024 that is greater than 1MB. |
WebLogic Server enables you to automatically log low memory conditions observed by the server.
You configure the low memory detection process using the Administration Console:
You can indicate whether a domain is to be used in a development environment or a production environment. WebLogic Server uses different default values for various services depending on the type of environment you specify.
| Tuning Parameter | Development Mode Default | Production Mode Default |
| Execute Queue: ThreadCount | 15 threads | 25 threads |
| JDBC Connection Pool: MaxCapacity | 15 connections | 25 connections |
Benchmarks show major performance improvements when you use native performance packs on machines that host WebLogic Server instances. Performance packs use a platform-optimized, native socket multiplexor to improve server performance. For example, the native socket reader multiplexor threads have their own execute queue and do not borrow threads from the default execute queue, which frees up default execute threads to do application work. However, if you must use the pure-Java socket reader implementation for host machines, you can still improve the performance of socket communication by configuring the proper number of socket reader threads for each server instance and the client machine.
The value of the ThreadCount attribute of an ExecuteQueue element in the config.xml file equals the number of simultaneous operations that can be performed by applications that use the execute queue. As work enters an instance of WebLogic Server, it is placed in an execute queue. This work is then assigned to a thread that does the work on it. Threads consume resources, so handle this attribute with care—you can degrade performance by increasing the value unnecessarily. By default, a new WebLogic Server instance is configured with a development mode execute queue, weblogic.kernel.default, that contains 15 threads. In addition, WebLogic Server provides two other pre-configured queues:
Unless you configure additional execute queues, and assign applications to them, Web applications and RMI objects use weblogic.kernel.default.
Note: If native performance packs are not being used for your platform, you may need to tune the default number of executing queue threads and the percentage of threads that act as socket readers to achieve optimal performance.
Adding more threads to the default execute queue does not necessarily imply that you can process more work. Even if you add more threads, you are still limited by the power of your processor. Because threads consume memory, you can degrade performance by increasing the value of the ThreadCount attribute unnecessarily. A high execute thread count causes more memory to be used and increases context switching, which can degrade performance. The value of the ThreadCount attribute depends very much on the type of work your application does. For example, if your client application is thin and does a lot of its work through remote invocation, that client application will spend more time connected — and thus will require a higher thread count — than a client application that does a lot of client-side processing. If you do not need to use more than 15 threads (the development default) or 25 threads (the production default) for your work, do not change the value of this attribute. As a general rule, if your application makes database calls that take a long time to return, you will need more execute threads than an application that makes calls that are short and turn over very rapidly. For the latter case, using a smaller number of executing threads could improve performance.
An execute queue represents a named collection of execute threads that are available to one or more designated servlets, JSPs, EJBs, or RMI objects. An execute queue is represented in the domain config.xml file as part of the Server element. For example, an execute queue named CriticalAppQueue with four execute threads appears in the config.xml file as follows: ... <Server Name="examplesServer" ListenPort="7001" NativeIOEnabled="true"/> <ExecuteQueue Name="default" ThreadCount="15"/> <ExecuteQueue Name="CriticalAppQueue" ThreadCount="4"/> ... </Server>
You can assign a servlet or JSP to a configured execute queue by identifying the execute queue name in the initialization parameters. Initialization parameters appear within the init-param element of the servlet's or JSP's deployment descriptor file, web.xml. To assign an execute queue, enter the queue name as the value of the wl-dispatch-policy parameter, as in the example:
<servlet>
<servlet-name>MainServlet</servlet-name>
<jsp-file>/myapplication/critical.jsp</jsp-file>
<init-param>
<param-name>wl-dispatch-policy</param-name>
<param-value>CriticalAppQueue</param-value>
</init-param>
</servlet> Assigning EJBs and RMI Objects to Execute Queues
To assign an EJB object to a configured execute queue, use the new dispatch-policy element in Weblogic-ejb-jar.xml.
To determine the ideal thread count for an execute queue, monitor the queue's throughput while all applications in the queue are operating at maximum load. Increase the number of threads in the queue and repeat the load test until you reach the optimal throughput for the queue. (At some point, increasing the number of threads will lead to enough contexts switching that the throughput for the queue begins to decrease.)
Although you can configure the default execute queue to supply the optimal number of threads for all WebLogic Server applications, configuring multiple execute queues can provide additional control for key applications. By using multiple execute queues, you can guarantee that selected applications have access to a fixed number of executing threads, regardless of the load on WebLogic Server.
For best socket performance, BEA recommends that you use the native socket reader implementation, rather than the pure-Java implementation, on machines that host WebLogic Server instances. However, if you must use the pure-Java socket reader implementation for host machines, you can still improve the performance of socket communication by configuring the proper number of executing threads to act as socket reader threads for each server instance and the client machine. The ThreadPoolPercentSocketReaders attribute sets the maximum percentage of executing threads that are set to read messages from a socket. The optimal value for this attribute is application-specific. The default value is 33, and the valid range is 1-99. Allocating execute threads to act as socket reader threads increase the speed and the ability of the server to accept client requests. It is essential to balance the number of executing threads that are devoted to reading messages from a socket and those threads that perform the actual execution of tasks in the server.
WebLogic Server automatically detects when a thread in an execute queue becomes "stuck." Because a stuck thread cannot complete its current work or accept new work, the server logs a message each time it diagnoses a stuck thread. If all threads in an execute queue become stuck, the server changes its health state to either "warning" or "critical" depending on the execute queue:
WebLogic Server diagnoses a thread as stuck if it is continually working (not idle) for a set period of time. You can tune a server's thread detection behavior by changing the length of time before a thread is diagnosed as stuck, and by changing the frequency with which the server checks for stuck threads.
WebLogic Server uses a free pool to improve performance and throughput for stateless session EJBs. The free pool stores unbound stateless session EJBs. Unbound EJB instances are instances of a stateless session EJB class that are not processing a method call. The following figure illustrates the WebLogic Server free pool, and the processes by which stateless EJBs enter and leave the pool. Dotted lines indicate the "state" of the EJB from the perspective of WebLogic Server.
WebLogic Server free pool showing stateless session EJB life cycle
A pool of anonymous entity beans (that is., beans without a primary key class) used to invoke finders and home methods and to create other entity beans. The max-beans-in-free-pool element also controls the size of this pool. If you are running many finders or home methods or creating many beans, you may want to tune the max-beans-in-free-pool element so that there are enough beans available for use in the pool.
Use the initial-beans-in-free-pool element of the weblogic-ejb-jar.xml file to specify the number of stateless session bean instances in the free pool at startup. If you specify a value for initial-beans-in-free-pool, WebLogic Server populates the free pool with the specified number of bean instances at startup. Populating the free pool in this way improves initial response time for the EJB because initial requests for the bean can be satisfied without generating a new instance. initial-beans-in-free-pool defaults to 0 if the element is not defined.
You can configure the number of active bean instances that are present in the EJB cache (the in-memory space where beans exist). Use the max-beans-in-cache element of the weblogic-ejb-jar.xml file to specify the maximum number of objects of this bean class that are allowed in memory. When max-beans-in-cache is reached, WebLogic Server passivates some EJBs that have not been recently used by a client. The max-beans-in-cache element also affects when EJBs are removed from the WebLogic Server cache.
At the end of this chapter you will be able to:
WLS Security Architecture Overview Architecture Goals
– EJBs – Web Services
– Web Applications – Miscellaneous J2EE Resources
(Servlets, JSP) (RMI objects JDBC, JNDI, MBeans)
Security Architecture
Process Architecture
Security Services
Authentication Providers
Authorization Providers
Confidentiality
Interested in mastering Weblogic Training? Enroll now for FREE demo
on Weblogic Training.
Credential Mapping
Auditing
Managing Users and Groups: Security Realms
What Is LDAP?
Embedded LDAP Server
Configuring Embedded LDAP
Connecting an external LDAP browser
Users and Groups
Configuring New Users
Groups
Configuring New Groups
Roles
Configuring New Roles
Migrating Security Data
Exporting WLS Default Authenticator Provider
Importing into a different domain
Protecting Application Resources
J2EE Declarative Security
Using Deployment Descriptors
Protecting Web Applications with declarative security:
Define Security Roles
Determine Protected Resources
Web resources are defined based on URL patterns. URL patterns provide a flexible way to define a single resource or a group of resources. 
Map Roles to Resources…
Map Roles to Users in Realms
Setup Authentication
Authentication Examples
Policies and Roles
Defining Policies and Roles for Web Resources
Defining Policies and Roles for Other Resources…
Protecting Communications
What Is SSL?
Trust and Identity
Using a SSL Connection
Enabling Secure Communication
WebLogic Server SSL Requirements
The keytool Utility
Obtaining a Digital Certificate: keytool Examples
Configuring SSL for a WebLogic Server
Configuring Keystores
Protecting Against Attacks
Man in the Middle Attacks
Man in the Middle Countermeasures
Denial of Service Attacks
WebLogic Interview Questions
DoS Countermeasures
Filtering Network Connections
Connection Filter
Consuming WLS Resources
Large Buffer Attacks…
Connection Starvation…
User Lockout
Configuring User Lockout
Unlocking Users
Summary:
In this chapter we discussed:
10:T462e,
At the end of this chapter you will be able to:
Inclined to build a profession as Weblogic Developer? Then here is the blog post on, explore Weblogic Training
In this chapter, we learned how to:
WebLogic Server allows you to configure how your application prioritizes the execution of its work. Based on rules you define and by monitoring actual runtime performance, WebLogic Server can optimize the performance of your application and maintain service level agreements. You define the rules and constraints for your application by defining a Work Manager and applying it either globally to the WebLogic Server domain or to a specific application component.
WebLogic Server prioritizes work and allocates threads based on an execution model that takes into account administrator-defined parameters and actual run-time performance and throughput.
Administrators can configure a set of scheduling guidelines and associate them with one or more applications, or with particular application components. For example, you can associate one set of scheduling guidelines for one application, and another set of guidelines for other applications. At run-time, WebLogic Server uses these guidelines to assign pending work and enqueued requests to execution threads. To manage work in your applications, you define one or more of the following Work Manager components:
You can use any of these components to control the performance of your application by referencing the name of the component in the application’s deployment descriptor. In addition, you may define a Work Manager that encapsulates all of the above components (except Context Request Class) and reference the name of the Work Manager in your application’s deployment descriptor. You can define multiple Work Managers—the appropriate number depends on how many distinct demand profiles exist across the applications you host on WebLogic Server.
Work Managers can be configured at the domain level, application level, and module-level in one of the following configuration files:
Example of a Work Manager definition.
<work-manager>
<name>highpriority_workmanager</name>
<fair-share-request-class>
<name>high_priority</name>
<fair-share>100</fair-share>
</fair-share-request-class>
<min-threads-constraint>
<name>MinThreadsCountFive</name>
<count>5</count>
</work-manager>
To reference the Work Manager used in the example the dispatch policy of a Web Application, add the code in the Web Application’s web.xml file:
<init-param>
<param-name>wl-dispatch-policy</param-name>
<param-value>highpriority_workmanager</param-value>
</init-param>
The components you can define and use in a Work Manager are described in following sections.
A request class expresses a scheduling guideline that WebLogic Server uses to allocate threads to requests. Request classes help ensure that high priority work is scheduled before less important work, even if the high priority work is submitted after the lower priority work. WebLogic Server takes into account how long it takes for requests to each module to complete There are multiple types of request class, each of which expresses a scheduling guideline in different terms. A Work Manager may specify only one request class.
For example, assume that WebLogic Server is running two modules. The Work Manager for ModuleA specifies a fair-share-request-class of 80 and the Work Manager for ModuleB specifies a fair-share-request-class of 20.
During a period of sufficient demand, with a steady stream of requests for each module such that the number of requests exceeds the number of threads, WebLogic Server will allocate 80% and 20% of the thread-usage time to ModuleA and modules, respectively.
| Note: | The value of a fair share request class is specified as a relative value, not a percentage. Therefore, in the above example, if the request classes were defined as 400 and 100, they would still have the same relative values. |
For example, given that ModuleA and ModuleB in the previous example, have response time goals of 2000 ms and 5000 ms, respectively, and the actual thread use time for an individual request is less than its response time goal. During a period of sufficient demand, with a steady stream of requests for each module such that the number of requests exceeds the number of threads, and no “think time” delays between response and request, WebLogic Server will schedule requests for ModuleA and ModuleB to keep the average response time in the ratio 2:5. The actual average response times for ModuleA and ModuleB might be higher or lower than the response time goals, but will be a common fraction or multiple of the stated goal. For example, if the average response time for ModuleA requests is 1,000 ms., the average response time for ModuleB requests is 2,500 ms.
For example, the context-request-class in Context Request Class assigns a request class to requests based on the value of the request’s subject and role properties.
A context request class allows you to define request classes in an application’s deployment descriptor based on a user’s context. For example:
<work-manager>
<name>responsetime_workmanager</name>
<response-time-request-class>
<name>my_response_time</name>
<goal-ms>2000</goal-ms>
</response-time-request-class>
</work-manager>
<work-manager>
<name>context_workmanager</name>
<context-request-class>
<name>test_context</name>
<context-case>
<user-name>system</user-name>
<request-class-name>high_fairshare</request-class-name>
</context-case>
<context-case>
<group-name>everyone</group-name>
<request-class-name>low_fairshare</request-class-name>
</context-case>
</context-request-class>
</work-manager>
Above, we explained the request classes based on fair share and response time by relating the scheduling to other work using the same request class. A mix of fair share and response time request classes is scheduled with a marked bias in favor of response time schedule.
A constraint defines the minimum and maximum numbers of threads allocated to execute requests and the total number of requests that can be queued or executing before WebLogic Server begins rejecting requests. You can define the following types of constraints:
max-threads-constraint—This constraint limits the number of concurrent threads executing requests from the constrained work set. The default is unlimited. For example, consider a constraint defined with maximum threads of 10 and shared by 3 entry points. The scheduling logic ensures that not more than 10 threads are executing requests from the three entry points combined. A max-threads-constraint can be defined in terms of the availability of resources that requests depend upon, such as a connection pool. A max-threads-constraint might, but does not necessarily, prevent a request class from taking its fair share of threads or meeting its response time goal. Once the constraint is reached the server does not schedule requests of this type until the number of concurrent executions falls below the limit. The server then schedules work based on the fair share or response time goal.
min-threads-constraint—This constraint guarantees a number of threads the server will allocate to affected requests to avoid deadlocks. The default is zero. A min-threads-constraint value of one is useful, for example, for a replication update request, which is called synchronously from a peer. A min-threads-constraint might not necessarily increase a fair share. This type of constraint has an effect primarily when the server instance is close to a deadlock condition. In that case, the constraint will cause WebLogic Server to schedule a request even if requests in the service class have more requests than its fair share recently.
capacity—This constraint causes the server to reject requests only when it has reached its capacity. The default is -1. Note that the capacity includes all requests, queued or executing, from the constrained work set. Work is rejected either when an individual capacity threshold is exceeded or if the global capacity is exceeded. This constraint is independent of the global queue threshold.
In response to stuck threads, you can define a Stuck Thread Work Manager component that can shut down the Work Manager, move the application into admin mode, or mark the server instance as failed. For instance, the Work Manager defined in Listing 2-4 shuts down the Work Manager when two threads are stuck for longer than 30 seconds.
<work-manager>
<name>stuckthread_workmanager</name>
<work-manager-shutdown-trigger>
<max-stuck-thread-time>30</max-stuck-thread-time>
<stuck-thread-count>2</stuck-thread-count>
</work-manager-shutdown-trigger>
</work-manager>
Essentially, there are three types of Work Managers, each one characterized by its scope and how it is defined and used. The three types are:
These three types of Work Managers are described in the following sections:
You can override the behavior of the default Work Manager by creating and configuring a global Work Manager called default. This allows you to control the default thread-handling behavior of WebLogic Server.
Following are guidelines to help you determine when you might want to use Work Managers to customize thread management:
In addition to globally-scoped Work Managers, you can also create Work Managers that are available only to a specific application or module. Work Managers can be specified in the following descriptors:
If you do not explicitly assign a Work Manager to an application, it uses the default Work Manager.
A method is assigned to a Work Manager, using the <dispatch-policy> element in the deployment descriptor. The <dispatch-policy> can also identify a custom execute queue, for backward compatibility.
Work Managers, Request Classes, and Constraints require the following:
Dispatch Policy for EJB
weblogic-ejb-jar.xml—the value of the existing dispatch-policy tag under weblogic-enterprise-bean can be a named dispatch-policy. For backward compatibility, it can also name an ExecuteQueue. In addition, we allow dispatch-policy, max-threads, and min-threads, to specify named (or unnamed with a numeric value for constraints) policy and constraints for a list of methods, analogously to the present isolation-level tag.
Dispatch Policy for Web Applications
weblogic.xml—also supports mappings analogous to the filter-mapping of the web.xml, where named dispatch-policy, max-threads, or min-threads are mapped for url-patterns or servlet names.
This section contains examples for defining Work Managers in various types of deployment descriptors. For additional reference, see also the schema for these deployment descriptors:
weblogic-ejb-jar.xml With Work Manager Entries
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>WorkEJB</ejb-name>
<jndi-name>core_work_ejb_workbean_WorkEJB</jndi-name>
<dispatch-policy>weblogic.kernel.System</dispatch-policy>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>NonSystemWorkEJB</ejb-name>
<jndi-name>core_work_ejb_workbean_NonSystemWorkEJB</jndi-name>
<dispatch-policy>workbean_workmanager</dispatch-policy>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>MinThreadsWorkEJB</ejb-name>
<jndi-name>core_work_ejb_workbean_MinThreadsWorkEJB</jndi-name>
<dispatch-policy>MinThreadsCountFive</dispatch-policy>
</weblogic-enterprise-bean>
<work-manager>
<name>workbean_workmanager</name>
</work-manager>
<work-manager>
<name>stuckthread_workmanager</name>
<work-manager-shutdown-trigger>
<max-stuck-thread-time>30</max-stuck-thread-time>
<stuck-thread-count>2</stuck-thread-count>
</work-manager-shutdown-trigger>
</work-manager>
<work-manager>
<name>minthreads_workmanager</name>
<min-threads-constraint>
<name>MinThreadsCountFive</name>
<count>5</count>
</min-threads-constraint>
</work-manager>
<work-manager>
<name>lowpriority_workmanager</name>
<fair-share-request-class>
<name>low_priority</name>
<fair-share>10</fair-share>
</fair-share-request-class>
</work-manager>
<work-manager>
<name>highpriority_workmanager</name>
<fair-share-request-class>
<name>high_priority</name>
<fair-share>100</fair-share>
</fair-share-request-class>
</work-manager>
<work-manager>
<name>veryhighpriority_workmanager</name>
<fair-share-request-class>
<name>veryhigh_priority</name>
<fair-share>1000</fair-share>
</fair-share-request-class>
</work-manager>
weblogic-ejb-jar.xml with Connection Pool Based Max Thread Constraint
These EJBs are configured to get as many threads as there are instances of a resource they depend upon—a connection pool, and an application scoped connection pool.
</weblogic-ejb-jar>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>ResourceConstraintEJB</ejb-name>
<jndi-name>core_work_ejb_resource_ResourceConstraintEJB</jndi-name>
<dispatch-policy>test_resource</dispatch-policy>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>AppScopedResourceConstraintEJB</ejb-name>
<jndi-name>core_work_ejb_resource_AppScopedResourceConstraintEJB
</jndi-name>
<dispatch-policy>test_appscoped_resource</dispatch-policy>
</weblogic-enterprise-bean>
<work-manager>
<name>test_resource</name>
<max-threads-constraint>
<name>pool_constraint</name>
<pool-name>testPool</pool-name>
</max-threads-constraint>
</work-manager>
<work-manager>
<name>test_appscoped_resource</name>
<max-threads-constraint>
<name>appscoped_pool_constraint</name>
<pool-name>AppScopedDataSource</pool-name>
</max-threads-constraint>
</work-manager>
</weblogic-ejb-jar>
weblogic-application.xml
<weblogic-application xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
http://www.bea.com/ns/weblogic/90/weblogic-application.xsd">
<max-threads-constraint>
<name>j2ee_maxthreads</name>
<count>1</count>
</max-threads-constraint>
<min-threads-constraint>
<name>j2ee_minthreads</name>
count>1</count>
</min-threads-constraint>
<work-manager>
<name>J2EEScopedWorkManager</name>
</work-manager>
</weblogic-application>
web application descriptor
This Web Application is deployed as part of the Enterprise Application defined in weblogic-application.xml. This Web Application’s descriptor defines two Work Managers. Both Work Managers point to the same max threads constraint, j2ee_maxthreads which is defined in the application’s weblogic-application.xml file. Each Work Manager specifies a different response time request class.
<weblogic xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
http://www.bea.com/ns/weblogic/90/weblogic.xsd">
<work-manager>
<name>fast_response_time</name>
<response-time-request-class>
<name>fast_response_time</name>
<goal-ms>2000</goal-ms>
</response-time-request-class>
<max-threads-constraint-name>j2ee_maxthreads
</max-threads-constraint-name>
</work-manager>
<work-manager>
<name>slow_response_time</name>
<max-threads-constraint-name>j2ee_maxthreads
</max-threads-constraint-name
<response-time-request-class>
<name>slow_response_time</name>
<goal-ms>5000</goal-ms>
</response-time-request-class>
</work-manager>
</weblogic>
web application descriptor
This descriptor defines a Work Manager using the context-request-class.
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/90
http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
<work-manager>
<name>foo-servlet-1</name>
<request-class-name>test-fairshare2</request-class-name>
<max-threads-constraint>
<name>foo-mtc</name>
<pool-name>oraclePool</pool-name>
</max-threads-constraint>
</work-manager>
<work-manager>
<name>foo-servlet</name>
<context-request-class>
<name>test-context</name>
<context-case>
<user-name>anonymous</user-name>
<request-class-name>test-fairshare1</request-class-name>
</context-case>
<context-case>
<group-name>everyone</group-name>
<request-class-name>test-fairshare2</request-class-name>
</context-case>
</context-request-class>
</work-manager>
</weblogic-web-app>
This section discusses how to enable backward compatibility with Execute Queues and how to migrate applications from using Execute Queues to Work Managers.
WebLogic Server, Version 8.1 implemented Execute Queues to handle thread management which allowed you to create thread-pools to determine how the workload was handled. WebLogic Server still provides Execute Queues for backward compatibility, primarily to facilitate application migration. However, new application development should utilize Work Managers to perform thread management more efficiently. You can enable Execute Queues in the following ways:
-Dweblogic.Use81StyleExecuteQueues=true
When enabled, Work Managers are converted to Execute Queues based on the following rules:
When an application is migrated from WebLogic Server 8.1, any Execute Queues defined in the server configuration before migration will still be present. WebLogic Server does not automatically convert the Execute Queues to Work Managers. When an 8.1 application implementing Execute Queues is deployed on WebLogic Server 9.x, the Execute Queues are created to handle thread management for requests. However, only those requests whose dispatch-policy maps to an Execute Queue will take advantage of this feature.
At the end of this chapter you will be able to:
The following sections describe general procedures that are applicable to both the Java and scripted version of Node Manager:
Node Manager must run on each computer that hosts a WebLogic Server instance. Configure each computer as a machine resource in WebLogic Server, and assign each server instance that you will control with Node Manager to the machine upon which it runs.
Ideally, Node Manager should run as an operating system service or daemon, so that it is automatically restarted in the event of system failure or reboot.
Node Manager is ready-to-run after WebLogic Server installation if you run Node Manager and the Administration Server on the same machine and use the demonstration SSL configuration.
By default, the following behaviors are configured:
However, by default, the nmConnect command cannot be used in a production environment. You must first perform the following procedures to use nmConnect in a production environment.
1. Start the Administration Server.
2. Using the Administration Console update the Node Manager credentials from the Advanced options under domain_name→Security→General.
3. Invoke WLST and connect to an Administration Server using the connect command.
4. Run nmEnroll using the following syntax: nmEnroll([domainDir], [nmHome])
For example,
nmEnroll('C:/bea/user_projects/domains/prod_domain',
'C:/bea/wlserver_10.0/common/nodemanager')
Running nmEnroll() ensures that the correct Node Manager user and password token are supplied to each Managed Server. Once these are available for each Managed Server, you can use nmConnect() in a production environment.
Note: You must run nmEnroll() on each machine that is running a Managed Server. Additionally, you should run nmEnroll() for each domain directory on each machine.
The nm_password.properties file contains the Node Manager username and password. These are used to authenticate the connection between a client (for example, the Administration Server) and Node Manager.
Note: This username and password are only used to authenticate connections between Node Manager and clients. They are independent of the server admin ID and password.
Administration Console NM Security
Domain_Name -> Security -> Advanced Options
Configure a machine definition for each machine that runs a Node Manager process using the Environment→Machines→<machine_name>→Node Manager page in the Administration Console. Enter the DNS name or IP address upon which Node Manager listens in the Listen Address field.
In the Administration Console, on the Server→Configuration→Server Start page for the Managed Server, specify the startup arguments that Node Manager will use to start a Managed Server. If you do not specify startup arguments for a Managed Server, Node Manager uses its own properties as defaults to start the Managed Server.
You can use the Node Manager to set the startup properties for a server. These properties can be defined in startup.properties or passed as an object using administrative utilities such as WLST. This file is defined for each server instance and is located in:
domain_home/servers/server_name/data/nodemanager/startup.properties
Node Manager requires you to set several environment variables before you start it. You can set these variables manually on the command line, or you can create a start script that sets them automatically. The sample start scripts provided with WebLogic Server, startNodeManager.cmd, and startNodeManager.sh, set the required variables.
The directory WL_HOMEserverbin (where WL_HOME is the top-level directory for the WebLogic Server installation) contains uninstallNodeMgrSvc.cmd, a script for uninstalling the Node Manager service, and installNodeMgrSvc.cmd, a script for installing Node Manager as a service.
Node Manager credentials are located on the domain_name→Security→General→Advanced Options page in the Administration Console.
Administration Console users do not need to provide credentials to connect to Node Manager explicitly—the Node Manager username and password are available in the domain configuration and are provided automatically.
Remote Server Start Security for Java-Based Node Manager
Credentials for Managed Servers and Administration Servers are handled differently:
Node Manager properties define a variety of configuration settings for a Java-based Node Manager process. You can specify Node Manager properties on the command line or define them in the nodemanager.properties file, which is created in the directory where you start Node Manager the first time it starts up after installation of WebLogic Server. Values supplied on the command line override the values in nodemanager.properties.
nodemanager.properties is created in the directory specified in NodeManagerHome, where NodeManagerHome is WL_HOME/common/nodemanager. If NodeManagerHome is not defined, nodemanager.properties is created in the current directory.
Each time you start Node Manager, it looks for nodemanager.properties on the current directory and creates the file if it does not exist in that directory. You cannot access the file until Node Manager has started up once.
If you have a domain that has Managed Servers on multiple physical machines, you must ensure that the Node Manager is installed and configured on each machine. You can use the WLST command nmEnroll to copy all of the required domain and configuration information from one machine to another.
When configuring Node Manager to run as an inetd or xinetd service, the following considerations apply:
The following example shows how the Node Manager can be configured within xinetd:
# default: off
# description:nodemanager as a service
service nodemgrsvc
{
type = UNLISTED
disable = no
socket_type = stream
protocol = tcp
wait = yes
user = <username>
port = 5556
flags = NOLIBWRAP
log_on_success += DURATION HOST USERID
server = <path-to-jave>/java
env = CLASSPATH=<cp> LD_LIBRARY_PATH=<ldpath>
server_args = -client -DNodeManagerHome=<NMHome> <java options> <nodemanager options> weblogic.NodeManager -v
}
– Using SSL With Script-based Node Manager
– Creating a Node Manager User
– Configuring Script-based Node Manager Security
At the end of this chapter you will be able to:
Node Manager can be used to:
WebLogic Server provides two versions of Node Manager, Java-based and script-based, with similar functionality. However, each version has a different configuration and security considerations.
Note:
It is recommended that you run a script-based Node Manager as an operating system service, which allows it to restart automatically when the system is rebooted.
Which version of Node Manager to use depends on the requirements of your WebLogic Server environment. The following considerations can help you decide which version is ideal for your environment:
A Node Manager client can be local or remote to the Node Managers with which it communicates. You access either version of Node Manager—the Java version or the script-based (SSH) version—from the following clients:
WLST offline serves as a Node Manager command-line interface that can run in the absence of a running Administration Server. You can use WLST commands to start, stop, and monitor a server instance without connecting to an Administration Server. Starting the Administration Server is the main purpose of the stand-alone client. However, you can also use WLST to:
The following diagram specifies the relationship between Node Manager, its clients, and the server instances it controls.
Note: If the user has previously connected to the Node Manager, a boot.properties file exists, and the user does not have to supply a username and password.
2 & 3. Node Manager looks up the domain directory in nodemanager.domains and authenticates the user credentials using a local file that contains the encrypted username and password.
Note: A stand-alone client can also issue a start command for a Managed Server.
Node Manager starts the Managed Server using the same root directory where the Node Manager process is running. To run the Managed Server in a different directory, set the Root Directory attribute in the Server—>Configuration—>Server Start console page.
Note: Node Manager waits for RestartDelaySeconds after a server instance fails before attempting to restart it.
Note: Managed Server Independence mode is enabled by default
Except where noted, configuration files apply to both Java-based and script-based Node Manager.
This is the configuration file used by the Java-based version of Node Manager. This file is located in WL_HOME/common/nodemanager, where WL_HOME is the location in which you installed WebLogic Server.
This file contains mappings between the names of domains managed by Node Manager and their corresponding directories. This file is located in WL_HOME/common/nodemanager.
This file stores the encryption data the Node Manager uses as an asymmetric encryption key. The data is stored in encrypted form. This file is located in WL_HOME/common/nodemanager.
This file stores the Node Manager username and password. This file is located in DOMAIN_HOME/config/nodemanager.
Node Manager uses this file to specify user credentials when starting a server. This file is located in DOMAIN_HOME/servers/<server_name>/data/nodemanager.
Note: Do not delete or alter this file. Without this file, the Node Manager cannot determine the current state of the server.
Use the Node Manager and WebLogic Server log files to help troubleshoot problems in starting or stopping individual Managed Servers.
NodeManagerHome/nodemanager.log, where NodeManagerHome is WL_HOME/common/nodemanager
DOMAIN_HOME/servers/<server_name>/logs/<server_name>.out, where DOMAIN_HOME is the location in which you installed your WebLogic Server domain, such as d:beauser_projectsdomains<domain-name>
DOMAIN_HOME/servers/<server_name>/logs/<server_name>.log
At the end of this chapter you will be able to:
A WebLogic Server administration domain is a logically related group of WebLogic Server resources. Domains include a special WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain. Usually, you configure a domain to include additional WebLogic Server instances called Managed Servers. You deploy Web applications, EJBs, Web Services, and other resources onto the Managed Servers and use the Administration Server for configuration and management purposes only.
You can use a single WebLogic Server installation to create and run multiple domains, or you can use multiple installations to run a single domain. Depending on your particular business needs and system administration practices, you might decide to organize your domains based on criteria such as:
For development or test environments, you can create a simple domain that consists of a single server instance. This single instance acts as an Administration Server and hosts the applications that you are developing. The wl_server domain that you can install with WebLogic Server is an example of this type of domain.
The Administration Server operates as the central control entity for the configuration of the entire domain. It maintains the domain’s configuration documents and distributes changes in the configuration documents to Managed Servers. You can also use the Administration Server as a central location from which to monitor all resources in a domain. Admin Clients: To interact with the Administration Server, you can use the Administration Console, WLST, or create your own JMX client.
Managed Servers host business applications, application components, Web Services, and their associated resources. To optimize performance, Managed Servers maintain a read-only copy of the domain's configuration document. When a Managed Server starts up, it connects to the domain's Administration Server to synchronize its configuration document with the document that the Administration Server maintains. For production environments that require increased application performance, throughput, or high availability, you can configure two or more Managed Servers to operate as a cluster. A cluster is a collection of multiple WebLogic Server instances running simultaneously and working together to provide increased scalability and reliability.
In addition to the Administration Server and Managed Servers, a domain also contains the resources and services that Managed Servers and deployed applications require.
Security providers, which are modular components that handle specific aspects of security, such as authentication and authorization.
Note: All managed servers in a domain must run the same version of WebLogic Server. The administration server can run either the same version as the managed servers in the domain or a later service pack.
In designing your domain configuration, note the following restrictions:
You might find it useful to configure multiple domains based on specific criteria, such as system administrator responsibilities, the logical classification of applications, the geographical locations of servers, or size. The following table outlines the most common domain configurations. 1) Domain with managed servers: In typical production environments, several managed servers can host applications, and an administration server performs management operations. 2) Domain with managed servers and clusters: In production environments that require increased performance, throughput, or availability for an application, several managed servers might be grouped in a cluster. In such a case, the domain consists of one or more clusters with the applications they host, additional managed servers, if necessary, and an administration server to perform management operations. 3) Stand-alone Server Domain: In development or test environments, a single application and server might be deployed independently without managed servers. In such a case, you can have a domain consisting of a single administration server that also hosts the applications you want to test or develop. Note: In production environments, it is recommended that you deploy applications only on managed servers; the administration server should be reserved for management tasks.
Before you can develop and run a WebLogic application, you must first create a domain. The Configuration Wizard (illustrated in Figure 1-2), simplifies the process of creating and extending a domain. To create or extend a domain by using the Configuration Wizard, you simply select the product components to be included in the domain (or choose a template that best meets your requirements) and provide basic configuration information. The Configuration Wizard then creates or extends the domain by using the settings from templates. 
After you create a domain by using the Configuration Wizard, you can start a WebLogic Server instance to run in the domain for developing, testing, and deploying applications.
You might want to customize your domain in the following circumstances:
. 
You can start the Configuration Wizard in graphical mode from either the Windows Start menu or from the command line. Note: If you attempt to start the Configuration Wizard in graphical mode on a system that cannot support graphical display, the Configuration Wizard automatically starts in console mode.
On Windows: config.cmd
On UNIX: sh config.sh
1. Open an MS-DOS command prompt window (on Windows) or a command shell (on UNIX).
2. Go to the commonbin subdirectory of the product installation directory.
3. Execute the following command:
– Windows: config.cmd -mode=console
– UNIX: sh config.sh -mode=console
Note: The command and arguments must be entered in lower case.
The Welcome screen is displayed.
Note: silent mode is deprecated in WebLogic Server 9.X
The Configuration Wizard guides you through the process of creating a new domain quickly and easily, by selecting the product components that you want to include in your domain, or by using domain templates.
1. Start the Configuration Wizard as described in Starting the Configuration Wizard. The Welcome window is displayed
3. Select Generate a domain configured automatically to support the following products: WebLogic Server is selected, by default. Select the checkboxes corresponding to the other products that you want to include in the
4) Click Next. The Configure Administrator Username and Password window are displayed and configure the username and password for the administrator: 
5) Select the WebLogic domain startup mode:
Select the JDK: In the JDK Selection pane, select the JDK for the startup mode that you selected in the WebLogic Domain Startup Mode pane. The Configuration Wizard presents a list of the JDKs included in the installer. You can choose one of these JDKs or another JDK that you have installed on your system.
Click next then The Customize Environment and Services Settings window is displayed.
6) Customizing the Environment and Service Settings… While creating the domain, you can specify the RDBMS security store settings, configure the distribution of your domain across servers, clusters, and machines, specify JDBC data sources, define JMS file store settings. Select Yes and click on Next.
7) Configure the Administration Server and Managed Servers
8) Configure Clusters
9) Assign Servers to Clusters
10) Configure Machines
11) Assign Servers to Machines
12) Enter the name of the domain and specify the domain location.
13) Click Create.
Note: You cannot overwrite an existing domain. If a domain with the name you specified already exists in the selected location, you must either delete the existing domain or specify a different name or location for the new domain.
The name of this directory is the name of the domain.
This directory provides a quick way to deploy applications in a development server. When the WebLogic Server instance is running in development mode, it automatically deploys any applications or modules that you place in this directory. The files you place in this directory can be Java EE applications, such as: An EAR file, A WAR, EJB JAR, RAR archived module.
This directory contains scripts that are used in the process of starting and stopping the Administration Server and the Managed Servers in the domain. These scripts are generally provided as .sh files for UNIX and .cmd files for Windows. The bin directory can optionally contain other scripts of domain-wide interest, such as scripts to start and stop database management systems, full-text search engine processes, etc.
This directory contains the current configuration and deployment state of the domain. The central domain configuration file, config.xml, resides in this directory.
This directory contains extensions to the Administration Console, which enable you to add content to the WebLogic Server Administration Console, replace content, and change the logos, styles, and colors without modifying the files that are installed with WebLogic Server. For example, you can add content that provides custom monitoring and management facilities for your applications.
This directory contains files used for WebLogic domain provisioning. You should not modify any files in this directory.
Any JAR files you put in this directory are added to the system classpath of each server instance in the domain when the server’s Java virtual machine starts.
This directory contains domain configuration files representing configuration changes that have been requested, but not yet activated. Once the configuration changes have been activated, the configuration files are deleted from this directory.
This directory holds those security-related files that are the same for every WebLogic Server instance in the domain: SerializedSystemIni.dat This directory also holds security-related files that are only needed by the domain’s Administration Server: DefaultAuthorizerInit.ldift, DefaultAuthenticatorInit.ldift, DefaultRoleMapperInit.ldift
This directory contains one subdirectory for each WebLogic Server instance in the domain. The subdirectories contain data that is specific to each server instance.
This directory stores temporary files used in the change management process. You should not modify any files in this directory.
By default, configuration information is automatically copied from the Administration Server to each Managed Server. If instead, you prefer to stage configuration changes manually, you can use this directory as an alternative to the config directory.
Welcome to the Weblogic Tutorial. The objective of these tutorials is to provide an in-depth understanding of the Weblogic Application Server.
In addition to free Weblogic Tutorials, we will also cover common interview questions, how-to tutorials and issues and their resolutions of Weblogic Application Server
WebLogic Tutorial - Table of Contents |
Weblogic Server is a sort of server that backings different administrations and in addition find that are connected with JEE applications. WebLogic server is fit for conveying segments and in addition applications through WSDL, UDDI, and SOAP.
A Weblogic server gets designed as a web server by making utilization of HTTP audience for supporting the HTTP. Web servers like that of Apache, Netscape, and Microsoft are utilized. The design of a web server permits WebLogic is fit for giving administrations to dynamic and static demands that are normally produced by servlets, HTML, and JSP.
Weblogic Server is a software product that acts as a liaison between the front end and back end applications. Weblogic Application Server is widely used for its JMS capabilities. Later in these sessions, we will learn in detail about Weblogic Installation, Security, JMS, and Clustering.
The following are the various Weblogic Server versions released from 2o02. The most recent version of Weblogic is 12c.
WebLogic Server 12c Release 3 (12.1.3) - June 26, 2014
WebLogic Server 12c Release 2 (12.1.2) - July 11, 2013
WebLogic Server 12c Release 1 (12.1.1) - Dec 1, 2011
WebLogic Server 11gR1 PS5 (10.3.6) - February 26, 2012
WebLogic Server 11gR1 PS4 (10.3.5) - May 16, 2011
WebLogic Server 11gR1 PS3 (10.3.4) - January 15, 2011
WebLogic Server 11gR1 PS2 (10.3.3) - April 2010
WebLogic Server 11gR1 PS1 (10.3.2) - Nov 2009
WebLogic Server 11g (10.3.1) - Jul 2009
WebLogic Server 10.3 - Aug 2008
WebLogic Server 10.0 - Mar 2007
WebLogic Server 9.2
WebLogic Server 9.1
WebLogic Server 9.0 - Nov 2006
WebLogic Server 8.1 - Jul 2003
WebLogic Server 7.0 - Jun 2002
| Want to acquire industry skills and gain complete knowledge of WebLogic? Enrol in Instructor-Led live WebLogic Training to get Job Ready! |
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.
Oracle WebLogic Server supports Oracle, DB2, MS SQL Server, MySQL Enterprise, and other JDBC-compliant databases. Oracle Weblogic Platform also includes:
Standards Supported by version
The table below lists major standards supported by the WebLogic Server product version.
| Standard | WLS 7.0 | WLS 8.1 | WLS 9.0 | WLS 10.0 | WLS 10.3 |
| Java | 1.3 | 1.4 | 5 | 5 | 6 |
| Java EE | 1.3 | 1.3 | 1.4 | 5 | 5 |
System administration of WebLogic Server includes a wide range of tasks: creating WebLogic Server domains; deploying applications; migrating domains from development environments to production environments; monitoring and managing the performance of the run-time system; diagnosing and troubleshooting problems. (A WebLogic Server domain is a collection of WebLogic Server services designed for a specific purpose. For example, you might create one domain to provide an employee portal and another domain to provide business services to your customers.)
Because 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. In addition, WebLogic Server includes several of its own standards-based, extensible utilities. Alternatively, you can use APIs to create custom management utilities.
At the end of this module you will be able to:
The software components of a multitier architecture consist of three tiers:
| Checkout Our Blog on WebLogic JDBC |
A Web server handles the HTTP protocol. When the Web server receives an HTTP request, it responds with an HTTP response, such as sending back an HTML page. To process a request, a Web server may respond with a static HTML page or image, send a redirect, or delegate the dynamic response generation to some other program such as CGI scripts, JSPs (JavaServer Pages), servlets, ASPs (Active Server Pages), server-side JavaScripts, or some other server-side technology. Whatever their purpose, such server-side programs generate a response, most often in HTML, for viewing in a Web browser.
Understand that a Web server's delegation model is fairly simple. When a request comes into the Web server, the Web server simply passes the request to the program best able to handle it. The Web server doesn't provide any functionality beyond simply providing an environment in which the server-side program can execute and pass back the generated responses. The server-side program usually provides for itself such functions as transaction processing, database connectivity, and messaging.
While a Web server may not itself support transactions or database connection pooling, it may employ various strategies for fault tolerance and scalability such as load balancing, caching, and clustering—features oftentimes erroneously assigned as features reserved only for application servers.
Proxy some requests to Application Servers
As for the application server, according to our definition, an application server exposes business logic to client applications through various protocols, possibly including HTTP. While a Web server mainly deals with sending HTML for display in a Web browser, an application server provides access to business logic for use by client application programs. The application program can use this logic just as it would call a method on an object (or a function in the procedural world).
Such application server clients can include GUIs (graphical user interface) running on a PC, a Web server, or even other application servers. The information travelling back and forth between an application server and its client is not restricted to simple display markup. Instead, the information is program logic. Since the logic takes the form of data and method calls and not static HTML, the client can employ the exposed business logic however it wants.
In most cases, the server exposes this business logic through a component API, such as the EJB (Enterprise JavaBean) component model found on J2EE (Java 2 Platform, Enterprise Edition) application servers. Moreover, the application server manages its own resources. Such gate-keeping duties include security, transaction processing, resource pooling, and messaging. Like a Web server, an application server may also employ various scalability and fault-tolerance techniques.
Application servers:
Checkout: [ WebLogic Server Installation ]
Application Server: A server that exposes business logic to client applications through various protocols including HTTP.
Web Server: A server that handles HTTP protocol.
Application Server: To deliver various applications to another device, it allows everyone in the network to run software off of the same machine.
Web Server: Keeping HTML, PHP, ASP, etc files available for the web browsers to view when a user accesses the site on the web, handles HTTP requests from clients.
Application Server: GUI’s, Web Servers
Web Server: HTTP, HTML
Application Server: Adds functionality
Web Server: Does not add any
Application Server: Oracle OC4J(Oracle), Sybase Application server(Sybase), SAP Netweaver (SAP), JBoss (Red Hat), Weblogic server (Oracle), WebSphere (IBM)
Web Server: Microsoft IIS, Apache Tomcat
| Checkout Our Blog on Work Managers in WebLogic |
WebLogic Server J2EE applications are based on standardized, modular components. WebLogic Server provides a complete set of services for those modules and handles many details of application behavior automatically, without requiring programming.
J2EE includes deployment specifications for Web applications, EJB modules, Enterprise applications, client applications, and connectors. J2EE does not specify how an application is deployed on the target server—only how a standard module or application is packaged.
Java is platform-independent, so you can edit and compile code on any platform, and test your applications on development WebLogic Servers running on other platforms. For example, it is common to develop WebLogic Server applications on a PC running Windows or Linux, regardless of the platform where the application is ultimately deployed.
Weblogic Tutorial Summary:
Our course design of tutorials is practical and informative. At TekSlate, we offer resources to help you learn various IT courses. We avail of both written material and demo video tutorials. For in-depth knowledge and practical experience explore Online WebLogic Training.
17:T4ff2,
At the end of this chapter you will be able to:
Examples:
In this chapter we discussed:
This Installation Guide describes how to use the WebLogic installation program on Windows and UNIX platforms. This document is intended for system administrators who are installing the WebLogic software.
The installation program can be used in the following modes:
It is an interactive, GUI-based method for installing software. It can be run on both Windows and UNIX systems.
Note: If you want to run the installation program in graphical mode, the console attached to the machine on which you are installing the software must support a Java-based GUI.
It is an interactive, text-based method for installing your software from the command line, on either a UNIX system or a Windows system.
Silent-mode installation is a non-interactive method of installing your software that requires the use of an XML property file for selecting installation options. You can run the silent mode installation from either a script or from the command line. Silent-mode installation is a way of setting installation configurations only once and then using those configurations to duplicate the installation on many machines.
The installable product components vary depending on the installer that you are using.
1) WebLogic Server
2) WebLogic Workshop
3) WebLogic Portal
4) Oracle Service Bus
| Want to acquire industry skills and gain complete knowledge of WebLogic? Enrol in Instructor-Led live WebLogic Training to get Job Ready! |
This type downloads a small setup file that enables you to select the components that you want to install on your system. The installer then downloads only the components you select. The Net installer eliminates the need to download the entire product before installing it and thereby reduces the time needed to complete the download, the disk space, and also the RAM required by the WebLogic Server.
This type downloads a standalone version of the installation program. The WebLogic Server installation program contains WebLogic Server and related samples, Workshop, and related samples as described in Installable Product Components, and the JRockit SDK and Sun JDK (for Windows and Linux platforms only).
Note: If you are planning to install the software in silent mode, you must download the package installer. Silent-mode installation is not supported by the net installer.
This type of installer is a .jar file. It is the same as the package and net installers, except that it does not include JDKs. You can use this type of installer to install the product on UNIX machines on which Java is already installed.
The following sections describe the installation prerequisites:
1. System Requirements:
| Platform configuration | Supported configuration of hardware, operating system, JDK, and DB specific to the product you are installing. |
| Processor | 1-GHz CPU |
| Hard disk drive | Installation requires approximately 3.5 GB of disk space. |
| Memory | Minimum of 1 GB RAM and recommends 2 GB of RAM. |
| JDK | The Products installation program requires a Java run-time environment (JRE) to run. A JRE is bundled in the Windows installation program and in some UNIX installation programs (those with filenames ending in .bin). For other UNIX platforms, the installation program does not install a JDK. Filenames for these installation programs end in .jar. To run the .jar installation programs, you must have the appropriate version of the JDK installed on your system, and include the bin directory of the JDK at the beginning of the PATH variable definition. |
2. Temporary Disk Space Requirements:
The installation program uses a temporary directory into which it extracts the files necessary to install the software on the target system. During the installation process, your temporary directory must contain sufficient space to accommodate the compressed Java Run-time Environment (JRE) bundled with the installation program and an uncompressed copy of the JRE that is expanded into the temporary directory.
Windows platforms: directory referenced by the TMP system variable
Ex: C: WINDOWSTemp
UNIX Platforms: system-dependent temporary directory
Ex: /tmp
3. Administrator Privileges:
When you are installing the software as a user with Administrator privileges, you are presented with the option to create the Start menu shortcuts in the All Users folder, or in the Local User’s Start menu folder. The following options are available...
All Users: All users registered on the machine are provided with access to the installed software. Subsequently, if users without Administrator privileges use the Configuration Wizard from this installation to create domains, the Start menu shortcuts to the domains are not created. In this case, users can manually create shortcuts in their local Start menu folders, if desired.
Local user: Other users registered on this machine will not have access to the Start menu entries for this installation.
4. Installation Considerations:
If the home directory is not empty and it does not contain registry.xml, or if any of the product installation directories are not empty, the following messages will be displayed:
| Checkout Our Blog on WebLogic Tutorial |
The following sections describe how to start the installation program on a Windows platform. The name of the installation program for the WebLogic Server package installer is server923_win32.exe
1. Starting Graphical Mode Installation:
Double-click on the installer file
2. Starting Console Mode Installation:
server923_win32.exe -mode=console -log=C:logsserver_install.log
Note: You can include the -log=full_path_to_log_file option in the command line to create a verbose installation log.
3. Starting Silent Mode Installation:
Note: Incorrect entries in the silent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation.
Ex : server923_win32.exe -mode=silent -silent_xml=C:silent.xml
-log=C:logsserver_install.log
The following sections describe how to start the installation program on a UNIX Platform.
Using Installers with Filenames Ending in .bin:
1. Starting Graphical-Mode Installation:
chmod a+x <filename.bin> ./<filename.bin>
In these commands, filename.bin is the name of your installation program. For example, for WebLogic Server, the file name is server923_solaris32.bin.
Note: You can include the log file option in the command line to create a verbose installation log.
For example: chmod a+x server923_solaris32.bin ./server923_solaris32.bin -log=/home/logs/install.log
2. Starting Console-Mode Installation:
chmod a+x <filename.bin> ./<filename.bin> -mode=console
For example: chmod a+x server923_solaris32.bin ./server923_solaris32.bin -mode=console -log=/home/logs/install.log
3. Starting Silent-Mode Installation:
For example: chmod a+x filename.bin ./<filename.bin> -mode=silent -silent_xml=/<path_to_silent.xml>
Here, filename.bin is the name of the installation file (for example, for WebLogic Server: server923_solaris32.bin), and path_to_silent.xml is the full pathname of the silent.xml template file. For example, for WebLogic Server, enter:
chmod a+x server923_solaris32.bin ./server923_solaris32.bin -mode=silent -silent_xml=/home/silent.xml -log=/home/logs/install.log
| Read this latest WebLogic Interview Questions that help you grab high-paying jobs |
1. Starting Graphical-Mode Installation:
a) Add the bin directory of the appropriate JDK to the beginning of the PATH variable definition on the target system. Here JAVA_HOME represents the full path to the JDK directory.
Ex: PATH=$JAVA_HOME/bin:$PATH
export PATH
b) Go to the directory where you downloaded the installation program.
c) Launch the installation program by entering the following command:
java -jar net_server<version>_generic.jar
Note: You can include the -log=full_path_to_log_file option in the command line to create a verbose installation log.
Ex: server<version>_generic.jar -log=/home/logs/install.log
2. Starting Console-Mode Installation:
a) Add the bin directory of the appropriate JDK to the beginning of the PATH variable definition on the target system. Here, JAVA_HOME represents the full path to the JDK directory.
Ex: PATH=JAVA_HOME/bin:$PATH
export PATH
b) Go to the directory where you downloaded the installation program.
c). Launch the installation by entering the following command:
java -jar <filename.jar> -mode=console
Here, filename.jar is the name of the Products installation file, for example,
net_server<version>_generic.jar.
Ex: java -jar server<version>_generic.jar -mode=console
-log=/home/logs/install.log
3. Starting Silent-Mode Installation:
a) Create a silent.xml file that defines the configuration settings normally entered by a user during an interactive installation process, such as graphical mode or console-mode installation. For information about creating a silent.xml file, see Creating a silent.xml File for Silent-Mode Installation.
b) Add the bin directory of the appropriate JDK to the beginning of the PATH variable definition on the target system.
EX: PATH=JAVA_HOME/bin:$PATH
export PATH
Here, JAVA_HOME is the full path of the JDK directory.
c) Go to the directory that contains the installation file.
d) Launch the installation by entering the following command:
java -jar <filename.jar> -mode=silent -silent_xml=/path_to_silent.xml
Here, filename.jar is the name of the Products installation file (for example, server<version>_generic.jar, where, path_to_silent.xml is the full path silent.xml file.
Ex: server<version>_generic.jar -mode=silent -silent_xml=/home/silent.xml -log=/home/logs/install.log
1) Double-click on the installer file
2) Welcome: Click Next to proceed with the installation. You may cancel the installation at any time by clicking Exit.
3) Choose BEA Home Directory: Specify the home directory that will serve as the central support directory for all products installed on the target system 
4) Choose Install Type: Select one of the following installation types:
Complete— All the software components included in your installation program, are installed on your system.
Custom— You can select the software components to be installed.
5) Choose Products and Components: Specify the components to be installed by selecting or clearing the appropriate checkboxes. This window displays a tree-view of all the components available for installation.
6) Choose Product Installation Directories: Specify the directories in which you want to install the products, and click Next. 
7) Windows service: Choose whether you want to install the Windows services indicated, specifically the WebLogic Server Node Manager Service. Node Manager is used to monitor, start, and stop server instances in a domain. If you select Yes, enter the Node Manager Listen Port in the appropriate field. The default is 5556 
8) Choose Shortcut Location: Specify the Start menu folder in which you want the Start menu shortcuts created All Users Start menu folder & Local User’s Start menu folder 
9) Installation Complete
To complete the console-mode installation process, respond to the prompts in each section by entering the number associated with your choice or by pressing Enter to accept the default. To exit the installation process, enter exit (or x, for short) in response to any prompt. To review or change your selection, enter previous (or p, for short) at the prompt. To proceed to the following window, enter next (or n, for short).
Note: In the sample console text and directory pathnames provided in this section, Windows conventions (such as backslashes in pathnames) are used, for example, C:beawlserver_<version>. When entering pathnames on a UNIX system, be sure to use UNIX conventions, instead. For example, use forward slashes in pathnames, such as /home/bea/wlserver_<version>.
To choose a complete installation, type 1 or press Enter – To choose a Custom installation, type 2. The Choose Products and Components to Install prompt is displayed.
Note: The installer displays the estimated size of the installation for the selected Components.
Do one of the following:
Enter 1 to install a node manager as a Windows service.
Enter 2 if you do not want to install Node Manager as a Windows service.
Specify the folder in which you want to create the Start menu shortcuts.
Do one of the following:
Type 1 or press Enter to create Start menu shortcuts in the All Users folder.
Type 2 to create shortcuts in your local user’s Start menu folder.
Press Enter to continue. The installation program begins by copying the components you specified to your system.
Note: QuickStart is not started automatically for console-mode or silent-mode installations. You can launch QuickStart from the Start Menu (Windows) or from the command line (Windows and UNIX).
Main Steps Important Considerations for Silent-Mode Installation
When you are running the installation program in silent mode, keep in mind the following considerations:
a) We must use the package installer for silent mode installation. Silent-mode installation is not supported by the net installer.
b) Silent-mode installation requires the same amount of temporary disk space and uses the same temporary storage directories as a standard installation. The installation program does not alert you if there is not enough space in the temporary directory.
c) A silent mode installation takes the same amount of time as a standard installation. At the beginning of a silent-mode installation, an initial installation program window or message is displayed briefly, indicating that the installation has started. No messages are displayed to indicate that the installation is in progress or has been completed successfully.
d) Incorrect entries in the silent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation.
e) The XML definition (<?xml version="1.0" encoding="UTF-8"?>) must be at the very beginning of the silent.xml file. Do not enter a space or line breaks before the XML definition.
f) You cannot reinstall any WebLogic product on top of a previously installed version of the same product—in the same home directory or in the same file location. You can, however, add products and product components to an existing installation.
The silent-mode installation process has two primary steps:
BEAHOME - The full path for the home directory of your choice.
WLS_INSTALL_DIR - The full path for the directory where you want to install WebLogic Server Ex - C:bea_HOMEwlserver_9.2
COMPONENT_PATHS Specify the components and subcomponents you want to install on your system.
For Example: To install WebLogic Server, use the following values:
WebLogic Server/Core Application Server
|WebLogic Server/Administration Console
|WebLogic Server/Configuration Wizard and Upgrade Framework
|WebLogic Server/Web 2.0 HTTP Pub-Sub Server
|WebLogic Server/WebLogic JDBC Drivers
|WebLogic Server/Third-Party JDBC Drivers
|WebLogic Server/WebLogic Server Clients
|WebLogic Server/WebLogic Web Server Plugins
|WebLogic Server/UDDI and Xquery Support
|WebLogic Server/Server Examples
INSTALL_NODE_MANAGER_SERVICE (Windows platforms only)
NODEMGR_PORT The Node Manager listen port.
Note: The INSTALL_NODE_MANAGER_SERVICE option must be set to yes.
INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER
Using QuickStart
When the product installation is completed using graphical-mode installation, the QuickStart application is launched automatically, by default. If you do not want to run QuickStart at the completion of the installation process, you can clear the Run QuickStart checkbox in the Install Complete window.
QuickStart is not invoked for console mode or silent-mode installations. QuickStart is designed to help first-time users evaluate, learn, and use Product software.
For example, the QuickStart application for WebLogic Server provides quick access to the following:
After installation, you can launch QuickStart as follows:
On Window systems, choose Start > Programs > Bea Product > QuickStart
On UNIX systems, perform the following steps:
For example cd /home/bea/wlserver_<version>/common/bin
Post Installation: BEA Directory
WebLogic Directory Structure:
JVM Run-Time Arguments
java options FullyQualifiedJavaClass ProgramOptions
Some virtual machine options:
To run WLS, you must configure:
These parameters can be set:
Configuring Your CLASSPATH
The WLS CLASSPATH is completely configured by the Java system CLASSPATH environment variable
Files that must be in the CLASSPATH:
Files that can be in the CLASSPATH:
Setting Environment Variables:
In this section, we discussed:
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. It manages system-level details so you can concentrate on business logic and presentation.
The following are the various Weblogic Server versions released from 2002. The most recent version of Weblogic is 12c.
WebLogic Server 12c Release 3 (12.1.3) - June 26, 2014
WebLogic Server 12c Release 2 (12.1.2) - July 11, 2013
WebLogic Server 12c Release 1 (12.1.1) - Dec 1, 2011
WebLogic Server 11gR1 PS5 (10.3.6) - February 26, 2012
WebLogic Server 11gR1 PS4 (10.3.5) - May 16, 2011
WebLogic Server 11gR1 PS3 (10.3.4) - January 15, 2011
WebLogic Server 11gR1 PS2 (10.3.3) - April 2010
WebLogic Server 11gR1 PS1 (10.3.2) - Nov 2009
WebLogic Server 11g (10.3.1) - Jul 2009
WebLogic Server 10.3 - Aug 2008
WebLogic Server 10.0 - Mar 2007
WebLogic Server 9.2
WebLogic Server 9.1
WebLogic Server 9.0 - Nov 2006
WebLogic Server 8.1 - Jul 2003
WebLogic Server 7.0 - Jun 2002
[button url="http://tekslate.com/weblogic-server-administration-training/" class="other" bg="" hover_bg="" size="0px" color="#f7f7f7" radius="0px" width="0px" height="0px" target="_self"] Oracle Weblogic Training [/button]
Oracle WebLogic Server supports Oracle, DB2, MS SQL Server, MySQL Enterprise and other JDBC-compliant databases. Oracle Weblogic Platform also includes:
The table below lists major standards supported by the WebLogic Server product version.
| Standard | WLS 7.0 | WLS 8.1 | WLS 9.0 | WLS 10.0 | WLS 10.3 |
| Java | 1.3 | 1.4 | 5 | 5 | 6 |
| Java EE | 1.3 | 1.3 | 1.4 | 5 | 5 |
System administration of WebLogic Server includes a wide range of tasks: 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. (A WebLogic Server domain is a collection of WebLogic Server services designed for a specific purpose. For example, you might create one domain to provide an employee portal and another domain to provide business services to your customers.)
Because 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. Also, WebLogic Server includes several of its own standards-based, extensible utilities. Alternatively, you can use APIs to create custom management utilities.
At the end of this module you will be able to:
The software components of a multitier architecture consist of three tiers:
[button url="http://tekslate.com/tutorials/weblogic-tutorials-how-to/" class="other" bg="" hover_bg="" size="0px" color="#f7f7f7" radius="0px" width="0px" height="0px" target="_self"] Oracle Weblogic Tutorials [/button]
A Web server handles the HTTP protocol. When the Web server receives an HTTP request, it responds with an HTTP response, such as sending back an HTML page. To process a request, a Web server may respond with a static HTML page or image, send a redirect, or delegate the dynamic response generation to some other program such as CGI scripts, JSPs (JavaServer Pages), servlets, ASPs (Active Server Pages), server-side JavaScripts, or some other server-side technology. Whatever their purpose, such server-side programs generate a response, most often in HTML, for viewing in a Web browser.
Understand that a Web server's delegation model is fairly simple. When a request comes into the Web server, the Web server simply passes the request to the program best able to handle it. The Web server doesn't provide any functionality beyond simply providing an environment in which the server-side program can execute and pass back the generated responses. The server-side program usually provides for itself such functions as transaction processing, database connectivity, and messaging.
While a Web server may not itself support transactions or database connection pooling, it may employ various strategies for fault tolerance and scalability such as load balancing, caching, and clustering—features often erroneously assigned as features reserved only for application servers.
Proxy some requests to Application Servers
As for the application server, according to our definition, an application server exposes business logic to client applications through various protocols, possibly including HTTP. While a Web server mainly deals with sending HTML for display in a Web browser, an application server provides access to business logic for use by client application programs. The application program can use this logic just as it would call a method on an object (or a function in the procedural world).
Such application server clients can include GUIs (graphical user interface) running on a PC, a Web server, or even other application servers. The information traveling back and forth between an application server and its client is not restricted to simple display markup. Instead, the information is program logic. Since the logic takes the form of data and method calls and not static HTML, the client can employ the exposed business logic however it wants.
In most cases, the server exposes this business logic through a component API, such as the EJB (Enterprise JavaBean) component model found on J2EE (Java 2 Platform, Enterprise Edition) application servers. Moreover, the application server manages its own resources. Such gate-keeping duties include security, transaction processing, resource pooling, and messaging. As a Web server, an application server may also employ various scalability and fault-tolerance techniques.
Application Server: A server that exposes business logic to client applications through various protocols including HTTP.
Web Server: A server that handles HTTP protocol.
Application Server: To deliver various applications to another device, it allows everyone in the network to run software off of the same machine.
Web Server: Keeping HTML, PHP, ASP, etc. files available for the web browsers to view when a user accesses the site on the web, handles HTTP requests from clients.
Application Server: GUI’s, Web Servers
Web Server: HTTP, HTML
Application Server: Adds functionality
Web Server: Does not add any
Application Server: Oracle OC4J(Oracle), Sybase Application server(Sybase), SAP Netweaver (SAP), Jboss (Red Hat), WebLogic Server (Oracle), WebSphere (IBM)
Web Server: Microsoft IIS, Apache Tomcat
WebLogic Server J2EE applications are based on standardized, modular components. WebLogic Server provides a complete set of services for those modules and handles many details of application behavior automatically, without requiring programming.
J2EE includes deployment specifications for Web applications, EJB modules, Enterprise applications, client applications, and connectors. J2EE does not specify how an application is deployed on the target server—only how a standard module or application is packaged.
Java is platform independent, so you can edit and compile code on any platform, and test your applications on development WebLogic Servers running on other platforms. For example, it is common to develop WebLogic Server applications on a PC running Windows or Linux, regardless of the platform where the application is ultimately deployed.
In this tutorial, we will see how to do Session replication in Weblogic Cluster You now need to use the node1 and node2 created before In session-test.war/WEB-INF/web.xml, add:
<web-app>
<display-name>Session Test</display-name>
<description>...</description>
<distributable/> <!-- -->
...
</web-app>
| Your application’s HTTP sessions now use the distributed cache. |
Now:
You can configure session replication here:
Inclined to build a profession as JBoss Developer? Then here is the blog post on, explore JBoss Training
Replication trigger: SET, SET_AND_GET, SET_AND_NON_PRIMITIVE_GET, ACCESS
Replication granularity: SESSION, ATTRIBUTE, FIELD
deploy/cluster/jboss-cache-manager.sar/META-INF/jboss-cache-manager-jboss-beans.xml:
<deployment ...>
...
<bean name="CacheConfigurationRegistry" ...>
...
<property name="newConfigurations">
<map keyClass="java.lang.String" valueClass="org.jboss.cache.config.Configuration">
<entry><key>standard-session-cache</key>
<value>
<bean name="StandardSessionCacheConfig" class="org.jboss.cache.config.Configuration">
...
<property name="clusterName">${jboss.partition.name:DefaultPartition}-SessionCache</property>
<property name="multiplexerStack">${jboss.default.jgroups.stack:udp}</property>
<property name="fetchInMemoryState">true</property>
<property name="nodeLockingScheme">PESSIMISTIC</property>
<property name="isolationLevel">REPEATABLE_READ</property>
<property name="useLockStriping">false</property>
<property name="cacheMode">REPL_ASYNC</property>
<property name="syncReplTimeout">17500</property>
<property name="lockAcquisitionTimeout">15000</property>
...
</bean>
</value>
</entry>
...
</map>
</property>
...
</bean>
...
</deployment>
You can also specify for each application some parameters: WEB-INF/jboss-web.xml:
<jboss-web>
<replication-config>
<replication-trigger>SET_AND_NON_PRIMITIVE_GET</replication-trigger>
<replication-granularity>SESSION</replication-granularity>
</replication-config>
</jboss-web>
1c:T4def,Preparing for an interview about managing Java applications at the enterprise level? You may face questions about the WebLogic Server, a widely used Java application server. To impress your interviewer and get the job, prepare by mastering WebLogic Architecture, features, and configuration settings. This guide provides expert tips and common interview questions.
In this article, we will cover the following:
Most Frequently Asked WebLogic Interview Questions |
Ans:
Ans:
Ans:
Ans: We can use Java WebLogic. Admin PING to check if we get a normal response. We need to take multiple thread dumps with kill -3 paid on Unix and CTLR Break on Windows. Analyze the thread dump to find the root cause.
Ans: Memory leak, database query taking a long time to return, Deadlock.
Ans: A memory leak is when objects are not removed from the heap even when they are not required.
| Inclined to build a profession as Weblogic Developer? Then here is the blog post on, explore Weblogic Training |
Ans:
Q8) How to troubleshoot and overcome such issues?
Ans:
Ans: It occurs when one process or one thread utilizes an unexpectedly high proportion of CPU.
Ans: In the Solaris environment, we need to take pstack and prstack and see what the threads are doing. In Windows, we need to use pslist and process explorer.
Ans:
Ans: Members of the Cluster communicate over the Cluster Multicast IP and Port by sending periodic heartbeat messages.
Ans:
Tuning JVM Parameters:
If you have a single processor, a single-thread machine then you should use the serial collector (default for some configurations, can be enabled explicitly for with -XX:+UseSerialGC). For multiprocessor machines where your workload is basically CPU bound, use the parallel collector. This is enabled by default if you use the -server flag, or you can enable it explicitly with -XX:+UseParallelGC. If you’d rather keep the GC pauses shorter at the expense of using more total CPU time for GC, and you have more than one CPU, you can use the concurrent collector (-XX:+UseConcMarkSweepGC). Note that the concurrent collector tends to require more RAM allocated to the JVM than the serial or parallel collectors for a given workload because some memory fragmentation can occur.
| Checkout Our Blog on WebLogic Tutorial |
Ans: It can be categorized into 4 parts. a. Application Tuning. jsp precompilation, ejb pool size cache...
Setting the TCP IP parameter. tcp_time_wait_interval tcp_conn_req_max_q
tune work manager, tune chuck size and chunk pool size, using performance packs, connection backlog buffering.
tuning gc strategy, monitoring garbage collection.
Ans:
Development Mode:
Production Mode:
Ans:
Ans:
Note: All of these protocols are, by default, multiplexed over the same connection to the server’s address and port. So you can access a web page hosted by the server using a URL such as http://host:port/page.jsp. An external client can set up an initial JNDI context to a server using the URL t3://host: port/. All that has changed is the protocol over which the client must communicate with the server.
1d:T8134,Ans:
Ans: Modules and applications have deployment descriptors—XML documents—that describe the contents of the directory or JAR file. Deployment descriptors are text documents formatted with XML tags. The J2EE specifications define standard, portable deployment descriptors for J2EE modules and applications.
Ans: Sun Hotspot JDK default for Development installation, JRockit is for Production mode for WebLogic 11g and 12c. The operating environment also factors to select the Certified JDK JVM. If you want to change you need to specify it.
Ans:
Ans: There are two modes: Development and production mode:
Development mode:
You use development mode while you are developing your applications. Development mode uses a relaxed security configuration and enables you to auto-deploy applications.
You can use the demonstration digital certificates provided by the WebLogic Server security services. With these certificates, you can design your application to work within environments secured by SSL.
WebLogic Server instances can automatically deploy and update applications that reside in the domain_name/applications directory.
When you start a server, the server automatically renames (rotates) its local server log file as server-name.log.n. For the remainder of the server session, the server rotates its local log file whenever the size of the file reaches 500 kilobytes.
The default number of threads available to Execute Queues is 15.
The default capacity is 15 JDBC connections.
Production mode:
You use production mode when your application is running in its final form. A production domain uses full security and may use clusters or other advanced features.
A warning message is displayed if you use the demonstration digital certificates.
The auto-deployment feature is disabled, so you must use the WebLogic Server Administration Console or the Weblogic. Deployer tool.
A server rotates its local log file after the size of the file reaches 500 kilobytes.
The default number of threads available to Execute Queues is 25.
The default capacity is 25 JDBC connections.
Ans:
Ans:
Ans:
Ans: The stub removes the instance that is failed from its list when a failure occurs. The stub uses DNS again for finding a running server and obtains a current list of instances when there are no servers left in its list. The list of available server instances in the cluster will get periodical refreshment, which allows taking advantage of new servers. This is because; the servers are added to the cluster.
Ans: Though the functionality of these two products is closer, there are minor differences in the standards that support it. These differences are:
Ans: WebSphere refers to a brand for IBM software products. It is designed for setting up, operation, and integration of electronic business applications. These applications could perform well in a cross-platform environment. These sets of software are Java-based web technologies.
Ans:
Ans: JDBC code may throw the following exception:
| Inclined to build a profession as Oracle WebLogic Developer? Then here is the blog post on, explore Oracle WebLogic Training |
Ans: For instance, I am deploying an EJB and a resource adapter (.rar), the EJB has no dependencies on the .rar because the EJB is writing to the common client interface (CCI). The EJB client application has sends/marshals as parameter classes that are defined in the .rar. For some reason, the EJB's classloader hierarchy cannot find the definition of this .rar-specific class, even though the .rar is deploying successfully. I receive the following error on the EJB client:
java.rmi.UnmarshalException: error unmarshalling arguments; nested
exception
is:
java. lang.ClassNotFoundException:
com. my company.InteractionSpecImpl
When you pass an instance of com. my client company.server.eai.InteractionSpecImpl as an argument to your EJB, the app server needs to de-serialize (unmarshal) the object under the EJB context, and it needs the required class for unmarshalling, inside the ejb-jar(raTester.jar). So, if you include the interactionspecimpl class in your ejb-jar file, then you do not need to include those classes in your server's classpath.
Ans: WebLogic jDriver for Oracle always returns a Java object that preserves the precision of the data retrieved. WebLogic jDriver for Oracle returns the following from the getObject() method:
Ans:
Ans:
Ans: WebSphere applications use the following kinds of technologies:
Ans:
Ans: WebSphere Extended Deployment delivers enhanced Qualities of Service with features for optimizing IT resources.
The suite comprises 3 products:
WebSphere Virtual Enterprise:
It increases flexibility and agility to ensure business process integrity, improve service, and application performance, and better manage health.
It provides application infrastructure virtualization capabilities that lower the costs required to create, manage, and run enterprise applications and an SOA environment.
WebSphere eXtreme Scale:
It is an essential IBM software technology for conducting extreme transaction processing.
It allows business applications to process exceptionally large volumes of transactions with extreme efficiency and linear scalability.
It provides transactional integrity and transparent failover to ensure high availability, high reliability, and constant response times.
It operates as an in-memory data grid that dynamically caches, partitions, replicates, and manages application data and business logic across multiple servers.
Compute Grid:
Enables the scheduling, execution, and monitoring of batch-type jobs with enhanced service policy and workload management
Ans:
Ans:
Ans:
Ans:
Ans:
Ans: The following is an example to run a Java application using ANT:
<target name=”run” depends=”some.target”,some.other.target”>
<java classname=”${run.class}” fork=”yes”>
<classpath>
<path refrid = “classpath” />
</classpath>
<jvmarg line=”${debug.jvmargs}”/>
<jvmarg line=”${my.jvmargs}”/> < BR>
<jvmargvalue=”-dname=${name}” style="padding: 0px; margin: 0px; color: rgb(0, 0, 0); font-family: Helvetica, "Open Sans", Arial, sans-serif, Verdana; font-size: 15px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><jvmarg line=”${run.jvmargs}”/>
<arg line=”${run.args}”/>
</java>
</target>
Ans:
Ans:
Ans:
Ans:
Ans:
Ans:
Looking for a job managing Java applications at the enterprise level? Be ready to impress your interviewer by mastering WebLogic Server, a widely used Java application server. With its ability to handle large applications, WebLogic has become a go-to choice for many enterprises. To help you prepare for your interview, we've put together an expert guide featuring common WebLogic Interview Questions and tips for answering them. Whether you're a seasoned WebLogic pro or new to the field, this guide can help you stand out from the competition and secure your dream job.
In this article, we will cover the following:
Ans: Weblogic server is basically a software application working on the middle tier, integrating the back-end database, related applications and browser-based clients. A Weblogic server is an instance of a Java process and executes in a JVM. It supports all major JDBC-compliant databases like Microsoft SQL Server, Oracle etc. There can be two types of Weblogic servers:
Ans: A WebLogic server primarily comprises the following:
Ans: Deployment descriptors are XML documents that are used in describing the contents of a jar file or a directory. These can be found in most of the modules and applications. The standard and deployment descriptors are defined by the J2EE applications and modules.
Ans: Admin server in WebLogic serves as the central point of control that allows you to gain access to the configuration, monitoring and management of all resources. It is one of the instances of the WebLogic server that allows and maintains the data configuration of a given domain. It is a singleton service and every domain has at least 1 admin server.
Ans: Web.xml is an XML document that finds its applicability in the listing out of J2EE components and is primarily used for application purposes. It also helps in the configuration of applications in the J2EE module format.
Ans: A logically related group of WebLogic server resources like Oracle and collectively managed as a single unit is called a domain. These can be used to logically separate organizational divisions, tests, production and development applications. Domains serve as a single administration point.
| Want to acquire industry skills and gain complete knowledge of WebLogic? Enrol in Instructor-Led live WebLogic Training to get Job Ready! |
Ans: Stage deployment refers to the process wherein the admin receives a physical copy that has been distributed among other instances.
Ans: A managed server is another instance of your WebLogic server that runs on the JVM and has a self-managed specific configuration. A managed server is used to deploy the components of Java-like EJB applications, Web applications, JMS applications and other related web services. A domain may or may not have a managed server and the count can go up to N number of managed servers. Until and unless the servers are in a cluster, a managed server always operates independently.
Ans: The basic point of relation between the admin server and the managed server is that the admin server acts as a master manager for all the other servers including a managed server. To initiate the managed server start-up configuration, the admin server must be running. This is only a one-time process. Every managed server has a local copy of the configuration stored in it. Whenever there is an unavailability of the admin server, the managed server uses its local copy to boot. However, the managed server needs an admin server to synchronize its configurations over subsequent reboots.
Ans: BSU stands for BEA Smart update which is a java based application used to apply patches on Weblogic servers. This utility allows you to work both online and offline.
Ans: Any physical computer that is present or hosts instances in the WebLogic environment is called a machine. It is logically represented in a WebLogic server.
Ans: In case of the absence of an admin server, the managed server can start up by fetching the configuration files and other related files. However, the managed server is bound to work on the retrieved information and no alterations are possible. Alterations can only be done as and when the admin server is actually available. The managed server can carry out its operation in the independent mode until the availability of the admin server.
Ans: SSL stands for Secure Sockets Layer which is a security protocol enabling secure transfer of data and information in an encrypted format. Standard certificate authorities provide SSL certification to ensure the authentication of the secure transfer of the data at the transport level.
Ans: Yes, there are multiple ways to start and stop a WebLogic server.
Following are the ways to start and stop the admin server:
Following are the ways to start and stop a managed server:
Ans: The T3 protocol in a WebLogic server is used to establish a connection between the internal and external servers. It is also used in the implementation of RMI in a WebLogic server.
HTTP is a protocol that is used for establishing communication between the web server and the browser. It is authenticated by the World Wide Web Consortium, W3C.
Ans: This can be dealt with by using Java WebLogic.Admin PING and see if there is a normal response. Several thread dumps need to be checked with a kill-3 pid on Unix and CTRL Break on Windows. This step needs to be analyzed deeply to narrow down the root cause.
Ans: A node manager is a controlling program that is used to manage and control the WebLogic server instances. It allows you to control all server instances that may be running on single or multiple physical machines. To be able to communicate with a node manager, every machine must be configured with your node manager.
| Checkout our Blog on Weblogic Tutorial |
Ans: There are three different application layers in a WebLogic server:
Ans: Multicasting refers to establishing a peer to peer communication to initiate the process of messaging communications between different IP sockets.
Ans: There are 7 different networking protocols deployed in a WebLogic server. These are:
Ans: A WebLogic Server can be installed in three different modes:
1. Silent mode: uses configuration files, there is no manual intervention during the installation
2. Graphical mode: GUI interaction with the user during installation
3. Console mode: Command-based interactive mode of installation
Ans: JVM tuning refers to the enhancement and improvisation in the performance of a JVM execution engine in the WebLogic server. This is done by changing, adding or removing a few parameters in the WebLogic server like garbage collection or heap size, etc.
Ans: The various capabilities of a WebLogic server are:
Ans: Yes, we can change the default JVM in Weblogic servers. It can be done as follows:
Ans: A classpath in Windows can be set using the following script WL_HOMEserverbinsetWLSEnv.cmd
Ans: A pooling in the Tomcat server can be created by:
Ans: Yes, it is different. When a server crash happens, the Java process does not exist whereas in server hang the Java process stops responding.
Ans: A server hang generally happens due to a memory leak, deadlock, longer than anticipated return time in a database query
Ans: A memory leak is a condition in which the objects are retained in the heap even after they are no longer required.
Ans: MSI mode can be enabled or disabled by ensuring that the managed server’s root directory has the configuration subdirectory available. The following command can be used: Environment > Servers > Server_Name > Tuning > Advanced > Managed Server Independence Enabled checkbox
| Checkout Our Blog on WebLogic Server Installation |
Ans: The default port for configuring the WebLogic server is port 7001.
Ans: DB or JDBC connection pools can be configured when the WebLogic server is started. The application you are running ideally borrows a connection from the existing database pool and returns it back to the pool by closing it.
Ans: The basic difference between WebLogic and WebSphere lies in the standards used in their functionality. While a WebLogic server focuses primarily on the ease of use of J2EE and emerging standards governing them, the WebSphere is more focused on connectivity, web services, and integration.
Websphere is better in terms of transaction management and integration and strictly follows J2EE architecture.
Ans: The WebLogic server failure can be dealt with in the following ways:
Ans: The switch from development mode to production mode can be done as follows:
Go to the $root_domain/bin folder and edit the setDomainEnv.cmd.
Set PRODUCTION_MODE = false; save and exit to restart in production mode.
Ans: A WebSphere supports:
Ans: The following syntax can be used to call such procedures:
CallableStatement cstmt = conn.prepare all(“Begin to proclaim;
END;”);
cstmt.execute();
Ans: Go to WebLogic console >> left navigation tree >> Environment >> servers >> click of any server >> click monitoring tab >> note the WebLogic version field.
Q39) What is meant by OS tuning?
Ans: OS tuning refers to the process of tuning your operating system with a WebLogic server by setting up TCP/IP parameters.
Ans: Multicast is essentially a broadcast UDP option that allows sending of packets or announcements over a specific multicast address to a given group listening to the announcement. The announcements are similar to getting broadcast updates on most social media platforms like Twitter.
Unicast is more personalized and refers to one to one option for sending a packet or message to a particular member and not the whole group. It can be compared with personal messaging apps.
Ans: The port number of a WebLogic server can be checked by using netstat-na|grep connected
Ans: No, there can be any number of WebLogic servers held inside a multi-processor machine.
Ans: The boot.properties file stores your credentials like user id and password
Q44) What are vertical and horizontal clustering?
Ans: There are 2 ways in which clustering can be done WebLogic server:
1. Vertical clustering: under this type, multiple Java applications are run on a single physical machine.
2. Horizontal clustering: under this type, multiple Java application servers are run over two or more than two physical machines. It accounts for higher reliability.
Ans: Every WebLogic server instance in a WebLogic domain sends regular heartbeats via multicast broadcasting to all other servers in the cluster which is indicative of its presence. If three consecutive heartbeats go missing, the other server instances drop the particular server instance whose heartbeat goes missing.
Ans: A broadcast message regarding the addition of a new server instance is sent to all existing users in case there is an addition. A server instance list is also maintained and regularly updated by the cluster-aware stubs.
Ans: The auto-deployment feature is a monitoring utility that checks the application folder in every 3 seconds to look for any potential changes in the existing applications and/or the addition of any new applications. If there is any such change, it auto-deploys these changes in the existing application dynamically. The same can be done by monitoring socket errors.
Ans: Managed servers communicate through the T3 protocol.
Ans: ANT is a task that helps you carry out a smooth configuration of other tasks and applications in a developed environment.
Ans: MSI stands for Managed Server Independence. Managed servers have the ability to launch and operate even in the absence of the admin server.
1f:T4322,We are going to discuss about:
This chapter describes how you use WebLogic Server logging services to monitor server, subsystem, and application events. It explains how you configure WebLogic Server to write messages to log files and listen for the log messages that WebLogic Server broadcasts. It also describes how to view log messages through the WebLogic Server Administration Console.
Using Logs
WebLogic Server subsystems use logging services to provide information about events such as the deployment of new applications or the failure of one or more subsystems. A server instance uses them to communicate its status and respond to specific events. For example, you can use WebLogic logging services to report error conditions or listen for log messages from a specific subsystem.
Server Log Files and Domain Log Files
Each WebLogic Server instance writes all messages from its subsystems and applications to a server log file that is located on the local host computer. By default, the server log file is located in the logs directory below the server instance root directory; for example, DOMAIN_NAME\servers\SERVER_NAME\logs\SERVER_NAME.log, where DOMAIN_NAME is the name of the directory in which you located the domain and SERVER_NAME is the name of the server.
In addition to writing messages to the server log file, each server instance forwards a subset of its messages to a domain-wide log file. By default, servers forward only messages of severity level NOTICE or higher. While you can modify the set of messages that are forwarded, servers can never forward messages of the DEBUG severity level.
The domain log file provides a central location from which to view the overall status of the domain. The domain log resides in the Administration Server logs directory. The default name and location for the domain log file is DOMAIN_NAME\servers\ADMIN_SERVER_NAME\logs\DOMAIN_NAME.log,
Where DOMAIN_NAME is the name of the directory in which you located the domain and ADMIN_SERVER_NAME is the name of the Administration Server.
Message Formats & Attributes
Log Message Format
When a WebLogic Server instance writes a message to the server log file, the first line of each message begins with #### followed by the message attributes. Each attribute is contained between angle brackets.
Here is an example of a message in the server log file:
####<Sept 22, 2004 10:46:51 AM EST> <Notice> <WebLogicServer> <MyComputer>
<examplesServer> <main> <<WLS Kernel>> <> <null> <1080575211904> <BEA-000360> <Server started in RUNNING mode>
In this example, the message attributes are: Locale-formatted Timestamp, Severity, Subsystem, Machine Name, Server Name, Thread ID, User ID, Transaction ID, Diagnostic Context ID, Raw Time Value, Message ID, and Message Text. (A subsequent section, “Message Attributes,” describes each attribute.)
Format of Output to Standard Out and Standard Error
When a WebLogic Server instance writes a message to standard out, the output does not include the #### prefix and does not include the Server Name, Machine Name, Thread ID, User ID, Transaction ID, Diagnostic Context ID, and Raw Time Value fields.
Here is an example of how the message from the previous section would be printed to standard out:
<Sept 22, 2004 10:51:10 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode
In this example, the message attributes are: Locale-formatted Timestamp, Severity, Subsystem, Message ID, and Message Text.
Message Attributes
The messages for all WebLogic Server instances contain a consistent set of attributes. In addition, if your application uses WebLogic logging services to generate messages, its messages will contain these attributes.
Message Severity & Messages Forwarded to Domain Log
The severity attribute of a WebLogic Server log message indicates the potential impact of the event or condition that the message reports.
Message Catalog
Message catalogs are available in HTML format on e-docs as part of the documentation deliverable. You can search for messages by error number using the search engine.
Configuring WebLogic Logging Services
Logging Configuration Tasks: Main Steps
The following steps summarize how you configure and filter log messages that WebLogic Server generates. Related documentation and later sections in this guide describe these steps in more detail.
Environment -> Servers -> Logging…
Filtering WebLogic Server Log Messages
WebLogic logging services provide several filtering options that give you the flexibility to determine which messages are written to WebLogic Server log files and standard out, and which are written to the log file and standard out that a client JVM maintains.
Create Log Filters
Step 1:
Domain -> Configuration -> Log Filters and then click on New
Step 2: Specify the Name of the Filter and click on Finish Button and Click on Activate Changes
Step 3: Specify the conditions according to the requirement and then apply save and Activate Changes.
Assigning a Log Filter to Server
Servers -> Select Server -> Logging -> Advanced and then apply the Filter according to the requirement.
Using the Console to Monitor
The Administration Console offers some monitoring capabilities:
Monitoring Running Servers
Monitoring Individual Servers
Server Status and Threads Monitoring
Check out our Related Courses Weblogic Tutorials Introduction to Clustering Weblogic Oracle Goldengate Training In Chicago Oracle Weblogic Server Installation
2:["$","$Lb",null,{"data":{"trending":[{"id":901,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":null,"table_of_content":null,"description":"$c","title":"Trouble Shooting in WebLogic","url_title":"trouble-shooting-weblogic","image_url":"","meta_title":"Trouble Shooting in WebLogic","meta_desc":"In this tutorial you will learn about trouble shooting in weblogic, common weblogic server deadlocks and how to avoid them.","views":0,"rating":4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"0","created_at":"2014-11-12T05:47:19.000Z","updated_at":"2020-10-15T18:59:28.000Z","status":1,"video_schema_name":null,"video_schema_upload_date":null,"video_schema_description":null,"faq_schema_q1":null,"faq_schema_a1":null,"faq_schema_q2":null,"faq_schema_a2":null,"faq_schema_q3":null,"faq_schema_a3":null,"like_counter":0},{"id":903,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":null,"table_of_content":null,"description":"$d","title":"Introduction to Clustering","url_title":"introduction-clustering-weblogic","image_url":"","meta_title":"Introduction to Weblogic Clustering","meta_desc":"In this tutorial you will learn about introduction to WebLogic clustering, benefits of clustering, cluster in networks and cluster communication.","views":498,"rating":4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"0","created_at":"2014-11-12T06:53:01.000Z","updated_at":"2020-10-15T18:37:06.000Z","status":1,"video_schema_name":null,"video_schema_upload_date":null,"video_schema_description":null,"faq_schema_q1":null,"faq_schema_a1":null,"faq_schema_q2":null,"faq_schema_a2":null,"faq_schema_q3":null,"faq_schema_a3":null,"like_counter":0},{"id":900,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":"","table_of_content":"","description":"$e","title":"Performance and Tuning","url_title":"weblogic-performance-tuning","image_url":"","meta_title":"Performance and Tuning in Weblogic","meta_desc":"In this tutorial you will learn about performance and tuning in weblog, and Setting Caching Size for Stateful Session and Entity Beans.","views":2754,"rating":4.2,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"192","created_at":"2014-11-12T05:41:07.000Z","updated_at":"2020-10-15T18:19:42.000Z","status":1,"video_schema_name":"","video_schema_upload_date":"","video_schema_description":"","faq_schema_q1":"","faq_schema_a1":"","faq_schema_q2":"","faq_schema_a2":"","faq_schema_q3":"","faq_schema_a3":"","like_counter":0},{"id":896,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":null,"table_of_content":null,"description":"$f","title":"Security","url_title":"weblogic-security","image_url":"","meta_title":"Security in Weblogic","meta_desc":"In this tutorial we will learn about security in weblogic, filtering network connections, connection filter and Consuming WLS Resources.","views":1070,"rating":4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"0","created_at":"2014-11-12T05:11:34.000Z","updated_at":"2020-10-15T11:31:18.000Z","status":1,"video_schema_name":null,"video_schema_upload_date":null,"video_schema_description":null,"faq_schema_q1":null,"faq_schema_a1":null,"faq_schema_q2":null,"faq_schema_a2":null,"faq_schema_q3":null,"faq_schema_a3":null,"like_counter":0},{"id":895,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":null,"table_of_content":null,"description":"$10","title":"Weblogic JMS (Java Message Service)","url_title":"jms-java-message-service-weblogic","image_url":"","meta_title":"Weblogic JMS (Java Message Service)","meta_desc":"In this tutorial you will learn about java messaging service, message-oriented middleware, monitoring JMS in WLS and monitoring destinations.","views":281,"rating":4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"0","created_at":"2014-11-11T12:58:16.000Z","updated_at":"2020-10-15T10:19:52.000Z","status":1,"video_schema_name":null,"video_schema_upload_date":null,"video_schema_description":null,"faq_schema_q1":null,"faq_schema_a1":null,"faq_schema_q2":null,"faq_schema_a2":null,"faq_schema_q3":null,"faq_schema_a3":null,"like_counter":0},{"id":893,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":null,"table_of_content":null,"description":"$11","title":"Work Managers in Weblogic","url_title":"work-managers-weblogic","image_url":"","meta_title":"Work Managers in Weblogic","meta_desc":"In this tutorial you will learn about using Work Managers, Request Classes, and Constraints. Also learn Migrating from Execute Queues to Work Managers.","views":114,"rating":4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"0","created_at":"2014-11-11T11:37:23.000Z","updated_at":"2020-10-14T19:01:07.000Z","status":1,"video_schema_name":null,"video_schema_upload_date":null,"video_schema_description":null,"faq_schema_q1":null,"faq_schema_a1":null,"faq_schema_q2":null,"faq_schema_a2":null,"faq_schema_q3":null,"faq_schema_a3":null,"like_counter":0},{"id":887,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":"","table_of_content":"","description":"$12","title":"Weblogic Node Manager Configuration","url_title":"weblogic-node-manager-configuration","image_url":"","meta_title":"Weblogic Node Manager Configuration","meta_desc":"This tutorial discusses on weblogic node manager configuration and configuring node manager on multiple machines in weblogic","views":2716,"rating":4.4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"192","created_at":"2014-11-11T08:50:40.000Z","updated_at":"2020-10-14T18:19:33.000Z","status":1,"video_schema_name":"","video_schema_upload_date":"","video_schema_description":"","faq_schema_q1":"","faq_schema_a1":"","faq_schema_q2":"","faq_schema_a2":"","faq_schema_q3":"","faq_schema_a3":"","like_counter":0},{"id":886,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":null,"table_of_content":null,"description":"$13","title":"Weblogic Node Manager Overview","url_title":"node-manager-overview-weblogic","image_url":"","meta_title":"Weblogic Node Manager Overview","meta_desc":"In this tutorial, you will learn about the Weblogic node manager overview and also discusses how the node manager restarts an administration server.","views":585,"rating":4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"0","created_at":"2014-11-11T07:33:19.000Z","updated_at":"2020-10-14T18:03:39.000Z","status":1,"video_schema_name":null,"video_schema_upload_date":null,"video_schema_description":null,"faq_schema_q1":null,"faq_schema_a1":null,"faq_schema_q2":null,"faq_schema_a2":null,"faq_schema_q3":null,"faq_schema_a3":null,"like_counter":1},{"id":879,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":null,"table_of_content":null,"description":"$14","title":"Configuring a WebLogic Server Environment","url_title":"configuring-weblogic-server-environment","image_url":"","meta_title":"Weblogic Server Environment","meta_desc":"In this tutorial, we will learn how to configure a webserver environment clearly explained step-by-step...Tekslate.","views":0,"rating":4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"0","created_at":"2014-11-11T05:46:22.000Z","updated_at":"2020-10-14T17:38:31.000Z","status":1,"video_schema_name":null,"video_schema_upload_date":null,"video_schema_description":null,"faq_schema_q1":null,"faq_schema_a1":null,"faq_schema_q2":null,"faq_schema_a2":null,"faq_schema_q3":null,"faq_schema_a3":null,"like_counter":0},{"id":11,"blog_category":159,"blog_type":1,"wp_id":1,"excerpt":"","table_of_content":"$15","description":"$16","title":"WebLogic Tutorial","url_title":"tutorialsweblogic-tutorials-how-to","image_url":"","meta_title":"WebLogic Tutorial for Beginners | What is the WebLogic Server?","meta_desc":"In this WebLogic Tutorial, you will learn about what is WebLogic Server ✔️ Server Versions ✔️ Application Server ✔️ Web Server ✔️ and Important terms.","views":1438,"rating":4.7,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"192","created_at":"2015-03-04T21:23:07.000Z","updated_at":"2020-10-14T17:04:58.000Z","status":1,"video_schema_name":"","video_schema_upload_date":"","video_schema_description":"","faq_schema_q1":"What is WebLogic 12c?","faq_schema_a1":"Oracle WebLogic Server 12c R2 is the industry's best application server for building and deploying enterprise Java EE applications with support for new features for lowering the cost of operations, improving performance, enhancing scalability, and supporting the Oracle Applications portfolio.","faq_schema_q2":"What is The Use of Domain in WebLogic?","faq_schema_a2":"A WebLogic Domain is a logically related group of WebLogic Server instances (Admin + managed Servers)that you manage from a single set of configuration artefacts. A WebLogic Domain contains exactly one Administration Server and zero or more than zero managed Servers.","faq_schema_q3":"What is The Use of the WebLogic Server?","faq_schema_a3":"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.","like_counter":1},{"id":894,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":null,"table_of_content":null,"description":"$17","title":"Weblogic JDBC","url_title":"jdbc-weblogic","image_url":"","meta_title":"weblogic jdbc overview","meta_desc":"In this tutorial you will learn about a brief overview, architecture, Modular Configuration and Deployment in jdbc environment.","views":739,"rating":4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"0","created_at":"2014-11-11T12:28:04.000Z","updated_at":"2020-10-09T22:17:47.000Z","status":1,"video_schema_name":null,"video_schema_upload_date":null,"video_schema_description":null,"faq_schema_q1":null,"faq_schema_a1":null,"faq_schema_q2":null,"faq_schema_a2":null,"faq_schema_q3":null,"faq_schema_a3":null,"like_counter":0},{"id":878,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":"","table_of_content":"$18","description":"$19","title":"WebLogic Server Installation","url_title":"weblogic-server-installation","image_url":"","meta_title":"WebLogic Server Installation","meta_desc":"In this Blog, you will learn about WebLogic Server Installation Modes ✔️ Prerequisites✔️ Installation Programs on Windows and Unix ✔️ and Server Dependencies.","views":1841,"rating":4.3,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"192","created_at":"2014-11-11T05:24:17.000Z","updated_at":"2020-10-08T13:34:52.000Z","status":1,"video_schema_name":"","video_schema_upload_date":"","video_schema_description":"","faq_schema_q1":"","faq_schema_a1":"","faq_schema_q2":"","faq_schema_a2":"","faq_schema_q3":"","faq_schema_a3":"","like_counter":0},{"id":875,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":null,"table_of_content":null,"description":"$1a","title":"Overview of Weblogic Application Server","url_title":"overview-weblogic-application-server","image_url":"","meta_title":"Weblogic Server | What is Weblogic Application Server","meta_desc":"Weblogic Server allows you to quickly develop and deploy reliable, secure, scalable and manageable applications which helps business logic and presentation.","views":0,"rating":4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"0","created_at":"2014-11-11T04:40:54.000Z","updated_at":"2020-10-08T12:39:14.000Z","status":1,"video_schema_name":null,"video_schema_upload_date":null,"video_schema_description":null,"faq_schema_q1":null,"faq_schema_a1":null,"faq_schema_q2":null,"faq_schema_a2":null,"faq_schema_q3":null,"faq_schema_a3":null,"like_counter":1},{"id":760,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":null,"table_of_content":null,"description":"$1b","title":"Session replication in Weblogic Cluster","url_title":"session-replication-in-weblogic-cluster","image_url":"","meta_title":"Session Replication in Weblogic Cluster","meta_desc":"Here, we discuss the session replication in the Weblogic cluster and are explained in detail...Tekslate.","views":0,"rating":4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"0","created_at":"2014-11-03T22:10:34.000Z","updated_at":"2020-10-08T12:16:43.000Z","status":1,"video_schema_name":null,"video_schema_upload_date":null,"video_schema_description":null,"faq_schema_q1":null,"faq_schema_a1":null,"faq_schema_q2":null,"faq_schema_a2":null,"faq_schema_q3":null,"faq_schema_a3":null,"like_counter":0},{"id":468,"blog_category":159,"blog_type":2,"wp_id":1,"excerpt":"","table_of_content":"","description":"$1c","title":"WebLogic Interview Questions and Answers","url_title":"interview-questions-on-weblogic","image_url":"","meta_title":"WebLogic Real Time Interview Questions and Answers (2023)","meta_desc":"Prepare for the Best WebLogic Interview Questions and Answers ➔ Real-time Case Study Questions✔️ Curated by Experts✔️ FAQs✔️ Interview Tips.","views":2434,"rating":4.4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"192","created_at":"2017-03-07T12:22:00.000Z","updated_at":"2020-10-06T13:02:33.000Z","status":1,"video_schema_name":"","video_schema_upload_date":"","video_schema_description":"","faq_schema_q1":"How do you troubleshoot Server Hang?","faq_schema_a1":"We can use Java WebLogic. Admin PING to check if we get a normal response. We need to take multiple thread dumps with kill -3 paid on Unix and CTLR Break on Windows. Analyze the thread dump to find the root cause.","faq_schema_q2":"When does High CPU Usage occur?","faq_schema_a2":"It occurs when one process or one thread utilizes an unexpectedly high proportion of CPU.","faq_schema_q3":"How does Cluster Communication Happen?","faq_schema_a3":"Members of the Cluster communicate over the Cluster Multicast IP and Port by sending periodic heartbeat messages.","like_counter":1},{"id":368,"blog_category":159,"blog_type":2,"wp_id":1,"excerpt":"","table_of_content":"","description":"$1d","title":"Oracle WebLogic Interview Questions","url_title":"interview-questions-on-oracle-weblogic","image_url":"","meta_title":"TOP 50 Oracle WebLogic Interview Questions [UPDATED] !!!","meta_desc":"Looking for Oracle WebLogic Interview Questions with Answers? Here we have compiled set of questions from the students who have attended interviews in Fortune 500 companies","views":0,"rating":4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"192","created_at":"2016-11-01T06:25:00.000Z","updated_at":"2020-10-06T12:52:42.000Z","status":1,"video_schema_name":"","video_schema_upload_date":"","video_schema_description":"","faq_schema_q1":"","faq_schema_a1":"","faq_schema_q2":"","faq_schema_a2":"","faq_schema_q3":"","faq_schema_a3":"","like_counter":0},{"id":166,"blog_category":159,"blog_type":2,"wp_id":1,"excerpt":"","table_of_content":"","description":"$1e","title":"WebLogic Interview Questions","url_title":"weblogic-interview-questions-and-answers","image_url":"","meta_title":"TOP 50+ WebLogic Interview Questions and Answers (2023)","meta_desc":"Looking for WebLogic Interview Questions and Answers ➔ Real-time Case Study Questions✔️ Curated by Experts✔️ FAQs✔️ Interview Tips.","views":21738,"rating":4.6,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"192","created_at":"2016-02-16T12:31:22.000Z","updated_at":"2020-06-09T00:00:00.000Z","status":1,"video_schema_name":"","video_schema_upload_date":"","video_schema_description":"","faq_schema_q1":"What do you mean by admin in WebLogic?","faq_schema_a1":"Admin server in WebLogic serves as the central point of control that allows you to gain access to the configuration, monitoring and management of all resources. It is one of the instances of the WebLogic server that allows and maintains the data configuration of a given domain. It is a singleton service and every domain has at least 1 admin server.","faq_schema_q2":"What is a machine in WebLogic?","faq_schema_a2":"Any physical computer that is present or hosts instances in the WebLogic environment is called a machine. It is logically represented in a WebLogic server.","faq_schema_q3":"How can you set a classpath in a WebLogic server?","faq_schema_a3":"A classpath in Windows can be set using the following script WL_HOMEserverbinsetWLSEnv.cmd","like_counter":3},{"id":889,"blog_category":159,"blog_type":3,"wp_id":1,"excerpt":null,"table_of_content":null,"description":"$1f","title":"Logging and Filtering","url_title":"weblogic-logging-filtering","image_url":"","meta_title":"Logging and Filtering in Weblogic","meta_desc":"In this tutorial you will learn logging and filtering in weblogic. you will also learn monitoring individual servers and assigning a Log Filter to server.","views":438,"rating":4,"author":"1","top_level_cat_id":"21","author_desc":"","course_id":"0","created_at":"2014-11-11T09:31:59.000Z","updated_at":"2018-10-26T11:17:07.000Z","status":1,"video_schema_name":null,"video_schema_upload_date":null,"video_schema_description":null,"faq_schema_q1":null,"faq_schema_a1":null,"faq_schema_q2":null,"faq_schema_a2":null,"faq_schema_q3":null,"faq_schema_a3":null,"like_counter":0}],"type":"blog-cat","categories":[]},"urlName":"weblogic"}] a:[["$","meta","0",{"name":"viewport","content":"width=device-width, initial-scale=1"}],["$","meta","1",{"charSet":"utf-8"}],["$","title","2",{"children":"weblogic"}],["$","meta","3",{"name":"description","content":"TekSlate provides all the essential resources to help you become a skilled salesforce professional. Here is the list of informative resources that include tutorials, interview questions, and other technical blogs to make it easy for you to master weblogic."}],["$","meta","4",{"name":"application-name","content":"tekslatetutor"}],["$","meta","5",{"name":"generator","content":"tekslatetutor"}],["$","link","6",{"rel":"canonical","href":"https://tekslate.com/weblogic"}],["$","meta","7",{"property":"og:title","content":"weblogic"}],["$","meta","8",{"property":"og:description","content":"TekSlate provides all the essential resources to help you become a skilled salesforce professional. Here is the list of informative resources that include tutorials, interview questions, and other technical blogs to make it easy for you to master weblogic."}],["$","meta","9",{"property":"og:url","content":"https://tekslate.com/weblogic"}],["$","meta","10",{"property":"og:site_name","content":"tekslatetutor"}],["$","meta","11",{"property":"og:locale","content":"en_US"}],["$","meta","12",{"property":"og:image","content":"https://tekslateassets.s3.amazonaws.com/images/TekSlate_New+Colour.svg"}],["$","meta","13",{"property":"og:image:width","content":"1200"}],["$","meta","14",{"property":"og:image:height","content":"628"}],["$","meta","15",{"property":"og:type","content":"website"}],["$","meta","16",{"name":"twitter:card","content":"summary"}],["$","meta","17",{"name":"twitter:creator","content":"@tekslatetutor"}],["$","meta","18",{"name":"twitter:title","content":"weblogic"}],["$","meta","19",{"name":"twitter:description","content":"TekSlate provides all the essential resources to help you become a skilled salesforce professional. Here is the list of informative resources that include tutorials, interview questions, and other technical blogs to make it easy for you to master weblogic."}],["$","meta","20",{"name":"twitter:image","content":"https://tekslateassets.s3.amazonaws.com/images/TekSlate_New+Colour.svg"}],["$","link","21",{"rel":"icon","href":"https://tekslateassets.s3.amazonaws.com/images/favicon.svg"}]] 1:null