nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

when primary open deploy RX fails

chandrachv

Hi

I am trying to deploy the files to production using workflow. i wrote a deploy.ipl file to do that job. but here I have two open deploy recievers on production server. when primary receiver is down the deployment should happen in secondary receiver. I have nmap unix command to get the status of primary receiver whether it is up or down.
so where should i incorporate this nmap command code?i tried to write the code in deploy.ipl where we deploy using iwod command. but here i am not getting the idea how to switch over to the secondary rx? if status is success i have to use primary rx,if staus is down i have to use secondary rx..

i hope you people understand my requirement..
it would be really helpful if u give me any suggestions..

thanks in advance..

Find more posts tagged with

Comments

Adam Stoller

I can think of a couple of ways to do this off the top of my head:

prasad54

I have the same problem buddy.
Thank you very much buddy for your suggestions...i will try to execute your idea..however i didnt get u fully...do u want me to pass the useNode value to deploy command ?
i was thinking of doing this using workflow tasks...first i will verify the status of primary RX in an external task using nmap command.for this task i will use success and failure attributes to transit to the next tasks according to the status of Primary RX.

i will use the deploy command in the next transition(external) task by passing secondary Rx node name as an argument which is configured in deployment conf file or odnodes.xml.

what do u think of my idea...plz reply me if it is a good one to implement.

anyways thanks for ur suggestions once again.

bye.

Adam Stoller

I have the same problem buddy.
Thank you very much buddy for your suggestions...i will try to execute your idea..however i didnt get u fully...do u want me to pass the useNode value to deploy command ?
i was thinking of doing this using workflow tasks...first i will verify the status of primary RX in an external task using nmap command.for this task i will use success and failure attributes to transit to the next tasks according to the status of Primary RX.

i will use the deploy command in the next transition(external) task by passing secondary Rx node name as an argument which is configured in deployment conf file or odnodes.xml.

what do u think of my idea...plz reply me if it is a good one to implement.

anyways thanks for ur suggestions once again.

bye.

Your deploy.ipl script is already an externaltask script - right? Why bother having a separate externaltask script to check the status of your receivers? Do it all-in-one:

Another alternative is to define a quorum of 1 and do a fan-out deployment to both receivers - as long as one is available, the deployment should work.Of course, none of this deals with the fact that if your receivers are bouncing up and down such that deployment A goes to "prod1" and deployment B goes to "prod2" - you have a mixed up production environment such that neither of the receivers is known to possess a complete set of the production content. Personally, if I have two receivers in my production environment - I'd want the deployment to succeed to both receivers or fail and alert someone that there's a problem in the production environment...

chandrachv

thank you guys i appreciate the effort you guys put into,

i think this will solve my problem....

chand