Posted on

Deploying applications with Oracle WLS

Deploying applications with Oracle WLS can be done using a variety of instruments:

  • Using the Eclipse environment: this is the favourite option for developers, as it allows deploying applications as you are coding, using just one instrument.
  • Using the WebLogic console: this is a multi-purpose option which is recommended in case you are deploying your applications from/to a remote environment or if you don’t know the exact name or location where your deployments are.
  • Using the WLST scripting language: this option comes to your rescue in case you have to perform some batch deployments, or you want to automate your deployments while adding some logic to it. This option is discussed in the chapter 10 “Managing Oracle WLS with WLST”.
  • Using the class weblogic.Deployer: thisis, as well, a shell script solution which has been available since the very first releases of WLS. It can be still useful if you don’t need all the power of the WLST scripting language.

Deploying applications from Eclipse

Once that you have installed the OEPE, you should be able to see, in the Server Tab, the Oracle WebLogic Server icon:

Right-click on it and choose “Add or Remove” option; this will allow you delivering applications on your server.

If you want to specify the list of servers on which your application will be deployed, right-click on the application server and choose “Properties”. Expand the WebLogic | Publishing | Advanced option as depicted by the following picture:

From there, you can choose which servers will be elected as Target servers for your application. Once you are done, return to the Server icon and Right-click and choose “Publish”.


Posted on

Developing applications with Oracle WLS

The WebLogic Server complete implementation of the Java EE 6.0 specification provides a standard set of APIs for creating distributed Java applications using a wide variety of services (such as databases, messaging services, and connections to external enterprise systems). It also supports the Spring Framework, a programming model for Java applications which provides an alternative to many aspects of the Java EE model.

Although the focus of this book is not on the development of applications, we will guide you through a set of topics which are important to know if you want to develop fully portable Java EE applications or simply if you want to kick-start your first Oracle WLS project.

  • The first part of this chapter covers the installation of a development environment which is an Eclipse on steroids, specifically designed for Oracle WLS.
  • In the second part we will learn some peculiar development features related to the JPA and JNDI API which are essentials when porting applications from other application servers to the WLS and vice versa.
  • In the last block, we will learn how to create shared libraries which can expand the default core server libraries.

Installing a development IDE for Oracle WLS

There are several alternatives for developing applications on Oracle WLS: in this recipe we will show how to download and install the Oracle Enterprise Pack for Eclipse (OEPE) which is an Eclipse based environment which contains all the required plugins for developing apps with Oracle WLS.

Oracle Enterprise Pack for Eclipse (OEPE) is installed out of the box in your distribution if you have installed it using the 32 bit Full Installer option.

In order to install the Oracle Enterprise Pack for Eclipse (OEPE),follow these simple steps:

  1. Move to the download page at:
  2. Download Oracle Enterprise Pack for Eclipse Standalone Installers suited for your OS.

The Oracle Enterprise Pack for Eclipse Standalone installers includes a preconfigured version of Eclipse and the OEPE plugins. Installing OEPE just requires unzipping it to a folder of your choice. Once done with it, start Eclipse by running the eclipse (eclipse.exe for Windows) command.

The first thing we will need to do is defining a new WebLogic Server. This can be achieved from the Eclipse File menu, by selecting New | Server:

Choose the latest stable release and, in the next screen, select your WebLogic home and Java home:

Click on Next. In the following screen, point to your Oracle WLS Domain directory:

Click Finish and verify that the Oracle WebLogic Server has been included in the Server Tab:

Posted on

Configuring JMS Services

Oracle WLS provides its own messaging system that fully implements the JMS specification; it also provides other configuration and programming options that go well beyond standard Enterprise-class messaging features.  Here are the key components of Oracle WLS JMS Architecture:


  • JMS Server: A JMS server is a management entity and container for JMS destination-related resources that reside on a single WLS instance. A WLS JMS Server instance can host zero or more JMS servers and can serve as a migration target for zero or more JMS servers. 
  • JMS Modules: JMS modules contain configuration resources such as queue and topic destinations, distributed destinations and connection factories. In WebLogic Server, these resources are configured inside the DOMAIN_HOME/config/jms directory.
  • JMS Producers/Consumers: This is a piece of software that either produces messages to destinations or consumes messages from destinations.
  • Persistent Store: This is used for storing the Data (Messages). It can be either a user defined Persistent Store or a Default Persistent store.

Here is a graphical view of the concepts exposed so far, which shows two JMS Servers each one containing a JMS module where JMS destinations are registered:


Steps to configure JMS resources

In order to create JMS resources, you need to perform a set of activities which include:

  1. Creating a JMS Server
  2. Creating a JMS Module
  3. Creating JMS Connection factories
  4. Creating JMS Destinations

In the following sections, we will create the first mandatory JMS resource, which is the JMS Server.

Creating a JMS Server

  1. Expand the Services option from the left menu and select Messaging | JMS Servers.
  2. Click New in the JMS Servers table. In the next screen, enter values for the following configuration parameters:

