Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    2
  • Subscribers subscribers
    6
  • Views views
    877
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to have script logic at beginning and end of an Application Process

Francesco Grossi

Hello everybody.

I wonder if somebody has already faced and solved my requirement..

In a given application deployment process I have 3 component to be deployed

The are destined to same application server (for a given enviroment).

Now when the deployment is carried out manually they put Application Server (AS) down , copy the 3 artifacts, and bring AS up, at the end of the manual process

So, at the end of the day, they shutdown and start the AS only once, no matter what is the number of components deployed.

Now we have been asked to do the same, with the Application Process,

stop AS

install cmp1

install cmp2

install cmp3

start AS

So far, I didn't find anything suitable to my need here (I mean: something like a shell step available in the Application Process, at start and end of the application Process)

Has anybody any suggestion ?

Thank you very much for helping!

Francesco

  • 0

    By thinking ove and over I thought of the following

    • break down any stop+deploy+start component process in three separated processes (each component has STOP, DEPLOY,STAR processes)
    • make stop and start process a smart one, do STOP/START when necessary: STOP: Application Server is UP? Then bring it down; START: Application Server is DOWN? then bring it UP; if the server state is already the one requested then do nothing.
    • build the Application process with all STOP processes, for every component, at the beginning, all deployment processes in the middle, and all START processes at the end of the Application Process.

    Thus, no matter what are/is the components versions to deploy, only one AS stop and one AS start should happen.

    In case somebody has a better solution , I would be happy to know.

    Thank you

    F.

  • 0 in reply to 

    Your suggestion seems best.  It will work if only one component is being updated, or if all three are being updated.  It is what I usually do when I am writing processes.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.