It's all about the answers!

Ask a question

Issue in starting Build Engine and Build Agent on z/OS


Shajeel Khan (2146) | asked Sep 06 '13, 11:53 a.m.
edited Sep 09 '13, 9:08 a.m. by Kevin Doyle (60425)
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


permanent link
Steve Dearth (2212) | answered Sep 09 '13, 10:51 a.m.
JAZZ DEVELOPER
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
Shajeel Khan commented Sep 13 '13, 10:31 a.m. | edited Sep 17 '13, 3:46 p.m.

Hi steve,

I checked bfaagent.conf but unable to find any port defined. Can you please tell where that port defined?

Also in BLZBENG job my repository is -https://myIP:9538/ccm


Thanks,
Shajeel Ahmed Khan


1
Steve Dearth commented Sep 13 '13, 10:53 a.m. | edited Sep 14 '13, 11:04 a.m.
JAZZ DEVELOPER

 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)? 



Shajeel Khan commented Sep 16 '13, 12:30 p.m. | edited Sep 17 '13, 3:46 p.m.

Hello Steve,

For Build Agent i tried uncommenting the port 5555 and it was successful, it started the shell script script without giving any error. But i was unable to see anything on Status of jobs or anywhere. where should i see started shell script? Now its giving me this error when i called BLZBFA as a procedure or i started again from the path:

EDC5111I PERMISSION DENIED

Secondly for BLZBENG pls fin our JCL below and its output as well:

//PROCLIB JCLLIB ORDER=JVB600.PROCLIB                      
//JBUILDEG EXEC PROC=JVMPRC66,VERSION='66',LOGLVL='+T',    
// JAVACLS='org.eclipse.equinox.launcher.Main'             
//MAINARGS DD                                             
-repository https://MyHostIP:9443/ccm                  
-engineID build                                            
-userId ibmuser                                            
-passwordFile /rtc4/rtcwork/jazz401/rtc4pass/pwfile        
-sleepTime 3                                               
//STDENV DD
                                              

                                                          


. /etc/profile                                             

                                                          


any environment variables for the Java JVM.              


Variables must be exported to be seen by the launcher.   


export JAVA_HOME=/u/Java6_64/J6.0_64                       

export JZOS_HOME=@javaPathPrefix@/java/J6.0_64/lib/ext   


BLD_TOOLKIT=/rtc4/usr/lpp/jazz/v4.0.1                      
BLD_TOOLKIT="$BLD_TOOLKIT"/buildsystem/buildtoolkit        
ANT_HOME=/rtc4/usr/lpp/jazz/v4.0.1                         
ANT_HOME=/rtc4/usr/lpp/jazz/v4.0.1                                 
ANT_HOME="$ANT_HOME"/buildsystem/buildengine/eclipse               
ANT_HOME="$ANT_HOME"/plugins/org.apache.ant_1.7.1.v20100518-1145   
export ANT_HOME="$ANT_HOME"                                        

                                                                  


export PATH="${JAVA_HOME}"/bin/classic:"${JAVA_HOME}"/bin:$PATH    

                                                                  


LIBPATH=/lib:/usr/lib:"${BLD_TOOLKIT}"                             
LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/classic:"${JAVA_HOME}"/bin   
export LIBPATH="$LIBPATH":                                         

                                                                  


echo "*** >>>>>"                                   
echo "PATH is :"                                                   
echo "${PATH}"                                                     
echo "***
<<<<<"                                   

                                                                  


CLASSPATH="/rtc4/usr/lpp/jazz/v4.0.1/buildsystem"                  
CLASSPATH="$CLASSPATH/buildengine/eclipse/plugins"                 
CLASSPATH="$CLASSPATH/org.eclipse.equinox.launcher"                
CLASSPATH="$CLASSPATH"_"1.1.1.R36x_v20101122_1400.jar"             
CLASSPATH="$CLASSPATH":"${BLD_TOOLKIT}/ibmjzos.jar"                
export CLASSPATH="$CLASSPATH":                                     
echo "classpath is : "                                             
echo $CLASSPATH                                                    

                                                                  


                                                       


                                                       


echo $CATALINA_OPTS                                     

                                                       


