Development Environments

Development Environments

We have four main development environments. They are local, development, test, and production. Our local and development environments both provide places for the development team to test their code changes before they are complete. Our test environment is where application testing occurs before code changes are released to production. Our production environment is our live environment being accessed by internal staff and external customers.

Local

Local tomcat instance

Local xe database instance

Development

tomcatdev01 – Application Server

Tomcat Instances

  • at-remote-connection
  • authorization
  • backoffice
  • device-management
  • event-logger
  • model-api
  • POSWebApplication
  • ResidentSelfServicePortal
  • ResientSelfServicePortalConsolidated

Web Applications

  • customer-portal

odbdev02 – Database Server

Test

tomcattest01– Core Application Server

Tomcat Instances

  • at-remote-connection
  • authorization
  • backoffice
  • device-management
  • event-logger
  • model-api
  • POSWebApplication
  • ResidentSelfServicePortal
  • ResientSelfServicePortalConsolidated

Web Applications

  • customer-portal

tomcatintegrationtest01 – Integration Application Server

Tomcat Instances

  • client-access
  • integration-pcc
  • integration-vision

odbtest01– Database Server

Production

tomcatprod01– Core Application Server

Tomcat Instances

  • authorization
  • backoffice
  • model-api
  • POSWebApplication
  • ResidentSelfServicePortal
  • ResientSelfServicePortalConsolidated

tomcatintegrationprod01– Integration Application Server

Tomcat Instances

  • client-access
  • integration-pcc
  • integration-vision

tomcatinternal01– Internal Application Server

Tomcat Instances

  • device-management

fcadmin01– Admin/Device Application Server

Tomcat Instances

  • at-remote-connection
  • event-logger

odbprod02– Database Server

    • Related Articles

    • Redmine Development Task Workflow - Bug Fix and Feature Requests

      Support Team enters new task in Redmine with a Project of Support, Tracker of Customer Support, and Assignee of Development. Support will choose either the Bug Fix or Feature Request template. A member of the development team will check for new tasks ...

    • Development Training Resources

      Below are a list of resources that were compiled by the development team. Javascript https://eloquentjavascript.net/01_values.html JUnit User Guide https://junit.org/junit5/docs/current/user-guide/ Hibernate Quick Guide ...

    • Development Best Practices

      Development Best Practices Code Review Checklist Code Review Checklist Subversion Best Practices Branches Always put in comments when checking into subversion Create one branch per task Name branch with Redmine task number and short description (Ex. ...

    • Outlooks Rules for Development Team

      Outlooks Rules for Development Team Here are a list of Outlook rules that can be set up to help organize the inbox of the development team. Prometheus Alerts – Sender is alertmanager@fullcount.net Applications Alerts - Sender is alerts@fullcount.net ...

    • Redmine Development Task Workflow - New Community Instance

      Support Team enters new task in Redmine with a Project of Support, Tracker of Customer Support, Assignee of Development, and New Community Instance template. A member of the development team will check for new tasks under the development project as ...