[Jhs-leads] epic52 - cutover

Kirkpatrick, Ivan Ivan.Kirkpatrick@dep.state.fl.us
Wed, 16 Mar 2005 13:48:12 -0500


Epic51 is not going away.   We are strongly encouraging those who can to
migrate ASAP to 52.  I am looking for any hard evidence that 52 is not
ready.....anyone who has any problems on 52 should bring them to the
attention of the Java Team ASAP.

Any projects that need a stable demo deployment can have one that is not
subject to the nightly build and deployment routine. =20

To enable a stable deployment of a demo application we would create a
GrpProjDemo container and deploy any version of your application =
manually.


-----Original Message-----
From:	Waters, Kathryn
Sent:	Wed 3/16/2005 1:11 PM
To:	Wallace, Leslie; jhs-leads@lists.dep.state.fl.us;
jhs-pms@lists.dep.state.fl.us
Cc:	Java Team
Subject:	RE: [Jhs-leads] epic52 - cutover
As a the PM for IMS MES, I request that access to epic51 be allowed to
continue until epic52 is fully operational and stable. I am to perform
several demonstrations on the MES application to the Business Needs =
Design
Team this month and I need to know that the application will be =
operational.

Thank you
Kathryn Waters



-----Original Message-----
From: jhs-leads-admin@lists.dep.state.fl.us
[mailto:jhs-leads-admin@lists.dep.state.fl.us]On Behalf Of Wallace,
Leslie
Sent: Wednesday, March 16, 2005 11:05 AM
To: jhs-leads@lists.dep.state.fl.us; jhs-pms@lists.dep.state.fl.us
Cc: Java Team
Subject: [Jhs-leads] epic52 - cutover


Attention Java Team-Leads and Project Managers,
	we are now officially cutting over to epic52 as our integration
server. Access to epic51 will soon no-longer be available. In support of =
this
cutover we ask that each team-lead verify that all pending changes to =
their
respective applications have been made on epic51. Once this is =
accomplished
the team-lead should send a request to the Java_team to request access =
to the
epic52 server. At that time java_team staff will:
1. Set the initial passwords for each group member on epic52
2. Setup the environment variables for each group member on epic52
3. Perform the project setup for each app

If at all possible, team-leads/project managers should verify that all =
team
members, have verified access to epic52 by COB today or asap.
=09
Leslie

**Note - Some groups have already requested and have been granted access =
to
this server. If your group falls in this category please ensure that all
necessary changes from this point forward are made on epic52. Not on =
epic51.
=09

_______________________________________________
Jhs-leads mailing list
Jhs-leads@lists.dep.state.fl.us
http://lists.dep.state.fl.us/cgi-bin/mailman/listinfo/jhs-leads