Creating and augmenting profiles for WebSphere eXtreme Scale

Augmenting profiles for use with WebSphere eXtreme Scale is optional, but is required in the following usage scenarios:

• To automatically start a catalog service or container in a WebSphere Application Server process. Without augmenting the server profiles, servers can only be started programmatically using the ServerFactory API or as separate processes with the startOgServer or startXsServer scripts.
• To use Performance Monitoring Infrastructure (PMI) to monitor WebSphere eXtreme Scale metrics.
• To display the version of WebSphere eXtreme Scale in the WebSphere Application Server administrative console.
  Note: WebSphere eXtreme Scale augmentation is supposed to add the XIO_ADDRESS port number when profiles are federated before augmenting the eXtreme Scale profile, but the port number is missing. If augmentation is done prior to federation, then you must manually run the addXIOPort.ant script to add XIO_ADDRESS port information. For more information, see the technote, The XIO_ADDRESS is missing for WebSphere Application Server node agent if WebSphere eXtreme Scale augment is done before federation.

If you are running WebSphere eXtreme Scale within WebSphere Application Server Version 7.0, you can use the Profile Management Tool plug-in or the manageprofiles command to create and augment profiles.