5.4.5 - Installing on Tomcat 6.0.x, 7.0.x - Teradata Warehouse Miner

Teradata Warehouse Miner Model Manager User Guide

Teradata Warehouse Miner
November 2017
User Guide

This topic explains how to install Model Manager into a Tomcat server.

In these examples, CATALINA_HOME refers to the Tomcat top-level directory. bin, conf, lib, logs, temp, webapps, and work are sub-directories.

Make sure that there are no spaces in the top-level directory name. The JSP compiler cannot find files under directories with spaces.

  1. Install Tomcat, and make sure it runs: CATALINA_HOME>/bin/startup.bat
  2. Shut down the Tomcat server.
  3. Put modelmanager.war in the CATALINA_HOME/webapps directory.
  4. From ModelManager.zip, extract activation.jar and mail.jar to the CATALINA_HOME/lib directory.
  5. Install the Teradata JDBC Driver by copying the tdgssconfig.jar and terajdbc4.jar files into the CATALINA_HOME/lib directory.
  6. Configure JAAS:
    1. Create a directory named Catalina/localhost under CATALINA_HOME/conf.
    2. Put jaas.config from ModelManager.zip in the CATALINA_HOME/conf/Catalina/localhost directory.
    3. Copy modelmanager.xml into the CATALINA_HOME/conf/Catalina/localhost directory.
    4. In the modelmanager.xml file, configure Realm for JAAS login under the Context tag as follows:
      Realm className="org.apache.catalina.realm.JAASRealm" 
         appName="mmLogin" useContextClassLoader="true"
  7. If the Windows Service Installer was used to install Tomcat:
    1. From the Windows Start Menu programs, select Apache Tomcat > Configure Tomcat.
    2. Add the following line at Java Options:
    3. Click OK.
  8. If the Windows Service Installer was not used to install Tomcat, append the Java OPTS option in CATALINA_HOME/bin/catalina.bat (catalina.sh on Linux):
    set JAVA_OPTS=%JAVA_OPTS% -Djava.security.auth.login.config=
  9. Configure the Email Server by modifying CATALINA_HOME/conf/Catalina/localhost/modelmanager.xml under Context tag and add JNDI for email server referencing an existing SMTP server for email notifications similar to the following example:
    Resource name="mail" auth="Container" type="javax.mail.Session" mail.store.protocol="pop3" mail.transport.protocol="smtp" mail.smtp.host="YOUR SMTP HOST ADDRESS" mail.smtp.port="25" mail.from="your.mailid@yourdomian.com"/

    For minimal configuration, the SMTP host needs to be a valid SMTP server that allows message relay to any destination. User ID and password are only needed if the SMTP server requires authentication.

  10. Create the metadata database:
    1. Set up Model Manager metadata database on a Teradata server by running the modelmanager_meta.sql script using a Teradata client application such as Teradata Administrator or Teradata SQL Assistant. The script creates a new database under DBC called MM_META_DATABASE.
    2. Issue the following SQL commands to establish appropriate privileges for two database users (although they may be the same) that will be used in the next step: GRANT SELECT, INSERT, UPDATE, DELETE ON MM_META_DATABASE. TO user1;


      where user1 and user2 are existing Teradata database users and TWM publish DB is the Miner publish database.

      MM_META_DATABASE and the Miner publish database may be on the same or different Teradata systems, with user1 and user2 defined on these same or different systems. user2 must have the privileges required to run the SQL for the published models.

  11. Configure the data source by modifying CATALINA_HOME/conf/Catalina/localhost/modelmanager.xml and add JNDI for mmMeta and mmData by filling in the server host names where the Model Manager metadata database and the Miner publish database reside. In each resource definition, the database user ID and password are the same user ID and password referenced in the previous step.
    Resource name="jdbc/mmMeta" auth="Container"
    	url="jdbc:teradata://TD SERVER NAME OR IP
     	maxActive="25" maxIdle="2" validationQuery="SELECT USER"/
    Resource name="jdbc/mmData" auth="Container"
    	url="jdbc:teradata://TD SERVER NAME OR IP
    	username="user2" password="PASSWORD"
    	maxActive="25" maxIdle="2" validationQuery="SELECT USER"/
  12. Start the Tomcat server and open a browser window to access Model Manager. Model Manager resides under the context modelmanager. By default, Tomcat runs on port 8080. In such case, the URL to access Model Manager is: http://localhost:8080/modelmanager/.
Two web user IDs have already been created within the Model Manager metadata database. They are mmadmin and mmuser. The former has an administrative role while the latter is a normal user. Use the same password as the user ID to log in.