<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>LPS-97547 Remove legacy per portal instance properties configuration …</title>
  <link rel="self" href="https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=118247621" />
  <subtitle>LPS-97547 Remove legacy per portal instance properties configuration …</subtitle>
  <id>https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=118247621</id>
  <updated>2026-06-12T14:46:36Z</updated>
  <dc:date>2026-06-12T14:46:36Z</dc:date>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118278753" />
    <author>
      <name>Olaf Kock</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118278753</id>
    <updated>2020-01-15T10:05:05Z</updated>
    <published>2020-01-15T10:05:05Z</published>
    <summary type="html">&lt;div class="quote-title"&gt;jay kumar:&lt;/div&gt;&lt;blockquote&gt;&lt;br /&gt;Actually we wanted to store each customers data separate, also if we get new customer than we can design its separate lportal locally and then push it to production, binding instance with that lportal.&lt;br /&gt;&lt;/blockquote&gt;&lt;br /&gt;On top of what was written above: This is not how sharding &lt;em&gt;ever&lt;/em&gt; worked. You could &lt;em&gt;never&lt;/em&gt; arbitrarily bind different shards to different portals and move them around. A shard always belonged to a single portal. And it never was guaranteed to have the data of one instance exclusively and completely. In order to restore a portal from backup, you always needed all of the shards to be restored together.&lt;br /&gt;Trust David and me: You don&amp;#39;t want shards. If you want to strictly separate customers from each other, separating them in individual databases doesn&amp;#39;t grant any security, as they&amp;#39;re all accessed from the same JVM anyway. If you want to strictly separate them, run different servers.</summary>
    <dc:creator>Olaf Kock</dc:creator>
    <dc:date>2020-01-15T10:05:05Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118274725" />
    <author>
      <name>jay kumar</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118274725</id>
    <updated>2020-01-15T06:06:39Z</updated>
    <published>2020-01-15T06:06:39Z</published>
    <summary type="html">&lt;div class="quote-title"&gt;David H Nebinger:&lt;/div&gt;&lt;blockquote&gt;&lt;br /&gt;Sharding was removed because it was a total PITA and has way too many complications...&lt;br /&gt;&lt;br /&gt;Backups, for example. Sure you can take snapshots of all of the shards, but trying to get a working restore done so everything is in sync? Not a fun trip.&lt;br /&gt;&lt;br /&gt;Forget about sharding, it is a nightmare best left forgotten.&lt;/blockquote&gt;&lt;br /&gt;&amp;lt;p&amp;gt;Actually we wanted to store each customers data separate, also if we get new customer than we can design its separate lportal locally and then push it to production, binding instance with that lportal.&amp;lt;/p&amp;gt;</summary>
    <dc:creator>jay kumar</dc:creator>
    <dc:date>2020-01-15T06:06:39Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118274705" />
    <author>
      <name>jay kumar</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118274705</id>
    <updated>2020-01-15T06:06:16Z</updated>
    <published>2020-01-15T06:06:16Z</published>
    <summary type="html">&lt;div class="quote-title"&gt;Christoph Rabel:&lt;/div&gt;&lt;blockquote&gt;&lt;br /&gt;Sorry, but sharding is gone. It cannot be done anymore. Well, some databases support sharding, but I would tread very careful here. It adds a lot of complexity, but what are the gains?&lt;br /&gt;The question is: Why do you want sharding? Do you really need it?&lt;/blockquote&gt;Actually we wanted to store each customers data separate, also if we get new customer than we can design its separate lportal locally and then push it to production, binding instance with that lportal.&amp;lt;</summary>
    <dc:creator>jay kumar</dc:creator>
    <dc:date>2020-01-15T06:06:16Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118275584" />
    <author>
      <name>Olaf Kock</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118275584</id>
    <updated>2020-01-14T08:45:38Z</updated>
    <published>2020-01-14T08:45:38Z</published>
    <summary type="html">&lt;div class="quote-title"&gt;jay kumar:&lt;/div&gt;&lt;blockquote&gt;&lt;br /&gt;&amp;lt;p&amp;gt;Actually we wanted to store each customers data separate, also if we get new customer than we can design its separate lportal locally and then push it to production, binding instance with that lportal.&amp;lt;/p&amp;gt;&lt;/blockquote&gt;Sharding was removed because it was a total PITA and has way too many complications...&lt;br /&gt;&lt;br /&gt;Backups, for example. Sure you can take snapshots of all of the shards, but trying to get a working restore done so everything is in sync? Not a fun trip.&lt;br /&gt;&lt;br /&gt;Forget about sharding, it is a nightmare best left forgotten. &lt;br /&gt;(credits: see above ;) )</summary>
    <dc:creator>Olaf Kock</dc:creator>
    <dc:date>2020-01-14T08:45:38Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118272947" />
    <author>
      <name>jay kumar</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118272947</id>
    <updated>2020-01-14T06:55:42Z</updated>
    <published>2020-01-14T06:55:42Z</published>
    <summary type="html">&amp;lt;p&amp;gt;Actually we wanted to store each customers data separate, also if we get new customer than we can design its separate lportal locally and then push it to production, binding instance with that lportal.&amp;lt;/p&amp;gt;</summary>
    <dc:creator>jay kumar</dc:creator>
    <dc:date>2020-01-14T06:55:42Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118272927" />
    <author>
      <name>jay kumar</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118272927</id>
    <updated>2020-01-14T06:54:58Z</updated>
    <published>2020-01-14T06:54:58Z</published>
    <summary type="html">&amp;lt;p&amp;gt;Actually we wanted to store each customers data separate,&amp;amp;nbsp; also if we get new customer than we can design its separate lportal locally and then push it to production, binding instance with that lportal.&amp;lt;/p&amp;gt;</summary>
    <dc:creator>jay kumar</dc:creator>
    <dc:date>2020-01-14T06:54:58Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118268029" />
    <author>
      <name>David H Nebinger</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118268029</id>
    <updated>2020-01-13T14:30:22Z</updated>
    <published>2020-01-13T14:30:22Z</published>
    <summary type="html">Sharding was removed because it was a total PITA and has way too many complications...&lt;br /&gt;&lt;br /&gt;Backups, for example. Sure you can take snapshots of all of the shards, but trying to get a working restore done so everything is in sync? Not a fun trip.&lt;br /&gt;&lt;br /&gt;Forget about sharding, it is a nightmare best left forgotten.</summary>
    <dc:creator>David H Nebinger</dc:creator>
    <dc:date>2020-01-13T14:30:22Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118267360" />
    <author>
      <name>Christoph Rabel</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118267360</id>
    <updated>2020-01-13T13:33:10Z</updated>
    <published>2020-01-13T13:33:10Z</published>
    <summary type="html">Sorry, but sharding is gone. It cannot be done anymore. Well, some databases support sharding, but I would tread very careful here. It adds a lot of complexity, but what are the gains?&lt;br /&gt;The question is: Why do you want sharding? Do you really need it?</summary>
    <dc:creator>Christoph Rabel</dc:creator>
    <dc:date>2020-01-13T13:33:10Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118262800" />
    <author>
      <name>jay kumar</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118262800</id>
    <updated>2020-01-13T06:27:30Z</updated>
    <published>2020-01-13T06:27:30Z</published>
    <summary type="html">Thank you so much Christoph Rabel , it is very helpful.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Can you please also guide me also on how to implement database sharding, as this feature is removed Now.&lt;br /&gt;&lt;br /&gt;How can we achieve this?</summary>
    <dc:creator>jay kumar</dc:creator>
    <dc:date>2020-01-13T06:27:30Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118253776" />
    <author>
      <name>Christoph Rabel</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118253776</id>
    <updated>2020-01-10T16:48:03Z</updated>
    <published>2020-01-10T16:48:03Z</published>
    <summary type="html">If you have your own module and configuration, it should be possible to set the scope to Scope.COMPANY. Then the configuration should appear in instance settings.&lt;br /&gt; &lt;a href="https://portal.liferay.dev/docs/7-0/tutorials/-/knowledge_base/t/making-your-applications-configurable"&gt;https://portal.liferay.dev/docs/7-0/tutorials/-/knowledge_base/t/making-your-applications-configurable&lt;/a&gt;&lt;br /&gt;e.g. like here:&lt;br /&gt;&lt;a href="https://github.com/liferay/liferay-portal/blob/7.2.x/modules/apps/product-navigation/product-navigation-personal-menu-api/src/main/java/com/liferay/product/navigation/personal/menu/configuration/PersonalMenuConfiguration.java"&gt;https://github.com/liferay/liferay-portal/blob/7.2.x/modules/apps/product-navigation/product-navigation-personal-menu-api/src/main/java/com/liferay/product/navigation/personal/menu/configuration/PersonalMenuConfiguration.java&lt;/a&gt;</summary>
    <dc:creator>Christoph Rabel</dc:creator>
    <dc:date>2020-01-10T16:48:03Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118253754" />
    <author>
      <name>Christoph Rabel</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118253754</id>
    <updated>2020-01-10T16:41:36Z</updated>
    <published>2020-01-10T16:41:36Z</published>
    <summary type="html">Server settings are global. You can&amp;#39;t configure them per instance. I don&amp;#39;t think it was ever possible to configure more than one mailserver.&lt;br /&gt;You could try to override the mail implementation of Liferay but after a quick look I don&amp;#39;t see a real nice way to do that. The MailEngine class which is used to send the mail is static and not &amp;#34;OSGIyfied&amp;#34;. Maybe you could try to replace MailMessageListener. &lt;br /&gt;Another way would be to send mails to a local smtp server like postfix and dispatch them from there. </summary>
    <dc:creator>Christoph Rabel</dc:creator>
    <dc:date>2020-01-10T16:41:36Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118252225" />
    <author>
      <name>jay kumar</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118252225</id>
    <updated>2020-01-10T15:30:54Z</updated>
    <published>2020-01-10T15:30:54Z</published>
    <summary type="html">I also wanted to ask, i don&amp;#39;t see Server Administration for each instance.I want to configure different SMTP settings for each one.&lt;div class="quote-title"&gt;Christoph Rabel:&lt;/div&gt;&lt;blockquote&gt;&lt;br /&gt;A lot of configuration was moved to the frontend (System Settings and Instance Settings).&lt;br /&gt;Can you tell us, which properties you are missing or what you try to achieve per instance?&lt;/blockquote&gt;</summary>
    <dc:creator>jay kumar</dc:creator>
    <dc:date>2020-01-10T15:30:54Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118252205" />
    <author>
      <name>jay kumar</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118252205</id>
    <updated>2020-01-10T15:29:42Z</updated>
    <published>2020-01-10T15:29:42Z</published>
    <summary type="html">I have connection settings for login. and during login.. each instance makes connection with its respective API for authenticating user.</summary>
    <dc:creator>jay kumar</dc:creator>
    <dc:date>2020-01-10T15:29:42Z</dc:date>
  </entry>
  <entry>
    <title>RE: LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118250707" />
    <author>
      <name>Christoph Rabel</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118250707</id>
    <updated>2020-01-10T14:53:02Z</updated>
    <published>2020-01-10T14:53:02Z</published>
    <summary type="html">A lot of configuration was moved to the frontend (System Settings and Instance Settings).&lt;br /&gt;Can you tell us, which properties you are missing or what you try to achieve per instance?</summary>
    <dc:creator>Christoph Rabel</dc:creator>
    <dc:date>2020-01-10T14:53:02Z</dc:date>
  </entry>
  <entry>
    <title>LPS-97547 Remove legacy per portal instance properties configuration …</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118247620" />
    <author>
      <name>jay kumar</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=118247620</id>
    <updated>2020-01-10T11:50:34Z</updated>
    <published>2020-01-10T11:50:34Z</published>
    <summary type="html">Hi guys,&lt;br /&gt;Liferay removed instance based properties in 7.2 GA2.&lt;br /&gt;Here : LPS-97547 Remove legacy per portal instance properties configuration&lt;br /&gt;Can you please guide alternative</summary>
    <dc:creator>jay kumar</dc:creator>
    <dc:date>2020-01-10T11:50:34Z</dc:date>
  </entry>
</feed>
