• Post Reply Bookmark Topic Watch Topic
  • New Topic

Not able to start Tomcat, Failed to initialize end point associated with ProtocolHandler  RSS feed

 
Alex Orozco
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi everyone,

This problem seems simply, just an issue with the ports, but I just cant get this work, here is what I'm trying to do:

I'm trying to install JTS (Jazz Team Server, Rational Team Concert) and CCM, so I download the zip and ran the server.startup.bat script, but it takes too long to deploy the admin.war, I left the console open for 1 day! and there's no new messages on the console, the log have the same info from the console, I tried on 3 different machines, 2 with win 7 and 1 with win server 2008, all with 8GB of memory and core i5, so, I don't think is a performance issue, then I realize that Tomcat is not starting, if I ran the startup.bat script under the bin folder I get this error:

The weird thing is that if I change the port on the server.xml I get the same error but now pointing to the new port, i.e. if I set this port 9995, I got this error:

Every time I change it it shows the new port on the error, after several configurations I'm still getting:

I check the 3 ports using the command netstat -aon | findstr xxxx, and all of them are used by java.exe but only when the Tomcat console is opened, after closing it and recheck the ports with the same command, the ports are free, I'm really confused, because if I change the ports I get the same error but now with the new ports.

can anybody help me with this?
Thanks.
 
Roger Sterling
Ranch Hand
Posts: 426
Eclipse IDE Fedora Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What method are you trying to use to do the installation ? Are you using Installation Manager ? Is it possible you have multiple installs going on at the same time, thereby creating the port conflicts ?

 
Alex Orozco
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's not through Installation Manager, I'm just running the server.startup.bat, I tough that only running this script I can configure a new Project Area via web admin console
 
Roger Sterling
Ranch Hand
Posts: 426
Eclipse IDE Fedora Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What URL did you use to download the package ? AFAIK, you cannot simply download the package, unpack it, and run something. You must perform the installation steps either through Installation Manager or Command line. If you post the URL, I can check to see the exact steps needed to install it for you.

You must accomplish the stpe-by-step instructions before you can use the product. Here's one flavor :


Planning checklist
Install the server
Set up the database
Start the Apache Tomcat server
Run the setup wizard
You have installed the server!
Install the Rational Team Concert client for Eclipse IDE
To install the Rational solution for CLM products follow these steps:

1Planning checklist Back to top
Before you install the Rational solution for Collaborative Lifecycle Management products, ensure to review the information in the following planning checklist.
Planning task More information
Verify that your hardware and software meet the minimum system requirements. There are new requirements for version 4.0 like supporting only 64-bit server operating systems. System requirements
Get the product installation media. For local repository download, you need approximately five gigabytes (5 GB) of hard drive space to download and extract your product installation media. The server installation files can be downloaded from jazz.net
Review your installation topology. Whether you are trying out the CLM solution, or installing the solution in your production environment, click the link at the right to see and study different installation topology examples. The examples include: evaluation topology, departmental topoloy, and enterprise topology. Installation topology examples
Synchronize the clocks on all machines. In a distributed environment, ensure that the clocks on all machines are synchronized using the Network Time Protocol (NTP). For more information about NTP, visit ntp.org
Know your database prerequisites:
The user who creates the database table must be a member in the sysadmin fixed server role, or an owner of the database (dbo).
You have the correct user name and password for the user who is creating the database.
The Java Database Connectivity (JDBC) driver is installed. Rational solution for CLM 4.0 no longer supports JRE 5.0. The version of supported JREs are 6.0 and 7.0. The sqljdbc.jar class library requires JRE 5.0 and the sqljdbc4.jar class library requires JRE 6.0 or later. You must use sqljdbc4.jar.
The SQL service is started.
Setting up an SQL Server database
Learn about licensing. The licensing scheme for version 4 products is role-based. When you purchase a role-based license, you will have read, write, and comment access to some or all of the capabilities of the Change and Configuration Management, Quality Management, and Requirements Management applications. Understanding licensing
2Install the server Back to top
When using IBM Installation Manager, there are two methods to install Rational solution for CLM products:
- Installation Manager Web Install: This archive file contains the Installation Manager launchpad program and the predefined installation repository locations. The benefit of using the Web install package is that it reduces the size of initial download and the installation process downloads only the resources you choose to install.
Note: The Web-based installation requires an Internet connection during the installation process.
- Local installation repository: This archive file contains a local copy of all the installable resources. The benefit of using the local install package is that it allows the installation to proceed without an Internet connection. To install using this method, extract the archive file to a temp directory. Start IBM Installation Manager. Select File > Preferences, click Add Repository and browse for the repository.config file in the directory that you extracted the archive file. Click OK to close the Preferences window and click Install to start the installation.
If you are installing all applications on one server (not recommended for medium and large scale deployments), from launchpad click Jazz Team Server with Required Base Keys, including Trials, and CCM, QM and RM Applications.
To install Jazz Team Server, from launchpad click Jazz Team Sever with Required Base Keys, including Trials.
To install Change and Configuration Management application, from launchpad select CCM, QM, and/or RM Applications. Choose this option if you have already installed Jazz Team Server. This option does not offer you to install the required base keys as they were installed with Jazz Team Server. During installation ensure that Change and Configuration Management check box is selected.
For more information, see Installing the server using IBM Installation Manager (The complete content of this topic has been loaded into this document and appears immediately below).
Installing > Installing the Rational solution for CLM > Installing Jazz Team Server and the CLM applications
This topic describes the process of installing the Rational solution for Collaborative Lifecycle Management (CLM) products with IBM® Installation Manager.
About this task

