WebLogic

JSESSIONID is the default name of the cookie used by WebLogic Server web applications. It can be changed to another string in weblogic.xml. The format of JSESSIONID is: SessionId!PrimaryServer JVM Hash!SecondaryServer JVMHash Other than this you don’t see any other details. Consider a scenario with two servers (SERVER-NAME1, SERVER-NAME2) in a cluster. When you enable […]

The CLASSPATH value specifies the classpath for the weblogic_sp.jar, weblogic.jar, and in case you are using PointBase, the client and server JAR files for PointBase should also be included in the classpath. CLASSPATH – It contains the paths of class files which are stored. For example: CLASSPATH=”C:\Program Files\Java\jdk1.7.0_51\jre\lib\rt.jar” PATH: It contains the path for the […]

You have two choices about the type of DataSource, XADataSource or non-XADataSource. See the following differences. An XA transaction can be defined as a global transaction because it can work on multiple resources. Unlike the XA transaction, a non-XA transaction always works on one resource. An XA transaction works on a transaction manager that coordinates […]

The thread dump is a well-known feature of the Java Virtual Machine. It is a snapshot of the JVM that helps the WebLogic administrator analyze which Java method the Java threads were executing in at the exact moment the snapshot was taken. As in the rest of the book, the JVM used in this recipe […]

Usually, the JMS file store created will be with .DAT extension and is not in human readable format. You will have to use the weblogic.store.Admin utility to extract the content of file store into an XML file to read it. Follow the steps outlined below and ensure managed servers are stopped before proceeding. 1. Run […]

The below options are for timeout only for JAX-WS Web Service clients generated from clientgen: import javax.xml.ws.BindingProvider; import javax.xml.ws.handler.MessageContext; import com.sun.xml.ws.developer.JAXWSProperties; import com.sun.xml.ws.client.BindingProviderProperties; /* The following classes are inside import com.sun.xml.ws.developer.JAXWSProperties; import com.sun.xml.ws.client.BindingProviderProperties; %WLSINSTALLATION%\modules\glassfish.jaxws.rt_1.1.0.0_2-1-4.jar */ Map requestContext = ((BindingProvider)port).getRequestContext(); requestContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, “http://<hostname.domain>/HelloWorldImpl/HelloWorldService”); requestContext.put(JAXWSProperties.CONNECT_TIMEOUT, 300); requestContext.put(BindingProviderProperties.REQUEST_TIMEOUT, 300); The below options are for timeout only for JAX-RPC Web […]

When you create a domain with multiple Managed Servers, all those servers function independently of each other. A cluster, on the other hand, is a group of WebLogic Server instances that work as a single instance from the point of view of a client. The reason you use a cluster is to increase scalability and […]

Question: There are several files with a .lok extension in the WebLogic Server (WLS) domain directory. What are these files used for? There are config.lok, EmbeddedLDAP.lok and XXXserver.lok files which are used by the admin server and managed server. Another lock file named edit.lok is used for the admin server only. Why are .lok files […]