Posts Tagged ‘Java Cloud Service’

 

clip_image001We are pleased to announce the availability of the 16.2.1 release of Application Development platform with Java Cloud Service, Application Container Cloud Service, and Developer Cloud Service. This April release marks a major milestone, we saw the addition of a number of features, enhancements, and integrations.  This release is so big we’ve even had to add a Table of Contents to this email!

clip_image002Table of Contents

Java Cloud Service
  Oracle WebLogic Server 12c (12.2.1) with Java Required Files 12c (12.2.1)
  Multi-node WLS and OTD
  Oracle Database Cloud with RAC Support
  SSH Access page to manage keys
  Load Balancer HA capability
  Activity Status moves to Menu
  New patchesclip_image004
  Developer Cloud Service Enhancements
Application Container Cloud Service
  Performance Improvements
  Trial Quota Increases
  New Assets
  Developer Cloud Service Enhancements

Java Cloud Service

Oracle WebLogic Server 12c (12.2.1) with Java Required Files 12c (12.2.1)

  • This is the foundation for Oracle Fusion Middleware 12c (12.2.1). WebLogic Server 12c (12.2.1) is Java EE 7 compatible. The WLS 12.2.1 features are limited (1 managed server, no LB, 0-1 partition, no scale in/out, no Multitenancy tooling).

clip_image006
NOTE:

1. You must create a full Oracle Java Cloud Service instance, not an Oracle Java Cloud Service — Virtual Image instance, if you want to create a domain partition for your instance.

2. JCS continues to offer …

  • Oracle WebLogic Server 12c (12.1.3) with Java Required Files 12c (12.1.3). This is the foundation for Oracle Fusion Middleware 12c (12.1.3). WebLogic Server 12c (12.1.3) is Java EE 6 compatible.
  • Oracle WebLogic Server 11g (10.3.6) with Java Required Files 11g (11.1.1.7). This is the foundation for Oracle Fusion Middleware 11g (11.1.1.7). WebLogic Server 11g (10.3.6) is Java EE 5 compatible.

3. You can enable Oracle Coherence in Oracle Java Cloud Service when you provision an environment to run Oracle WebLogic Server 12c (12.1.3) or Oracle WebLogic Server 12c (12.2.1), and Enterprise Edition with Coherence. When enabled, the environment provides a predefined cache capacity out-of-the-box for the Coherence applications that you deploy to the cloud environment.

  • Oracle Coherence 12.2.1 Multi-Tenancy is supported, you can enable MT partitions on Coherence cluster post provisioning.

Support for Multi-node WLS and OTD is planned in an upcoming releases.

Support for Oracle Database Cloud – Database as a Service instances that were set up with the RAC option

  • This support allows Oracle Java Cloud Service instances to access the data from any database instance in the database cluster.
  • Coordinated backup between Java Cloud Service and Database Cloud Service with RAC is enabled.

An SSH Access page to view and manage SSH keys for Oracle Java Cloud Service instances in the identity domain

  • If the SSH private key that is used to access an Oracle Java Cloud Service instance becomes lost or corrupted, one can add a new public key to the service instance. Addition of a new public key to a service instance should also be done in order to comply with the organization’s security policies or regulations.

clip_image008Load Balancer HA capability

  • For high availability, a second load balancer node can be added when provisioning an Oracle Java Cloud Service instance. Alternatively, a second load balancer node can also be added to an existing instance from the Topology tab.

A new Menu icon next to the ‘Welcome!’ linkclip_image010

This displays information about the status of selected operations performed on Oracle Java Cloud Service instances. Note: This menu option replaces the Activity tab found in prior releases.
New patches

1. Patch Set Update (PSU) for Oracle WebLogic Server
2. Java Development Kit (JDK) update for Oracle WebLogic Server and Oracle Traffic Director.

You can see the availability of patches on the Administration tile and on the Patching tab

Developer Cloud Service Enhancements

Developer Cloud Service has added new options for using WebLogic Server deployment REST APIs when deploying from DevCS to JCS running WLS 12.1.3 and higher.