There are two ways to download and install version 4 products. You can perform a web-based installation that includes a smaller download and connects to the Internet during the installation to get the repository files. If you must install the server in an environment without Internet access, you can download and extract all repository files to a local computer to install the server locally. Instructions for both methods are provided in this topic.
Note: You cannot install the Jazz™ Team Server on the IBM i or z/OS® operating systems with Installation Manager.
Note: For instructions about installing the IBM Rational® Team Concert Eclipse client, see Installing the client.
The launchpad program includes links to install Jazz Team Server and the Change and Configuration Management (CCM), Quality Management (QM), and Requirements Management (RM) applications. In addition, the Rational Team Concert launchpad program includes the Rational Team Concert clients for the Eclipse and Microsoft Visual Studio IDEs, Build System Toolkit, Rational ClearCase® and Rational ClearQuest® Synchronizers, and the Windows shell extentions. By default, the server includes a Derby database that is limited to 10 users. For production environments and for enabling more users, install other supported databases like IBM DB2®, Oracle, or SQL Server. You can obtain programs such as DB2, WebSphere Application Server, and Rational Reporting for Development Intelligence by clicking the Optional Programs link in the Plan and Prepare page of the launchpad program.
Note: The online Information Center (clmhelp.war) is installed with the Jazz Team Server. For any application deployed on a different server, you must configure the location of the clmhelp.war, as described in Configuring the location of the help in a distributed environment. In a WebSphere environment, the clmhelp.war must be explicitly deployed, as described in Deploying the Rational solution for Collaborative Lifecycle Management applications on WebSphere Application Server.
Procedure

Download either the Web Installer or the Installation Manager Repository package for your platform.
For IBM Rational Team Concert, go to Rational Team Concert™ All Downloads.
For IBM Rational Quality Manager, go to Rational Quality Manager All Downloads.
For IBM Rational Requirements Composer, go to Rational Requirements Composer All Downloads.
See Download tips for tips about improving download performance and reliability.
Extract the .zip file to a temporary directory. To avoid issues, do not use long paths and directories with spaces in the directory names.
For the Installation Manager Repository package, complete these steps. For the Web Installer installation, go to step 4.
Start IBM Installation Manager.
If you do not have IBM Installation Manager version 1.5.2 or later, you can obtain it at the IBM Support Portal or download the Web Installer, which includes Installation Manager 1.5.2.
In Installation Manager, click File > Preferences and then select Add Repository.
For the Repository location, browse to the directory where you downloaded the .zip file and open the repository.config file.
Click OK to finish the editing preferences, and then click Install to start the installation process.
Go to step 8.
For the Web Installer installation, open the directory that you extracted the .zip file to, and run the launchpad executable file. On Windows, run the launchpad.exe command. On UNIX systems, run the launchpad.sh command. This opens the launchpad program.
Note: If you want to install the product as a non-root user on UNIX systems or as a non-administrator on Windows, in the Select user mode for Installation Manager, select Non-Administrator.
For Linux operating system Important: You must have the GTK x32 libraries available in your Linux system to be able to open the Installation Manager link from the launchpad program. For more information, see this article on jazz.net.
For a small deployment with default topology and Derby database, in the Plan and Prepare page, skip to Express Install and then click Jazz Team Server with required Base Keys, including Trials, and CCM, QM and RM Applications. The Derby deployments are limited to 10 users.
For advanced deployments, click Custom Install and select one of the following:
To install Jazz Team Server and required base keys, click Jazz Team Server with Required Base Keys, including Trials.
To install individual applications, click , CCM, QM and/or RM Applications.
IBM Installation Manager starts.
Type your jazz.net user name and password, and click OK.
In the Install Packages window, select the packages to install and click Next.
If another version of the Jazz Team Server is installed, you are notified. Click Continue to install the package to a new package group.
Note: If you are installing this instance in order to upgrade from a previous version, choose one application at a time and in the later step select the appropriate context root. However, if you are upgrading only one application and want to install the other two applications as new instances on the same application sever (for example, in an evaluation topology), select all applications.
If your operating system is not supported, you are presented with a system check in the Prerequisite window. Click the supported server operating systems link to learn more about supported environments, then click Next.
Read and accept the license agreement by selecting the appropriate radio button, then click Next.
Optional: If this is your first time installing with IBM Installation Manager, you will be prompted, just this first time, to create a shared resource directory. This directory will be shared by all products that you subsequently install with IBM Installation Manager.
Create a new package group, and accept or modify the default installation directory. The default location on Windows is C:\Program Files\IBM\JazzTeamServer. On UNIX systems, the default location is /opt/IBM/JazzTeamServer.
Note: In a WebSphere Application Server environment, it is recommended that you change the installation path to one that contains no spaces, such as C:\IBM\JazzTeamServer.
In the Architecture Selection section, select 32-bit or 64-bit. Click Next.
Note: Although, the installation works on 32-bit systems, only the 64-bit systems are tested and supported.
To install additional languages, select one or more languages, and click Next.
In the Features window, review the items to be installed and then click Next.
In the Common Configuration page, to install the included Tomcat, select the checkbox next to Install Tomcat 7. Clear this checkbox if you already have a supported Tomcat Application Server installed and plan to use it, or plan to deploy the web applications (WAR files) into IBM WebSphere Application Server. By clearing the checkbox, Installation Manager asks you to specify a location to place the web applications for later deployment. The default directory is JazzInstallDir/server/webapps. Click Next.
In the Context Root Options window, select a context root option to align the context roots of installed applications with context root values that you used in your deployment of previous product versions.
Options might include:
Use default 3.x/4.x application context roots
Note: Use this option for new installations, in addition to upgrading from a version 3.x CLM application.
Use Rational Team Concert 2.x context root
Use Rational Quality Manager 2.x context root
Use Rational Requirements Composer 2.x context root
Select custom context root values (advanced)
Note: Selecting this option allows you to edit the defaults and customize the application context roots.
Based on your application choices and the context root options, these context root values are used:
Table 1. Application context root values
Application Default 3.x/4.x application context roots Rational Team Concert 2.x context roots Rational Quality Manager 2.x context roots Rational Requirements Composer 2.x context roots
Change and Configuration Management application ccm jazz ccm ccm
Jazz Team Server jts jts jts jts
Lifecycle Project Administration admin admin admin admin
Quality Management application qm qm jazz qm
Requirements Management application rm rm rm rdm
Note: The context root is part of the URL that you use to access each application and the Jazz Team Server. For example, if your installation is originated from Rational Team Concert v2, the context root for Change and Configuration Management will be /jazz, rather than /ccm.
Click Next.
In the summary window, review your selections and click Install to begin the installation process.
When the installation is complete, ensure that under "Which program do you want to start" Documentation to configure the server for new or upgrade installations is selected, then click Finish. This action opens a page in the information center that includes links for next steps in configuring the server, including sections that cover upgrading, setting up databases other than default Derby, setting up WebSphere Application Server, and running the setup wizard.
What to do next

