It's all about the answers!

Ask a question

Deploying new Process Template in RTC


sweety ferdous (333) | asked Feb 08 '12, 3:55 a.m.
Hi,

Please tell us the steps of deploying a new version of process template in a project area where already an existing version of the process template is deployed.

Right now we are copying/pasting the content of the new process template in the Process Configuration Source tab in RTC. THX.

9 answers



permanent link
Martha (Ruby) Andrews (3.0k44051) | answered Feb 08 '12, 9:09 p.m.
JAZZ DEVELOPER
In your case, we recommend exporting the process from the test server as a process template, then creating a new master project area on the production server and pointing the consumers to the new area.

Here are step by step instructions:
These instructions allow changes in a process provider project area to be moved across repositories.
Assume there are two repositories : repository1 and repository2 and each repository has a project area that provides process and project areas that consume that process.

1. Make changes to the process provider project area in repository1
2.Show the context menu for the project area in the Eclipse client and select "Extract Process Template...", enter a process ID, click Finish.
3.File > Export > Team Process > Process Template to export the template to a .zip file
4. File > Import > Team Process > Process Template to import the template into repository2
5. In repository2, create a new project area that will provide process. Use the template imported in step 4.
6. Edit the project areas that consume process to point to the new project area.
7. (optional) When all project areas have stopped consuming process from the old project area in repository2, archive the old project area.

Regards,
Martha
JazzDeveloper, Process Team

Our situation is that we have ~150 projects all of which point at a master project for their configuration. We have run into snags managing updates to the master process. We do our development and testing on a test server. The plan is to move changes from test to production. Copying the process source is problematic because it leaves behind attachments, we're not sure what else might be lost if anything.

It would be useful if we could export the full process template then import it into the existing master process. I can't figure out how to accomplish this.

We have also found that after "pushing" a process template we need to take an outage to cycle the CCM to clear the cache. Otherwise projects and Eclipse sometimes have inconsistent views of process model. We consider this a serious problem, we should not need to cycle the system to deploy process changes.

What are your thoughts to manage this in an Enterprise settings?

Mark

I'd recommend updating the process configuration of a project area by
having the project area "share" the process from another project area,
i.e. a "process master" project area.

Note that you also have to null out the process guidance section of your
project area (or else that will override the shared process guidance).
To see what it should look like when you are done, just look at the
Process Configuration Source of the built-in "Unconfigured Process"
template. Just paste that into the Process Configuration Source of your
project area.

Cheers,
Geoff

On 2/8/2012 4:08 AM, sweetyferdous wrote:
Hi,

Please tell us the steps of deploying a new version of process
template in a project area where already an existing version of the
process template is deployed.

Right now we are copying/pasting the content of the new process
template in the Process Configuration Source tab in RTC. THX.

permanent link
Geoffrey Clemm (30.1k23035) | answered Feb 08 '12, 1:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I'd recommend updating the process configuration of a project area by
having the project area "share" the process from another project area,
i.e. a "process master" project area.

Note that you also have to null out the process guidance section of your
project area (or else that will override the shared process guidance).
To see what it should look like when you are done, just look at the
Process Configuration Source of the built-in "Unconfigured Process"
template. Just paste that into the Process Configuration Source of your
project area.

Cheers,
Geoff

On 2/8/2012 4:08 AM, sweetyferdous wrote:
Hi,

Please tell us the steps of deploying a new version of process
template in a project area where already an existing version of the
process template is deployed.

Right now we are copying/pasting the content of the new process
template in the Process Configuration Source tab in RTC. THX.

Comments
marco covi commented Sep 19 '12, 2:48 p.m.

Hi Geoffrey,

Kind of new to process templates. What do you mean by "process guidance" of a project area? I am not quite sure. My team is trying to see:

a) how we can change process templates if we are no longer using the traditional approach and want to move to agile/scrum for example

b) what happens when we change a process template. Especially how would work items be impacted?

for example: we use simple work item categories out of the box (defects/enhancements) but we did put in some preconditions - i .e. only allow a change set to be delivered if the work item has been approved or resolved first.

and lets say we also change the permissions of different roles - i.e. developers can create their own project area as an example

Are those preconditions/customizations able to be carried over for example if we have to change the process template in one project area to another type of process template?

Thanks


permanent link
Mark Richmond (5144) | answered Feb 08 '12, 5:20 p.m.
Our situation is that we have ~150 projects all of which point at a master project for their configuration. We have run into snags managing updates to the master process. We do our development and testing on a test server. The plan is to move changes from test to production. Copying the process source is problematic because it leaves behind attachments, we're not sure what else might be lost if anything.

It would be useful if we could export the full process template then import it into the existing master process. I can't figure out how to accomplish this.

We have also found that after "pushing" a process template we need to take an outage to cycle the CCM to clear the cache. Otherwise projects and Eclipse sometimes have inconsistent views of process model. We consider this a serious problem, we should not need to cycle the system to deploy process changes.

What are your thoughts to manage this in an Enterprise settings?

Mark

I'd recommend updating the process configuration of a project area by
having the project area "share" the process from another project area,
i.e. a "process master" project area.

