status
For our client, we are developing some libraries and applications that are "module" Let's go as a big application that has been distributed as an internal Java Web Start application. Customer maintains infrastructure that this application is running "Server Side" is made up of some web services based on Axis 2. Both parts are deployed as two different web applications in the form of a separate hatchat instance.
When we are releasing new versions of our artworks, we only produce necessary jar files (like ourapp-client.jar and ourapp-server .jar) and send them to our customer, Which in turn takes them to the appropriate places and - if necessary - restart the Tomcat server.
Goal
We are currently fortifying all our projects and in the future we want to release our "Release". The main goal is to automate the release and deployment process on our behalf and make it less error prone and more reliable and comfortable on the client side.
The main problem
The difficult part is that in our customer application to include their own self-developed module, the same Tommak web applications ("Server Side" and Axis2 for Expression App) Uses. So we can not use clear solutions and can only provide a new web app (war) that just gets deployed in the server. This is the reason that we are currently presenting single jar files which are kept in the right place by "hand".
What strategies can you generally use to distribute your products to your customers? Does anyone have any experience with such a situation (i.e. shared environment for third party and self-developed applications)?
The main goal is to automate the release and deployment process on our behalf and make it less error Be made prone and more reliable and comfortable on the client side.
Not sure you exactly means "release and deployment process" (in Maven, it is a remote repository about SCM functions, automation of artifacts and About deployment) If it is about deployment on production machines , then personally I do not think that it is actually a job for Maven (and we do not use Maven for it We do). There may be a look at dedicated solutions such as ,,,,,, etc.
Which strategies do you usually use to distribute your products to your customers? Does anybody have any experience with such a situation (i.e. runtime environment shared for third party and self-developed applications)?
We can distribute those things that we can control if a customer wants to include their bits in a given app, we will provide the necessary sub-bases , But the packaging would probably be his responsibility.
Related Questions
Comments
Post a Comment