Established Member.. HaseebIqbal
Established Member..
1778 views

HP Trim (EDRMS) requirement matrix

Jump to solution

We are thinking to implement HP Trim(EDRMS).
Now, first thinking about platforms.
Our plan is using Windows 2012 R2 (x64) on VM and MS SQLSERVER. All desktops clients are on Windows 7 Enterprise SP1 x64.

So we need the specification document or Internet website page which high lights the basic configuration.

So that, atleast we can be prepared and estimate a project plan.

Thanks

0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: HP Trim (EDRMS) requirement matrix

Jump to solution

I've attached the specifcations guide for the latest version of Records manager - 8.3.0

**Any opinions expressed in this forum are my own personal opinion and should not be interpreted as an official statement on behalf of Micro Focus**
5 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: HP Trim (EDRMS) requirement matrix

Jump to solution

I've attached the specifcations guide for the latest version of Records manager - 8.3.0

**Any opinions expressed in this forum are my own personal opinion and should not be interpreted as an official statement on behalf of Micro Focus**
Established Member.. HaseebIqbal
Established Member..

Re: HP Trim (EDRMS) requirement matrix

Jump to solution

Thanks Greg.

Thats what I asked for.

Now comes next part. We have
Server sides:

  • HP Trim x64
  • HP TRIM desktop
  • HP Trim Enterprise Studio
  • HP Trim Queue Processor
  • HP Trim webDrawer ISAPI extension Configuration Tool
  • IIS>WebDrawer
  • SQL Server 2012
  • User Desktops:

    • HP TRIM Microsoft runtimes for VS2008 x86 (7.0.0.0)
    • HP TRIM Microsoft VB runtimes (7.0.0.0)
    • HP TRIM x86 (7.34.5739)
    • HP Records Manager 7.x
    • HP TRIM Desktop 7.x

      Will it be easy to migrate from the above environment? At the moment, we are not sure, if we are going migrate or implement fresh system.
    • If we are implementing fresh system and match the above or existing modules (already installed) will we miss out very important stuff or we can add later?
0 Likes
Harry-Koppanyi Outstanding Contributor.
Outstanding Contributor.

Re: HP Trim (EDRMS) requirement matrix

Jump to solution

In HPRM / HP TRIM world (especially) when you are looking to upgrade from previous release of binaries and database (DataSet) you would need to install the new version binaries. To assess if you would be able to use the current OS is based on your current OS and Verion of HPTRIM. (Why and How) looking at your Client it seems that you have TRIM7.34 means most probably your Server is running HP TRIM 7.34 Workgroup server and might be on Windows 2008R2 with .Net 3.5.

For HPRM 8.x and especially 8.2 or 8.3 you would be better of running Windows 2012 R2 as of Server and SQL Server 2012 or higher. Windows 2012 R2 comes with .Net 4.5 framework and its has all the latest MS OS which HPRM leverages on as it is also based on new architecture.

Coming to your question of if you migrate or Fresh implementation, actually these are two fold and falls under two different categories. When we talk about Migration that means using new version of binaries and upgrading the exisiting Dataset to latest schema level (tables and columns  and system configuration tables etc). If you were running on new OS and architecture this could be done however if you are on Windows 2008 and looking to use RM 8. or higher you would be ideally looking at Windows 2012 R2 that means you would be taking the existing Dataset backup and bring it over to the new OS (Workgroup) and from Enterprises Stuido run the Schema Upgrade. That is Migration. In this strategy Customer only install the new versions of Software and and Client machines are also upgrade to latest software version with no Functional Changes for Record Types, or any other functional structure.

For Fresh Implementation, which is usually a part of Functional upgrade or modernisation or whatever you would like to call is when an Organisation releaises that current setup (record types, Additional fields, folder structure, classification etc) is not meeting the User requirements. They start from Business Analysis and user process understanding and adjust or define new functional structure in HPRM / HP TRIM. That is where fresh implementation or revised implementation makes sense.

In summary if you are only doing the Software upgrade that means you would assess if your Current OS is suitable and is mentioned in the Specs Document from HPRM (if yes), then you would uninstall the older HP TRIM Software and install the new binaries (following best practices for install and upgrade) and rollout the Client software and that would be your upgrade.

Hope this helps.


Cheers,
Harry
Grundy Acclaimed Contributor.
Acclaimed Contributor.

Re: HP Trim (EDRMS) requirement matrix

Jump to solution

Some good advice above, however these forums wont be able to help you throughout an entire project.

I would highly recommend you employ the services of an experience TRIM / Records Manager consultancy to run through the project with your organisation.



::::::::::::::::::::::
NOT A HP EMPLOYEE
::::::::::::::::::::::

INFORMOTION.com.au
0 Likes
kofax_captured
Visitor.

Re: HP Trim (EDRMS) requirement matrix

Jump to solution

Hi

We have a customer using W7 workstations with Kofax Capture 10.1.0 connected to HP TRIM 8.2

They want to upgrade the workstations to W10.  We are told 10.1.0 is not supported on W10.

Kofax Capture 10.2 has a HPE Connector for CM9.x

Can we use Kofax Capture 10.2 with the HPE Connector against TRIM 8.2

 

Is there a support matrix showing what is support where?

 

Thanks

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.