Monday Jul 21, 2014

Elastic PaaS with WebLogic and OpenStack, part I By Jernej Kaše

In my previous blog I described the steps to get OpenStack on Solaris up and running. Now we'll explore how WebLogic and OpenStack can work together to deliver truly elastic Middleware Platform as a Service.
Middleware / Platform as a Service goals
First, let's define what PaaS should be : PaaS offerings facilitate the deployment of applications without the complexity of managing the underlying hardware and software and provisioning hosting capabilities.
To break it down:
- PaaS provides a complete platform for hosting solutions (Java EE, SOA, BPM, ...)
- Infrastructure provisioning (virtual machine, OS, platform) and managing is hidden from the PaaS user [administrator or developer]
- Additionally, PaaS could / should define target SLAs, and the platform should ensure the SLAs are meet automatically.
PaaS use case
To make it more tangible, we have an IT Administrator who has the requirement to deploy a Java EE enterprise application. The application is used by external users who need to submit reports by the end of each month. As a result, the number of concurrent users will fluctuate, with expected huge spikes around the end of each month. Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Getting the most out of WLDF Part 3: Notifications by C2B2

his blog directly follows on from part 2 on watches, so if you haven’t already read that then you should probably go and do that now. You can still create notifications without having any watches configured; you just won’t receive anything on them. In the last post, I had created two watches, one Server Log watch and one Collected Metrics watch. In this post, I will create notifications to work with these watches.

What are notifications?
WLDF notifications are nothing more than a particular configuration for alerting based on a condition. Think of them as channels of communication; unless something is sent down those channels, they will stay empty. The forms that these channels can take are:

  • SMTP Email
  • JMS Message
  • Diagnostic Image
  • JMX Notification
  • SNMP Trap

Which notification should I use?
There’s no right or wrong when it comes to choosing notification methods, but there is certainly annoying and non-annoying! Of the notification methods above, all but email are passive methods of alerting people concerned. The reason I classify them as passive is that you, as the end-user who wants to be notified, must perform some sort of action to consume that notification. For example, to consume JMS message data, you must use a JMS client and would likely process the data automatically, perhaps for graphing. Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Search

Archives
« July 2014 »
SunMonTueWedThuFriSat
  
11
12
15
19
20
  
       
Today