Showing posts with label BEA. Show all posts
Showing posts with label BEA. Show all posts

Monday, April 16, 2007

BEA WebLogic 8.1 Certified Administrator (3)

Manage Quality of Service

##CONTINUE##

  • Http session state clustering and object clustering are the two primary cluster services that Weblogic server provides.
  • Data Source objects can be defined with or without JTA, which provides support for distributed TX.

Troubleshoot and Diagnose Error Conditions

  • To test two-tier and three-tier JDBC database connections after installing weblogic Server use the utils.dbping utility.
  • A cluster is part of a particular WLS domain. You can’t split cluster in multiple domains.

Other

  • Before Completion Interation Limit is a TX setting which gives the number of beforeCompleption callbacks that are processed before the system forces a rollback.
  • Forget Heuristic is a Boolean value specifying whether the transaction manager should instruct a resource to forget any TX with a euristic outcome.
  • A connection object represents an open communication channel between an application and the messaging system. Connection objects are used to create a session for producing and consuming messages. A connectionFactory object encapsulates connection information and enables JMS applications to create a connection. The session object, defines the serial order for the messages produced and consumed. By default a connection is created in stopped mode.
  • You can create destination keys to define the sort order for messages arriving on a specific JMS destination (queue or topic).

    1. name of the destination key

    2. message sort key name or the name of a message header field on which to sort. Message header field keys start with the letters JMS and ignore the key type setting. (For better performance, use message header fields as sorting keys, rather than message properties.)

    3. The expected property type for the sort key. (This setting is ignored for message header field keys, which have an implied type.)

    4. The direction in which the key will sort messages (ascending or descending).

  • WLS model of centralizing management responsibilities on the Administration Server, Administration Server hosts Configuration Mbeans for all managed resources on all server istances in the domain.
  • WLS Mbeans that expose attributes and operations for configuration a managed resource are called Configuration Mbeans while Mbeans that provide information about the runtime state of a managed resource are called Runtime Mbeans.
  • JDBC Multipools provide backup pools and load balancing to enhance database connectivity. Multipools don not apply to multiple-server configurations, so they are not supported in distributed TX. Multipools allow a configurable algorithm for choosing a connection pool from its list of pools. The connection pools whin a Multipools may be associated with different DBMS.
  • All WLS resources are managed through this JMX based service.
  • The EJB container blocks the concurrent method call and allows it to proceed when the perious call has completed if the value of allow-concurrent-calls is true. The concurrency-strategy element determines ejbLoad and ejbStore behavior for entity EJB instances.
  • Check testConnsOnReserve , and testConnsOnRelease

BEA WebLogic 8.1 Certified Administrator (2)

Manage Deployed Applications

##CONTINUE##
  • The getRequestDispatcher() method returns a RequestDispatcher object that acts as a wrapper for the resource located at the given path. A RequestDispatcher object can be used to forward a request to the resource or to include the resource in a response. The resource can be dynamic or static

Public RequestDispatcher getRequestDispatcher(String path)

Return null if the servletContext cannot return a requestDispatcher.

  • Javax.transaction.UserTransaction provides an interface to the transaction manager that allows the application developer to manage the scope of a transaction explicitly. The client application uses JNDI to obtain an object reference to the UserTransaction object for the Weblogic Server domain.

Client:

UserTransaction ut = (UserTransaction) jndicontext.lookup(“javax.transaction.UserTransaction”)

Bean:

UserTransaction ut = ejbContext.getUserTransaction()

  • The default Transaction level for EJB’s in Weblogic is Supports
  • JSP tag libraries are copied into the WEB-INF directory
  • WLS allows TX to be terminated only by the client that created the TX. WLS implements the flat TX model; nested TX are not supported. WLS supports multithreaded TX clients; clients can make TX requests concurrently in multiple threads. In WLS a client or a server object cannot invoke methods on an object that is infected with another TX. In WLS, client cannot using third-party implementations of the JAVA TX API.

BEA WebLogic 8.1 Certified Administrator (1)

Environment Preparation and WebLogic Installation

  • WLS webservices support A Stateless Session Bean, JMS Message Consumer and JMS Message Producer, Web service operations implemented with Java classes.
##CONTINUE##
  • Memory Usage, throughput(and queue) and Locked-out users can be monitored in the console.
  • Weblogic.Admin

    LIST : list the bindings of a node in the JNDI naming tree

    CONNECT :

    GETSTAT : return current state of a server.

    PING:

  • Use JPDA to perform remote debugging or use the logging services in weblogic.
  • When updating two tables in different databases and when updating a table in a database and writing a message to a JMS Queue do required the use of two-phase commit.


BEA WebLogic 8.1 Certified Administrator Preparation Note

BEA WebLogic 8.1 Certified Administrator :

This exam is not easy and has little of materials. However, you can read all the BEA materials from the BEA web site. But I think that is too much to read.

In order to pass this exam, I attented the Administrator of BEA WebLogic Server 8.1 workshop.
That is the only material I read to pass the exam.

Following posts are the preparation note I noted when I studied for this exam,

Hope it helps ~