About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Question & Answer
Question
This document will answer the question, "How do you change the TCP/IP host and/or domain name used by an IBM WebSphere Application Server Profile (Standalone or DMGR topologies) after changing the IBM i server's TCP/IP host and/or domain information in CFGTCP Option 12?"
Cause
IBM i server's TCP/IP host and/or domain information changed in CFGTCP Option 12. This might occur when a migration occurs to a new IBM i OS VRM or hardware partition.
Answer
NOTE: The video above only provides a walk-through on how to change the host name for a standalone Websphere profile. It does not cover how to change the host name for a Deployment Manager Federated Environment topology.
To change/update the TCP/IP host and/or domain information used by your IBM WebSphere Application Server Profile (Standalone or DMGR topologies) to initialize its TCP/IP transports, follow the steps below.
| 1. | Identify and record the current TCP/IP host and domain name of your IBM i server. CFGTCP Option 12 The Fully Qualified Domain Name (FQDN) is equal to the "Host name"."Domain name" values. Example: Host name . . . AS400 Domain name . . . IBM.COM FQDN = AS400.IBM.COM For the new Websphere Host Name, we would use the value, AS400.IBM.COM. $HOST = FQDN you identified |
| 2. | Start a Qshell session and change to the Websphere profile_root/bin directory. Standalone: STRQSH cd /QIBM/UserData/WebSphere/AppServer/<version>/<edition>/profiles/<profileName>/bin where... <version> = V7, V8, V85, or V9 <edition> = Express, Base, or ND <profileName> = Name of the Websphere Full Profile you wish to modify Example: STRQSH cd /QIBM/UserData/WebSphere/AppServer/V9/Base/profiles/default/bin DMGR and Federated Nodes: STRQSH cd /QIBM/UserData/WebSphere/AppServer/<version>/ND/profiles/<DMGRprofileName>/bin Example: STRQSH cd /QIBM/UserData/WebSphere/AppServer/V9/ND/profiles/dmgr/bin |
| 3. |
Stop all application servers that need their host name changed. For DMGR topologies, this included the Deployment Manager, Node Agent(s), and Application Server(s).
Standalone:
cd /QIBM/UserData/WebSphere/AppServer/<version>/<edition>/profiles/<profileName>/bin stopServer DMGR and Federated Nodes:
cd /QIBM/UserData/WebSphere/AppServer/<version>/ND/profiles/<DMGRprofileName>/bin stopManager cd /QIBM/UserData/WebSphere/AppServer/<version>/<edition>/profiles/<federatedProfile>/bin stopNode stopServer <server> Repeat for all nodes and servers. |
| 4. | Identify the Node Name of your Websphere Profile by executing the "dspwasinst" command. NOTE: For DMGR topologies, you will need to identify the DMGR node as well as each federated node name and identify the Deployment Manager's SOAP port. ./dspwasinst Record the value next to the "Node:" text towards the top of the output from the dspwasinst command. Example (standalone): Instance type: Express Application Server Display WAS instance: Instance name: WAS85SVR Profile path: /QIBM/UserData/WebSphere/AppServer/V85/Express/profiles/WAS85SVR Template path: /QIBM/ProdData/WebSphere/AppServer/V85/Express/profileTemplates/default Administrative Security status: Disabled Instance type: Express Application Server Cell: AS400_WAS85SVR Node: AS400_WAS85SVR where $NODE = AS400_WAS85SVR Example (dmgr and federated nodes): Instance type: Network Deployment Deployment Manager Display WAS instance: Instance name: DMGR01 Profile path: /QIBM/UserData/WebSphere/AppServer/V85/ND/profiles/DMGR01 Template path: /QIBM/ProdData/WebSphere/AppServer/V85/ND/profileTemplates/management Administrative Security status: Disabled Instance type: Express Application Server Cell: AS400_DMGR01 Node: AS400_DMGR01 ... Managed nodes: AS400_WASNODE ... Additional ports: 8879 SOAP_CONNECTOR_ADDRESS port where Deployment Manager $NODE = AS400_DMGR01 Federated Nodes $NODE = AS400_WASNODE DMGR SOAP port = 8879 You will need these node and DMGR soap port values for the upcoming steps. |
| 5. |
Enter the wsadmin administration scripting environment by executing the "wsadmin" command.
NOTE: For DMGR environments, ensure you are executing this under the DMGR profile root bin directory. (i.e. /QIBM/UserData/WebSphere/AppServer/V9/ND/profiles/dmgr/bin)
./wsadmin -conntype NONE -lang jython NOTE: After executing the above command, the "*sys-package-mgr*" will load several JAR files during the initialization of the wsadmin administration scripting envrionment. After the the environment has been initialized, a "wsadmin>" prompt will be displayed. |
| 6. | Execute the AdminTask.changeHostName script to change the host name of your Websphere Profile. At the "wsadmin>" prompt, execute the following command, AdminTask.changeHostName('[-interactive]') DMGR and Federated Nodes: Ensure wsadmin is connected to the DMGR profile. Run the AdminTask.changeHostName() function for the DMGR node and then again for each Federated Node. |
| 7. | Enter the Node Name of your Websphere Profile. Enter the value for the $NODE variable you recorded in step 4 and then press ENTER. > AdminTask.changeHostName('[-interactive]') Change Host Name Change the host name of a node *Node Name (nodeName): > AS400_WAS85SVR |
| 8. | Enter the new TCP/IP Host Name you want your Websphere Profile to use. Enter the value for the $HOST variable you recorded in step 1 and then press ENTER. > AdminTask.changeHostName('[-interactive]') Change Host Name Change the host name of a node *Node Name (nodeName): > AS400_WAS85SVR *Host Name (hostName): > AS400.IBM.COM |
| 9. | When prompted for "System Name", do not specify a value. Leave this blank and press ENTER. > AdminTask.changeHostName('[-interactive]') Change Host Name Change the host name of a node *Node Name (nodeName): > AS400_WAS85SVR *Host Name (hostName): > AS400.IBM.COM System Name (systemName): > |
| 10. | When prompted for "Regenerate Certificates", enter the value "true" and press ENTER. NOTE: Do not include the quotation marks. This value is case-sensitive. Any other value besides "true" will not force the regeneration of the default SSL certificates. > AdminTask.changeHostName('[-interactive]') Change Host Name Change the host name of a node *Node Name (nodeName): > AS400_WAS85SVR *Host Name (hostName): > AS400.IBM.COM System Name (systemName): > Regenerate Certificates (regenDefaultCert): > true |
| 11. | Enter "F" and press ENTER to finish the change host name process. NOTE: The generated command that will be executed will be displayed. If the execution of the command is successful, no messages will be displayed and the "wsadmin>" prompt will be returned. Change Host Name F (Finish) C (Cancel) Select [F, C]: [F] > F WASX7278I: Generated command line: AdminTask.changeHostName('[-nodeName AS400_WAS85SVR -hostName AS400.IBM.COM -regenDefaultCert true ]') '' wsadmin> |
| 12. | Execute the "AdminConfig.save()" command to save the configuration changes to the Websphere Profile. AdminConfig.save() NOTE: If the execution of the command is successful, no messages will be displayed and the "wsadmin>" prompt will be returned. wsadmin> > AdminConfig.save() '' wsadmin> |
| 13. | For DMGR topologies only - Execute steps 6-12 for the Deployment Manager profile and all Federated Node profiles before proceeding to the next step. |
| 14. | Execute the "exit" command on the wsadmin prompt to exit the wsadmin administration scripting environment. wsadmin> > exit $ |
| 15. | For DMGR toplogies only - Start the Deployment Manager application server and then execute the syncNode command for each federated profile to sync the host name changes to each node. cd /QIBM/UserData/WebSphere/AppServer/<version>/ND/profiles/<DMGRprofileName>/bin startManager cd /QIBM/UserData/WebSphere/AppServer/<version>/<edition>/profiles/<federatedProfile>/bin syncNode <dmgrHost> <dmgrSOAPport> -profileName <federatedProfile> Repeat this for each federated profile. |
| 16. | Start your Websphere Profile(s) and HTTP Server for the changes to take affect. Standalone: ./startServer <serverName> DMGR and Federated Nodes: cd /QIBM/UserData/WebSphere/AppServer/<version>/<edition>/profiles/<federatedProfile>/bin startNode startServer <server> Repeat for all nodes and servers. where... <serverName> = Your application server name. If your application server name is the same name as the profile name, then you do not need to specify the <serverName> value on the stopServer and startServer scripts. If your HTTP Server is running on the IBM i OS, you can execute the following commands to restart your HTTP Server. ENDTCPSVR *HTTP HTTPSVR(<HTTPServerName>) STRTCPSVR *HTTP HTTPSVR(<HTTPServerName>) |
| 17. | Congratulations! You have now successfully changed the TCP/IP host name for your Websphere Profile. |
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CHUAA2","label":"WebSphere Application Server"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
More support for:
IBM i
Component:
WebSphere Application Server
Software version:
All Versions
Operating system(s):
IBM i
Document number:
667349
Modified date:
27 September 2024
UID
nas8N1021509
Manage My Notification Subscriptions