Working with your new federated server nodes
After you complete the customization instructions, you have a WebSphere® Application Server for z/OS® application server federated node.
Procedure
- Check the default host alias list and all other cell-level documents to see if any need to be added in support of the applications and application servers on the newly federated node. Cell-level documents are not automatically updated by the federation process.
- Remove the location service daemon port definitions from your TCP/IP profile for the standalone application server cell because these are not used after federation.
What to do next
Note that web server configurations in an unmanaged node in a standalone application server cell are not migrated as part of federation. Use the administrative console or scripting to add new web server definitions to a Network Deployment cell.
Once these tasks are accomplished, a federated application server node is just like any other application server node. The primary difference is that it already has an application server and applications if they were federated as well. Read Working with your new managed server nodes for further information.