CERN WebLogic CLI tool is written in Python. A project is being realized in an object oriented way to contribute towards flexibility, modularity and legibility of a solution and the modules of the system are designed to maximize end-user productivity. It is a comprehensive solution using WebLogic RESTful management services and providing a simple way of interacting with a user and possibility of integration with third party systems. The goal of the system is to provide a set of standardized functionality for managing resources shared in a distributed environment composed of hundreds WebLogic servers. Among them there are significant and business-critical applications. The product hides administration mechanisms by removing the complexity of the REST interface and shares user friendly abstraction layer. The system together with Oracle WebLogic Server follows the client- server architectural style.
The power of the REST
REST is an architecture style for designing Web services that focus on a server’s resources. It is a lightweight alternative to Web Services (SOAP, WSDL) or RPC. REST interfaces can be used by any programming language. One of the key characteristics of a RESTful service is that communication is stateless. It means that a complete request doesn’t require the server to retrieve any kind of application context or state. Each request from any client contains just essential information necessary to service the request, and session state should be held in the client side. Regarding managing Oracle WebLogic Server, REST management API is faster than WebLogic Scripting Tool.
Abstractions in a RESTful system:
- Server resources
- Resource representations
- Actions on server resources
What is a RESTful resource? It is anything that can be accessed within the scope of designed REST service over the Web. Representation of a resource is sent back from server to client as a result of the request. Server resource cannot be sent or received, only its representation can be sent. Representations can be of a various forms, such as JSON, XML or even plain text. Actions are used to operate on server resources. RESTful clients use HTTP requests for all four CRUD (Create / Read / Update / Delete) operations. The key features are presented below.
The Good, the Bad, and the Ugly – WebLogic API
Although REST is very simple, lightweight and fast, there are some requests that might make a tremendous burden on WebLogic Server. For instance, if the domain is full of logs, queries for all of them may take longer. Likewise, starting a laden server can put the user’s patience to the test. REST lightness needs to be separated from the operation weight. REST requests are hitting the target very quickly, but demanded action may take much more time.
Another downside is an impression that WebLogic REST API is not complete. The API does not address yet full management functionality for WebLogic Server. Let me give an example. It is still impossible to create a domain, a cluster or even a server with the API – here it is still necessary to use a more traditional way, for example Administration Console. 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
Technorati Tags: WebLogic,WebLogic Community,Oracle,OPN,Jürgen Kress