Calling all IFS REST gurus…Has anyone successfully sent multipart/form-data requests to REST endpoints using IFS standard functionality or do you need to go down the UTL_HTTP route to do this? I seem to get parsing errors whenever i try to send the message using plsql_rest_sender_api.call_rest_endpoint2.
I’m setting up an SFTP reader in IFS Cloud21. I’ve uploaded a knownhosts file and id key file (both in txt format as IFS returns an unexpected server error if no file extension is given). The reader is enabled but not picking up any files.I would like to scrutinise the IFS Connect logs to troubleshoot. The Cloud 21 documentation on IFS Connect logging seems sparse and it isn’t clear where the logs are. Looking on the ubuntu server there appears to be a config file which is driven by the JSF properties/Logging properties in Cloud 21. This file contains a file location but it’s commented out:## Connect log file##handler.connectlog.type=textfile#handler.connectlog.filename=@IFS_HOME@/instance/@IFS_INSTANCE@/logs/j2ee/ifsconnectlog-@IFS_MWS_SERVER@.log#handler.connectlog.level=info#handler.connectlog.maxsize=10M#handler.connectlog.filecount=5#handler.connectlog.categories=integrationI suspect that these commented out elements are from Apps 10. This environment was uplifted to Cloud21
I’m trying to utilise the plsql_rest_sender_api.call_rest_endpoint method passing the CLOB. As soon as i try to follow the documentation to add url parameters the method fails with wrong number or types of arguments in call to ‘CALL_REST_ENDPOINT’.My problem is, if i don’t use url parameters then i’ll need to set up multiple routing addresses for each specific endpoint. This will cause issues when the endpoint changes from test to production as i’ll need to change them all.Has anyone managed to utilise the url_params_ functionality within plsql_rest_sender_api.call_rest_endpoint ?
“Failure of Web Server BridgeNo backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.” Has anyone encountered this message? The environment comes up and stays up for a brief amount of time (anything from 5 mins to 45 mins) before it fails with the error above when trying to connect.Nothing obvious in server monitoring tools. This is a test environment which isn’t heavily stressed. RegardsChris
Has anyone ever seen this error when trying to publish custom fields?…
When using the Excel Data Migration Add-in if any fields contain dates IFS brings them into Excel in the form DD/MM/YYYY HH:MI:SS. If you do nothing and try to Validate the row, the result column seems to insist that the field doesn’t contain anything (if mandatory). If you click in the field and then out again Excel re-presents the field as YY/MM/YYYY HH:MI and right aligns it. It then validates ok. Obviously if you have a lot of records you can’t click in every field to ensure the formatting corrects itself. Does anyone know how to solve this ?
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.