I wanted to understand the database mapping in detail for Liferay User Management system. Do I get any reference where I can I Database mapping in any format like (ER diagrams / Block diagrams). Please give me some references for complete analysis of liferay database user management(6.2).
there's no offical ER diagram of data base schema. use workbench for reverse engineering the sql files
Related
on the web there are many resources about exporting a development database (HSQL) into a production one (eg. MySQL), but I need to move data in the opposite way.
I usually use the Liferay embedded function to export data to a new database, but it needs for a running database server instance (and it seems to be impossible using HSQL).
Does a way to achieve this goal exist in Liferay 6.2?
Thanks
Go to Control Panel / Server Administration / Data Migration. You can give the standard HSQL URLs - you don't need a running HSQL server. The standard HSQL parameters can be found in Liferay's portal.properties under Hypersonic
Can you please point me to a good guide on how to migrate Customer Relationship roles to Connections? I am using CRM 2013 on-premise.
I am going to try exporting the Roles and Importing them as Connections but this is giving me look up errors. In my opinion this is a simplistic approach and I might be wrong in the first place using this approach.
So has anyone tried this approach before and does it work? And is there an another way of doing this?
Here is a blog about doing it using Scribe:
http://blog.customereffective.com/blog/2011/10/crm-2011-converting-relationships-to-connections.html
Here is a blog about doing it using the built in import/export functionality:
http://www.powerobjects.com/blog/2013/04/25/replace-relationship-roles-with-connections-in-dynamics-crm/
If I needed to migrate a large volume of relationships I would build the connection table based off the old relationship roles table using direct SQL injection. Of course this is unsupported.
I have got the following problem: I created a database diagram in a database which is used by a special software. This software creates its own relationships programmatically - I only created the diagram to show the relationships to someone who is not familiar with the software.
I told the admin to delete the diagram, which he did, nonetheless there seem to be relationships from this diagram interfering with the software.
Do you have any idea how I can get rid of all the relationships?
Start SQL Server Management Studio (awesome tool). Use the tree view on the left, navigate to your database and subsequent to your tables. Check out, review and delete the relations if necessary.
We have a SharePoint document management site and the documents will be uploaded from java portal, via SharePoint web services.
The metadata values will be provided multi language (Like Spanish).
Is it safe to accept and store such data in SharePoint as SQL server uses unique code format to store the SharePoint data in SQL server.
If storing the multilingual data in SharePoint is not right approach, is there any other way we can do it.
Please let us know your views if possible.
Given that this question is from 2013, I will base my answer on the On Premises versions of SharePoint.
From the description, it looks like the entry point for document to this document center is a Java portal that is probably in Spanish. It looks like the concern is the data entry of metadata (such as Description etc.) is coming from a Spanish based interface. It is quite possible that the hosting servers are also running with Language Packs (such as Spanish) installed. As such, it is possible for the user to enter and produce characters that do no appear in the English language and that is what concerns the original poster. The poster is correct in that SharePoint uses SQL Server as its back end data store, however, both the SharePoint and SQL Server products are (at least now) language agnostic. If you can produce the text and the Java interface correctly encodes said text, then there is no cause for concern. The data will be stored with full fidelity in SharePoint and by proxy SQL Server regardless of the host's language pack configuration.
In short, it's OK to do.
What is the difference between this services?
DLFileEntryLocalServiceUtil
and
DLAppLocalServiceUtil
When should we use one and when the other? Is DLAppLocal a new interface in Liferay 6.1 which discourages the old DLFileEntry for application level code?
What is the difference between these services DLFileEntryLocalServiceUtil and DLAppLocalServiceUtil?
DLFileEntry services and DLFolderEntry services are specifically for storing file and folder entries in liferay's database and are totally unaware of the new repository concept introduced in 6.1. The user-guide & this wiki explains how to add a new repository.
Were as DLApp (DLAppService & DLAppLocalService) services take into account these things i.e. to say that they take care of syncing documents between liferay database and other repositories, and not just store entries in Liferay database.
The documentation for the class DLAppServiceImpl explains it all (this is almost same for DLAppLocalServiceImpl), the following is an excerpt from the documentation:
The document library local service. All portlets should interact with the document library through this class or through DLAppServiceImpl, rather than through the individual document library service classes.
This class provides a unified interface to all Liferay and third party repositories. While the method signatures are universal for all repositories. Additional implementation-specific parameters may be specified in the serviceContext.
The repositoryId parameter used by most of the methods is the primary key of the specific repository. If the repository is a default Liferay repository, the repositoryId is the groupId or scopeGroupId. Otherwise, the repositoryId will correspond to values obtained from RepositoryLocalServiceUtil.
Is DLAppLocal a new interface in Liferay 6.1?
Yes
which discourages the old DLFileEntry for application level code?
In a sense yes, refer the above explanation. DlAppLocalServices is much better to use as its scope is much greater than the individual document services. Still if you want to use these interfaces for storing the documents & media from your custom plugin portlet you can go ahead and use these, I don't think there should be a problem since even DlAppLocalServices also internally uses the individual document services for storing in liferay repository.
Hope this provides some relevant information for your question.