Engineering

Engineering

Come for answers, stay for best practices. All we're missing is you.

 View Only
  • 1.  What shortcomings have you experienced in your organization on JAZZ installation/deployment?

    Posted Tue February 21, 2017 06:01 PM

    What shortcomings have you experienced in your organization on JAZZ installation/deployment, including end-user usage,  as well as IBM support requests?


    #Engineering
    #Sustainability


  • 2.  RE: What shortcomings have you experienced in your organization on JAZZ installation/deployment?

    Posted Fri February 24, 2017 10:44 AM

    When wanting to have PROD data being used in QA and/or DEV environments, I would like to see IBM development to improve the Server Rename to be much more/completely automated to insure a success. I have done this and had to have 2 IBM support folks, 1 IBM services person to help resolve that. It was so bad I swore I would never do it again unless there was improvement. 


    #Engineering
    #Sustainability


  • 3.  RE: What shortcomings have you experienced in your organization on JAZZ installation/deployment?

    Posted Sun March 12, 2017 01:41 AM

    Oh my, now that is a question!  Ours are haven't been great.  Even our last upgrade (we only take 1 upgrade annually now since 2011 as we always have issues), which went relatively smoothly, took all weekend.  And due to our current enterprise environment, involved way more departments than it should have (middleware group, DB group, etc).  My new-ish boss felt so bad, he promised me I wouldn't have to go through another upgrade again (we're looking at the cloud offerings).  I would love it if IBM could just isolate their code and offer feature groups (even if there are dependencies between them) so we could implement in a more devOps manner, and only have to test out/update training materials, etc. for a small portion of the tools.  But more than anything, script out and automate everything so we didn't have to follow elaborate instructions with odd tools that don't account for different client configurations (ok, we would still need to upgrade DBs and add servers, but hopefully only once in a very long while).


    #Sustainability
    #Engineering


  • 4.  What shortcomings have you experienced in your organization on JAZZ installation/deployment?

    Posted Sun March 12, 2017 11:55 AM
    I’d agree with the upgrade impression. We had done a half dozen test upgrades, just not with the current data set. The test upgrades went fairly smooth. The production run tool 21 hours due to a couple of projects implementing module baselines, and had so many problems that we had to do a full roll back. Thankfully the rollback process is easy.


    [cid:image001.jpg@01CE56ED.D9ED5290]




    Brian Erbe
    Systems Administrator, Division of Information Systems
    Virginia Department of Social Services
    801 East Main Street, Richmond VA 23219-2901
    Office: (804) 726-7019 - Cell: (804) 380-6518
    www.dss.virginia.govhttp://www.dss.virginia.gov
    [cid:image007.png@01CE56ED.8B625BC0]<http://www.youtube.com/user/virginiadss> [cid:image008.png@01CE56ED.8B625BC0] <https://www.facebook.com/VDSSGOV> [cid:image009.png@01CE56ED.8B625BC0] <http://twitter.com/VDSS>



    From: Carole Schwarz [mailto:jazzclm-ra@lists.imwuc.org]
    Sent: Sunday, March 12, 2017 1:41 AM
    To: JazzCLM-ra@lists.imwuc.org
    Subject: [JazzCLM-ra] - RE: What shortcomings have you experienced in your organization on JAZZ installation/deployment?


    Oh my, now that is a question! Ours are haven't been great. Even our last upgrade (we only take 1 upgrade annually now since 2011 as we always have issues), which went relatively smoothly, took all weekend. And due to our current enterprise environment, involved way more departments than it should have (middleware group, DB group, etc). My new-ish boss felt so bad, he promised me I wouldn't have to go through another upgrade again (we're looking at the cloud offerings). I would love it if IBM could just isolate their code and offer feature groups (even if there are dependencies between them) so we could implement in a more devOps manner, and only have to test out/update training materials, etc. for a small portion of the tools. But more than anything, script out and automate everything so we didn't have to follow elaborate instructions with odd tools that don't account for different client configurations (ok, we would still need to upgrade DBs and add servers, but hopefully only once in a very long while).

    -----End Original Message-----

    #Engineering
    #Sustainability