Version: 12.1.1 (developer edition, ZIP, no installer)
Installation
unzip wls1211_dev as follows

In order to be able to work with this edition we have to call configure.cmd. This basically unpacks all jars, create the registry.xml and wlserver\.product.properties
To have some reusable snippets I have created additional scripts in the new MW_HOME
env_wls12c_dev.cmd
@echo off
@rem ***************************************************************************
@rem This script is used to set the environment for
@rem Oracle WebLogic Server 12.1.1 dev ZIP edition
@rem ***************************************************************************
set MW_HOME=C:\oracle\product\12.1.1\middleware
set JAVA_HOME=C:\oracle\product\11.1.2.1\middleware\jdk160_24
set JAVA_VENDOR=Sun
install_wls12c_dev.cmd
@echo off
@rem ***************************************************************************
@rem This script is used to install Oracle WebLogic Server 12.1.1 dev ZIP edition
@rem ***************************************************************************
call env_wls1211_dev.cmd
title Installing WLS 12.1.1.0...
call %MW_HOME%\configure.cmd
pause
Now execute install_wls12c_dev.cmd
In order to create a domain by configuration wizard
a) call env_wls12c_dev.cmd
b) %MW_HOME%\wlserver\common\bin\config.cmd
RESTful Management Service API
Sounds cool...lets try
Activate by Domain > Configuration > Advanced Configuation > Enable RESTful Management Services
=> (restart required)
After restart you will notice the following in the output
INFO: Scanning for root resource and provider classes in the packages:
weblogic.management.rest.resources
weblogic.management.rest.provider
13.12.2011 00:03:13 com.sun.jersey.api.core.ScanningResourceConfig logClasses
INFO: Root resource classes found:
class weblogic.management.rest.resources.ApplicationResource
class weblogic.management.rest.resources.TestResource
class weblogic.management.rest.resources.ClusterResource
class weblogic.management.rest.resources.DataSourceResource
class weblogic.management.rest.resources.ServerResource
13.12.2011 00:03:13 com.sun.jersey.api.core.ScanningResourceConfig logClasses
INFO: Provider classes found:
class weblogic.management.rest.provider.CollectionResponseXmlProvider
class weblogic.management.rest.provider.ItemResponseJsonProvider
class weblogic.management.rest.provider.CollectionResponseJsonProvider
class weblogic.management.rest.provider.CollectionResponseHtmlProvider
class weblogic.management.rest.provider.ItemResponseHtmlProvider
class weblogic.management.rest.provider.ItemResponseXmlProvider
13.12.2011 00:03:14 com.sun.jersey.server.impl.application.WebApplicationImpl _i
nitiate
INFO: Initiating Jersey application, version 'Jersey: 1.9 09/02/2011 11:17 AM'
(=> This is good news! It states that some RESTful service will be available.)
After Restart open http://localhost:7001/management/tenant-monitoring/servers
(the authorized users must be in the group Administrators or Monitors)

Login in as weblogic user and see the default HTML output

If you e.g. need better proccessable formats, JSON and XML are of course also supported. Let's see how it is done and what it looks.
Add Accept Header with application/json

Add Accept Header with application/xml

Currently there is REST support for Servers (all in a domain or specific one), Clusters ( all in a domain or specific incl server members), applications (all in a domain or specific app), data sources (all in a domain or specific).
With these capabilities it' possible to implement a custom monitoring solution. A slim mobile wls monitoring app (and more)! => Hands on;)
See doc for details of all available RESTful-Services in WLS12.1.1 http://docs.oracle.com/cd/E24329_01/web.1211/e26722/toc.htm
Collected Documentation links
Overview OTN: http://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html
WLS 12c Data sheet: http://www.oracle.com/us/products/middleware/application-server/oracle-weblogic-server-ds-1391360.pdf
WLS 12c online Documentation Library: http://docs.oracle.com/cd/E24329_01/index.htm
Usind RESTful Services With WLS 12c: http://docs.oracle.com/cd/E24329_01/web.1211/e26722/toc.htm
Dislikes
- Still many BEA* stuff in diffrent scripts. It would be nice to have a clean and straight product without any historical garbage.
- configure.xml : ProgramGroupName=BEA WebLogic Platform 10.3 (Integrated Build)....
Why there is still the need to have a programm group called "BEA WebLogic Platform 10.3"?
My suggestions: Oracle WebLogic Platform 12.1.1 or Oracle Fusion Middleware Platform 12.1.1, everythin else, but not 10.3!
Like
- Java EE 6 Support. (It took a long time..)
- Better Maven Support
- RESTful Management Service
- ZIP distribution. Although the file is called wls1211_dev.zip it is possible to create a domain in production mode by the configuration wizard. At least in a simple testdrive it worked for me.
-Startup time feels better than wls11g
- more to test...(-Dservertype=wlx to avoid loading EJB, JMS, JCA )