![]() ![]() If you have any processes running outside the application server, such as monitoring daemons, you'll need to eliminate them or migrate them elsewhere. Identify all outside processes and daemons running on the production servers For more information, see Use Redis as a session cache with Tomcat. If session persistence is required, you'll need to use an alternate PersistentManager implementation that will write to an external data store, such as VMware Tanzu Session Manager with Redis Cache. Because App Service may load balance among several instances and transparently restart any instance at any time, persisting mutable state to a file system isn't recommended. Tomcat's built-in PersistentManager implementations, such as StandardManager or FileStore aren't designed for use with a distributed, scaled platform such as App Service. ![]() Look for the element, and then note the value of the className attribute. To identify the session persistence manager in use, inspect the context.xml files in your application and Tomcat configuration. For more information, see Serve content from Azure Storage in App Service on Linux. Dynamic or internal contentįor files that are frequently written and read by your application (such as temporary data files), or static files that are visible only to your application, you can mount Azure Storage into the App Service file system. We've provided a sample implementation for your use at Uploading and CDN-preloading static content with Azure Functions. If your application allows for static content that is uploaded/produced by your application but is immutable after its creation, you can use Azure Blob Storage and Azure CDN as described above, with an Azure Function to handle uploads and CDN refresh. For more information, see Static website hosting in Azure Storage and Quickstart: Integrate an Azure storage account with Azure CDN. You may wish to consider moving static content to Azure Blob Storage and adding Azure CDN for lightning-fast downloads globally. If your application currently serves static content, you'll need an alternate location for it. You may identify some or all of the following scenarios. You can view all certificates on the production server(s) by running the following command: keytool -list -v -keystore ĭetermine whether and how the file system is usedĪny usage of the file system on the application server will require reconfiguration or, in rare cases, architectural changes. Inventory certificatesĭocument all the certificates used for public SSL endpoints or communication with backend databases and other systems. These may include META-INF/context.xml, and, for Spring Boot applications, application.properties or application.yml files. ![]() You may also find configuration files containing passwords or credentials inside your application. Be sure to check server.xml and context.xml in $CATALINA_BASE/conf. Inventory secrets Passwords and secure stringsĬheck all properties and configuration files on the production server(s) for any secret strings and passwords. It's your team's responsibility to verify that you can satisfy every external dependency of your application after the migration. It isn't feasible to document every possible external dependency in this guide. Where can I find the JDBC driver JAR file?įor more information, see JNDI Datasource HOW-TO in the Tomcat documentation.What is the connection pool configuration?.For each datasource, document the following information: Datasourcesĭatasources are JNDI resources with the type attribute set to. In server.xml files, JNDI resources will be described by the elements inside the element. In context.xml files, JNDI resources will be described by the elements inside the top-level element. xml files found in $CATALINA_BASE/conf// directories. Inspect the $CATALINA_BASE/conf/context.xml and $CATALINA_BASE/conf/server.xml files as well as the. Some such resources may require migration or reconfiguration. Inventory external resourcesĮxternal resources, such as data sources, JMS message brokers, and others are injected via Java Naming and Directory Interface (JNDI). To obtain the current version used by Azure App Service, download Tomcat 9, depending on which version you plan to use in Azure App Service. To obtain your current Tomcat version, sign in to your production server and run the following command: $/bin/version.sh Download Java 11, 17, and all future LTS versions.These binaries are available for free download at the following sites: For Java 11, 17, and all future LTS releases of Java, App Service provides the Microsoft Build of OpenJDK. On Azure App Service, the binaries for Java 8 are provided from Eclipse Temurin. To obtain your current Java version, sign in to your production server and run the following command: java -version This validation is especially important if your current server is running on an unsupported JDK (such as Oracle JDK or IBM OpenJ9). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |