Troubleshooting
Problem
When attempting to deploy a customization JAR file using the IBM Sterling Order Management CLI, the process fails with a 'FATAL: EOF' error. The same JAR file can be successfully uploaded and deployed manually through the SST interface.
Symptom
Use is unable to deploy the JAR file through the CLI command. The error messages include 'FATAL: EOF' and 'interface conversion: interface {} is nil, not string'. The same JAR deploys successfully through manual upload to SST.
Cause
The issue is caused by configuration file or the CLI parsing/handling.
Diagnosing The Problem
- Inspect the CLI command used for deploying the JAR file.
- Verify the configuration file (NAME_config.json) for any errors or inconsistencies.
- Check the ssctl command's syntax and options for deploying customizations.
- Compare the configuration file used with a known working configuration.
- Update the CLI tool to the latest version and refresh the SST token in the config file.
- Use the corrected command ./ssctl customization deploy -f $FILE --config ./$CONFIG_FILE to deploy the JAR file.
Resolving The Problem
1. Ensure the JAR file is correctly named and located in the expected directory.
2. Use the correct CLI command to deploy the customization: ./ssctl customization deploy -f $FILE --config ./$CONFIG_FILE.
3. Verify the configuration file ($CONFIG_FILE) is correctly referenced and contains the necessary settings.
4. Execute the command and confirm the deployment is successful by checking the process ID returned.
Related Information
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
05 February 2026
UID
ibm17259764