User cannot configure SMTP Mail Server
search cancel

User cannot configure SMTP Mail Server

book

Article ID: 9242

calendar_today

Updated On:

Products

DSERIES- SERVER ESP dSeries Workload Automation - System Agent (dSeries) ESP dSeries Workload Automation - Scheduler (dSeries) ESP dSeries Workload Automation

Issue/Introduction

  • The SMTP Mail server configuration is missing and DE Administrator cannot configure the SMTP Mail server in Admin perspective Topology view on the Desktop Client.
  • After initial installation, the SMTP Mail server address has changed, and ESP dSeries is not sending email notifications or alerts correctly because the new SMTP host configuration has not been updated or propagated to the database.
  • How to Update SMTP Mail Server Configuration Post-Installation for ESP dSeries.

Environment

Workload Automation DE (dSeries)

Cause

There could be several causes for this issue, including:

  • The DE (dSeries) installation program prompts for the SMTP Mail Server Address and Port during server installation but the server may not be able to setup the SMTP Server if the SMTP Mail server address is invalid.
  • The DE (dSeries) server's database configuration for the mail.smtp.host property has not been correctly populated or updated from the smtpconf.xml file after a post-installation change in the SMTP server address. The POPULATED flag in the ESP_VERSION table might be preventing the server from re-reading the configuration from the DBInit directory.

SMTP Mail Server Address - Specifies the name of your SMTP mail server.
Example: mail.example.com

 

Resolution

Prerequisites:

  • Database Administrator (DBA) Coordination: This procedure requires direct involvement and coordination with your DBA for database updates and backups.
  • Database Backup (Critical): The DBA must take a full backup of the ESP dSeries database before proceeding with these steps.

Verification Steps:

  • Query Database: Coordinate with your DBA to run the following SQL query against the ESP dSeries database:

    • select IN_USE_1,IN_USE_2,DESIRED from ESP_CONFIG_PROPERTY where NAME like 'mail.smtp.host';

      Interpretation: If this query returns no result, it confirms that the SMTP Mail server is not properly configured in the database, and you should proceed with the steps below.

  • Verify smtpconf.xml:

    • Navigate to the <DE_Install_dir>/conf/DBInit/Config/smtp directory.
    • Ensure the smtpconf.xml file exists and contains the correct and valid mail.smtp.host entry for your new SMTP server.

Procedure to Populate SMTP Configuration into Database:

If the smtpconf.xml file is correct, but the database query in Step 1 returns no results, follow these steps to force the database to be populated with the SMTP configuration data:

  1. Stop DE (dSeries) Servers:

    • If running in a High Availability (HA) environment, first stop the Standby DE server.
    • Then, stop the Primary DE server.

  2. Backup DBInit Directory:

    • Create a backup copy of the entire <DE_install_dir>/conf/DBInit directory (e.g., rename it to DBInit_bkup or copy it to a safe location). This preserves all initial configuration files.

  3. Clean DBInit Directory:

    • Navigate to <DE_install_dir>/conf/DBInit.
    • Crucially, remove all subdirectories within DBInit except the Config subdirectory. This ensures only the core configuration the server needs to re-read remains.

  4. Flag Database for Repopulation (DBA Action):

    • The DBA should connect to the ESP dSeries database.
    • Execute the following SQL command to set the POPULATED column in the ESP_VERSION table to zero (0):
      UPDATE ESP_VERSION SET POPULATED = 0;
    • Explanation: This flag tells the ESP dSeries server to re-read and populate its configuration data from the DBInit/Config directory upon its next startup.

  5. Commit DBA Changes:

    • The DBA must commit the change made in the previous step.

  6. Start DE (dSeries) Servers:

    • Start the Primary DE (dSeries) server.
    • If in an HA environment, then start the Standby DE (dSeries) server.
    • Note: During startup, the server will detect the POPULATED = 0 flag, read the smtpconf.xml (and other configurations in the Config directory), and update the database accordingly.

  7. Verify SMTP Configuration in Topology:

    • Once the DE servers are running, log into the ESP dSeries client.
    • Navigate to the Topology view and verify that the correct SMTP Server configuration is now displayed.

  8. Restore Other DBInit Files:

    • Copy all the directories except Config from your DBInit_bkup (created in Step 2) back to the original <DE_install_dir>/conf/DBInit directory. This restores any other initial configuration files that were temporarily removed in Step 3, ensuring the complete configuration is available.

Additional Information

Configuring the SMTP Server

Powered by Wolken Software