SSAJAROFF
Reputable Poster
Hi there!
I'd also like to be able to launch full server or workstation packages from
a Win2K+WTS Deployment.
I understand that Denver discourages JDE development on WTS clients because
specs could be corrupted, etc... but why should
it be disabled on the Deployment?
I think that OneWorld bugs are far more harmful that any potential spec
corruption that could appear from my WTS activity!
I also agree that Win2K+WTS client is excellent... It's far better than
PCAnywhere and its performance is similar to ICA.
Nevertheless, while we all wait for that WTS fix some package stuff can be
done on a Win2K+WTS Deployment :
a) Update packages that don't include any TBLE trigger or BSFN.
b) Full workstation or server packages can be partially done on the
Deployment if you :
b.1) Define a full client package there, but keep BSFN, NER generation and
Compression checks unmarked.
b.2) Submit it
b.3) When it finishes, go to a development workstation, Package Build, reset
that package, unactivate it, Build Revisions,
uncheck Spec generation, and check BSFN generation, keep Compression
unmarked (compression runs much much faster
on the Deployment), activate the package, Submit, it will ask if you want to
erase package directories, say NO.
b.4) When it ends, you'll have specs and BSFN already generated.
b.5) If you want compression, you may go to the Deployment, Package Build,
reset that package, unactivate it, Build Revisions,
uncheck Spec generation, uncheck BSFN and NER generation, check Compression,
activate the package, Submit, it will ask
if you want to erase package directories, say NO. At the end, you'll have a
full compressed client package.
Note that server packages don't usually run with compression.
This runs much faster than a full package being built on the client
workstation.
Sebastian Sajaroff
B7321 to Xe, NT/W2K/SQL
JAS, Interoperability
MCDBA,MCP+I,MCSE,Citrix Admin
[email protected]
Grupo ASSA - Application Software SA
I'd also like to be able to launch full server or workstation packages from
a Win2K+WTS Deployment.
I understand that Denver discourages JDE development on WTS clients because
specs could be corrupted, etc... but why should
it be disabled on the Deployment?
I think that OneWorld bugs are far more harmful that any potential spec
corruption that could appear from my WTS activity!
I also agree that Win2K+WTS client is excellent... It's far better than
PCAnywhere and its performance is similar to ICA.
Nevertheless, while we all wait for that WTS fix some package stuff can be
done on a Win2K+WTS Deployment :
a) Update packages that don't include any TBLE trigger or BSFN.
b) Full workstation or server packages can be partially done on the
Deployment if you :
b.1) Define a full client package there, but keep BSFN, NER generation and
Compression checks unmarked.
b.2) Submit it
b.3) When it finishes, go to a development workstation, Package Build, reset
that package, unactivate it, Build Revisions,
uncheck Spec generation, and check BSFN generation, keep Compression
unmarked (compression runs much much faster
on the Deployment), activate the package, Submit, it will ask if you want to
erase package directories, say NO.
b.4) When it ends, you'll have specs and BSFN already generated.
b.5) If you want compression, you may go to the Deployment, Package Build,
reset that package, unactivate it, Build Revisions,
uncheck Spec generation, uncheck BSFN and NER generation, check Compression,
activate the package, Submit, it will ask
if you want to erase package directories, say NO. At the end, you'll have a
full compressed client package.
Note that server packages don't usually run with compression.
This runs much faster than a full package being built on the client
workstation.
Sebastian Sajaroff
B7321 to Xe, NT/W2K/SQL
JAS, Interoperability
MCDBA,MCP+I,MCSE,Citrix Admin
[email protected]
Grupo ASSA - Application Software SA