|
Problem |
Editing the ServerGroup for the "System
Properties" will not propagate the changes to clones |
|
|
|
Solution |
The "System Properties" has been
changed to be a Clone-Only attribute on WebSphere Application Server 4,
for PTF 2, and above. The "System Properties" will not be propagated to
the clones, but the user can add/modify the properties in the clone
attributes.
The reason for the change of the design on WAS 4.0.2 is because on 4.0.1,
one can add the "System Properties" to the clones only through the Server
Group and the system properties field on the clones is "uneditable". The
"System Properties" for a server group are copied into all clones. This
has the potential of causing a critical error when starting the server
group
in many situations.
For example:
The server group contains application servers (clones) on different system
platforms. We add a system properties with some path specified for a
server group to enable security. The server group contains 20 application
servers, 10 of which are on AIX machine(s), and the others on NT
machine(s).
was.home=c:/WebSphere/AppServer
enable.Java2Security=true
java.security.policy=c:/WebSphere/AppServer/properties/java.policy
If we propogate the system properties to all clones (application
servers), it would fail to start the application servers on any AIX node
since the WAS install path on AIX is different from the NT. The user has
to change the properties for the clones on any AIX node to their local
directory (e.g., was.home=/usr/WebSphere/AppServer ...).
However, the System Properties field on the clones is
"uneditable" on 4.0.1. This is clearly incorrect behavior, thus the
"System Properties" were changed to be a Clone-Only Attribute on 4.0.2
release, and beyond. |
|
|
|
|
|
|