Oracle Weblogic Server 11gR1 PS2: Administration Essentials

By Michel Schildmeijer
  • Instant online access to over 7,500+ books and videos
  • Constantly updated with 100+ new titles each month
  • Breadth and depth in over 1,000+ technologies
  1. Oracle WebLogic: Your First Step into the Middleware World!

About this book

Oracle's WebLogic 11g Server is an application server for building and deploying enterprise Java EE applications. WebLogic's infrastructure supports the deployment of many types of distributed applications and is an ideal foundation for building applications based on a Service Oriented Architecture. This book will guide you through the important administration aspects of WebLogic server.

Oracle WebLogic Server 11gR1 PS2: Administration Essentials is a focused step-by-step tutorial that provides an overview of the important administrative tasks performed by WebLogic Server administrators.

This book will teach administrators the techniques for installing and configuring Oracle WebLogic Server and how to deploy Java EE applications using the Administration Console, command-line interface, and scripting tools such as WLST. It starts with a good overview of the techniques needed in the middleware world of today. Clear explanations of definitions and concepts of JEE and how Oracle WebLogic fits into this picture are also provided. The book then dives into performing routine Oracle WebLogic server administration functions, and how to deploy different types of Java EE applications to WebLogic server.

Publication date:
September 2011


Chapter 1. Oracle WebLogic: Your First Step into the Middleware World!

Ever wondered how information about the different areas, such as personal, financial, medical, or whatever you can think of, is processed, distributed, and secured in a safe way? The digital, electronic, and complex world today needs good and solid solutions to make sure that they fulfill the needs of our entire society.

You as an IT technician can play an important role in that world. You will have to translate business needs into technical solutions. And business needs are very demanding these days. Computer systems need to be available 24/7 and must deliver a solid environment where no loss of data is allowed.

And in our fast economy, systems need to perform at the top of their abilities, because applications running on them are highly critical and information needs to be delivered in a limited amount of time.

IT technicians play an important role in building a solid solution for all these requirements. In this book, you will discover Oracle's very solid solution, presented as the Oracle WebLogic Server.


The very first steps into middleware

Nowadays, middleware is the key component in IT infrastructure. It connects various systems to each other, lets users interact with their applications, and lets them manipulate data. That's why big software vendors, such as Oracle, have a so-called strategic platform for their middleware. Let's take a deeper look into the unveiled secrets of the middleware world!

Middleware is computer software that connects software components, people, and their applications.

The software consists of a set of services that allows multiple processes running on one or more machines to interact. This technology evolved to provide for interoperability in support of the move towards coherent distributed architectures, which are most often used to support and simplify complex distributed applications.

Middleware, as the name suggests, sits "in the middle" of the application software that may be working on different operating systems. It is similar to the middle layer of three-tier single system architecture, except that it is stretched across multiple systems or applications. Examples include EAI software, telecommunications software, transaction monitors, and messaging-and-queuing software.

The pre-middleware era

Before the introduction of middleware platforms, applications had isolated programs running on isolated computers. As an administrator, if a new version of the program came out, you had to go by every client computer to update or reinstall the software.

Also, when problems occurred, it was very hard to determine what the cause was, because all resources ran locally on the client machine, each with their own settings and configurations. Later on, things got more evolved by pushing software from a central store to the client PCs, but still they ran isolated, and was very difficult to administer.

With the upcoming Internet during the 90's, applications also began to evolve from client computers into centralized environments, accessed through a web browser, such as Internet Explorer. The birth of middleware environments was a fact, and more and more different vendors began to develop their own strategic platforms.

What is a middleware environment?

There is no strict definition of a middleware environment, but in general one can say: middleware is software that connects components, systems, users, and their applications. It includes web servers, application servers, and other tools that provide application development, deployment, execution, and delivery. Middleware is able to handle all kinds of information technology based on XML, SOAP, web services, and SOA.

