Congratulations Alex Walter – 2018 IBM Champion!

For immediate release: February 13, 2018


Tampa, FL: Every year IBM chooses the best of the best and names them to a list of Champions.  Jumping the hurdle to become part of this group requires innovation, skill and dedication.  A3J Group is proud to announce that Alex Walter was named to the distinguished list of 2018 IBM Champions.

An IBM Champion is a thought innovator in IBM’s technical community.  IBM Champions are experts in IBM technologies, communities and solutions.  By recognizing these leaders, IBM strives to amplify the Champions’ voices and increase their sphere of influence.  An IBM Champion is an IT professional, business leader, developer, or educator who influences and mentors others to help them make best use of IBM software, solutions, and services.

I am honored to be named to the list of 2018 Champions. It’s exciting to be included in this distinguished group.  And I’m looking forward to continuing our focus on innovative solutions.

 Alex, CIO, A3J Group

After fifteen years in the EAM space, A3J Group formed under Alex’s executive leadership as a traditional consulting firm but also one that pushed the boundaries.  A3J Group’s widely varied customers have helped guide the team at A3J Group when deciding on which mobile initiatives to tackle next.  Being the best means listening to your customers and providing value they didn’t even know they wanted or existed.

Alex is someone who is always looking to be on the cutting edge of technology in order to provide the best user experience. He constantly researches and studies everything he can so that he remains the most knowledgeable and best equipped. It’s great to be working with someone with so much knowledge who is willing to have discussions on all topics at any time.   

Kelly, Senior Analyst, A3J Group

Executives at A3J Group are excited for how 2018 has shaped up for their company roadmap. They have aggressive plans to continue attacking the mobile market based on their customer experiences and demands as well as other macro elements influencing what users want and need.

It’s exciting to think about where we are going as a company. And seeing Alex recognized as a Champion is hopefully just the tip of the iceberg.  Sharing and collaborating is the way we will grow as a company and as an industry.  Our one goal remains – provide more value than expected at all times.  If we do that, we’ve done our jobs.

Kim, President, A3J Group

About A3J Group, LLC: A3J Group is a boutique consulting firm founded in 2016 and focused on technology solutions within the EAM industry.  In specific, they are focused on all areas of work with Maximo, an asset management system, through IBM.

Please direct inquiries to: or 877-A3J-GRP4

For more information about A3JGroup visit:

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:
  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!