5.5 KiB
ESM-ODL-Integration_693613201
This is wiki helps the R&D team for the successfully integration of ESM and Operation Platform Integration for a tenant.
Pre-requisites:
ESM and OP charts are deployed on the same cluster on different name spaces.
ESM tenat is created and Automation Center capabilty is enabled
ESM tenant, the Operation Platform tenant and users are created
1. Configure OPTIC Data Lake certificates
Download OPTIC Data Lake certificates
https://docs.microfocus.com/doc/SMAX/24.3/IntegrateODL
Follow the below steps to get Opeation Platform certificates:
-
- Invoke
https://<OpsbServerName>:443/ browser, click Not secure and Certificate is not valid. 2. Go to the Details tab and select the root certificate, then click Export.
- Invoke
(Optional) If you want to use ports different from 443, you also need to import different certificates for them. For example, you have the following Administration and Data receiver URLs:
-
- https://<
OpsbServerName>:30004/itom-data-ingestion-administration - https://<OpsbServerName>:30001/itom-data-ingestion-receiver
- https://<
* Follow the aove steps to get the Administrator (or) Receiver certificates
Import ODL certificate into SMAX
Export the certificates and copy into path: /var/vols/itom/itsma//certificate/source
Eg: /var/vols/itom/itsma/config-volume/certificate/source
On SaaS envrioment: /efs/var/vols/itom/itsma/config-volume/certificate/source
2. Restart SMAX pods by running commands on a control plane node or the bastion node:
Connect to the basion node of the SMAX cluster to run the K8 commands:
1. Run the following commands to restart the SMAX platform pods.
kubectl rollout restart deployment -n itsma-xxxx itom-xruntime-platform
kubectl rollout restart deployment -n itsma-xxxx itom-xruntime-platform-offline
2. Run the following command to restart the bo-ats pod.
kubectl rollout restart deployment -n itsma-xxxx itom-bo-ats-deployment
3. Run the following command to restart the ac-vulnerability-patching
kubectl rollout restart deployment -n itsma-xxxx itom-ac-vulnerability-and-patching
* Wait until all the pods are deleted pods are started and running successfully
3. Login to BO to Deploy the OP capability for tenant.
Create ODL IDM organization for the tenant.
1. Login to BO and click on specific tenant, goto "Configurations=>Credentials store"
2. Add IDM user credentials (with di-admin and di-ingestion role) in SMAX BO interface=>Configurations=>Credentials store
Here the Organization name should be name of OperationPlattform <tenant_name>
Deploy OPTIC Data Lake Capability for the tenant
1. In the Tenant → Application Settings, click on 'Deploy new Capability and follow the below steps:
a. Select OPTIC Data Lake
b. Provide the Administrator URL: https://dawn120.dev.opsware.com:30443/itom-data-ingestion-administration
c. Select the credentail user and click 'OK'
2. Repeat the setting for 'Receiver UR:
b. Provide the Receiver URL: https://dawn120.dev.opsware.com:30443/itom-data-ingestion-receiver
c. Select the credentail user and click 'OK'
4. Enable ODL Integration in Agent Interface for the tenant
Login to Agent Interface => Integration Management=>Integration Configuration:
1. Click 'Add' and select the AC entity types and saved.
a. Device
b. Actual Sevice
c. CVE
d. Vulnerability
e. Patch
f. Policy
g. Policy Implementations
2. Click on 'OPTIC Data Lake' and select 'Appy' button to create OP tables
3. Click on 'OPTIC Data Lake' and select 'Active' and Save.
Select the required record type or all record types for data ingestion into ODL
Add all the required record types, check "Active" to ingest data and click on Apply to create required tables in ODL Vertica
Note: Without enabling ODL capability, data will not sync in the Vertica DB.
Known Limitation:
- The data sync is successful only for those AC existing entites which are sucessfully sycned in ESM database
- The data ingeration for AC entities is sucessful only from the point of integration to Operation Platform is done (i.e Full Sync support to push data created before integration is not supproted)
( i.e. for any existing data available before the Operation Platform integration, the data ingestion wil not work, we need to re-ingest the data to sync in OP)
Related pages
- Page: ESM Cloud Farm Version Tracking
- Page: How to get an Opentext Confluence account
- Page: ITOM APM AppPluse Cloud Farm Information
- Page: ITOM Cloud Service Ops Doc Management Process
- Page: ITOM ESM Cloud Service Catalog
- Page: ITOM OpsB NOM Cloud Service Catalog
- Page: OpsB and NOM Cloud Deployments Version Tracking