6 Replies Latest reply on Jun 28, 2012 1:11 AM by piyush pandey

    Patch Remediation Batch Job BL 7.6 scenario

      Hi,

      We have BL 7.6 Implemented in our environment. We are trying to create a blcli based Windows Patching Solution. Now After running ht epatch analysis when we try to creatr patch remediation job for multiple servers using blcli and try to execute it ,the execution is happening in a strange way.

       

      Here First the batch job is created. Under the bach job if there are multiple deploy jobs then first deploy job is exectued under batch job. Ones this deploy job gets completed then only next deploy job gets executed. We have a very limited downtime window of 1 hour. Some times single deploy job takes most of the time and the next jobs have not been executed yet and they get executed outside the desired window.

       

      Can we set any property so that the batch job for patch remediation in BL 7.6 Executed all the deploy job in parallel and not in serial order.

      Can we use some property instance that we can add to patch analysis job or something?

       

      I know there is an option in batch job to execute the job in parallel but how can we setit so that using auto remediation for windows patch analysis it would be automatically set.

        • 1. Patch Remediation Batch Job BL 7.6 scenario

          I think there may have been a bug at some point where the Batch Job was being created with 'sequential' option checked, rather than 'in parallel' during auto-remediation....

           

          what the appserver version?

          what's the contents of your script?

          • 2. Patch Remediation Batch Job BL 7.6 scenario

            H,

            Script basically performs following actions:

            1.) Create Patch Analysis Job with Auto Remediation from a White List

            2.) Set Deploy Job Options for necessary reboot option.

            3.)Executes the Blcli as per local time 1am for all the servers.

             

            Our BL version is 7.6.0.293.

            • 3. Patch Remediation Batch Job BL 7.6 scenario

              You mentioned that the jobs are executed sequentially, which implies that you are executing the Batch Job, so I take it that in step 3 you are executing the Batch Job, correct?

               

              Here's is what you could do:

              In step 2 when you set the Deploy Job options for necessary reboot, you could also set the schedule options to execute the Deploy Jobs at a specific time (when you would normally run step 3).

               

              New way:

              1.) Create Patch Analysis Job with Auto Remediation from a White List

              2.) Set Deploy Job Options for necessary reboot option and schedule options

               

              At the scheduled time all the deploy options will run at once, so the Batch Job is not even used in this case, and the deploy jobs are executed in parallel.

              • 4. Patch Remediation Batch Job BL 7.6 scenario

                Hi ,

                So there are 2 problems to it:

                1.) When you we use set auto remediation and execute the patch analysis(in BL 7.6) it automamtically create the patch job and tries to excecute it. We saw that when this batch job is created automatically the default option to run the deploy job in the batch job in sequence check box is automatically selected.

                Is there any way we using unreleased blcli we can remove this thing so that deploy job under batch job execute in parallel.

                 

                 

                2.) When we try to add schedule usng a blcli we cannot select the option which time zone to select( same thing we can set while adding the schedule using GUI but cannot do using cli). Also when we try to run the job the job execution has probelm during scheduling. We showed Bill Robinson our use case today he also found it strange.

                • 5. Patch Remediation Batch Job BL 7.6 scenario

                  JobGroup="/Folder"

                  JobName="BatchJobName"

                  blcli_execute BatchJob getDBKeyByGroupAndName "$JobGroup" "$JobName"

                  blcli_execute BatchJob setParallel true

                  blcli_execute Job update

                   

                  The last two commands are unreleased. The 'update' command is important, as it will actually save the job with the new setting. After having "updated" the job, if you need to reference it again within this same script, you need to run the getDBKeyByGroupAndName again, so that you get the new db key of the latest version, rather than old.

                  • 6. Patch Remediation Batch Job BL 7.6 scenario

                    Hi,

                    Thanks Lazar. We were able to change the execution to parallel. We will update as soon as we are able to do 2 step patching i.e stage,simulate and Commit in 2 steps.