Continuing with my series about Logic Apps and EDI, today I will start a "sub-series" about how to use PowerShell and the API Rest, to deploy EDI artifacts to our Enterprise Integration Account.
Monday, July 31, 2017
Thursday, July 27, 2017
Large Data Growth In Biztalk360 Database
Recently in one of our BizTalk360 deployments, the database grow fast, even that we have configured the Purging (Settings > BizTalk360 Health > Data Purging).
BizTalk360 don't send e-mail notifications
Recently we configured a BizTalk360 and in our environment, alerts/notification aren’t being sent.
Monday, July 03, 2017
Tracing SAP Adapter
When we have problems with the SAP Adapter, is easy to turn on tracing.
We need only add in our connection URI the RfcSdkTrace parameter and set to true.
Adding this parameter, the adapter traces will be sent to system32 folder, with a minimum trace level.
If you need to send the traces to other directory, you have to add RFC_TRACE_DIR environment variable and set the value of the desired output folder.
Also, if you need traces more detailed, you have to add RFC_TRACE environment variable and set it to 1 or 2. By default and if we don't add this variable, the value is 0 that means tracing level is bare minimum. The 2 value is the more detailed tracing level.
For more information, check this documentation.
We need only add in our connection URI the RfcSdkTrace parameter and set to true.
Adding this parameter, the adapter traces will be sent to system32 folder, with a minimum trace level.
If you need to send the traces to other directory, you have to add RFC_TRACE_DIR environment variable and set the value of the desired output folder.
Also, if you need traces more detailed, you have to add RFC_TRACE environment variable and set it to 1 or 2. By default and if we don't add this variable, the value is 0 that means tracing level is bare minimum. The 2 value is the more detailed tracing level.
For more information, check this documentation.
Subscribe to:
Posts (Atom)