Jis flangedimensions pdf

The approach for replatforming application libraries and dependent software is similar to the approach for OSs but you only upgrade the libraries. You then test the application's functionality and replicate the required libraries in your pre-production and production servers. Typically, the COTS application's vendor handles the required updates for application components through their ongoing software releases.

The replatforming approach for application components that run on unsupported OSs is different for each application component. The following table summarizes the replatforming options available for application components that reached EOS.

Jis flangedimensions

Hardened Class 10.9 JIS Flange Bolts eliminate the need for a separate washer, distributing tightening force over a greater area.

JIS10KFlangedimensions pdf

COTS applications – Contact the application's vendor and request application binaries that are certified for the required OS or application server versions.

JIS flangevs ANSIflange

To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.

If you replace unsupported application servers (for example, Apache Tomcat 6.0, Apache 2.2, or IIS 7.x), your new application server versions might require an underlying OS upgrade. Most unsupported OSs are Red Hat Enterprise Linux (RHEL) versions 5 and 6, CentOS versions 5 and 6, or Windows 2008 R2. You should deploy the following steps for applications running those OSs:

For legacy COTS applications that run Windows Server and don’t work with the most recent OS, we recommend using the AWS End-of-Support Migration Program (EMP) for Windows Server to package the application and run it on the latest Windows version in an EC2 environment.

We recommend that you compile and rebuild your in-house application’s software by using the most recent OS and software runtime versions (for example, Java, C++, .NET, or Python). You can then clone the existing application environment, manually deploy and validate the functionality, and update your build environment to the most recent OS, runtime software components, and libraries before upgrading to your production environment.

Most COTS application vendors support Windows 2016 or RHEL 7. If your legacy COTS application doesn't support Windows 2016, we recommend an in-place upgrade from Windows 2008 R2 to Windows 2012 R2 by using the in-place upgrade option provided by Microsoft. You can also use AWS Systems Manager Automation runbooks to automatically upgrade Windows Server running on EC2 instances. We recommend that you contact the application’s vendor and ask them to certify their software for the latest OS version.