Configuring TomEE with Derby, Oracle, or Microsoft SQL Server

You can use the TomEE Configuration Utility to set up the application server with either database. You can also use the TomEE Configuration Utility to change the configuration settings.

This task shows you how to:

Configure TomEE with Derby

  1. Start the TomEE Configuration Utility with the following batch file or script:

    • On Windows:

      <SEE_install_dir>\config\tomcat\bin\config.bat

      Note: You may have to run config.bat as Administrator if you do not have access rights.

    • On Linux:

      <SEE_install_dir>/config/tomcat/bin/config.sh

    This step is not necessary if the installer has already started the configuration utility.

  2. Select Derby as the database.
  3. Select either Configure existing database or Configure new database.
  4. If you chose Configure existing database, browse to the existing Derby installation directory.

    Note: If the existing Derby database you intend to select was created by Isight 5.9-x then, before you move to step 6 below, you must first rename two directories in the Derby Database directory.

    • Rename filemgr59 directory to filemgr
    • Rename Isight59 directory to Isight

    By default, the Derby Database directory for TomEE-Derby based SEE is

    • On Windows:
      <SEE_install_dir>\config\DerbyDatabase
    • On Linux:
      <SEE_install_dir>/config/DerbyDatabase

    unless you changed it explicitly during 5.9-x SEE installation/configuration.

  5. If you chose Configure new database, Derby will be installed at the default location.
  6. Click Next to define the LDAP configuration.
  7. Select one of the following:
    • Secured Mode (configure TomEE in secured mode).
    • Unsecured Mode (configure TomEE in unsecured mode).
    • Skip LDAP Configuration (skip the LDAP security configuration if you have already configured the mode and do not intend to change it).
  8. If you chose Secured Mode, enter the following information:
    • Connection URL: The location and the port number for the LDAP server. Typically, the port is 389.

      Use the following format:

      ldap://10.10.10.10:389/
      or
      ldap://ldapservername:389/

    • Connection Name: The distinguished name that is used to connect to the LDAP repository. For more information, consult your local system administrator. You can also find the information at the following URL: http://msdn.microsoft.com/en-us/library/aa366101%28v=vs.85%29.aspx.
    • Connection Password: The password for the user name.
    • User Base: The base entry for a user search. For more information, consult your system administrator.
    • Role Base: The base entry for a role search. For more information, consult your system administrator.
  9. Assign user(s) and/ or group(s) to the required roles by entering a list of user names and/ or group names separated by semicolons.
  10. Click Next to define the TomEE configuration.
  11. Enter the EJBD Port. The default is 4201.

    This port number will be reflected in the tomee.cpr connection profile file, which will be used by all SIMULIA Execution Engine clients to connect to the SIMULIA Execution Engine server.

  12. Select Install TomEE as a service if you want to configure the TomEE process as a service.
  13. Select one of the following:
    • HTTP (configure TomEE to use HTTP protocol).
    • HTTPS (configure TomEE to use HTTPS protocol).
  14. If you chose HTTP, enter the following information:
    • Webtop Port: Port number for Webtop application.
    • WebDashboard Port: Port number for WebDashboard application.
  15. If you chose HTTPS, you need to first import certificate in a keystore file (for more information, see Steps to create Keystore) before entering the following information:
    • Webtop Port: Port number for Webtop application.
    • WebDashboard Port: Port number for WebDashboard application.
    • Keystore path: Browse keystore file path.
    • Keystore Alias Name: Alias name of certificate.
    • Keystore Password: Keystore password used while creating the keystore file.
    • Key Password: Key password used while creating the keystore file.
  16. Click Finish and then OK to complete the utility.

Configure TomEE with Oracle

The TomEE Configuration Utility also supports the use of an Oracle database.

