.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)
rpm2html(1) General Commands Manual rpm2html(1)NAME
rpm2html - make an html database from rpm repository
SYNOPSIS
rpm2html [-q][-v][-force][-lang langfile] config-file
DESCRIPTION
Rpm2html tries to solve 2 big problems one face when grabbing a RPM package from a mirror on the net and trying to install it:
- it gives more information than just the filename before installing the package.
- it tries to solve the dependency problem by analyzing all the Provides and Requires of the set of RPMs. It shows the cross references
by the way of hypertext links.
The second point will only be efficient if the actual number of indexed RPMs is important.
Each configuration file is handled independently as if it was a new invocation of rpm2html.
A configuration file represents a list of directories and a ditribution as a whole. All the references between packages listed in the
directories of a single config file are marked by hyperlinks in the resulting HTML files. Here is the process leading to the creation of
the HTML pages:
1/ The configuration file is parsed, it sets all the default values for rpm2html. Then all the directory entries are parsed and a list
of directories to scan is built.
2/ For each directory, the RPM are scanned, the HTML page describing the package is generated immediately.All ressources provided and
needed by the RPM file are stored in a list of ressources. A list of parsed RPMs is also constructed.
3/ Once all the RPM for this config file have been scanned all ressources are dumped in ressources files with links to the RPM providing
them (one could also add the RPM needing them but everything needs libc for example).
4/ The sorted lists of packages are generated by sorting the RPM list for various criteria and general front-end pages are generated
unsing the new list order.
5/ The main page is generated with links to the various front-end pages, statistics and description of the packages analyzed.
6/ All the lists are freed and global variables are reset.
rpm2html is now ready to handle the next configuration file.
CONFIGURATION
A configuration file a text file, lines beginning with semicolumns are comments. The first part is a global section defining some important
parameters of rpm2html. Parameters are defined with the syntax:
variable=value
Values shouln't be quoted and end up with the end of line
The folowing variables are supported:
maint The maintainer of the local mirror, NEEDED !
mail The E-mail of the maintainer, NEEDED !
dir The directory for for the HTML output, NEEDED !
url The URL for the HTML files on the WWW server
host The hostname for the server.
After these variables, one section should be filled for each directory on your system containing RPM files. It starts with the directory
filename between brackets:
[The name between brackets is the directory, NEEDED !]
The special directory name [localbase] extract information from the RPM base of installed software instead of listing a directory. It
allows to dump HTML pages for the installed RPM base on a machine.
All the variables defined below until the next directory or the end of file pertain to this directory. Here are the possible variables:
name A significant name for this mirror, NEEDED !
ftp The original FTP/HTTP url, NEEDED !
ftpsrc Where the associated sources are stored
color Background color for pages
trust Unused yet
url The local FTP/HTTP url.
It is possible to indicate other mirrors by adding some mirror=value lines withing the section. The first one will be considered the local
one.
EXAMPLE
Example of configuration files:
;
; Sample configuration file for rpm2html
;
maint=Joe
mail=joe@mydistrib.org
dir=/home/http/html/MyDistrib
url=/Mydistrib
tree=true
rdf=true
rdf_dir=/home/ftp/pub/mydistrib/RDF
[/MyDistrib/RPM/noarch]
name=Arch independent packages for MyDistrib
ftp=ftp://ftp.mydistrib.org/pub/mydistrib/noarch
subdir=noarch
[/MyDistrib/RPM/i386]
name=i386 packages for MyDistrib
ftp=ftp://ftp.mydistrib.org/pub/mydistrib/i386
ftpsrc=ftp://ftp.mydistrib.org/pub/mydistrib/srcs
color=#e0ffff
subdir=i386
mirror=ftp://ftp.mydistrib.org/pub/mydistrib/i386
mirror=ftp://ftp.elsewhere.org/pub/mydistrib/i386
[/MyDistrib/RPM/alpha]
name=Alpha packages for MyDistrib
ftp=ftp://ftp.mydistrib.org/pub/mydistrib/alpha
ftpsrc=ftp://ftp.mydistrib.org/pub/mydistrib/srcs
color=#ffe0ff
subdir=alpha
mirror=ftp://ftp.mydistrib.org/pub/mydistrib/alpha
mirror=ftp://ftp.elsewhere.org/pub/mydistrib/alpha
[/MyDistrib/RPM/sparc]
name=Sparc packages for MyDistrib
ftp=ftp://ftp.mydistrib.org/pub/mydistrib/sparc
ftpsrc=ftp://ftp.mydistrib.org/pub/mydistrib/srcs
color=#ffffe0
subdir=sparc
[/MyDistrib/RPM/ppc]
name=PPC packages for MyDistrib
ftp=ftp://ftp.mydistrib.org/pub/mydistrib/ppc
ftpsrc=ftp://ftp.mydistrib.org/pub/mydistrib/srcs
color=#e0ffe0
subdir=ppc
mirror=ftp://ftp.mydistrib.org/pub/mydistrib/ppc
mirror=ftp://ftp.pear.com/pub/mydistrib/ppc
OPERANDS
The following operands are supported:
files
List of configuration files
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
SEE ALSO rpm(1),
22 Feb 1998 rpm2html(1)