Difference between revisions of "Scripting - OpenKM 5.1"

From OpenKM Documentation
Jump to: navigation, search
(→‎After uploading a file, remove all grants - except read - to all users but mantain to uploader)
Line 1: Line 1:
 
{{TOCright}} __TOC__
 
{{TOCright}} __TOC__
  
−
Scripting is an advanced feature - a sort of experimental - that enables administrator to execute some BeanShell scripts in folders fired on every notified event ( for example uploading documents ). It could be useful for making automatic operations at repository level.
+
Scripting is an advanced feature - a sort of experimental one - that enables administrators to execute some BeanShell scripts in folders, fired on every notified event ( for example uploading documents ). It could be useful for performing automatic operations at repository level.
  
−
Scripting can be set by folder or document. You need to go to '''Administration''' > '''Repository view''' and browse the repository at low level. Be careful because and error can damage the document repository! When you have located the right place, select '''Scripting: Set script''' and a new scripting property will be added to the node. This new property can be edited to set your custom BeanShell code.
+
Scripting can be set by folder or document. You need to go to '''Administration''' > '''Repository view''' and browse the repository at low level. Be careful because an error can damage the document repository! When you have located the right place, select '''Scripting: Set script''' and a new scripting property will be added to the node. This new property can be edited to set your custom BeanShell code.
  
  
Line 17: Line 17:
  
  
−
Starting with OpenKM 5.0 you can also execute a custom script when OpenKM starts or stop. To do so, just create a '''start.bsh''' (and / or '''stop.bsh''') file at $JBOSS_HOME. For example, we use this feature to create a complete environment (create custom users, register property groups, register workflow) each time the OpenKM demo is reinitialized.
+
Starting with OpenKM 5.0 you can also execute a custom script when OpenKM starts or stops. To do so, just create a '''start.bsh''' (and / or '''stop.bsh''') file in $JBOSS_HOME. For example, we use this feature to create a complete environment (create custom users, register property groups, register workflow) each time the OpenKM demo is reinitialized.
  
 
== Variable substitution ==
 
== Variable substitution ==
Line 55: Line 55:
  
 
== Examples ==
 
