Marina, can you describe your objective in more detail? What is the use case / scenario you are pursuing? Are you evaluating using DOORS Next, or evaluating an integration to DOORS Next?

Note: DOORS Next has many APIs; you are probably interested in a small subset of them. The API documentation is at https://jazz.net/wiki/bin/view/Deployment/ELMProductAPILanding

Hi Marina,

there is no real limit, but of course it will generate load on the server. When updating artifacts in 6.0.6 there was a risk of overloading the system because one index creation process could keep the speed when doing mass imports, but this problem is gone in newer versions as far as I know.

the most common mistake we see out in the wild is to use basic auth to access the api. This will trigger an authentication with jts for every request that will bring your system in trouble.

For artifacts you need to se the oslc documentation for requirements. 

If you want to skip the research and have an easier API you could have a look at our DNG API Gateway that provides and easy Rest-API for reading and writing data in a performant and system resource preserving way: https://requisis.com/en/produkte/elm-api.html

Regards,

Nikolai

Unfortunately, I can't find the 'reply' button.

So,

 1. Thanks for your replies.

 2. We are just looking for potential limits, such as pagination with a small number of rows per page. We did not find such limits. One of the potential use cases is to update a large number of artifacts in bulk (status, additional fields/attributes). The transactions number could be one for 1,000 artifacts or two (if such a limit exists, for example, if the limit is 500 per page).

As far as I know, when using OSLC you have to update the artifacts individual.

But you can make that in parallel.

With our migration tool we were reaching about 20-40 artifact updates per second (containing of 3 steps: read artifact, update artifact, check artifact)