Service type is specified in the initial configuration used to create NoSQLClient instance and indicates what kind of service the driver will be using. Currently supported values are CLOUDSIM, CLOUD and KVSTORE. In addition to ServiceType enumeration, these values may be specified as strings "CLOUDSIM", "CLOUD" or "KVSTORE", case-insensitive. This is useful if using JSON configuration file. If ServiceType is not present in the initial configuration, the driver will try to deduce service type from the information provided in authorization property auth (see AuthConfig) in the following way:

  • If auth is undefined or null, the service type is determined as follows: if region is specified, the service type defaults to CLOUD, otherwise it defaults to CLOUDSIM.
  • If auth contains iam property, the service type is assumed to be CLOUD.
  • If auth constains kvstore property, the service type is assumed to be KVSTORE. You may specify value {} (empty object) for kvstore property to connect to non-secure kvstore, although it is advisable to specify the service type explicitly in this case. See KVSTORE.
  • If auth contains provider property, the service type depends on the type of the provider: CLOUD if the provider is IAMAuthorizationProvider and KVSTORE if the provider is KVStoreAuthorizationProvider. If using user-specified provider type, the service type will remain undefined.
Note that only one of properties iam, kvstore or provider may be specified. If none is specified, this is equivalent to auth not defined and the service type will default to CLOUD or CLOUDSIM as described above.

See

Enumeration Members

Enumeration Members

CLOUD: "CLOUD"

Oracle NoSQL Cloud Service. Authorization is managed by IAM.

See

CLOUDSIM: "CLOUDSIM"

Cloud Simulator, no authorization used.

See

Connecting an Application to Oracle NoSQL Database Cloud Service

KVSTORE: "KVSTORE"

On Premise Oracle NoSQL Database. This includes both secure and non-secure stores. For secure store, authentication information must be provided in kvstore as KVStoreAuthConfig. For non-secure store, it is enough to specify serviceType to be KVSTORE without having kvstore property.

See

Generated using TypeDoc