Liferay. How to set multiple portal instance in portal-ext.properties - Forums. This website uses cookies and similar tools, some of which are provided by third parties (together “tools”). These tools enable us and the third parties to access and record certain user-related and activity data and to track your interactions with this website. These tools and the informationcollected are used to operate and secure this website, enhance performance, enable certain website features and functionality, analyze and improve website performance, and personalize user experience. If you click “Accept All”, you allow the deployment of all these tools and collection of the information by us and the third parties for all these purposes.
If you click “Decline All” your IP address and other information may still be collected but only by tools (including third party tools) that are necessary to operate, secure and enable default website features and functionalities. Visit our Privacy Policy. Page Rendering. Chapter 5. Liferay Services. The last major step to implementing permission to your custom portlet is to check permission. This may be done in a couple of places. For example, your business layer should check for permission before deleting a resource, or your user interface should hide a button that adds a model (e.g., a calendar event) if the user does not have permission to do so. Checking Portlet Resource Permission Similar to the other steps, the default permissions for the portlet resources are automatically checked for you. You do not need to implement anything for your portlet to discriminate whether a user is allowed to view or to configure the portlet itself.
However, you do need to implement any custom permission you have defined in your resource-actions XML file. The second place that checks for the add entry permission is in the file BlogsEntryServiceImpl. PortletPermission.check( getPermissionChecker(), plid, PortletKeys.BLOGS, ActionKeys.ADD_ENTRY); Checking Model Resource Permission. Can I "hide" portlets without removing them from the server? - Forums.
Chapter 6. Multiple Portal Instances. Chapter 6. Multiple Portal Instances Liferay was built from the ground up to be used by application service providers. By installing multiple portal instances a complate isolation of the users, organizations, locations, communities and any other data created through Liferay's portlets is achieved. This is possible because all of the tables used by Liferay have a column called companyId that identifies the portal instance to which the entry belongs. The following is a sample list of portals running off of one portal instance hitting one database and shows the capabilities of Liferay: The installation of multiple portal instances is specific to each application server. The following steps are common for all applications servers: It is recommended to start with a clean database. 286. Status: Final JCP version in use: 2.6 Java Specification Participation Agreement version in use: 2.0 Description: Version 2.0 of the Portlet Specification plans to align with J2EE 1.4, integrate other new JSRs relevant for the portlet, and align with the WSRP specification V 2.0.
Please direct comments on this JSR to the Spec Lead(s) Updates to the Original JSR The following information has been updated from the original proposal. Maintenance Lead: Martin Scott Nicklous E-Mail Address: scott.nicklous@de.ibm.com Telephone Number: +49-7031-16-4808 Fax Number: +49-7031-16-3335 Original Java Specification Request (JSR) Identification | Request | Contributions | Additional Information Section 1. Submitting Member: IBM Name of Contact Person: Stefan Hepper E-Mail Address: sthepper@de.ibm.com Telephone Number: +49 7031 16 3445 Fax Number: +49 7031 16 4888 Specification Lead: Stefan Hepper Initial Expert Group Membership: Supporting this JSR: BEA IBM Oracle SAP Sun Microsystems Vignette Section 2: Request No.
168. Status: Final JCP version in use: 2.1 Java Specification Participation Agreement version in use: 1.0 Description: To enable interoperability between Portlets and Portals, this specification will define a set of APIs for Portal computing addressing the areas of aggregation, personalization, presentation and security. Please direct comments on this JSR to the Spec Lead(s) Updates to the Original Java Specification Request (JSR) The following sections of the JSR have updated from the original request. Maintenance Lead: Martin Scott Nicklus E-Mail Address: scott.nicklous@de.ibm.com Telephone Number: +49-7031-16-4808 Fax Number: +49-7031-16-3335 HP has decided to cede its place on the Expert Group to TIBCO. Supporting this JSR: 2.11 Please describe the anticipated schedule for the development of this specification.
Community Review: 04/03 Public Review: 06/03 Release: 08/03 3.1 Please list any existing documents, specifications, or implementations that describe the technology. Section 1. No. No Yes.