Note that you also have to null out the process guidance section of your
project area (or else that will override the shared process guidance).
To see what it should look like when you are done, just look at the
Process Configuration Source of the built-in "Unconfigured Process"
template. Just paste that into the Process Configuration Source of your
project area.

Cheers,
Geoff

On 2/8/2012 4:08 AM, sweetyferdous wrote:
Hi,

Please tell us the steps of deploying a new version of process
template in a project area where already an existing version of the
process template is deployed.

Right now we are copying/pasting the content of the new process
template in the Process Configuration Source tab in RTC. THX.

permanent link
Martha (Ruby) Andrews (3.0k44051) | answered Feb 08 '12, 9:11 p.m.
JAZZ DEVELOPER
Hello,
Geoff is correct that using a shared process can make the update easier. Template changes will not automatically be applied to the process provider. However, once the provider is updated, changes will be reflected in all of the areas that consume process from that provider.

Martha
Jazz Developer, Process Team
Hi,

Please tell us the steps of deploying a new version of process template in a project area where already an existing version of the process template is deployed.

Right now we are copying/pasting the content of the new process template in the Process Configuration Source tab in RTC. THX.

permanent link
Mark Richmond (5144) | answered Feb 09 '12, 8:43 a.m.
Your approach does not scale in Enterprise Level deployments we have hundreds of projects and the number is growing daily. With your approach someone has to touch every project in the system. Which assumes that someone on our team is an administrator on every project. Jazz admin rights are restricted to the central administration. (we can talk about real distributed admin for enterprise level deployment some other time suffice to say the story is very poor). After we touch every project. We need to take an outage to cycle the CCM to clear the cache. Our testing has shown if we don't cycle the system projects and Eclipse often maintain a stale version of the project, resulting in inconstant behavior.

We need a better solution than touching hundreds of projects by hand.

In your case, we recommend exporting the process from the test server as a process template, then creating a new master project area on the production server and pointing the consumers to the new area.

Here are step by step instructions:
These instructions allow changes in a process provider project area to be moved across repositories.
Assume there are two repositories : repository1 and repository2 and each repository has a project area that provides process and project areas that consume that process.

1. Make changes to the process provider project area in repository1
2.Show the context menu for the project area in the Eclipse client and select "Extract Process Template...", enter a process ID, click Finish.
3.File > Export > Team Process > Process Template to export the template to a .zip file
4. File > Import > Team Process > Process Template to import the template into repository2
5. In repository2, create a new project area that will provide process. Use the template imported in step 4.
6. Edit the project areas that consume process to point to the new project area.
7. (optional) When all project areas have stopped consuming process from the old project area in repository2, archive the old project area.

Regards,
Martha
JazzDeveloper, Process Team

Our situation is that we have ~150 projects all of which point at a master project for their configuration. We have run into snags managing updates to the master process. We do our development and testing on a test server. The plan is to move changes from test to production. Copying the process source is problematic because it leaves behind attachments, we're not sure what else might be lost if anything.

It would be useful if we could export the full process template then import it into the existing master process. I can't figure out how to accomplish this.

We have also found that after "pushing" a process template we need to take an outage to cycle the CCM to clear the cache. Otherwise projects and Eclipse sometimes have inconsistent views of process model. We consider this a serious problem, we should not need to cycle the system to deploy process changes.

What are your thoughts to manage this in an Enterprise settings?

Mark

I'd recommend updating the process configuration of a project area by
having the project area "share" the process from another project area,
i.e. a "process master" project area.

Note that you also have to null out the process guidance section of your
project area (or else that will override the shared process guidance).
To see what it should look like when you are done, just look at the
Process Configuration Source of the built-in "Unconfigured Process"
template. Just paste that into the Process Configuration Source of your
project area.

Cheers,
Geoff

On 2/8/2012 4:08 AM, sweetyferdous wrote:
Hi,

Please tell us the steps of deploying a new version of process
template in a project area where already an existing version of the
process template is deployed.

Right now we are copying/pasting the content of the new process
template in the Process Configuration Source tab in RTC. THX.

permanent link
Geoffrey Clemm (30.1k23035) | answered Feb 09 '12, 2:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I believe you'd be interested in something like work item 171446:
"Allow a project area to both use a process from another project area as
well as share its process with other project areas".
This would give you an extra level of indirection, so that you could
just point parent project area at a new grandparent project area, and
then all the child project area would inherit the process of the new
grandparent.

If this is something you'd like to see, please feel free to add a
comment to 171446, indicating your interest/support.

Cheers,
Geoff

On 2/9/2012 8:53 AM, mgr100 wrote:
Your approach does not scale in Enterprise Level deployments we have
hundreds of projects and the number is growing daily. With your
approach someone has to touch every project in the system. Which
assumes that someone on our team is an administrator on every
project. Jazz admin rights are restricted to the central
administration. (we can talk about real distributed admin for
enterprise level deployment some other time suffice to say the story
is very poor). After we touch every project. We need to take an outage
to cycle the CCM to clear the cache. Our testing has shown if we don't
cycle the system projects and Eclipse often maintain a stale version
of the project, resulting in inconstant behavior.

