Packaging modules into an application

First, let's define what a module is on the context at hand; apart from the usual Java EE modules deployed in WebLogic Server—our applications and shared libraries, for instance—there are modules that group server resources such as JDBC and JMS components.

When we create a data source using WebLogic's administration console, we're actually creating a module inside the domain's configuration folder. This structure is read at the server's startup procedure to configure it properly.

Tip

You can check the folder /opt/packt/domains/tickets/config/jdbc to see the JDBC modules, Ticket and Theater, defined in our server.

There are two kinds of such modules, classified according to the way they are defined: globally-scoped (also called system modules) and application-scoped. The first is the most commonly found and used module—resources are created using WebLogic's administration console or WebLogic Scripting Tool (WLST) scripts, and are available to any application...