Email setup notes

This solution requires that you have an email infrastructure in place, including a properly configured SMTP server and configurations in some Service Manager files.

Configurations in the sm.ini file

Open the sm.ini file using a text editor and verify that the following parameters are correctly configured.

Parameter Description
querysecurity:1 Enforces the Service Manager server to require a security hash with Web tier URL queries.
queryhashcode:hostname:port

Enables all Service Manager processes to consistently generate a unique hash code, which can be accepted and properly decoded by the Web tier. The parameter value must be a combination of the Service Manager hostname and communications port. If you provide the fully qualified domain name (FQDN) of a server host in web.xml, you need to provide the same value in this parameter.

Example:

queryhashcode:smserverhost:13080

smtphost:smtpserverhost

Specifies the name of the SMTP server host for client requests. The value for the parameter can be the IP address, machine name, or DNS name of the SMTP server uses for sending notifications.

Example:

smtphost:smtpserverhost

smtpport:port

Specifies the communications port the SMTP server uses.

Example:

smtpport:25

mailFrom:EmailAddress

Specifies the descriptive name or other identifier of the sender of an e-mail. This parameter should be set in the format of email address.

Example:

mailFrom:accountname@microfocus.com

For more information about the JavaMail connection parameters, see System configuration parameters.

Configuration in the web.xml file

Open the web.xml file that is located in the $TOMCAT_HOME\webapps\webtier-9.61\WEB-INF folder using a text editor, and add the following text at the end of the file if it does not exist.

<init-param>
<param-name>querySecurity</param-name>
<param-value>true</param-value>
</init-param>

When this parameter is enabled, the Service Manager Web tier embeds a security key in all queries generated by the Web client. The Service Manager server verifies the security key and, if valid, authorizes the query.