Configure JVM options                                 


                                                       


IJO="$IJO -Djava.io.tmpdir=/rtc4/rtcwork/jazz401/ccm"   
export IBM_JAVA_OPTIONS="$IJO "                         
export JAVA_DUMP_HEAP=false                             
export JAVA_PROPAGATE=NO                                
export IBM_JAVA_ZOS_TDUMP=NO              

Output for this JCL is:
ÝJazz build engine¨ CRRTC3524W: Communication with the repository failed due to this error: CRJAZ1371E The following URL cannot be reached: https://MyHostIP:9443/ccm/versionCompatibility?clientVersion=4.0.1. The server cannot be reached. The network could not connect to the server. Error details: EDC8128I Connection refused..            

For your info i have hide My Host IP address as its an open forum. But This the IP from which we used to connect our PCOMM session.

So, what would be an issue? It would be your great help.


Thanks,
Shajeel Ahmed Khan

9 other answers



permanent link
Steve Dearth (2212) | answered Sep 16 '13, 1:29 p.m.
JAZZ DEVELOPER
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:

16806852 ?         0:00 /var/testsrv2/usr/lpp/jazz/v4.0.5/buildagent/bfagent

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
Shajeel Khan commented Sep 17 '13, 9:05 a.m. | edited Sep 17 '13, 3:46 p.m.

Hello Steve,

Just a quick question for RTC or Jazz Server. Do we need to start the server from any job? Or BLZBENG and BFA will start it. We have installed RTC server on same machine. I can ping MyIP from PCOMM.

I believe we have finished installation but unable to start the server


Thanks,


Steve Dearth commented Sep 17 '13, 10:11 a.m. | edited Sep 17 '13, 3:47 p.m.
JAZZ DEVELOPER

 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.


Steve Dearth commented Sep 17 '13, 10:12 a.m. | edited Sep 17 '13, 3:47 p.m.
JAZZ DEVELOPER

 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.


Shajeel Khan commented Sep 17 '13, 10:52 a.m. | edited Sep 17 '13, 3:48 p.m.

Hi Steve,

We have deployed *.war files on Websphere Application Server. After Restarting WAS i can see the applications are started. Now what we have to do? am connecting through this address but unable to see any screen.

https://MyIP:9443/jazz/admin

Thanks,



permanent link
Shajeel Khan (2146) | answered Sep 17 '13, 10:55 a.m.
For Jazz Team does any job require to be in execution or started? Because i want to see admin console for JTS.


-Shajeel

permanent link
Steve Dearth (2212) | answered Sep 17 '13, 11:12 a.m.
JAZZ DEVELOPER
 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

permanent link
Shajeel Khan (2146) | answered Sep 17 '13, 11:55 a.m.
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

permanent link
Shajeel Khan (2146) | answered Sep 17 '13, 12:09 p.m.
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

permanent link
Steve Dearth (2212) | answered Sep 17 '13, 12:13 p.m.
JAZZ DEVELOPER
 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.

permanent link
Shajeel Khan (2146) | answered Sep 17 '13, 12:20 p.m.
yes it's /jts i just checked it again.

Secondly in Websphere WC_defaulthost_secure was 9538 which i changed to 9443 and also gave host as 192.85.33.82.

My Server listening on both of these:

9443  TCP  AVSR00A

9538  TCP  AVSR00A


Thanks,
Shajeel

Comments
Steve Dearth commented Sep 17 '13, 12:26 p.m. | edited Sep 17 '13, 3:49 p.m.
JAZZ DEVELOPER

 If you've changed the value of WC_defaulthost_secure, you'll also need to make sure that the virtual host entries have been changed to match your new settings. 


If you intend to use 9443, from the WebSphere admin console, select Environment->Virtual Hosts and verify that the entries match your current port values. You may have to restart WAS for the changes to take effect. 


permanent link
Shajeel Khan (2146) | answered Sep 17 '13, 1:10 p.m.
Yes i already added 9443 there. Still same error what could be the cause?


Thanks,
Shajeel

permanent link
Steve Dearth (2212) | answered Sep 17 '13, 4:23 p.m.
JAZZ DEVELOPER
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


Register or to post 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.