Knowledge Center Web and Java
On a recent project, I ran into a problem with an XML document, that had to be enclosed within another XML document, generated from a database query. The problem I ran into was the character encoding of the XMLElement function, which eventually was worked around with UPDATEXML.
In this blog post I would like to share with you several attempts to solve this problem, why they failed and the final solution to the problem.
Printing of official documents happened in a separate printing module. Whenever a document needed to be printed, an XML document was generated in a database query and sent to the printing module. Most of the data came from relational database tables, but pieces of standard text were supplied as XML documents by another party… and saved in our database in an XMLType column based on CLOB storage.
Our printing module expected to find these standard text XML documents within a tag in our generated XML document. Also both XML documents, our generated XML and the supplied XML, had different namespaces, this needed to maintained this way. The Oracle database version we were working with was 10.1.0.5.0.
In this post I will use a simplified version of the real XML More >
Recently I did an audit on a WebLogic 11g platform of one of our customers. There were many problems with the availability of their JAVA Applications. Some of the problems we’re platform related ( installation, configuration and infrastructure related) but a lot of them already existed in an earlier stage at application programming and configuration level.
So I decided to bundle some tips for JAVA programmers how they should configure their EJB, MDB and Servlet applications when they will be deployed on a WebLogic cluster.
This is an example of a typical EJB application architecture in WebLogic Server:
Some hints and tips:
Creating a EIS ConnectionFactory in your Database Adapter can be done with the WebLogic Administration Console, but of course this is also “scriptable”. What I needed was a script that created a Data Source with EIS Connection factory bound to the specific datasource.
First I created a properties file, let’s call it DsCf.properties. Everything between <> should be replaced with your own values:# Propertie file for creating datasource and EIS DB Adapter # Created by Michel Schildmeijer # Domain settings domainname="<your WLS DOMAIN>" adminurl=<WLS HOST:Admin Port> adminusername=weblogic adminpassword=<passwd weblogic> #datasource settings datasourcename=<Name DataSource> datasourcedatabasename=<database> datasourcetarget=<targeted manaegd server> datasourcefilename= datasourcename + '.xml' datasourcejndiname= 'jdbc/' + datasourcename datasourcedriverclass=oracle.jdbc.OracleDriver datasourceurl=jdbc:oracle:thin:@<db host>:1521:<db sid> datasourceusername=<db user> datasourcepassword=<db user password datasourcetestquery=SQL SELECT * FROM DUAL #EIS Connection Factory settings connfactname=eis/DB/<Connection factory More >
Where as in WebLogic 11g JPA was not support by default, in WebLogic 12c it is the default persistency provider.JPA 2.0 is part of JAVA EE 6.
I was trying some new JAVA EE 6 features in WebLogic 12c, so here is a is a way to create a Web Application with JPA under WebLogic 12c
Some of the JAVA EE 6 specifications weâ€™re already supported in WebLogic 11g. JPA 2.0 was one of them. Though version 1.0 was the default. 2.0 also worked.Unless an explicit <provider>…</provider> wass specified in the persistence.xml file of a deployed application, WebLogic 11g used OpenJPA/Kodo by default.
The default JPA provider setting is exposed via a new MBean: JPAMBean on the DomainMBean, and persists the configuration into the config.xml file.
Furthermore, you needed to install the patch QWG8 – Enable JPA 2.0 support on WebLogic Server.
To make it work on 11g, you had to use Oracle TopLink as the persistency provider like the image shows youÂ in the WebLogic Admin Console
Now for 12c this is not needed anymore, TopLink will be the default JPA Provider
At December the 1st, 2011, Oracle announced it’s new major release, the 12c release. As Oracle added the i (internet) at its 8 release, the g(gridcomputing) at its 10 release, now the focus will be on the c(cloudcomputing).
Many new features come out of the fact that Oracle has made its key application server ready for the cloud, that is, ready for to run on enigineered systems, in fact its own Exalogic machine, Oracle’s solution for implementing the cloud.
So let’s take a look what this new release brings us, in this blogpost. There are several new features available in the 12cNew or enhanced WebLogic 12c features
- JAVA EE 6 support all kinds of JEE6 specifications are implemented like :
- JSF 2.0,Java Servlets 3.0Â JPA 2.0 andÂ EJB 3.1.
- Managed Beans 1.0
- WebLogic 12c also supports supports Java SE 7 (and Java SE 6).
- Java language optimizations and Internationalization
- Client and server support
- SSL/TLS 1.2 in JSSE to support JAVA Socket Transport security
- Converged Java VM:JRockit and HotSpot are Â incorporated with the best features from both.The JVM convergence will be a multi-year process, which was confirmed during my presence at Oracle’s Publisher Seminar 2011 during
A few months back, in August, I received an electronic copy of the book: “Oracle WebCenter 11g PS3 Administration Cookbook” by Yannick Ongena (Packt Publishing, 2011). I promised you then you write a review on it and now I finally deliver on that promise.
Main conclusion: if you want to get started with WebCenter 11g, this book will help you take your first steps on many of the most important areas of Web Center (Portal). The recipes in the book provide clear instructions on getting things going. Where the Web Center documentation can be a little overwhelming – the Web Center Developer’s Guide has 69 chapters and presumably over 1500 pages of content – Yannick’s book is clear, straightforward and easy to follow.
I am not exactly sure about the intended reader for the book. The title and Yannick’s introduction mention Administration and a technical person responsible for administration. Many recipes however discusses topics and tasks I would associate with developers. So presumably both administrators and developers will benefit from the book. Note that the traditional roles of developer, administrator and end user are not as clearly defined with Web Center Portal: business or end More >