Hello Vijay, I don't know what is your aim, but here we are doing the following: - Stop the WebLogic server (domain); - Copy the deployment artifacts to the place where WebLogic looks for them; - Clear the WebLogic (domain) caches; - Start the app.server (WL domain). For a couple of years this works like a charm. Well, when we add new applications to the domain we need to manually deploy and start them via the administrative console, but this happens just a couple of times per year so we don't strive to automate it.
You can easily stop a remote server using the t3 protocol. Unfortunately you can not start it this way but you still have some options: - add a Shell Script step and start an ssh session to the remote server; - install a standalone Jenkins on the remote server and configure it as a slave with the only job to start the server. I see that your question is not answered for a while and suppose that you already resolved the problem. In such a case it would be nice to update your publication :-) Best Regards, Monique -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
