single or multiple profiles in WebSphere?
Accepted answer
Hi Robin,
I would like to recommend going through the article :
https://jazz.net/wiki/bin/view/Deployment/StandardTopologiesOverview
In the above referred article, you can find different deployment options based on different parameters.
Some key considerations to make before going for a certain deployment option would be
a. the concurrent user load,
b. the purpose - scm is high or requirements usage is high or something else
c. acceptable performance expectations.
d. required scalability, may be you start small but would be bringing in more users/projects in, soon sometime..
In fact, based on the usage needs, you could co-locate some applications while giving a dedicated JVM (yes a new profile for it) for others.
If you are talking about v6.x, one profile will be an overkill.
Below 6.x, it may still be ok for a evaluation purpose. Use the article mentioned above as your guide and you may be in good shape even when new projects are on-boarded with more users...
Hope this helps.
Regards,
Dinesh
I would like to recommend going through the article :
https://jazz.net/wiki/bin/view/Deployment/StandardTopologiesOverview
In the above referred article, you can find different deployment options based on different parameters.
Some key considerations to make before going for a certain deployment option would be
a. the concurrent user load,
b. the purpose - scm is high or requirements usage is high or something else
c. acceptable performance expectations.
d. required scalability, may be you start small but would be bringing in more users/projects in, soon sometime..
In fact, based on the usage needs, you could co-locate some applications while giving a dedicated JVM (yes a new profile for it) for others.
If you are talking about v6.x, one profile will be an overkill.
Below 6.x, it may still be ok for a evaluation purpose. Use the article mentioned above as your guide and you may be in good shape even when new projects are on-boarded with more users...
Regards,
Dinesh
One other answer
I think it depends on how much isolation of these applications you want.
If you install all three into the same WAS profile, they share the same JVM, JDBC connection pool, and etc. If you install them separately into multiple WAS profiles, JVM, JDBC connection pools and etc will be isolated and what gets shared is at the OS level, such as CPU, physical memory and etc.
A single profile is easier to maintain, that's for sure. You can separate the application from this shared profile when the need comes (e.g. work load on a particular application increase significantly and affects other applications). It's a good practice to set up a reverse proxy to have a consistent public URI.
If you install all three into the same WAS profile, they share the same JVM, JDBC connection pool, and etc. If you install them separately into multiple WAS profiles, JVM, JDBC connection pools and etc will be isolated and what gets shared is at the OS level, such as CPU, physical memory and etc.
A single profile is easier to maintain, that's for sure. You can separate the application from this shared profile when the need comes (e.g. work load on a particular application increase significantly and affects other applications). It's a good practice to set up a reverse proxy to have a consistent public URI.