clip_image002
With the trend of container technologies going on it is great to see Oracle is providing the so called Application Container Cloud Service. Its current architecture is based on Docker and allows to run Java SE and Node.js applications in its current version. See the the following diagram

The Load Balancing, dockerizing and scaling is fully transparent. From developer perspective you are deploying a ZIP containing a manifest.json with a command property that states what should be executed once the deployment has been installed on the specific container.
In the following figure you see the overview screen of Application Container Cloud service (ACC).

clip_image003Next lets create an app and deploy it to ACC. For Java SE lets see how that manifest.json looks like

Java SE App

The important properties are runtime / majorVersion and command. It states that the deployment needs Java 8. The application is started with the given "java -jar …" command. Currently two working samples are provided, one works with embedded Tomcat the other works with Grizzly Http Server. Here is how a typical Main.java class would look like. 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 Forum Wiki

 

clip_image002Microservices implemented in JavaScript running on NodeJS are becoming quite popular lately. In order to gain some experience with this, I created a little in memory NodeJS cache service. Of course statefulness complicates scalability, but if I would also have implemented a persistent store to avoid this, the scope of this blog article would have become too large. Please mind that my experience with NodeJS is limited to a NodeJS workshop from Lucas Jellema and a day of playing with NodeJS. This indicates it is quite easy to get started. In this blog I’ll highlight some of the challenges I encountered and how I solved them. Also I’m shortly describing what Oracle is doing with NodeJS. Because the JavaScript world changes rapidly, you should also take into account the period between when this blog is written and when you are reading it; it will most likely quickly become outdated. You can download the code from GitHub here.

Choosing an IDE

In the Java world there are several popular IDE’s such as JDeveloper, Eclipse, Netbeans, IntelliJ. For JavaScript, the IDE’s I’ve heard most about from JavaScript developers (as a newby it helps to talk to people with experience) are Microsoft Visual Studio Code and Jetbrain’s WebStorm. Netbeans also has JavaScript support and is the IDE of choice for Oracle JET development. I have not looked into Netbeans yet. I decided on Microsoft Visual Studio Code since WebStorm requires a paid license.

NodeJS package manager

The NodeJS package manager is npm. npm can install modules globally and locally. Supporting tools like ‘mocha’ for testing and ‘typings’ for TypeScript support are good candidates to install globally. Do keep track though of your globally installed modules since if you want to reproduce your environment somewhere else, these modules could be dependencies (especially in your build process). You can configure local dependencies in a package.json file. When you do a ‘npm install’, modules mentioned in that file are installed locally in the node_modules folder of your project. If you want to also update the package.json, you can do ‘npm install –save’. This allows you to easily update versions of modules. When your node_modules directory is corrupt because you for example interrupted a module download, you can just remove the node_modules directory and rebuild it from the package.json file.

Code completion

As a spoiled modern developer, I need code completion! This especially helps a lot when you are unfamiliar with a language and want to explore what you can do with a specific object or how to use standard libraries/modules. JavaScript is not strongly typed. You need type information to provide code completion. Microsoft has provided the open source TypeScript to help with that. 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 Forum Wiki

 

clip_image002Introduction

Using the multi-tenancy features of WebLogic Server 12.2.1, administrators can use domain partitions to share computing resources in the WebLogic domain across different tenants. Administrators can also simplify administration and management by consolidating multiple WebLogic domains into multiple domain partitions in a single domain.

Yet sharing the same resources across multiple partitions works against isolating the partitions from each other for security and privacy reasons. This short article explores that tension and highlights how you can use the multi-tenancy features to optimize sharing or isolation.

Virtual Targets

To see how all this works we need to talk about virtual targets in WebLogic Server and their role in multi-tenancy. Briefly, a virtual target does two things:

  1. It establishes how end users connect to apps in a partition (using a partition-specific URI prefix, a partition-specific port number, etc.)
  2. It refers to a WebLogic cluster (or individual server).

The WebLogic administrator creates one or more virtual targets, associating each with a server or cluster, and creates one or more partitions, linking each partition with one or more virtual targets. These associations control where the apps and resources in each partition will run.

Sharing Resources

Here is how you would set up a domain’s virtual targets and partitions to maximize resource sharing.

