Tuesday, September 27, 2011

Grails

Spring Source tools eclipse is used foe Grails Development.

Now will tell some steps

1. By default in the controller index method will be called
2. In the views folder name of the controller (login) folder will be created if you create loginController

3. In the controller we can instantiate Java classes and call them

4. In the contoller we will have the enclosures.

if you have the enclosure by name search inside LoginController
then it will look for
views --> login-->search.gsp

def search= {
render "abccc.gsp";
}

5. to define variables use def, semicolons are not mandatory

6. USes Gstrings similar to Velocity.

Sample

package com.hersheys.groovy.quickr

import com.hersheys.quickr.migration.TestClass

class LoginController {

/* def index = {

//can be double or string
def i = 4;

System.out.print("Inside the LoginController");

if(i < 0.5){
render "Hellvsgvdso World";
}else{
// brackets are not mandtory
render ("asfasgfasg");
}

//grroovy typeless, no return type , No semicolons , Gstring we have extrac com pared to Java

// Now calling Java

TestClass testClass = new TestClass();
def name = testClass.getNickName("john");

render name;
}
*/

def index = {

//We can configure the gsp to be used as below
//render "abccc.gsp";

// if you leave this method emptry then the index.gsp will be take n from the login folder of views
}

// url --- We can access closure similar to Dispatch Action
//http://localhost:8080/QuickrAlfresco/login/index
//login -- Controller
//index-- closure

def update = {
//render "updatehit"
System.out.print("Inside the update Closure. If we dont return anything then it will look for update.gsp inside song folder in views");
}

def search ={

def x = params.item;
//render x;
request.message = x;
}

}

We can explictly specify the name of the file where to go also

Link to get the Remote object

https://forums.alfresco.com/en/viewtopic.php?t=17587

Sunday, September 25, 2011

Getting all the users present in Liferay

final Set users = authorityService.getAllAuthorities(AuthorityType.USER);

Saturday, September 24, 2011

Policy and Behaviour

We can trigger same policy for 2 contents in 2 different classes

EX:
public class UsageQuotaProtector implements NodeServicePolicies.OnUpdatePropertiesPolicy

public void init()
{
if (contentUsageService.getEnabled())
{
// Register interest in the onUpdateProperties policy
policyComponent.bindClassBehaviour(
QName.createQName(NamespaceService.ALFRESCO_URI, "onUpdateProperties"),
ContentModel.TYPE_PERSON,
new JavaBehaviour(this, "onUpdateProperties"));
}
}

Similarly we can have
public class RepositoryAuthenticationDao implements MutableAuthenticationDao, InitializingBean, OnUpdatePropertiesPolicy, BeforeDeleteNodePolicy

