.war files packaged as RPM for JBOSS/Tomcat - best practices?
Hi,
I'm planing to package WAR files as RPMs. Current deployment process just doesn't work for us and my idea of fixing it would be to create a new Custom Channel in RHN Satellite and publish my WAR files through that Channel. Currently (as we are trying to win some time) I'm managing some config files through Satellite so configs are not a big problem. We don't keep them in WAR for many reasons but that's different story.
Anyway, has anyone packaged WAR as RPMs? Do you do hot deployment or do you force JBOSS/Tomcat to restart? Is that After RPM installation or as a part of it? What's your SPEC file looks like? Can I please see it as an example? Do you check in your SPEC for JBOSS/Java/Oracle client or just install WAR? Any stories to tell? Any major problems?
Should I consider something else?
I can build RPMs no problem but I'd like to hear what's the best way of doing this with WAR files and JBOSS (some Tomcats are still runnig here but they will be phased out soon-ish so I'm not too worried about them).
unzip -v gives CRC info of each file in a zip(in my case .EAR) file.
# unzip -v my-application.ear
Archive: my-application.ear
Length Method Size Cmpr Date Time CRC-32 Name
-------- ------ ------- ---- ---------- ----- -------- ----
197981 Defl:N 183708 7%... (1 Reply)
dears
i am trying to install the autoconf-2.63-1.aix6.1.noarch.rpm but its shows the below error message .
P700_dev/svn/dependencies>rpm -i autoconf-2.63-1.aix6.1.noarch.rpm
error: failed dependencies:
m4 is needed by autoconf-2.63-1
P700_dev/svn/dependencies> (6 Replies)
Hi,
We have upgrade tomcat from 5.0.20 to 7.0.33 and made changes to server.xml file according to newer version.. how ever the upgrade went fine and now i am unable to deploy application remotely.. it is giving 403 access denied error.. we have seperate appbase directory mentioned in server.xml..... (0 Replies)
How to make RPM not write to RPM database if RPM fails to deploy?
IE I create an rpm spec file that contains the following
if
then
exit 1
fi
My rpm will fail at deployment, but if I do rpm -qa , I can see the rpm in the rpm db (3 Replies)
I was experimenting with ZoneMinder CCTV software on Suse 10.0. After some major configuartion problems, all caused by me I eventually decided on a complete clean re-install of Suse 10.
I downloaded the new opensuse 10.1 DVD with includes all 5 of the OpenSuse10.1 CDs and the Additional Addon... (2 Replies)
RHNREG_KS(8) Red Hat, Inc. RHNREG_KS(8)NAME
rhnreg_ks - A program for non interactively registering systems to RHN Satellite or Red Hat Network Classic.
SYNOPSIS
rhnreg_ks [options]
DESCRIPTION
rhnreg_ks is a utility for registering a system with the RHN Satellite or Red Hat Network Classic. It is designed to be used in a non-
interactive environment (a kickstart style install, for example). All the information can be specified on the command line or stdin.
OPTIONS --profilename
Specify the profile name that should be used as an identifier for the system in RHN Satellite, Red Hat Network Classic
--username
The username to register the system with under RHN Satellite or Red Hat Network Classic. This can be an existing RHN Satellite or
Red Hat Network Classic username, or a new username.
--password
The password associated with the username specified with the --username option. This is an unencrypted password.
--activationkey
Specify/use a serial number to associate with the system. This is optional, but activation keys can really simplify the registration
process. Learn more about activation keys in the online RHN documentation.
--contactinfo
This option has been deprecated. Please login to the server web user interface and update your contactinfo.
--nohardware
Do not probe or upload any hardware information.
--nopackages
Do not profile or upload any package information.
--novirtinfo
Do not profile or upload any virtualization information.
--norhnsd
Do not start rhnsd after completion.
--force
Register the system even if it has already been registered.
--version
Show the version of rhnreg_ks.
--proxy
Specify a HTTP proxy to use.
--proxyUser
Specify a username to use with an authenticated HTTP proxy.
--proxyPassword
Specify a password to use with an authenticated HTTP proxy.
--sslCACert
Specify a path to a SSL CA certificate to use.
--serverUrl
Specify a URL to as the server.
-h, --help
Show a help message and exit.
FILES
/etc/sysconfig/rhn/systemid
The digital server ID for this machine if the system has been registered onto RHN Satellite or Red Hat Network Classic. This file
does not exist otherwise.
/etc/sysconfig/rhn/up2date
The common configuration file used by RHN client programs.
EXAMPLES
Register a new system to Red Hat Network Classic:
rhnreg_ks --profilename "example_profile_name" --username "someexampleuser" --password "foobar"
Register a new system to Red Hat Network Classic with contact info:
rhnreg_ks --profilename "example_profile_name" --username "someexampleuser" --password "foobar" --contactinfo < contactinfo
where the file "contactinfo" contains data in the format:
first_name: Billy
last_name: Bob
company: SomeCompanyName
city: Springfield
fax: 555-5555
phone: 555-5555
SEE ALSO rhn_check(8), rhn_register(8), rhnsd(8), rhn-profile-sync(8), rhnplugin(8), up2date(5).
AUTHORS
See the AUTHORS file included with this software.
This manual page was written by Adrian Likins <alikins@redhat.com> and James Bowes <jbowes@redhat.com>
BUGS
Report bugs to <http://bugzilla.redhat.com>.
COPYRIGHT
Copyright (C) 1999-2011 Red Hat, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
Linux 2011 February 4 RHNREG_KS(8)