File agent cannot log in to the Jazz Team Server for
System z
The following error message: CRHTC0201E
Unable to log-in repository "https://localhost:9443/jazz/" indicates
that the file agent running on the build machine could not log in
to the Jazz Team Server for System z that is running on the same machine
as the client. You can make the Jazz Team Server for System z accessible
from an Antz build by changing settings in the advanced server properties.
Complete
these steps to make the Jazz Team Server for System z accessible from
an Antz build when the server is running on the same machine as the
client:
- In a supported Web browser, on the Jazz Team Server for System
z workstation, navigate to the administrative page: https://localhost:9443/jazz/admin
- From the left navigation, click Advanced Properties.
- Scroll to com.ibm.team.repository.servlet.internal.ServletConfigurationService.
- For the Host Name property, enter a host
name or IP address for the build machine to use to access Jazz Team
Server for System z.
- Restart the Jazz Team Server for System z.
Incorrect Data Set Definitions and Language Definitions
in a build
When two or more project areas are defined in
one Jazz repository, the Antz build attempts to find Data Set Definitions
and Language Definitions in the project area where the Rational Build
Agent is defined. If an Antz build is defined in a different project
area, the Antz build pulls the Data Set Definitions and Language Definitions
from an incorrect project area.
Complete these steps to make
the Antz build locate the correct definitions:
- Delete the existing RationalBuildAgent build engine in the Team
Artifacts view.
- Create a new RationalBuildAgent build engine in the project area,
where the build definition that you want to run is defined.
- In the Build Engine editor, check the build definition to ensure
that it is supported by the newly created RationalBuildAgent build
engine.
How to enable tracing in the file transfer step on
an Antz build
If you have problems with the File Agent step
in your Antz build, you can enable tracing with the following steps:
- Create a log4j.properties on your computer.
For example:
log4j.rootLogger=DEBUG, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%-4r %-5p [%t] %c %3x - %m%n
Note: If
log4j.rootLogger=DEBUG generates
too many messages, change the content of the
log4j.properties file
to:
log4j.rootLogger=INFO, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%-4r %-5p [%t] %c %3x - %m%n
log4j.logger.com.ibm.teamz.fileagent=DEBUG
(To limit the
number of messages, comment out the last line.)
- Upload the log4j.properties file that was
created in the previous step to the z/OS USS directory.
- Edit startbfa.sh and specify the location of this log4j.properties
file. This is done by setting the system property log4j.configuration.
In the following example the configuration file is fully specified
by the URL: file:/u/user1/log4j.properties.
FA_JAVA_OPTIONS="-Djava.ext.dirs=${JAVA_HOME}/lib/ext"
FA_JAVA_OPTIONS="${FA_JAVA_OPTIONS}:${BLD_TOOLKIT}"
FA_JAVA_OPTIONS="${FA_JAVA_OPTIONS} -Dlog4j.configuration=file:/u/user1/log4j.properties"
- Restart the Rational Build Agent using the modified startbfa.sh and
request your Antz build. You will see additional tracing in the build
log file.
Note: With tracing enabled, you will see error lines from
com.ibm.team.repository.common.util.ExtensionRegistryReader on
the component elements with ID attributes that are not unique. An
example of such an error is shown below. You can ignore those messages.
9467 ERROR [main] com.ibm.team.repository.common.util.ExtensionRegistryReader
- The com.ibm.team.repository.common bundle's plugin.xml file contains a <component>element
with the id attribute value com.ibm.team.repository that is not unique.