Just a note to myself.

How to duplicate a table structure with / without data. Drop the where 1=0 to copy over the data as well.

As an example the Oracle HR scheme with the employees table is used and replicated to employees2 (see bold SQL line below).

Note, that not null constraints are replicated but primary keys, foreign key, unique constraints and triggers aren’t.

SQL> describe employees;
 Name Null? Type
 ----------------------------------------- -------- ----------------------------
 EMPLOYEE_ID NOT NULL NUMBER(6)
 FIRST_NAME VARCHAR2(20)
 LAST_NAME NOT NULL VARCHAR2(25)
 EMAIL NOT NULL VARCHAR2(25)
 PHONE_NUMBER VARCHAR2(20)
 HIRE_DATE NOT NULL DATE
 JOB_ID NOT NULL VARCHAR2(10)
 SALARY NUMBER(8,2)
 COMMISSION_PCT NUMBER(2,2)
 MANAGER_ID NUMBER(6)
 DEPARTMENT_ID NUMBER(4)

SQL> 
SQL> create table employees2 as select * from employees where 1=0;

Table created.

SQL> describe employees2;
 Name Null? Type
 ----------------------------------------- -------- ----------------------------
 EMPLOYEE_ID NUMBER(6)
 FIRST_NAME VARCHAR2(20)
 LAST_NAME NOT NULL VARCHAR2(25)
 EMAIL NOT NULL VARCHAR2(25)
 PHONE_NUMBER VARCHAR2(20)
 HIRE_DATE NOT NULL DATE
 JOB_ID NOT NULL VARCHAR2(10)
 SALARY NUMBER(8,2)
 COMMISSION_PCT NUMBER(2,2)
 MANAGER_ID NUMBER(6)
 DEPARTMENT_ID NUMBER(4)

WebLogic 12.2.1 is out since Oracle Open World 2015 and comes with a new RESTful management interface.

• RESTful management for 12.2.1 is a rewritten and different implementation.
  The previous two implementations supported only a small subset of JMX attributes, you could only read them, URLs and versioning were different.
• The new URL format is:

   http://server:port/management/weblogic/latest/...

  if you scripts still contain /wls/ you are using the previous format.

• Access to all WebLogic JMX MBeans and attributes is supported now.
• Unlike in the previous version, RESTful management is turned on per default.
• Unlike in the previous version, RESTful management is available on admin and managed servers.
• The URL syntax is modelled after the WLST syntax (WLST tutorial  in this screencast).
• A simple HTTP GET example (just type it into your browser), e.g. to retrieve name and state runtime values for a managed server named surf1:

  http://localhost:7001/management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/surf1?links=none&fields=name,state

  Response:
  { "name": "surf1", "state": "RUNNING" }

• Another example to create a new server surf7 using curl:

  curl –v --user weblogic:welcome1 \
   -H X-Requested-By:MyClient \
   -H Accept:application/json \
   -H Content-Type:application/json \
   -d "{ name: 'surf7' } "
   -X POST \http://localhost:7001/management/weblogic/latest/edit/servers

• Within the /edit subtree, edit sessions are implicit.
• To manually start/cancel/activate edit sessions:
  /edit/changeManager/startEdit|cancelEdit|activate
• Unlike the previous version of the RESTful management where HTTP OPTIONS was used to get a JSON form of possible values e.g. when creating a ressource, now /ressourceCreateForm is used, e.g. you can retrieve the values to create a server with the following HTTP GET:

  http://localhost:7001/management/weblogic/latest/edit/serverCreateForm

• You can issue bulk requests, which runs a search of a set of specific JSON nodes and returns the results at once. As shown in the following example, an HTTP POST operation to the following URL

  http://localhost:7001/management/weblogic/latest/domainRuntime/search

  and using the following JSON as payload:
  

More?

More interesting facts about the RESTful management interface:

• The RESTful management interface comes with very good error messages if something goes wrong.
  However, if  you try to update a property that cannot be overwritten, e.g. the server name of a managed server, it will be silently ignored. This is intended behaviour.
• In the curl example above all(?)  -H options could be omitted (if you were a sloppy person, but I guess you aren’t). This is true for all HTTP verbs except HTTP POST, then X-Requested-By header is required to prevent cross-site request  forgery (CSRF).
• You could also get access to all WebLogic MBeans and attributes using the highly popular open source Jolokia, as I explained already in 2012. Jolokia works for every major application server and also supports bulk requests. Ever wondered where the chili on my WebLogic book comes from?
  Jolokia also involves using real MBean names and is therefore more complicated for the typical WebLogic user. Also it involves adding Jolokia as a JVM agent, proxy, or WebLogic deployment. So most typical WebLogic users will be better off using the built-in RESTful management interface.
  I was planting some real spicy Jolokia this year. Two tiny crumbs of dried Jolokia is enough for a Chili con Carne with 500g of meat serving at least 3 people. Give it a try!

More about WebLogic 12.2.1?

Some more examples of the RESTful management, and also 11 additional “things” about WebLogic 12.2.1 are shown in a presentation I’ve done at Oracle Open World 2015:

WebLogic 12.2.1 is available since Open World 2015.

Some news regarding Java and WebLogic 12.2.1:

• WebLogic 12.2.1 requires Java 8 (JDK 8) as a runtime.
• WebLogic 12.1.3 can be used with Java 7 or Java 8. Using WebLogic 12.1.3 with Java 7 caused warnings because of the permspace settings in the WebLogic start scripts. Permspace is removed from JDK 8, so also these warnings are gone now with WebLogic 12.2.1 and JDK8.
• JDK 8 comes with Nashorn JavaScript engine. Try the jjs command line tool.
• Main reason from a development perspective to upgrade: WebLogic 12.2.1 finally supports Java EE 7.
• WebLogic 12.2.1 makes use of changes in the JVM. In JDK 8u40 a new feature was introduced to the JVM called resource management. Together with the G1 garbage collector WebLogic 12.2.1 uses this commercial feature to track resource usage (CPU, retained heap, # open file descriptors). It is enabled as follows:

  java   -XX:+UnlockCommercialFeatures  -XX:+ResourceManagement ...

WebLogic / Coherence / JCS SIG

I will be still travelling in Peru after delivering a presentation for the leading API management, microservices, and container conference SOALatam  in Lima, so I won’t be able to attend, but there is an interesting special interest group (SIG) meeting happening in Munich Germany if you want to know more about what was announced at Open World 2015. You can register here for the SIG.

DOAG 2015

Even before the SIG, if you are attending DOAG conference in Nürnberg this year don’t miss out my presentations about WebLogic 12.2.1 and WebLogic with Docker.