Refer: https://docs.ifs.com/techdocs/23r1/070_remote_deploy/010_installing_fresh_system/200_installing_ifs_cloud/035_ifs_cloud_ifsinstaller/030_installation_parameters/#parameters_for_connect
IFS Connect PL/SQL query timeout parameter (IFS_QUERY_TIMEOUT) is exposed to custom_values.yaml as connectQueryTimeout from 23R1SU7 onwards.
Please add more details about the flow. Specially, about the Routing Address is used in this flow and about the timeout that you have set to 1min.
This can be defined in Routing Addressed and according to the values in the message conditional based Routing Rule can be configured to use the relevant Routing Address.https://docs.ifs.com/techdocs/Foundation1/040_administration/240_integration/300_ifs_connect/030_routing_rules_addresses/default.htm#How_to_create_a_destination_address
You can duplicate the default FILE_SENDER1 and configure it accordingly.Refer documentation: https://ifstechdocs10.azurewebsites.net/Foundation1/040_administration/240_integration/300_ifs_connect/010_configure_connect/#How_to_create_a_new_configuration_parameter_instanceThen you can define separate Routing Addresses using the different FILE Sender instances.
IFS Connect Projection Sender (Routing Address type Projection) does only support only Unbound Actions and Functions with an Input Structure. The projection ‘SalesGroupEntity’ you are trying to call is not supported by Projection Sender since it doesn’t have any Action/Function defined.Refer: https://docs.ifs.com/techdocs/23r2/030_administration/030_integration/300_ifs_connect/030_routing_rules_addresses/#address_dataAs a workaround you can try using IFS Connect REST Sender.
Can you please share the Routing Rule and the Address details?
@Takesha Kaluarachchi Please find the answers for your questions below:IFS Connect is a light weight integration broker and it has known limitations with File Integrations. One of those limitations is, IFS Connect memory consumption is high when processing files. To read/process a file with the size 100 MB IFS Connect consume around 2 GB of a heap memory.This sizing is possible assuming the messages are processing InOrder (one at a time). If the execution is Parallel which means 100 MB * (nX parallal threads), then the heap consumption will also increases along with the running parallels threads. Also the other integrations which are running in the environment also consume the same heap memory which should be a considerable factor for the memory allocation.With that IFS Connect Framework limitation in mind, R&D can recommend some changes/modification for the integration solution:Send files in smaller chunks – Require changes in file pushing solution also may require changes in dat
You can find it from here: IFS23R1_TEMPLATE_SMALL_14082023.txt
OAuth2.0 Authentication support was added in apps10 UPD6
Authentication is handled by IFS Connect itself. You don’t have to get the token and pass it. You just have to set the authentication details and the rest endpoint details in the Routing Address Configurations. https://docs.ifs.com/techdocs/Foundation1/040_administration/240_integration/300_ifs_connect/010_configure_connect/060_transport_connectors/rest_samples_itd/rest_post_example.htm
command_sys.send_rest_message is not the ideal option for your requirement. This is an inbuilt method to be used with REST type Event Actions. There is a dedicated API for REST type of integrations which is plsql_rest_sender_api.Refer: https://docs.ifs.com/techdocs/Foundation1/040_administration/240_integration/300_ifs_connect/010_configure_connect/060_transport_connectors/configure_rest_transport_connector.htmhttps://docs.ifs.com/techdocs/Foundation1/050_development/200_all_ref_manuals/api_ref_itd/restapi/default.html
Hi Bryan,There is no projection endpoint available in IFS Cloud to send mails. Because the use case of mail sending is mainly for outbound (from IFS Cloud to outside). But there is a PL/SQL API that you can use for send mail. /Udesha
Hi Jan,Sorry for my mistake. HTTP Method is ‘PATCH_NO-X’ not HTTP_NO-X’.What is the error you get for the 3rd scenario above. I can not see the entire error text in the screenshot.
After setting the HTTP Method to ‘HTTP_NO-X’, IFS Rest sender will send direct ‘PATCH’ requests. From the last exception (after changing the HTTP Method to ‘HTTP_NO-X’), it seems that your third party end point doesn’t support direct ‘PATCH’. So better to check with your third-party endpoint whether they support direct ‘PATCH’ or PATCH set with the ‘X-HTTP-Method-Override’ header parameter.
Please report a support ticket for this./Udesha
No any built-in support for KAFKA in soapgateway as well.
Setting an application server task (application message) to a Cancel state can only be done manually. Application Server Tasks are scheduled using a Database task. But still any database error/shutdown should make the Application Server Tasks in to Failed state. But not to Cancel. I can’t think of a scenario that this happens automatically.
HTTP Method in REST Type Routing Address can be set in two ways. One way is in Routing Address Configurations. And the other way is in Pl/SQL code when using plsql_rest_sender_api. If the HTTP method set in both places then the priority will be given to the value sent from PL/SQL side.Please refer the tech doc: https://docs.ifs.com/techdocs/Foundation1/040_administration/240_integration/300_ifs_connect/010_configure_connect/060_transport_connectors/configure_rest_transport_connector.htm (Under the topic How to call a REST endpoint using REST Connector → Request Method
FTPS, SFTP File Based Integrations are also support in IFS Cloud
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.
