data_engine IM Configuration

uimpga-ga
data_engine_IM
Prerequisites
The data_engine probe requires the appropriate version of the 
compat-libstdc++
 runtime library to be installed on your system. The correct version is required for C++ runtime compatibility. The copy of distribution-specific 
compat-libstdc++
 runtime library can be obtained from one of the following links:
For CentOS, follow these steps to get the 
compat-libstdc
 library:
  1. Go to 
    Programs
     > 
    System
     > 
    Add/Remove Software
     
    .
     
  2. Select the 
    Searc
    h tab and search for 
    compat-libstdc
     and use 
    33
     library.
  3. For 
    5
     compatibilities, select the appropriate version of the compat-libstdc++ library for your distribution and install it.
 
Contents
 
 
 
Configure the data_engine by selecting the data_engine probe in Infrastructure Manager, then right-click and select Configure. You can view the default settings for all fields in the data_engine.cfx file in the system files: for example, under <UIM_install>\Nimsoft\probes\slm\data_engine.
The following limitations are applicable for the Standard Edition of Microsoft SQL Server:
  • Table partitioning is not supported in the Standard Edition of Microsoft SQL Server. Therefore, the data maintenance jobs and the index maintenance jobs, which are scheduled from the data_engine probe UI, will not be effective because of the unsupported version.
  • During the scheduled data maintenance job, the data is deleted in batches based on the values set in the data_engine configuration file. Ensure that enough space is available on the drive where the transaction log file is located to avoid space issues.
  • During the table maintenance and the index maintenance, you must use the offline option in the data_engine UI before scheduling the index maintenance. The online index maintenance is not supported in the Standard Edition of Microsoft SQL Server.
The General Tab
The General tab displays the appropriate data management default attributes based on the database you are using. These attributes differ for SQL Server, MySQL, and Oracle databases.
The General tab contains the following subsections:
 
Data Management default values
: The default settings for data maintenance. These settings apply to all QoS settings unless they have been individually overwritten in the Quality of Service settings.
  •  
    Compress data before delete
    : If selected, compression is done on raw data and copied into historic tables before a delete is performed. And historic data is compressed and aggregated into Daily Data, before deleting it from the HN tables.
  •  
    Delete raw data older than
    : Raw data older than the indicated the number of days is deleted.
  •  
    Delete historic data older than
    : Historic table data older than the indicated the number of days is deleted.
  •  
    Automatically reindex tables
    : Perform table reindexing with other maintenance routines, which by default are executed every 24 hours.
     You cannot rebuild the index for single partitions for SQLServer 2014 or earlier. You can only reorganize individual partitions. We do not recommend automatic indexing for large tables from the data_engine, as indexing might not complete in a reasonable amount of time.
  •  
    Index maintenance properties (SQL Server option only)
    : Click the 
    Advanced 
    button to activate or deactivate the index maintenance properties. For more details, go to the Index Maintenance Properties section. This option will not appear if you are using Oracle or MySQL.
  •  
    Partition data tables (SQL Server option only): 
    Option to partition the data tables.
    Although you can select the 
    Partition data tables
     check box for data_engine v8.3, this function has been disabled within IM. If you select this check box in IM, the data tables are not partitioned. Use the data_engine configuration in Admin Console to turn on partitioning for Microsoft SQL Server Enterprise Edition and MySQL databases.
 
Log Setup
: This section allows you to set the log level details.
  •  
    Log Level
    : Sets the level of details that are written to the log file. Log as little as possible during normal operation to minimize disk consumption, and increase the amount of detail when debugging.
 
Status
: This button opens the Status window and provides the current work status of the probe. For more details, see the Status Window section.
 
Statistics: 
This section displays the current transmission rate for transferring QoS messages into the database.
Index Maintenance Properties (SQL Server Only)
To configure the index maintenance properties, click the 
Advanced 
button in the 
General 
tab. 
 
Maintenance mode:
 Defines how the indexes are maintained.
  •  
    Dynamic:
     Maintenance is performed based on the index statistics.
  •  
    Reorganize:
     Maintenance is performed using the "alter index ... reorganize" SQL Server script.
  •  
    Rebuild: 
    Maintenance is performed using the "alter index ... rebuild" SQL Server script.
     You cannot rebuild the index for single partitions prior to SQLServer 2014. You can only reorganize individual partitions. We do not recommend that you perform automatic indexing for large tables, as indexing might not complete in a reasonable amount of time.
 
