Federated default WebSphere Application Server instance
The information below describes the default instance provided with WebSphere Application Server after it is federated, or added, to a Network Deployment cell. Use the addNode script or the Network Deployment administrative console to federate an instance into a Network Deployment cell.
When you federate an instance 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 instances, see Administer instances of WebSphere Application Server Network Deployment.
General properties
- Instance name: default
- Cell name: hostnameNetwork, where hostname is the host name of the iSeries server. For example, MYISERIESNetwork. The cell name is case-sensitive.
- Node name: The host name of the iSeries server. For example, MYISERIES. The node name is case-sensitive.
- Application server name: server1. The application server name is case-sensitive.
- Node agent server name: nodeagent. The node agent server name is case-sensitive.
- JMS server name: jmsserver. The JMS server name is case-sensitive.
JMS support
If JMS is enabled for the instance before you federate the instance, a separate server process, named jmsserver, is created for the instance's JMS server. For a federated instance, the embedded JMS server does not run in the application server process.
Pre-deployed applications
The server1 application server includes these applications:
The DefaultApplication example application
The DefaultApplication contains the snoop, hello, and hitcount examples, which allow you to quickly verify your application server configuration.The install verification application (ivtApp)
This application allows you to use the ivt Qshell script to verify the application server configuration.
Default ports
The default instance is configured to use the ports listed here. To change a port for any of the servers in the federated default instance, you can use the chgwassvr script provided with the WebSphere Application Server Network Deployment product. This script is located in the /QIBM/ProdData/WebAS5/ND/bin directory. For more information about the script, see The chgwassvr script.
Note: Do not use the chgwassvr script shipped in /QIBM/ProdData/WebAS5/Base/bin. If you use this script, the changes are replaced when the deployment manager synchronizes its master copy of the configuration files with the node.
Default application server ports
The default application server (server1) uses these ports. To change these ports, run this command from Qshell:
/QIBM/ProdData/WebAS5/ND/bin/chgwassvr -node nodename -server server1 -port_parameter new_portwhere nodename is the name of the node for the default instance, -port_parameter is the parameter for the port that you want to change, and new_port is the new port number. For example, to change the name service port to 9811 for an application server in the MYISERIES node, run this command:/QIBM/ProdData/WebAS5/ND/bin/chgwassvr -node MYISERIES -server server1 -nameservice 9811After you make changes to a federated instance, Synchronize the configuration changes with the node.
Potential port conflicts with other versions or editions of WebSphere Application Server are noted where appropriate.
Port number Usage chgwassvr parameter Potential conflicts 9810 Name service port (also called bootstrap port or RMI connector port) -nameservice 8880 SOAP port -soap 9080 Internal HTTP port -inthttp
- WebSphere Application Server V4.0, Advanced Edition default internal HTTP port
- WebSphere Application Server V4.0, Advanced Single Server Edition default internal HTTP port
7873 Data replication service (DRS) client port -drsclient 9501 SAS server port -sas 9503 CSIv2 server authentication port -csiv2server 9502 CSIv2 client authentication port -csiv2client Default node agent server ports
The default node agent server (nodeagent) uses these ports. To change these ports, run this command from Qshell:
/QIBM/ProdData/WebAS5/ND/bin/chgwassvr -node nodename -server nodeagent -port_parameter new_portwhere nodename is the name of the node for the default instance, -port_parameter is the parameter for the port that you want to change, and new_port is the new port number. For example, to change the name service port to 2819 for a node agent server in the MYISERIES node, run this command:/QIBM/ProdData/WebAS5/ND/bin/chgwassvr -node MYISERIES -server nodeagent -nameservice 2819Potential port conflicts with other versions or editions of WebSphere Application Server are noted where appropriate.
Port number Usage chgwassvr parameter Potential conflicts 2809 Name service port (also called bootstrap port or RMI connector port) -nameservice 8878 SOAP port -soap 7888 Data replication service (DRS) client port -drsclient 9900 ORB listener port -orblistener 9901 SAS server port -sas 9201 CSIv2 server authentication port -csiv2server 9101 CSIv2 client authentication port -csiv2client 7272 Node discovery port -nodediscovery 5000 Node multicast discovery port -nodemulti The default JMS server (jmsserver) uses these ports. To change these ports, run the chgwassvr script from Qshell:
/QIBM/ProdData/WebAS5/ND/bin/chgwassvr -node nodename -server jmsserver -port_parameter new_portwhere nodename is the name of the node for the default instance, -port_parameter is the parameter for the port that you want to change, and new_port is the new port number. For example, to change the name service port to 2820 for a JMS server in the MYISERIES node, run this command:/QIBM/ProdData/WebAS5/ND/bin/chgwassvr -node MYISERIES -server jmsserver -nameservice 2820Potential port conflicts with other versions or editions of WebSphere Application Server are noted where appropriate.
Port number Usage chgwassvr parameter Potential conflicts 2810 Name service port (also called bootstrap port or RMI connector port) -nameservice 8876 SOAP port -soap 5557 Internal JMS server port -jmssecure 5558 Queued JMS server port -jmsqueued 5559 Direct JMS server port -jmsdirect To display information such as node name, ports used, servers and installed applications for the default instance, run the dspwasinst script from Qshell.