Issue in starting Build Engine and Build Agent on z/OS
Shajeel Khan (21●4●6)
| asked Sep 06 '13, 11:53 a.m.
edited Sep 09 '13, 9:08 a.m. by Kevin Doyle (604●2●5)
Hello everyone,
We have installed RTC 4.0.1 on zOS. When we are running Build Engine job (BLZBENG) we are getting this error: CRRTC3524W: Communication with the repository failed due to this error: https://Myserver(example):9443/ccm/versionCompatibility?clientVersion=4.0.1.. Even its showing the same error for port 9538 whcih is already defined in Websphere Application Server. Also when we are running shell script startbfa.sh we are getting this error. Ý50397792¨ bfdaemon: bf_listener_new: EDC5111I Permission denied. Then we tried to submit BLZBFA job which showing us the above same error too. Please help us in this issue. Thanks, Shajeel |
Accepted answer
The error message you are getting when you run startbfa.sh and BLZBFA indicates that the bfagent port, which is specified in the bfagent.conf file, is reserved for another job or user. Please check with your system administrator to verify that the bfagent port is available for use by the agent.
The error message you get when running BLZBENG is caused by the engine not being able to communicate with the server. Have you completed the customization described in the comment header of BLZBENG? Is the URL specified on the "-repository" parameter in the job correct?
Shajeel Khan selected this answer as the correct answer
Comments Hi steve,
1
In bfagent.conf, you should see a line that looks like this:
#port 5555
By default, the agent will run on port 5555. To change the port, you need to remove the #, which is a comment character, and then provide a different port number.
The communication problem with the build engine could be caused by a number of things. Could you please provide the BLZBENG JCL you are using, and the exact output of the job when the connection fails (either in the comments or by opening a work item)?
Hello Steve,
any environment variables for the Java JVM.Variables must be exported to be seen by the launcher.
export JZOS_HOME=@javaPathPrefix@/java/J6.0_64/lib/ext
Configure JVM options
|
9 other answers
When the build agent is started from the command line with the startbfa.sh script, you can use the standard UNIX command ps to see the running process:
ps -A | grep bfagent
This should result in output similar to the following:
To stop the process, you can then issue "kill <pid>". In this case, you would issue "kill 16806852".
The EDC5111I error message when starting the agent suggests that the user who is trying to start the agent doesn't have the correct permissions. This could be caused by multiple issues:
1. Is the port you're running on (5555) available for use by this process? The sysadmin may have locked it down.
2. Does the user who is attempting to run the startbfa.sh script have permissions on the script and the directory structure containing it? Does this user have permission to access the bfagent binary at <installDirectory>/usr/lpp/jazz/v4.0.1/bfagent?
3. If you are attempting to run BLZBFA as a started task, has the RACF setup described in BLZRACFT been completed?
The build engine is having trouble contacting the server. The JCL you've posted appears to be correct, so I would start looking at network issues.
1. Is the RTC server running on the same machine as the build engine? If not, can you ping the server host successfully?
2. Is there a firewall blocking you from contacting the server?
Thanks,
Steve
Comments Hello Steve,
Server startup depends on how you've deployed the server.
If you intend to run CLM on WebSphere Application Server, you will need to deploy the web apps and configure the application server as described in Configuring the Rational solution for CLM and WebSphere Application Server for z/OS . Once this configuration is complete, you can either restart the application server or start the deployed WAR files to start the CLM server.
If you are running on Tomcat, you will need to customize and submit one of two sample jobs in <HLQ>.SBLZSAMP. BLZSRVD starts the server with DB/2z support, while BLZSRVC can be used for servers backed by Derby databases.
Server startup depends on how you've deployed the server.
If you intend to run CLM on WebSphere Application Server, you will need to deploy the web apps and configure the application server as described in Configuring the Rational solution for CLM and WebSphere Application Server for z/OS . Once this configuration is complete, you can either restart the application server or start the deployed WAR files to start the CLM server.
If you are running on Tomcat, you will need to customize and submit one of two sample jobs in <HLQ>.SBLZSAMP. BLZSRVD starts the server with DB/2z support, while BLZSRVC can be used for servers backed by Derby databases.
Hi Steve,
|
For Jazz Team does any job require to be in execution or started? Because i want to see admin console for JTS.
-Shajeel |
You need to make sure that in addition to deploying the war files, you've performed the configuration steps described in the link above. There are a number of custom JVM properties that need to be set before you can run the CLM applications.
After you've completed the deployment to WebSphere Application Server, you will need to run the CLM setup wizard as described in Running the setup by using Custom setup in the setup wizard. If you deployed your web applications using the default context roots, you need to access https://MyIP:9443/jts/setup through your web browser.
Did you change the context root for one of the applications? The CCM application should default to /ccm, and the JTS application is at /jts. None of the current applications default to a context root of /jazz.
Thanks,
Steve
|
Hello,
Already done with all steps, when i am connecting through this URL: https://192.88.56.36:9443/jts/setup we are getting this error. SRVE0255E: A WebGroup/Virtual Host to handle /jts/setup has not been defined. SRVE0255E: A WebGroup/Virtual Host to handle 192.88.56.36:9443 has not been defined. IBM WebSphere Application Server |
Hello,
I gave https://192.85.33.82:9443/jts/setup but am getting this error now: Error 404: ProxyServlet: /jts/setup What should we do? Thanks, Shajeel |
Did you use /jts as the context root when you deployed jts.war?
Also, is WAS actually listening on port 9443? Your first question hints that your server may be listening on 9538. Please double check the value of WC_defaulthost_secure in your configured server.
|
Yes i already added 9443 there. Still same error what could be the cause?
Thanks, Shajeel |
Are there any useful error messages in the JTS or CCM logs? You will find these at <install_root>/u/jazz401/logs, in the files jts.log and ccm.log. Note that these files are UTF-8 encoded.
If not, review the steps outlined in the topic Running Jazz Team Server and the CLM applications on z/OS systems and verify that all of the configuration is correct.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.