Best practice: transfer content to your own wiki and fill it out Please transfer the contents of this page and fill them out in your own wiki. Please note, however, that you are only allowed to do so if you are a //SEIBERT/MEDIA customer.

Contents of this page:

Basic data

Basic data describe the server configuration on which Confluence / JIRA or Foswiki run. You can find out more about appropriate hardware equipment for Confluence here and consult a JIRA orientation guide here.

  •  Operating system:
    • Version:
    • Architecture/edition (32 bit, 64 bit):
    • Language:

  •  Virtualization (VMWare, XenSource, Citrix XenServer):

  •  Main memory (RAM):

  •  Host name:
  •  Domain name:
  •  IP address:
  •  Net mask:
  •  Default gateway:
  •  1st DNS:
  •  2nd DNS (optional):
  •  3rd DNS (optional):
  •  DNS suffix (identical to domain name, if applicable):

  •  1st NTP (optional):
  •  2nd NTP (optional):

  •  HTTP proxy (optional):
  •  HTTP proxy access data (optional):

  •  FTP proxy (optional):
  •  FTP proxy access data (optional):
  • 1. NTP (optional):
  • 2. NTP (optional):
  • HTTP-Proxy (optional):
  • HTTP-Proxy Zugangsdaten (optional):
  • FTP-Proxy (optional):
  • FTP-Proxy Zugangsdaten (optional):

  • Size of the initial hard disk capacity:
    •  Size of system partition (optional):
    •  Size of database partition (optional):
    •  Size of web data partition (optional):

Or partitioning scheme as follows:

  • User names of administrator accounts: please submit via fax, phone or encrypted e-mail

  • Passwords of administrator accounts: please submit via fax, phone or encrypted e-mail

  • “Trusted networks” from which remote/SSH access is permitted (optional):
  • Any additional firewall restrictions (optional):

Second network interface (optional) 

A second network interface can be used for a separate back-up network. You can describe the configuration of this interface here.

  • IP address:
  • Net mask:
  • Default gateway:

E-Mail configuration: system

Confluence, JIRA and Foswiki include the option to send and even receive e-mails e.g. notification purposes (e.g. JIRA for creating processes/tasks).

  • Host name of the internal e-mail relay (Smarthost):
  • IP address of the internal e-mail relay (Smarthost):
  • Sending e-mails via the internal e-mail relay possible without authentication (yes/no):

  • Hostname des internen Mail-Relays (Smarthost):
  • IP-Adresse des internen Mail-Relays (Smarthost):
  • Mailversand über den internen Mailrelay ohne Authentifizierung möglich (ja/nein):
    • If not, user name:
    • Password for authentication: please submit via fax, phone or encrypted e-mailE-mail domain with which e-mails are to be sent via the local SMTP server:
  • Administrator e-mail address to which system notifications are sent:

LDAP / Active Directory connection (optional) 

An LDAP/Active Directory connection enables users to login with their usual user name/password identification e.g. their Windows log-in.

  • Host name of the LDAP server (not domain):
  • Type and version of LDAP server:
  • LDAP version:
  • Encryption to LDAP server possible via TSL or SSL (yes/no):
  • LDAP Base DN:
  • LDAP Bind User (complete DN):
  • Password for Bind User: please submit via fax, phone or encrypted e-mail

  • LDAP object class of user (person/user):
  • LDAP attribute for user (uid/cn):
  • LDAP attribute for given name (givenname):
  • LDAP attribute for surname (sn):
  • LDAP attribute for displayed/complete name (displayname):
  • LDAP attribute for e-mail address (mail):

  • LDAP object class of groups (group) (only required if groups need to be displayed):
  • LDAP attribute for group (cn) (only required if groups need to be displayed):
  • LDAP attribute for group member (member) (only required if groups need to be displayed):
  • LDAP path that contains the groups recursively:
    • Are the groups organized again in additional containers (yes/no):
  • LDAP path that recursively contains users allowed to authenticate themselves in the web application:
    • Are the users organized again in additional containers:
    • or LDAP groups with users allowed to authenticate themselves in the web application:
    • or specific LDAP attribute that unlocks users for authentication:

SSL certificate (optional)

For an encrypted (HTTPS) connection to Confluence/JIRA/Foswiki, an SSL certificate must be configured for the desired domains/web addresses in the web server. This certificate can be created by an internal certification body (if applicable) or be ordered at, for example. If you want //SEIBERT/MEDIA to process your certificate, please fill out the information below.

  • Process via internal certification body or apply for an external certificate (internal/external):

  • 2-letter country code (DE):
  • State:
  • City or town:
  • Company name:
  • Department:
  • FQDN of the web application:
  • E-mail address:

Siehe diese Seite auf Deutsch

  • No labels

This content was last updated on 11/07/2014.

This content hasn't been updated in a while. That doesn't have to be a problem. Some of our pages live for years without becoming obsolete. Please click this link if you want us to update this page. Old content can be incorrect, misleading or outdated. Please get in contact with us via a form on this page, our live chat or via email with if you are in doubt, have a question, suggestion, or want changes from us.