This documentation supports an earlier version of BMC Helix IT Service Management on-premises deployment. To view the documentation for the latest version, select 23.3.04 from the Product version picker.


Preparing for migration

Perform the following tasks to prepare for the data migration of Remedy on-premises to BMC Helix Service Management on-premises:

Prepare for migration.png

Task 1: To create documents required for planning your migration project

Create the following documents and use them to assess and define the scope of work for the migration. This information helps you plan your implementation and data migration activities. 

  1. Create your implementation planning document—Add details of your existing environments and applications, integrations, configurations, custom plugins or Java code, and custom AI jobs. Include several script files for activities such as  reviewing workflow and field-level customizations. Review the document to understand the project requirements and define the scope of work for the migration. 
    Review the following points to prepare an implementation planning document:

    Review and record the existing integrations
    • Summary about the integrations and how the integrations work
    • Database integrations
    • Details about plug-in or file system integrations
    • Files to be added to any of the Remedy file systems
    • Custom workflow that incorporates a run process of custom scripts or binaries
    • Custom plug-ins in any integration
    • Third-party applications
    Review and record your existing noncontainer environment

    Component

    Description

    Configurations in your environment

    Specify the number of configurations in your environment.

    Implementation of archive feature

    We  recommend that you stop archiving your data when you start with the data migration process. Resume the data archiving after you complete the migration process and  go-live.

    Products and product versions deployed in your current environment

    Specify the list of products, product versions, and sizing.

    Total number of users

    Specify the total user count.

    Number of Action Request System users

    Specify the number of Action Request System users.

    Number of BMC Helix Digital Workplace users

    Specify the number of BMC Helix Digital Workplace users.

    Maximum concurrent users

    Specify the concurrent user count.

    Customizations in your environment

    Specify the number of customizations in your environment.

    Total number of custom forms

    Use the following command to find the total number of custom forms:
    select count(*) from arschema where overlayProp = 4

    Schema ID of custom forms

    Use the following commands to find the schema ID of custom forms:

    select schemaid, resolvedname "Form Name",
    case when schematype = 0 then 'Invalid Form Type'
    when schematype = 1 then 'Regular Form'
    when schematype = 2 then 'Join Form'
    when schematype = 3 then 'View Form'
    when schematype = 4 then 'Vendor Form'
    when schematype = 5 then 'Inheritance Form'
    when schematype = 6 then 'Place Holder Form'

    end as  SchemaType,
    case
    when overlayprop = 0 then 'Unmodified'
    when overlayprop = 1 then 'Base'
    when overlayprop =  2  then 'Overlay'
    when overlayprop = 4 then 'Custom' end as
      CustomizationType
    from arschema a where a.overlayprop = 4

    Overlay objects count

    Use the following commands to find the overlay objects count:

    select ((select count(*) from arschema where overlayProp = 2) +
    (select count(*) from actlink where overlayProp = 2) +
    (select count(*) from filter where overlayProp = 2) +
    (select count(*) from escalation where overlayProp = 2) +
    (select count(*) from field where overlayProp = 2) +
    (select count(*) from vui where overlayProp = 2) +
    (select count(*) from char_menu where overlayProp = 2) +
    (select count(*) from arcontainer where overlayProp = 2)
    ) as totalOverlays,

    (select count(*) from arschema where overlayProp = 2) as Overlay,
    (select count(*) from actlink where overlayProp = 2) as actlinkOverlay,
    (select count(*) from filter where overlayProp = 2) as filterOverlay,
    (select count(*) from escalation where overlayProp = 2) as escalationOverlay,
    (select count(*) from field where overlayProp = 2) as FieldOverlay,
    (select count(*) from vui where overlayProp = 2) as vuiOverlay,
    (select count(*) from char_menu where overlayProp = 2)  as menuOverlay,
    (select count(*) from arcontainer where overlayProp = 2) as arcontainerOverlay

    List of all fields and views having overlays

    Use the following commands to find the list of all fields and views having overlays:
    select b.resolvedname "Form Name", a.fieldname "Field Name" , 'Field' "Object Type" 
    from field a, arschema b where a.schemaid = b.schemaid and a.overlayprop=2
    union
    select b.name "Form Name", vuiname "View Name", 'View' "Object Type"
      from AR_System_Metadata__vui  a, arschema b where a.schemaid = b.schemaid and a.overlayprop=2

    List of active links, filters, escalations, menus, and  overlays

    Use the following commands to find the list of active links, filters, escalations, menus, and overlays:

    select  resolvedname "Object Name", 'Active Link' "Object Type"
    from actlink where 
    actlink.overlayprop = 2
    union
    select resolvedname "Object Name", 'Filter' "Object Type"
      from filter where 
    overlayprop = 2
    union
    select resolvedname "Object Name", 'Esclation' "Object Type"
      from escalation where 
    overlayprop = 2
    union
    select resolvedname "Object Name", 'Menu' "Object Type"
      from char_menu  where 
    overlayprop = 2
    union
    select resolvedname "Object Name", 'Container' "Object Type"
      from arcontainer  where 
    overlayprop = 2 order by 2

    List of binaries such as custom plugins and run process binaries

    Specify the list of binaries.

    View form or vendor form details

    Specify the view or vendor form details.

    Custom files in the server file systems

    Specify the number of custom files in the server file systems.

    Remedy objects having Run process command

    Use the following command to find the objects:

    select distinct name, 'Active Link' "Object Name" from actlink where actlinkId in (select actlinkid from actlink_process where overlayGroup = 1)
    union
     select distinct name, 'Filter' "Object Name" from filter where filterId in (select filterid from filter_process where overlayGroup = 1)

    Remedy objects having SQL command

    Use the following commands to find the objects:

    SELECT distinct name, 'Active Link' "Object Name" FROM actlink where actlinkId in (select actlinkId from actlink_sql where overlayGroup = 1)
    union
    SELECT distinct name, 'Active Link' "Object Name" FROM actlink where actlinkId in (select actlinkId from actlink_set where overlayGroup = 1 and (assignShort LIKE '107\1%' OR assignLong LIKE '107\1%'))
    union      

     SELECT distinct name, 'Filter' "Object Name" FROM filter where filterId in (select filterId from filter_sql where overlayGroup = 1)
    union
    SELECT distinct name, 'Filter' "Object Name" FROM filter where filterId in (select filterId from filter_set where overlayGroup = 1 and (assignShort LIKE '107\1%' OR assignLong LIKE '107\1%'))

    Custom fields in BMC Reserved field ID range

    Specify the number of custom fields in BMC Reserved field ID range.
    For information about the BMC Reserved field ID range, see Reserved field ranges in AR System documentation.

    Use the following command to find the fields that you have created in the BMC Reserved field ID range:

    select b.resolvedname "Form Name", b.schemaid "Form ID", a.fieldname "Field Name" ,a.fieldid "Field ID" ,
    case
    when b.overlayprop = 0 then 'Unmodified'
    when b.overlayprop = 1 then 'Base'
    when b.overlayprop =  2  then 'Overlay'
    when b.overlayprop = 4 then 'Custom'
     end as
      CustomizationType
     from field a, arschema b where a.schemaid = b.schemaid and
    b.overlayprop >4 and
    ((a.fieldid >=1 and a.fieldid <=99) or
    (a.fieldid >=101 and a.fieldid <=149) or
    (a.fieldid >=150 and a.fieldid <=159) or
    (a.fieldid >=200 and a.fieldid <=399) or
    (a.fieldid >=450 and a.fieldid <=469) or
    (a.fieldid >=600 and a.fieldid <=699) or
    (a.fieldid >=700 and a.fieldid <=750) or
    (a.fieldid >=800 and a.fieldid <=810 ) or
    (a.fieldid >=820 and a.fieldid <=880 ) or
    (a.fieldid >=900 and a.fieldid <=999) or
    (a.fieldid >=1000 and a.fieldid <=1100) or
    (a.fieldid >=1101 and a.fieldid <=1399) or
    (a.fieldid >=1500 and a.fieldid <=1525) or
    (a.fieldid >=1700 and a.fieldid <=1799) or
    (a.fieldid >=2000 and a.fieldid <=2299) or
    (a.fieldid >=2300 and a.fieldid <=2699) or
    (a.fieldid >=10000 and a.fieldid <=14999 ) or
    (a.fieldid >=15000 and a.fieldid <=15999) or
    (a.fieldid >=17000 and a.fieldid <=17399) or
    (a.fieldid >=18000 and a.fieldid <=19999) or
    (a.fieldid >=20000 and a.fieldid <=39999) or
    (a.fieldid >=40000 and a.fieldid <=40499) or
    (a.fieldid >=53000 and a.fieldid <=53199 ) or
    (a.fieldid >=60000 and a.fieldid <=60999) or
    (a.fieldid >=536870999 and a.fieldid <=536880999) or
    (a.fieldid >=536881000 and a.fieldid <=536890000) or
    (a.fieldid >=610000000 and a.fieldid <=610001000) or
    (a.fieldid >=610001001 and a.fieldid <=610001100) or
    (a.fieldid >=900000000 and a.fieldid <=909999999) or
    (a.fieldid >=1000000000 and a.fieldid <=1999999999 ))

    Authentication used such as SAML and LDAP

    Specify the type of authentication used.

    Details about email and notifications usage

    Specify if you are using  email and notifications for events such as incidents and approvals.

  2. Create your implementation, data migration, and project plans—Based on the data assessment from the Implementation planning document, create the following plans:
    • Implementation plan—For development work that includes code updates, workflow customizations, integrations, configurations, custom plugins or Java code, custom AI jobs, and any new development work.
    • Data migration plan—For form-level, table-level, and field-level data customizations.
      To create the data migration plan:
      • Evaluate your data volume and database size.
      • Investigate and document any custom forms or field updates to be added to the BMC Helix migration pack.
    • Project plan template—Create a plan that includes phases of your migration project.

