Oracle Banking Platform Controller

This controller provisions and maintains Oracle Banking Platform (OBP). The following versions have been tested and are supported.

  1. Oracle Banking Platform 2.7.x

  2. Oracle Banking Platform 2.12.0

Up until 2.7.x , OBP media Pack only shipped monolith installers, i.e. installers that will configure all the components for OBP Host. From OBP 2.12.0, OBP media pack now ships as modules. For example, Originations have its own installer, servicing has its own installer and so on. OBP also has a full installer which will be the last one for OBP 2.12. Future versions of OBP will not have a full installer. Full installers have all modules of OBP (originations, deposits, collections etc) packaged as one.

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

TODO

Using MintPress Runtime JSON Format

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

Using OBP OBEO Installer

  1. OBEO OBP SOA 2.12.0

  2. OBEO OBP Host (Batch) 2.12.0

  3. OBEO OBP UI 2.12.0

Using OBP Full Installer

  1. OBP SOA 2.12.0

  2. OBP Host (Batch) 2.12.0

  3. OBP UI 2.12.0

These samples can also be found under docs.limepoint.com/mintpress/reference/runtime-json-templates

FAQ

Q. How to install different modules for OBP Host, e.g. Pricing, LCM etc ?

A. The properties that control what modules get installed are installed_component and obp_component_class. Change the property in the installation attributes and the templateList, e.g

In the InstallationList,

{
  "name": "obp-host",
  "product": "OracleBankingPlatform::ModularHostInstallation",
  "version": "2.12.0.0.0",
  "installPath": "/oracle/app/binaries/obphost/fmw/obpinstall",
  "softwareStage": "/oracle/stage/obp/2.12.0/obeo/obphost/obpinstall-host",
  "attributes": {
    "newworld": "true",
    "OracleBankingPlatform::ModularHostInstallation": {
      "installed_component": "Batch",
      "obp_component_class": "Oracle Banking Platform",
      <... other properties ...>
    }
  }
}

In the templateList

{
  "name": "OracleBankingPlatform::ModularHostTemplateSet",
  "attributes": {
    "OracleBankingPlatform::ModularHostTemplateSet": {
      "installed_component": "batch",
      "obp_component_class": "Oracle Banking Platform",
      <... other properties ...>
    }
  }
}

The following modules are supported: ['Batch', 'LCM', 'Deposits', 'Collection_Recovery', 'Product_Manufacturing', 'Origination', 'Pricing', 'Party', 'Loan', 'Shared', 'Broker']. Only one component can be specified per JSON file. If you don’t specify the component name, batch is the default component. Ensure that the property in the installation and template must match, i.e. you can’t have the value batch in the installation and lcm in the templateList.

The following component classes are supported. ['Oracle Banking Platform', 'Oracle Banking Enterprise Originations','Oracle Banking Enterprise Default Management', 'Oracle Banking Loans Servicing', 'Oracle Banking Deposits and Lines of Credit Servicing'] Note that these correspond to the modular installer OBP launches.

Q. What modules are supported for OBP SOA and OBP UI

A. OBP SOA and OBP UI do not have modules, however they have different installers based on the OBP Host Modules. For examples, OBP SOA that ships with Full OBP Installer is different to OBP SOA that ships with Originations Installer (OBEO). MintPress looks for the value of obp_component_class in the installationList and templateList sections to determine how to configure SOA/UI. Just like OBP Host, you must mention the values for these properties for SOA and UI.

Q. How to define Managed Server Names for OBP Host

A. MintPress supports custom managed server names for OBP Host domains, e.g. pricing domain can have pricing_server1, lcm domain can have lcm_server1 etc. MintPress controls this behavior using two properties viz. pattern and the name of the managed server in the managedServerList.

{
	"name": "OracleBankingPlatform::ModularHostTemplateSet",
	"attributes": {
		"OracleBankingPlatform::ModularHostTemplateSet": {
			"pattern": "batchhost_server*",
			< --- other properties >
		}
	}
}

"managedServerList": [
	{
		"name": "batchhost_server1",
		"machineName": "Machine-apphost1",
		"clusterName": "batch_cluster",
		< -- other properties -- >
	}
]

In the above example, MintPress will name the managed servers as batchhost_server1, batchhost_server2 and so on. Make sure that the value for the pattern property must match the name of the managed server without the numeric value.

