Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Maximum Payload Size and limitations for Soap router

Avatar

Avatar
Validate 1
Level 2
Aalokitoaami
Level 2

Likes

14 likes

Total Posts

29 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 2
Aalokitoaami
Level 2

Likes

14 likes

Total Posts

29 posts

Correct Reply

3 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
Aalokitoaami
Level 2

31-10-2019

We are using nl/jsp/soaprouter.jsp for creating new records in the database. We are planning to use the xtk:session WriteCollection method and create/update multiple records in one call.

What is the maximum size of request payload the endpoint accepts?

As per the contract, we cam make 50K engine calls per day. So if I merge multiple record insert/updates into one payload, that will be considered as one call. Please confirm.

The methods like write and others accepts the open XML as parameter and thus it is very difficult for the caller to know the actual structure of the payload. Is it possible to generate a wsdl which will expose the attributes of a schema as class properties and some method accepting the class or class collection as parameter to save the records.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Establish
MVP
wodnicki
MVP

Likes

969 likes

Total Posts

1,090 posts

Correct Reply

513 solutions
Top badges earned
Establish
Affirm 500
Contributor
Shape 1
Give Back 100
View profile

Avatar
Establish
MVP
wodnicki
MVP

Likes

969 likes

Total Posts

1,090 posts

Correct Reply

513 solutions
Top badges earned
Establish
Affirm 500
Contributor
Shape 1
Give Back 100
View profile
wodnicki
MVP

04-11-2019

Hi,

API calls have no limit in size AFAIK, they're ordinary HTTP POST.

The Update data workflow activity defaults to transaction batches of 10k.

That said, if possible use files for ETL as they are strictly better:

  • Simple, don't need a message bus or specialized code
  • Reliable, doesn't require high availability, files can be checksummed
  • Performant, use bulk load feature of db
  • Auditable, can zip files to look backward in time
  • Free, don't need extra hardware and not subject to license limitation

Thanks,

-Jon

Answers (0)