We need a better solution than touching hundreds of projects by hand.


mandrewwrote:
In your case, we recommend exporting the process from the test server
as a process template, then creating a new master project area on the
production server and pointing the consumers to the new area.

Here are step by step instructions:
These instructions allow changes in a process provider project area
to be moved across repositories.
Assume there are two repositories : repository1 and repository2 and
each repository has a project area that provides process and project
areas that consume that process.

1. Make changes to the process provider project area in repository1

2.Show the context menu for the project area in the Eclipse client
and select "Extract Process Template...", enter a process
ID, click Finish.
3.File> Export> Team Process> Process Template to export
the template to a .zip file
4. File> Import> Team Process> Process Template to
import the template into repository2
5. In repository2, create a new project area that will provide
process. Use the template imported in step 4.
6. Edit the project areas that consume process to point to the new
project area.
7. (optional) When all project areas have stopped consuming process
from the old project area in repository2, archive the old project
area.

Regards,
Martha
JazzDeveloper, Process Team

mgr100wrote:
Our situation is that we have ~150 projects all of which point at a
master project for their configuration. We have run into snags
managing updates to the master process. We do our development and
testing on a test server. The plan is to move changes from test to
production. Copying the process source is problematic because it
leaves behind attachments, we're not sure what else might be lost if
anything.

It would be useful if we could export the full process template then
import it into the existing master process. I can't figure out how to
accomplish this.

We have also found that after "pushing" a process template
we need to take an outage to cycle the CCM to clear the cache.
Otherwise projects and Eclipse sometimes have inconsistent views of
process model. We consider this a serious problem, we should not need
to cycle the system to deploy process changes.

What are your thoughts to manage this in an Enterprise settings?

Mark

gmclemmwrote:
I'd recommend updating the process configuration of a project area by

having the project area "share" the process from another
project area,
i.e. a "process master" project area.

Note that you also have to null out the process guidance section of
your
project area (or else that will override the shared process
guidance).
To see what it should look like when you are done, just look at the

Process Configuration Source of the built-in "Unconfigured
Process"
template. Just paste that into the Process Configuration Source of
your
project area.

Cheers,
Geoff

On 2/8/2012 4:08 AM, sweetyferdous wrote:
Hi,

Please tell us the steps of deploying a new version of process
template in a project area where already an existing version of the
process template is deployed.

Right now we are copying/pasting the content of the new process
template in the Process Configuration Source tab in RTC. THX.


permanent link
Mark Richmond (5144) | answered Feb 09 '12, 3:40 p.m.
Martha:

Please expand on the update of the process provider. The behavior we want is for process changes to appear in a slave project when the master is updated. What we have observed is after an update in the master many projects now hold a slate copy of the project template which results in inconsistent behavior or out right failure. Our only solution is to cycle the CCM. This is unacceptable in the Enterprise Environment we can't take a downtime hit to accomplish a simple process change.

Hello,
Geoff is correct that using a shared process can make the update easier. Template changes will not automatically be applied to the process provider. However, once the provider is updated, changes will be reflected in all of the areas that consume process from that provider.

Martha
Jazz Developer, Process Team
Hi,

Please tell us the steps of deploying a new version of process template in a project area where already an existing version of the process template is deployed.

Right now we are copying/pasting the content of the new process template in the Process Configuration Source tab in RTC. THX.

permanent link
Geoffrey Clemm (30.1k23035) | answered Feb 10 '12, 12:38 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
This was addressed earlier in this thread. In particular:

Note that you also have to null out the process guidance section of your
project area (or else that will override the shared process guidance).
To see what it should look like when you are done, just look at the
Process Configuration Source of the built-in "Unconfigured Process"
template. Just paste that into the Process Configuration Source of your
project area.

Cheers,
Geoff

On 2/9/2012 3:53 PM, mgr100 wrote:
Martha:

Please expand on the update of the process provider. The behavior we
want is for process changes to appear in a slave
project when the master
is updated. What we have observed is after an update
in the master many projects now hold a slate copy of the project
template which results in inconsistent behavior or out right failure.
Our only solution is to cycle the CCM. This is unacceptable in the
Enterprise Environment we can't take a downtime hit to accomplish a
simple process change.

mandrewwrote:
Hello,
Geoff is correct that using a shared process can make the update
easier. Template changes will not automatically be applied to the
process provider. However, once the provider is updated, changes
will be reflected in all of the areas that consume process from that
provider.

Martha
Jazz Developer, Process Team
sweetyferdouswrote:
Hi,

Please tell us the steps of deploying a new version of process
template in a project area where already an existing version of the
process template is deployed.

Right now we are copying/pasting the content of the new process
template in the Process Configuration Source tab in RTC.
THX.


permanent link
Mark Richmond (5144) | answered Feb 10 '12, 8:16 a.m.
We found that copying the project source can leave things behind such as icons and other attachments. There may be other items we don't know about about.

Hi,

Please tell us the steps of deploying a new version of process template in a project area where already an existing version of the process template is deployed.

Right now we are copying/pasting the content of the new process template in the Process Configuration Source tab in RTC. THX.

Your answer


Register or to post your answer.