An Application Server plays the key role in a middleware environment. In fact, this is the platform that connects all systems with each other, with the many plugins, resources, and other interfaces that the Application Server delivers.

The Java EE Application Server

Oracle WebLogic implements the JEE standards. JEE is the standard for JAVA Server programming and runtime JAVA.

JEE has a wide variety of APIs (Application Programming Interface) in it, such as JDBC, RMI, e-mail, JMS, web services, XML, and more. These components are also part of the WebLogic Server environment and will be discussed in the coming chapters. JEE also features some specifications for components that are unique to Java EE. Besides leveraging the APIs, JEE also contains Enterprise JavaBeans, connectors, servlets, portlets, Java Server pages, and several web service technologies. This allows developers to create enterprise applications that integrate with legacy technologies.

A Java EE application server can handle transactions, security, scalability, concurrency, and management of the components that are deployed to it, in order to enable developers to concentrate more on the business logic of the components rather than on infrastructure and integration tasks.


The case: Your company needs middleware!

In this book we will be an employee of a fictive company, where you act as a senior technical consultant. You have a very demanding boss who is a very stressed person, because he receives a lot of pressure from his boss about the status of several projects. But you, middleware expert that you are, can provide him with all the solutions that are discussed in this book, and in the end, your boss (and you of course) is very happy. So go for the "Hollywood happy ending" when you finish this book.

FinanceFiction Enterprises

You work for a big worldwide financial company with many customers around the world. The following are some of the key aspects of your company:

  • Company size: 60,000 employees worldwide

  • Estimated equity: $250 billion

  • Yearly profit: $25 billion (but under pressure because of bad performing systems!)

  • Key customers: Large companies, such as oil industries, telco's worldwide

  • Key departments:

    • Marketing and communication

    • Financial and accounting services

    • Customer relations

    • Settlements, clearance and security

    • Human resources

Your company is an international financial institution serving many end-customers all over the world including large enterprises that trust your company for all their financial transactions. So it's obvious that a good computer infrastructure is needed to deliver the highest level of service to the customers. Also, internally your company depends on good infrastructure. The current infrastructure needs a thorough renewal because most of the technologies are outdated. A lot of legacy systems have become more and more isolated. Customers begin to complain that they experience have all kinds of problems; your boss gets more and more pressured and nervous. But you, being the cool and calm technician that you are, provide him with the solution:

The Oracle Fusion Middleware Solution

Oracle WebLogic is part of the Oracle Fusion Middleware Solution as Oracle has called its middleware product stack.

The previous diagram gives a schematic overview of the entire stack of the Oracle middleware portfolio. Of course, in this book we will focus mainly on Oracle WebLogic, but we will occasionally touch on some other areas as well.

Oracle WebLogic is the key platform in the entire Fusion Middleware stack. All kinds of different layers of software have the Oracle WebLogic Server as the base platform.

From OC4J to WebLogic

With the introduction of the "i" after its main releases (8i, 9i), Oracle began to put more and more focus on Internet and browser-based computing. Oracle builds from version 9i its own J2EE server, based on HTTP (Apache) and Oracle Containers for Java (OC4J). Each OC4J was a Java Virtual Machine. On top of OC4J, many applications could be deployed such as Oracle Forms & Reports, Oracle Portal, Oracle Discoverer Web version (all on version 10.1.2), and Oracle SOA Suite (BPEL, ESB and OWSM) on 10.1.3.

The following diagram shows the OC4J versus WebLogic comparison:

In July 2008, Oracle launched its new 11g Middleware platform: Oracle WebLogic 11g.

However, with the acquisition of Sun and BEA, a lot of customers were added as well. So it will take some time to get all customers in line!


Oracle WebLogic architecture and terminology

Finally! Your big day is here. Your company, FinanceFiction has decided to modernize its outdated middleware solutions with the Oracle Fusion Middleware stack.

