Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


webobjects (3) Versions 0.0.2

Installs and configures a WebObjects service (wotaskd and JavaMonitor) and Apache adaptor

cookbook 'webobjects', '= 0.0.2', :supermarket
cookbook 'webobjects', '= 0.0.2'
knife supermarket install webobjects
knife supermarket download webobjects
Quality -%


Installs and configures a WebObjects service (wotaskd and JavaMonitor) and Apache adaptor.



Only tested on Ubuntu.


  • apache2
  • build-essential
  • java


  • node["java"]["install_flavor"] - Flavor of JVM you would like installed (sun or openjdk), default openjdk.

  • node[:app_environment] - The chef environment. Default: "_default"

  • node[:webobjects][:wonder_source_remote_url] - Where to downlowd the wonder source. Default: ""

  • node[:webobjects][:wonder_source_local_package] - What to call wonder source once downloaded. Default: "Wonder-Source.tar.gz"

  • node[:webobjects][:wonder_source_dir_Utilities] - Where to find the wonder utilities dir. Default: "Utilities"

  • node[:webobjects][:wonder_source_dir_Adaptors] - Where to find the wonder adaptors dir. Default: "Utilities/Adaptors"

  • node[:webobjects][:webobjects_apache_conf_remote_url] - Where to get a generic webobjects.conf file. Default: ""

  • node[:webobjects][:webobjects_apache_conf_local_name] - What to call the webobjects.conf file. Default: "webobjects.conf"

  • node[:webobjects][:webobjects_user] - What user to run WebObjects as. Default: "appserver"

  • node[:webobjects][:webobjects_group] - What group to run WebObjects as. Default: "appserveradm"

  • node[:webobjects][:webobjects_site_url] - The publicly facing URL for WebObjects (used for setting the adaptor within JavaMonitor). Default: "http://localhost"

  • node[:webobjects][:webobjects_resources_url] - The URL path for resources. Default: "/WebObjects"

  • node[:webobjects][:webobjects_apps_url] - The URL path for WebObjects Applications. Default: "/cgi-bin/WebObjects"

  • node[:webobjects][:webobjects_wotaskd_host] - The host for wotaskd. Default: "localhost"

  • node[:webobjects][:webobjects_wotaskd_port] - The port for wotaskd. Default: "1085"

  • node[:webobjects][:webobjects_wotaskd_interval] - The wotaskd polling interval. Default: "10"

  • node[:webobjects][:webobjects_wotaskd_receive_timeout] - The wotaskd receive timeout. Default: "5000"

  • node[:webobjects][:webobjects_wotaskd_startup_wait] - The number of seconds to wait for wotaskd to startup before adding hosts or applications. Default: "10"

  • node[:webobjects][:webobjects_JavaMonitor_host] - The host for JavaMonitor. Default: ""

  • node[:webobjects][:webobjects_JavaMonitor_port] - The port for JavaMonitor. Default: "56789"

  • node[:webobjects][:webobjects_JavaMonitor_receive_timeout] - The JavaMonitor receive timeout. Default: "10000"

  • node[:webobjects][:webobjects_WOLocalRootDirectory_dir] - Where to install WebObjects frameworks and runtimes. Default: "/opt"

  • node[:webobjects][:webobjects_WOApplications_dir] - Where to install yoru WebObjects applications. Default: "/opt/WOApplications"

  • node[:webobjects][:webobjects_WOWebServerResources_dir] - Where to install web server resources. Default: "/opt/WOWebServerResources"

  • node[:webobjects][:webobjects_WODeployment_dir] - Where to install the wotaskd and JavaMonitor. Default: "/opt/WODeployment"

  • node[:webobjects][:webobjects_WOLog_dir] - Where to create log files for wotaskd, JavaMonitor, and individual apps. Default: "/var/log/webobjects"

  • node[:webobjects][:webobjects_JavaMonitor_remote_url] - Where to download JavaMonitor. Default: ""

  • node[:webobjects][:webobjects_JavaMonitor_local_package] - What to call JavaMonitor once downloaded. Default: "JavaMonitor.tgz"

  • node[:webobjects][:webobjects_JavaMonitor_app] - Name of the JavaMonitor app. Default: "JavaMonitor.woa"

  • node[:webobjects][:webobjects_JavaMonitor_password] - What JavaMonitor password to set. Default: "wonderful"

  • node[:webobjects][:webobjects_wotaskd_remote_url] - Where to download wotaskd. Default: ""

  • node[:webobjects][:webobjects_wotaskd_local_package] - What to call wotaskd once downloaded. Default: "wotaskd.tgz"

  • node[:webobjects][:webobjects_wotaskd_app] - Name of the wotaskd app. Default: "wotaskd.woa"

  • node[:webobjects][:file_limit] - The system-wide file limit. Default: "200000"

  • node[:webobjects][:security_limit_hard] - The users specific hard file limit. Default: "200000"

  • node[:webobjects][:security_limit_soft] - The users specific sot file limit. Default: "200000"



