It's all about the answers!

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

×42,877

question asked: Aug 20 '09, 9:11 a.m.
question was seen: 4,653 times
last updated: Aug 20 '09, 9:11 a.m.

Related questions

Massive email flooding migration of RTC 1.0.1.1 to RTC 2.0

0
Adil Chahid (455●2●41●18) | asked Aug 20 '09, 9:11 a.m.
Hi all,

could you explain the following behaviour that did occur on our end after we did a migration exercice in our lab to assess on the impact of migration RTC 1.0.1.1 to RTC 2.0 in production ?

Here are the steps that were followed: 

* We did configure on a VM a WebSphere Express Instance pointing on the same LDAP as the WAS instance in  production.

* We did export the 50 GB and plus database using repotool.sh provided in the production RTC 1.0.1.1 instance.

* We did install RTC 2.0 on the production server (parallel to version 1.0.1.1)

* We did run the import of the previously exported repository in a new databse defined with the 8k pages as documented.

* We did deploy the RTC 2.0 WAR file into the Lab's WAS instance.

* We did configure it to reflect the same configuration as production: it points on the same AD, uses the same mail server, same whilelist ...



Once we did start the instance we were happy to see all our projects running in this new version but we were suprised to see that the new RTC 2.0 instance start flooding all the staff with mails about all the events that occured in WI that were concerning them.
So thousand of mails were sent in just a few minutes.
We had to stop the instance and to disable the mail notification.

So how can we prevent this from occurring the day of the real migration ?
We thank you for your time!

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Work Item & UI Commons Team (1.3k●1) | answered Aug 20 '09, 9:28 a.m.
Thunder wrote:
Hi all,

could you explain the following behaviour that did occur on our end
after we did a migration exercice in our lab to assess on the impact
of migration RTC 1.0.1.1 to RTC 2.0 in production ?

Here are the steps that were followed:

* We did configure on a VM a WebSphere Express
Instance pointing on the same LDAP as the WAS instance in
production.
* We did export the 50 GB and plus database using repotool.sh provided
in the production RTC 1.0.1.1 instance.
* We did install RTC 2.0 on the production server (parallel to
version 1.0.1.1)
* We did run the import of the previously exported repository in a new
databse defined with the 8k pages as documented.
* We did deploy the RTC 2.0 WAR file into the Lab's WAS instance.
* We did configure it to reflect the same configuration as
production: it points on the same AD, uses the same mail server,
same whilelist ...


Once we did start the instance we were happy to see all our projects
running in this new version but we were suprised to see that the new
RTC 2.0 instance start flooding all the staff with mails about all
the events that occured in WI that were concerning them.
So thousand of mails were sent in just a few minutes.
We had to stop the instance and to disable the mail notification.

So how can we prevent this from occurring the day of the real
migration ?
We thank you for your time!


Hi,

this is a known issue in 2.0, please see the related technote . This
is fixed in the 2.0.0.1 stream, sorry for the spam.

http://www-01.ibm.com/support/docview.wss?rs=3488&uid=swg21391225

--
Benjamin Pasero
Work Item & UI Commons Team

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.