Mark -'s Library tagged confluence →  View Popular

nstalling Confluence Standalone As A Service





From your Windows-based server running Confluence 2.2 standalone or later:





1. Open a command prompt in the <CONFLUENCE-INSTALL>/bin directory
   
   
   
   
2. Confirm that the JAVA_HOME variable is set to the JDK base directory with the command
   
   
   

   echo %JAVA_HOME%

   
   
   
   

   Note that any directory in the path with spaces (eg. C:\Program Files must be converted to its eight-character equivalent (eg. C:\Progra~1)
   
   

3. Install the service with default settings with the command
   
   
   

   service.bat install Confluence

   
   
4. In addition, to have the service start automatically when the server starts, run
   
   
   

   tomcat5 //US//Confluence --Startup auto
   

   
   
5. If you have a less than a 512 meg of memory, skip this step. For users with large Confluence installs, you can increase the maximum memory Confluence can use (default will already be 256MB). For example, you can set the maximum memory to 512 megs using
   
   
   

   tomcat5 //US//Confluence --JvmMx 512
   

   
   
6. If you do not have any JVM parameters you pass to your freestanding version of Confluence, you can skip this step. If you do, add them to the service using
   
   
   

   tomcat5 //US//Confluence ++JvmOptions="-Djust.an.example=True"
   

   
   
7. For any further configuration, check out the Tomcat Windows Service How-To guide
   

Example

Expandable Text

Expandable Panel

Description/Features

This plug-in contains macros for creating 'permanent templates' and editable forms.

It provides many macros which allow data to be entered into a form. It does so by allowing the editing of specified sections on a page when viewing the page, if the current user has 'edit' permissions to the page being viewed.

There is a public library of scaffolds people have used in real life availabile here.

For more information, visit this plugin's homepage

Description/Features








Provides a simple template system for creating dynamic templates based on zones.





Essentially, you define a page that is the zone template. Each zone template contains one or more zones. Zones are basically just named placeholders for data defined pages which are instances of the template.





Once you have defined a template, you can start creating pages which implement that templace using a zone template instance. The instance provides zone data for each zone in the template.





If you need to go back and change the overall layout of the instance pages, you simply change the template, as one might expect.





Zone templates differ from scaffolds in a few ways:




• Template and instance data are stored in the content of a page. So you can use Confluence to manage the data versioning.
• Zones only provide a very simple mechanism for managing a dynamic template, scaffolds provide a much richer set of tags to support more dynamic data sets.





Version 1.2 has only been tested on Confluence 2.2.9. The utilities-plugin is no longer needed.

Users can create editable forms to enter page content by creating a template. For example, a software development project may have a template for use-cases; or a systems administration space, a template for defining what information is being kept about each server.





In Confluence, there are two types of templates:



• Global Templates : These are defined by site administrators through the Administration Console and are available in every space.
• Space Templates: These are defined by space administrators in the space administration screens, and are only available in the space in which they are defined.





Global templates can only be created by site administrators, and space templates by space administrators.





Templates are written in regular Confluence markup, using special markup to define form fields that need to be filled in.





Here is an example:

Confluence allows you to integrate your own stylesheets within the theme plugin so you can have greater control over the appearance of your site. Confluence's main stylesheet is a useful reference when overriding styles and can be found in the Confluence install directory under ...confluence/WEB-INF/classes/styles/site-css.vm.

Step One: Defining the stylesheet in the atlassian-plugin.xml

To make a stylesheet available to a decorator, you will need to reference it as a resource from within the central configuration file - atlassian-plugin.xml.

Here is an example where a stylesheet is being used to define the 'leftnavigation' theme:

<layout key="main" name="Main Decorator" class="com.atlassian.confluence.themes.VelocityDecorator"
overrides="/decorators/main.vmd">
<resource type="velocity" name="decorator"
location="templates/leftnavigation/main.vmd"/>
<resource type="stylesheet" name="leftnav.css"
location="templates/leftnavigation/leftnav-css.vm">
</resource>
</layout>