Public URI missing in in JTS Setup running WAS 7.0.0.17

I have performed all the prerequsite steps but the public URI is not showing up in the Configure Public URI page. How can I resolve this issue?

Here are the steps that I have performed to get CLM 3.0.1 to run on WAS 7.0:

1. Install & Configure WAS 7.0
- Create a WAS profile named "JTS" with default 9080 and 9443 ports
- Set the JVM min and max heap size to 100 and 1250
- Create the following environment entries:
- JAZZ_HOME: file:///C:/JTS/server/conf
- java.awt.headless: true
- org.eclipse.emf.ecore.plugin.EcorePlugin.doNotLoadResourcesPlugin: true
- log4j.configuration: file:///C:/JTS/server/conf/startup_log4j.properties
- Configure the Local operation system relam and set it as the current relam
- Assign a local admin user as the Primary administrative user name
- Enable administrative & application security, and disable Java 2 security
- Click Administrative group roles, search and add the "Administratives" group
- Enable Web and SIP security > General Settings > Use available authentication data when an unprotected URI is accessed
- Restart the "JTS" WAS profile

2. Install CLM 3.0.1.x
- Install all features except for Requirements Management, Quality Management and the Application Server to C:\JTS
- Update the C:\JTS\server\conf\jts\teamserver.properties & C:\JTS\server\conf\ccm\teamserver.properties
- Comment out Derby database properties and uncomment the DB2 database properties
- Updated the com.ibm.team.fulltext.indexLocation and com.ibm.team.jfs.index.root.directory properties to point to absolute paths
- Create the empty DB2 repository DB for JTS and CCM and run the following commands:
- repotools-jts -createTables -clean
- repotools-ccm -createTables -clean

3. Deploy the CLM 3.0.1.x WAR files
- Install the following WAR files and assign the appropriate context roots:
- C:\JTS\server\webapps\admin.war (root: /admin)
- C:\JTS\server\webapps\ccm.war (root: /ccm)
- C:\JTS\server\webapps\clmhelp.war (root: /clmhelp)
- C:\JTS\server\webapps\jts.war (root: /jts)
- Perform the Security role to user/group mapping for the ccm_war and jts_war Web apps
- Restart the "JTS" WAS profile

4. Run the JTS Setup tool
- Open browser and access https://<fully_qualified_hostname>:9443/jts/setup
- Log on using a local admin user name and password
- The Introduction page is displayed, click Next
- The Configure Public URI page is displayed but the URI field is empty!

Please note that when I installed the same CLM 3.0.1 build on the same machine and ran it on Tomcat and Derby, the public URI did show up and I was able to complete the setup.