[ome-users] Upgraded but LDAP users can't pull their groups

Leon Kolchinsky lkolchin at gmail.com
Fri Aug 19 01:36:56 BST 2011


Thanks Josh/Mark,

OK, I'm not a java or python programmer, although I'm running quite a lot of
Java Apps on our servers.
I'm a Linux System Administrator.

The guy who was creating .jnlp files left and he was using a custom script
to sign and create .jnlp files.
I will forward your comments to our new Java programmer and try to find this
script.
I'll also ask to document this procedure and if all good I'll send it back
to the list ;)

Cheers,
Leon Kolchinsky



On Fri, Aug 19, 2011 at 03:06, Woodbridge, Mark R <
m.woodbridge at imperial.ac.uk> wrote:

> Hi,
>
> Yes, Josh is quite right, recent versions of OMERO.insight can be
> distributed using Web Start. It makes users don't have to install the
> clients manually, and makes updates much easier. There is a problem with
> OMERO.importer and Web Start since 4.3 which I haven't had time to
> investigate because we don't distribute it to our users any more.
>
> It's possible to produce a Web Start compatible tarball from the standard
> client distribution. Basically you need to do the following:
>
> Unpack the distribution (I used the Linux one)
> Put your server in the config/container.xml hostName setting
> Jar the config folder
> Un-jar and Re-jar the hibernate jar (for some reason the distributed
> version can't be signed)
> Sign all the jars
> Create jnlp files and add an icon for each
> Copy the resultant files to a webserver
>
> We actually distribute the jnlp files as jsps (i.e. the codebase attribute
> isn't hardcoded). We've also added a jnlp for activation.jar which is
> necessary for Java 5.
>
> The result of doing this is the following folder:
>
>
> http://cisbic.bioinformatics.ic.ac.uk/static/omero/omero-4.3.1-unsigned.tar.bz2
>
> To use this you need to modify the config/container.xml file, sign all the
> jars using jarsigner, and put all the files in a servlet container. It won't
> work without signing. In theory you could remove the jsp stuff and serve the
> jars from your existing OMERO.web server.
>
> It would be great if this could be built into the OMERO build process and
> distributed alongside the standalone versions.
>
> Mark.
>
> ________________________________________
> From: ome-users-bounces at lists.openmicroscopy.org.uk [
> ome-users-bounces at lists.openmicroscopy.org.uk] on behalf of Josh Moore [
> josh at glencoesoftware.com]
> Sent: 18 August 2011 07:27
> To: Leon Kolchinsky
> Cc: ome-users at lists.openmicroscopy.org.uk users
> Subject: Re: [ome-users] Upgraded but LDAP users can't pull their groups
>
> Hi Leon,
>
> On Aug 18, 2011, at 3:24 AM, Leon Kolchinsky wrote:
>
> > Hello Josh,
> >
> > Sure I would be able to test it when I get a new VM.
> > Where would I get the new OMERO version (with sync. support)?
>
> Great. It's available on the OME git:
>
>  #
>  #
> http://git.openmicroscopy.org/?p=ome.git;a=shortlog;h=refs/heads/bug/6501-ldap
>  #
>  git fetch origin bug/6501-ldap
>  git checkout -b bug/6501-ldap origin/bug/6501-ldap
>
> Remember, please, that this is test code, so use it only on a copy of your
> database. And thanks!
>
> > BTW,
> > If I'd like to create a JNLP versions of OMERO clients, like -
> insight.jnlp,
> > where would I find some manuals/step-by-step tutorials on that?
> > Does anyone on the list already did it?
>
> Though he can and may certainly speak up for himself, Mark Woodbridge from
> Imperial has done this previously. We applied a patch from him to make it
> easier:
>
>  http://trac.openmicroscopy.org.uk/ome/ticket/2635
>
> I don't have a current version of the JNLP he used, but I'm attaching a
> version that worked with 4.1.1 as a starting point.
>
> Cheers,
> ~Josh
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openmicroscopy.org.uk/pipermail/ome-users/attachments/20110819/8a5f26f7/attachment.html>


More information about the ome-users mailing list