Thursday, 17 August 2017

IBM API Connect - Adding IBM DataPower Gateway into the mix - SOMA import failed

I've been tinkering with an IBM API Connect 5.0.7.2 implementation on my Mac, running all three VMs; the API Manager, the Developer Portal AND the DataPower Gateway on the same box.

However, I saw this: -


when attempting to integrate APIC and IDG.

I dumped out the APIC CMC logs: -

debug postmortem export sftp 10.10.2.3 user fred file /tmp/foobar.tar.gz

and, on the Mac, exploded the resulting tarball, giving me this: -

log/cmc.out:2017-08-17 13:19:30.076 SEVERE [T-83] [com.ibm.datapower.gwapi.impl.GatewaysImpl.deployFilesAndConfig] Deploy: APIMgmt_9A8A3AFACB/gw1: failed: IOException:SOMA import failed
log/cmc.out:Throwable occurred: java.io.IOException: SOMA import failed
log/cmc.out: at com.ibm.datapower.gwapi.soma.Manager.importConfig(Manager.java:657)
log/cmc.out: at com.ibm.datapower.gwapi.soma.Manager.importConfig(Manager.java:625)
log/cmc.out: at com.ibm.datapower.gwapi.soma.Manager.importConfig(Manager.java:621)
log/cmc.out:2017-08-17 13:19:30.084 SEVERE [T-83] [com.ibm.apimgmt.exception.APIGenericException$Serializer.serialize] Error(599597e2e4b0d25e2a2ee700), Http-Code(500), Message(SOMA import failed), User(cmc/admin), Path(post:/gatewayClusters/599426b4e4b04960a3daf1dd/servers/59959798e4b0d25e2a2ee6fa)


As a quick test, I'm moving the IDG VM from the main Mac to another Mac, in order to spread the load, leaving the Manager and Portal VMs on the primary box.

We'll see ……

*UPDATE*

Yes, as I suspected, once I moved the IDG VM to another box, and increased it's RAM from 4 GB to 8 GB, all is now well.


Now to test my API ....

No comments: