Skip to Content
author's profile photo Former Member
Former Member

Hybris deployment best practices

Hi,

I just read the pages about the ZIP deployment of Hybris

  1. Create Hybris ZIP -> https://wiki.hybris.com/display/release5/Create+Deployment+ZIP+Files

  2. Install Hybris ZIP -> https://wiki.hybris.com/display/release5/Install+Deployment+ZIP+Files

But I have still some questions.

  1. What is the best way to do a deployment of your code from Accept to Production, we like to do this with one push on the button. So we should create some scripts that will do the trick. First of all we should do a 'Create Hybris ZIP', than we should copy the file to the other server with xcopy and than we should do the 'Install Hybris ZIP', my question is, is this the best way to do this or is there a better solution.

  2. I think I know the answer on this question already, but I still will ask it. I'm using Hybris 5.2.0.1 and we still need to stop the Hybris instance to deploy our new code, is it possible to do this without downtime or is this something that is still on the roadmap for version 5.x?

Thanks for your answers

note: we are using for both environments a Windows server and Hybris 5.2.0.1

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jul 23, 2014 at 06:55 PM

    Regarding 1)

    yes, you could write scripts to do so, or you use a deployment software like Jenkins

    http://jenkins-ci.org/

    Find some notes on Jenkins and alternative deployment methods here:

    https://wiki.hybris.com/display/pe/Introduction+to+Setting+Up+Continuous+Integration

    Regarding 2)

    You can use JRebel to hot deploy java classes and spring configuration (but not configuration), but that's intended for development environment only, to increase personal productivity by avoiding time consuming restarts.

    But for production environments this seems to be too dangerous to me as you would never run through the normal build & initialization process. A hot deployment can never mirror everything that happens on reinit of the platform - the state of the Java VM, of any web sessions, etc. have an unpredictable status on a hot deployment. That's acceptable for a development system as you can always guess that this is the cause of strange behavior of the system, but it will kill the reliability of a production system.

    So the effort to make such thing really reliable would be tremendous and not worth it - as it's really easy to flip your setup node by node in a 2+ cluster node setup without downtime.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      I don't see why it would hard or very uncomfortable to run the build?

      It was worth going with this copy procedure if it saved you a difficult or long other procedure, but to risk a bunch of problems just for the few minutes of a build is not a real advantage in my view.

  • author's profile photo Former Member
    Former Member
    Posted on Jul 24, 2014 at 01:31 PM

    Special case: migration

    If you would like to upgrade hybris commerce to newer version (migration), there is highly recommended to turn off the previous system, e.g. to perform backup of DB. Afterwards you need to run System Update to bring the data layer on the newest state.

    See Migration Guide as example: https://wiki.hybris.com/display/release5/Migration+from+5.1.1+to+5.2.0

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.