7.1, portal-setup-wizard.properties and setup.wizard.enabled=false7.1, portal-setup-wizard.properties and setup.wizard.enabled=falsehttps://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1120879992024-03-28T08:22:54Z2024-03-28T08:22:54ZRE: 7.1, portal-setup-wizard.properties and setup.wizard.enabled=falseBen Collinshttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1123493662019-02-14T15:42:21Z2019-02-14T15:42:21ZHi all,<br /><br /><br />Apologies for not replying earlier - I wasn't getting notifications of your replies - so I want to start by saying thank you for your time !<br /><br />@Olaf - you are correct it's related to the in-memory database being used! I was testing all of this locally on my desktop using the HSQL database. In the "real world" we clearly don't use this but I was extrapolating the issue from local to that - incorrectly.<br /><br />I did raise a support ticket on this - https://issues.liferay.com/browse/LPS-89504 - and the upshot was that I found a change in the HSQL script between 6.2 and 7.1 GA3 in that GA3 starts adding users therefore ignoring my settings. Like you say Olaf - if there are settings in there at the start, the wizard won't overwrite them.Ben Collins2019-02-14T15:42:21ZRE: 7.1, portal-setup-wizard.properties and setup.wizard.enabled=falseOlaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1122883292019-02-11T08:17:29Z2019-02-11T08:17:29Z<html><head></head><body><blockquote>Alex Frolov<br>English is not my native language... and perhaps I have not quite accurately described. <img alt="emoticon" src="@theme_images_path@/emoticons/sad.gif"><br></blockquote>Don't worry, that's why were here, and you did right: Explain with more detail, when a previous answer didn't help.<br><br>I'm not sure I'm doing right when I mix both, your first and your last post here. But here are a couple of thoughts that you can use:<br><br>To fully work around the problems that you describe without reproducing:<br><br>Configure portal-ext.properties with<br><pre><code>company.default.web.id=example.com
default.admin.email.address.prefix=liferayadmin</code></pre>If you get the standard login dialog before you could set a password on your own, login with "liferayadmin@example.com" and password "test", then immediately change the password.<br><br>In the context of autoscaling (mentioned in your first post) and the database connection you configure here: Your database URL contains "localhost", hinting at an individual database per Liferay instance: An autoscaled cluster must share the same database. And "localhost" in this case doesn't make sense, as it's each machine's individual location, not a shared one. I'd expect to have a proper machine name/IP-address to connect to a common database. And note that you'll need a common Document Library storage as well as a common search index as well - but that'll have time until the current problems are solved.</body></html>Olaf Kock2019-02-11T08:17:29ZRE: 7.1, portal-setup-wizard.properties and setup.wizard.enabled=falseAlex Frolovhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1122874072019-02-11T08:01:10Z2019-02-11T08:01:10Z<html><head></head><body>English is not my native language... and perhaps I have not quite accurately described. <img alt="emoticon" src="@theme_images_path@/emoticons/sad.gif"><br><br>I'll try again.<br><br>I use MySQL as a database.<br>Create DB (<u><em>lportal</em></u>) and user <u><em>liferay</em></u>, grant all permission for <u>liferay </u>to <u><em>lportal</em></u>.<br><br>Unpack <em>liferay-ce-portal-tomcat-7.1.2-ga3-20190107144105508.7z</em> to /opt<br><br>Create <strong>portal-ext.properties </strong>and put in /opt/liferay-ce-portal-7.1.2-ga3/<strong>:</strong> <pre><code>jdbc.default.driverClassName=com.mysql.jdbc.Driver
jdbc.default.url=jdbc:mysql://localhost/lportal?characterEncoding=UTF-8&amp;dontTrackOpenResources=true&amp;holdResultsOpenOverStatementClose=true&amp;useFastDateParsing=false&amp;useUnicode=true
jdbc.default.username=liferay
jdbc.default.password=***************
locales.enabled=ru_RU,en_US</code></pre>Start tomcat first time.<br>Open in browser page IP_PORTAl:8080<br>After a while, the "Basic Configuration" window appears.<br>Check settings and press "Finish Configuration".<br><br>After restart tomcat, I get a standard login window to the portal and it is not possible to set an administrator password.<br><br>Stop tomcat.<br>Edit <strong>portal-setup-wizard.properties</strong> <br>Set <u><em>setup.wizard.enabled=true <br></em></u>Start tomcat.<br><br>This time in the "Basic configuration" database connection fields are not editable.<br>Press "Finish Configuration".<br><br>Restart tomcat. Browser page left open.<br><br>After some time appear page with license agreement, and after it acceptance, I was able to set admin password/</body></html>Alex Frolov2019-02-11T08:01:10ZRE: 7.1, portal-setup-wizard.properties and setup.wizard.enabled=falseOlaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1122718842019-02-08T07:39:56Z2019-02-08T07:39:56Z<blockquote>Ben Collins<br /><br />In 6.2 (and I am sure also in 7.1 GA1) we were able to preset the<br /> properties for a Portal instance through portal-ext.properties and not<br /> be presented with the setup wizard on firing up the site. This created<br /> us a custom admin account and we were all good to go. To do this we'd<br /> use the following: ...<br /></blockquote>I'm not sure I fully understand...<br />The configuration values you quote are values that would go into the database upon <em>first start</em>. However, you already have a running instance and with autoscaling you'd connect to the same database anyways, no newly started system would create another instance (company), but just continue to run on the existing one. <br />In other words, I'd expect you to be able to hardcode setup.wizard.enabled=false once you have your database ready. A new autoscaled server should behave exactly like an existing server that restarts - there's no new instance data created, just an additional server accessing the same database.<br /><br />Edit: After writing this, it seems there's something missing in your configuration: The database connection. If you don't configure the database that you're going to use, Liferay will use its default hsql installation. This is not what you want. Inspect portal-ext.properties or portal-setup-wizard.properties for the required values, or take them from Alex's answer here (or use a JDBC connection pool, if you don't want username/password here). Once your new autoscaled server connects to the same database, it will show the same data as every other server that connects to the same database.<br /><br />Note: It's not only the same database, it's also the same Elasticsearch server as well as a common Document Library storage that you need. But that's then all property of a correct cluster setup.Olaf Kock2019-02-08T07:39:56ZRE: 7.1, portal-setup-wizard.properties and setup.wizard.enabled=falseAlex Frolovhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1122710392019-02-08T07:02:15Z2019-02-08T07:02:15Z<html><head></head><body>I had a similar problem. (liferay-ce-portal-tomcat-7.1.2-ga3)<br><br>I got this solution:<br><br>Create such files:<br><strong>portal-ext.properties:</strong><br><pre><code>jdbc.default.password=************
jdbc.default.username=************
jdbc.default.url=jdbc:mysql://localhost/lportal?characterEncoding=UTF-8&amp;dontTrackOpenResources=true&amp;holdResultsOpenOverStatementClose=true&amp;useFastDateParsing=false&amp;useUnicode=true
jdbc.default.driverClassName=com.mysql.jdbc.Driver
locales.enabled=ru_RU,en_US
</code></pre><strong>portal-setup-wizard.properties</strong><br><pre><code>admin.email.from.address=admin@*******.**
admin.email.from.name=Admin
company.default.locale=ru_RU
company.default.web.id=*******.**
default.admin.email.address.prefix=**********
liferay.home=/opt/liferay-ce-portal-7.1.2-ga3
setup.wizard.add.sample.data=on
setup.wizard.enabled=true</code></pre>Start tomcat<br>Setup Wizard starts<br>Click on Finish Configuration<br>Restart tomcat<br>After the reboot, a page with a license agreement appeared. Took it. There was a page with a password for the administrator and a security question.</body></html>Alex Frolov2019-02-08T07:02:15Z7.1, portal-setup-wizard.properties and setup.wizard.enabled=falseBen Collinshttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1120879982019-01-22T15:09:13Z2019-01-22T15:09:13Z<p>Looking for some advice here for setting up a site in 7.1 GA2+.</p>
<p> </p>
<p>In 6.2 (and I am sure also in 7.1 GA1) we were able to preset the
properties for a Portal instance through portal-ext.properties and not
be presented with the setup wizard on firing up the site. This created
us a custom admin account and we were all good to go. To do this we'd
use the following:</p>
<p>
<em>setup.wizard.enabled=false</em></p>
<p>
<em>company.default.name=XXXXX<br />
company.default.web.id=XXXXX<br /> company.default.locale=XXXXX</em></p>
<p>
<em># default admin account<br /> default.admin.password=XXXX<br />
default.admin.screen.name=XXXXX<br />
default.admin.email.address.prefix=XXXXX<br />
default.admin.first.name=XXXX<br /> default.admin.last.name=XXXX</em></p>
<p>
<em>admin.email.from.name=XXXXX<br /> admin.email.from.address=XXXX</em></p>
<p> </p>
<p>We're upgrading to 7.1 GA2 and this feature doesn't seem to be
available anymore. </p>
<p>If I set setup.wizard.enabled=false, it skips the wizard, but also
doesn't apply my changes (the portal stays as Liferay, there's no
custom admin account and I have to login with test/test). The
properties ARE saved as I can see them in the system config UI.</p>
<p>If I then set setup.wizard.enabled=true, the wizard shows, preset
with my values, though it won't take my preset password. It does
create the portal-setup-wizard.properties file and resets
setup.wizard.enabled=false which is nice. I can then use my custom
admin account, etc.</p>
<p>The problem then lies in the fact that we deploy to the AWS cloud
with autoscaling enabled. The upshot is that if I redeploy my code OR
autoscaling kicks in the portal-setup-wizard.properties file is lost
because it's not part of my build and we are then presented with the
wizard once more. What's worse is that if this was due to autoscaling
and we didn't cat