Tomcat installations only:
In a Windows installation, verify that Start the Jazz Team Server and Stop the Jazz Team Server items are available on the Windows Start > All Programs > IBM Collaborative Lifecycle Management menu.
In a Linux installation, verify that Start the Jazz Team Server and Stop the Jazz Team Server items are available on the Applications menu of your Linux distribution.
3Set up the database Back to top
You need to create a separate database to use with Jazz Team Server.
You need to create a separate database to use with Change and Configuration Management.
You need to create a separate database to use with data warehouse.
To setup a SQL Server database, see Setting up a SQL Server database (The complete content of this topic has been loaded into this document and appears immediately below).
Installing > Installing the Rational solution for CLM > Setting up the database
Set up an SQL Server database to work with the Jazz™ Team Server, the Change and Configuration Management, and the Quality Management applications.
This procedure requires that the following prerequisites have been met for the SQL Server:
The service is started.
The Java Database Connectivity (JDBC) driver is installed.
Tip: To download the JDBC driver, go to Microsoft JDBC Driver 4.0 for SQL Server. The download includes both sqljdbc.jar and sqljdbc4.jar. You must use sqljdbc4.jar.
The TCP protocol is enabled for SQL Server.
The user who creates the database table must be a member in the sysadmin fixed server role, or an owner of the database (dbo).
For Windows operating system Ensure that your server security is in mixed mode. You can verify the mode by checking the server security. It should be set to SQL Server and Windows Authentication Mode.
Setting up a database

Set up the SQL Server database by using the sqlcmd command line tool, which is provided with the SQL Server installation.
To activate the sqlcmd tool for Microsoft SQL Server 2008 Express edition:
From the Start menu, locate Microsoft SQL Server 2008, and click Configuration Tools > SQL Server Configuration Manager.
In the SQL Server Configuration Manager window, in the left pane, click SQL Server Network Configuration > Protocols for SQLEXPRESS.
Double-click the protocol Named Pipes.
In the Name Pipes Properties dialog box, select Yes for the Enabled field.
Change the Pipe Name as follows: \\.\pipe\sql\query.
Click Apply; then, restart the SQL Server Services.
You can also use a visual tool, such as SQL Server Studio Management, which is also available for the Express® version as SQL Server Studio Management Express. See the SQL Server documentation or a SQL Server database administrator (DBA) for more information.
Important: If you install Jazz Team Server with the Change and Configuration Management or Quality Management applications either on the same computer or distributed platforms, a separate database and a database user who is associated with that database must be created.
Create a database for each instance of the Change and Configuration Management, Quality Management, Jazz Team Server, and data warehouse. Use the following example, substituting jts with your database name:
Note: The Requirements Management application uses the same database as Jazz Team Server.
CREATE DATABASE jts
GO
Create a user and password and change the ownership of the database by run these commands:
CREATE LOGIN jtsDBuser
WITH PASSWORD = 'jtsDBpswd';
USE jts;
exec sp_changedbowner 'jtsDBuser'
GO
Change the collation of the Jazz Team Server database. From the command line tool, type:
ALTER DATABASE jts COLLATE SQL_Latin1_General_CP437_CS_AS
GO
Change the row version system for the database. From the command line tool, run this command:
Note: Ensure that the connection to the database is open before running this command.
ALTER DATABASE jts SET READ_COMMITTED_SNAPSHOT ON
GO
Change the collation of the data warehouse database. From the command line, type:
ALTER DATABASE dw COLLATE SQL_Latin1_General_CP1_CS_AS
GO
Create an environment variable named SQLSERVER_JDBC_DRIVER_FILE and point to the sqljdbc4.jar JDBC driver. The location of the driver varies depending on your installation.
For Windows operating system
Click Start > Control Panel > System.
Click the Advanced tab, and then click Environment Variables.
In the System variables list, click New.
In the Variable name enter SQLSERVER_JDBC_DRIVER_FILE, and in the Variable value enter C:\Path_to_JDBC_dirver\sqljdbc4.jar.