This is the typical consolidation use case – often called the PaaS (platform-as-a-service) model. Several divisions of one enterprise – for example, HR and Finance for one company – might have their own separate partitions in a single WebLogic domain but want to share the computing resources.

In the simplest example, the WLS administrator creates a virtual target for each partition and links each virtual target with the same cluster (including managed servers MS1 and MS2). Applications and resources from different partitions run in the same managed servers. In this way the WebLogic administrator can share the hardware and software resources on those servers – including the Java virtual machine – across the partitions.

This lets the administrator achieve higher density. Because the partitions are part of the same enterprise, isolating the partitions’ code and data from each other might not be a major concern.

In contrast, if a single WebLogic domain is hosting different enterprises, each as a different partition, questions of isolation become much more important.

Even so, sometimes it might still make sense for different partitions to share the same managed servers. For example if you are offering access to a suite of applications to different customers you have full control over those applications. If you are confident in the applications themselves you might be willing to have different partitions share the same managed servers, comfortable that the apps themselves are well-behaved and will isolate data for one partition from data for another. 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 Forum Wiki

 

clip_image002My presentation and Live DEMO at “Oracle Hardware Solutions Event”. Demonstrated live Java Server Loader (JSL) on Solaris Sparc T5-2 Server and did performance tests (CPU, Memory, Network Socket) instantly at session duration.

Artifacts:

  • Java Server Loader (JSL)
  • WLSDM (WebLogic Smart Dashboard and Monitoring)
  • Oracle WebLogic (12.2.1)
  • Oracle Solaris 11.3
  • Java 1.8_071

Read the complete article here and Slideshare Link 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 Forum Wiki

 

clip_image002WLDF is a diagnostic framework inside Weblogic, which provides several functionalities to measure, track and monitor a domain at runtime. With WLDF, administrators can set alarms on specific incidents and automatically execute some tasks when certain events are triggered.

One good starting point to learn about WLDF is Radu Dobrinescu’s blog. It provides a compressive tutorial on how to monitor common events in Weblogic. The newest version of Weblogic (12.2.1) has made some changes and improvements to the WLDF Framework with the inclusion of the new smart rules.

Smart rules provide a set of predefined rules that represent the most common monitored events in Weblogic domains. This blog is going to show how to monitor stuck threads and overloaded datasources and send an email if one of these events occurs.

1. Creating a mail session

The first task required is to create a mail session in order to reference it in the WLDF watches. The following steps explain how to define a mail session.

  • In the domain structure go to Services -> Mail Sessions -> New
  • Enter a name, a JNDI name and your user account in Weblogic. In the JavaMail properties enter at least the host and port of the SMTP server and the sending email account, like this:

mail.smtp.port=2525

mail.smtp.from=“soa_admin@example.com“

mail.smtp.host=localhost

  • Press “Next”.
  • Select the server where you want to target this mail session and press “Finish”.

2. Create a Diagnostic Module

A diagnostic module is and administrative unit that contains collected metrics, instrumentations, policies and actions. The following steps show how to define a diagnostic module. 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 Forum Wiki

clip_image002

This recorded demonstration will show how you can use Oracle Enterprise Manager Cloud Control 13c to track compliance of your WebLogic Server environments to the Defense Information Systems Agency’s (DISA) Oracle WebLogic Server 12c Security Technical Implementation Guide (STIG). Watch the video 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 Forum Wiki

 

clip_image002 The release of WebLogic 12.2.1 has introduced some cool features. One of them: the domain partition exports. Could this feature really reduce all the deployments to just one deployment? Let’s find out!

To fully grasp the idea of just needing one deployment, we need to explain Domain Partitions first. As Oracle states: “A domain partition (partition for short) is an administrative and runtime slice of a WebLogic domain. In many ways you can think of a partition as a WebLogic micro-container.” A Domain Partition can be assigned as micro-containers called Resource Groups. Resource Groups can contain WebLogic components such as applications, libraries, JMS Servers and Data Sources.

Resource Groups and Templates

In previous WebLogic versions you would deploy WebLogic components to the whole domain (global) and have it targeted to servers or clusters. Starting from 12.2.1, you can now also deploy these WebLogic components to specific Resource Groups and Resource Groups Templates. Resource Groups can be used to group every component needed in a business flow to one container.

Using Virtual Targets, Administrators can specify on which servers or clusters the Domain Partition is available. 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 Forum Wiki