While installing Maximo Asset Management (MAM) 7.6.1.3 on WebSphere Application Server (WAS), we encountered a critical issue during the Tivoli Process Automation Engine (TPAE) configuration process. The deployment step, which applies database changes using the updated script, failed with the error:
“ADMC0016E: The system cannot create a SOAP connector to connect to host [hostname] at port [port number]“
This problem persisted despite checking relevant configurations like TLS settings and host names, which made the troubleshooting process challenging.
The SOAP connector error likely stemmed from a miscommunication between the WebSphere Application Server and Maximo during database connection establishment. Initial investigations suggested that the issue could be linked to the use of a CNAME for the VirtualHost name or problems with certificates due to self-signed certificates. This theory was further supported by the fact that the WebSphere console and Maximo UI worked fine but the database changes would not apply.
Root Cause: Encryption Mismatch in maximo.properties
The root cause of the issue was traced to the database connection string and password encryption within the maximo.properties file. By default, sensitive information like database credentials must be encrypted in the properties file. However, the database URL itself was in plaintext, while the password was not encrypted. This mismatch led to the SOAP connector failure, as WebSphere could not establish a secure connection to the database.
We discovered that by adding “;encrypt=false;” to the database URL, WebSphere could handle the connection string properly, allowing for a plaintext URL while keeping the password encrypted. This setup allowed Maximo to connect securely and proceed with the deployment process without further issues.
Solution: Encrypting the Database Password
To resolve the issue, the following steps were taken:
- Modify the database URL: Add ;encrypt=false; at the end of the URL in the maximo.properties file. This tells WebSphere that the database URL does not need encryption, which avoids conflicts during connection establishment.
- Encrypt the password: Run the encryptproperties.bat script to encrypt the database password. This script ensures that sensitive credentials are securely stored while allowing the server to connect to the database. https://www.ibm.com/docs/en/maximo-eam-saas?topic=SSBLW8/com.ibm.mbs.doc/securgroup/t_encrypt_properties_security.htm
By separating the encryption for the URL and password, we were able to proceed with the TPAE configuration and complete the EAR file deployment successfully.
About
A3J Group is a leading solutions and consulting firm based in Tampa, Florida, specializing in Enterprise Asset Management (EAM) with a focus on fully developed Computerized Maintenance Management System (CMMS) solutions like IBM Maximo.
In addition to our suite of proprietary products—including MxMobile, our powerful mobile solution for Maximo—we provide traditional consulting services that help organizations plan, implement, optimize, and support their EAM strategies. Whether clients need hands-on configuration, strategic guidance, or ongoing system support, our team delivers the expertise to drive long-term success.
With over 50 years of combined experience, our specialized team is dedicated to our core mission: to serve as excellent stewards of our clients’ trust and investments, while driving measurable results through tailored, high-impact solutions and intelligent consulting.
Visit us at www.a3jgroup.com. Or drop us a line at info@a3jgroup.com.
