Hello Kenneth,

I'm sorry that you are encountering this challenge and confusion.

I can understand it when it is not stated clearly is difficult to find an answer.

Let me begin by stating that I am not a NNMi or a NOM engineer, but I do have experience with Classic and Containerized products from the OpsBridge area.

OPTIC is an acronym that stands for Operations Platform for Transformation, Intelligence and Cloud.

It used to be called the ITOM Platform but was rebranded to OPTIC.

You can learn more about OPTIC on the following Blog:
https://community.microfocus.com/it_ops_mgt/b/sws-571/posts/announcing-optic---the-operations-platform-for-transformation-intelligence-and-cloud

Here is also a general marketing page that provides some overview of information:
https://www.microfocus.com/en-us/solutions/simplify-it-transformation

The OPTIC Platform is what is considered Shared Resources by a number of ITOM products.  These Shared Resources include OPTIC Orchestration Engine (Ex. Operations Orchestration), OPTIC Discovery, CMDB & Service Topology (Ex. UCMDB, UD & CMS), OPTIC AI, ML and Analytics, OPTIC Data Lake and OPTIC Core Services (Ex. OPTIC Management Toolkit, formerly Container Delivery Foundation or CDF).

OPTIC Data Lake is a Shared service that can be included with Data Center Automation (DCA), Network Operations Management (NOM), and Operations Bridge (OpsB).  It is not a standalone product.

OPTIC Data Lake can only be installed on a Containerized environment that uses Kubernetes.  Kubernetes is an Orchestration software, created by Google, to manage container environments like Docker and ContainerD.  With later versions of our products, we are using ContainerD and not Docker.

You can install DCA, NOM and/or OpsB with OPTIC Data Lake on AWS, Azure or On-Premise.  For On-Premise installations, you would install OPTIC Management Toolkit (OMT) first and then install the other product (DCA, NOM or OpsB) on top of it.  You can also install CMS, SMAX, HCMX and OO on top of OMT for On-Premise Installations.

You do not install Kubernetes on your Classic Software installation.  You would install it within a separate environment and then integrate the Classic Software with it.

The most common purpose for these integrations is for the use of Reporting.  Here are the documentation links that talk about integrating OPTIC Reporting with Classic NNMi, Classic NA and Classic OBM.  You have two of these within your list above.

Integrate OPTIC Reporting with NNMi and Smart Plugins (SPIs)
https://docs.microfocus.com/doc/Network_Operations_Management/2022.05/IntegrateNNMi

Integrate OPTIC Reporting with NA
https://docs.microfocus.com/doc/Network_Operations_Management/2022.05/IntegrateNA

Integrate NOM with Operations Bridge Manager using Operations Agent
https://docs.microfocus.com/doc/Network_Operations_Management/2022.05/NOMOBMIntegration

I hope that this helps answer your first question.

As for your second question, I cannot find the "Import your CA Certificate" section that you are referencing.

I did find the following page that explains how to import CA Certificates for NOM.  However, that is not related to any integrations.

Import CA Certificates
https://docs.microfocus.com/doc/Network_Operations_Management/2022.05/ImportCACert

in order to integrate any product with OPTIC DL, you need to import certificates so that communication between the products can use TLS 1.2.  As you know, this is a requirement.

Within the information provided for the 'Integrate OPTIC Reporting with NA', I can see that it has two options described depending on if you are using a CA signed certificate or a Self-Signed certificate for NA.   It then steps you through the steps to exchange certificates between NOM and NA.

NA Certificate added to NOM:

It appears that importing the NA CA certificate into NOM only requires that you place the certificate within the $HOME/nom/ directory.  My guess is that the product will automatically import it and recognize it later.  This is feature/function it is done for some other products within the ITOM portfolio.

NOM Certificate added to NA:

Importing the NOM certificate into NA is a little more involved and appears to be the remaining steps.  NA pushes its data into OPTIC Data Lake for reporting purposes.

I hope that this information is helpful and clarifies the situation.

Thank you for your questions.

Regards,

Mark Butler

Hello Kenneth,

I'm sorry that you are encountering this challenge and confusion.

I can understand it when it is not stated clearly is difficult to find an answer.

Let me begin by stating that I am not a NNMi or a NOM engineer, but I do have experience with Classic and Containerized products from the OpsBridge area.

OPTIC is an acronym that stands for Operations Platform for Transformation, Intelligence and Cloud.

It used to be called the ITOM Platform but was rebranded to OPTIC.

You can learn more about OPTIC on the following Blog:
https://community.microfocus.com/it_ops_mgt/b/sws-571/posts/announcing-optic---the-operations-platform-for-transformation-intelligence-and-cloud

Here is also a general marketing page that provides some overview of information:
https://www.microfocus.com/en-us/solutions/simplify-it-transformation

The OPTIC Platform is what is considered Shared Resources by a number of ITOM products.  These Shared Resources include OPTIC Orchestration Engine (Ex. Operations Orchestration), OPTIC Discovery, CMDB & Service Topology (Ex. UCMDB, UD & CMS), OPTIC AI, ML and Analytics, OPTIC Data Lake and OPTIC Core Services (Ex. OPTIC Management Toolkit, formerly Container Delivery Foundation or CDF).

OPTIC Data Lake is a Shared service that can be included with Data Center Automation (DCA), Network Operations Management (NOM), and Operations Bridge (OpsB).  It is not a standalone product.

OPTIC Data Lake can only be installed on a Containerized environment that uses Kubernetes.  Kubernetes is an Orchestration software, created by Google, to manage container environments like Docker and ContainerD.  With later versions of our products, we are using ContainerD and not Docker.

You can install DCA, NOM and/or OpsB with OPTIC Data Lake on AWS, Azure or On-Premise.  For On-Premise installations, you would install OPTIC Management Toolkit (OMT) first and then install the other product (DCA, NOM or OpsB) on top of it.  You can also install CMS, SMAX, HCMX and OO on top of OMT for On-Premise Installations.

You do not install Kubernetes on your Classic Software installation.  You would install it within a separate environment and then integrate the Classic Software with it.

The most common purpose for these integrations is for the use of Reporting.  Here are the documentation links that talk about integrating OPTIC Reporting with Classic NNMi, Classic NA and Classic OBM.  You have two of these within your list above.

Integrate OPTIC Reporting with NNMi and Smart Plugins (SPIs)
https://docs.microfocus.com/doc/Network_Operations_Management/2022.05/IntegrateNNMi

Integrate OPTIC Reporting with NA
https://docs.microfocus.com/doc/Network_Operations_Management/2022.05/IntegrateNA

Integrate NOM with Operations Bridge Manager using Operations Agent
https://docs.microfocus.com/doc/Network_Operations_Management/2022.05/NOMOBMIntegration

I hope that this helps answer your first question.

As for your second question, I cannot find the "Import your CA Certificate" section that you are referencing.

I did find the following page that explains how to import CA Certificates for NOM.  However, that is not related to any integrations.

Import CA Certificates
https://docs.microfocus.com/doc/Network_Operations_Management/2022.05/ImportCACert

in order to integrate any product with OPTIC DL, you need to import certificates so that communication between the products can use TLS 1.2.  As you know, this is a requirement.

Within the information provided for the 'Integrate OPTIC Reporting with NA', I can see that it has two options described depending on if you are using a CA signed certificate or a Self-Signed certificate for NA.   It then steps you through the steps to exchange certificates between NOM and NA.

NA Certificate added to NOM:

It appears that importing the NA CA certificate into NOM only requires that you place the certificate within the $HOME/nom/ directory.  My guess is that the product will automatically import it and recognize it later.  This is feature/function it is done for some other products within the ITOM portfolio.

NOM Certificate added to NA:

Importing the NOM certificate into NA is a little more involved and appears to be the remaining steps.  NA pushes its data into OPTIC Data Lake for reporting purposes.

I hope that this information is helpful and clarifies the situation.

Thank you for your questions.

Regards,

Mark Butler