docker images of ACE audit ?

[Geoffrey Brimhall]

Are there docker images that have been made of ACE audit ?

Was looking on dockerhub, couldn't find anything.

[Michael Ritter]

Hi Geoffrey,

At the moment there are no docker images for the ACE Audit Manager. I've played around a bit in making one for the Integrity Management Service but haven't really had too much time to get it functioning properly as I don't have much experience with Docker.

I do have some dev work for ACE coming up soon; if it would be useful I can take a look at creating some Docker images and getting them up on dockerhub for the ACE services.

-Mike

[Geoffrey Brimhall]

Turned out to be easier than I thought to get a docker image of ace-audit-manager created.

Check out https://github.com/ualibraries/ace-audit-manager

It's looking like getting the IMS running in docker will be harder cause I can't find good installation instructions. Are there some floating around somewhere ?

[Michael Ritter]

Hi Geoffrey,

The IMS Documentation is sadly lacking... it looks like there are very brief instructions on installing the IMS on the ACE Wiki:
https://wiki.umiacs.umd.edu/adapt/index.php/Ace:IMS_Installation

I can expand on them a bit from my experience migrating the IMS to newer versions of Glassfish (I've tried other J2EE application servers without much success, though maybe it would be different now that I have more experience with the IMS).

* mysql-server

* smtp-server

* j2ee application server (preferably Glassfish)

* ace-ims.ear (which does not look like it is easily available for download so it needs to be built from source. I'll have to go through and upload the artifact for each release)

You'll then need to start your Glassfish server and create a JDBC Connection Pool, JDBC Resource, and a Java Mail Resource. When setting these up, the jndi-name is particularly important because it is the lookup name that the IMS uses.

The JDBC Connection Pool takes the following fields:
* res-type: java.sql.Driver

* driver-classname: com.mysql.jdbc.Driver

* user: ${YOUR_USER}

* password: ${YOUR_PASSWORD}

* url: jdbc:mysql://${MYSQL_HOST}/${IMS_DB}

Then the JDBC Resource:

* jndi-name: ace-ims

I have in my notes to use the connection pool above.. which I assume means you associate the resource with the connection pool.

Last the Java Mail Resource:
* host: ${SMTP_HOST}
* jndi-name: mail/ace-ims
* from: ${SMTP_FROM}

* user: ${SMTP_USER}

Our from and user fields are set to a local user on the machine. So 'us...@umiacs.umd.edu' and 'user' respectively.

Once the resources are set up, you just need to deploy the ace-ims.ear on the application server.

Most of the time I do these through Glassfish's admin interface; I'm sure you can do it through the as-admin command as well. I should add that one of the newer versions of Glassfish I was unable to create the jdbc connection pool as it was throwing an exception and prevented my from deploying the IMS on that version (I think 4.1.2).

-Mike

[Mike Ritter]

Oh, I almost forgot:

* The default port for the admin interface in Glassfish is 4848

* The default port for http is 8080

* After deploying the IMS you can check http://your-glassfish-server:8080/ace-ims/IMSWebServer.wsdl

[Geoffrey Brimhall]

After two days of trying to get ace-ims working on wildfly and payara(aka glassfish), only one I was able to have success with was glassfish using just about exactly the directions you gave.

I *think* I have enough to try and create a docker image of ace-ims now using glassfish, will announce on this mailinglist when done.

What I'm trying to figure out now is how ace-am works in peer mode so it can compare duplicate copies of a collection. This was our last criteria that needed to be working.