Create an Oracle Java Cloud Service Instance by Using a QuickStart Template
Note:
QuickStart is not available for Oracle Cloud accounts that include only Oracle Cloud Infrastructure regions, or include a mix of Oracle Cloud Infrastructure and Oracle Cloud Infrastructure Classic regions.Note:
You must have a Universal Credits subscription in order to use QuickStart. This feature is not available to other subscription types.
Create a QuickStart Instance
Use the QuickStart page to choose from one of the available Oracle Java Cloud Service templates. These templates are executed with Oracle Cloud Stack.
The Bring Your Own License (BYOL) option enables you to bring your on-premises Oracle WebLogic Server licenses to Oracle Cloud. BYOL instances are billed at a lower rate than other instances. See Frequently Asked Questions: Oracle BYOL to PaaS. If your cloud account includes the BYOL entitlement for Oracle Java Cloud Service, then all QuickStart instances use BYOL. If you prefer not to use BYOL, then create a custom service instance.
Note:
Before you scale up or scale out a BYOL instance, you must have enough WebLogic Server licenses for the additional OCPUs that will be allocated to the instance after it is scaled.Oracle Java Cloud Service generates the user name and password that you will need to administer the Oracle WebLogic Server and the Load Balancer components in the selected configuration. This same password is also used to administer the Oracle Database. Oracle Java Cloud Service generates an archive file for you to download, which contains:
-
A text file with the administrator user name and password for WebLogic Server and the Load Balancer
-
A copy of the Secure Shell (SSH) public key that will be associated with each of the nodes in this configuration
-
The corresponding SSH private key, which will be necessary to access any of the nodes in this configuration
To create a service instance:
Click the name of your new Oracle Java Cloud
Service instance to view its details or perform management operations. To return to the Oracle Cloud
Stack console at a later time, click at the top left corner of the page (next to the Oracle logo), and then choose Cloud Stack.
Next steps:
-
By default, access to the WebLogic Server and Load Balancer administration consoles is disabled. In order to use these tools to modify the default configuration or to deploy applications, see Enable Console Access for a Service Instance.
-
The generated private key file is in OpenSSH format. Before connecting to a node in this service instance with the PuTTY SSH client, you must first convert the key to PuTTY’s proprietary format. See Convert a Private Key with PuTTY.
-
Service backups are not enabled in QuickStart instances. See Add a Backup Configuration to an Oracle Java Cloud Service Instance.
-
In order to delete this Oracle Java Cloud Service instance , you must use Oracle Cloud Stack. See Deleting a Cloud Stack in Using Oracle Cloud Stack.
Simple Java Web App
This Oracle Java Cloud Service template is comprised of a single Oracle WebLogic Server node and a single Oracle Database node.
When you execute this template, Oracle Cloud provisions an Oracle Java Cloud Service instance as well as an Oracle Database Cloud Service deployment. This simple template implements a typical development or test Java EE environment, or a production environment for a departmental Java EE application that doesn’t require high availability 24 hours a day. It requires a total of 2 OPCUs.
This template includes:
-
WebLogic Server 12c (12.2) Enterprise Edition installation.
-
Oracle Database 12c (12.2) Standard Edition installation.
-
Single node running a WebLogic Administration Server and a single WebLogic Managed Server. Use the Administration Server to perform administration tasks like configuring Java EE resources and deploying applications. These applications are hosted on the WebLogic Managed Server, and are accessed by end users and other external clients.
-
Single node running Oracle Database. This database has 25 GB of total space and is provisioned with the required schemas for running Oracle Java Cloud Service.
You can scale up your WebLogic Server node at a later time if your applications require more compute or storage capacity. Similarly, you can add more compute or storage capacity to the database. You cannot add more nodes to a Standard Edition instance (scaling out).
You can enable automatic backups on this service instance after creating it.
Multi-Tier Java EE App with High Availability
This Oracle Java Cloud Service template is comprised of multiple Oracle WebLogic Server nodes to ensure maximum availability. External clients access your applications through a load balancer node.
When you execute this template, Oracle Cloud provisions an Oracle Java Cloud Service instance as well as an Oracle Database Cloud Service deployment. This template implements a typical, production-level Java EE environment that requires high availability of the application tier. A separate load balancer tier transparently distributes incoming client requests across the application tier. This template requires a total of 5 OPCUs.
This template includes:
-
WebLogic Server 12c (12.2) Enterprise Edition installation.
-
Oracle Database 12c (12.2) Enterprise Edition installation.
-
One node running a WebLogic Administration Server and a WebLogic Managed Server. Use the Administration Server to perform administration tasks like configuring Java EE resources and deploying applications.
-
One node running a second WebLogic Managed Server. Both Managed Servers are part of a single cluster for high availability. Applications are hosted on these Managed Servers.
-
Two nodes running an enterprise-grade load balancer (Oracle Traffic Director). End users and other external clients access applications via the load balancers. Each load balancer node has its own public IP address.
-
One node running Oracle Database. This database has 256 GB of total space and is provisioned with the required schemas for running Oracle Java Cloud Service.
You can scale your service instance at a later time if your applications require additional capacity. Similarly, you can add more compute or storage capacity to the database.
You can enable automatic backups on this service instance after creating it.
Highly Available Java EE App with Caching
This Oracle Java Cloud Service template is comprised of multiple Oracle WebLogic Server nodes to ensure maximum availability. To optimize performance, applications deployed to WebLogic Server can also take advantage of an Oracle Coherence node running an in-memory data cache.
When you execute this template, Oracle Cloud provisions an Oracle Java Cloud Service instance as well as an Oracle Database Cloud Service deployment. This template implements a high-performance, production-level Java EE environment that requires high availability of the application tier. A separate load balancer tier transparently distributes incoming client requests across the application tier. Finally, a data grid tier enables you to predictably scale applications by providing fast access to frequently used data. This template requires a total of 6 OPCUs.
This template includes:
-
WebLogic Server 12c (12.2) Suite installation.
-
Oracle Database 12c (12.2) Enterprise Edition installation.
-
One node running a WebLogic Administration Server and a WebLogic Managed Server. Use the Administration Server to perform administration tasks like configuring Java EE resources and deploying applications.
-
One node running a second WebLogic Managed Server. Both Managed Servers are part of a single cluster for high availability. Applications are hosted on these Managed Servers.
-
Two nodes running an enterprise-grade load balancer (Oracle Traffic Director). End users and other external clients access applications via the load balancers. Each load balancer node has its own public IP address.
-
One node running Oracle Coherence and configured with a 1.5 GB in-memory cache. Applications can use the Coherence API to cache and retrieve data.
-
One node running Oracle Database. This database has 512 GB of total space and is provisioned with the required schemas for running Oracle Java Cloud Service.
You can scale this environment in a number of different ways as your applications require additional capacity. Similarly, you can add more compute or storage capacity to the database.
You can enable automatic backups on this service instance after creating it.
Compare QuickStart Templates
Compare the attributes of each Oracle Java Cloud Service QuickStart template, including the amount of cloud resources that each template consumes.
Attribute | Simple Java Web App | Multi-Tier Java EE App with High Availability | Highly Available Java EE App with Caching |
---|---|---|---|
OCPUs |
2 |
5 |
6 |
Memory |
15 GB |
38 GB |
45 GB |
Total Storage (approx.) |
225 GB |
635 GB |
850 GB |
Database Storage |
25 GB |
256 GB |
512 GB |
Public IP Addresses |
2 |
4 |
4 |
WebLogic Server Version |
12c (12.2.1) |
12c (12.2.1) |
12c (12.2.1) |
WebLogic Server Edition |
Standard |
Enterprise |
Suite |
Oracle Database Version |
12c (12.2.1) |
12c (12.2.1) |
12c (12.2.1) |
Oracle Database Edition |
Standard |
Enterprise |
Enterprise |
Total Nodes |
2 |
5 |
6 |
WebLogic Server Nodes |
1 |
2 |
2 |
Oracle Database Nodes |
1 |
1 |
1 |
Load Balancer Nodes |
0 |
2 |
2 |
Coherence Nodes |
0 |
0 |
1 |
Backups Enabled |
No |
No |
No |