Amine :
According to my experience (across South America) 2-3 Kbps per
concurrent user are more than enough for HTML Clients, but Java
clients need about 15 Kbps to run well.
I have to admit that it's much easier to setup and administer WTS
clients than HTML/JAS clients, nevertheless users tend to prefer the
Web interface provided by JAS Server.
JAS Server doesn't provide any Internet security at all, it's up to
you to setup proxies, firewalls, SSL, etc.
Assuming that you want to install the NT JAS Server, you will need :
a) W2K Server, IIS 5.0, WebSphere 3.5 (much better than 3.0.2.x),
Xe SP14.1 or higher.
I've tested JAS with B7331 and it was a horror story, JAS B7332
was so-so, and finally I've found that JAS Xe is fine.
b) JDBC drivers (Oracle provides them for free, SQL ones have to be
bought to BEASys), IBM JDK 1.2.2 (provided by WebSphere) and MS JDK.
c) Define the J Environments (create your JAS Server with a Oneworld
plan)
d) Install the JAS OneWorld
e) Set it up (a quite annoying task, it's very sensitive to upper
and lower case, spaces, pufff!)
f) Test it thoroughly on the Intranet
g) Setup OneWorld and external (proxy, firewall,...) security
h) Be aware than JAS Service Packs come on different CDs that regular
OneWorld Service Packs, but both have to be at the same level.
Yours, Sebastian
Sebastian Sajaroff
MCP+I,MCSE,MCDBA,Citrix Admin
B7321 to Xe, NT/SQL, JAS, Interop, Citrix
--------------------------------------------------------------------
B7321 to Xe, NT/W2K/SQL
JAS, Interoperability
MCDBA,MCP+I,MCSE,Citrix Admin
[email protected]
Grupo ASSA - Application Software SA