In fact, there are 2 ‘sub-types’ of W* environments.
One ‘sub-type’ that was shipped with OneWorld Xe out-of-box (Sep 2000) had about 300 (400?) business functions mapped to enterprise server and all other bus functions were mapped to the client (LOCAL datasource) by default.
Sometime after that, JDE folks have changed their mind, and now they recommend to map all business functions to the ES by default, and only 200-300 specific function should be mapped to the client.
We started with 1st type of W* environment, and, eventually switched to the 2nd type.
The problem is that there is no ‘ideal’ set of mappings. When we asked JDE to send us their current set of OCM for W* environments, we found out that mappings for at least 4 BFs were making problems, and we had to change these mappings. The funny part of it is that these 4 issues are described on JDE Knowledge Garden. So it looks that some people in JDE don’t know what other people in JDE are doing.
I am saying ‘at least 4’ because we are not using HR/Payroll, we are almost not using Distribution, and don’t use all possible application in Financials and Manufacturing.
So I believe that our mappings are not 100% error free.
As to performance issues, we didn’t mention any speed degradation after switching from type 1 to type 2 mappings, but we don’t use advanced pricing as far as I know.
On other side, we didn’t mention any significant performance improvement
As to UBEs – we always had them mapped to the Enterprise server in W* environments, so I can’t say anything about performance difference.
By the way, W* environments are not purely Citrix environments; it also makes sense to use them on Fat clients, especially if network speed is not ideal.
Yaroslav Mudrenko
Xe, XU1, SP16.1, HP-UX 11.11, Oracle 8.1.7.1
W2000/Citrix Metaframe 1.8a.