Your boss keeps smiling all day, because your department has been chosen to be the pilot and do a proof of concept. You've been asked to do some preliminary research in order to explain to the non-technical board members what the Oracle WebLogic Server can do for FinanceFiction.

Oracle WebLogic: A JEE Server

Oracle WebLogic is, as said earlier, the middleware infrastructure environment that all kinds of applications—Oracle or non-Oracle—make use of. Oracle WebLogic is a JEE (Java Enterprise Edition) Server . More about the JEE concept will be discussed later in this chapter.

Oracle WebLogic technology facts

You have been promoted by your boss to do the research about Oracle WebLogic. A catchy one-liner you could use in your presentation is:

Oracle WebLogic Server is a scalable, enterprise-ready, Java Platform Enterprise Edition (Java EE) application server.

The WebLogic Server infrastructure supports the deployment of many types of distributed applications and is an ideal foundation for building applications based on Service Oriented Architectures (SOA). SOA is a design methodology aimed at maximizing the reuse of application services.

Although this sounds like a line of a typical salesperson, it's still true. The WebLogic Server delivers implementation of the Java EE 5.0 specification, and provides a standard set of APIs for creating distributed Java applications that can access a wide variety of services, such as databases, messaging services, and connections to external enterprise systems.

This is exactly what your company needs: more interaction between the diversity of your systems.

WebLogic Server enables enterprises to deploy mission-critical applications in a robust, secure, highly available, and scalable environment.

Another one, but also true. WebLogic is easy to scale and can be set up with continuity for the business so that they wouldn't notice if a system is down.

Next, we will dive a little deeper into the basic concepts of the WebLogic Server.

The WebLogic domain structure

The basic administrative unit for a WebLogic Server is called a domain. A domain is a logically related group of WebLogic Server resources that you manage as a unit. A domain always includes the minimum of one instance called the Administration Server. The Administration Server is a central point of contact for server instances and system administration tools. A domain may also include additional WebLogic Server instances called Managed Servers and clusters.

A Managed Server might be part of a WebLogic Server cluster. A cluster is a group of WebLogic Server instances that work together to provide scalability and high-availability for applications. A Managed Server in a cluster can act as a backup for services such as JMS that are hosted on another server instance in the cluster. Applications are normally deployed in a Managed Server.

The domain can run in two modes:

  • Development mode: A domain running in development mode does not require a password during startup of the Administration Server. You also can do autodeploy of your applications, as some other parameters are not that strictly configured.

  • Production mode: Running in production mode needs passwords, encryption of files at a higher level, and some parameters within the resources (such as JDBC, JMS) are strictly configured.

You can have multiple domains based on:

  • Physical location

  • Logical division of applications (backend application domain, frontend application domain)

  • Size (smaller manageable units instead of one huge domain)

The next diagram shows the flow of the several steps creating a domain. This will be discussed later on.

Administration Server

Each WebLogic domain has an Administration Server. As its name suggests, it's the base administration unit to handle all kinds of administration tasks within the WebLogic domain. An Administration Server does all its tasks within the Java Virtual Machine (JVM). The Administration Server can be accessed through a web browser. You can deploy your application on an Administration Server but it is recommended to create Managed servers and deploy your application in a Managed server and leave the Administration Server for configuration and maintenance purposes only. There will allways be only one Administration Server per domain.

Managed Servers

Other instances running in their own JVM than the Administration Server that are within a WebLogic domain are called Managed Servers. As stated, it runs in its own JVM. A Managed server can start independently from an AdminServer, if configured so.

Two or more Managed servers can be configured as a WebLogic Server cluster to increase scalability and availability. In a WebLogic Server cluster, most resources and services are deployed identically on each Managed Server, enabling failover and load balancing. A single domain can contain multiple WebLogic Server clusters, but can also contain nonclustered Managed Servers.

The main difference between clustered and nonclustered Managed Servers is the support for failover and load balancing handled by the WebLogic domain (one can configure clustering outside WebLogic of course). These features are available only in a cluster of Managed Servers.

Managed Servers are used to facilitate applications and their resources, as described in the next section.


"I don't have enough resources available!", you hear your boss scream on the phone to the program manager, who is demanding quicker results in order to get the project going. Your boss is running out of his office yelling, "Work harder, faster, more!!".

You get a slight smile on your lips. Through your research, you already began to understand that the WebLogic Server is very efficient in managing its resources. Your boss could learn managing his own resources as the WebLogic Server does.

Both a WebLogic Administration Server and a Managed Server manage their resources and services efficiently to such an extent that nothing is wasted.

The domain delivers resources and services required by Managed Servers and hosted applications deployed in the domain. The domain configuration includes information about the environment.

The domain configuration also includes information about resources and services associated with applications hosted on the domain. Examples of these resources and services include:

  • Application components, such as EJBs or JSPs

  • Security providers

  • Resource adapters

  • JDBC data sources

  • JMS servers or other messaging resources

  • Store-and-forward service

  • Persistent store

  • Startup classes

  • Diagnostics and monitoring services

Resources and services can be limited to one or more Managed Servers in the domain, rather than being available to the domain as a whole. You can deploy resources and services to selected Managed Servers or to a cluster.

A deeper look into Managed Servers will be handled in Chapter 5, What is a Managed Server?.


Oracle WebLogic—a JEE server… but what is JEE?

Oracle WebLogic is a JEE application server, that is Java Enterprise Edition. But what does this mean?

The JEE distributed system

A WebLogic infrastructure containing multiple managed JEE application servers is called a distributed system.

It divides the work among several independent modules. The failure of a single module has less impact on the overall system, which makes the system more:

  • Available

  • Scalable

  • Maintainable

JEE standards allow:

  • Modularization of complex hardware and software

  • A larger portion of the project costs to go toward solving business software needs

Java EE is a widely used platform for server programming in the Java programming language. The Java EE platform differs from the standard edition of Java, in that it adds libraries which provide functionality to deploy fault-tolerant, distributed, multi-tier Java software, based largely on modular components running on one or more JEE application servers.

Applications deployed with Java EE technologies are standardized, have specification guidelines, are written in Java, and are deployable to any JEE application server.

The following diagram shows an example of a typical JEE architecture:

In this overview, you can see practically all components that are a part of the JEE. We will discuss some of them in this chapter.

JEE Resources

As your boss was screaming for resources, well, you can present him the JEE distributed system. It contains a lot of resources, such as:

  • Java Servlets

  • Java Server Pages (JSP)

  • Enterprise JavaBeans (EJB)

  • Java Database Connectivity (JDBC)

  • Java Naming and Directory Interface (JNDI)

  • Java Transaction API (JTA)

  • Java Message Service (JMS)

  • Java Authentication and Authorization (JAAS)

  • Java Management Extensions (JMX)

  • Java EE Connector Architecture (JCA)

We will look into the different components and how they interact with each other to get an overview of how a (WebLogic) JEE system works.

Java Servlets

A servlet is a Java program that executes on the server, accepts client requests, and generates dynamic responses. An example of a servlet is an HttpServlet that accepts HTTP requests and generates other HTTP Servlets, which may be packaged in a WAR file as a Web application.

Simple code of an HttpServlet:

