Appendix-JCS

Properties File Format

The format of the properties file is as follows:

Property Name

Required

Description

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.
Current choices are [oc3,oc4,oc5, oc6,oc7,oc1m,oc2m,oc3m,oc4m, oc5m]

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

Property Name

Required

Description

cloudStorageContainer

No

The storage container name. e.g. CName
Defaults to FDJCS_INSTANCE_NAME + "BK".

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

Property Name

Required

Description

otd.shape

Yes

The shape of the otd instance. Current choices are
[oc3,oc4,oc5,oc6,oc7,oc1m, oc2m,oc3m,oc4m,oc5m]

 

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.

Here is an example error message from leaving a field blank:

SEVERE - flexagon.fd.core.exceptions.FlexRemotePluginException.init() - FDJCS-00051: Unexpected status code 400 - Bad Request - "OTD shape must be specified when provisioning OTD. Valid OTD shape values are [oc3, oc4, oc5, oc6, oc7, oc1m, oc2m, oc3m, oc4m, oc5m].

This means that you need to send in otd.shape={something}

If you set it to an invalid value, you will receive an error like this:

flexagon.ff.common.core.exceptions.FlexCheckedException.init() - FDJCS-00051: Unexpected status code 400 - Bad Request - Invalid value [something] for shape [otd_shape]. Valid shape values are [[oc3, oc4, oc5, oc6, oc7, oc1m, oc2m, oc3m, oc4m, oc5m]].

When it says otd_shape, replace the “_” with a “.”

Set the value of otd.shape to one of the choices shown in the square brackets.

See https://docs.oracle.com/cloud/latest/jcs_gs/JSRMR/op-paas-service-jcs-api-v1.1-instances-%7BidentityDomainId%7D-post.html for more information about Oracle's API.

Sample Properties File
weblogic.adminUserName=adminUser weblogic.adminPassword=xxxxxxxxxxxxxxx weblogic.dbServiceName=FLEXDB1 weblogic.dbaName=sys weblogic.version=12.1.3.0.5 weblogic.dbaPassword=xxxxxxxxxx weblogic.shape=oc3 weblogic.VMsPublicKey=ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDTC0PurZLamhfblqq4ql91O+WRQ0i33nh5HC5myMP as/rs+AxQPnWkRitMQ53TYmq7e7r4Iv6XNm229c19uTO9NgvYSk3Iqgg5/4idfgaRUSrF6z CGEVeTOpIxGP+shdfsvUQpJdu/Ng/0VESLlSqja3ZSOWyYZ5WEJ/IG4FK3sqvnWyK2DZ5Qs ZCvvkfYfmjcNhorX28k/9r23NKW4FbG9JOj4TTSTS/ibf3gZuVLU9Oq88vp1TpSEU2vi6TQ Ikmn level=PAAS subscriptionType=HOURLY description=Example, Inc product distribution center provisionOTD=true otd.shape=oc3 sampleAppDeploymentRequested=false
The following macros are not currently supported in the footer:
  • style