Open dasdagir opened 2 years ago
@dasdagir , we've found the problem which is that the zowe-scripts folder needs to be removed from the path.
Can you try and refactor /ims/zowe-scripts/bin/start.sh
to ims/bin/start.sh
in your USS directory, and update EXTERNAL_COMPONENTS
to point to /ims/bin
only ?
Let us know how you get on, and in the meantime I'll try and push a fix to the repository code and do a new build and update the docs.
@Joe-Winchester ,
Thank you for the work around. But still I was not able to fix the problem. i.e ZOWE launcher unable to start the IMS component.
Hi @dasdagir , can you e-mail on winchest@uk.ibm.com
and suggest some times when you're free and I'm happy to jump on a webex and get this fixed for you.
Hi @Joe-Winchester , I have sent my joblog to your mail-id. Now I can able to initiate the IMS component where as it throws me an Error : Invalid or corrupt jarfile
Hi All,
I was installing & configuring IMS API for ZOWE launcher task. I just followed the steps given in the below linki: https://github.com/zowe/ims-operations-api/blob/master/ims/docs/installing-ims-operations-api.md
But still unable to find IMS API services running either in API ML Catalog services & no unix process (ZWE1IM) has been started as mentioned in the link.
Getting the below error from the start-component script: ZWEL0001I component /usr/lpp/zowe-extensions/ims/zowe-scripts started unable to determine start script from component /usr/lpp/zowe-extensions/ims/zowe-scripts manifest, fall back to default bin/start.sh component /usr/lpp/zowe-extensions/ims/zowe-scripts (xxxxxxx) terminated,status = 0
Configured as below :
My question is here : while checking the scripts, it validates ZWELS_START_COMPONENT_ID & it enter in to backward compatible with no reason? Did I miss anything ??
Please suggest if I miss anything.