Public Events Registration

Owned by Arlen Johnson
Last updated: Jan 17, 2013

Bedework Public Events Registration System

Bedework 3.9 supports a basic public events registration system that allows authenticated users to register for events.  Users may view and modify their registrations, such as unregistering or changing the number of tickets they've requested.  When registration is full, users may choose to be placed on a waiting list. Users on waiting lists will automatically be moved up in the queue if space becomes available.

 

Administrators can specify how many users may register, how many tickets each registrant may request, and set the opening and closing dates of registration.  Administrators can view and modify a registration list and download CSV files of their registrations on-demand.

 

Enabling and Disabling Public Events Registration

Enabling Public Events Registration in Bedework 3.9

The public events registration system is enabled by default if you have installed Bedework 3.9 with the data available in the quickstart.

Disabling Public Events Registration

If you wish to disable the public events registration system remove the "Eventreg admin token" from the System Preferences in the administrative web client:

  • Log into the Bedework public events administrative client, e.g. http://localhost:8080/caladmin 
  • Go to the System tab and select "Manage System Preferences"
  • Remove the value of the "Eventreg admin token" field (set it to an empty value)
  • Click "Update" button to save your changes. 

Enabling Public Events Registration after upgrade to 3.9 from a previous release

If you have moved to Bedework 3.9 using data from a previous release, you are not likely to have the data required for event registration in your system yet.  Follow these steps to turn on the event registration system:  (Please note: the process outlined below is only set up for the default quickstart and postgresql configs at the moment.) 

  • Start up jboss and apacheDS

  • Log into the JMX-Console shipped with Bedework's JBoss, e.g. http://localhost:8080/jmx-console
    • Click "org.bedework" in the left menu, then "service=Eventreg" in the right menu
      • If no database exists:
        • Set “create” and “export” attributes to "True"
        • Click "Apply changes" button (at the bottom of the list of attribute values)
        • Find the "schema" operation in the lower list, and click the “Invoke” button to export schema and create database
        • You should see a successful result; click "Back to MBean" button to return to "service=Eventreg"
      • Point at needed systems:
      • Admin token:
        • If no admin token exists, click “generateAdminToken”
        • You should see a successful result; click "Back to MBean" button to return to "service=Eventreg"
        • You should see a string such as "c0e93685-93cd-4bee-bed2-9996b89be28c" in the EventRegAdminToken attribute value.
        •  Click "Apply changes" button
        • Copy the EventRegAdminToken value (for use in the next step)

  • Log into the Bedework public events administrative client, e.g. http://localhost:8080/caladmin
     
    • Go to the System tab and select "Manage System Preferences"
    • Paste the EventRegAdminToken value into the "Eventreg admin token" field
    • Click "Update" button to save your changes.

  • Test:
    • Add a new public event.  You should be able to select the checkbox "Users may register for this event", and make the event registerable.
    • Visit the event in public client -- you should be able to register for it.  


Enabling Public Events Registration in Bedework 3.8

The public events registration features have been backported into Bedework 3.8.  If you would like to install the system, perform the following steps: (Please note: the process outlined below is only set up for the default quickstart and postgresql configs at the moment.) 

  • Update the Bedework source, build the event registration system, and clean/build Bedework:  
    • ./bw -updateall
    • ./bw -quickstart -eventreg
    • ./bw -quickstart clean
    • ./bw -quickstart deploy
      (These commands should be performed from the root of the quickstart directory.  See also: building the Quickstart release.)

  • Fix up quickstart
    • mkdir quickstart-3.9/jboss-5.1.0.GA/server/default/data/bedework/eventreg/
    • unzip pubcalws-soap.zip into quickstart-3.9/jboss-5.1.0.GA.server/default/deploy/ROOT.war/wsdls/

  • Start up jboss and apacheDS

  • Log into the JMX-Console shipped with Bedework's JBoss, e.g. http://localhost:8080/jmx-console
    • Click "org.bedework" in the left menu, then "service=Eventreg" in the right menu
      • If no database exists:
        • Set “create” and “export” attributes to "True"
        • Click "Apply changes" button (at the bottom of the list of attribute values)
        • Find the "schema" operation in the lower list, and click the “Invoke” button to export schema and create database
        • You should see a successful result; click "Back to MBean" button to return to "service=Eventreg"
      • Point at needed systems:
      • Admin token:
        • If no admin token exists, click “generateAdminToken”
        • You should see a successful result; click "Back to MBean" button to return to "service=Eventreg"
        • You should see a string such as "c0e93685-93cd-4bee-bed2-9996b89be28c" in the EventRegAdminToken attribute value.
        •  Click "Apply changes" button
        • Copy the EventRegAdminToken value (for use in the next step)

  • Log into the Bedework public events administrative client, e.g. http://localhost:8080/caladmin
     
    • Go to the System tab and select "Manage System Preferences"
    • Paste the EventRegAdminToken value into the "Eventreg admin token" field
    • Click "Update" button to save your changes.

  • Test:
    • Add a new public event.  You should be able to select the checkbox "Users may register for this event", and make the event registerable.
    • Visit the event in public client -- you should be able to register for it.


Bedework Enterprise Calendar, version 3.9