Challenges in Development perspective:
1. In-build file server location is missing in CPI for testing the file scenarios as we have al11 there.
2. Still it is difficult to do iflow transport mechanism
3. Lagging with some predefined camel expressions.
4. For each step payload validation in missing in Web UI on the debug mode.
5. HTTP adapter still missing with PATCH method, but there is an workaround for using it.
6. Editing the Iflow from the manage integration content is not possible.
7. Multiple receive channels should not use same WSDL port name which doesn’t allow to use single wsdl with many services unless it has unique port name
8. Save doesn’t save the changes to current version, saved as draft, sometime misses the unsaved changes on webpage timeout
9. Unlike PI, for File adapter- source file is not deleted immediately after its picked up but only after complete processing of the file which results in reprocessing of the same file when the current message processing fails or the lock time is not specified appropriately.
10. Sometimes, iFlow remains in starting state itself and latest changes deployed doesn’t reflect at runtime.
Challenges in Support perspective:
1. No queue monitoring in CPI.
2. Filtering of error/success messages is not that efficient on tracking the issues.
3. No restart/resend option available to send the failed messages in certain cases.
4. If the end system has downtime, no option to control the messages at CPI like we stop sender channel in PI.
5. If there is extract to Excel option in messages monitoring screen, will be more helpful.
Challenges in Testing:
1. SAP enabled the option for internal mapping test sometime back, but end to end test is missing in CPI as we do in PI.
2. With help of log level information for debugging the issue is still not matured
1. In-build file server location is missing in CPI for testing the file scenarios as we have al11 there.
2. Still it is difficult to do iflow transport mechanism
3. Lagging with some predefined camel expressions.
4. For each step payload validation in missing in Web UI on the debug mode.
5. HTTP adapter still missing with PATCH method, but there is an workaround for using it.
6. Editing the Iflow from the manage integration content is not possible.
7. Multiple receive channels should not use same WSDL port name which doesn’t allow to use single wsdl with many services unless it has unique port name
8. Save doesn’t save the changes to current version, saved as draft, sometime misses the unsaved changes on webpage timeout
9. Unlike PI, for File adapter- source file is not deleted immediately after its picked up but only after complete processing of the file which results in reprocessing of the same file when the current message processing fails or the lock time is not specified appropriately.
10. Sometimes, iFlow remains in starting state itself and latest changes deployed doesn’t reflect at runtime.
Challenges in Support perspective:
1. No queue monitoring in CPI.
2. Filtering of error/success messages is not that efficient on tracking the issues.
3. No restart/resend option available to send the failed messages in certain cases.
4. If the end system has downtime, no option to control the messages at CPI like we stop sender channel in PI.
5. If there is extract to Excel option in messages monitoring screen, will be more helpful.
Challenges in Testing:
1. SAP enabled the option for internal mapping test sometime back, but end to end test is missing in CPI as we do in PI.
2. With help of log level information for debugging the issue is still not matured
No comments:
Post a Comment