import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class HelloWorld extends HttpServlet {
  public void doGet(HttpServletRequest request, HttpServletResponse response)
      throws ServletException, IOException {
    PrintWriter out = response.getWriter();
    out.println("<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.0 " +
                "Transitional//EN\">\n" +
                "<html>\n" +
                "<head><title>Hello WWW</title></head>\n" +
                "<body>\n" +
                "<h1>Hello WWW</h1>\n" +


Downloading the example code

You can download the example code files for all Packt books you have purchased from your account at If you purchased this book elsewhere, you can visit and register to have the files e-mailed directly to you.

Java Server Pages (JSP)

A JavaServer page is a way to generate dynamic HTML and XML. This is done by Java code and some predefined actions, called JSP actions.

JSPs use a JSP compiler to access the Java code and loads this into a servlet, as you can see in the following code:

The following is an example snippet of a JSP generated servlet:

package jsp_servlet;
 import java.util.*;
 import javax.servlet.*;
 import javax.servlet.http.*;
 import javax.servlet.jsp.*;
 import javax.servlet.jsp.tagext.*;
 import example ; // Imported as a result of <%@ page    import="" %>
 import …
class _myservlet implements javax.servlet.Servlet, javax.servlet.jsp.HttpJspPage {
    // Inserted as a
    // result of <%! int serverInstanceVariable = 1;%>
    int serverInstanceVariable = 1;
    public void _jspService( javax.servlet.http.HttpServletRequest request,
    javax.servlet.http.HttpServletResponse response )
    throws javax.servlet.ServletException,
        javax.servlet.ServletConfig config = …; // Get the servlet config
        Object page = this;
        PageContext pageContext = …;            // Get the page context for this request
        javax.servlet.jsp.JspWriter out = pageContext.getOut();
        HttpSession session = request.getSession( true );
        try {
            out.print( "<html>\r\n" );
            out.print( "<head>\r\n" );

Java Naming and Directory Interface (JNDI)

The API used for accessing resources is JNDI. It's a layer built for accessing naming and directory services (naming service such as an internet address). It uses a directory kind of structure to bind the objects and is accessible by passing simple strings showing logical directory structure such as "jdbc/DB1" (a JNDI for a JDBC service).

A developer does not need to code resource references by using the computer, host, or database names, he /she can use the JNDI name. This makes the code much more generic and can be easily reused. Therefore it's independent of the underlying structure. In the following diagram you can see how a web service connects to an EJB using JNDI.

Enterprise JavaBeans (EJB)

The Enterprise Java Bean is a JAVA API server-side component that handles business logic of an application. The beans are running in an EJB Container on a JEE Server.

Many Oracle products, such as the Oracle SOA Suite, use EJBs. As an administrator, it's good to know the basic knowledge of EJB and how they behave in a WebLogic environment. As an example, it can help you to know how to size your JVMs.

From the previous diagram, you can see that the EJB client (can be an application)connects over RMI (Remote Method Invocation) by using JNDI naming.

Java Database Connectivity (JDBC)

An important resource in your Oracle WebLogic is most certainly your set of JDBC resources. Java Database Connectivity (JDBC) is also a standard Java API that consists of a set of classes and interfaces.

Developers use JDBC to write database applications and execute SQL statements. JDBC requires the use of a driver; implements database-specific connectivity, and statement handling. WebLogic provides many drivers for different kinds of databases. It's used internally for metadata purposes and for application and business purposes.

As noted, JDBC can be used for supporting the infrastructure (for example, the Oracle SOA Suite Infra application) or for customer-related data.

Java Transaction API (JTA)

JTA is an API too that allows distributed transactions, such as XA transactions. It contains three elements: a high-level application transaction demarcation interface, a high-level transaction manager interface intended for an application server, and a standard Java mapping of the X/Open XA protocol intended for a transactional resource manager. It supports user transaction in EJB, JNDI, and Servlets. The WebLogic Server can process the transaction process that is addressed by the JTA. Application servers handle the bulk of application operations and take some of the load off the end-user application.

Java Message Service (JMS)

Java Message Service is an API for accessing message-oriented middleware.

The interface supports:

  • Point-to-point communication

  • Publish/subscribe ("pub/sub") communication

  • Guaranteed message delivery

  • Transactional participation

  • Application- or system-scoped resources

  • Interoperability with other messaging systems

JMS is a way of loosely coupled messaging. It uses a queuing mechanism; the publisher puts a message on the queue without knowing that it will be picked up. The subscriber then picks up the message. It knows that the message is for that person because it's embedded in the message header.

Key components of JMS are:

  • JMS provider

    • The JMS interface for a Message Orientated Middleware (MOM)

  • JMS client

    • Produces and/or receives messages

  • JMS producer/publisher

    • Creates and sends messages

  • JMS consumer/subscriber

    • Receives messages

  • JMS message

    • The actual message

  • JMS queue

    • An area that contains messages that have been sent and are waiting to be read

  • JMS topic

    • A distribution mechanism for publishing messages

The next diagram shows the WebLogic JMS Server Architecture:

Java Authentication and Authorization Service (JAAS)

Java Authentication and Authorization Service (JAAS) is a Java-based security management framework. It supports Single Sign-On, and is implemented within the WebLogic Server. Terms that are used in the WebLogic JAAS implementation are security providers and realms.

A realm is a collection of users and groups that are controlled by the same authentication policy. Security providers implement the underlying security framework for your JEE applications. The default security providers can be used or one can implement his/her own security provider within the WebLogic Server. The following diagram shows an example of an authentication process:


Java Management Extensions is a technology that lets you implement management interfaces for Java applications. The specification describes MBeans, which are the building blocks of JMX. One can access these MBeans (Managed Beans) using the WebLogic Scripting Tool (WLST). It supports managing and monitoring for all kinds of services.

JMX is an open technology that is not specific to WebLogic, but is a part of JEE/JSR specification.

Java EE Connector Architecture (JCA)

Another connector API is called the JCA adapter. It connects EIS (Enterprise Information System) with the so-called resource adapters, deployed in an archive (RAR).

For instance, you could use a SAP resource adapter to connect to a SAP EAI.

With JCA, one could connect to many Enterprise systems, such as SAP, PeopleSoft, and Siebel, among others.

Secondary components in the JEE architecture

Besides the components that are directly managed in a JEE system, there are also external, yet influential, components that should be discussed briefly here.

HTTP clients and servers

During the 90's, with the expanding Internet, the web server began to play a key role. A web server—as the name suggests—provides web content, mainly with the HTTP(S) protocol, and sometimes also through FTP and others. It can handle some scripting such as JavaScript and CGI.

A HTTP client connects to a web server, and depending on the role of the web server, passes the request through to an application server. Web clients can connect through JAVA, web browsers, FTP, and Mail.

Proxy servers

A proxy server is more like an intermediate between clients and web servers or application servers. It can speed up connections by caching frequently requested pages. It can apply policies and mask the identities of the clients. Sometimes it is also referred to as a gateway.


Firewalls are a well-known and always topical issue. Firewalls can block unauthorized users from outside a company, detect intrusions, and scan for malware and spyware. In fact, they are the lock on the door to the outside world.


Key players in the middleware market

During your research into whether Oracle's WebLogic is the best option for FinanceFiction, you came across some other middleware vendors and their products. Although it was not your assignment to investigate them, you thought it was wise to have a quick look at the kind of solutions other companies provided.

IBM WebSphere

IBM provides a wide variety of middleware products, with its strategic platform called WebSphere Application Server. In general, it provides the same resources as Oracle WebLogic does.

Some of the products are:

  • WebSphere Application Server

  • WebSphere Business Integration Toolset

  • WebSphere InterChange Server

  • WebSphere MQ

  • WebSphere Message Broker

  • WebSphere Adapters

  • WebSphere Process Server

  • WebSphere Portal Server


Another vendor is TIBCO, which is also a provider of infrastructure software for companies. Some of its products are:

  • TIBCO ActiveMatrix

  • TIBCO BusinessEvents

  • TIBCO Collaborative Information Manager

  • TIBCO Silver

  • TIBCO Spotfire


SAP is a software vendor that provides Enterprise Software (as discussed in the JCA adapter). It specializes in ERP (Enterprise Resource Planning) software, and provides a lot of business solutions such as supply chain management and data management. Technical platforms are NetWeaver and some specialized frameworks.

Open source-like Apache Software Foundation

The open source community also provides middleware solutions. One of the well-known solutions is Apache, that is also used within Oracle Fusion Middleware.

Apache is an open source web server for all kinds of operating systems such as AIX, Solaris, Windows, and AS 400.

The first version came out in 1995 as an answer to the Netscape web server, but unlike Netscape, Apache still exists and is still popular. It's being used by a lot of vendors as their HTTP server.

In the Oracle Webtier Utilities, Apache is used as the web server (Oracle HTTP Server). To integrate the Webtier, a new module is used, which is mod_ohs.


The big day: Presenting your research!

How can you best present your research? Here you go:

Presentation to the board

Your boss has asked you to do the big presentation for the members of the board. He's very nervous and agitated, because getting this assignment would give his (and your) department a big boost in the company. Also, the introduction of new technologies would give your department a big lift in your company.

So, you think about what you need to tell them without sounding like a salesperson selling a product, in this case, Oracle WebLogic.

In general, you could ask yourself, "Why Oracle WebLogic anyway? And why not some other player in the market?"

Decisions to make

Of course you could recommend another platform, but that was not your assignment. Because your company already uses a lot of other Oracle products, the main goal should be to introduce Oracle WebLogic as the middleware platform.

As with any other platform, technology, or solution there are always pros and cons to choose or not to choose a certain direction. But during your research, you became convinced that "Oracle WebLogic 11g is the future!!"

Your presentation…

The first slide of your presentation could be the following one:

You need to tell your audience about Oracle WebLogic being a middleware platform, which is needed as a key component in the many different environments in the company. Also, you have to explain to them how to reduce costs by introducing SOA and process management, also on the WebLogic platform, and about the platform's scalability, stability, and performance.

Driven by your enthusiasm, you see the members changing their expressions into smiling ones, and your boss, who is sitting behind them, is giving you the thumbs-up. It looks like all your research and effort will be rewarded.

But there's one grumpy old man, who always has negative opinions, including about this whole subject; he (although he has zero technical knowledge) tries to bombard you with all kinds of questions that could prove that his negative view is right.

For example, he asks you: "We have a lot of different legacy systems, and it will cost a whole lot of money to hire all the developers to recode to the WebLogic platform," and he triumphantly laughs at his colleagues. You even see your boss's eyelid tremble, but when you tell him about the many integration solutions, such as the JCA adapter, even he becomes enthusiastic.

Then, after a two-hour session, you finish your presentation, and your boss gives you a big compliment. The final decision will be taken later.



This chapter contained your first careful steps into the middleware world. Although a middleware environment can become very complex, many companies underestimate the administration and configuration aspect of it. As big projects mainly focus on developing new applications and functionality, they often forget to think about the infrastructure, or do so just at a very late stage of the project.

But you, after your initial research, emphasize the importance of a good infrastructure that is built on Oracle WebLogic.

Because of the good and solid presentation of your research, you get the green light to go forward.

In the next chapter, we will focus on installing the Oracle WebLogic Server with its many options, examples, and demos. Have fun!

About the Author

  • Michel Schildmeijer

    Michel Schildmeijer was born in the Netherlands in 1966. He studied pharmaceuticals, and after the military duty he started in industrial and hospital pharmacy. Because he got more involved in computers, he made the change to IT in 1996. At this moment he is an Oracle Fusion Middleware Architect at Qualogy, with focus on technical infrastructure, Serverside solutions, installing, administering, configuring the Oracle Fusion Middleware stack. His experience is from integrations at telco´s using Oracle AIA, Oracle Portal, OID, Forms&Reports, and Discoverer up to the latest Oracle WebLogic 12c releases with practically all Oracle products running on top of it He has a special interest in developing tools for administrators and automation of common administration tasks, so he has in depth knowledge of the Oracle WebLogic server and its unveiled secrets.

    Browse publications by this author
Book Title
Access this book, plus 7,500 other titles for FREE
Access now