*/
public void afterPropertiesSet() throws Exception
{
this.policyComponent.bindClassBehaviour(
OnUpdatePropertiesPolicy.QNAME,
ContentModel.TYPE_PERSON,
new JavaBehaviour(this, "onUpdateProperties"));

Friday, September 23, 2011

Alfresco Liferay doclib

http://pypeline.net

In this site you have the demo for alfreso and liferay doclib integration

Commands to copy file

sudo su -liferay

cp /home/hbasa/share-config-custom.xml /opt/liferay-portal-6.0-ee/tomcat-6.0.29/shared/classes/alfresco/web-extension/

file operations
vim filename
to open the file

press i to write the content

once you are done with file operation do this to save and quit
esc:q! --- To Quit the file

escape+:+w+q
To write and quit the file

Wednesday, September 21, 2011

We can generate the classes from the below command

http://axis.apache.org/axis2/java/core/docs/jaxws-guide.html

We can generate the classes from the below command
wsimport -keep -verbose wsdl_URL


 This is how we generate files

wsimport -p com.patil.jax -keep file.wsdl

Sunday, September 18, 2011

Alfresco Doc lib portlets working

When we start Liferay server after putting share war we see the below line info

23:52:27,703 INFO [site.servlet.SSOAuthenticationFilter] NTLMAuthenticationFil
ter initialised.

So this is the one which makes sso possible.
In the web.xml of share we have the following filter

Share SSO authentication support filter.

Authentication Filter

org.alfresco.web.site.servlet.SSOAuthenticationFilter

endpoint

alfresco

So this filter is looking for endpoint alfresco present in share-config-custom.xml

alfresco
Alfresco - user access
Access to Alfresco Repository WebScripts that require user authentication

alfrescoCookie

http://localhost:8080/alfresco/wcs

user

true

Here to make the external users to allow , we have external-auth true.

Now /wcs is mapped to following filter in alfresco's web.xml

WebScript Authentication Filter

/wcs/*

which points to the class

WebScript Authentication Filter

Authentication filter mapped to web script URLs. Mainly for SSO support

org.alfresco.repo.web.filter.beans.BeanProxyFilter

beanName

WebscriptAuthenticationFilter

And here again WebscriptAuthenticationFilter
maps to

${ntlm.authentication.sso.enabled}

Wednesday, September 14, 2011

CKEditor

http://localhost:9090/html/js/editor/ckeditor/editor/filemanager/browser/liferay/browser.html?Connector=%2fc%2fportal%2ffckeditor%3fp_l_id%3d10141%26p_p_id%3d15%26doAsUserId%3dYhlw4Jlrv4M%253d%26doAsGroupId%3d18&CKEditor=CKEditor1&CKEditorFuncNum=1&langCode=en

This call will get converted as below

From the File Browser following url will be called

http://localhost:9090/c/portal/fckeditor?p_l_id=10141&p_p_id=15&doAsUserId=Yhlw4Jlrv4M%3d&doAsGroupId=18&Command=GetFoldersAndFiles&
Type=Image&CurrentFolder=%2F&uuid=1316050672680

In the structs-config.xml we have the maping for

Here the ConnectorAction based on the parameters is going to call the corresponding
command method
ex: GetFoldersAndFilesCommand
This is going to return the xml
and the returned xml will be parsed.

Tuesday, September 13, 2011

Place to change the FCKEditor

You can extend the FCKEditor using hook

E:\Dumps\Liferay\liferay-portal-src-6.0.5\liferay-portal-src-6.0.5\portal-web\docroot\html\js\editor\fckeditor_diffs

from the above mentioned location.

SingleSigon For Share

Lets do single sign on step by step
1. alfresco-global.properties

ntlm.authentication.sso.enabled=true

authentication.chain=alfrescoNtlm1:alfrescoNtlm,external1:external

2. share-config.custom.xml
Here we should enable connector with the name alfrescoCookie and with the endpoint
alfresco as below

false

production

false

-1

http://localhost:8080/alfresco

false

application/msword
application/vnd.ms-excel
application/vnd.ms-powerpoint

true

alfresco://company/home

false

500

secret

ALFRESCO.ORG

HTTP/repository.server.com@ALFRESCO.ORG

ShareHTTP

alfresco/web-extension/alfresco-system.p12
pkcs12
alfresco-system

alfrescoCookie
Alfresco Connector
Connects to an Alfresco instance using cookie-based authentication
org.springframework.extensions.webscripts.connector.AlfrescoConnector

alfresco
Alfresco - user access
Access to Alfresco Repository WebScripts that require user authentication

alfrescoCookie

http://localhost:8080/alfresco/wcs

user

true

alfresco-noauth
Alfresco - unauthenticated access
Access to Alfresco Repository WebScripts that do not require authentication

alfresco

http://localhost:8080/alfresco/s

none

alfresco-feed
Alfresco Feed
Alfresco Feed - supports basic HTTP authentication via the EndPointProxyServlet

http

http://localhost:8080/alfresco/s

true

user

setting up the memory(Perm Gen)

In the startup.bat file put the below lines(C:\Alfresco3.4.3\tomcat\bin)
set JAVA_OPTS=-Xms512m -Xmx1024m -Xss1024k -XX:MaxPermSize=256m

By setting the above parameter we can start the server from startup.bat file.

@echo off
rem Licensed to the Apache Software Foundation (ASF) under one or more
rem contributor license agreements. See the NOTICE file distributed with
rem this work for additional information regarding copyright ownership.
rem The ASF licenses this file to You under the Apache License, Version 2.0
rem (the "License"); you may not use this file except in compliance with
rem the License. You may obtain a copy of the License at
rem
rem http://www.apache.org/licenses/LICENSE-2.0
rem
rem Unless required by applicable law or agreed to in writing, software
rem distributed under the License is distributed on an "AS IS" BASIS,
rem WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
rem See the License for the specific language governing permissions and
rem limitations under the License.

if "%OS%" == "Windows_NT" setlocal
rem ---------------------------------------------------------------------------
rem Start script for the CATALINA Server
rem
rem $Id: startup.bat 908749 2010-02-10 23:26:42Z markt $
rem ---------------------------------------------------------------------------

rem Guess CATALINA_HOME if not defined
set JAVA_OPTS=-Xms512m -Xmx1024m -Xss1024k -XX:MaxPermSize=256m -XX:NewSize=256m
set "CURRENT_DIR=%cd%"
if not "%CATALINA_HOME%" == "" goto gotHome
set "CATALINA_HOME=%CURRENT_DIR%"
if exist "%CATALINA_HOME%\bin\catalina.bat" goto okHome
cd ..
set "CATALINA_HOME=%cd%"
cd "%CURRENT_DIR%"
:gotHome
if exist "%CATALINA_HOME%\bin\catalina.bat" goto okHome
echo The CATALINA_HOME environment variable is not defined correctly
echo This environment variable is needed to run this program
goto end
:okHome

set "EXECUTABLE=%CATALINA_HOME%\bin\catalina.bat"

rem Check that target executable exists
if exist "%EXECUTABLE%" goto okExec
echo Cannot find "%EXECUTABLE%"
echo This file is needed to run this program
goto end
:okExec

rem Get remaining unshifted command line arguments and save them in the
set CMD_LINE_ARGS=
:setArgs
if ""%1""=="""" goto doneSetArgs
set CMD_LINE_ARGS=%CMD_LINE_ARGS% %1
shift
goto setArgs
:doneSetArgs

call "%EXECUTABLE%" start %CMD_LINE_ARGS%

:end

Liferay CMIS hook to connect to Alfresco

Install and make Alfresco up and running with the version Alfresco 3.4.1
Install Liferay and make it up. liferay-portal-tomcat-6.0-ee-sp1

In the portal-ext.properties put following properties and restart server

dl.hook.impl=com.liferay.documentlibrary.util.CMISHook

cmis.credentials.username=admin

cmis.credentials.password=admin

cmis.repository.url=http://localhost:8080/alfresco/service/api/cmis

cmis.repository.version=1.0

cmis.system.root.dir=Liferay Home

Restart Liferay and create content in the Document Library, the created content should go and sit in Alfresco.

But here the disadvantage is , it is storing the files in binary in Alfresco.

Hope that in the future releases we will have the actual content inside Alfresco

You can find more info in the blog
https://www.liferay.com/web/jonas.yuan/blog/-/blogs/integrating-alfresco-through-cmis-in-liferay

Monday, September 5, 2011

Content Storage and Lifecycle

http://wiki.alfresco.com/wiki/Content_Store_Configuration

In Alfresco, the content binaries are stored separately from the metadata, which is always found in the database. The primary metadata that acts as a reference to the binaries takes the form contentUrl=store://.........|mimetype=...(etc). The abstraction that takes care of mapping the store://... part of the reference to a physical location is the ContentStore interface.

Content Binaries and Transactions

Because binaries are not modified, it means that writes to the filesystem do not become visible until the metadata has been committed to the database. In the event of transaction failure or rollback, the metadata will be left in the pre-transaction state i.e. referencing the older binary; the newer content binary will be left in an orphaned state for later cleanup.

Deleting Files

When a file node (or anything containing a reference to raw content) is permanently deleted, there is just one less reference to the raw content. When there are no more references to some raw content, it is called orphaned. Were nothing further done, the content stores would just irreversibly fill up with content.

Cleaning up Orphaned Content (Purge)

Once all references to a content binary have been removed from the metadata, the content is said to be orphaned. Orphaned content can be deleted or purged from the content store while the system is running. Identifying and either sequestering or deleting the orphaned content is the job of the contentStoreCleaner.

In the default configuration, the contentStoreCleanerTrigger fires the contentStoreCleaner bean.

        ...               14

protectDays

Use this property to dictate the minimum time that content binaries should be kept in the contentStore. In the above example, if a file is created and immediately deleted, it will not be cleaned from the contentStore for at least 14 days. The value should be adjusted to account for backup strategies, average content size and available disk space. Setting this value to zero will result in a system warning as it breaks the transaction model and it is possible to lose content if the orphaned content cleaner runs whilst content is being loaded into the system. If the system backup strategy is just to make regular copies, then this value should also be greater than the number of days between successive backup runs.

store

This is a list of ContentStore beans to scour for orphaned content.

listeners

When orphaned content is located, these listeners are notified. In this example, the deletedContentBackupListener copies the orphaned content to a separate deletedContentStore.

Note that this configuration will not actually remove the files from the file system but rather moves them to the designated deletedContentStore, usually contentstore.deleted. The files can be removed from the deletedContentStore via script or cron job once an appropriate backup has been performed.

Code for Purging the content

delete

/images/icons/delete.gif
dialog:deleteItem

#{DialogManager.setupParameters}

#{actionContext.id}

Sunday, September 4, 2011

Exposing objects in Alfresco share

The way we use to expose the objects in the DM, similar way we can expose the objects in Alfresco share as surf objects.

This is done by extending ScriptBase object

org.springframework.extensions.webscripts.ScriptUser ---> exposes user object

Root scoped objects in Alfresco share

Refer to below link
http://wiki.alfresco.com/wiki/Surf_Platform_-_Freemarker_Template_and_JavaScript_API

Root-scoped Objects

Create a Meeting Workspace

You can create a Meeting Workspace in Share at the time you create a meeting request. The existing Share users that you add as meeting attendees automatically become members of the Meeting Workspace. The user who creates the Meeting Workspace automatically becomes the site manager.

To create a Meeting Workspace from Outlook:

Open Outlook and create a meeting request in the Calendar view with the following details:
To
usera@alfrescodemo.org; userb@alfrescodemo.org
Subject
Project Planning
Location
Conference Room
Start time
any date in the future, 10:00
End time
same day as start date, 12:00
Message
Please use the link provided to review the agenda and associated material for this meeting.
Click Meeting Workspace on the Meeting tab.
The Meeting Workspace task pane opens on the right side of the dialog box.
Click Change settings and configure the workspace as follows:
1. Specify http://localhost:7070/alfresco as the workspace location.
2. Select Create a new workspace.
3. Select Alfresco Meeting Workspace as the template type.
  If prompted, log in as the administrator (admin, admin).
  Click Create.
  If prompted, log in as the administrator (admin, admin).
  
  Outlook creates the Meeting Workspace (Share site), adds to this the meeting being scheduled, and inserts a link into the body of the meeting request. This link provides attendees with easy access to the workspace.
Click Go to workspace at the top of the task pane to access the Meeting Workspace. Again, log in as the administrator.
Use this link to create an agenda and upload meeting materials to the site before sending the meeting request. These tasks are not required as part of the tutorial.
The new Meeting Workspace opens with the calendar component displayed. The meeting request Subject line becomes both the meeting title and the workspace name (non-alphanumeric characters, including spaces, are converted to underscores for the workspace name). When you create a Meeting Workspace from Outlook, the site includes only the Document Library and Calendar components. To include additional page components—Wiki, Blog, Links, Discussions, or Data Lists—refer to the Share user help.
Log out of Share and close the browser.
In the meeting request in Outlook, click Send.
Outlook sends the meeting request. In Share, the meeting attendees are added to the Meeting Workspace as site members. By default, they are given the role Collaborator.

Create a Meeting Workspace

To create a Meeting Workspace from Outlook:

Open Outlook and create a meeting request in the Calendar view with the following details:
To
usera@alfrescodemo.org; userb@alfrescodemo.org
Subject
Project Planning
Location
Conference Room
Start time
any date in the future, 10:00
End time
same day as start date, 12:00
Message
Please use the link provided to review the agenda and associated material for this meeting.
Click Meeting Workspace on the Meeting tab.
The Meeting Workspace task pane opens on the right side of the dialog box.
Click Change settings and configure the workspace as follows:
1. Specify http://localhost:7070/alfresco as the workspace location.
2. Select Create a new workspace.
3. Select Alfresco Meeting Workspace as the template type.
  If prompted, log in as the administrator (admin, admin).
  Click Create.
  If prompted, log in as the administrator (admin, admin).
  
  Outlook creates the Meeting Workspace (Share site), adds to this the meeting being scheduled, and inserts a link into the body of the meeting request. This link provides attendees with easy access to the workspace.
Click Go to workspace at the top of the task pane to access the Meeting Workspace. Again, log in as the administrator.
Use this link to create an agenda and upload meeting materials to the site before sending the meeting request. These tasks are not required as part of the tutorial.
The new Meeting Workspace opens with the calendar component displayed. The meeting request Subject line becomes both the meeting title and the workspace name (non-alphanumeric characters, including spaces, are converted to underscores for the workspace name). When you create a Meeting Workspace from Outlook, the site includes only the Document Library and Calendar components. To include additional page components—Wiki, Blog, Links, Discussions, or Data Lists—refer to the Share user help.
Log out of Share and close the browser.
In the meeting request in Outlook, click Send.
Outlook sends the meeting request. In Share, the meeting attendees are added to the Meeting Workspace as site members. By default, they are given the role Collaborator.

Command to change tomcat server settings in tomcat

Open the path till bin and execute the command //ES//alfrescoTomcatnum2
C:\Alfresco3.4.3\tomcat\bin>tomcat6w.exe //ES//alfrescoTomcatnum2

Here alfrescoTomcatnum2 is the name of the service. You can change this name based in your service name.
Now set the required memory settings in the Java tab

Initail Memory pool 256 MB
Maximum memory pool 512mb
Thread stack size 64

If memory is not set then alfresco service may not start

DB Creation scripts for Alfresco with mysql

Database creation scripts for mysql

create database alfresco default character set utf8 collate utf8_bin;
grant all on alfresco.* to 'alfresco'@'localhost' identified by 'alfresco' with grant option;
grant all on alfresco.* to 'alfresco'@'localhost.localdomain' identified by 'alfresco' with grant option;

Database deletion scripts for mysql
create database alfresco default character set utf8 collate utf8_bin;
grant all on alfresco.* to 'alfresco'@'localhost' identified by 'alfresco' with grant option;
grant all on alfresco.* to 'alfresco'@'localhost.localdomain' identified by 'alfresco' with grant option;

Configuring Alfresco to this database is done by below lines

### database connection properties ###
db.driver=org.gjt.mm.mysql.Driver
db.username=alfresco
db.password=alfresco
db.name=alfresco
db.url=jdbc:mysql://localhost:3306/alfresco

How documentlibrary folder gets created when we create site in Alfresco

The pages will be defined here

calendar

wiki-page?title=Main_Page

documentlibrary

discussions-topiclist

blog-postlist

links

tasks

knowledgebase

The corresponding page definition will be available in the folder.

C:\Alfresco3.4.1\tomcat\webapps\share\WEB-INF\classes\alfresco\site-data\pages

discussions-topiclist

discussions-topiclist

Discussions

page.discussionsTopicList.title

Displays the forum topics

page.discussionsTopicList.description

discussions-topiclist

user

For the documentlibrary we will hava the below page definition.

Document Library

page.documentLibrary.title

Document library with Tree view

page.documentLibrary.description

documentlibrary

user

If you see the page It has Template-instance, so it will look for template-instance. The template-instance are located at C:\Alfresco3.4.1\tomcat\webapps\share\WEB-INF\classes\alfresco\site-data\template-instances\documentlibrary.xml

The template-instance is made up of the components. Components will have the region-id as below.

org/alfresco/documentlibrary

documentlibrary

documentLibrary

title

/components/title/collaboration-title

portlet-title

/components/title/portlet-collaboration-title

navigation

/components/navigation/collaboration-navigation

actions-common

/components/documentlibrary/actions-common

toolbar

/components/documentlibrary/toolbar

documentlist

/components/documentlibrary/documentlist

true

filter

/components/documentlibrary/filter

tree

/components/documentlibrary/tree