Conquest DICOM server as web server with Apache or WAMP

  • I tested wamp and apache2.2.6. I put the 3 webserver files (exe, ini and OCX) in c:\wamp\apache2\cgi-bin; for apache that would be "C:\Program Files\Apache Group\Apache2.2\cgi-bin\". I put the OCX as well is c:\wamp\www. For apache that would be: C:\Program Files\Apache Group\Apache2.2\htdocs.


    I did NOT edit any apache config! (wamp is default more closed). I then edited the dicom.ini in the cgi-bin directory file changing 127.0.0.1 into the servers real IP address (for me at home 192.168.1.115) - this should allow non-local access - like so (excerpt):


    Code
    [sscscp]
    MicroPACS = sscscp
    kFactorFile = c:\dicomserver\dicom.sql
    TruncateFieldNames = 10
    WebServerFor = 192.168.1.115
    TCPPort = 5678
    WebReadonly = 0
    WebCodeBase = http://192.168.1.115/
    WebScriptAddress = http://192.168.1.115/cgi-bin/dgate.exe
    WebMAG0Address = http://192.168.1.115/mag0


    Not that the dicom server itself default registers the OCX: use regsvr32 /u E:\dicomserver\webserver\ActiveFormProj1.ocx to uninstall it for testing the viewer on the local computer.


    Then the web page runs but the OCX will only install when I add http://192.168.1.115/ as trusted site to internet explorer and enable download of non-signed activeX controls.


    To test the share with the OCX open the viewer page and view source (shows as notepad with dgate[1]) and find the line with:


    codebase="http://192.168.1.115/ActiveFormProj1.ocx"


    Copy and paste later line into to your browser and it should ask to download the OCX.


    To test the DICOM share find the line with DCMFilelist and copy the first http: entry (until the *) in your browser like:


    http://192.168.1.115/cgi-bin/d…?....&dsize=0&compress=n4


    When pasted into my browser it downloads a DICOM file (with a weird filename and not with a DCM extension).


    If these both work and the viewer still does not run there must be a security problem.


    Marcel

  • Hi,


    I guess it would download the HTML contents if you would say yes. I cannot think of a solution on the browser side. Maybe it is possible to create a different named reference on apache so that the server is not called dgate.exe. On linux I just copied dgate (binary) to dgate.html in the server to circumvent this problem.


    Marcel

  • Hi,


    After searching a while, the firefox mystery is solved. The servers HTML pages start with content_type: application/html, while it should have been content-type: application/html or content-type: text/html.


    Solved in next version.


    Marcel

  • HI guys,


    I have successfully installed the web server component. Is there anyway of customising the GUI which says "Welcome to Conquest Dicom Server" ... perhaps changing the colour or the text etc?


    Regards,


    Gerry

  • Hi Marcel,


    Would i need the initial C++ files? Or can i work backwards from the executable?


    I would like to test this but my programming skills are somewhat unused in the last 3 years and any help you can offer would be greatly appreciated


    Regards,


    Gerry

  • Hi there.
    I installed the web component of conquest server and it works fine from intranet.
    My questions are: 1. how can you access the web server from outside of the network, e.g internet. Maybe using a router which routes port 80 to server? Do you need a real static IP ?
    2. Can you query through internet the conquest dicom server installed on a network PC if you correctly configure IPs and ports ?


    Thank you.

  • Hi,


    this is a web question really. I use a virtual host for port 22 (SSH) to tunnel to a router in my house with myentunnel to make a connection. You can also enable a virtual host for port 80 to open up web access from outside your home. The conquest web server will then be easy. As far as DICOM connectivity is concerned you need two tunnels:


    e.g.,
    client port 5678 to server: port 5678
    server port 104 to client port 104


    because a C-MOVE starts its own new connection.


    Marcel

  • Hey Marcel,


    I have the GUI viewer working internally. The .ocx loads fine and displays results. Is there a reason why it won't load successfully over the intenet? I know someone posed a quesion similar to this in the thread but I shouldn't have to open any other port in the firewall besides port 80, correct?


    |------------EXTERNAL ------------------| -------------------------INTERNAL ----------------|


    [pc] -------> { internet } --------> [firewall]--------> [conquest web / conquest server]

  • Hi,


    OCX's are notoriously untrusted nowadays. It will probably work (in IE) if you download the OCX and register it manually. Localy it works because ConquestDicomserver.exe registers the OCX itself. It only uses http, port 80.


    Marcel

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!