== Examples ==
−
{{Advice|To register these example you must go to repository view, select some folder for example into /okm:root/Books/ and set script to enable mixing. It'll appear new property '''okm:scripCode''' now must edit it and paste the code from scripting example.}}
+
{{Advice|To register these examples you must go to repository view, select some folder for example /okm:root/Books/ and set script to enable mixing. A new property will appear - '''okm:scripCode'''. Edit it and paste the code from the scripting example.}}
  
 
{{Note|If you are using OpenKM 4.1 (or previous), the right package is "es.git.openkm". The package "com.openkm" is valid starting at OpenKM 5.0}}
 
{{Note|If you are using OpenKM 4.1 (or previous), the right package is "es.git.openkm". The package "com.openkm" is valid starting at OpenKM 5.0}}
  
−
=== Automatic renaming document ===
+
=== Automatic renaming of document ===
 
<source lang="java">
 
<source lang="java">
 
String parent = com.openkm.util.FileUtils.getParent(eventNode.getPath());
 
String parent = com.openkm.util.FileUtils.getParent(eventNode.getPath());
Line 66: Line 66:
 
</source>
 
</source>
  
−
=== Automatic adding keyword ===
+
=== Automatic adding of keyword ===
 
<source lang="java">
 
<source lang="java">
 
eventNode.setProperty("okm:keywords", new String[]{"maligno"});
 
eventNode.setProperty("okm:keywords", new String[]{"maligno"});
Line 122: Line 122:
 
</source>
 
</source>
  
−
You can see also a modified version with runs on older OpenKM 5.0 branch at [http://forum.openkm.com/viewtopic.php?f=5&t=5278&p=11751#p11715 Forum: Purge trash of all users].
+
You can see also a modified version which runs on the older OpenKM 5.0 branch at [http://forum.openkm.com/viewtopic.php?f=5&t=5278&p=11751#p11715 Forum: Purge trash of all users].
  
 
=== Using Beanshell to move Mails ===
 
=== Using Beanshell to move Mails ===
Line 169: Line 169:
 
See related forum topic [http://forum.openkm.com/viewtopic.php?f=6&t=5360 Using Beanshell to move Mails].
 
See related forum topic [http://forum.openkm.com/viewtopic.php?f=6&t=5360 Using Beanshell to move Mails].
  
−
=== After uploading a file, remove all grants - except read - to all users but mantain to uploader ===
+
=== After uploading a file, remove all rights - except read - to all users but mantain to uploader ===
−
The Script should remove all grants to all users and roles - except read grant - and will continue mantaining privileges to uploader user.
+
The Script should remove all rights to all users and roles - except read right - and will retain existing privileges of the uploader user.
  
 
<source lang="java">
 
<source lang="java">

Revision as of 14:00, 15 November 2011

Scripting is an advanced feature - a sort of experimental one - that enables administrators to execute some BeanShell scripts in folders, fired on every notified event ( for example uploading documents ). It could be useful for performing automatic operations at repository level.

Scripting can be set by folder or document. You need to go to Administration > Repository view and browse the repository at low level. Be careful because an error can damage the document repository! When you have located the right place, select Scripting: Set script and a new scripting property will be added to the node. This new property can be edited to set your custom BeanShell code.


RepositoryView Scripting.png



Nota clasica.png OpenKM uses BeanShell. For more information point your browser to http://www.beanshell.org/intro.html.

BeanShell is a small, free, embeddable Java source interpreter with object scripting language features, written in Java. BeanShell dynamically executes standard Java syntax and extends it with common scripting conveniences such as loose types, commands, and method closures like those in Perl and JavaScript.


Okm admin 003.jpeg


Starting with OpenKM 5.0 you can also execute a custom script when OpenKM starts or stops. To do so, just create a start.bsh (and / or stop.bsh) file in $JBOSS_HOME. For example, we use this feature to create a complete environment (create custom users, register property groups, register workflow) each time the OpenKM demo is reinitialized.

Variable substitution

  • java.lang.String eventType - says the event that has fired the script. See below for event types.
  • javax.jcr.Session session - users session that executes the script.
  • javax.jcr.Node eventNode - node that causes the event.
  • javax.jcr.Node scriptNode - node where is stored the script.

Events types

Document related

  • CREATE_DOCUMENT
  • DELETE_DOCUMENT
  • SET_DOCUMENT_CONTENT
  • SET_DOCUMENT_PROPERTIES
  • CHECKOUT_DOCUMENT
  • CANCEL_CHECKOUT_DOCUMENT
  • CHECKIN_DOCUMENT
  • LOCK_DOCUMENT
  • UNLOCK_DOCUMENT
  • PURGE_DOCUMENT

Folder related

  • CREATE_FOLDER
  • DELETE_FOLDER
  • PURGE_FOLDER

Mail related

  • CREATE_MAIL
  • DELETE_MAIL
  • PURGE_MAIL

Property related

  • ADD_CATEGORY
  • REMOVE_CATEGORY
  • ADD_KEYWORD
  • REMOVE_KEYWORD

Examples


Nota idea.png To register these examples you must go to repository view, select some folder for example /okm:root/Books/ and set script to enable mixing. A new property will appear - okm:scripCode. Edit it and paste the code from the scripting example.


Nota clasica.png If you are using OpenKM 4.1 (or previous), the right package is "es.git.openkm". The package "com.openkm" is valid starting at OpenKM 5.0

Automatic renaming of document

String parent = com.openkm.util.FileUtils.getParent(eventNode.getPath());
session.move(eventNode.getPath(), parent+"/renamed_document.doc");
session.save();

Automatic adding of keyword

eventNode.setProperty("okm:keywords", new String[]{"maligno"});
eventNode.save();

Change log level

import org.apache.log4j.*;

Logger log = Logger.getLogger("com.openkm.module");
log.setLevel(Level.DEBUG);

Reload log configuration

This sample work-as-is in OpenKM-LTE. 

import org.apache.log4j.*;
import com.openkm.util.*;

String filename = ServerDetector.getHomeDir() + "/lib/log4j.properties";
new PropertyConfigurator().doConfigure(filename, LogManager.getLoggerRepository());

Purge all users trash

Works on OpenKM 5.1 branch. 

import javax.jcr.*;
import com.openkm.core.*;
import com.openkm.bean.*;
import com.openkm.module.base.*;
 
String token = JcrSessionManager.getInstance().getSystemToken();
Session session = JcrSessionManager.getInstance().get(token);
Node trash = session.getRootNode().getNode(Repository.TRASH);
 
for (NodeIterator it = trash.getNodes(); it.hasNext(); ) {
    Node userTrash = it.nextNode();
    print("User Trash: " + userTrash.getPath() + "<br/>");
 
    for (NodeIterator itut = userTrash.getNodes(); itut.hasNext(); ) {
        Node child = itut.nextNode();
        print("About to delete: " + child.getPath() + "<br/>");
 
        if (child.isNodeType(Document.TYPE)) {
            BaseDocumentModule.purge(session, child.getParent(), child);
        } else if (child.isNodeType(Folder.TYPE)) {
            BaseFolderModule.purge(session, child);
        }
    }
    
    userTrash.save();
}

You can see also a modified version which runs on the older OpenKM 5.0 branch at Forum: Purge trash of all users.

Using Beanshell to move Mails

The Script should check a specific Mail folder ("Docs") and move all the mails in another folder ("okm:root/Mails") in the Taxonomy. This runs as a Cronjob. 

import javax.jcr.*;
import com.openkm.core.*;
import com.openkm.bean.*;
import com.openkm.module.*;

String token = JcrSessionManager.getInstance().getSystemToken();
Session session = JcrSessionManager.getInstance().get(token);

Node okmmail = session.getRootNode().getNode(Repository.MAIL);
Node okmroot = session.getRootNode().getNode(Repository.ROOT);

for (NodeIterator it = okmmail.getNodes(); it.hasNext(); ) {
  Node userMailFolder = it.nextNode();
   
  if( userMailFolder.getPath().equals("/okm:mail/Docs") ) {
    //Check the mail in the "Docs" folder
    for (NodeIterator itut = userMailFolder.getNodes(); itut.hasNext(); ) {
      Node mail = itut.nextNode();
      String name = mail.getName();
      
      //Check the keyword
      int available = name.indexOf("al");
      if (available != -1){
        session.move(mail.getPath(), okmroot.getPath() + "/alFolder/" + mail.getName());
        session.save();
      }
      
      available = name.indexOf("ka");
      if (available != -1){
        session.move(mail.getPath(), okmroot.getPath() + "/kaFolder/" + mail.getName());
        session.save();
      }
    }
    
    userMailFolder.save();
  }
}

See related forum topic Using Beanshell to move Mails.

After uploading a file, remove all rights - except read - to all users but mantain to uploader

The Script should remove all rights to all users and roles - except read right - and will retain existing privileges of the uploader user. 

import java.util.Map;
import com.openkm.api.OKMAuth;
import com.openkm.bean.Permission;

if (eventType.equals("CREATE_DOCUMENT")) {
	String userId = session.getUserID();
	String path = eventNode.getPath();
	OKMAuth oKMAuth = OKMAuth.getInstance();
	
	// All Roles only will continue having read grants
	Map hm = oKMAuth.getGrantedRoles(null, path);
	for (String roleName : hm.keySet()) {
		oKMAuth.revokeRole(null, path, roleName, Permission.WRITE, false);
		oKMAuth.revokeRole(null, path, roleName, Permission.DELETE, false);
		oKMAuth.revokeRole(null, path, roleName, Permission.SECURITY, false);
	}
	
	// All users only will continue having read grants
	hm = oKMAuth.getGrantedUsers(null, path);
	for (String userName : hm.keySet()) {
		if (!session.getUserID().equals(userName)) {
			oKMAuth.revokeUser(null, path, userName, Permission.WRITE, false);
			oKMAuth.revokeUser(null, path, userName, Permission.DELETE, false);
			oKMAuth.revokeUser(null, path, userName, Permission.SECURITY, false);
		}
	}
}

Execute repository stats

import com.openkm.module.direct.*;
import com.openkm.bean.*;
import com.openkm.core.*;

String systemToken = JcrSessionManager.getInstance().getSystemToken();
print("Token: " + systemToken);
StatsInfo si = new DirectStatsModule().getDocumentsSizeByContext(systemToken);
print("StatsInfo: " + si);
Retrieved from "https://www.openkm.com/wiki/index.php?title=Scripting_-_OpenKM_5.1&oldid=5638"