In this post, I am going to present, how to provision very easy and fast a Weblogic Application Server - FMW infrastructure with enabled JRF template and fully operational domain ready for ADF Application.

Oracle provides a very easy process for WebLogic installation by using a predefined image that is ready for cloud deployment and simple integration with all surrounding services in the cloud.

If you following the below steps you will see how simple is to bring up, for example, WebLogic with ATP database or Database as a Service with that internal development and predefined integration in the image it will make the process for deployment seamless

I will share a lot of tips and tricks and some of the process for debugging and testing in case of troubles  

First, prior to any actions, you need to have Oracle account as Oracle Cloud free tier 

Please read the following documentation in order to have a good understanding of what and how

https://docs.oracle.com/en/cloud/paas/weblogic-cloud/tutorial-create-jrf-domain-atp/

https://docs.oracle.com/en/cloud/paas/weblogic-cloud/user/components-oracle-weblogic-cloud.html#GUID-D5F1469F-C9C5-4A7C-99B6-8DA7F1C16F79

https://docs.oracle.com/en/cloud/paas/weblogic-cloud/user/create-data-source-atp-database.html#GUID-6786B961-1283-4F32-8D2D-93B46102BA63

What kind of policy should be added 

https://docs.oracle.com/en/cloud/paas/weblogic-cloud/user/you-begin-oracle-weblogic-cloud.html#GUID-373918C3-A952-43BC-B61F-558DF0CD1A5B

---

Oracle Cloud Free Tier

Oracle Cloud with Create WebLogic instance from the marketplace

Configure WebLogic Instance Parameters

Database System. Then select or enter the following:

• The compartment in which you've created the database.
• The VCN on which you've created the database. If this VCN is different than the WebLogic Server VCN, they cannot have overlapping CIDRs. For example, you cannot create a domain on VCN 10.0.0.0/16 that uses a database on VCN 10.0.0.1/24.
• The DB system to use for this WebLogic domain.
• The database home within the selected DB system.
• The database home version.
• The database within the selected DB system where you want to create the JRF schemas for this domain.
• The Pluggable database (PDB) name, only if the selected database is running Oracle Database 12c or later.
• The name of a database user with database administrator (DBA) privileges, and the encrypted password for that database administrator.
• The database listen port (1521 by default)

You need to configure preliminary port access as described in the below two steps in order to give access from Weblogic to the database.

Also keep in mind that you may neeed to add more ports based on the configuration of MS servers, Console ports etc.

 Vault should be created like this:

You need to Vault in order to be able to encrypt and decrypt keys via special endpoint service which is required during Stuck creation 

Posible errors if you dont have correct policy setup on compartment of tenant:

Prior any action password for weblogic admin user should be encoded with base64

This is one of the way to encode

e.g.

[weblogic@host ~]$ echo -n 'OraCOOL1234_1234_'| base64

T3JhQ09PTDEyMzRfMTIzNF8=

This is important but you have to remember that you need to pass encripted value.. here you can see what ill happns if you add plain text password

[weblogic@host ~]$ oci kms crypto encrypt --key-id ocid1.key.oc1.eu-frankfurt-1.bfpcyukqaacmg.gjghghgjhjjgkjgfkdlddfgkhhlj --endpoint https://kjggkglhkhkl-crypto.kms.eu-frankfurt-1.oraclecloud.com --plaintext OraCOOL1234_1234_

ServiceError:
{
"code": "InvalidParameter",
"message": "The plaintext must be a valid base64 encoded string.",
"opc-request-id": "B7C8F2A3DC0C402ABF956F0A69990ED2",
"status": 400
}

The above test validate that enpoint cannot work with plain text password :)

The correct way to trigger encrypt to the endpoint is following:

[weblogic@host ~]$  oci kms crypto encrypt --key-id ocid1.key.oc1.eu-frankfurt-1.bfpcyukqaacmg.gjghghgjhjjgkjgfkdlddfgkhhlj --endpoint https://kjggkglhkhkl-crypto.kms.eu-frankfurt-1.oraclecloud.com --plaintext T3JhQ09PTDEyMzRfMTIzNF8=
{
"data": {
"ciphertext": "lhlhlLkhKHl+Kgkgankafg/zBdU0013TMUlFXZDJPjCuh/AAAAAA=="
}
}

I will user following user/password for the WebLogic

WL-user : weblogictest
Password: lhlhlLkhKHl+Kgkgankafg/zBdU0013TMUlFXZDJPjCuh/AAAAAA==  

Now we can validate decrypt process

[weblogic@host ~]$ oci kms crypto decrypt --key-id ocid1.key.oc1.eu-frankfurt-1.bfpcyukqaacmg.gjghghgjhjjgkjgfkdlddfgkhhlj --endpoint https://kjggkglhkhkl-crypto.kms.eu-frankfurt-1.oraclecloud.com  --ciphertext lhlhlLkhKHl+Kgkgankafg/zBdU0013TMUlFXZDJPjCuh/AAAAAA==  
{
"data": {
"plaintext": "T3JhQ09PTDEyMzRfMTIzNF8=",
"plaintext-checksum": "783888468"
}
}

if you have pass of the above process, this mean that all should work :)
*******
Enter the KMS encrypted password in creation wizard not the textual password

*******

Here you can see full process of  Marketplace image deployment:

After a few minutes WebLogic instance will be ready and you can connect with ssh to check process for provisaning 

Discovered Limitation Until Now:

Cannot change the name of the domain, the only option is to add prefix

Root access is not possible

Cannot change the path for Weblogic installation 

....