How to Change Oracle JDeveloper 12c Font Size on Mac OS X

There are a few references to this on the Internet but they all seem to describe the behavior of Oracle JDeveloper 11g and not the current version 12c.

If you, like me, have been using Oracle JDeveloper 12c on a Mac OS X and wondered how can you change the IDE's font size then look no further :) Here are the instructions that worked for me:

• After installing Oracle JDeveloper 12c go to the Help menu and Check for Updates. Install the necessary extensions to do the kind of work you want (i.e. Mobile Application Framework) and restart JDeveloper.
• You'll probably see an undesired font size after you restart JDeveloper like the picture below. 

• Shut down JDeveloper and open a Terminal session.
• Go to /Users/<username>/.jdeveloper/system12.x.x.x.xx.xxxxxx.xxxx/o.jdeveloper.12.x.x.x.xx.xxxxxx.xxxx (i.e. /Users/Marcelo/.jdeveloper/system12.1.3.0.41.140521.1008/o.jdeveloper.12.1.3.1.41.150325.1239)
• Open the file ide.properties (you can use vi, nano, etc). Any text editor will do it.
• Find the line Ide.FontSize.Aqua=10. It should be something similar to:

 # The default Ide.FontSize for Mac OS X.  
 Ide.FontSize.Aqua=10  

• Update the IDE's font size replacing the lines above with the following:

 # The default Ide.FontSize for Mac OS X.  
 Ide.FontSize=10  

• Save and close the file. Start JDeveloper again and you should see the updated IDE's font size similar to the picture below.

Getting Started with HTML5 WebSocket on Oracle WebLogic 12c

The current release of Oracle WebLogic (12.1.2) added support to HTML5 WebSocket (RFC-6455) providing the bi-directional communication over a single TCP connection between clients and servers. Unlike the HTTP communication model, client and server can send and receive data independently from each other. 

The use of WebSocket is becoming very popular for highly interactive web applications that depend on time critical data delivery, requirements for true bi-directional data flow and higher throughput.

To initiate the WebSocket connection, the client sends a handshake request to the server. The connection is established if the handshake request passes validation, and the server accepts the request. When a WebSocket connection is established, a browser client can send data to a WebLogic Server instance while simultaneously receiving data from that server instance. 

The WebLogic server implementation has the following components:

•  The WebSocket protocol implementation that handles connection upgrades and establishes and manages connections as well as exchanges with the client. The WebLogic server fully implements the WebSocket protocol using its existing threading and networking infrastructure.
• The WebLogic WebSocket Java API, through the weblogic.websocket package, allows you to create WebSocket-based server side applications handling client connections, WebSocket messages, providing context information for a particular WebSocket connection and managing the request/response handshake. For additional information about the WebLogic WebSocket Java API interfaces and classes, visit the following resource: http://docs.oracle.com/middleware/1212/wls/WLPRG/websockets.htm#BABJEFFD
• To declare a WebSocket endpoint you use the @WebSocket annotation that allow you to mark a class as a WebSocket listener that's ready to be exposed and handle events. The annotated class must implement the WebSocketListener interface or extend from the WebSocketAdapter class.

When you deploy the WebSocket-based application on WebLogic, you basically follow the same approach using the standard Java EE Web Application archives (WARs), either as standalone or WAR module. Either way, the WebLogic Application Server detects the @WebSocket annotation on the class and automatically establishes it as a WebSocket endpoint.

Here is a simple application that creates a WebSocket endpoint at the /echo/ location path, receives messages from the client and sends the same message back to the client.

import weblogic.websocket.WebSocketAdapter;
import weblogic.websocket.WebSocketConnection;
import weblogic.websocket.annotation.WebSocket;

@WebSocket(pathPatterns={"/echo/*"})
public class Echo extends WebSocketAdapter{

@Override
  public void onMessage(WebSocketConnection connection, String msg){
      try{
          connection.send(msg);
      }catch(IOException ioe){
          //Handle error condition
      }
  }
}

On the client side, you typically use the WebSocket JavaScript API that most of the web browsers already support.


There are many samples out there that you can use to test the implementation above. One quick way of doing that is to navigate to http://www.websocket.org/echo.html and then point the location field to your WebLogic server. If you follow the sample available on https://github.com/mjabali/HelloWorld_WebSocket then you'll end up with something like ws://localhost:7001/HelloWorld_WebSocket/echo/ for the WebSocket server application.

The sample client provided will be available at http://localhost:7001/HelloWorld_WebSocket/index.html after the WebLogic deployment. See the README.md file on GitHub for additional instructions.

Have fun!

Getting Started with Oracle WebLogic 12c Dynamic Clusters

One of the new features introduced on WebLogic 12c (12.1.2) is the ability to create and add new managed servers to a clustered environment dynamically. Dynamic Clusters make the task of creating additional servers for scaling out your environment really easy.

 You no longer have to configure managed servers individually but instead you configure a cluster with the number of servers you want and the server template or the domain default values. From there the system maps out managed servers with attributes inherited from the server template.

Dynamic clusters can absolutely be a building block for elasticity in the cloud environment.

To create a sample WebLogic Dynamic Cluster configuration, follow the steps below:

- Download and install Oracle WebLogic Server 12.1.2 at http://www.oracle.com/technetwork/middleware/fusion-middleware/downloads/index.html

- Create a new domain called mydomain. If you need the instructions on how to create a WebLogic domain, go to: http://docs.oracle.com/middleware/1212/wls/WLDCW/newdom.htm#i1097775

- Start WebLogic Admin Server by running $WLS_HOME/user_projects/domains/my_domain/startWebLogic.sh | .bat where WLS_HOME is the directory where you have installed WebLogic

- Navigate to WebLogic console at http://localhost:7001/console (default settings used here)

- Under the domain structure, click on Machines and configure a new Machine called myMachine and the default settings.

- Create the Dynamic Cluster. Click on Cluster under the Domain Structure menu

- Click on the New button and then select Dynamic Cluster

- Specify the name for your Dynamic Cluster (i.e. myDynamicCluster) and press Next

- Select the number of dynamic server you want to configure, select the server name prefix and the template to be used when creating new servers. Click Next

- For this simple local configuration, specify the Machine Binding to be using the machine you created (myMachine) previously. Click Next

- Select the listen port for the first server in the dynamic cluster and then the SSL lister port for the first server in the dynamic cluster. The subsequent servers will be assigned with an incremental port number. Click Next

- You will be presented with the summary of your New Dynamic Cluster configuration. Click Finish and it will be created for you.

- The Summary of Clusters screens should show you the recently created Dynamic Cluster.

- Click on myDynamicCluster and then go to the Control tab. 

Before you can start any of the dynamic cluster members, make sure you have started the Node Manager on your machine with the following command: $WLS_HOME/user_projects/domains/my_domain/bin/startNodeManager.sh | .bat

As soon as the Node Manager is started, then go back to the WebLogic Admin Console, then select one of the servers in the cluster and then click Start. As a result of that operation, you should see the selected server up and running.

- The next step here is to start the other servers configured in your cluster and as a bonus you can dynamically add new members to the dynamic cluster.

 

I hope you found this sample tutorial and stay tuned for more!