Current Architecture

<Add your current architecture details and diagrams capturing integration details & flow (in/out) >

Environment details

Update the table with your current environment detai;ss  

Sl. No	Environment (Dev/QA)	Operating System (OS)
1
2
3
4
5
6

Database details

Database Type	Current Database  (Y/N)	Version	Target Database for Helix version (Y/N	Size
Oracle
SQL Server
Postgres

Product details

Please indicate the products in On-Prem	Using  (Y/N)	Version
Action Request System
BMC Helix CMDB
BMC Helix ITSM
BMC Helix Incident
Problem
Change
Asset
Release
BMC Helix ITSM: Knowledge Management
BMC Helix ITSM: Smart IT
BMC Helix ITSM: Smart Reporting
BMC Helix Digital Workplace

Integrations

Update details about each integration and their implementation details, and also methods used for integration,

Sl.No	Integration Name	Details	Integration method   (Rest API, Web Services, Database Integrations, Plug-in Integrations…etc)
1
2
3

User and system information

Sl. No	Task Name	Notes
1	Is Archiving enabled	Y/N
2	IS Database case sensitive	Y/N
3	Is Database Unicode	Y/N
4	Number of users in the system
5	Number of Action Request System users
6	Number of BMC Helix Digital Workplace users
7	Maximum concurrent users
8	Total number of custom forms
9	Total number of Overlay forms
10	Authentication used such as SAML and LDAP
11	Details about email and notifications usage	Specify if you are using  email and notifications for events such as incidents and approvals
12	No# of Resources that will be working on the upgrade project.

Prerequisites

Perform these steps in your current AR Server environments. 

1. To optimize the upgrade process, convert overlays to granular overlays.   
   This reduces the number of overlays and simplifies reconciliation during the three-way reconciliation process post-upgrade. For more details, see Moving your AR object customizations to a new target system .
   Information

   Important

   You must perform this step in your current environment during a maintenance window to prevent disruptions. 

2. Run Configuration Checker to capture custom configurations. For more details, see Performing configuration checks - Documentation for Remedy Deployment 20.02 - BMC Documentation .
   Information

   Important

   The process is non-intrusive and does not require an outage window. The configurations captured serves as a reference for adding or updating custom settings in the Helix Cloud environments. 

3. Download latest version of following client tools or utilities and install them on the staging server. See Preparing for migration.
4. Review and record the existing integrations

   Tasks	On-prem	SaaS
   Download and install Helix Data Manager (HDM) tool	Required	Required. Additional installation of  HDM tool will be made available as part of the staging server provisioned.
   Download and install latest version of Developer studio	Required	Required (needs to be installed on an On-Prem VM)
   Download and install AR Import tool	Required	Required (needs to be installed on an On-Prem VM)
   Download and install BMC Digital Workplace OnPrem Data Migration Tool (Data Migration utility)	Required	Required. Additional installation of  DWP utility will be made available as part of the staging server provisioned.
   Download and install the License Compliance Utility	Required	Required (needs to be installed on an On-Prem VM)
   Download and install Workflow Migration utility	Required	Required (needs to be installed on an On-Prem VM)

5. Update a summary of the database integrations, including their purpose and functionality. Make sure to describe how these integrations are connected or utilized by the AR System Server, detailing the methods of data exchange and interaction.

   Information

   Important

   • Database Read-Only Integrations – Supported on-prem; requires additional approval from SaaS Migration. 
   • Database Read/Write Integrations – supported on-prem; Requires redesign for SaaS migration. 

   Sl .No	Integration Name	Read only / RW	Integration Details	Notes
   1
   2
   3
   4
   5
   6

6. Update the summary of the custom plug-ins or file system integrations, including their purpose and functionality. Ensure that to describe how these integrations interact with the AR System Server, including the data exchange and integration methods. 

   Information

   Important

   If the integration requires redesign, assess the feasibility of modifications. 

   For static file-based integrations, consult the SaaS team to determine if they can be incorporated into a container.
   This might involve additional costs for SaaS migration.

    

   Sl.No	Integration Name	Permitted	Non-permitted	Notes
   1
   2
   3
   4
   5
   6

7. Update the summary of the files used in the current system integrations, to be added to AR Server to support above plug-in / file system integrations. Describe how these integrations are connected to or utilized by the AR System Server. (note: this may involve additional costs for SaaS migration). 
   For custom plug-ins developed using AR APIs or Java APIs, see the pluginsvr_config.xml for configuration details. 
   For additional deployment steps, see Deploying custom plug-ins.

   Sl.No	Integration Name	Redesign required?	Notes
   1
   2
   3

8. Update the summary of the third-party applications integrated into the current system, including their purpose and functionality. Describe the integration methods used and how these applications interact with the system.

   Document current method and refer to the following recommended methods -  

   • AR API 

   • Java API 

   • Rest API 

   • Web services 

   Sl.No	Third-party application Name	Description
   1
   2
   3
   4

   Workflow customizations :

   Custom Fields in the BMC Reserved field ID Range on overlay forms

   Analyze your current system for current customizations and identify conflicting field Ids.

   Sl. No	Form Name	Field ID	Field Name	Notes
   1
   2
   3
   4
   5
   6

   Remedy objects having SQL command

   Analyze your current system for current customizations and identify workflow objects using SQL commands:

   Sl.No	Object Name	Type	Rework needed?
   1
   2
   3
   4
   5
   6

   Remedy objects having Run process command

   Analyze your current system for current customizations using “Run Process” command:

   Sl. No	Object Name	Type	Rework needed?
   1
   2
   3
   4
   5
   6

   List of overlay objects

   Analyze your current system to identify overlay workflow objects (Active links, Filters, Escalations, Menus, Fields, Views): 

   Sl. No	Object Name	Type	Rework needed?
   1
   2
   3
   4
   5
   6

   AI Jobs

   Review and document transformation steps that has reference to any files placed in the server and/or has a connection to database for any write activities.  

   Sl. No	Job Name	Using Direct SQL ?	Using File system?	Rework needed?
   1
   2
   3
   4
   5
   6

   Check License Compliance

   To determine the number of bundled license packs needed for your new environment, run the License Compliance tool in assessment mode to generate a report. During implementation, you can use the same tool in conversion mode to transition existing classic licenses to the bundled license format. For more information, see Preparing for migration .