Online mode:
 Defines the effect of maintenance on concurrent use of the QoS tables.
If partitioning is enabled on SQL Server, online mode is not supported.
  •  
    Dynamic:
     The maintenance is determined by the edition of SQL Server. In SQL Server Enterprise Edition, Online mode is used for maintenance (if the chosen maintenance mode supports it). Otherwise, offline mode is used.
  •  
    Online:
     The QoS tables are available for update and query during the table maintenance period. Online mode offers greater concurrency but requires more resources.
  •  
    Offline: 
    The QoS tables are unavailable for update and query during the table maintenance period.
 
Fragmentation Level:
 The fragmentation level information is used if Index name pattern is anything other than "All".
  •  
    Low Threshold
    : If the fragmentation for an index is less than the low threshold percent value, then no maintenance is performed.
  •  
    High Threshold
    : If Dynamic maintenance mode is selected and fragmentation is between the low and high threshold percentages, then the Reorganize mode is used. Otherwise the Rebuild mode is used.
  •  
    Index name pattern
    : The indexes that are maintained. The default is Blank, which indicates a blank entry that results in all indexes being considered for maintenance.
The Quality of Service Type Status Window
Clicking the 
Status 
button opens the Quality of Service Type Status window. This window provides data regarding the QoS tables and is read-only.
The status is based on statistics that are generated by the database provider. If incorrect information is displayed, you might need to update the table statistics. For more information, see Out-of-date Information in the Quality of Service Type Status Table section in the Troubleshooting article.
The Database Tab
 The database connection properties should only be changed in limited circumstances such as recovery operations. Changing the Database Vendor can cause connection issues. If you are changing database vendors, CA recommends reinstalling CA Unified Infrastructure Management.
