You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fortress@directory.apache.org by Nuno Miquelina <Nu...@compta.pt> on 2019/07/29 12:08:45 UTC
Update procedure from 2.0.0 to 2.0.3
Hi,
What is the correct procedure to update a working installation from version 2.0.0 to 2.0.3.
Is necessary to guarantee that no OpenLDAP data is erased or the schema stays updated.
Thanks,
Nuno Miquelina
RE: Update procedure from 2.0.0 to 2.0.3
Posted by Nuno Miquelina <Nu...@compta.pt>.
Hi,
The procedure was very simple. Just define the fortress.properties and deploy.
I think, as the web project, the rest should also copy from the core project the fortress.properties file.
Best regards,
Nuno Miquelina
-----Original Message-----
From: Shawn McKinney <sm...@apache.org>
Sent: 29 de julho de 2019 14:59
To: fortress@directory.apache.org
Subject: Re: Update procedure from 2.0.0 to 2.0.3
> On Jul 29, 2019, at 8:54 AM, Nuno Miquelina <Nu...@compta.pt> wrote:
>
> But we should update the core and web library/applications also, correct?
> I will give feedback after the upgrade.
Yes, the Web should be drop-in replacement as well.
The Core depends. Is it a maven app — upgrade version and rebuild. Otherwise you’ll need to upgrade the jars manually.
And yes, please keep us in the loop.
—Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
Re: Update procedure from 2.0.0 to 2.0.3
Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 29, 2019, at 8:54 AM, Nuno Miquelina <Nu...@compta.pt> wrote:
>
> But we should update the core and web library/applications also, correct?
> I will give feedback after the upgrade.
Yes, the Web should be drop-in replacement as well.
The Core depends. Is it a maven app — upgrade version and rebuild. Otherwise you’ll need to upgrade the jars manually.
And yes, please keep us in the loop.
—Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
RE: Update procedure from 2.0.0 to 2.0.3
Posted by Nuno Miquelina <Nu...@compta.pt>.
Hi,
But we should update the core and web library/applications also, correct?
I will give feedback after the upgrade.
Thanks!
Nuno Miquelina
-----Original Message-----
From: Shawn McKinney <sm...@apache.org>
Sent: 29 de julho de 2019 13:42
To: fortress@directory.apache.org
Subject: Re: Update procedure from 2.0.0 to 2.0.3
> On Jul 29, 2019, at 7:08 AM, Nuno Miquelina <Nu...@compta.pt> wrote:
>
> What is the correct procedure to update a working installation from version 2.0.0 to 2.0.3.
> Is necessary to guarantee that no OpenLDAP data is erased or the schema stays updated.
Hello Nuno, welcome!
By your other message I’m assuming you are updating Apache Fortress Rest, is tat right?
If so, it’s a drop-in replacement of the .war. Of course any configuration elements you have in fortress.properties file will have to be moved into the new deployment as well.
All config elements in the configuration node, stored in OpenLDAP will be used by the new deployment, assuming you’re still pointing to it in the property file.
As for the data schema, it has changed very little since then. Specifically, one element has been added for managing UID/GID number sequencing for RFC2307 usage.
Since you are on 2.0, that isn’t a concern, although you will want to update the fortress.schema in OpenLDAP to use the latest.
Let us know if you have any problems with this upgrade, or if I’m misunderstood your question.
—Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org
Re: Update procedure from 2.0.0 to 2.0.3
Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 29, 2019, at 7:08 AM, Nuno Miquelina <Nu...@compta.pt> wrote:
>
> What is the correct procedure to update a working installation from version 2.0.0 to 2.0.3.
> Is necessary to guarantee that no OpenLDAP data is erased or the schema stays updated.
Hello Nuno, welcome!
By your other message I’m assuming you are updating Apache Fortress Rest, is tat right?
If so, it’s a drop-in replacement of the .war. Of course any configuration elements you have in fortress.properties file will have to be moved into the new deployment as well.
All config elements in the configuration node, stored in OpenLDAP will be used by the new deployment, assuming you’re still pointing to it in the property file.
As for the data schema, it has changed very little since then. Specifically, one element has been added for managing UID/GID number sequencing for RFC2307 usage.
Since you are on 2.0, that isn’t a concern, although you will want to update the fortress.schema in OpenLDAP to use the latest.
Let us know if you have any problems with this upgrade, or if I’m misunderstood your question.
—Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org