For Unix operating systems
On Unix systems, add the following environment variable declaration:
SQLSERVER_JDBC_DRIVER_FILE =.;Path_to_JDBC_dirver/sqljdbc4.jar
Note: Rational solution for CLM 4.0, no longer supports JRE 5.0. The version of supported JREs are 6.0 and 7.0. The sqljdbc.jar class library requires JRE 5.0 and the sqljdbc4.jar class library requires JRE 6.0 or later. You must use sqljdbc4.jar.
If you are using WebSphere Application Server, you must also add a custom property that points to the sqljdbc4.jar JDBC driver. For more information, see Setting up a WebSphere Application Server.
To configure your databases connections and create database tables complete one of these steps:
If you are using Tomcat, start the server and continue with Running the setup wizard (Custom setup).
If you are deploying WebSphere Application Server, see Deploying and starting WebSphere Application Server, and then continue with Running the setup wizard (Custom setup).
If you prefer to manually modify the teamserver.properties file for database connection and run the repotools commands to create database tables, see Manually configuring an SQL Server database.
If you are upgrading from a previous version, continue to run the appropriate upgrade scripts which will migrate your existing database connections. For the data warehouse, you can modify the information to connect to the database while configuring the server after the upgrade.
Troubleshooting

If the repotools command does not work, check the appropriate log files, which are located in the JazzInstallDir/server directory.
Also, verify that these conditions are correct:
The SQL Server is configured to allow connections that use the TCP/IP protocol. If required, restart the SQL service.
The SQL Server computer host name, and the port is correctly reflected in the teamserver.properties files.
The login name, password, and database name are correctly reflected in the teamserver.properties files.
A firewall does not prevent you from accessing the SQL Server. Use a Telnet command to connect to the server using the host name and port from the teamserver.properties file.
The created user has the correct permissions in the Jazz Team Server database.
The JDBC driver environment variables are properly configured for your environment.
Note: The database code for Jazz Team Server was designed to be generic and standard in order to run on multiple database platforms; however, differences between the enterprise databases exist in syntax, optimization strategies, and locking semantics. The server has been tested on SQL Server using a combination of automated tests and simulations of normal workloads and stress testing. The simulation of normal workloads showed acceptable performance. In some instances, database deadlocks have been observed in automated concurrency tests; however, these have not been consistently reproduced on different server hardware.
The server is designed to handle a large number of simultaneous requests. In exceptional cases, deadlocks can occur in the repository database, as similar or equal objects are updated concurrently in transactions that are associated with the requests. These are rare, but typical events. The system is designed to be defensive against deadlocks, and data integrity is maintained; there is no loss of data. Occasionally, deadlocks are logged by tasks, such as build engine execution. Generally, the condition is detected, and the task is retried. A deadlock can result in a failed build. In very rare cases, a user action, such as working with work items or source code, is stopped to resolve a deadlock. In that case, the user action fails and an error message with details regarding the deadlock is displayed to the user. The user can then try the action again.
All deadlocks are logged on the server to provide information about what happened when the deadlock occurred. The log entry has text similar to the following entry: com.ibm.team.repository.common.RetryableDatabaseException: Serialization failure.
If your system encounters deadlocks, see the error log, which is available at https://servername:9443/jts/service/com.ibm.team.repository.common.internal.IFeedService?category=SystemLog.
If you encounter frequent deadlocks, contact your product support or check the forums on jazz.net for the latest information, updates, or mitigating techniques.
Manually configuring an SQL Server database
Running the setup wizard is the recommended method to configure the database connections and create the database tables. If you prefer to do this procedure manually, use this topic to edit the teamserver.properties file to setup an SQL Server database connection and run the -createTables command to create database tables.
Related information:
Server tuning guide on jazz.net
4Start the Apache Tomcat server Back to top
You are now ready to start the Apache Tomcat server.
Before you start the server, verify that the following tasks have been completed:
Apache Tomcat has been installed in the directory JazzInstallDir/server/tomcat.
The following web applications have been installed in the Apache Tomcat directory webapps:
- jts.war
- admin.war
- ccm.war
- clmhelp.war
To start the server, from the JazzInstallDir\server directory, run the following command:
server.startup.bat
Note: A separate Apache Tomcat console window opens. Do not close this window or the server will stop working.
To stop the server, from the JazzInstallDir\server directory, run the following command:
server.shutdown.bat
If you installed Jazz Team Server using IBM Installation Manager, you can also run the commands from the Jazz Team Server Windows start menu.
To configure your server with LDAP, see Managing users with LDAP (The complete content of this topic has been loaded into this document and appears immediately below).
Installing > Installing the Rational solution for CLM > Setting up user management > Managing users on Apache Tomcat
If you plan to use an LDAP registry with your Jazz™ Team Server, you must configure your Apache Tomcat to use an LDAP registry to authenticate users.
IBM i restriction: Apache Tomcat application server is not supported on the IBM® i operating system.
If you use LDAP for user management and you enable the option to not use case-sensitive user management, make sure that Jazz Team Server is also configured to allow user management that is not case sensitive. To configure the Jazz Team Server login property, on the Advanced Properties page of the Administrative web interface, modify the Use case insensitive user ID matching property.
LDAP configuration parameters
Use this reference topic to learn about each LDAP configuration parameters
Configuring an LDAP connection
Configure an LDAP connection and import users.
Manually configuring the Apache Tomcat web container to use LDAP
If you used the Jazz Team Server setup wizard to create the Tomcat configuration files, this procedure was automatically completed, and you do not need to configure the web container.
Related concepts:
Synchronizing LDAP with Jazz(tm) Team Server repository user information
Related tasks:
Running the setup wizard (Custom setup)
Importing users from an external registry service
Related information:
Apache Tomcat Realm Configuration: Configuring Apache Tomcat to use LDAP via JNDI lookups
User Management in Tomcat
5Run the setup wizard Back to top
After installing the applications, databases, and starting the servers, run the setup wizard to configure the servers. For more information, see Running the setup wizard (The complete content of this topic has been loaded into this document and appears immediately below).
Installing > Installing the Rational solution for CLM > Configuring the server
The setup wizard will run you through setting up your database, configuring email settings, configuring the user registry, and registering applications. The wizard will detect and allow you to setup the applications that you have just installed.
Before you begin

