Troubleshooting
Problem
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 in order to add XIO_ADDRESS port information.
Diagnosing The Problem
Check the serverindex.xml file for your node and verify if the node agent entry contains an XIO_ADDRESS endpoint. If the XIO_ADDRESS is missing, then this is the problem.
Resolving The Problem
You should only attempt to resolve this issue if you want to use XIO and plan to use the WebSphere Application Server node agent as an eXtreme Scale catalog server.
The addXIOPort.ant script can be run manually as follows:
cd <WAS_HOME>\bin
Run ant script as follows:
ws_ant.bat(.sh) -f <WAS_HOME>\profileTemplates\xs_augment\actions\addXIOPorts.ant -DprofilePath=<WAS_HOME>\profiles\<ProfileToFix> -DWAS_HOME=<WAS_HOME>
Example:
C:\WAS85\bin>ws_ant.bat -f C:\WAS85\profileTemplates\xs_augment\actions\addXIOPorts.ant -DprofilePath=C:\WAS85\profiles\AppSrv03 -DWAS_HOME=C:\WAS85
where C:\WAS85 is my WAS_HOME directory
AppSrv03 is the profile to be updated by addXIOPorts.ant script
If your deployment manager profile was already augmented, the node was augmented after federation, and the XIO_ADDRESS was still missing on the node agent, then you must either create the XIO_ADDRESS manually on the node agent or augment the deployment manager again.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21640030