In this session we will start by examining some of features that developers have available when using the Foundation service interfaces: how to initiate and use transactions; how and when to make use of transactional resources; using different types of search; controlling behaviors e.g. 'cm:auditable'; changing CopyService behavior. Following this, some repository internals will be examined, including: typical content lifecycles and parameters that control these; schema generation files, upgrade scripts and runtime SQL (3.4-specific); considerations for large-scale custom data structures.

1. Alfresco Repository Internals 1 Derek Hulley Senior Engineer, Alfresco twitter: @derekhulley

2. Alfresco Repository Internals 2 Resource Contention Node Creation and Modification Actions Scheduled Jobs Transactions Resources Implicit and Explicit Using Alfresco’s Transaction Support Agenda (1)

3. Alfresco Repository Internals 3 Navigating Hierarchies Lucene-based APIs NodeService-based APIs Walking Child Associations Policies and Behaviour Policy Behaviour Filters CopyService Agenda (2)

4. Alfresco Repository Internals 4 Content Lifecycles ContentData Properties Binary Files and Transactions Orphaned Content System Properties Application Bootstrap Spring init Lifecycle Classes Modules Questions Agenda (3)

6. Read-committed isolation: Invisibleuntil commit

8. Invisible until commit, but can hold resource locks

11. ‘version’ column: optimistic locking

12. Each transaction requires a thread

18. CPU cycles

20. Bean naming convention: NodeServicevsnodeService

21. Cost is in starting a transaction, not continuing one

22. public-services-context.xml and ServiceRegistry

25. 3ms lost per low-level operation ... How much per user click?Get Stores Get Children Lucene Query

27. Unnecessary additional indexingCIFS and FTP index Create Node Get Writer index Add Content

28. 1 Transactions 13 Direct Contention: Demo begin 0 0 1 1 1 1 1 0 0 0 log4j.logger.org.alfresco.repo.transaction.RetryingTransactionHelper=warn Eg: Retrying OptimisticLockingDemo-8: count 0; wait: 0.1s; msg: "Failed to update node 14575"; exception: ...ConcurrencyFailureException

30. Reliable, resolves contention

31. “non propagating”: Transaction suspended and a new one started.

32. TransactionService.getRetryingTransactionHelper -> your instance

33. TransactionalListener and TransactionListenerAdapter

34. Bind to events associated with a transaction

35. AlfrescoTransactionSupport

36. Helper around Spring’s TransactionSynchronizationManager

37. getTransactionReadState: Allows logic conditional on the state of the transaction.

38. bindResource and getResource: Bind objects to current transaction. This is like ThreadLocal but is safer i.e. Resources are bound to the transaction and go away when the transaction is terminated.

39. TransactionalResourceHelper

41. Versatile

42. Not always transactionally consistent

44. Fast for simple path-based searches only: e.g.:“/app:company_home/app:data_dictionary”

45. Always consistent!

46. NodeService.*

47. Use for consistent views

48. FileFolderService.*

49. Limited to cm:folder-based lookups

52. Use type QName for better search selectivity.

54. typeQName

55. qname

56. Also unique cm:nameN2

58. Bound to the currenttransaction

62. Spring init(): no resources available

63. Alfresco Bootstrap: order of AbstractLifecycleBean