For new installations, if you do not want to use the default port numbers, you must change them before you use the setup wizard. For more information, see Changing the port numbers for the application server.
If you are using an enterprise database such as DB2®, Oracle, or Microsoft SQL Server, you must have created the databases for each application and for the Data Warehouse. For more information, see Setting up a DB2 database, Setting up an Oracle database, or Setting up an SQL Server database. Note that when you create the databases, you do not need to create the database tables by running the repotools command. On the Configure database page of this wizard, click Create tables to create the database tables.
Make sure that you have started the server by following the instructions in Deploying and starting the server.
About this task

Complete each step in this wizard to configure the Jazz Team Server and the applications you have just installed. If you want to make any changes after setup is complete, you can return to the wizard and start over.
Procedure

Note: If you are running the wizard to setup distributed applications, carry out the following steps in order:
Install the Jazz Team Server application and trial licenses on the first server. Start the first server but do not run the setup wizard on the server.
Install the Change and Configuration Management, Quality Management, or Requirements Management applications on the second server (or on a server for every application, as in the Enterprise topology examples). Start the servers, but do not run the setup wizard.
Run the setup wizard on the first server (with the Jazz Team Server application), starting from step 2 below. When you get to the Register Applications page of the setup wizard (see step 7, below), provide the discovery URL of the applications installed on the other servers.
On Tomcat, if you want the distributed applications (CCM and QM only. Other applications use delegated authentications.) to use LDAP, after you setup the user registry in step 8 below, copy the server.xml and web.xml files and the LDAP attributes in teamserver.properties files from the server with the Jazz Team Server to the servers with the other applications and then restart all servers.
Point your Web browser to the following address: https://[fully qualified hostname]:9443/jts/setup
Note: Default port number on IBM i systems is 29443.
The Jazz Team Server login page appears.
Type ADMIN (case-sensitive) in both the User ID and Password fields. Click Log In.
Do not use ADMIN (case-sensitive) as user ID and password if you enabled applications to use Lightweight Directory Access Protocol (LDAP) on WebSphere® Application Server. Instead, login as an LDAP registered user who has JazzAdmin privileges. Note that the LDAP user or group must be mapped to the repository group. For mapping security roles to a user or repository group, see Step 9 in this topic.
For WebSphere Application Server on z/OS® with RACF® security or WebSphere Application Server on IBM i with local OS authentication, use a user ID that has been granted JazzAdmin privileges on the system. Default user ID and password on IBM i are JTSADMIN and JTSADMPWD.
On the Welcome page, there are two options available for setting up the server: Express setup and Custom setup. For information about Express setup, see Running the setup wizard (Express setup). For production environments, select Custom setup and click Next.
On the Configure Public URI page, provide a Public URI Root that is of the form https://[fully qualified hostname]:9443/jts and select the checkbox to confirm that you have read and understood the recommendations on this page. Click Test Connection. After the test is successful, click Next.
Important:
A [fully qualified hostname] is the host name along with the DNS domain reference of the machine on which the Jazz Team Server is installed.
An example of a good [fully qualified hostname] is clmwb.example.com.
Examples of bad [fully qualified hostname] are localhost and an IP address.
On the Configure Database page, provide information to set up a connection to the database.
If you are using the Derby database, you should not have to change the default values, and you will not be prompted to create database tables.
If you change the default values or set values for an enterprise database like DB2, Oracle, or SQL Server, click Test Connection to make sure the connection is configured correctly.
If you did not previously use repotools to create the database tables, you might see a warning that the database exists but that it does not contain any tables. To create the tables, click Create tables. You might have to wait several minutes for the command to finish.
If you have tested the connection and you see no warnings or errors, click Next.
On the Enable E-mail Notification page, enable or disable e-mail notifications. If you choose to enable notifications, you will need to provide information about your e-mail server and test the connection to the e-mail server. Click Next after making your selections and testing the connection.
On the Register Applications page, the wizard detects the applications that were installed along with the Jazz Team Server. It might take a minute for each application to be discovered and added to the list of applications to register. The wizard will also detect the Lifecycle Project Administration application, which must be on the same server as the Jazz Team Server application. The wizard will not detect those applications installed on a different server. You must manually add them; see Step c below.
Optional: If you do not want to register an application, click the Close icon to the far right of the application name. Typically, you should register all applications; however, you might not want to register one or more applications in the following situations:
You downloaded and deployed all applications, but you do not intend to use all of them.
You will not have licenses that allow access to an application.
You are configuring this Jazz Team Server application as a stand-alone floating or token license server.
Verify the Application Type and Discovery URL of the installed applications. The wizard creates default pre-authorized functional User IDs for each application.
What is the Discovery URL?: The discovery URL is the service contribution resource (SCR) URL of an application. In general the SCR URL is formed by adding /scr to the Public URI for the application. For example, if the Public URI for the Change and Configuration Management application is https://[fully qualified hostname]:9443/ccm, the corresponding SCR URL must be https://[fully qualified hostname]:9443/ccm/scr. For a locally installed applications, this URL and a functional User ID will be filled in by the setup wizard.
Optional: To add an application installed on a different server, click Add Application and provide the application name and discovery URL. After you provide the application name and discovery URL, the Functional User ID will be generated and filled-in automatically. The functional user ID will be used to run tasks in the background. The functional user ID does not have to exist in the external user registry or as a user in the repository; if the user doesn't exist in the repository, it will be automatically created.
Click Register Applications.
Note: The wizard creates friend relationships, registers the applications, and generates a consumer key and secret for each application.
After registration is successful, click Next to configure the registered applications.
Note: Notice that the menu on the left now lists the registered application along with sub-steps.
On the Setup User Registry page, provide the following information.
Select the type of user registry you will use.
Note:
If you select an LDAP user registry, you must provide information to configure the connection between the Jazz Team Server and your LDAP server. You might need to request this information from your LDAP administrator.
For WebSphere Application Server on z/OS with RACF security or WebSphere Application Server on IBM i with local OS authentication, select non-LDAP external registry.
Provide the user ID, name, password, and e-mail Address of the user who will have administrative access to the Jazz Team Server.
Depending on the installed applications, under Rational Requirements Composer, Rational Team Concert™, and Rational Quality Manager select the Client Access Licenses (CALs) you want the administrative user to have. You can assign only one type of role-based CAL to the administrator. For example, you can assign the administrator only a Rational Team Concert - Developer CAL or a Rational Team Concert - Stakeholder CAL, but not both. The same rule applies to other applications.
If you have installed the trial licenses, you must accept the terms of a license before you can assign it to the administrative user. To activate a license, click Activate Trial; then, in the Client Access License Agreement window, click I accept the terms in the license agreement and click Finish.
Tip: See Client access license management overview for information on how licenses can provide different levels of access to the capabilities in the applications in the current release.
Click Next after making your selections.
On the Configure Data Warehouse page provide information to setup a connection to the data warehouse. The data warehouse is a database used for reporting and analytics. By default, the application is configured to use the Derby database that is included with the application. If you have a database prepared on an enterprise database server such as DB2 or Oracle, you must configure the Jazz Team Server to use that database.
Important: If you are planning to use Rational Reporting for Development Intelligence (RRDI), make sure you are using a database other than default Derby. RRDI does not support Derby.
Optional: To not configure the Data Warehouse at this time, click I do not wish to configure the data warehouse at this time. Only bypass the data warehouse in the following circumstances:
You used Rational Insight and all of the following are true:
You want to use your existing Rational Insight data warehouse database as the data warehouse for your CLM products;
You have not yet upgraded to Rational Insight version 1.1.Next, which is the earliest version that supports this version of CLM.
Important: The Rational solution for Collaborative Lifecycle Management (CLM) v4.0 does not support Rational Insight v1.1 and earlier. Rational solution for CLM v4.0 intends to support the upcoming version of Rational Insight (v1.1.Next), which is scheduled for general availability at a later date. If you are currently using Rational Insight as your development intelligence reporting solution, do not upgrade to Rational solution for CLM v4.0 until Rational Insight v1.1.Next is available. Please refer to the Rational solution for CLM system requirements for details.
After you have upgraded Rational Insight to version 1.1.Next, you can come back to the setup wizard and configure the Jazz Team Server and the other applications to use the existing Rational Insight database.
If you do not configure the data warehouse, your applications will be functional but you will not be storing any reporting data and most reports will not work.
In the Configure Data Warehouse Database Vendor and Connection Type section, select your Database Vendor and Connection type for that database vendor. The defaults are to use the included, pre-configured Derby database with a JDBC connection. You can either keep this default or choose a different database vendor and connection type.
If you are not using the Derby database, in the Configure Data Warehouse Database Connection Properties section, type the connection properties to connect to your database. The required values will vary depending on your database vendor and connection type.
For Oracle or Microsoft SQL Server, in the Database Table Space Folder field, type the path to an existing directory on the database server where the tablespace will be created.
If you used Rational Common Reporting or Rational Insight and you want to use the existing data warehouse database as the data warehouse for your CLM products, provide the information to connect to that existing database. You will be prompted to add tables to your Rational Common Reporting or Rational database.
Type the login information for a functional user that will run the data collection jobs. If you are using Tomcat and the built-in Tomcat User Database, that user will be created in the registry. If you are using LDAP or a different external registry, you must specify a user that exists in the external registry.
Note: The User ID that you enter for the functional user must be a different ID than the administrative user that you are currently using to configure the application. The functional user must be a member in the JazzAdmins group.
Click Test Connection to verify that the server can successfully communicate with the database using the connection information you provided.
If you did not previously use a repotools command to create the database tables, you might see a warning that the database exists but that it does not contain any tables. To create the tables, click Create tables. You might have to wait several minutes for the command to finish. If you are using the default Derby data warehouse, you will not see this warning.
Click Next.
For each application configure the database and the data warehouse similar to the steps you carried out above.
Note: Requirements Management uses the same database as Jazz Team Server. As a result, the databases steps are not available in the menu for Requirements Management.
If you did not configure the data warehouse for the Jazz Team Server in step 9, on the Configure Data Warehouse page for the application, select I do not wish to configure the data warehouse at this time.
For the user that will run the data collection jobs, you must enter a different user ID than the ID you are using the configure the application.
On the Finalize Setup page for each application, click Finalize Application Setup. In this step, the consumer key and secret for an application are stored and the users on the Jazz Team Server are synchronized. For the Requirements Management application, if you are upgrading from Rational Requirements Composer version 2 or you are adding a Requirements Management application to an existing Jazz Team Server environment, also click Rebuild Index. If you are configuring an entirely new environment, you do not have to rebuild the index. After you see a message that the process is complete, click Next.
Note: If the applications are on different servers and you see an error message that says "500 error - unexpected error occurred failure during finalize application step," verify that all servers have the correct times by using the NTP time server.
On the Finalize Setup page for the Lifecycle Project Administration application, if the browser blocked the popup to finalize LPA, click Authorize to allow the registration. You might have to log on to any registered applications; log in as an administrative user (the same user ID you are using to run through the setup wizard). Then, click Finalize Application Setup. When the process is complete, click Next.
On the Summary page, click Finish to access the Jazz Team Server Administration page where you can perform administration tasks such as, managing the server, users, and licenses. For more information, see Administering Rational solution for Collaborative Lifecycle Management servers.
6You have installed the server! Back to top
For information about post-installation tasks, see Completing the installation (The complete content of this topic has been loaded into this document and appears immediately below).
Installing > Installing the Rational solution for CLM > Configuring the server
After the server is installed, you must consider some configuration options before continuing.
Procedure

