Specifying multiple profiles enables you collect information
for multiple cells, either for the top-level group or for the agent.
You specify multiple profiles during deployment. You specify them
in a websphere.profilePath property in one of two
places:
- Top-level group: Set the websphere.profilePath here
to collect profiles from multiple cells deployed across multiple hosts.
All hosts must use the same installation directory for the cell.
- Agent: Set the websphere.profilePath here
to collect profiles for multiple profiles on the same host.
Values for the websphere.profilePath property
Specify
one or more paths as the property value. Separate multiple paths with
a comma. The paths can be one of the following:
- path to a profile. The path does not have to specify /bin/wsadmin.sh,
but autodiscovery works with paths that do.
- path to a container directory of profiles. In this case the autodiscovery
code loops over each first-level directory. It registers base and
nd profiles. It skips node and server profiles.
When you specify multiple profiles, the following values are
read during autodiscovery:
- SOAP port (read from portdef.properties)
- profile path
- install path
Example value with two container directories and one profile
path:
"/opt/IBM/WebSphere/Profiles/,/opt/WAS/Profiles,/opt/IBM/profiles/dmgr"
Restriction: If you specify multiple container directories,
there should be no duplicates in the profile names they contain. If
autodiscover finds the same profile name, it overwrites the previously
found profile name.
Example: /opt/IBM/WebSphere/Profiles and /opt/WAS/Profiles both
contain a dmgr profile. A resource is created only
for the second dmgr resource, because the first profile
is overwritten.
If you encounter this situation, you can work
around it by creating a separate top-level group and segregate the
profile directories.