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.

  1. What exactly is being replaced, and why?

    With the removal of Jazz™ Team Server, the Apache Tomcat and WebSphere® Application Server deployment servers are no longer supported in v9.0.1. They are replaced with IBM® WebSphere® Application Server Liberty Core v8.5.5.2. Liberty is a lightweight version of IBM® WebSphere®, and because it is embedded in AppScan® Enterprise, there are no separate installation and configuration steps required. Liberty has a lighter footprint, optimizes resource usage, and eliminates the need to administer users in an extra database.

    Note: In AppScan Enterprise v9.0.2, support for Liberty Server v8.5.5.2 has been replaced with v8.5.5.4.
  2. What is WebSphere® Liberty?

    IBM® WebSphere® Liberty is a lightweight version of WebSphere®, and is easier to install and configure. Liberty is embedded into AppScan® Enterprise 9.0.1, eliminating the need to install an extra component in your environment.

  3. What operating systems does it run on?

    Liberty runs on the same OS as AppScan® Enterprise: Windows™ and Linux™ Redhat (for AppScan® Source user administration component only).

  4. What happens to my Jazz™ Team Server settings during upgrade to v9.0.1?

    During upgrade, the Jazz Team Server folder is backed up and stored in the installation folder (JazzTeamServer.bak) and the Liberty server is installed. Static credentials are not preserved in case LDAP does not allow anonymous access. During configuration, you are prompted to provide your user name and password for the LDAP server.

  5. Can I roll back to using Jazz™ Team Server?

    You can roll back to AppScan® Enterprise v9.0.0.1 and use Jazz™ Team Server. You will not be able to take advantage of any new products features in v9.0.1, as Jazz™ Team Server is not supported.

  6. I am using Jazz Team Server users without LDAP or Windows authentication. How do I migrate my users to this new authentication method?

    You can export a .csv file of users by using the cd <install-dir>\Appscan Enterprise\JazzTeamServer\server\ repotools-jts.bat -exportUsers toFile=C:\users.csv repositoryURL=https://<hostname>:9443/jts. Then follow the steps in Migrating Jazz Team Server users to Liberty in AppScan Enterprise to import the users into Liberty.

  7. I still use WebSphere® Application Server for other IBM® applications. Will I need to do anything to make sure that nothing is affected by these new changes in v9.0.1?

    WebSphere® Application Server can co-exist with Liberty, provided they use different ports. During AppScan® Enterprise configuration, you can change the port number for Liberty from 9443 to use a different number.

  8. What happens to the ASC application of AppScan® Enterprise that runs on Tomcat?

    WebSphere® Liberty Profile replaces Tomcat + Jazz™ Team Server + ASC. A Liberty profile is created, and uses the same instance name as AppScan® Enterprise. The configuration wizard makes all of these changes for you. You can remove the reference to the ASC application in WebSphere® Application Server if you wish. The asc.properties file is kept after upgrade for use if you use AppScan® Source with an Oracle database.

  9. In my current environment, I have a Jazz™ Team Server for ASE and a different Jazz™ Team Server for Rational® Quality Manager. They are both pointing to the same LDAP server. What happens to My RQM Jazz™ Team Server instance if you are removing Jazz™ Team Server from AppScan® Enterprise v9.0.1?

    Both products use different versions of Jazz™ Team Server, and so the Jazz™ Team Server version used by Rational® Quality Manager will not be affected by the removal of Jazz™ Team Server in AppScan® Enterprise v9.0.1. During upgrade, the AppScan® Enterprise installer removes the Jazz™ Team Server that the previous version used and replace it with Liberty. The new Liberty server is used to point to the LDAP server. Because Rational® Quality Manager and AppScan® Enterprise have the same user base registered in the LDAP server, users are still recognized by both products. No extra work is required to re-input users.

  10. Will AppScan® Enterprise retain the mapping between user groups and LDAP groups?

    Yes. We retain the server host, server port, base dn, and the uid mapping.

  11. Do I need any certificates for Liberty to secure IIS?

    Yes. If you don't have a server certificate, you can request one from your certificate authority and then use it during the configuration wizard. See Using a certificate in your certificate store with Liberty.

  12. I'm a US federal government agency. Does Liberty support FIPS 140-2 and NIST SP800-131a security standards?

    Switching to Liberty does not affect the level of support that is provided in previous versions. See Enabling FIPS 140-2 or NIST SP800-131a on WebSphere Liberty Profile.

  13. I use a non-standard port number for Jazz™ Team Server. Will the move to Liberty respect this use?

    Yes. Using a non-standard port is supported; modify the default port during configuration.

  14. Can I upgrade from all previous versions of AppScan® Enterprise? What happens for my particular deployment scenario?
    All previous versions can upgrade to use Liberty. This table explains how the upgrade works for each deployment scenario:
    Table 1. Scenario migrations

    Upgrade scenarios
    Scenario Upgrading from older versions to V9.0.1
    Jazz™ Team Server + LDAP on local server During upgrade, the Jazz Team Server folder is backed up and stored in the installation folder (JazzTeamServer.bak) and the Liberty server is installed. Static credentials are not preserved in case LDAP does not allow anonymous access. During configuration, you are prompted to provide your user name and password for the LDAP server.

    During configuration, AppScan® Enterprise pre-populates as many of the LDAP settings from the backup it made during installation. You must complete the LDAP settings.

    AppScan® Source (using LDAP users with SolidDB) During upgrade, the Jazz Team Server folder is backed up and stored in the installation folder (JazzTeamServer.bak) and the Liberty server is installed. Static credentials are not preserved in case LDAP does not allow anonymous access. During configuration, you are prompted to provide your user name and password for the LDAP server.

    During configuration, AppScan® Enterprise pre-populates as many of the LDAP settings from the backup it made during installation. You must complete the LDAP settings.

    Jazz™ Team Server with Windows™ authentication (also applies to AppScan Source with Windows authentication) During installation and configuration, all the necessary settings are propagated. No user action is required.
    Jazz™ Team Server + LDAP on remote server During configuration, you must enter LDAP settings when prompted. You can delete the ASC application from Jazz™ Team Server if wanted.
    Jazz™ Team Server (using JTS user authentication only) on local or remote server You must manually add those users into the Liberty server.xml file. This file is stored in <install-dir>\AppScan Enterprise\Liberty\usr\servers\ase.
    WebSphere® Application Server + LDAP on remote server During configuration, you must complete the LDAP settings when prompted. You can delete the ASC application from WebSphere® if wanted.
    AppScan® Source (using ASE Jazz Team Server users) During installation, AppScan® Enterprise uninstalls Jazz™ Team Server on Tomcat, makes a backup of the settings, and then deletes Jazz™ Team Server. Nothing changes during configuration.
    AppScan® Source (using LDAP users with Oracle Source DB) Change the filepath in the asc.properties file from Jazz™ Team Server to Liberty. See Upgrading the AppScan Source LDAP connection with an Oracle database.