Some files contain passwords. Those files should be protected so that they are readable only by users authorized to know the password for the accounts.
teamserver.properties - The Jazz™ Team Server, CCM, and QM require that the database password is stored in JazzInstallDir/server/conf/<application>/teamserver.properties. When properties files are saved, the application always makes a backup copy of the previous version in the same directory. If you want to remove all files that contain the clear-text password, remove the backup properties files after configuring the server for the first time.
The ClearCase® Synchronizer sync engine requires that user passwords be stored in an properties file.
cqconnector.properties - The ClearQuest® Synchronizer requires that both ClearQuest user IDs and passwords be stored in a properties file.
When connecting to Jazz Team Server you might see security certificate warnings. To disable the warning, see Configuring security certificates.
Optionally, make the login case-insensitive for interoperability between UNIX systems and Windows. On UNIX systems, the native file system is case-sensitive while on Windows computers the native file system is case-insensitive. The default setting for user ID in Jazz Team Server is case-sensitive. To change the default setting to case-insensitive, follow these steps:
Login to Jazz Team Server administrative web interface as an administrator.
Under Configurations, click Advanced Properties.
In the Advanced Properties page, search for Use case insensitive user ID matching.
Click Edit and under Current® Value, select true.
For IBM i operating system Note: For IBM® i, using the case-insensitive option allows user IDs to be lowercase instead of uppercase only.
The creation of the warehouse on Oracle requires more permissions as compared to other databases. When you specify the database user in the connection spec for data warehouse, ensure that the database user has DBA permissions.
GRANT DBA TO <data warehouse user>
If this type of permission is a concern, after the data warehouse is created, you may change the user in the connection spec, using the Reports Admin Web UI. You need to change this value in the JTS, CCM, and QM applications. To create the new user with less permissions for running data collection (ETL) jobs, open a SQL *Plus window and run the following commands:
CREATE USER <etl db user> PROFILE DEFAULT
IDENTIFIED BY <password> DEFAULT TABLESPACE USERS
ACCOUNT UNLOCK;

ALTER USER <etl db user> TEMPORARY TABLESPACE RIS_TEMP;
ALTER USER <etl db user> QUOTA UNLIMITED ON VNF_32K;
ALTER USER <etl db user> QUOTA UNLIMITED ON VNF_IDX;
ALTER USER <etl db user> QUOTA UNLIMITED ON USERS;
ALTER USER <etl db user> QUOTA UNLIMITED ON VSTR_32K;
ALTER USER <etl db user> QUOTA UNLIMITED ON VSTR_IDX;

GRANT CREATE SESSION TO <etl db user>;
GRANT CONNECT TO <etl db user>;
GRANT DROP ANY TABLE TO <etl db user>;
GRANT EXECUTE ANY PROCEDURE TO <etl db user>;
GRANT ANALYZE ANY TO <etl db user>;

BEGIN
FOR TABNAME IN (SELECT OWNER,TABLE_NAME FROM ALL_TABLES WHERE OWNER IN ('RIODS','RIDW','CONFIG','RIASSET','RISCHK','RICALM'))
LOOP
EXECUTE IMMEDIATE 'GRANT SELECT,UPDATE,DELETE,INSERT ON ' || TABNAME.OWNER || '."' || TABNAME.TABLE_NAME || '" TO <etl db user>';
END LOOP;
END;
/

