• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Problems deploying app on Leopard server
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problems deploying app on Leopard server


  • Subject: Re: Problems deploying app on Leopard server
  • From: Art Isbell <email@hidden>
  • Date: Thu, 26 Jun 2008 11:25:57 -1000

On Jun 26, 2008, at 4:26 AM, Yves Selliez wrote:

I don’t know if that may help you, but what is sure is that you should modify your woapp with this set of permission :

chown -R appserver:appserveradm yourapp.woa
chmod -R 755 yourapp.woa

For me the group “appserverusr” (as written somewhere) did not work, and just made that the app just didn’t start at all.

You must be experiencing a different problem, because we deploy our WO apps with root owner and wheel group.  So changing owner to appserver and group to appserveradm for all app files is unnecessary.  Also, making every file in the woa bundle executable is just wrong, but may be solving the real problem (although using overkill to do so).

If you are using ant to build deployable apps with the build.xml file included with WOLips, you may be running into the problem that yourapp.woa/yourapp and yourapp.woa/Contents/MacOS/yourapp have 750 permissions but an owner that's not appserver.  In this situation, wotaskd, running as appserver, cannot execute your WO app shell scripts, so your WO apps won't start.

The manual fix:

sudo chmod 755 yourapp.woa/yourapp yourapp.woa/Contents/MacOS/yourapp

An automatic fix (thanks to Chuck Hill!) is to insert the following in build.xml just prior to the closing </target> tag in the "build.woapp" target:

<!-- Change file permissions from 750 to 755 for build product executables -->
        <chmod file="${dest.dir}${file.separator}${project.name}.woa${file.separator}${project.name}" perm="755"/>
        <chmod file="${dest.dir}${file.separator}${project.name}.woa${file.separator}Contents${file.separator}MacOS${file.separator}${project.name}" perm="755"/>

Making this build.xml change in all of your app projects will ensure that you won't forget to perform the manual fix after each deployment installation which plagued me.

Aloha,
Art

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: Problems deploying app on Leopard server (From: Yves Selliez <email@hidden>)

  • Prev by Date: Re: Maven
  • Next by Date: Re: Disable displaying contents of WOComponent
  • Previous by thread: Re: Problems deploying app on Leopard server
  • Next by thread: How to fill the WOLips binding validation rules?
  • Index(es):
    • Date
    • Thread