Oracle Data Integrator Controller

This controller provisions and maintains Oracle Data Integrator Enterprise Edition. The following versions have been tested and are supported.

Oracle Data Integrator 12.2.1.3
Oracle Data Integrator 12.2.1.4

In addition to the above, this controller supports Oracle Data Integrator Agent setups in the following configurations.

Deployed as a J2EE application on a Weblogic Cluster
Deployed as a J2EE application on a Weblogic Cluster and as a System Component

The controller does supports deploying the agent just as a System Component but it has not been throughly tested at the time of writing. The documentation assumes that the user has prior knowledge of working with MintPress SDK and/or MintPress Runtime.

How to Use the Controller

The controller can be used in two ways, (a) Using the MintPress Controllers Directly (b) Using MintPress Runtime JSON Format.

Using this controller directly

A fully documented script to create a single node ODI domain with the Agent deployed on a Weblogic Cluster is here. A fully documented script to create a single node ODI domain with the Agent deployed on a Weblogic Cluster and also as a System Component is here.

Using MintPress Runtime JSON Format

Sample single node JSON format that are supported via MintPress Runtime are located:

FAQ

Q. How to create additional database schemas in Oracle Data Integrator.

A. Additional database schemas can be created by passing in the following properties to the template properties.

"AdditionalDatabaseSchemas": [
  {
    "SchemaName": "odi_custom_schema1",
    "SchemaPassword": "Welcome1",
    "DefaultTablespace": "odi_custom_ts1",
    "TablespaceFileSize": "10M",
    "DropTablespace": "true",
    "TablespaceOptions": "ENCRYPTION DEFAULT STORAGE (ENCRYPT)"
  },
  {
    "SchemaName": "odi_custom_schema2",
    "SchemaPassword": "Welcome1",
    "DefaultTablespace": "odi_custom_ts2",
    "TablespaceFileSize": "10M",
    "DropTablespace": "false"
  }
]

The controller supports creating multiple schemas, if you specify the DefaultTablespace option, the controller will create the tablespace if it does not exists and then make that tablespace as a default for the schema. If you pass DropTablespace as true, the controller will also delete the tablespace when dropping the schema (usually happens during clobber operation).

The only mandatory values are SchemaName and SchemaPassword.

Key	Mandatory	Default	Description
SchemaName	Yes	None	Name of the schema you want to create.
SchemaPassword	Yes	None	Password for the schema you want to create.
DefaultTablespace	No	USERS	The tablespace assigned to the user. It is recommended to always provide this option though. If you don’t provide a value for this option, ensure that the value for ‘DropTablespace` is false else you will lose your data!
TablespaceFileSize	No	1G	The default tablespace size we will create.
TablespaceOptions	No		The tablespace options which will be appended when creating the tablespace, default is empty. You can pass in encryption options here.
DropTablespace	No	true	If this is set to true, the controller will drop the tablespace when dropping the schema. Be careful with this option, it will drop the tablespace that might be being used by other schemas.

Q. How to create Additional Work Repositories for Oracle Data Integrator

A. Additional work repositories can be created by passing in the following properties to the template properties. At the time of writing, only “Execution” type of work repositories are supported, creating additional development repositories is not yet supported.

"AdditionalWorkRepositories": [
  {
    "RepositoryName": "WORKREP_NEW",
    "RepositorySchema": "odi_custom_schema1",
    "RepositorySchemaPassword": "Welcome1",
    "MasterRepositorySchema": "odi_odi_repo",
    "MasterRepositorySchema_password": "Welcome1"
  },
  {
    "RepositoryName": "WORKREP_NEWER",
    "RepositorySchema": "odi_custom_schema2",
    "RepositorySchemaPassword": "Welcome1",
    "MasterRepositorySchema": "odi_odi_repo",
    "MasterRepositorySchemaPassword": "Welcome1"
  }
]

The controller supports creating multiple work repositories. The following table describes all the properties.

Key	Mandatory	Default	Description
RepositoryName	Yes	None	Name of the work repository.
RepositorySchema	Yes	None	Name of the Database schema the work repository will be associated to.
RepositorySchemaPassword	Yes	None	Password of the database schema the work repository will be associated to.
MasterRepositorySchema	No	RCUPREFIX_ODI_REPO	The name of the Master ODI Repository the work repo will be associated to. The RCUPREFIX will be used with whatever has been specified in the domain.
MasterRepositorySchemaPassword	No		The password of the Master ODI Repository the work repo will be associated to. If not specified, the password for ‘MasterRepositorySchema` will be used from the domain.
DatabaseUrl	No		The URL of the database in the format host:port/service that the work repository will use. If not provided, URL of the RCU component will be picked up from the domain.

Q. SSL & Additional Properties for Oracle Data Integrator System Components

A. The following properties are supported for Oracle Data Integrator System Components. These can be passed as attributes under the SystemComponents key when using the MintPress JSON model. A sample structure is shown below. If the AgentProtocol is https, you must also provide other Identity and Trust related properties otherwise they are optional. The AdditionalSSLProperties and and AdditionalJavaProperties are reflected in the instance.sh script for the System Component.

"systemComponentList": [
  {
    "name": "OracleDISAgent1",
    "componentType": "OracleDataIntegrator",
    "machineName": "odihost01.mintpress.io",
    "attributes": {
      "OracleDataIntegrator": {
        "AgentHostname": "odihost01.mintpress.io",
        "AgentPort": "2091",
        "AgentProtocol": "https",
        "IdentityKeyStore": "/oracle/app/runtime/odi/domains/odi_domain/security/DemoIdentity.jks",
        "IdentityKeyStorePassPhrase": "DemoIdentityKeyStorePassPhrase",
        "TrustKeyStore": "/oracle/app/binaries/odi/fmw/wlserver/server/lib/DemoTrust.jks",
        "TrustKeyStorePassPhrase": "DemoTrustKeyStorePassPhrase",
        "PrivateKeyAlias": "demoidentity",
        "PrivateKeyPassPhrase": "DemoIdentityPassPhrase",
        "AdditionalSSLProperties": "-Doracle.net.ssl_version=1.2",
        "AdditionalJavaProperties": "-Xmx1G"
      }
    }
  }
]

Oracle Data Integrator Properties Reference

Refer the LimePoint Controller Reference for details on all properties supported.