The Database tab enables you to specify the database connection settings. The currently supported databases include:
Microsoft SQL Server Options
  •  
    Database vendor
    : Select the name of the vendor of the database. For MS-SQL, select
     Microsoft 
    option.
  •  
    Provider
    : The ADO provider that is used for the database connection. For TLS 1.2 support, SQLNCLI11 is required.
  •  
    Initial Catalog
    : The database name
  •  
    Data Source
    : The database server
  •  
    User ID
    : The login user
  •  
    Password
    : The login user password. Ensure that the password does NOT contain any special characters (such as "
    ;
    ").
  •  
    Parameters
    : Other parameters to the OLEDB connection.
  •  
    Test Connection
    : Click the button to verify the current connection setup.
  •  
    Enable TLS
    : Select the option to enable TLS v1.2 in CA UIM, which lets the UIM Server to establish a secure communication with Microsoft SQL Server (UIM database). For more information about TLS v1.2 support, see Support for TLS v1.2 (Microsoft SQL Server).
  •  
    Always Trust Server Certificate
    : Select the option to allow the system to trust the server certificate. If you select this option, you do not need to provide the TrustStore file location and associated password.
  •  
    Trust Store File (.jks)
    : Browse to the location where you have created the source .jks file. This file includes your database server security certificate. You can use keytool to create your source .jks file. For more information about how to create the source .jks file using keytool, see "Create Java KeyStore (.jks File) for Server Certificate" in Support for TLS v1.2 (Microsoft SQL Server). For additional information about keytool, see keytool - Key and Certificate Management Tool.When you click 
    Apply
     or 
    OK
     after providing the TrustStore file and password information, the data_engine probe copies the source .jks file and places it in the
    <uim>\Nimsoft\security
    folder as truststore.jks. The
    <uim>\Nimsoft\security
    location is then displayed in the 
    Trust Store File (.jks)
     field.
    Additionally, see the "Additional Information" section in Support for TLS v1.2 (Microsoft SQL Server) to review the steps that are required to enable TLS v1.2 in upgrade scenarios and in situations where you want to enable TLS v1.2 support after the UIM Server installation.
  •  
    Trust Store Password
    : Specify the password to access the source .jks file.
     When you click the 
    Test Connection
     option, CA UIM does not verify the validity of the specified .jks file. Instead, it verifies the validity of the certificate that you have imported into the Microsoft Management Console (MMC) on the UIM Server.
The following screenshot shows all the configuration options, including TLS v1.2 options (
Enable TLS
Always Trust Server Certificate
Trust Store File (.jks)
Trust Store Password
):
SQL_IM_TLS_Options.jpg  
 If you install 
CA Unified Infrastructure Management
 and MS-SQL on a nonstandard port, you must configure the data_engine "server" parameter to include the port. For example: "<server>,< port>".
MySQL Options
  •  
    Database vendor
    : Select MySQL option.
  •  
    Schema
    : Enter the database schema name
  •  
    Server Host
    : Enter the database server name or IP address
  •  
    Port
    : Enter the port number to connect to the database server
  •  
    Username
    : The login user name
  •  
    Password
    : The login user password
    Ensure that the password does NOT contain any special characters (such as "
    ;
    ").
Click the 
Test Connection
 button to verify the current connection setup.
Oracle Options
  •  
    Database vendor
    : Select Oracle option.
  •  
    Hostname
    : Enter the database server name or IP address
  •  
    Port
    : Enter the port number to connect to the database server
  •  
    Username
    : The login user name
  •  
    Password
    : The login user password. Ensure that the password does NOT contain any special characters (such as ";")
  •  
    Service Name
    : Enter the Service name.
  •  
    Test Connection
    : Click the button to verify the current connection setup.
  •  
    Enable TLS
    : Select the option to enable TLS v1.2 in CA UIM, which lets the UIM Server to establish a secure communication with Oracle (UIM database). For more information about TLS v1.2 support, see Support for TLS v1.2 (Oracle).
  •  
    Need Client Authentication
    : Select the option to specify whether you want to enable client authentication.
     
  •  
    Wallet Type
    : Select the wallet type from the drop-down list. The selected wallet type takes the precedence. Note that both SSO and PKCS12 are copied to the UIM Server (
    <uim>\Nimsoft\security
    ) irrespective of the wallet type you select.
  •  
    Wallet Location
    : Specify the location of the client wallet where your trusted security certificates are available. This location includes your trusted security certificates. data_engine copies the required wallet files from this location and places them in the 
    <uim>\Nimsoft\security
     folder. For more information about how to work with certificates using wallets, see Support for TLS v1.2 (Oracle).
    Additionally, see the "Additional Information" section in Support for TLS v1.2 (Oracle) to review the steps that are required to enable TLS v1.2 in upgrade scenarios and in situations where you want to enable TLS v1.2 support after the UIM Server installation.
  •  
    Wallet Password
    : Specify the password to access the wallet information.
The following screenshot shows all the configuration options, including TLS v1.2 options (
Enable TLS
Need Client Authentication
Wallet Type
Wallet Location
Wallet Password
): Oracle_IM_TLS_Options.jpg  
The Quality of Service Tab
The tab contains a list of all the QoS types that are defined in the database.
  •  
    QoS Name
    : The QoS type name
  •  
    Description
    : Description of the QoS type
  •  
    QoS Group
    : The QoS group is a logical group to which the QoS belongs (optional)
  •  
    Unit (abbrev.)
    : The abbreviated unit of the QoS data
  •  
    Has Max Value
    : Indicates the data type has an absolute max
  •  
    Is Boolean
    : The Boolean state
    Example: host is available, printer is up.
  •  
    Type
    : Different data types:
    0 = Automatic (The sample value is read at fixed intervals, individually set for each of the probes).
    1 = Asynchronous (the sample value is read only each time the value changes, and the new value is read.
The individual QoS definitions can be edited to have specific values:
  1. Double-click a row in the Quality of Service tab to open the Override window.
  2. Select "Override with" to specify a value to change the default QoS definitions. 
  3. Click 
    OK
    , then click 
    Apply 
    to save your changes.
The Schedule Tab
The Schedule tab is used to schedule the process of data maintenance.
  • Range
    •  
      Start now
      : Select this option to start the data maintenance process now.
    •  
      Start at
      : Select the date from the calendar by clicking the drop-down arrow. This date and time indicates the time when the data maintenance starts.
    •  
      No end date/End after/End by
      : Select an option to end the data maintenance process.
      • Select 
        No end date
         option to continue the data maintenance process non-stop.
      • If you select the 
        End After
         option, enter the number of occurrences in the box.
      • If you select the 
        End by
         option, then select the date from the calendar by clicking the drop-down arrow.
  • Pattern: The options for the pattern changes depending on your duration selection.
    •  
      Minutely/Hourly/Daily/Weekly/Monthly/Yearly
      : Select the duration pattern at which you want the data maintenance process to run.
    •  
      Every/ Every <pattern>
      : For the selected pattern, specify time more precisely. The options in this section change for each duration pattern. For example, if you select Minutely:
      • Select Every to set minutes manually by entering the minute in the box.
      • Select Every minute to run the data maintenance every minute.