BEGIN
FOR VNAME IN (SELECT OWNER,VIEW_NAME FROM ALL_VIEWS WHERE OWNER IN ('RIDW','RICALM'))
LOOP
EXECUTE IMMEDIATE 'GRANT SELECT ON ' || VNAME.OWNER || '."' || VNAME.VIEW_NAME || '" TO <etl db user>';
END LOOP;
END;
/
For more information about Oracle data warehouse setup, see this wiki.
Related concepts:
Configuring security certificates
Related tasks:
Installing the client using the IBM Installation Manager
Related information:
Deploying ClearCase Synchronizer
Deploying the ClearQuest(r) Connector
Building with Jazz Team Build
Getting started: Server and repository administrator
7Install the Rational Team Concert client for Eclipse IDE Back to top
You can use the launchpad program to install the client for Eclipse IDE. For more information, see Installing the client using the IBM Installation Manager (The complete content of this topic has been loaded into this document and appears immediately below).
Installing > Installing optional tools, clients, and samples > Installing Rational Team Concert Client
The client is distributed as a downloadable file via the IBM® Installation Manager.
About this task

There are two ways to download and install IBM Rational Team Concert v4.0 client from IBM Installation Manager. You can perform a web-based installation that includes a smaller download and connects to Internet during the installation to get the repository files, or if you need to install the server in an environment without internet access, you can download and extract all repository files to a local machine to perform a local installation. Instructions for both methods are provided below.
You can also install Rational Team Concert client from a DVD. The DVDs are available from IBM Passport Advantage when you purchase the product.
Procedure

Download either the Web Installer for your platform or the Installation Manager Repositories package.
Extract the .zip file to a temporary directory.
For a local installation, perform the following steps. For a web-based installation, go to Step 4.
Start IBM Installation Manager.
If you do not have IBM Installation Manager version 1.5.2 or later, you can obtain it at the IBM Support Portal or download the Web Install, which includes Installation Manager 1.5.2.
In Installation Manager, click File > Preferences and then select Add Repository.
For the Repository location, specify the directory where you extracted the .zip file and open the repository.config file.
Click OK to finish editing preferences and then click Install to start the installation process.
Go to step 7.
For the Web Installer installation, open the directory that you extracted the .zip file to, and run the launchpad executable file. On Windows, run the launchpad.exe and on AIX or Linux systems, run the launchpad.sh. This opens the launchpad program.
Note: If you want to install the product as a non-root user on UNIX systems or as a non-administrator on Windows, in the Select user mode for Installation Manager, select Non-Administrator.
In the left pane, click Install Optional Tools and in the right window, click Rational Team Concert - Client for Eclipse IDE. This opens IBM Installation Manager.
Type your jazz.net user name and password, and click OK.
In the Install Packages window, ensure Rational Team Concert - Client for Eclipse IDE and Version 4.0 check boxes are selected, click Next.
Read and accept the license agreement by selecting the appropriate radio button. Click Next.
Create a new package group and accept or modify the default installation directory. The default location on Windows is C:\Program Files\IBM\TeamConcert and on UNIX systems it is /opt/IBM/TeamConcert.
Select 32-bit or 64-bit architecture, select Next.
Optional: If you want to install the client into an existing Eclipse workbench, select the Extend an existing Eclipse check box and provide the location of the Eclipse IDE. When you extend Eclipse, the package functions are available in your Eclipse IDE, but the package files are still installed in their own directory.
To install additional languages, select one or more languages and click Next.
In the Features screen, if you want to install the Sametime Integration Update Site, select its check box and click Next. For instructions about using the update site to enable the integration, see Connecting to local Sametime applications.
In the Help System page, select one of the following options to access help:
Access help from the Web (default): Select this option to dynamically retrieve the latest product documentation from the web.
Download the help and access the content locally: Only limited help content is included during installation. When you first start the product, the complete online help is downloaded and installed provided that you have an Internet connection. On subsequent startups, available updates to the help are downloaded and installed.
Access help from a server on your intranet: Select this option to connect to a help system that is set up on your intranet system. You will need the host, port number, and the path to the help system.
In the summary screen, review your selections and click Install to begin the installation process.
Starting the client and connecting to the server

Procedure
Start the client by clicking the Rational Team Concert™ shortcut created by the installation.
Connect to the server. The easiest way to connect to a server is using the Team Invitation. If you do not have an invitation, you can connect manually.
Click File > Accept team invitation. Paste the invitation text
Paste the invitation text from the E-mail message into the field and click Finish.
If you do not have an invitation, you need the URL from your server administrator. Click on the connecting to an existing project area hyperlink in the Accept Team Invitation window.
Follow the instructions in the wizard to set up your connection.
Latest entries in the jazz.net library on installing Rational Team Concert
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!