StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11147777
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-06-21T22:31:25.663
FavoriteCount
0
LastActivityDate
2012-06-21T22:31:25.663
LastEditDate
LastEditorUserId
0
OwnerUserId
1452562
ParentId
9032210
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
<p>I have packaged a WAR file and its companion config file as RPM. My SPEC file checks whether JBoss is running. If it is, the installation exits with an error message, requesting that JBoss be stopped before installation. </p> <p>In general, it is not a good idea to kill processes or force restart through RPMs. The person in charge of installation should have a separate procedure for doing this.</p> <h2>Other considerations:</h2> <h3>1. Does your organization have other installations on the same server?</h3> <p>If so, you might want to standardize on a path under which all installations on the server will go. (For example, /usr/local/bin/myorg/) It might also help to have a custom *nix user and group, for which file attributes are set for all installations on the server.</p> <h3>2. Do you want a relocatable RPM?</h3> <p>Is there ever a chance that you might want to change the default path for your installation? If so, a relocatable RPM will help. There are conditions where a relocatable RPM may not work, so check out <a href="http://www.rpm.org/max-rpm/s1-rpm-reloc-wrinkles.html">these things to consider</a> at <a href="http://www.rpm.org/max-rpm/ch-rpm-reloc.html">www.rpm.org</a>.</p> <h3>3. Do you want to back up an existing deployment when your RPM runs?</h3> <p>If so, you would need to write that code in your SPEC file.</p> <h2>Here is my complete SPEC file:</h2> <pre class="lang-sh prettyprint-override"><code>Summary: Summary for my Java project Name: Name for my Java project Version: 2.1.2 Release: 5 Requires: jboss >= 5.1 BuildArch: noarch Group: Internet / Applications Prefix: /usr/local/bin License: (C) Copyright my organization Vendor: my organization %description Description for my Java project %prep # Check if the WAR file has been created %install # Copy war file to buildroot's Jboss deployment directory # Copy config file to buildroot's Jboss config directory %files # Set file permissions and ownership %pre # Check if JBoss deployment path exists on the web server. # If not, exit with an error. # Check if JBoss config file path exists on the web server. # If not, exit with an error. # Check if custom user 'myuser' exists. If not, exit with an error. # Check if custom group 'mygroup' exists. If not, exit with an error # Check if JBOSS is running. If yes, exit with an error. # Take backup of existing deployment, if needed. %post # Perform post-installation steps, if needed. echo "Installation complete." </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PO.war files packaged as RPMs for JBOSS/Tomcat - best practices?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USnohup
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PO.war files packaged as RPMs for JBOSS/Tomcat - best practices?
  singulars
  PostTypePostTypeId
  PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.