BMC ITSM 19.x Upgrade & Migration Project (On Premise)
Experience highlights:
Modules:
• ITSM, CMDB, ADDM, SmartIT
Roles:
As a member of a cross-functional and plurinational team, the main roles where I was involved were:
• Identification and prioritization of activities through SCRUM technology
• Migration of different types of integrations (Email, Web Services, REST, RDWH, etc.)
• Identification analysis of the different custom/overlay objects related to the different integrations
• Proposal of deprecation of developments to the new version
• Proposal for possible improvements or new approaches in existing integrations
• Facing a double change in technology (Oracle -> MS SQL, Unix / Linux -> Windows)
• Identification/adaptation of different database objects (Tables, Views, Indexes, Grants)
• Identification/adaptation of different Unix/Linux commands/scripts to Windows (using Powershell)
• Realization of basic functional tests of validation of the adapted integrations
• Migration of these integrations to the user validation environment
• Generating documentation of each integration in shared resource (Confluence)
• Agile collaboration with team members in both daily-SCRUMs and spontaneously
• Show interest in new technologies (CMT of Alderstone) that is being used in data migration
Main Activities
1. Platform Migration
On an environment with a very high percentage of customizations, my main task was to migrate the different existing integrations.
We are talking about a very high number of integrations (more than 50) and based on different technologies (Email, Web Services, REST, RDWH, LDAP) and that could accommodate different customer needs:
- Generation and exchange of emails between Remedy systems.
- Generation and exchange of tickets (INC, CHG, PBM) between Remedy systems
- Generation and sending of dynamic notifications
- Reporting via DWH to import into Remedy and generate dynamic CIs, relations between CIs, relations against People and People Organizations, CI unavailability, CI Blackouts, etc.
- Reporting via DWH to import in Remedy and generate Cost Center information
- Integration of people information via LDAP reading (and CIS)
- etc.
For each of the integrations different activities were performed:
- Identification of the functionalities (Know-how-transfer, documentation search, workflow analysis).
- Adaptation of each of the integrations to new technological changes (from Unix/Linux to Windows, from Oracle to SQL):
a) modification of the automatic processes governing the integrations to ensure their correct operation under Windows
(transforming, modifying or generating new scripts based on Powershell where before there were Unix/Linux scripts)
b) modifying also these processes for their correct operation on the new DB engine.
2. Analysis and implementation of new functionalities on integrations.
In a second phase, in collaboration with the client and based on the prioritization indicated by the client, new functionalities were implemented on existing integrations.
Also, re-engineering was done to propose improvements in the performance of these integrations, many of them vital for the customer (RDWH, SAP, APSBW, MDM, LDAP).
3. Requirements gathering, analysis and development of new REST-based integrations.
In parallel, activities were carried out to implement new integrations that have allowed the Client to improve processes that, to date, were based on solutions that were not very robust.
An example of a new integration would be RZCampus, where a system based on REST API was implemented, which allows the communication of 3 major areas of the Client.
4. Documentation
During all the phases of this project, deep and detailed documentation was carried out in Confluence, for each of the integrations, and of each of the configurations of such a customized system.
All these main activities, outlined only in broad strokes, could not have been carried out without the support of a transversal and collaborative team and relying on technologies such as SCRUM/SAFe, both in the programming of PI's (with its sprints and stories) and in our day-to-day work (dailys) and JIRA.