Like many products, the HP TRIM SharePoint Integration has developed a whole collection of acronyms used both internally and throughout documentation. It can be a bit of a minefield so I put together this quick post as an aide memoire for all the acronyms used in the integration itself, together with relevant acronyms from both HP TRIM and SharePoint.
|MLI||Managed List Item||An MLI is a SharePoint list item or document that is being managed by HP TRIM. This includes items that have been exposed from HP TRIM into SharePoint.
An MLI will only have one corresponding LIR.
|LIR||List Item Record||An LIR is the corresponding record created in HP TRIM for a given list item or document in SharePoint.
An LIR can be related to multiple MLIs, but also understands which MLI was the originator.
For instance, a policy document may have been managed from SharePoint, and then exposed to multiple other sites within SharePoint.
|RMO||Records Management Options||RMOs are configuration pages that control how content is managed by HP TRIM. They control container creation and classification, and can be defined against sites, lists and templates.|
|LMO||Lifetime Management Options||LMOs control when content is managed and archived by HP TRIM, by providing the mechanism to assign Lifetime Management Policies (LMPs). LMOs can be defined against sites, lists and templates.|
|LMP||Lifetime Management Policy||An LMP is a SharePoint workflow-based policy, which can be used to define rules for automatic capture and management of SharePoint content.
Examples might include “Manage items when the status is set to 'In Progress'”, or 'Archive items that have not been modified for 6 months, after approval'. LMPs are used to define the rules and actions, LMOs are used to apply those rules
|CT2RT||Content Type to Record Type||CT2RT mapping configures how content captured from SharePoint will be represented in HP TRIM. Each relevant Content Type (Typical not all will be mapped) can be mapped to a corresponding Record Type in HP TRIM.|
|RT2CT||Record Type to Content Type||RT2CT mapping configures how content will be exposed from HP TRIM into SharePoint. By mapping each Record Type to a Content Type, it is possible to control which Content Types will be used to represent information from HP TRIM.|
|SCIS||Site Collection Integration Settings||The SCIS page exists at the root of each Site Collection. It provides configuration for default settings, including a default Record Type for content and containers, plus default classification. These settings are used as default settings in the event they have not been specifically configured elsewhere (CT2RT, RMO)|
|WAIS||Web Application Integration Settings||The WAIS page is used to configure high-level integration settings. It is used to configure settings such as the database ID of the HP TRIM database and the privileged access service accounts. These settings are mandatory for the integration between SharePoint and HP TRIM to function.|
|TES||TRIM Enterprise Studio||The TES is used to configure HP TRIM itself. It is used in the context of the SharePoint Integration, to configure accounts that can be trusted for impersonation, to configure Workgroup Servers for the integration, and to configure event processing to support two way synchronization and exposure of HP TRIM content into SharePoint|
|TPA||TRIM Privileged Account||The TPA is one of three accounts that are required to support a functioning integration. In real terms these are service accounts that require privileged levels of access in order to perform certain tasks. In the case of the TPA it is creation of Record Types, user defined fields in HP TRIM and in some cases creation/modification of list items in SharePoint and HP TRIM. The other two accounts are the SPA, covered next, and TrimServices, which already exists in an HP TRIM deployment.|
|SPA||SharePoint Privileged Account||The SPA is the second of the three accounts required for a functioning integration. Like the TPA, the SPA requires elevated privileges, in this case in SharePoint only. The account is used for creation of list columns, logging, reading property bags, and adding/modifying items in certain circumstances. Note this is not necessarily an exhaustive list.|
|SCA||Site Collection Administrator||The SCA does what it says on the tin, it means a user account that is a member of the Site Collection Administrators group, rather than just a site administrator. There is a distinction.|
|GAC||Global Assembly Cache||The GAC is a term you will see a lot if you work in SharePoint development. This is a global location where the SharePoint Integration assemblies are deployed. This means they are given full-trust and that they can be used in any web application.|
|RBS||Remote Blob Storage||RBS in simple terms is a provider mechanism that can be used to abstract storage of documents from the SharePoint SQL database to a file storage location. The integration currently provides an optional RBS component, however the reality is that most enterprises choose to purchase and deploy a third-party solution. So, the integration does have an RBS, but it is built specifically to work with the integration, and not without it.
Note that the integration will work with third-party RBS solutions; everything the integration does is through the SharePoint object model, so use of these solutions is supported.
|WFE||Web Front-End||A WFE is a server in a SharePoint farm configured to act as the point of contact between a user and the farm. It runs as a web server and serves up SharePoint pages via HTTP. A pure WFE server will only be configured to run the Foundation Web Application, although there are plenty of hybrid implementations where additional application services are run on WFEs. In anything other than small implementations there will be multiple WFE servers in a load balanced configuration.
For more information on capacity, scaling and architecture see http://technet.microsoft.com/en-us/library/ff758647.aspx#reference
|AS||Application Server||An AS server, runs any number of SharePoint application services, such as Indexing, Excel Calculation Services, managed Metadata, Search querying and so on. Again, depending on the deployment configuration there may be multiple AS servers running different services|
|AAM||Alternate Access Mappings||AAM is a feature of SharePoint that allows a website to function correctly under different URL scenarios, including, reverse proxies and load balancing. If AAMs have been configured then additional entries need to be made in order to ensure stable communication between SharePoint and HP TRIM. The HP TRIM SharePoint Integration Install Guide covers this in more detail|
|SSL||Secure Sockets Layer||SSL is an encrypted communication protocol, commonly used to prevent eavesdropping and tampering of SharePoint communication. If a SharePoint web application has been configured to use SSL, the integration requires some configuration changes in order for communication to work correctly. These changes are detailed in the HP TRIM SharePoint Integration Install Guide.|
|ULS||Unified Logging Service||The ULS writes detailed SharePoint events to the trace logs. These logs can then be viewed directly in the logs folder:
(C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS)
or through an application like ULS Viewer . Note there are lots of other ULS Viewer applications out there, I just happen to use this one.
The SharePoint Integration writes custom log entries through the ULS, meaning it is possible to troubleshoot issues by viewing both SharePoint and integration specific events in the same place.
|RSS||Really Simple Syndication||RSS is a feed format used to publish frequently update web content from blogs, discussion groups, news headlines etc. It is XML based and is widely used to consume content around the world, using dedicated RSS viewer software. In fact, you may even be consuming my blog using RSS!
RSS is only mentioned in this list because the federated search component of the integration uses RSS in the background to serve up security-trimmed HP TRIM search results.
This could potentially be leveraged to provide RSS feeds of specified searches against TRIM datasets. Feel free to discuss and explore this.
If I’ve missed any you think are relevant or important, please let me know and I’ll add them to the table. If you want to know more about any of these, you have a few options:
- In the case of integration specific terms, the install & configuration guides are your only resource (Other than this blog!) for now. The configuration guide is a work-in-progress, so only contains a couple of chapters.
- For other SharePoint and general terms, Google is your friend!
- Some of these areas will be covered in much more detail in future posts, check my Introduction Post for a list of planned topics.