Does nothing.


Downloads the wonder adaptor source, builds, and installs the mod_WebObjects module.


Assumes you already have a ant build script and simply runs the default target.


Copies the built deployments to the local applications and resources directories, useful for standalone deployments.


Tells the JavaMonitor about the apps location and adds and instance of it.


Clones the application source from git, configured via data bags.


Creates an Apache config file from a template.


Changes the number of open files allowed.


Creates a few directories and config files needed fro building WebObjects apps from source


Downloads and installs wotaskd and JavaMonitor, installs and starts a webobjects service,
and sets JavaMonitor up with a host, site config, and password.



An example webobjects_application_server role which installs WebObjects 5.4 application server (wotaskd and JavaMonitor):

    name "webobjects_application_server"
    description "A WebObjects application server"
    run_list "recipe[java]", "recipe[webobjects::modify_system_file_limits]", "recipe[webobjects::setup_deployment_environment]"

An example webobjects_http_server role which installs an Apache 2 web server and builds a WebObjects adaptor:

    name "webobjects_http_server"
    description "A server which handles HTTP requests and pass them via wonder adapter to a WebObjects application server"
    run_list "recipe[apache2]", "recipe[apache2::mod_ssl]", "recipe[webobjects::build_apache_adaptor]", "recipe[webobjects::modify_apache_config]"

An example webobjects_compile_server role which installs resources to compile WebObjects applications from source:

    name "webobjects_compile_server"
    description "A server which compiles WebObjects apps"
    run_list "role[webobjects_application_server]", "recipe[webobjects::setup_compile_environment]"

Note that you must provide the Apple, Wonder, woproject.jar, and other third-party frameworks.

Data Bags

See this post
on the use of Opscode's application deployment cookbooks and the use of data bags.

While this cookbook doesn't directly use any of the deployment recipes in that cookbook it follows
the same precedence there.

There some additional data bag attributes specific to this cookbook:


    "app_environment": "_default"

sets the general chef environment being used.


    "deploy_name": "MyApp"

designates that you're deploying a WebObjects app of MyApp.woa.


  "application_properties": {
    "production": {
        "application_url": "",
        "smtp_host": "",
    "staging": {
        "application_url": "",
        "smtp_host": "localhost",

is how you might manipulate a system properties file from a chef template before deploying.

Application configuration settings

"webobjects_receive_timeout": "240",
"webobjects_connect_timeout": "240",
"webobjects_additional_arguments": "-Xmx512m -Xms128m"

are settings applied when adding the application to JavaMonitor.


"webobjects_num_instances": 2

is how you could specify that two instances of your application should be created.


  • The webobjects service seems to terminate at the end of a knife ec2 bootstrapping process for some reason so you'll have to ssh to the instance and run sudo service webobjects start to get it running again.
  • At the time of this writing there seems to be an issue getting chef-client running on CentOS 5.x images unrelated to this cookbook.
  • This cookbook was adapted from the work done at ObjectStyle Wiki.

License and Authors

Author:: Ray Gauss

Copyright:: 2011, RightsPro.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

No quality metric results found