Test Environment

Epicor ERP 10
1

When I started we already had test environment set up. So I know little about how it was set up, etc. What I am wanting is where to find info setting up test environment and how to update test so it is identical to my live environment. Seems that our test has not been updated in over 2 years. So, not really a good test environment.

2

The simple answer is to copy your Live environment directly over to your Test.
Be careful!

1 Like
3

Simple + Be careful…Sounds not so simple! LOL!

1 Like
4

William

I’ll have to assume that your test environment is setup the exact same from an Appserver and extension standpoint (mobile, web access, help, social, search, etc.) The extensions are not as important, but we made sure the Test was the SAME as Prod in every way save the server hostnames. We even have special directories shared for Test data to make sure we can tell them apart when we’re comparing directories/logs/etc.

Some other things you need to check are:

  • the Appserver/extensions all connect using the correct userid/password combinations
  • you’ve copied custom report files (both Crystal and SSRS) to the correct location for your Test DB
  • The config files on the Test DB are correct for your environment
  • see the part of the script where I change the Company Names - this is very helpful to the users and your Epicor Admins.

I’m sure some other folks will have more tidbits, but these are the ones I can think of off the top of my head.

What we do is:

  1. take a ‘copy-only’ backup of the production database and move it to the Test server.
  2. we also take a backup of the test DB for good measure :slight_smile:
  3. Stop the Appserver and the Task Agent for Test.
  4. Restore over the Test database (leave operational, close connections, etc.)
  5. Run the attached script in it’s various sections to validate all the settings or change the ones we need to change. This is a debatable process, as I’m writing directly to the Epicor tables, but it’s the Test DB and this is easier than using the UI, since I do this monthly.
  6. Generate the Data Model for the Test DB on the Test Appserver. This is a KEY step.
  7. Start the Appserver and make sure it’s OK.
  8. Start the Task Agent and try and print/process something. Occasionally the Task Agents ‘says’ it’s OK, but it really isn’t.
  9. for good measure, take another DB copy, so you don’t have to start form scratch when someone messes up your DB.

,ProdToTest Settings.txt (4.1 KB)

Hope this helps,
Mike

2 Likes