Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  • In this stage, it is necessary to analyze the existing AIS infrastructure and configuration.

  • Following the analysis report, recommendations can be made regarding the appropriate infrastructure for Adeptia Connect (clustered or non-clustered).

  • Provide a detailed explanation of the migration process to the client

E.g. - A client named ABC currently has the following AIS setup in place.

TEST

(Kernel & Webrunner on Same Instance)

Non-Clustered

QA

(Kernel & Webrunner on Same Instance)

Non-Clustered

PROD

(Kernel & Webrunner on Same Instance)

Non-Clustered

  • AIS v6.6

  • 1 Instance

  • Core- 2

  • 16 GB RAM

  • 200 GB Storage

  • Linux

  • Backend DB- Oracle 19C

  • Quartz DB- HSQLDB

  • Log DB- SQL- Oracle 19C

  • AIS v6.6

  • 1 Instance

  • Core- 1

  • 8 GB RAM

  • 100 GB Storage

  • Linux

  • Backend DB- Oracle 19C

  • Quartz DB- HSQLDB

  • Log DB- SQL- Oracle 19C

  • AIS v6.6

  • 1 Instance

  • Core- 2

  • 16 GB RAM

  • 100 GB Storage

  • Linux

  • Backend DB- HSQLDB

  • Quartz DB- HSQLDB

  • Log DB- SQL- Oracle 19C

Given the existing AIS infrastructure, Discussion with the Client, and data transaction volume, it is possible to provide recommendations and define the scope of work for the migration.

E.g:

  • In-Scope

    1. Environment Migration - AIS V6.6 to AC V3.7 on Premises

    2. Set Up AC Environment with the latest version of Adeptia

    3. Setup 2 new Non-Prod (Test and QA) non-clustered environments

    4. Setup 1 new Prod clustered environment

    5. Perform current solution migration from AIS to AC V3.7 on-premises

    6. Assist with QA/UAT

  • Out-Scope

    1. Current solution optimization is not part of the scope

Once the scope has been defined, Adeptia will now proceed with guiding the client through the migration process.

  • Infrastructure Setup: 

    1. Identify the infrastructure resources for the AC application

    2. Procure and provision the AC servers

    3. Deploy and configure AC

  • Analysis and Phase Planning:

    1. Perform impact analysis for migration integration (database endpoints, connectivities, web services) 

    2. Determine the migration plan

    3. Determine the QA process for verification and testing

    4. Determine Rollback plan 

  • Migration and Rollout: 

a. Adeptia migrates AC-compatible QA Objects to AC Test and QA environments

b. Adeptia validates Objects on Test and QA environments

c. Adeptia migrates AC-compatible PROD Objects to the AC PROD environment

d. Adeptia validates Objects in the PROD environment

e. The client performs testing on AC PROD environments

The finalized migration plan from AIS to AC On-Premises has been shared with the client.

a. AIS to AC Migration (on-premise - New Infrastructure)

b. Migration Duration: Approx. 8 Weeks (Depending on UAT)

c. Adeptia Backend, Logs, and quartz database need to be migrated from HSQL to Oracle as HSQL is not supported in AC

Recommended Adeptia Connect Infra:

TEST

(Kernel  & Webrunner on Same Instance)

Non-Clustered

QA

(Kernel  & Webrunner on Same Instance)

Non-Clustered

PROD -

Non-Clustered Connect Server & Portal on Same Instance)
Clustered

  • Adeptia Connect V3.7.2

  • 1 Instance

  • Core- 8

  • 32 GB RAM

  • 200 GB Storage

  • Linux

  • Backend DB- Oracle 19C

  • Quartz DB-  Oracle 19C

  • Log DB- SQL- Oracle 19C

  • Adeptia Connect V3.7.2

  • 1 Instance

  • Core- 8

  • 16 GB RAM

  • 100 GB Storage

  • Linux

  • Backend DB- Oracle 19C

  • Quartz DB-  Oracle 19C

  • Log DB- SQL- Oracle 19C

  • Adeptia Connect V3.7.2

  • 2 Instances

  • Core- 16

  • 32 GB RAM

  • 100 GB Storage

  • Linux

  • Backend DB- Oracle 19C

  • Log DB- SQL- Oracle 19C

  • Quartz DB-  Oracle 19C

  • Shared Drive- 500 GB