Re: RE: OneWorld Config on AS/400
The deployment server MUST be NT. The application server can run on NT or
natively under OS/400. There are many environments running both the
database server and app server functions on the same box and same
partition. (you don't have to use LPAR or anything like that). You could
also have the app server on a separate 400 or in a separate partition if
you wanted.
We regularly use the Integrated NT card as a deployment server in our lab
tests and it works well. The big limitation to the integrated card is that
it is limited to a single processor. If your development environment is
such that you need fast and frequent package builds, then you might be
better with an external dual processor box for the deployment server.
Also, on older models, (prior to 8xx series and 270s), you are limited to a
333MHz integrated card, which is a little slow. The newer models are
running at 850MHz and should work well.
I haven't worked with or heard of anyone using the integrated card as an
application server. Basically, it functions the same as any other NT
server, so it SHOULD work fine. Again, the limit is going to be whether
your environment would require a multi-processor application server. If
so, then you'll need an external box, or you can just keep that
functionality running natively on the 400. I've only seen one very
informal, unstructured test comparing a 400 with an NT app server and the
400 performed better, but the difference was probably due more to
communications than the platform.
I don't think there are any big setup issues when using the integrated card
as the deployment server. From a high level, you configure the card,
allocate disk space to the NT server, and install NT, service packs, etc.
Once NT is loaded, it functions like any other NT server. You need to pay
attention to the same things you would on an external server, such as
network config and speeds, Client Access Express settings and service
packs, NT service packs, etc. From a OneWorld point of view, once NT is
installed, I don't think you need to perform any additional steps or
changes from an install on an external box.
The biggest issue is understanding how the disk space is allocated, and the
network setup for the card can be a bit confusing, but that has been
simplified in the latest releases of the card and OS/400. There are a
couple redbooks that go into details on the Integrated Netfinity Card, as
well as using it as a OneWorld deployment server. "Implementing Windows
NT on the Integrated Netfinity Server" - SG24-2164 & "J. D. Edwards
OneWorld Implementation on the AS/400" - SG24-5195
The card uses the 400's disks, but they are not in the same file system.
You allocate an amount of disk space or drive space, then assign it to the
card. The space is spread across all of the disks in the ASP, so you are
not allocating specific drives, just an amount of space. This space is
then formatted as FAT or NTFS and isn't used by OS/400, but appears as a
standard drive volume under NT. You can have multiple drive spaces
allocated to 1 integrated card.
Benefits of the card are that you can administer the NT server through the
400, reboot it remotely from the 400, administer and synchronize NT and 400
user IDs from the 400, have 1 centralized backup, use the 400's fast tape
and other devices, and you are using the 400's highly available disks.
It's also very easy to add more disk space.
In my opinion, there are a few drawbacks. You are using fairly expensive,
(although highly reliable and high performance), 400 disks, when you could
be using cheaper PC based disks. There are some cases where this makes
sense, but others where it doesn't. Also, there is a learning curve.
You'll have to learn a little about how the card works, and how to add
disk, etc. Another limitation is the single processor. Finally, a minor
issue, is that it boots a little slower than an external box. Normally
that isn't an issue, but usually when installing new drivers or software on
NT, you have to reboot a lot and it can be frustrating.
Hope this helps. Sorry if my bias shows through TOO much!
Rob Jump
IBM/J.D. Edwards International Competency Center
303-334-1054
[email protected]
DRezanka <
[email protected]>@jdelist.com on 03/12/2001 07:00:34 AM
Please respond to
[email protected]
Sent by:
[email protected]
To:
[email protected]
cc:
Subject: Re: RE: OneWorld Config on AS/400
Tom,
I have heard of a couple/few AS400 shops with the Deployment Server(DS) on
an IPCS card. As a warning, I understand this is not as straight forward a
setup as using a seperate server (usually requiring consulting). I have not
heard of an App Server on an integrated card.
Does the IPCS use the same disk and directory space as the AS400, or are
they segmented into separate partitions? If not, I suppose the problem with
using an IPCS for a DS and/or an App Server would be the directory
structure. Additionally, the DS and App Serv would have to be seperate
machine IDs. Could you do multiple IPCSs?
You can see, I don't know a whole lot about these IPCS cards. I also don't
know why it would be so complex to set one of these up if you know what you
are doing. However, from a practical standpoint and from what I have heard
about these cards, I don't know why you would want this sort of complexity
in your system. A network has enough trouble of its own. Also, it seems
from a price and scalability standpoint, it would be a whole lot simpler
and cheaper to maintain separate NT machines for a DS and App Serv.
My thoughts. For what the're worth.
Doug
[email protected]
Xe SP13.1, AS400 V4R3, CO-Oracle806, Co-A73c10, Citrix, NT JAS
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat
=&Board=OW&Number=7081
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at
http://www.JDELIST.com
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +