clewis
Member
Changing AS400s - What\'s the best way?
This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.
--=_356EA2DC.1E7F1F8A
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
We have been testing One World Xe on a test AS400 for the past few months. =
We installed all environments on the test AS400, in coexistence mode, and =
went through a bunch of testing, which included customizing the Customer =
Inquiry programme, and then moving it through OMW and installing it in the =
Production Environment on the test AS400. We are now preparing to install =
One World on our production AS400, and I'm wondering about the best way of =
doing this. We want to end up with all environments pointing to the =
production AS400 - currently they all point to the test AS400. We also =
want to keep the modifications we've made to the Customer Inquiry =
programme.
My original thought was to wipe clean the Deployment Server and start =
again from scratch - that way I could be sure that no gremlins are left =
over from the previous install and testing. However, that won't keep the =
mods we've made. Is it possible to check out the mods to a client, wipe =
the deployment server and install everything pointing to the production =
AS400, and then somehow check the mods back in to the production AS400 =
from the client? (After changing the ODBC Data Sources on the client to =
point to the production AS400). How do we do the check-in without having =
done a check-out from the production AS400?
Is that the best way to go? Are there any other ways to accomplish the =
task?=20
Configuration:
Test AS400 - Model 720 running v4r5; Central Objects on the AS400. WinNT =
Deployment server with 2Gig RAM and 70+ Gig HD space. One World Xe in =
Coexistent environment
Want to end up with:
Production AS400 - Model 820 running v4r5; Central Objects on the AS400. =
WinNT Deployment server with 2Gig RAM and 70+ Gig HD space. One World Xe =
in Coexistent environment
Any suggestions??
Thanks,
Colin
--=_356EA2DC.1E7F1F8A
Content-Type: text/html
Content-Disposition: attachment; filename="TEXT.htm"
Content-Description: HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4134.600" name=GENERATOR></HEAD>
<BODY style="MARGIN-TOP: 2px; FONT: 10pt Arial; MARGIN-LEFT: 2px"
bgColor=#ffffff>
<DIV>We have been testing One World Xe on a test AS400 for the past few months.
We installed all environments on the test AS400, in coexistence mode, and went
through a bunch of testing, which included customizing the Customer Inquiry
programme, and then moving it through OMW and installing it in the Production
Environment on the test AS400. We are now preparing to install One World on our
production AS400, and I'm wondering about the best way of doing this. We want to
end up with all environments pointing to the production AS400 - currently they
all point to the test AS400. We also want to keep the modifications we've made
to the Customer Inquiry programme.</DIV>
<DIV></DIV>
<DIV>My original thought was to wipe clean the Deployment Server and start again
from scratch - that way I could be sure that no gremlins are left over from the
previous install and testing. However, that won't keep the mods we've made. Is
it possible to check out the mods to a client, wipe the deployment server and
install everything pointing to the production AS400, and then somehow check the
mods back in to the production AS400 from the client? (After changing the ODBC
Data Sources on the clientto point to the production AS400). How do we do
the check-in without having done a check-out from the production AS400?</DIV>
<DIV></DIV>
<DIV>Is that the best way to go? Are there any other ways to accomplish the
task? </DIV>
<DIV></DIV>
<DIV>Configuration:</DIV>
<DIV></DIV>
<DIV>Test AS400 - Model 720 running v4r5; Central Objects on the AS400.
WinNT Deployment server with 2Gig RAM and 70+ Gig HD space. One World Xe in
Coexistent environment</DIV>
<DIV></DIV>
<DIV>Want to end up with:</DIV>
<DIV></DIV>
<DIV>
<DIV>ProductionAS400 - Model 820 running v4r5; Central Objects on
the AS400. WinNT Deployment server with 2Gig RAM and 70+ Gig HD space. One World
Xe in Coexistent environment</DIV>
<DIV></DIV>
<DIV>Any suggestions??</DIV>
<DIV></DIV>
<DIV>Thanks,</DIV>
<DIV></DIV>
<DIV>Colin</DIV></DIV></BODY></HTML>
--=_356EA2DC.1E7F1F8A--
This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.
--=_356EA2DC.1E7F1F8A
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
We have been testing One World Xe on a test AS400 for the past few months. =
We installed all environments on the test AS400, in coexistence mode, and =
went through a bunch of testing, which included customizing the Customer =
Inquiry programme, and then moving it through OMW and installing it in the =
Production Environment on the test AS400. We are now preparing to install =
One World on our production AS400, and I'm wondering about the best way of =
doing this. We want to end up with all environments pointing to the =
production AS400 - currently they all point to the test AS400. We also =
want to keep the modifications we've made to the Customer Inquiry =
programme.
My original thought was to wipe clean the Deployment Server and start =
again from scratch - that way I could be sure that no gremlins are left =
over from the previous install and testing. However, that won't keep the =
mods we've made. Is it possible to check out the mods to a client, wipe =
the deployment server and install everything pointing to the production =
AS400, and then somehow check the mods back in to the production AS400 =
from the client? (After changing the ODBC Data Sources on the client to =
point to the production AS400). How do we do the check-in without having =
done a check-out from the production AS400?
Is that the best way to go? Are there any other ways to accomplish the =
task?=20
Configuration:
Test AS400 - Model 720 running v4r5; Central Objects on the AS400. WinNT =
Deployment server with 2Gig RAM and 70+ Gig HD space. One World Xe in =
Coexistent environment
Want to end up with:
Production AS400 - Model 820 running v4r5; Central Objects on the AS400. =
WinNT Deployment server with 2Gig RAM and 70+ Gig HD space. One World Xe =
in Coexistent environment
Any suggestions??
Thanks,
Colin
--=_356EA2DC.1E7F1F8A
Content-Type: text/html
Content-Disposition: attachment; filename="TEXT.htm"
Content-Description: HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4134.600" name=GENERATOR></HEAD>
<BODY style="MARGIN-TOP: 2px; FONT: 10pt Arial; MARGIN-LEFT: 2px"
bgColor=#ffffff>
<DIV>We have been testing One World Xe on a test AS400 for the past few months.
We installed all environments on the test AS400, in coexistence mode, and went
through a bunch of testing, which included customizing the Customer Inquiry
programme, and then moving it through OMW and installing it in the Production
Environment on the test AS400. We are now preparing to install One World on our
production AS400, and I'm wondering about the best way of doing this. We want to
end up with all environments pointing to the production AS400 - currently they
all point to the test AS400. We also want to keep the modifications we've made
to the Customer Inquiry programme.</DIV>
<DIV></DIV>
<DIV>My original thought was to wipe clean the Deployment Server and start again
from scratch - that way I could be sure that no gremlins are left over from the
previous install and testing. However, that won't keep the mods we've made. Is
it possible to check out the mods to a client, wipe the deployment server and
install everything pointing to the production AS400, and then somehow check the
mods back in to the production AS400 from the client? (After changing the ODBC
Data Sources on the clientto point to the production AS400). How do we do
the check-in without having done a check-out from the production AS400?</DIV>
<DIV></DIV>
<DIV>Is that the best way to go? Are there any other ways to accomplish the
task? </DIV>
<DIV></DIV>
<DIV>Configuration:</DIV>
<DIV></DIV>
<DIV>Test AS400 - Model 720 running v4r5; Central Objects on the AS400.
WinNT Deployment server with 2Gig RAM and 70+ Gig HD space. One World Xe in
Coexistent environment</DIV>
<DIV></DIV>
<DIV>Want to end up with:</DIV>
<DIV></DIV>
<DIV>
<DIV>ProductionAS400 - Model 820 running v4r5; Central Objects on
the AS400. WinNT Deployment server with 2Gig RAM and 70+ Gig HD space. One World
Xe in Coexistent environment</DIV>
<DIV></DIV>
<DIV>Any suggestions??</DIV>
<DIV></DIV>
<DIV>Thanks,</DIV>
<DIV></DIV>
<DIV>Colin</DIV></DIV></BODY></HTML>
--=_356EA2DC.1E7F1F8A--