About Oracle Java Cloud Service - SaaS Extension
Topics
-
Understanding the Oracle Java Cloud Service - SaaS Extension Architecture
-
About Supported Java EE_ Oracle WebLogic Server_ and Oracle ADF Applications
-
About Supported Interfaces to Oracle Java Cloud Service - SaaS Extension
-
About the Application Deployment Validation Process and Run-time Security
Version Support
This Oracle Java Cloud Service - SaaS Extension release supports the latest WebLogic Server PSU and JDK update.
Understanding the Oracle Java Cloud Service - SaaS Extension Architecture
As shown in the previous illustration, Oracle Java Cloud Service - SaaS Extension instances are hosted within the Oracle Cloud in a data center operated by Oracle. This architecture provides a great deal of power and flexibility. Advantages include:
-
Quick provisioning of new Oracle Java Cloud Service - SaaS Extension instances in a self-service fashion on the
cloud.oracle.com
page. -
The ability to choose the service's capacity, throughput, and high availability at provisioning time.
-
A fully-managed and operated environment from Oracle with high availability, scalability, and built-in disaster recovery.
-
Allows for the portability of applications between Oracle Cloud and on-premise environments.
Understanding the PaaS Infrastructure and Java Environment
The infrastructure of the Oracle Java Cloud Service - SaaS Extension runtime is not directly exposed to its service users. In other words, Oracle Java Cloud Service - SaaS Extension is not an Infrastructure as a Service (IaaS) solution. Despite this limitation, certain aspects of the infrastructure can be managed through the Infrastructure Classic Console interface of the Oracle Java Cloud Service - SaaS Extension as follows:
-
Type of Oracle Java Cloud Service - SaaS Extension instance (that is, basic, standard, enterprise). The type of Oracle Java Cloud Service - SaaS Extension determines the number of Java EE server processes, memory storage, and file system capacity for the service instance.
-
Identity domain to which the Oracle Java Cloud Service - SaaS Extension belongs. The identity domain determines the identity store and single-sign-on realm of the instance.
-
The association of an Oracle Java Cloud Service - SaaS Extension instance with a Database Cloud Service instance. This association makes the database instance available to deployed applications as a JDBC data source.
About Supported Java EE, Oracle WebLogic Server, and Oracle ADF Applications
You can create these kinds of environments:
-
Standard Java EE WAR (Web Application Archive) or EAR (Enterprise Archive) formats.
-
Applications that make use of Oracle WebLogic Server-specific extensions in release 10.3.6. See:
-
Oracle Application Development Framework (ADF) constructs in release 11.1.1.9.0. See:
About Supported Interfaces to Oracle Java Cloud Service - SaaS Extension
Interface | Description | More Information |
---|---|---|
Oracle Java Cloud Service - SaaS Extension Control |
A web-based management console that enables you to deploy and monitor your hosted applications. |
Using the Oracle Java Cloud Service - SaaS Extension Control |
Oracle Java Cloud Service - SaaS Extension SDK |
Provides utilities that facilitate the management of Oracle Java Cloud Service - SaaS Extension instances and the development of applications for the Oracle Java Cloud Service - SaaS Extension. |
About the Oracle Java Cloud Service - SaaS Extension SDK Downloading the Oracle Java Cloud Service - SaaS Extension SDK |
Oracle Java Cloud Service - SaaS Extension interface in Oracle JDeveloper IDE |
Provides tooling so developers can directly interact with target service instances as part of the development process. |
Using Oracle JDeveloper with Oracle Java Cloud Service - SaaS Extension |
Oracle Java Cloud Service - SaaS Extension interface in Oracle Enterprise Platform for Eclipse IDE |
Provides tooling so developers can directly interact with target service instances as part of the development process. |
Using Oracle Enterprise Pack for Eclipse with Oracle Java Cloud Service - SaaS Extension |
Oracle Java Cloud Service - SaaS Extension interface in NetBeans IDE |
Provides tooling so developers can directly interact with target service instances as part of the development process. |
Using NetBeans with Oracle Java Cloud Service - SaaS Extension |
About the Oracle Java Cloud Service - SaaS Extension SDK
The Oracle Java Cloud Service - SaaS Extension SDK is required if you want to integrate your service instance with one of the supported IDEs described in About Using Integrated Development Environments.
The Oracle Java Cloud Service - SaaS Extension SDK contains:
-
Command-line interfaces (CLI):
-
javacloud.jar
– general application management tasks -
File System Access Shell – local file system management
-
Configuration Shell – application and domain configuration
-
-
Apache Ant tasks
-
Apache Maven plug-in
-
Whitelist validation
-
Documentation
Note: See the
index.html
file under the/doc
directory for all SDK usage instructions. -
Sample applications
Note: See the
sample.html
file under theSDK_HOME
/doc
directory for all sample installation and usage instructions.
You can download the Oracle Java Cloud Service - SaaS Extension SDK and use its CLI-based utilities from Oracle. See:
About Using Integrated Development Environments
Topics:
-
Using Oracle JDeveloper with Oracle Java Cloud Service - SaaS Extension
-
Using NetBeans with Oracle Java Cloud Service - SaaS Extension
-
Using Oracle Enterprise Pack for Eclipse with Oracle Java Cloud Service - SaaS Extension
Use the Oracle Cloud Resources menu to access additional tools that enable you to directly interact with your Oracle Java Cloud Service - SaaS Extension instance.
You can download these tools and the Oracle Java Cloud Service - SaaS Extension SDK from: http://www.oracle.com/technetwork/topics/cloud/downloads/
Using Oracle JDeveloper with Oracle Java Cloud Service - SaaS Extension
Supported Versions:
Oracle JDeveloper 11.1.1.9.0. See http://www.oracle.com/technetwork/developer-tools/jdev/overview/index.html.
Documentation:
Documentation for the current releases of JDeveloper is available at http://www.oracle.com/technetwork/developer-tools/jdev/documentation/index.html.
Using NetBeans with Oracle Java Cloud Service - SaaS Extension
Supported Versions:
NetBeans 7.4 + Update plug-in for Oracle Cloud. See http://www.netbeans.org.
Documentation:
The official NetBeans documentation contains information on using the IDE's Oracle Java Cloud Service - SaaS Extension integration capabilities. See http://netbeans.org/kb/docs/web/oracle-cloud.html
Using Oracle Enterprise Pack for Eclipse with Oracle Java Cloud Service - SaaS Extension
Oracle Enterprise Pack for Eclipse (OEPE) provides tools that make it easier to develop applications using specific Oracle Fusion Middleware technologies and Oracle Database. For Oracle Cloud, OEPE provides direct deployment to Oracle Java Cloud Service - SaaS Extension, integrated whitelist scanning to check for errors before deployment, integration into the Oracle Java Cloud Service - SaaS Extension Control, and log viewers to check on the status of the application.
Supported Versions:
OEPE 12.1.2.3 (and higher) . See http://www.oracle.com/technetwork/developer-tools/eclipse/overview/index.html
.
Documentation:
Documentation for the Enterprise Pack for Eclipse integration with the Oracle Java Cloud Service - SaaS Extension is available from Oracle. See Oracle Cloud Tools.
http://docs.oracle.com/cd/E27086_05/help/oracle.eclipse.tools.cloud.doc/html/index.html
About Managing Application Security
Special instructions are required for managing the security of the Java EE and ADF applications that have been deployed to an Oracle Java Cloud Service - SaaS Extension instance.
Topics
Default User Authentication
All Java EE and ADF web applications deployed to an Oracle Java Cloud Service - SaaS Extension instance are automatically secured. When users access an application deployed on Oracle Cloud the default authentication mechanism requests their user ID, password, and the name of the identity domain.
Once logged in, users are authenticated for applications. By default (that is, if no specific configurations are defined), only users who have been authenticated through Single Sign-On (SSO) can access a deployed application, but this includes users from any identity domain.
To provide finer- grained secure access to your Java EE or ADF applications, you can specify role-based authentication that can vary from being publicly accessible to restricted to only users within the same identity domain. See Securing Applications in Oracle Java Cloud Service - SaaS Extensionand Managing Users and Roles in Getting Started with Oracle Cloud.
Securing Web Services
Applications deployed on Oracle Java Cloud Service - SaaS Extension can invoke externally exposed web services (Outbound WS Client), as well as host web services (Inbound Web Service), that can be either non-secured or secured (for example, using WS-Security).
For guidelines on building secure JAX-WS web services, see Securing JAX-WS Web Services.
For more information on supported OWSM policies, see Predefined Policies in Oracle Fusion Middleware Security and Administrator's Guide for Web Services.
To use OWSM policies, you must attach them at design time:
About Third-Party Framework Support
Oracle makes no specific claims about a definite list of third-party libraries that should work within an Oracle Java Cloud Service - SaaS Extension environment.
In general, an application's use of most third-party frameworks should work within Oracle Java Cloud Service - SaaS Extension, so long as:
-
All dependencies can be embedded within the deployment archives.
-
All third-party JARS and their dependencies pass the Oracle Java Cloud Service - SaaS Extension whitelist. See Oracle Java Cloud Service - SaaS Extension Whitelist Validation.
See Supported Third Party Frameworks for Oracle Java Cloud Service - SaaS Extension for a list of supported third-party frameworks .