[midPoint] Installing MySQL Driver

Ivan Noris ivan.noris at evolveum.com
Thu Oct 18 09:00:14 CEST 2018


Hi Eric,

good point, I have just added a note to
https://wiki.evolveum.com/display/midPoint/MidPoint+Home+Directory

I have only used this with stand-alone deployment, otherwise (= in the
old midPoints) I was using Tomcat's lib/ directory. So I'm not sure if
that would work for non-standalone too.

Best regards,

Ivan

On 17. 10. 2018 19:02, Solberg, Eric wrote:
>
> Gotcha – I probably didn’t try that. I’ll add that to my list of
> things to try when I come back to this. This is another thing you may
> want to make clear in the installation documentation –
>
>  
>
> You’ll note that it isn’t mentioned here:
>
> https://wiki.evolveum.com/display/midPoint/Installing+MidPoint+Server
>
>  
>
> This one shows the directory structure of midpoint home, but doesn’t
> mention lib:
>
> https://wiki.evolveum.com/display/midPoint/MidPoint+Home+Directory
>
>  
>
> Also not mentioned here:
>
> https://wiki.evolveum.com/display/midPoint/Repository+Configuration
>
>  
>
> This one does mention where to put the driver- the wrong location!
>
> “… insert driver (for instance mysql-connector-java-5.1.30-bin.jar) on
> classpath either in deployed midpoint */webapps/midPoint/WEB-INF/lib
> or in */apache-tomcat/lib”
>
> https://wiki.evolveum.com/display/midPoint/MySQL
>
>  
>
> Anyway I’m up and running now, and when I come back to this I should
> be able to clean up and get my docker-based repeatable deploy working
> as I had hoped.
>
>  
>
> Thanks,
>
> Eric
>
>  
>
> *From: *midPoint <midpoint-bounces at lists.evolveum.com> on behalf of
> Pavol Mederly <mederly at evolveum.com>
> *Reply-To: *midPoint General Discussion <midpoint at lists.evolveum.com>
> *Date: *Wednesday, October 17, 2018 at 8:55 AM
> *To: *<midpoint at lists.evolveum.com>
> *Subject: *Re: [midPoint] Installing MySQL Driver
>
>  
>
> Hello Eric,
>
> but I was referring to _/opt/midpoint/*var*/lib_ directory (not
> _/opt/midpoint/lib_), assuming midpoint home is _/opt/midpoint/var_.
> This should work, as far as you use embedded Tomcat (which is now the
> default way of running midPoint).
>
> But of course, you can modify midpoint.war; that's also a way.
>
> Best regards,
>
>
> Pavol Mederly
> Software developer
> evolveum.com
>  
>
> On 17.10.2018 17:35, Solberg, Eric wrote:
>
>     Hi Pavol,
>
>      
>
>     I’m pretty sure this is the first thing I tried. But I think we
>     may not be talking about the same thing. I’m talking about the
>     standard install for Midpoint 3.8. In this install, the lib file
>     in midpoint home contains:
>
>     /opt/midpoint/lib:
>
>       * midpoint.war
>       * ninja-3.7.2.jar
>       * ninja.jar
>
>      
>
>     In this approach, following the installation docs, everything is
>     self-contained in the midpoint.war file, right? I don’t think any
>     java classes are referenced external to this war that I could tell
>     at least.
>
>     Putting the driver jar file here didn’t work- and I couldn’t see
>     anywhere where the classpath was being set to look at the files in
>     this directory.
>
>     On the other hand, inside of midpoint.war there is a WEB-INF/lib
>     directory that contains many jars, that are on the classpath at
>     runtime. Putting the driver in that directory did work. It’s just
>     an awkward approach to in modify a distribution war file to add
>     additional jars to it. It seems the instructions that deal with
>     drivers, and your discussion below, are based on a different
>     installation approach. Of course, I may be totally confused as I
>     was chasing down many issues at once.
>
>      
>
>     Thanks for the feedback.
>
>      
>
>     *From: *midPoint <midpoint-bounces at lists.evolveum.com>
>     <mailto:midpoint-bounces at lists.evolveum.com> on behalf of Pavol
>     Mederly <mederly at evolveum.com> <mailto:mederly at evolveum.com>
>     *Reply-To: *midPoint General Discussion
>     <midpoint at lists.evolveum.com> <mailto:midpoint at lists.evolveum.com>
>     *Date: *Wednesday, October 17, 2018 at 12:06 AM
>     *To: *<midpoint at lists.evolveum.com>
>     <mailto:midpoint at lists.evolveum.com>
>     *Subject: *Re: [midPoint] Installing MySQL Driver
>
>      
>
>     Hello Eric,
>
>     you can put the driver into the /lib/ directory of the midPoint home.
>
>     Like here:
>     https://spaces.at.internet2.edu/display/MID/External+repository+demo
>     (this is a part of the TIER midPoint dockerization
>     <https://spaces.at.internet2.edu/display/MID/Dockerized+midPoint>).
>
>     Note that some of the featured described there are specific to
>     upcoming 3.9 version, but this driver placement should work for
>     3.8 as well.
>
>     Best regards,
>
>     Pavol Mederly
>
>     Software developer
>
>     evolveum.com
>
>     On 16.10.2018 18:41, Solberg, Eric wrote:
>
>         I've been playing with the Midpoint demo and now want to get a real installation set up.
>
>          
>
>         I'm using Google Cloud Platform and have made the demo work in a VM on the compute engine, and in a Kubernetes cluster. I've made both the binary install and the Docker install work. All good there.
>
>          
>
>         The instructions seem to be incomplete or unclear on installation of the MySQL driver. Where to put the driver so it is on the class path? Or how to modify the classpath to include it? After a lot of trial and error, the approach I found that worked was to add the driver jar to midpoint.war - and specifically adding it without compression (0 flag), using this command:
>
>         jar uf0 ${MP_DIR}/lib/midpoint.war WEB-INF/lib/mysql-connector-java-8.0.12.jar
>
>          
>
>         This seems to have worked (though I'm having another issue I'll ask about separately). 
>
>          
>
>         Is there a better way?
>
>          
>
>          
>
>         _______________________________________________
>
>         midPoint mailing list
>
>         midPoint at lists.evolveum.com <mailto:midPoint at lists.evolveum.com>
>
>         http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
>     _______________________________________________ midPoint mailing
>     list midPoint at lists.evolveum.com
>     <mailto:midPoint at lists.evolveum.com>
>     http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
>
>
>     _______________________________________________
>
>     midPoint mailing list
>
>     midPoint at lists.evolveum.com <mailto:midPoint at lists.evolveum.com>
>
>     http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
> _______________________________________________ midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint

-- 
Ivan Noris
Senior Identity Engineer
evolveum.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20181018/83ff3afa/attachment.htm>


More information about the midPoint mailing list