Specify the following mandatory settings:

  • Name: The name of the JMS server.
  • Persistent Store: A JMS store can be file-based or database. Database is usually a bit slower, but can take advantage of high-availability or failover solutions offered by the database. A value of “none”, means that the JMS server will use the default persistent store that is configured on each targeted WLS instance.

If you don’t want to rely on the default Persistent Store, hit the “Create a New Store” button. This will continue navigation to another screen where you can select File Store or JDBC Store.

If you selected JDBC Store, in the next screen you need to select a JDBC data source or configure a new JDBC data source for the store.

– If you selected File Store, in the next screen you need to enter the path name for your storage (mind it, the directory must exist on your system, so be sure to create it before completing this step).

Complete this section by targeting a JMS server to an Oracle WLS server:

Click Save to complete the JMS Server creation.


Posted on

Advanced JAX-WS Web services sample chapter

This chapter discusses about what JAX-WS is and how to get started with developing services using it. The focus of the book will mainly be on JBossWS a Web Service framework developed as part of WildFly (formerly known as JBoss Application Server), that implements the JAX-WS specification (JSR 224, Java API for XML-based Web Services 2.0). Most of what will be explained, especially in this chapter, still applies to any JAX-WS implementation, though.

Continue reading Advanced JAX-WS Web services sample chapter

Posted on

From Tomcat to WildFly

from tomcat to wildfly
from tomcat to wildfly

Published: September 2014

Author: Francesco Marchioni

Pages: 105

 eBook (PDF) Price: 9.99 €

{quicksell file=”FromTomcatToWildFly-ItBuzzPress(2014).pdf” price=”9.99″ title=”From Tomcat to WildFly” currency=”EUR” customPayPal=”” emailDelivery=”on” requireRegistration=”” discount_rate=”” return_url=”” notification_email=”” rm=”” cbt=”” sub=”” addToCart=”on”}css_buttons/00001{/quicksell}


Any trouble in displaying this page? contact us at

Credit Card Payments are performed using Skrill Payment gateway. Skrill is the easy way to make safe and fast online payments internationally, with the highest security standards. Learn more about Skrill here

{tab Description|blue}

Apache Tomcat is a popular Web server and Servlet Container developed as an open-source project by the Apache Software Foundation since 1999. Today it is one of the most widely used platform for running Web applications both in simple sites and in large networks.
Nevertheless, the amount of libraries available on Apache Tomcat are usually just enough for very simple architectures which require just the HTTP protocol and a limited number of services; this caused the natural tendency to increase its capabilities with new extensions or modules such as Spring, Hibernate, JDO or Struts.
Although the purpose of this book is not to cast in a bad light on these architectures, we do believe that a comparative knowledge of other solutions can help you to choose the best for your projects. The term of comparison in this book is JBoss application server that is now called “WildFly” since its 8th release; WildFly is a fully compliant Java Enterprise Edition 7 container with a much wider set of available services and options compared to Tomcat. In this book, we will teach you how to port your existing Tomcat architectures to WildFly, including both the server configuration and the applications running on the top of it. We will also give you exposure to the most common pitfalls and drawbacks, which might happen during the migration.

{tab Table of Contents|green}

Chapter 1, Installing WildFly covers the first steps for getting started with the new application server, including installation as a service, start, stop and startup settings

Chapter 2, WildFly configuration introduces the core configuration of the application server and shows how to port the basic Tomcat Web server settings to WildFly.

Chapter 3, Core services configuration covers in detail two core services such as Database connectivity and JNDI which are to be ported in the new infrastructure

Chapter 4, Deploying applications, teaches how to deploy applications on WildFly using file system commands or a set of management instruments.

Chapter 5, Migrating Tomcat applications discusses about the steps needed for migrating your applications from Tomcat WildFly with special focus on Spring, Hibernate and Web services applications.

Chapter 6, Security configuration covers the foundation of the application server Security framework showing how to migrate the security configuration of your Tomcat web server to WildFly

Chapter 8, Clustering is about the nuts and bolts of WildFly’s clustering and the differences with the Tomcat Web server.

{tab The Author|red}

The Author 
Francesco Marchioni is an OpenGroup and Sun Certified Enterprise Architect employed for an Italian company based in Rome. Over the past 5 years, he has started an IT portal focused on JBoss products ( and has authored the following titles:


{tab Print Version|grey}
The Print version of the eBook will be soon available on Lulu bookstore. Print Book Price: 16,99 €




Posted on

Configuring JMS endpoints with WebSphere MQ

websphere mq configuring jms destinations

Configuring JMS endpoints with WebSphere MQ

You can configure both the Queue and Topic destinations for the WebSphere MQ messaging provider. In this section, we introduce how to create and configure a WebSphere MQ Queue destination. To configure a Queue destination for the WebSphere MQ messaging provider, complete the following steps:

  1. Click Resources > JMS> Queues. In the Queues window, click Scope (we will use Server scope in this sample), and then click New.
  2. Select the WebSphere MQ messaging provider option, and enter the following basic properties:

 websphere mq configuring jms destinations

Click OK. The new Queue is created. Save the changes to the master configuration.