Scribd Logo
Upload

Welcome to Scribd!

  • 10 views

    Check Point 2034

    Uploaded by

    sushant

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Check Point 2034

    Uploaded by

    sushant
    10 views3 pages

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    10 views3 pages

    Check Point 2034

    Uploaded by

    sushant

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3

    Parts Strategic Solution-UAT TESTING AND DEPLOYMENT-PSS

     Reverse Engineer the functionality Developed for creation of part.


     Understand the Function Requirement and corresponding business logic.
     Understand the data model created to support the functionality.
     Understand the impact on Downstream system.
     Document the Solution Design Document for PSS.

    As an architect work with Iteration manager to prepare deployment plan.


    As an Architect I was analyzing the risk to PSS implementation and Deployment. I also can up
    with risk mitigation plan. We also prepared a rollback plan after getting the inputs from all
    the stake holders.

    Work with WWDC team to support the UAT for roll out of ETL and sftp jobs. During this UAT
    testing I gain a lot of Business knowledge about MTM and Parts and EOS details.
    WWDC uses Parts data from IBM to manage their inventory of part for customer orders.

    We understood in greater detail about End of Service logic and Parts life cycle.
    I was able to understand the big picture of TLS (Technology Life Cycle) and what does Non-
    Branded Multi-Vendor Support program is at IBM.
    I took initiative to find out range of products and service that are offered by IBM as part of
    MVS program.

    To get deeper understanding of MIW business aspect, I collaborated with Service Planning
    Executive.
    Thus, I was able to understand various functions of MVS and corresponding tools and IT
    system developed/ Maintained by CIO
    1) Product Life Cycle management Enovia
    2) Deal Portal – Service Delivery and solution design and Bidding.
    3) Service planning.
    4) Conga (contract management system)
    5) MVSPRD – For product translation.
    6) CCT – Is used for pricing.
    7) PIM
    8) OIM
    9) WWDC

    I have spent more than a year in Q2C subdomain, I have worked on project such as deal
    portal and vend hub.

    I have got significant depth in understanding of MVS business process and its impact on IBM.

    CIO CI/CD Migration and Technology Upgrade


    This project involved migration of Cirrus Dev Ops to New CIO CI/CD Devops pipeline.
    MIW application had vulnerabilities which required upgrade to spring boot 3.x. The Spring
    boot 3.x is supported by Java 17.

    Therefore, both Spring boot and Java version upgrade was undertaken. The spring boot 3.x
    upgrade required adoption of new Jakarta Persistence
    1) New CIO CI/CD migration we adopted community Pipeline for spring boot.
    2) I did a high-level discovery and then came up with a plan to implement CIO CI/CD
    3) We upgraded the Java JDK version to 17 and spring boot version to 3.x.
    4) I also worked on release management for CIO CI/CD deployments with help of the
    development team.

    Upgrade to Jakarta Persistence


    This involved adding update to package structure present in MIW from javax to jakarta which
    was done via tool available.
    Code changes were made in the application to support Jakarta. Extensive training was
    carried out to test all the database operations.
    1) Due to change in Java SDK and Spring Boot 3 version the persistence layer required to
    be upgraded.
    2) We had to do code changes to move to Jakarta Persistence API. Also, we upgraded to
    Hibernate 5.6 to support Jakarta.
    3) Due to upgrade to Hibernate version, the current code required to be refactored at
    various places to make it work.
    4) In spring boot 3 and Spring Security 6 few key methods in Spring security were
    deprecated.
    5) We upgrade MIW code to incorporate new security code and corresponding
    dependencies. We implement SAML 2.0 using spring security.
    6) We also found that Method based security was also impacted. We made the required
    code changes and tested the entire application.

    Upgrade Spring Security to Spring Security version 6


    In spring boot 3x most of the supporting security method are deprecated. I updated the
    code to implement new methods for SAML and Ldap.

    Multiple Entry point Authentication was also impacted, and corresponding updated code
    was added.
    1) In spring boot 3 and Spring Security 6 few key methods in Spring security were
    deprecated.
    2) We upgrade MIW code to incorporate new security code and corresponding
    dependencies. We implement SAML 2.0 using spring security.
    3) We also found that Method based security was also impacted. We made the required
    code changes and tested the entire application.
    4) I also worked on release management for CIO CI/CD deployments with help of the
    development team.

    You might also like