Q. How to create additional credential mappers in Oracle Banking Host.

A. MintPress supports setting credentials for the default credential mapper that ships OOB with OBP Host via properties. However, in circumstances where you would like to create additional credential mapper that do not ship with OBP media pack, use the following mechanism. Add the following section under your template properties, e.g.

{
	"name": "OracleBankingPlatform::ModularHostTemplateSet",
	"attributes": {
		"OracleBankingPlatform::ModularHostTemplateSet": {
      "customized_credential_mappers": [
        {
          "destination_name": "ra/name_of_connector",
          "username": "weblogic",
          "password": "Welcome123",
          "application_name": "com.ofss.fc.app.connector",
          "mapping_username": "weblogic_ra_default",
          "module_name": "com.ofss.fc.connector.rar",
          "eis_name": "Sample"
        },
        {
          "destination_name": "ra/another_name_of_connector",
          "username": "weblogic",
          "password": "Welcome123",
        }
      ]
		}
	}
}

The controller supports creating multiple credentials as shown in the example above.

The only mandatory values are destination_name, username and password.

Key Mandatory Default Description
destination_name Yes None Name of the destination you want to set the credential for.
username Yes None Username for the credential.
password Yes None The password for the credential.
application_name No com.ofss.fc.app.connector The name of the connector application.
mapping_username No weblogic_ra_default The name of the mapping username for the connector.
module_name No com.ofss.fc.connector.rar The module name in Weblogic for the connector.
eis_name No Sample eis name of the resource.

Q. Important properties for OBP Host

A. The following table lists all the properties applicable for OBP Host. The column template/installation signifies where the property should be mentioned. If it is installation, then the property must be mentioned in the installationList else templateList.

Property Default Value Description template/installation
is_bip_installed false Set this property to true if you have a BIP/OAS domain and for OBP. This property controls if xdo-jars are copied. Installation
installed_component Batch allowed_values: [‘Batch’, ‘LCM’, ‘Deposits’, ‘Collection_Recovery’, ‘Product_Manufacturing’, ‘Origination’, ‘Pricing’, ‘Party’, ‘Loan’, ‘Shared’]. Components to configure in the domain. Installation & Template
obp_component_class Oracle Banking Platform allowed_values: [‘Oracle Banking Platform’, ‘Oracle Banking Enterprise Originations’,‘Oracle Banking Enterprise Default Management’, ‘Oracle Banking Loans Servicing’, ‘Oracle Banking Deposits and Lines of Credit Servicing’]. This property signifies which SOA components should be installed for the domain. This is applicable only when using OBP 2.12 or higher and only when using modular installers supplied by OBP. Installation & Template
target_oracle_home fmw_home/obpinstall Full path of the obpinstall folder, defaults to fmw_home/obpinstall Installation
software_stage_custom software_stage/../custom Full path of the custom stage location where OBP will pick up BIP/IPM modules from Installation
database_schema_prefix domain.metadata_repository.schema_prefix The RCU prefix for OBP Host schema. This defaults to the schema_prefix for the domain metadata repository Template
database_schema_name database_schema_prefix_OBP The username for OBP Host schema. This defaults to the schema_prefix_obp. Template
database_schema_password domain.metadata_repository.schema_password.value The password to be used for OBP Host schema. Defaults to the RCU password for the domain. Template
database_tablespace_name domain.metadata_repository.schema_prefix_OBP The target Unit code For OBP. Template
database_tablespace_options Additional options to pass to the tablespace creation. Template
create_obp_schema true Should the controller create OBP Host schema? defaults to true Template
drop_obp_schema true Should the controller drop OBP Host schema when clobbering the domain. defaults to true Template
seed_obp_schema true Should the controller create obp schema objects? defaults to true Template
seed_obp_security_policy true Should the controller create obp security policies in the opss schema Template

Oracle Banking Platform Properties Reference

OBP Host

Refer ModularHostInstallation for all installation properties for OBP Host 2.12.

Refer ModularHostTemplate for all template properties for OBP Host 2.12.

OBP SOA

Refer ModularSOAInstallation for all installation properties for OBP SOA 2.12.

Refer ModularSOATemplate for all template properties for OBP SOA 2.12.

OBP UI

Refer ModularUIInstallation for all installation properties for OBP UI 2.12.

Refer ModularUITemplate for all template properties for OBP UI 2.12.

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