Web Services

Web Services

Welcome to the home of Panda Web Services. This wiki should

Welcome to the home of Panda Web Services. This wiki should

• list existing tools and services
• explain them
• describe their installation and configuration

• list existing tools and services
• explain them
• describe their installation and configuration

Computer

Computer

The services (as of 2014/02) are running on a virtual machine in a GSI network segment.
The VM is equiped with:

The services (as of 2014/02) are running on a virtual machine in a GSI network segment.
The VM is equiped with:

IP address is 140.181.3.19
DNS is lxpndwww.gsi.de

IP address is 140.181.3.19
DNS is lxpndwww.gsi.de

The machine can not be accessed directly via ssh from outside the GSI network. You can use pandawww user to hop from the lxi's to lxpndww and use the account's "sudo" rights.
All services are installed in directory /srv/www (/srv is mountpoint for the lvm hd)

The machine can not be accessed directly via ssh from outside the GSI network. You can use pandawww user to hop from the lxi's to lxpndww and use the account's "sudo" rights.
All services are installed in directory /srv/www (/srv is mountpoint for the lvm hd)

Services

Services

Drupal

Drupal

URL(s):
https://lxpndwww.gsi.de
http://lxpndwww.gsi.de

URL(s):
https://lxpndwww.gsi.de
http://lxpndwww.gsi.de

Description

Description

The Drupal content management system (CMS) will replace the existing Panda website.
To launch the service officially, the DNS entry for www-panda.gsi just needs to point to the new IP (cname entry).
. The CMS provides the service for the Panda member list, the Panda document system (incl. review process support) and the website to server content.

The Drupal content management system (CMS) will replace the existing handmade Panda website.
To launch the service the DNS entry for www-panda.gsi just needs to point to the new IP.

Features (2014/05/15):

- LDAP login
- User profile with LDAP sync and avatar
- Personalisation (group based) / specific access permissions
- User importer/exporter and simple statistics
- Panda module to auto-generate PubCom conform publication titles
- Context specific input forms for publications
- Specific views for pubs incl. sorting and filtering
- Notification emails
- Publishing landing page
- Autocreate forum topic when creating a publication
- Autogenerate Panda author list tex/pdf
- Event calendar list
- Linking event <-> talk

Known ToDos:
- Incomplete Panda member list in LDAP
- Define "new Panda member" process
- Content: To be created or migrated/imported from old site
- Design: Contacts, logo,... and a lot more
- Login: Password forgotten. There is a help->bug in ldap module?
- Change notification email addresses from udo->groups
- Check author list generation + setup cron
- Set up voting for Panda elections

Installation + configuration

Installation + configuration

Installation directory is /srv/www/drupal7/drupal-7.xx $BR$ In PandaApacheConfig the Docroot is "/var/www/current", which is a symlink to /srv/www/drupal7/drupal-7.xx.
So you can install new drupal releases next to each other and switch the symlink when ready.
In order to do that, the "site" subfolder within the drupal-7.xx directories need to be a symlink to "../sites".
In /srv/www/drupal7/sites you can find ALL site specific configs incl. the files directories with uploaded content. So for backups it is sufficient to keep that folder and a db dump.

Installation directory is /srv/www/drupal7/drupal-7.xx $BR$ In PandaApacheConfig the Docroot is "/var/www/current", which is a symlink to /srv/www/drupal7/drupal-7.xx.
So you can install new drupal releases next to each other and switch the symlink when ready.
In order to do that, the "site" subfolder within the drupal-7.xx directories need to be a symlink to "../sites".
In /srv/www/drupal7/sites you can find ALL site specific configs incl. the files directories with uploaded content. So for backups it is sufficient to keep that folder and a db dump.

Alfresco

Alfresco

EDM-System

EDM-System

Description

Description

Installation + configuration

Installation + configuration

service alfresco start/stop/restart

service alfresco start/stop/restart

global config:
/srv/www/alfresco-4.2.e/tomcat/shared/classes/alfresco-global.properties

global config:
/srv/www/alfresco-4.2.e/tomcat/shared/classes/alfresco-global.properties

logging:
/srv/www/alfresco-4.2.e/tomcat/logs
Also via sysmlink /var/log/alfresco

logging:
/srv/www/alfresco-4.2.e/tomcat/logs
Also via sysmlink /var/log/alfresco

ldap configuration:
/srv/www/alfresco-4.2.e/tomcat/shared/classes/alfresco/extension/subsystems/Authentication/ldap/ldap1 log4j config change to get debug output for the authentication subsystem: %br% In file /srv/www/alfresco-4.2.e/tomcat/webapps/alfresco/WEB-INF/classes/log4j.properties add:
#LDAP Server Debug FLAGS
log4j.logger.org.alfresco.repo.importer.ImporterJob=debug
log4j.logger.org.alfresco.repo.importer.ExportSourceImporter=debug
log4j.logger.org.alfresco.repo.security.authentication.ldap=debug

ldap configuration:
/srv/www/alfresco-4.2.e/tomcat/shared/classes/alfresco/extension/subsystems/Authentication/ldap/ldap1 log4j config change to get debug output for the authentication subsystem: %br% In file /srv/www/alfresco-4.2.e/tomcat/webapps/alfresco/WEB-INF/classes/log4j.properties add:
#LDAP Server Debug FLAGS
log4j.logger.org.alfresco.repo.importer.ImporterJob=debug
log4j.logger.org.alfresco.repo.importer.ExportSourceImporter=debug
log4j.logger.org.alfresco.repo.security.authentication.ldap=debug

Seafile

Seafile

Description

Description

Installation + configuration

Installation + configuration

Future plans

Future plans

GIT repository

GIT repository

Redmine

Redmine

Site Tools of the WebServices Web

Site Tools of the WebServices Web

Notes:

Notes: