...
To import Kyvos Reporting certificate in JRE of Kyvos,
Navigate to the ../kyvos/approger/kyvos/jre_latest/lib/security installed directory location where Kyvos is installed and place the generated certificate under security folder.
Execute the keytool -import -v -trustcacerts -alias your_aliasname -file your_certificatename.cer/crt -keystore cacerts to import the certificate.
To import Kyvos certificate in JRE of Kyvos Reporting,
Navigate to the ../kyvos/app/KyvosReporting/jre/lib/security installed directory location where Kyvos is installed and place the generated certificate under security folder.
Execute the keytool -import -v -trustcacerts -alias your_aliasname -file your_certificatename.cer/crt -keystore cacerts to import the certificate.
Verify that the Kyvos and Kyvos Reporting certificate domain.
If Kyvos and Kyvos Reporting are using the same certificate to run the URL in HTTPS mode, after importing the certificates on both the nodes where Kyvos Reporting and Kyvos is running, you must map host name and IP under hosts file at the /etc/hosts location.
On Kyvos Reporting node: Kyvos node IP and host name
On Kyvos node: Kyvos Reporting node IP and host name
For example, ifIP: 127.0.0.1
Hostname: xyz
then entry in the hosts file should be 127.0.0.1 xyz
If Kyvos and Kyvos Reporting are using different certificates to run the URL in HTTPS mode, after importing the certificates on both the nodes where Kyvos Reporting and Kyvos is running, you must map host name, IP address and certificate name under hosts file at the /etc/hosts location.
On Kyvos Reporting node: Kyvos node IP, host name, and certificate name
On Kyvos node: Kyvos Reporting node IP, host name, and certificate name
For example, ifIP: 127.0.0.1
Hostname: xyz
Certificate name: certificatename.cer/crt
then entry in the hosts file should be 127.0.0.1 xyz certificatename.cer/crt
Login to Kyvos Manager.
In the navigation pane, click Kyvos and Ecosystem > Kyvos Properties.
On the Kyvos Properties page, in the Globals.properties section, search for the INTELLICUS_URL property and provide the Kyvos Reporting HTTPS URL:
If Kyvos and Kyvos Reporting are using the same certificates to run the URL in HTTPS mode, enter:
INTELLICUS_URL - https://<machine hostname>:port/kyvosreportingIf Kyvos and Kyvos Reporting are using different certificates to run the URL in HTTPS mode, enter:
INTELLICUS_URL - https://<certificate name>:port/kyvosreporting
Save the configuration and restart Kyvos Web Portal.
Go to Kyvos Reporting Portal and create a new connection.
...
After performing post-deployment steps, you can sign in to Kyvos Reporting Services to design smart reports, charts, and dashboards without knowing where and how the data is fetched from the database. For more information about Kyvos Reporting, see the Intellicus documentation.
Known Behavior
Anchor | ||||
---|---|---|---|---|
|
Selecting the Kyvos Reporting link from the Kyvos Manager dashboard redirects to the IP-based Kyvos Reporting URL, not the load-balanced Kyvos reporting URL.
TLS is not supported in Kyvos Reporting deployment.
All the Kyvos Reporting services (Kyvos Reporting Server and Kyvos Reporting Portal) are installed on the same node.
Migration of Kyvos Reporting services from one node to another is not supported.
Postgres instance is shared between Kyvos and Kyvos Reporting.
If Kyvos Reporting Service has already been deployed and you want to roll back the Kyvos Manager release earlier to 2024.2, then before performing Kyvos Manager rollback, you must remove Kyvos Reporting Service.
...