Manage servoy via web (SSL)

We have servoy server installed on a linux box that does not have x-windows, so management has to be via the servoy-admin web interface. Whilst it is possible to import a solution via the web interface, it doesnt seem possible to unload/delete/disable one? Have I missed something? Can we control access to solutions on our server through the web admin interface or must we use developer (which implies copying the entire repository across to our hosting enrivonment whenever we make a change).

Also, the default connectivity to the admin console is via http://server.com:8080/servoy-admin which is not secure. What is the simplest way to set this up to use SSL? We already have a valid certificate on the server for this purpose.
Al.

I am not familiar with ssl stuff so I can’t answer you on that one.

But for the management of solutions you have the solutions page to activate a (not only the last) release.

BTW this is all perfectly described in the the pdf (or printed) manuals…

Hope this helps

Hi Marcel, you must have different manuals? ;-)

The ones I’ve read tell you how to import, activate androll back a solution. I believe Alb is asking if it is possible to unload/delete/disable via server-admin. You can do this in developer, then shift the repository to the server. But can it be done directly on the server-admin pages?

I read that it’s possible to share a repository between developer and server, but this means that sequences are also shared, so this won’t work where you are actively developing.

How do other folks manage this?

OK, if that’s the case I consider this to be a language thing. What is the difference between ‘disable’ and ‘de-activate’?

Sorry for the misunderstanding :oops: I just can’t find anywhere in the manual where it tells me how to unload or delete a solution via server-admin. I can roll back, but there still has to be an active version for each solution in the repository. I’ve failed to find a way to remove or disable an entire solution.

ok, deleting a solution or release must be done via developer. Think for security reasons…

Not sure what those security reasons could be, since Servoy-Admin is already both powerful and potentially destructive.

There are times when it would be useful to be able to use Servoy-Admin to ‘clean-up’ a remote installation and remove solutions that are no longer needed. Not really a priority but would be interesting to know why this is not possible.

Graham Greensall
Worxinfo Ltd

Well, it is certainly potentially destructive the way it is now. So, when I give my client access to web admin I don’t mind him to roll back a solution. But, the way I see it, I do mind him to delete a solution…

Reading this thread you could conclude that there is a need for a more fine grained security model in the admin pages and more options for disabling (hiding if you will) and/or removing a solution.
Maybe a possibility to assign groups of users to certain solutions for them to manage (not delete), maybe even their connections/transactions/locks.
Only an admin could import/disable(hide)/delete a solution and has access to all server settings.

Disabling could be a special flag that makes it act like modules. I.e. they are not shown anymore in the open solution dialog. Truly disabling a module used in a solution would not be desirable.

Just an idea.

Just to add to this: As of 3.0, all solutions you have active in your repository will be published as a webclient as well and users can start them as a webclient.

I would like to be able to flag solutions as “Webclient enabled: true/false”, because a lot of solutions will not work, without modification (thinking dialogs and beans for example) in 3.0. I’d like to upgrade the server to 3.0, but not alter all my existing solutions yet.

Also, in the future, I might want to have some solutions available only as smart client, for example because of certain things that just cannot be done in the WebClient (yet…).

Paul

Guys, if you haven’t done so yet, please don’t forget to file this as a request…

alb:
…the default connectivity to the admin console is via http://server.com:8080/servoy-admin which is not secure. What is the simplest way to set this up to use SSL? We already have a valid certificate on the server for this purpose.

Enable ssl inside the apache tomcat config