Default federated server profiles
We can use the addNode script or the WAS Network Deployment console to federate a profile into a WAS Network Deployment cell.
When you federate a profile into a cell, a node agent server is created to monitor the application server. The node agent server serves as an intermediary between the application servers on the node and the deployment manager that oversees the entire cell.
For more information on working with federated profiles, see the article on administering applications and their environment in the information center.
This article describes the default profile provided with WebSphere Application Server after it is federated, or added, to a WAS Network Deployment cell.
The following properties are available for the default profile:
- Profile name
- Cell name
- The cell name with the form hostNetwork, where host is the host name of the server, for example, MYIBMINetwork. The cell name is case-sensitive.
- Node name
- The host name of the iSeries server. For example, MYIBMI. The node name is case-sensitive.
- Application server name
- server1. The application server name is case-sensitive.
- Node agent server name
- nodeagent. The server name of the node agent is case-sensitive.
The server1 application server includes these applications:
- The DefaultApplication example application
- Use DefaultApplication application, which contains the snoop, hello, and hitcount examples that quickly verify the application server configuration.
- The install verification application (ivtApp)
- Use ivtApp application to use the ivt Qshell script and verify the application server configuration.
The default profile is configured to use the ports listed in the Port number settings article in the information center. To change any of these ports, use the deployment manager console or run the chgwassvr script from Qshell and specify the dmgr profile on the -profileName option. The chgwassvr script is in the app_server_root/bin directory.
For more information about the script, see the article on the chgwassvr command in the information center. Potential port conflicts with other versions or editions of WAS are noted where appropriate.
To display information such as node name, ports used, servers, and installed applications for the default profile, run the dspwasinst script from Qshell. For more information, see the article on the dspwasinst command in the information center.
Manage default profiles