Skip to content

Changing the hostname of a Maximo WebSphere Application Server

There may come a time when you need to change the hostname of your IBM Maximo WebSphere Application Server. This could be due to migrating the configuration to another machine, changing domain/subnet information, or copying a virtual machine for development purposes. Whatever the reason, this article aims to help get Maximo back up and running after a hostname change on the IBM WebSphere Application Server. For example, let’s assume the old hostname is, and we want to change it to in a WebSphere v8.5.5 environment.

Step 1: Change the Host Name for the Cell Manager and Node

  1. Sign into the IBM WebSphere Application Server machine as an administrative user.
  2. Stop the IBM Cell Manager and Node Agent Windows Services if they are running.
  3. Open a command prompt as an administrator and navigate to the C:\IBM\WebSphere\AppServer\bin directory (substitute your WebSphere folder if necessary).
  4. Run the following command: wsadmin.bat -conntype NONE -lang jython
  5. At the wsadmin> prompt, issue the following command: AdminConfig.list('ServerIndex') This will list out the existing servers (typically the Cell Manager and Node). The results will look like: '(cells/ctgCell01/nodes/ctgCellManager01|serverindex.xml#ServerIndex_1)' '(cells/ctgCell01/nodes/ctgNode01|serverindex.xml#ServerIndex_1)'
  6. For each of the entries returned in the previous step, issue the following command: AdminConfig.modify('(cells/ctgCell01/nodes/ctgCellManager01|serverindex.xml#ServerIndex_1)', "[[hostName]]") AdminConfig.modify('(cells/ctgCell01/nodes/ctgNode01|serverindex.xml#ServerIndex_1)', "[[hostName]]")
  7. Save the changes by running:
  8. Exit the wsadmin> prompt by running: exit
  9. Start the IBM Cell Manager Windows Service. This should enable you to log into the IBM WebSphere Console.

Step 2: Change the Host Name for the various Ports

  1. Sign into the IBM WebSphere Console as the wasadmin user.
  2. Open the Servers > Server Types > WebSphere application servers page.
  3. Click on the MXServer application server.
  4. Click on the Ports link under Communications.
  5. Click on each address that has the old hostname and change it to the new hostname. Click OK.
  6. Open the System administration > Deployment manager page.
  7. Click on the Ports link under Additional Properties
  8. Click on each address that has the old hostname and change it to the new hostname. Click OK.
  9. Open the System administration > Node agents page.
  10. Click on the nodeagent Node agent.
  11. Click on the Ports link under Additional Properties
  12. Click on each address that has the old hostname and change it to the new hostname. Click OK.
  13. Click the Save to master configuration file link.
  14. Synchronize changes back to the cell.
  15. Log out of the IBM WebSphere Console
  16. Restart the IBM Cell Manager Windows Service.
  17. Start the IBM Node Agent Windows Service.
  18. Depending on whether the MXServer application server is set to start automatically, you may need to log back into the IBM WebSphere Console to start it.
Maximo should now be running on a new host name!

Share This

Related Posts

ibm_mxmobile_maximo mobile_app_application_suite_report_maintenance_reliability_industry_4_work_order_enterprise_asset_management_inventory_perform_count_log_time_create_meter_reading_shipping_and_recieving_mobility_admin_service_request_issue_parts_material_approve_task_job_plan_software_upgrade
MxMobile Update May 2023 Release
As an IBM Maximo mobile solution provider, A3J Group consistently improves the functionality and features...
Workflow Delegates
Pretend you are going to take a real vacation, two weeks in Spain with no work laptop. You have planned...
ibm_mxmobile_maximo mobile_app_application_suite_report_maintenance_reliability_industry_4_work_order_enterprise_asset_management_inventory_perform_count_log_time_create_meter_reading_shipping_and_recieving_mobility_admin_service_request_issue_parts_material_approve_task_job_plan_software_upgrade
MxMobile Update April 2023 Release
A3J Group is happy to announce the latest MxMobile releases below. The releases will be available on...

8 Responses


  1. Hi, thanks for this article. how about when the domain name changes? After changing the domain name from the default name of ‘WorkGroup’, Maximo stopped working.

    • Changing the domain name effectively changes the fully qualified host name of the server. Even if the computer name remains the same, WebSphere wants that fully qualified host name (or an IP address). You should be able to follow these same steps, but be sure to input the fully qualified name.

  2. hi,does maximo need to be redeployed after it?
    whats about other maximo app (e.w. maximo anywhere).

    regards, Tom

    • The Maximo application should not need to be redeployed, but all of the WebSphere-related services need to be restarted for the change to take effect.

  3. Hi Alex,
    Are there other changes needed like regenerating or recreating security certificates or changing the HTTP Server configurations or anything else?

    • Certainly. There are several System Properties in the Maximo database that store the host name, such as Integration Framework URLs and attached document mapping. Also if you are using SSL and change the host name of the machine, you’ll need to generate and import a new certificate.

      • We did it like a manual IBMWAS90Service – ctgNode01 no start


  4. Thanks for the article. Unfortunately looks likes it is not working for version. After those steps (after bounce cell and node services), if you are back to wsadmin and run the following‘(cells/ctgCell01/nodes/ctgCellManager01|serverindex.xml#ServerIndex_1)’, ‘hostName’)

    you still get the IP address instead of the name. Also, if you are back to ” Servers > Server Types > WebSphere application servers ” you will see the hostname is still the IP address.

Add a Comment