Skip to end of banner
Go to start of banner

2.6.1 Core Engine Setup

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

  • Introduction

  • AuditProxy and Data Connectors

  • LDAP Authentication

  • Web Server settings

  • Mailer settings

  • Access settings

  • Role settings

Hello. In this video, you will learn about AuditProxy — what it is, where it’s used, and how to configure it. To redirect requests from HTTP or HTTPS — from specific endpoints to appropriate ports that are used by different services — ACDI uses its ACDI Proxy service.

engine1.jpg

For example, if you use the endpoint “/opensearch,” it will redirect you to a port, defined as a local port for OpenSearch.

engine2.jpgengine3.jpg

If you need Opensearch dashboards or the ACDI server, all these services and ports have a direction table from the endpoint to the internal port.

engine4.jpg

This means that only one local port should be opened for external connections. For HTTP, by default, it is 3191 and for HTTPS it's 3190. So let's go to the Core Engine configuration page.

engine5.jpg

Go to “Administration,” then to “Core Engine.” Here you see cards with stand for settings components.

engine6.jpg

This first one is a list of all LDAP connections that are used to collect data from data connectors and by history browser to display the current state of objects.

engine7.jpgengine8.jpg

When you create a new data connector, the LDAP connection will be automatically added to this list of connections.

engine9.jpg

Here you can define a connection’s name, select connection type, eDirectory or Active Directory, and check if we will use this connection for the LDAP authentication.

engine10.jpg

You can also configure URL, timeout, define a user which is used to connect to the LDAP server, and TLS options.

engine11.jpg

The next Core Engine settings component is “LDAP authentication settings.” You can learn about how to configure the LDAP authentication in the respective video in SKyPRO Academy.  

engine12.jpg

The next one is “Web Server settings.” Here you can set if you need to use both HTTPS and HTTP. Ports, internal host names, timeouts, and level of debug are to be defined on this page as well as if you need logs to be sent to the console or to be saved to a file. These settings are extremely helpful for troubleshooting events in ACDI.

Also here you can find the path to a keystore with a certificate used by AuditProxy for HTTPS connection, its password, and a folder where you will store your JavaScript functions which can be used for data transformation.

engine13.jpg

Additionally, there are “Self-test settings” on this page.

engine14.jpg

Results of “Self-test settings” can be found in dashboards — ACDI System Health Dashboard.

engine15.jpg

Here you are able to check the amount of used disk space, RAM, CPU, and all other parameters enabled and configured in the self-test settings.

engine16.jpg

The “OpenSearch Stats settings” are to be found on this page. They are configured and used to monitor the health status of your OpenSearch.

engine17.jpg

Results of the OpenSearch status health checks are in the OpenSearch Health Dashboard.

engine18.jpgengine19.jpg

And the last setting here is Bypass bodyParser URLs.

engine20.jpg

Should you have any questions or require any assistance, please do not hesitate to contact us at any time swsupport.skypro@skypro.ch

  • No labels