altquark
Legendary Poster
I just discovered a relatively new document on the KG entitled "Why Websphere 4.0 Single Server Is Not A Production Solution for OneWorld Jas Server" in which JD Edwards states
Only one environment can be used with each install of Websphere 4.0 Single Server since the first time an end user logs into a OneWorld environment on the Jas server, this application for this environment is cached. The next person who signs in that goes to the exact application will be pulling the specs from the OneWorld environment previously logged in. If more than one environment is installed on this Jas server, then specs will have to be the same between environments otherwise or spec corruption could occur.
and
Websphere 4.0 Single Server can not be configured for more than one environment since each environment needs it's own instance (AS_JDEdwards_X). WAS 4.0 Advanced Edition Single Server can only have one instance, then only one environment can be set up on a JAS server with WAS 4.0 AES. This is due to the way that WebSphere caches for each instance. If multiple instances are wanted for multiple environments, then WebSphere 4.0 Advanced Edition should be used. The Advanced Edition allows for creation of multiple instances.
Also, WebSphere 4.0 Advanced Single Server is single threaded. It should not be used in a production environment unless there will be less than 20 concurrent users accessing it at one time. We have noticed a severe performance decrease with the Single Server Edition if more than 20 users are accessing that instance.
I somewhat agree technically with the above - that SSE is not designed to create multiple instances of the Web Application Server - but completely disagree for the requirements FOR multiple instance of the Java Application Server.
All of my customers are running multiple individual servers - but each server is configured with only a single Websphere instance. One instance of Websphere will EASILY support multiple OneWorld environments - since the environment is split by pathcode.
I might be wrong here - but why would JDE post such a deplorable document on the knowledge garden ? Response Line is starting to use this as a defence - referring to it on the simplest of support issues. Customers I am dealing with are actually using the Enterprise Edition of Websphere themselves since they use Websphere for other purposes - but they still only have a single Web Application Server instance running. I have seen other companies run Single Server Edition with NO repurcissions - and (wrongly stated above) Single Server Editions is certainly NOT single threaded.
I would love to hear comments on this from other listeroos - including the configuration you are running the HTML solution.
Only one environment can be used with each install of Websphere 4.0 Single Server since the first time an end user logs into a OneWorld environment on the Jas server, this application for this environment is cached. The next person who signs in that goes to the exact application will be pulling the specs from the OneWorld environment previously logged in. If more than one environment is installed on this Jas server, then specs will have to be the same between environments otherwise or spec corruption could occur.
and
Websphere 4.0 Single Server can not be configured for more than one environment since each environment needs it's own instance (AS_JDEdwards_X). WAS 4.0 Advanced Edition Single Server can only have one instance, then only one environment can be set up on a JAS server with WAS 4.0 AES. This is due to the way that WebSphere caches for each instance. If multiple instances are wanted for multiple environments, then WebSphere 4.0 Advanced Edition should be used. The Advanced Edition allows for creation of multiple instances.
Also, WebSphere 4.0 Advanced Single Server is single threaded. It should not be used in a production environment unless there will be less than 20 concurrent users accessing it at one time. We have noticed a severe performance decrease with the Single Server Edition if more than 20 users are accessing that instance.
I somewhat agree technically with the above - that SSE is not designed to create multiple instances of the Web Application Server - but completely disagree for the requirements FOR multiple instance of the Java Application Server.
All of my customers are running multiple individual servers - but each server is configured with only a single Websphere instance. One instance of Websphere will EASILY support multiple OneWorld environments - since the environment is split by pathcode.
I might be wrong here - but why would JDE post such a deplorable document on the knowledge garden ? Response Line is starting to use this as a defence - referring to it on the simplest of support issues. Customers I am dealing with are actually using the Enterprise Edition of Websphere themselves since they use Websphere for other purposes - but they still only have a single Web Application Server instance running. I have seen other companies run Single Server Edition with NO repurcissions - and (wrongly stated above) Single Server Editions is certainly NOT single threaded.
I would love to hear comments on this from other listeroos - including the configuration you are running the HTML solution.