ECMS - ECM/Imaging Environments

This document explains the ECM/Imaging Environments.

ECM/Imaging Environments

The following outlines the environments of our ECM/Imaging service. It details what is available in software and configuration in the environments. It also explains expectations for use of these environments.

  1. PROD - other system's PROD; Production.
  2. TEST - other system's QA; non-production.
  3. DEV - other system's TEST; non-production.
  4. SCHEMA - latest version sandbox; non-production.

Environments

PROD

Description
  1. Primary ECM/Imaging shared system
  2. Basis for TEST, SCHEMA, and DEV environments.
Server/Client Version
  1. Server version 7.2.3.489, Perceptive Experience version 2.4.3

Client Installer Link

Connection Profile Settings
  1. Profile name: Anything you like, e.g. Production
  2. Server name: imaging.services.wisc.edu
  3. Port number: 6000
  4. Type: production

TEST

Description
  1. COPY of current production environment DB and OSM
  2. Includes folders workflow, queues, groups, users, views, and documents
  3. Has some ancillary services (sFTP, etc.)
  4. No agents enabled in TEST by default; enabled manually as needed (contact Imaging team)
Server/Client Version
  1. Server version 7.2.3.489, Perceptive Experience version 2.4.3

Client Installer Link

Refresh Interval

Monthly from PROD

Purpose
  1. Pre-production staging of new work
  2. Available for development projects shorter than 4 weeks.
  3. Essentially full PROD environment so mapping to system objects should be accurate for pre-production testing.
Connection Profile Settings**
  1. Name: what ever you want, like "7Test"
  2. Server: imagingtest.services.wisc.edu
  3. Port: 6000
  4. Type: production

David retains the ability to "monitor" TEST.

DEV

Description

SANITIZED COPY of current PROD DB

  1. Folders, workflow, queues, groups, users as in PROD
  2. NO real, sensitive data should ever be used; dummy data/documents only.
  3. NO documents or document data from PROD
  4. Independent OSM (into which end-users can put new documents)
  5. Some ancillary services as needed for end-user projects/testing.
Server/Client version
  1. Server version 7.2.3.489, Perceptive Experience version 2.4.3 / Oracle 12.2

Client Installer Link

Refresh Interval
  1. Refreshed for functional changes (patches, etc.)
  2. 6-month refresh barring other exigencies.
Purpose
  1. Provide an early testing environment for Imaging Team and customers with the latest builds/patch releases
  2. Provide an environment that is segragated from environments in which Imaging customers do development and testing of real processes.
  3. NOTE: Almost always the server/client builds will require a client different from that used in PROD, TEST, and SCHEMA; you will need a dedicated system (or a VM) to use the newer clients for connections so that the client for the other environments is not removed.
Connection Profile Settings
  1. Name: what ever you want, like "7Dev"
  2. Server: imagingdev.services.wisc.edu
  3. Port: 6000
  4. Type: production

SCHEMA

Description

SANITIZED COPY of current PROD DB

  1. Folders, workflow, queues, groups, users as in PROD
  2. NO real, sensitive data should ever be used; dummy data/documents only.
  3. NO documents or document data from PROD
  4. Independent OSM (into which end-users can put new documents)
  5. Some ancillary services as needed for end-user projects/testing.
Server/Client version
  1. Server version 7.3.0.375, Perceptive Experience version 3.0
  2. Requires client 7.2.2 Build 277

If you need a version of the client to connect to SCHEMA, please email a request to imaging-support@doit.wisc.edu

Refresh Interval
  1. Refreshed for functional changes (patches, etc.)
  2. 6-month refresh barring other exigencies.
Purpose
  1. Initial/Early end-user DEVELOPMENT work
  2. Create docs, etc. which go into its OSM. These objects cannot be copied/migrated to TEST or PROD
  3. iScript development
  4. If there is a need for elevated security in SCHEMA we will provide it to you.
Connection Profile Settings
  1. Name: what ever you want, like "7Schema"
  2. Server: schema.imaging.services.wisc.edu
  3. Port: 6000
  4. Type: production

Notes

See Also: