Cant change AETitle for dcm4chee-arc device and do study searches on the ui2

[Stephen Adler]

I've just installed dcm4chee-arc 5.22.1. This is a fresh install. I'm using wildfly 17.0.1-Final, but I'm getting the same error with wildfly 19.0.0-Final. The problem is summarized in the two screen shots. I've changed the AETitle of the dcm4chee-arc device to BOO. Yet, when I go to the navigation window to search for studies, the 'Web app service' field does not give me an option to choose the BOO AETitle. It shows the default DCM4CHEE AETitle for dcm4chee-arc device.... I thought this problem was due to an upgrade from 5.18.1 to 5.22.1, and since one needs to edit the upgrade ldif ldap files if you've changed the default AETitle for dcm4chee-arc, I thought the problem was in my not properly editing the ldif files. Well, this is a fresh install of 5.22.1. I get this problem with both chrome and firefox. I cleared the all caches in both browsers as best I knew how. Any ideas? Is there something I can further test?

[Shefki Esadi]

Hi,

well the "WEBAPPSERVICE" drop-down shows the webaps not the AETs (We don't use in the new study page AET-s directly anymore instead we use WebApplications), you have to change the webApp name, You can do that by going to Configuration->dcm4chee-arc(or the device of your own archive if you have another one)->Extensions->Device Extension->Child Object->Web Applications.

Best Regards
Shefki Esai

[Gunter Zeilinger]

https://github.com/dcm4che/dcm4chee-arc-light/releases/tag/5.19.1

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

--

You received this message because you are subscribed to the Google Groups "dcm4che" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/b24cf1b2-6d6b-4deb-a5cd-b483714b7fc8%40googlegroups.com.

[Gunter Zeilinger]

configuration of http/https connections is no longer required:

https://github.com/dcm4che/dcm4chee-arc-light/releases/tag/5.20.0

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

[Stephen Adler]

Thanks everyone for your replies. I'm still confused. Basically I need to change the AETitle of the dcm4chee-arc, but in doing so, I can't query the archived studies. At least changing the AETitle in the way I did in 5.18.1. I don't necessarily need to change the name of the web app, I just need to be able to query the studies page the way I did in 5.18.1 with the new AETitle set for the dcm4chee-arc archive. I'll poke around a bit more in the web application forms, but if there is an updated set of instructions on how to change the AEtitle for dcm4chee-arc and still be able to query the archived studies using the web interface that would be great.

To be clear, when I change the AETitle of the dcm4chee-arc from DCM4CHEE to BOO, and then I select the DCM4CHEE web app to do the query, I get an error 500. So there must be some other place I need to change an AETitle. If I don't touch the AETitle from the default configuration, the study queries work fine from the UI when I select the DCM4CHEE webapp.

Error detail
javax.ws.rs.WebApplicationException: HTTP 404 Not Found at org.dcm4chee.arc.qido.QidoRS.getApplicationEntity(QidoRS.java:567) at org.dcm4chee.arc.qido.QidoRS.newQueryContext(QidoRS.java:516) at org.dcm4chee.arc.qido.QidoRS.search(QidoRS.java:403) at org.dcm4chee.arc.qido.QidoRS.searchForStudies(QidoRS.java:219) at org.dcm4chee.arc.qido.QidoRS$Proxy$_$$_WeldClientProxy.searchForStudies(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:138) at org.jboss.resteasy.core.ResourceMethodInvoker.internalInvokeOnTarget(ResourceMethodInvoker.java:517) at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTargetAfterFilter(ResourceMethodInvoker.java:406) at org.jboss.resteasy.core.ResourceMethodInvoker.lambda$invokeOnTarget$0(ResourceMethodInvoker.java:370) at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:355) at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:372) at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:344) at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:317) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:440) at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4(SynchronousDispatcher.java:229) at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:135) at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:355) at org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:138) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:215) at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:227) at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) at javax.servlet.http.HttpServlet.service(HttpServlet.java:791) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129) at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:173) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at io.opentracing.contrib.jaxrs2.server.SpanFinishingFilter.doFilter(SpanFinishingFilter.java:55) at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61) at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131) at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:68) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748)

To unsubscribe from this group and stop receiving emails from it, send an email to dcm...@googlegroups.com.

[Gunter Zeilinger]

Did you adjust

Web Service Path	string	HTTP Path of the services of the Web application (dcmWebServicePath)
AE Title	string	AE title of Network AE associated with this Web Application (dicomAETitle)

of the Web application configuration accordingly?

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/a2ccc799-5fde-4095-8a69-d80b9ed9f680%40googlegroups.com.

[Stephen Adler]

Thanks gunterze,

that was the missing field I had to change. So in 5.18.1 I only had to change one field, while in 5.22.1 I had to change 2 fields. I've summarized the steps below for whomever falls

into this same hole as I did when changing the AETitle of the main network AE. I also figured out that you can leave the original dcm4chee-arc AETitle alone and just clone the network AE and give the clone a new AETitle.

(See method #2 below). So the design question is, if one needs to customize the AETitle of the main dcm4chee-arc archive network AE, should one change the DCM4CHEE default

AETitle using the 2 step method #1, or clone the original DCM4CHEE network AE and change the cloned AETitle?

------------------- This should be added to some dcm4chee-arc document wiki someplace ---------

The following are the steps to change the AETitle in dcm4chee-arc 5.22.1

method #1 surf to...

devicelist->dcm4chee-arc->child objects[Network AEs][DCM4CHEE]->Attributes->AE Title

edit AE Title field with new AETitle and save
example: Change default

    DCM4CHEE

to

   NEW_AE_TITLE

click save

next surf to...

devicelist->dcm4chee-arc->extensions[device extensions][edit extensions]->Child Objects[Web Applications][DCM4CHEE]->Web Service Path
Edit web service path and change AETitle of path to new AETitle

example: Change default

   /dcm4chee-arc/aets/DCM4CHEE/rs

to


   /dcm4chee-arc/aets/NEW_AE_TITLE/rs

Click save


Method #2, just clone the dcm4chee object and give the clone a new AETitle.

surf to...
devicelist->dcm4chee-arc->Child Objects[Network AEs][DCM4CHEE]

Click on the 'Clone this Network AEs Part'

In the attributes section edit the new AE Title

example: Edit default AE Title

    DCM4CHEE

to

   NEW_AE_TITLE

Click save

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/a2ccc799-5fde-4095-8a69-d80b9ed9f680%40googlegroups.com.