Task 2: To install BMC Helix Data Manager, Developer Studio, and other client tools

  1. Download and install BMC Helix Data Manager.
    BMC Helix Data Manager is currently available only to customers in the Controlled Availability (CA) program. Create a support ticket for BMC to send you the required password to download the BMC Helix Data Manager installation files.

    Best practice
    We recommend you use the latest version of BMC Helix Data Manager.

    If you encounter data migration issues due to customizations, we recommend that you contact BMS Service resource or a HDM certified partner to perform the HDM data migration.

    • For more information about planning and installing the BMC Helix Data Manager installation, see Planning and Installing in BMC Helix Data Manager documentation.

    • For information about downloading the installation files, see Downloading the installation files in BMC Helix Data Manager documentation.

    • For more information about available migration packs, and downloading them, see Licensing BMC Helix Data Manager in BMC Helix Data Manager documentation.

    • Use the BMC Helix Data Manager tool to get accustomed to the migration process. You can perform all the data migration steps on your on-premises system except the actual import of data that requires transferring the exported data through your FTP server.

    • We recommend that you complete the BMC Helix Data Manager 21.x: Fundamentals Migrating training.

  2. Download and install Developer Studio.
    See Accessing and navigating Developer Studio in BMC Helix innovation Suite documentation.

  3. Download and install AR Import.
    See Importing data into forms by using Data Import in BMC Helix innovation Suite documentation.

  4. Download and install BMC Digital Workplace OnPrem Data Migration Tool (Data Migration utility)
    Download the BMC Helix Digital Workplace OnPrem Data Migration Tool file from EPD. Access the EPD website by providing your BMC Support credentials and complete the Export Compliance Form, if prompted.
    Make sure that you download the latest version of the Data Migration utility.

Important

The utility uses the Java version same as that of your AR System server.

Task 3: To run license compliance checks

Run the license compliance checks to convert your existing classic licenses to a simplified and easy-to-understand bundled licensing model.

  1. Perform the following tasks to complete license assessment on the current system:
    1. Download the License Compliance Utility from the BMC Electronic Product Distribution (EPD) site.

    2. Run the License Compliance Utility in assessment mode to evaluate the classic fixed, floating, and bundled licenses that you must purchase.
      See Moving to the bundled license model by using the Bundled License Conversion Utility in BMC Helix innovation Suite documentation.
      The utility generates an Excel report about your license compliance and helps you to decide on the required bundled licenses you must purchase. 

    3. Purchase the relevant fixed and floating bundled licenses for BMC Helix Innovation Suite platform and application licenses.
  2. Perform license assessment and conversion on the BMC Helix systems during migration.
    During migration, you must assess and convert the People profile data licenses multiple times. To convert the People profile data licenses, run the License Compliance Utility in assessment mode and then in the conversion mode. Make sure that you run the License Compliance Utility on the new development environment during the following stages:

Best practice
We recommend that you convert your existing people profile data from classic to bundled licenses before you go live.

Where to go from here

Migrating-Remedy-on-premises-to-BMC-Helix-Service-Management-on-premises

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*