Before you begin: Before starting these steps, be sure you have completed all the steps described in Configuring an Oracle Database.
  1. Start the TomEE Configuration Utility with the following batch file or script:

    • On Windows:

      <SEE_install_dir>\config\tomcat\bin\config.bat

    • On Linux:

      <SEE_install_dir>/config/tomcat/bin/config.sh

    This step is not necessary if the installer has already started the configuration utility.

  2. Select Oracle as the database.
  3. Under Oracle Database Configuration with TomEE, enter the following values for your Oracle database:

    • Hostname
    • Port
    • SID
    • Username
    • Password

  4. In File Manager Setting, enter the path for the file manager.
  5. Click Next to define the LDAP configuration.
  6. Select one of the following:
    • Secured Mode (configure TomEE in secured mode).
    • Unsecured Mode (configure TomEE in unsecured mode).
    • Skip LDAP Configuration (skip the LDAP security configuration if you have already configured the mode and do not intend to change it).
  7. If you chose Secured Mode, enter the following information:
    • Connection URL: The location and the port number for the LDAP server. Typically, the port is 389.

      Use the following format:

      ldap://10.10.10.10:389/
      or
      ldap://ldapservername:389/

    • Connection Name: The distinguished name that is used to connect to the LDAP repository. For more information, consult your local system administrator. You can also find the information at the following URL: http://msdn.microsoft.com/en-us/library/aa366101%28v=vs.85%29.aspx.
    • Connection Password: The password for the user name.
    • User Base: The base entry for a user search. For more information, consult your system administrator.
    • Role Base: The base entry for a role search. For more information, consult your system administrator.
  8. Assign user(s) and/ or group(s) to the required roles by entering a list of user names and/ or group names separated by semicolons.
  9. Click Next to define the TomEE configuration.
  10. Enter the EJBD Port. The default is 4201.

    This port number will be reflected in the tomee.cpr connection profile file, which will be used by all SIMULIA Execution Engine clients to connect to the SIMULIA Execution Engine server.

  11. Select Install TomEE as a service if you want to configure the TomEE process as a service.
  12. Select one of the following:
    • HTTP (configure TomEE to use HTTP protocol).
    • HTTPS (configure TomEE to use HTTPS protocol).
  13. If you chose HTTP, enter the following information:
    • Webtop Port: Port number for Webtop application.
    • WebDashboard Port: Port number for WebDashboard application.
  14. If you chose HTTPS, you need to first import a certificate in a keystore file (for more information, see Steps to create Keystore) before entering the following information:
    • Webtop Port: Port number for Webtop application.
    • WebDashboard Port: Port number for WebDashboard application.
    • Keystore path: Browse keystore file path.
    • Keystore Alias Name: Alias name of certificate.
    • Keystore Password: Keystore password used while creating the keystore file.
    • Key Password: Key password used while creating the keystore file.
  15. Click Finish and then OK to complete the utility.

Configure TomEE with Microsoft SQL Server

The TomEE Configuration Utility also supports the use of Microsoft SQL Server database.

Before you begin: Before starting these steps, be sure you have completed all the steps described in Configuring Microsoft SQL Server Database.
  1. Start the TomEE Configuration Utility with the following batch file or script:

    • On Windows:

      <SEE_install_dir>\config\tomcat\bin\config.bat

    • On Linux:

      <SEE_install_dir>/config/tomcat/bin/config.sh

    This step is not necessary if the installer has already started the configuration utility.

  2. Select Microsoft SQL Server as the database.
  3. Under Microsoft SQL Server Database Configuration with TomEE, enter the following values for your Microsoft SQL Server database:

    • Server name
    • Port
    • Database name
    • Username
    • Password

  4. In File Manager Setting, enter the path for the file manager.
  5. Click Next to define the LDAP configuration.
  6. Select one of the following:
    • Secured Mode (configure TomEE in secured mode).
    • Unsecured Mode (configure TomEE in unsecured mode).
    • Skip LDAP Configuration (skip the LDAP security configuration if you have already configured the mode and do not intend to change it).
  7. If you chose Secured Mode, enter the following information:
    • Connection URL: The location and the port number for the LDAP server. Typically, the port is 389.

      Use the following format:

      ldap://10.10.10.10:389/
      or 
      ldap://ldapservername:389/

    • Connection Name: The distinguished name that is used to connect to the LDAP repository. For more information, consult your local system administrator. You can also find the information at the following URL: http://msdn.microsoft.com/en-us/library/aa366101%28v=vs.85%29.aspx.
    • Connection Password: The password for the user name.
    • User Base: The base entry for a user search. For more information, consult your system administrator.
    • Role Base: The base entry for a role search. For more information, consult your system administrator.
  8. Assign user(s) and/ or group(s) to the required roles by entering a list of user names and/ or group names separated by semicolons.
  9. Click Next to define the TomEE configuration.
  10. Enter the EJBD Port. The default is 4201.

    This port number will be reflected in the tomee.cpr connection profile file, which will be used by all SIMULIA Execution Engine clients to connect to the SIMULIA Execution Engine server.

  11. Select Install TomEE as a service if you want to configure the TomEE process as a service.
  12. Select one of the following:
    • HTTP (configure TomEE to use HTTP protocol).
    • HTTPS (configure TomEE to use HTTPS protocol).
  13. If you chose HTTP, enter the following information:
    • Webtop Port: Port number for Webtop application.
    • WebDashboard Port: Port number for WebDashboard application.
  14. If you chose HTTPS, you need to first import a certificate in a keystore file (for more information, see Steps to create Keystore) before entering the following information:
    • Webtop Port: Port number for Webtop application.
    • WebDashboard Port: Port number for WebDashboard application.
    • Keystore path: Browse keystore file path.
    • Keystore Alias Name: Alias name of certificate.
    • Keystore Password: Keystore password used while creating the keystore file.
    • Key Password: Key password used while creating the keystore file.
  15. Click Finish and then OK to complete the utility.