Blog Xebia France

WebLogic Persists Blind

The server of applications Weblogic allows to declare servers JMS. To every server JMS is linked one Blind, site intended Persist to persist JMS messages in case of complete failures between the publication of a message and its consumption. Two possible support:

• Queue Persistence Store, an accessible directory by the server Weblogic composed of one or several files of binary structures (.DAT)
• JDBC PERSISTENCE STORE, group of tables contained in a relational and accessible database across ' DataSource '. The structure of tables and their contents are an exclusiment managed by the server of applications.

The choice of one of both types of stocking is mainly dictated by pressures of architecture and of working; the advantages of the one are the disadvantages of other one.

Up to the version 8 WebLogic, it was impossible to be able to manage them, especially to be able to open them, analyse them or dumper the contents.

From version 9, the server of applications offers a tool: weblogic.store. Admin

Main orders are: open, dump and compact.

Read the continuation of this article

The plans of deployment WebLogic

"It would be necessary to be able to change the name of DataSource according to environments"
"Ouh, it is complicated, it is necessary to relax the archive of application MonApp and 5 files.war and 8 files.jar of ejb. This will take minimum 3 weeks, and without material!"

(Functionality "plans of deployment" described in this article is available from WebLogic 9)

During the previous article, we had shown how packager a pool of connections JDBC with EAR. It seems obvious that if this solution is interesting, she is sufficient to define this application in different environments plans (Recipe, Preproduction or Production). It is not possible that for every environment, it is necessary to open archive, to change the file XML with new parametres and to end up closing again it.
The idea of the plans of deployment is to leave archive such which and to link him at the time of deployment new parametres. A plan of deployment is a file XML which takes back all new parametres to be overloaded.
Read the continuation of this article

Review of the papers Xebia

The review of the papers of actuality Popular dance / weekly J2EE offered by Xebia.

Actuality editors / SSII

• GlassFish and MYSQL, first signs of integration
• IBM invests in EnterpriseDB
• DomainHealth: A tool of monitoring for servers Weblogic (9 and 10)

Agility

• Certification ScrumMaster, they speak about it

The corner of technology

• Spring WS 1.5: a strong potential to be made concrete
• Milestone 3 for Spring Java Configuration

Read the continuation of this article

Packagez your sources of data with WebLogic

This article inaugurates a series around often misread and advanced functions appeared in the last versions of the server of application WebLogic.

A J2EE application uses generally one or several sources of data (Datasources). Specification J2EE allows at best to classify the name JNDI of the source of data in the descripteur of deployment of application (or of the web - app). On the other hand, the complete definition of parametres of the source of data (Type, URL JDBC, Size of the Pool) is an operation specific for every server of application. When comes the time of the delivery of application except the environment of development (Integration, Recipe...) teams give generally the archive of application to be displayed and a document of installation in format Word. It describes operations, with the aid of many copies of screen, to be performed across the application of administration to declare and to define the sources of data before undertaking the deployment of the file MonApplication as such. This article shows how with the server of application Weblogic 9 +, it is possible to link, in application to display, group of its resources, especially, the definition of parametres of its sources of data.

Example: To illustrate my purpose, I will use an application web, MYWEBAPPLICATION, which shows information on a connection JDBC got by DataSource registered in the tree JDNI. This application is traditionally packag e in form of an archive web, MYWEBAPPLICATION.WAR, itself encapsul e in an archive MYWEBAPPLICATIONEAR.EAR.

Read the continuation of this article

Review of the papers Xebia

The review of the papers of actuality Popular dance / weekly J2EE offered by Xebia.

Actuality editors / SSII

• Weblogic Server 10.3

The corner of technology

• Release of Seam 2.0
• A wind of Websphere 7 to IBM
• Apache Wicket 1.3.0-rc1 released simple percentage!

Read the continuation of this article

JCONSOLE and WebLogic 9

JCONSOLE is an available tool from JDK 5.0 who is based on the IPA - INTERNATIONAL PHONETIC ALPHABET JMX to show and to follow the metric of a virtual machine Popular dance.
The different categories are:

• The state of memory and of garbages collections.
• Threads, list activity and, as on Thread dump.
• Load of classes.
• Coherent and the management of MBEANS.
• General information on JVM (ClassPath, Library Path, Argument of JVM).

There are two ways of linking JCONSOLE on a virtual machine Popular dance 5:

Read the continuation of this article

WebLogic Scripting Tools

In a previous post, I explained how to display MBEAN with Spring in WebLogic Server 8.1. I am going to show you how interact with this MBEAN with WLST.

WebLogic Scripting Tool (WLST) is an online tool of order which allows to watch and to manage authorities WebLogic Server. This tool of Scripting is based on language Jython [1], a realisation of language Python 100 % Popular dance. This tool originates, was developed for WebLogic 8.1.x. He is available in version 5.4 [2] on the site CodeShare, the repository of plans open source linked to the world of servers WebLogic. From the version 9.0 WebLogic Server, WLST was included into distribution and is completely supported by GAPED.

With WLST he is possible:

• To go through the shape of a domain and its parametres runtime.
• To edit the shape of a domain and to safeguard these modifications.
• To achieve all the MBEAN of the server (MBEAN WebLogic, MBEAN WebLogic INTEGRATION, Mbean WebLogic Portal, MBEAN defined by the users).
• To automate the procedures of deployment of application and of shape.

Read the continuation of this article

Display MBEAN with Spring in WebLogic Server 8.1

The specification linked to extensions of management, more known as JMX is one of the most ancient of JCP. She hits . However, it was validated only in July, 2000 and commonly used when very recently. He has JSE 5 needed to wait for the servers of application J2EE 1.4 or to see this technology becoming in great numbers broadcast in version 1.2. Before every editor offered his own realisation with incompatible versions between them.

The server of application WebLogic 8.1 uses this technology in great numbers to allow to configurer and to monitorer servers. The console of administration is only a graphic interface in this MBEANS (Management Bean). However it can be interesting to display additional MBEAN:

• MBEAN portrays ' Facade ': Existent Aggregation de MBeans to unify management and to limit calls
• MBEAN portrays 'Composite ': Exhibition of methods of high level which synthetize group of MBEAN and technical data
• MBEAN portrays ' Applicatifs ': Interface of management either at technical level (server of application) but fonctionelle

Here are therefore stages to be followed and traps to be avoided to display MBEAN with the framework Spring 2.0 in . The environment of development is Eclipse 3.2 with WTP.

• Let us create a plan of type "'Dynamic Web Project" (name WeblogicSpringMBean) with the target runtime 'Generic GAPED WebLogic Server 8.1'
• Let us add to the directory WEB-INF / lib, library spring and common-logging.jar.
• Let us implement our MBEAN of (very simple) test: fr.xebia.management. InfoMBean

Read the continuation of this article