Dcm4chee-arc-5.5.1-mysql - trouble installing - have some questions

[Docjay]

Gunter,

    HI - I've gotten all the way down the wiki to the wildfly setup.

https://github.com/dcm4che/dcm4chee-arc-light/wiki/Installation#setup-wildfly

I am trying to use the .cli files in the '$DCM4CHEE-ARC/cli' folder, as in:

$WILDFLY_HOME/bin/jboss-cli.sh -c -f $DCM4CHEE_ARC/cli/add-data-source-<db>.cli

..but what returns is:  

[root@centest bin]# ./jboss-cli.sh -c -f /opt/dcm4chee-arc-5.x/cli/add-data-source-mysql.cli
'/opt/dcm4chee-arc-5.x/cli/add-data-source-mysql.cli' is assumed to be a command(s) but the commands to execute have been specified by another argument: [-f]
[root@centest bin]#

Is there actually a '-f' option to run with the 'jboss-cli.sh' script?  I look up the switches for it and it didn't show anything like it.  Anyway, I don't think the response I got back after I ran the command above was normal.

any ideas on what I'm doing wrong with this step?

I just went ahead and did it by hand with jboss-cli.sh anyway...on to another problem. 

I cannot deploy the 'dcm4chee-arc-ear-5.5.1-mysql.ear' file.  This is actually my biggest issue.

[standalone@localhost:9990 /] deploy /opt/dcm4chee-arc-5.x/deploy/dcm4chee-arc-ear-5.5.1-mysql.ear
{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"dcm4chee-arc-ear-5.5.1-mysql.ear\".\"dcm4chee-arc-service-5.5.1.jar\".component.ArchiveServiceImpl.START" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"dcm4chee-arc-ear-5.5.1-mysql.ear\".\"dcm4chee-arc-service-5.5.1.jar\".component.ArchiveServiceImpl.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
    Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
    Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.dcm4chee.arc.impl.ArchiveDeviceProducer.init() on org.dcm4chee.arc.impl.ArchiveDeviceProducer@645d122e
    Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.dcm4chee.arc.impl.ArchiveDeviceProducer.init() on org.dcm4chee.arc.impl.ArchiveDeviceProducer@645d122e
    Caused by: java.lang.reflect.InvocationTargetException
    Caused by: javax.enterprise.inject.CreationException
    Caused by: org.dcm4che3.conf.api.ConfigurationException: javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused]
    Caused by: javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused]
    Caused by: java.net.ConnectException: Connection refused"}}}}
[standalone@localhost:9990 /]

Thanks

Jamie

[Docjay]

okay, apparently I have something wrong with ApacheDS.  I have changed the port to '389', but maybe I don't have the admin user created in the right spot?  Can someone look  at my screenshot?

thanks

[gunterze]

You have to adjust $WILDFLY_HOME/standalone/configuration/dcm4chee-arc/ldap.properties to match your LDAP settings, particularly change

java.naming.security.principal=cn=admin,dc=dcm4che,dc=org

to

java.naming.security.principal=uid=admin,ou=system