Upgrading and migrating
Learn how to upgrade the product.
- Product changes when you upgrade from a previous version
  Learn about changes that might affect your scans or report data when you upgrade from a previous version. Make sure that you read all the topics so that you understand the upgrade process.
- Fix pack installation
  Fix packs are available for download from FNO.
- Replacing Jazz™ Team Server with WebSphere® Liberty - Frequently asked questions
  Beginning with v9.0.1, AppScan® Enterprise includes an architecture redesign to reduce the installation footprint and to remove Rational® Jazz™ Team Server (Jazz Team Server) as the user authentication component.
- Migrating Jazz Team Server users to Liberty in AppScan Enterprise
  To migrate Jazz Team users to use the Liberty authentication method, export a .csv file of users by using a command before you begin upgrading to v9.0.1 and higher. Then, you can follow one of the following two methods and register the same users in Liberty so that they can access AppScan Enterprise v9.0.1 and higher.
- Upgrading to the latest version of AppScan Enterprise
  For a successful upgrade to the latest version of AppScan Enterprise, read this topic carefully.
- Configuring the SQL Server database for AppScan® Enterprise
  The AppScan® Enterprise Server configuration needs information about SQL Server. Configure the SQL Server first to save time during the AppScan configuration. If you upgrade SQL Server to a newer version, follow these instructions as well.
- Configuring a basic user registry for the Liberty profile
- Using a certificate in your certificate store with Liberty
  This procedure describes how to use Liberty certificates to secure IIS.
- Upgrading the AppScan® Source LDAP connection with an Oracle database
  If you are changing LDAP settings (such as the server name or alias name) or if you are moving the AppScan® Enterprise Server to another computer, you must update the asc.properties file to reflect those changes.
- Enabling FIPS 140-2 or NIST SP800-131a on WebSphere Liberty Profile
  Use one of these procedures to enable FIPS 140-2 or NIST SP800-131a on WebSphere Liberty Profile.

Using a certificate in your certificate store with Liberty

This procedure describes how to use Liberty certificates to secure IIS.

Procedure

Optional: If you don't have a server certificate, create one from your certificate authority.
1. Generate a certificate request to send to your external certificate authority.
2. Send the certificate request to the certificate authority using a method that the certificate authority accepts.
3. When you receive the certificate, complete the certificate request.
Install AppScan Enterprise Server.
Run the configuration wizard.
In the Server Certificate window, choose a certificate specific to your organization. This step helps you deploy a secure AppScan® Enterprise in your environment. See Server Certificate.
In the Server Keystore screen, select a server keystore to be used by the Enterprise Console. If you exported a .pfx file, select Public key cryptography standards #12 (PKCS #12). Browse to the location where you saved the .pfx file, import it and enter the password you created when you exported the file. See Server Keystore.
Finish the configuration wizard.