At our community workspace here (membership required) we posted:

About Oracle Java Cloud Service

Java Cloud Service is an enterprise-class application deployment platform for Java EE, WebLogic and Fusion Middleware .

Application Container Cloud Service

Performance Improvements

ACCS application creation and redeployment times continue to shrink.  Once the first application is created and the service is initialized, application creation, scaling, and update/redeployment are significantly faster than in the previous release.  These improvements are due to optimization in the usage of the underlying compute infrastructure.

Trial Quota Increases

Restrictions on the number of ACCS application instances has been lifted in trial accounts.  It is now possible for users to take advantage of the full 6 OCPU trial account quota to create more applications and to scale those applications out.

Developer Cloud Service Enhancements

Developer Cloud Service’s support for Application Container Cloud has been enhanced with:

1. New utilities for JavaScript and Node packaging and dependency management installed in DevCS Hudson by default (grunt, gulp, and npm)
2. New Deployment configurations targeting ACCS for Java-based applications. These can be used in the DevCS Deploy tab or in Build jobs either on-demand or continuously.
3. New Developer Cloud Service sample project to demonstrate creation, build, and deployment to ACCS containers.

Learn More

See the Oracle Application Container Cloud Service documentation What’s New page for more details and learn more at http://cloud.oracle.com/acc

At our community workspace here (membership required) we posted:

For free JCS trail services please see PaaS Demo Accounts

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_image002In this previous articleGetting started with Java Cloud Service on the Oracle Public Cloud (WebLogic as a Service) – I have taken  you on a introductory tour into JCS. That article describes how to get going – how to provision a JCS instance – associated with an instance in DBaaS and with backup set up with Storage CS.

In the article you are currently reading, I show you how to use this instance for deploying a Java EE application onto – and subsequently invoking that application.

Since the same consoles are available to us with JCS as with on premises WLS, we can perform an application deployment in the same way from the console by uploading a WAR or EAR file as we can do on premises. I tried my hand at a fairly large application – without any Java EE dependencies (no EJB, JMS or JDBC data source requirements): the ADF Faces Rich Client components Demo application – available from http://www.oracle.com/technetwork/developer-tools/adf/downloads/index.html . The downloaded file is about 105 MB. The subsequent deployment of this file to JCS fails: the step takes quite long – because 105 MB have to be uploaded again, from my laptop into the Oracle Public Cloud. This console could be extended by Oracle perhaps to also offer to upload directly from a URL. On three attempts, after about three minutes into the upload, the deployment process fails. Either on the JCS end or in the browser to server communication is a problem. I am not sure what it is caused by. For now, I will simply try my hand at a smaller WAR.

Plan B or Take Two at deploying a Java EE application

Instead of looking around for a suitable ready to deploy WAR file, it is probably even more rewarding to quickly develop a Java EE application, build it as a WAR file and deploy it to my new JCS instance. Using JDeveloper, I quickly whip up a JAX-WS application: a simple Java Class that with some JAX-WS applications is turned to a SOAP Web Service (by right clicking the Class and selecting the option Create Web Service):

The functionality of this service should be fairly obvious from the code. The WSDL that the derived service exposes can be previewed in JDeveloper:

Deployment of the service can be done from the project navigator: right click on the ViewController project: 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: Lucas Jellema,JCS,Java Cloud Service,PaaS,Cloud,WebLogic,WebLogic Community,Oracle,OPN,Jürgen Kress

 

clip_image002The Java Cloud Service (JCS) in the Oracle Public Cloud allows me to deploy Java EE applications such as JAX-RS and JAX-WS REST and SOAP Web Services, Servlet | JSP | JSF Web Applications, EJB and JMS artifacts and ADF applications to the public cloud and make them accessible to developers, testers and end users anywhere in the world. For components to be deployed to the JCS – I have to do nothing special (!) during development or deployment: anything that runs on premises will run in JCS.

In this article, I will describe some of my initial experiences with JCS: what did I have to do to get going the first time – from having nothing more but a (trial) subscription to JCS to deploying and running my first Java EE application on JCS. I thought this would be a very long article with a large number of tips and tricks and with deeply technical steps. I felt some reluctance to even get going – feeling a little daunted by a new world full of new terminology. As it turned out – this is not a long article and it certainly does not contain a lot of tips. My initial reluctance was misplaced. JCS is just WebLogic – hosted on a different machine than my laptop and with a different provisioning interface. The amount of cloud terminology is limited (cloud account, identity domain, service instance is probably the bulk of it – along with simple tooling: dashboard, service console). JCS builds on three other Oracle Public Cloud Services that we need to be aware of: DBaaS (Database), Compute Cloud Service and Storage Cloud Service.

You do not need guidance from me for all the steps you need to go through. I worked with an excellent tutorial on Oracle Help Center – Getting Started with Oracle Java Cloud Service – and I heartily recommend you do the same.

The steps (described in this tutorial) that you need to go through in order to have your first Java EE application running are:

  • (do: 5 minutes | then wait: days up to months) Get a [Trial] Subscription to the Oracle Java Cloud Service – for your Oracle account (the same one you use for OTN and any other interaction with Oracle); an Oracle Java Cloud Service trial environment or purchased subscription comes with Oracle IaaS Public Cloud Services, which provides you access to Storage CS and Compute CS – both of which underpin the JCS instance;
    Note: Database Cloud Service is a prerequisite of Java Cloud Service and is priced separately. When you request provisioning of an instance of JCS, you need to specify the DBaaS instance that it should make use of.  Read my previous article on DBaaS to get going with the Oracle Database as a Service offering and prepare a database instance.
  • (do: 5 minutes) Associate the [trial]subscription with an existing or a new Oracle Public Cloud account (and thereby to an identity domain)
  • (do: 5 minutes) Generate SSH keys (you can reuse the SSH key pair you may already have created to get going with Oracle DBaaS) 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_image002As part of our communities we do offer free PaaS accounts (only for partners in Europe, Middle East and Africa. In case you are not part of EMEA please contact your local partner manager):

· Java Cloud Service & Mobile Cloud Service PaaS Demo Accounts (WebLogic Community membership required)

· Integration Cloud Service & Process Cloud Service PaaS Demo Accounts  (SOA Community membership required)

Watch the GSE Overview Video! Get an overview of what GSE is and how you can use GSE to help you sell. You can also get long running dedicated PaaS instances, therefore please send us details about your use cases.

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

Had I been working in Operations and on-call at an organisation using Java Cloud Service then it appeared I may well have been rudely woken up last night! At around 2am in the UK this email innocently dropped into my mail box:

This warning of an impending outage to Java Cloud Service was closely followed by one for Database Cloud Service. Judging by the email – “during the maintenance your services will be unavailable” – it seems an hour and a half later the instance failure notifications (from Enterprise Manager or Nagios etc) would have probably started coming in.

Then at 4:36am I had an email to say my JCS was now available again, and 5:11am to say my DBCS was too so, a total outage according to the emails of just under 2 hours. However when it happened all of my Java and Database test instances (test) were down already but as far as I can tell no changes were actually made to them (they were not started up for example) – be sure to read my conclusions at the end of this post!

What’s New?

So this evening I’ve been having a good look round. The most obvious first change is that you can provision new domains with WebLogic 12.1.3.0.4, and existing full JCS ones (i.e. the ones including ‘cloud tooling’ for patching) have the following patches 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

clip_image002We are pleased to announce the availability of Oracle Java Cloud Service (JCS) in EMEA datacenters.
This option can now be selected in WebQuote, for new customers.  Please note that this announcement applies to both the metered and non-metered SKUs of Java Cloud Service and Java Cloud Service Virtual Image. Java Cloud Service SaaS Extenstion has been available for provisioning in EMEA for quite a long time now.

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

Learn how to create and manage your Oracle Java Cloud Service instances and deploy your first application to the cloud. For more information, see the documentation.

Attend the free on-demand training 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