Telecommunications Company OVERVIEW A IT, (AWS). SQL The billing application team had already migrated Abend-AID Fault Analytics to AWS. Since iStrobe was running on an internally managed Windows server, they were mandated to migrate iStrobe to AWS if possible. They explored moving iStrobe to USS with Db2 on the mainframe but were told they could not use Db2 due to the cost involved. The iStrobe administrator explored moving iStrobe from Windows to z/Series Linux; however, he was shot down again due to the cost of the RDMBS license to do so. DB, supplied by Strobe, is not robust enough for their enterprise use of Strobe/iStrobe. With the CIO mandate, they had to explore options to move iStrobe to AWS. It was essential that they could keep this in service and adapt the environment to AWS if possible. The CIO wanted to cut infrastructure costs and move to a pay-as-we-use model by moving any internally managed servers to AWS in the cloud. Simultaneously, the CIO was tracking all servers still in use and keeping track, weekly, of efforts to move any server-based applications to AWS. The administrator for iStrobe and other Compuware tools, including Topaz, CES and Abend-AID Fault Analytics, contacted Compuware Product Manager Spencer Hallman. Spencer got Product Manager John Dannenberg and Customer Solutions representative Rick Webb involved. John and Spencer both agreed, as with Abend-AID Fault Analytics, iStrobe could be run via AWS. The administrator worked closely with Rick to migrate his current iStrobe internal Windows environment to a Windows environment on AWS. Rick was helpful in providing guidelines for the TLS 1.2-secured environment needed. There were testing challenges getting iStrobe profiles sent from Strobe users on the mainframe to iStrobe on AWS. Each user uses a batch job to send iStrobe profiles to the iStrobe server for the profile database.
Telecommunications Company OVERVIEW A IT, (AWS). SQL The billing application team had already migrated Abend-AID Fault Analytics to AWS. Since iStrobe was running on an internally managed Windows server, they were mandated to migrate iStrobe to AWS if possible. They explored moving iStrobe to USS with Db2 on the mainframe but were told they could not use Db2 due to the cost involved. The iStrobe administrator explored moving iStrobe from Windows to z/Series Linux; however, he was shot down again due to the cost of the RDMBS license to do so. DB, supplied by Strobe, is not robust enough for their enterprise use of Strobe/iStrobe. With the CIO mandate, they had to explore options to move iStrobe to AWS. It was essential that they could keep this in service and adapt the environment to AWS if possible. The CIO wanted to cut infrastructure costs and move to a pay-as-we-use model by moving any internally managed servers to AWS in the cloud. Simultaneously, the CIO was tracking all servers still in use and keeping track, weekly, of efforts to move any server-based applications to AWS. The administrator for iStrobe and other Compuware tools, including Topaz, CES and Abend-AID Fault Analytics, contacted Compuware Product Manager Spencer Hallman. Spencer got Product Manager John Dannenberg and Customer Solutions representative Rick Webb involved. John and Spencer both agreed, as with Abend-AID Fault Analytics, iStrobe could be run via AWS. The administrator worked closely with Rick to migrate his current iStrobe internal Windows environment to a Windows environment on AWS. Rick was helpful in providing guidelines for the TLS 1.2-secured environment needed. There were testing challenges getting iStrobe profiles sent from Strobe users on the mainframe to iStrobe on AWS. Each user uses a batch job to send iStrobe profiles to the iStrobe server for the profile database.
Customer%20Success%20Story%20GK%20Telecommunications%20%20iStrobe%20AWS.docx