Content Migrated by the Tool for BES

Unmigrated Content

System logs: Tomcat system logs are configured in the logging.properties file. Only the log module name, log path, and log level are configured. BES can use its own system log configuration instead of Tomcat's.

Migrated Content

• Tomcat HTTP listener: If the listener of the listen port already exists in BES, the migration tool skips the listener and prompts you to manually migrate the listener. If you still want to use the migration tool for the migration, change the port and run the migration script again.
• Tomcat's virtual host: If a JDBC resource with the same name already exists in BES, the migration tool skips the virtual host and prompts you to manually migrate the virtual host. If you still want to use the migration tool for the migration, change the name and run the migration script again.
• SSL: The SSLHostConfig configuration of Tomcat 8.5 or later cannot be migrated. Only the common configuration that is the same as that of Tomcat 7 can be migrated.
• JVM attributes: Migrate the JVM attributes specified by JAVA_OPTS and CATALINA_OPTS in the catalina.sh script. However, the migration may not be accurate. You need to check the migration result after the migration is complete. A tag is added to the server.config file of BES. If you need to manually migrate JVM attributes, add subelements under the tag in the server.config file.
• Applications: The tool migrates all applications in the directory specified by docBase in the Host tag of the server.xml file, but does not migrate applications with the same names in BES. If applications are designated in the server.xml file, the tool migrates the application deployment information to the tag in the server.config file of BES, and copies the applications to the deployments directory of BES. In addition, the tool converts the private descriptor file of applications (META-INF/context.xml) into bes-web.xml. If an application is not configured in the server.xml file, the application is directly copied to the hotdeploy directory of BES and the private descriptor file is converted.
• User role groups: The tool reads the type="org.apache.catalina.UserDatabase" resources configured in the server.xml file of Tomcat to obtain the location of the Tomcat user file (for example, tomcat-users.xml). The user information in the tomcat-users.xml file is migrated to the conf/security/keyfile directory of BES. The corresponding user, password, and role are added. (The role is read from the role parameter of the Tomcat group.) In addition, the role mapping configuration of the corresponding file security domain is added to server.config.
• shared.loader in catalina.properties: The tool migrates the shared.loader configuration to the shared-loader-suffix attribute in the tag of the BES server.config file. Copy the JAR package specified by shared.loader to the lib/shared/tomcat directory of BES.
• JAR package: The tool migrates all JAR packages, except the JAR packages in the lib directory of Tomcat, to the lib directory of BES.
• JDBC: The tool migrates the JDBC resources configured in the conf/context.xml and server.xml files to the server.config file of BES. JDBC resources configured in <Engine>/<Host>/<Context>/<Resource> in the server.xml file are not migrated.