Re: RE: OneWorld Sizing
The network bandwidth really depends on the number of transactions that occur given a certain amount of time - and the size of the transactions.
As an example - a Sales Order differs between customers - some customers have sales orders with hundreds of lines - others have sales orders on the magnitude of only a few lines. Each line is a transaction to me - the majority of Sales Order Processing occurs with each individual line rather than the Beginning of the Document or the End of the Document (though this is where the commits occur usually).
In a Citrix environment, it really doesn't matter how many or how little sales orders one is plugging into the system. The more "active" users moving their mouse around and touching the keyboard will generate more network traffic than those who are not as active - but the two types of user normally use approximately the same amount of bandwidth. Streaming technologies such as Citrix are more Latent dependant than Transactional technologies such as the web.
The JD Edwards HTML client - when it is running 100% HTML - is pretty efficient. It does however work slightly different from the Windows client in that it works in a Page Mode - ie, the user types in all of the transactions in one web page and submits the whole page at once. Any errors would then be reported back. It is not, therefore, as interactive as the Windows client (I may be wrong about this with certain new forms under Xe - I await the flaming over this one....)
However - the transactions between client and server (browser and web server) are relatively light - especially on the number of Turns. Each sales order is purely a page of HTML being transferred backwards and forwards - hence bandwidth is not necessarily a problem. It should not be, therefore, at the top of your mind when sizing up the ERP application - make sure you have "enough" bandwidth that web-surfing ceases to become an issue.
Remember that the web solution requires that the web server is placed as close to the Enterprise Server as possible - I promise you that you do not want to see JDBC commands reaching over any latent network, it'll kill performance.
I have seen the OneWorld HTML client work on a CDPD connection with a handheld. It seems to work relatively well - given the fact that CDPD provides a maximum bandwidth of 19200 baud and the latency is usually >1 second. Citrix works over this connection type - but it is a little painful (>1 second between clicks and screen updates) - any other client type would never work correctly.
Rule of thumb. You need approximately 5K of concurrent bandwidth per user for Citrix with a minimum of 28K. I'd suggest that for each CONCURRENT web user size the network using about half. Therefore if 500 users are hitting your OneWorld Web Server CONCURRENTLY - I'd size up close to a T1.
None of the above information, by the way, is a reflection of any JD Edwards Sizing - and is only a suggestion and an opinion. Please treat this information accordingly.
Jon Steel
erpSOURCING LLC
http://www.erpsourcing.com
ERP Sourcing
http://www.erpsourcing.com
[email protected]