Read Me - Getting Started

GrooperGuru

Congratulations. We couldn't be more excited that you've come to join us.
Since you're new both to Grooper and to the Grooper xChange community, we thought it would be best to show you around. So we've organized a series of articles to make your initial experience a pleasant one.

Using Grooper x Change

1. Adding a Profile Picture to your Account
2. Configuring Notifications
3. Adding a Personal Signature

Getting your environment up and running

1. Grooper Installation Files
2. Grooper Installation Guide
3. License Activation
4. Installing and Managing Services
5. Importing and Exporting Objects in Grooper
6. Grooper Update Guide
7. How to Contact Grooper Support

Understanding the Grooper approach

1. RegEx 101 Tutorial
2. Batch Processes
3. Introduction to Image Processing
4. Introduction to Grooper OCR
5. Working with Custom Scripts

Other Important Resources

1. The Grooper Wiki
2. Grooper Reference Documentation (2.80)

[Deleted User]

This looks great!

GrooperGuru

jlamb said:

This looks great!

Thanks Jessica. We are really excited.

jdickenson

[Deleted User]

GrooperGuru said:

Congratulations. We couldn't be more excited that you've come to join us. Since you're new both to Grooper and to the Grooper xChange community, we thought it would be best to show you around. So we've organized a series of articles to make your initial experience a pleasant one.

I read this in the voice of an apathetic Squidward.

GrooperGuru

Ryan said:

GrooperGuru said:

Congratulations. We couldn't be more excited that you've come to join us. Since you're new both to Grooper and to the Grooper xChange community, we thought it would be best to show you around. So we've organized a series of articles to make your initial experience a pleasant one.

I read this in the voice of an apathetic Squidward.

I was actually thinking back to the old Dungeons of the Unforgiven by Moraff. There was a very smart dungeon snake that kept you going in the right direction.

cjlarue

Hello
Is there a post related to hardware requirements?  Didn't find anything in the search.

GrooperGuru

cjlarue said:

Hello
Is there a post related to hardware requirements?  Didn't find anything in the search.

Sending you a direct message now. I can assist.

rcawthon

Do you have a link to here are the best practices for a system who can handle X number of documents per hour?  I understand that will be based on a lot of factors, but we need some method to estimate the number of resources required.  Our initial plan will be to use SQL PaaS, 2 vms for dedicated to Grooper with 4 to 8 vCPU and 8-16GB of RAM. It would be helpful to know a head of time if we need to rethink our design.

The other item we touched on briefly in training was the use of Tiered storage, do you have any metrics we can use to gauge when SSD vs standard spindal HDDs?

RandoCalrisian

@rcawthon The best estimate I could give you is minimum system requirements:

Grooper Processing Server

• Windows 10/Server 2012
• 16GB RAM
• 4-∞ virtual cores (as required)
• Default port for licensing 13900 (this is arbitrary and can be changed)

This can be a virtual or physical machine. The main consideration is number of CPU cores, as this determines your concurrent processing power. Enough memory to support this is also requisite, especially considering Image Processing. This comes down entirely to your demands as a company over time. Do you need to be able to process 1k pages at a time, or 100k pages at a time?

Grooper SQL Server

• DB Size ~20GB & set scaling to % growth, no MBs
• SQL Port 1433

SQL can be on the same machine as the main processing server, or separate. You can choose to manage multiple Grooper repositories from one SQL instance if you choose, so demands of that particular server should be considered in that scope.

Grooper FileStore Share

• ~150GB FileStore size for small to medium installs
• CIFS/SMB AD Authentication

Like the SQL server, this share for the Grooper FileStore can be local to the processing server, or not. Be sure to use UNC paths when initializing Grooper repositories.

End User PC • Grooper Thick Client Installs

• Latency <50ms
• Throughput >50MB

This would be a VM or physical machine with an installation of just the Grooper software. Activity Processing Services can be installed on these machines to take advantage of their processing power for unattended activities. This allows you to, essentially, infinitely scale out a Grooper environment and take full advantage of parallel processing.
For designers of Grooper, they can connect to the main Grooper repository from these machines, or spin up their own local environments that can use the licensing of the main repository.
For end users that plan to do task processing like scanning, Data Review, etc, their Grooper software simply needs to connect to the main Grooper repository. If you plan to do scanning, the PC with the scanner needs to be a 32bit installation of Grooper (the Windows installation can be 64bit, however.)

rcawthon

Thanks for the quick reply Randall!  To help me not waste anyone's time, was that information readily available in the forums but I missed it?  We plan to have it configured very similar to your recommendation, but my infrastructure team wanted more details on industry-standard builds/best practices to build the initial environment on. 

RandoCalrisian

@rcawthon This thread would have been the closest thing.
I'm going to add to that thread with what I just wrote though, as it does add a bit of flavor to it.