Migrating JSR-286 portlets from Websphere Portal to Liferay PortalMigrating JSR-286 portlets from Websphere Portal to Liferay Portalhttps://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1188414382024-03-28T16:55:36Z2024-03-28T16:55:36ZRE: Migrating JSR-286 portlets from Websphere Portal to Liferay PortalOlaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1188420642020-04-01T10:11:29Z2020-04-01T10:11:29Z<div class="quote-title">Dennis Møllegaard Pedersen:</div><blockquote><br />We need to migrate more than 40 portlets, so I am wondering if anyone got some insights on how we can approach this and pitfalls to avoid.<br /><br />For the proof-of-concept, I have just created a portlet using the IDE, replaced the sourcecode with one of our portlet and then manually begin resolving the errors that might appear (we expect to see Websphere specific code, that we need to change).<br /><br />Is there a better way?<br /></blockquote>Assuming that you're migrating to (one of) the latest releases, e.g. 7.x, you'll have the choice between WAR style deployment (aka JSR-286) and OSGi Components. It's your choice, which one you choose. If you deploy one portlet per plugin, the OSGi way scales better (e.g. less resource use), but if you bundle several of them together, you can omit the OSGi-migration.<br />Depending on the complexity of your 40 portlets, and on common code patterns, you <em>may</em> want to script some migration steps - unless that doesn't look like it'll generate benefit. <br />Over all, the complexity will greatly depend on the amount and complexity of the Websphere-Portal specific APIs you're using, and that's where I won't be able to help you at all with suggestions. On the JSR-286-side you're safe, that part should work out-of-the-box (with WAR style deployment). And any OSGi-style migration is quite straightforward, if you fancy to add this in the same step.<br />Following <a href="https://liferay.dev/blogs/-/blogs/radio-liferay-episode-64-david-nebinger-s-horror-stories">David's suggestion</a>, I'd recommend to do the bulk of migration under a code freeze. Don't mix upgrade with review/new features. Once it all is migrated and works, unfreeze and go ahead. Depending on your familiarity with OSGi, that already applies to the OSGi migration.Olaf Kock2020-04-01T10:11:29ZMigrating JSR-286 portlets from Websphere Portal to Liferay PortalDennis Møllegaard Pedersenhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1188414372020-04-01T09:59:36Z2020-04-01T09:59:36ZWe need to migrate more than 40 portlets, so I am wondering if anyone got some insights on how we can approach this and pitfalls to avoid.<br /><br />For the proof-of-concept, I have just created a portlet using the IDE, replaced the sourcecode with one of our portlet and then manually begin resolving the errors that might appear (we expect to see Websphere specific code, that we need to change).<br /><br />Is there a better way?<br /><br