Properties File Format
The format of the properties file is as follows:
Property Name | Required | Description |
|---|---|---|
weblogic.adminUserName | Yes | The admin username for the Weblogic Servers |
weblogic.adminPassword | Yes | The password for weblogic.adminUserName |
weblogic.dbServiceName | Yes | The Service name of the database for the Weblogic instances |
weblogic.dbaName | Yes | A database username which has sysdba rights |
weblogic.dbaPassword | Yes | The password for weblogic.dbaName |
weblogic.shape | Yes | The shape of the Weblogic server to create. |
weblogic.VMsPublicKey | Yes | The public key for the VM. This should be a text string starting with ssh-rsa. |
provisionOTD | No | Should a load balancer be provisioned for this instance? True or false. Defaults to false. |
level | No | PAAS / BASIC Defaults to PAAS |
subscriptionType | No | HOURLY / MONTHLY Defaults to HOURLY |
...
If level is set to PAAS, these fields are used:
Property Name | Required | Description |
|---|---|---|
cloudStorageContainer | No | The storage container name. e.g. CName The container is automatically created if it doesn't already exist in the Storage Cloud. |
cloudStorageUser | No | The username with which to connect to the Storage Cloud Service instance, if different from FDJCS_USERNAME |
cloudStoragePassword | No | The password for cloudStorageUser if different from FDJCS_PASSWORD |
If provisionOTD is set to true, this field is used:
Property Name | Required | Description |
|---|---|---|
otd.shape | Yes | The shape of the otd instance. Current choices are |
...
This plugin is designed to accommodate changes in Oracle's REST API. It will pass all properties that don't start with [weblogic., otd., or datagrid.] as top-level data in the JSON request , and pass each prefixed data as data inside of parameters as the type of the prefix. Any properties that Oracle supports can be used even if not listed in the tables above. If there is a validation error, the data from Oracle is excellent for providing the solution.
...