Request to specific peer

[ruben-cruz]

First of all congrats on the good job with this tool.

I have just a small question regarding the DICOM peers... I know that it's possible to configure multiple DICOM peers on the config file like this:

config.peers = [
  {
    aet: 'AET1',
    ip: 'localhost',
    port: 1,
  },
{
    aet: 'AET2',
    ip: 'localhost',
    port: 2,
  }
];

But, it's possible to make p.e. QIDO or WADO resquests for a specific peer of the configured list? For example: "http://localhost:5000/aets/AET1/rs/studies"?

[knopkem]

Hi, I'm not aware that differentiating between multiple AETs over one defined Endpoint is part of dicomweb. I think the idea is that each dicomweb provider stands for one AET, thus you would need to have multiple instances of providers. You can already do this:

• configure e.g. two dicomweb-proxy servers with different ports, e.g. "http://localhost:5000/rs/studies" (configured with one peer AET1) and "http://localhost:5001/rs (peer: AET2)
• host the js static files with e.g. nginx (e.g. port 80)
• use a proxy (nginx, haproxy) to route requests :
• http://localhost:80/aet1/rs/studies --> "http://localhost:5000/rs/studies"
• http://localhost:80/aet2/rs/studies --> "http://localhost:5001/rs/studies" However your dicomweb viewer also needs to be able to differentiate AETs (e.g. user selects which AET he/she wants to search)

[ruben-cruz]

@knopkem how can I configure more than one dicomweb-proxy servers? Do I have to create multiple config default.js files or it can be done with just one config file?

[knopkem]

You should checkout the proxy again in another folder and use isolated proxies. Using the same project with two differently configured instances is not possible (without changes)

[ruben-cruz]

@knopkem ok. Thanks for all your help.