It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,878
×4,715

question asked: Jan 04 '13, 2:09 p.m.
question was seen: 3,817 times
last updated: Jan 05 '13, 10:44 a.m.

Related questions

How can i auto-close the parent workitem when all my child workitems are closed ?

0
Prasad Annamdasu (154●5●36●43) | asked Jan 04 '13, 2:09 p.m.
Hi, 

How can i auto-close the parent workitem when all my child workitems are closed 

One answer

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Jan 04 '13, 2:28 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
 You would have to create a Java Server extension, a so called Participant. See http://rsjazz.wordpress.com/2012/11/27/resolve-parent-if-all-children-are-resolved-participant/ and http://rsjazz.wordpress.com/2012/07/31/rtc-update-parent-duration-estimation-and-effort-participant/ as well as other posts on that blog for example code and links to enablement material.
Comments
Prasad Annamdasu commented Jan 05 '13, 6:02 a.m.

Hi Ralph, 


Thanks for your quick response. 
Using the code shared in the above links , I am trying to create a Participant. 

I am referring to this link https://jazz.net/library/article/495 and couldn't finish the creation. 

After exporting the projects to the Eclipse client, i created a new Updatesite project and ran the build using buildall option.
It created artificats.jar & Contents.jar, later i copied these files to a folder in my server directory created as per the instructions given in the extending RTC4.0 document and created the .ini file as per the instructions. Couldn see that working. 

I tried coying the files & .ini file into a normal RTC server and after restart it gives me error when i try to login to RTC. 

Ralph Schoon commented Jan 05 '13, 8:12 a.m. | edited Jan 05 '13, 10:44 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Article 1000 is for 4.x the one you refer to is for 3.x. My suggestion is to run the Extensions workshop first, to get experience. Always test your extensions first in debug mode, to be sure they run, before deploying them. Always run against a test system, also first deployments.


We have run that Extensions workshop in different versions with numerous people and it works if you succeed to follow it closely. If you try to skip steps and have no experience, creating an extension typically fails. It is almost impossible to debug this remotely, especially without any log information. For example, I have never managed to get my servers in a state where login would not work anymore, deploying an extension.

Ralph Schoon commented Jan 05 '13, 10:41 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

I reviewed the article you referenced, 495 is for 2.x and assumes you have some experience. You should check https://jazz.net/library/article/1000 or the earlier versions, whichever matches the version you use. Get that working first before trying your own extension. Definitely check the other references I provided. 

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.