Configuring on-premises components
To create a hybrid installation, you must install the Netcool Hybrid Deployment
Option Integration Kit on your on-premises Operations Management installation, enable scope-based grouping, configure WebSphere® to use SSL_TLSv2, and configure your on-premises ObjectServer gateway mappings.
Enabling on-premises scope-based event grouping cloud native analytics component in your hybrid deployment disables any existing on-premises scope-based event grouping triggers during installation. However, the triggers that are related to enriching the ScopeID column and needed for scope grouping are not disabled. A specific set of triggers is added for cloud native analytics . Cloud native analytics creates scope-based groups, based on scope enrichment, and augments those groups with other groups from other analytics. The original on-premises scope-based event grouping triggers must remain disabled while cloud native analytics is actively preforming the task of scope-based grouping. To re-enable the on-premises scope-based grouping, you must first set the scope-based policy in the cloud native analytics policy UI to Disabled. Then, complete the following steps to re-enable the on-premises scope-based grouping.Setting WebSphere protocol to TLSv1.2 Operations Management installation, needs to be able to import certificates from the cloud native components deployment on Red Hat® OpenShift® Container Platform . To do this task, WebSphere must be configured to use TLSv1.2. Use this procedure to help you verify or change this setting. If you have more than one WebGUI/DASH node, complete this procedure on each WebGUI/DASH node.Installing the integration kit IBM® Installation Manager to install the Netcool Hybrid Deployment Option Integration Kit on your on-premises Operations Management installation.Enabling the persistent OAuth 2.0 service in WebGUI in a hybrid deployment Update gateway settings cloud native components mappings to enable bidirectional data replication.