# packages

pkgId: 90cbcc1a45a49f2f2180479de8505fbda25f6365dba9a9332b553fb30230dd0d
name: schedulix-base
arch: x86_64
version: 2.8
epoch: 0
release: 25.el7
summary: The schedulix base package installs all files that are used both by the server and the client
url: http://www.schedulix.org
rpm_license: AGPLv1
rpm_vendor: independIT Integrative Technologies GmbH
rpm_group: Applications/System
rpm_buildhost: ocelot
rpm_sourcerpm: schedulix-2.8-25.el7.src.rpm
rpm_packager: Ronald Jeninga <ronald.jeninga@schedulix.org>
location_href: schedulix-base-2.8-25.el7.x86_64.rpm
checksum_type: sha256
description:
  schedulix is a production proof open source enterprise job scheduling system.
  It consists of a central scheduling server and several agents called jobservers,
  as well as a Zope application server which provides the access to the system
  by a standard web browser.
  For operation schedulix requires an installed RDBMS and a suitable JDBC driver.
  The server package to install should reflect the RDBMS that is installed.

  On installation a user called 'schedulix' is created. The password is set to
  'schedulix' (same as user name) and should be changed after installation.
  If one of the server packages is installed, it will restart the required DBMS.
  This might cause side effects if some other software that uses the database
  system is running.

  The schedulix base package provides the files that are used by most other packages


pkgId: 7d55568c298cc6e4a5da2799682ee2580533479889156ef8cf06c5d9f5aedd50
name: schedulix-client
arch: x86_64
version: 2.8
epoch: 0
release: 25.el7
summary: The schedulix client package installs everything needed to setup a jobserver
url: http://www.schedulix.org
rpm_license: AGPLv1
rpm_vendor: independIT Integrative Technologies GmbH
rpm_group: Applications/System
rpm_buildhost: ocelot
rpm_sourcerpm: schedulix-2.8-25.el7.src.rpm
rpm_packager: Ronald Jeninga <ronald.jeninga@schedulix.org>
location_href: schedulix-client-2.8-25.el7.x86_64.rpm
checksum_type: sha256
description:
  schedulix is a production proof open source enterprise job scheduling system.
  It consists of a central scheduling server and several agents called jobservers,
  as well as a Zope application server which provides the access to the system
  by a standard web browser.
  For operation schedulix requires an installed RDBMS and a suitable JDBC driver.
  The server package to install should reflect the RDBMS that is installed.

  On installation a user called 'schedulix' is created. The password is set to
  'schedulix' (same as user name) and should be changed after installation.
  If one of the server packages is installed, it will restart the required DBMS.
  This might cause side effects if some other software that uses the database
  system is running.

  The schedulix client package installs everything needed to setup a jobserver


pkgId: 5bd2b46367b07d1432a73697b398133a8ba34f33430c0a2cb2baa52ccdfb691d
name: schedulix-server-mariadb
arch: x86_64
version: 2.8
epoch: 0
release: 25.el7
url: http://www.schedulix.org
rpm_license: AGPLv1
rpm_vendor: independIT Integrative Technologies GmbH
rpm_group: Applications/System
rpm_buildhost: ocelot
rpm_sourcerpm: schedulix-2.8-25.el7.src.rpm
rpm_packager: Ronald Jeninga <ronald.jeninga@schedulix.org>
location_href: schedulix-server-mariadb-2.8-25.el7.x86_64.rpm
checksum_type: sha256
summary:
  The schedulix server mariadb package installs a schedulix server based on an underlying MariaDB od MySQL RDBMS

description:
  schedulix is a production proof open source enterprise job scheduling system.
  It consists of a central scheduling server and several agents called jobservers,
  as well as a Zope application server which provides the access to the system
  by a standard web browser.
  For operation schedulix requires an installed RDBMS and a suitable JDBC driver.
  The server package to install should reflect the RDBMS that is installed.

  On installation a user called 'schedulix' is created. The password is set to
  'schedulix' (same as user name) and should be changed after installation.
  If one of the server packages is installed, it will restart the required DBMS.
  This might cause side effects if some other software that uses the database
  system is running.

  The schedulix server mariadb package installs a schedulix server based on an
  underlying MariaDB or MySQL RDBMS.
  A DBMS user 'schedulix' with password 'schedulix' will be created, which will
  create a database called 'schedulixdb'.

  It will load the convenience package, but does not load the examples.
  (use the schedulix-examples package to do so).


  Within the scheduling system there will be a user called 'SYSTEM' with password 'G0H0ME'
  installed. It is advisable to change the password as soon as possible.  This is done by
  changing the SysPasswd property in the /opt/schedulix/etc/server.conf file.
  Afterwards it will be a good idea to change the corresponding entry in the ~/.sdmshrc
  file too.

  Another issue can be firewall related. In order to be able to access the scheduling
  server you might need to add a rule to the iptables like:

  -A INPUT -p tcp -m state --state NEW -m tcp --dport 2506 -j ACCEPT

  This will make the port 2506 accessible from other computers.
  (We don't do this, because we don't want to automagically introduce holes into
  your security concept).


pkgId: 45dd4ebdc7cf797086ca1f37b52d14eccd8d109680121f9be666a638d60a70c7
name: schedulix-server-pg
arch: x86_64
version: 2.8
epoch: 0
release: 25.el7
summary: The schedulix server pg package installs a schedulix server based on an underlying Postgres RDBMS
url: http://www.schedulix.org
rpm_license: AGPLv1
rpm_vendor: independIT Integrative Technologies GmbH
rpm_group: Applications/System
rpm_buildhost: ocelot
rpm_sourcerpm: schedulix-2.8-25.el7.src.rpm
rpm_packager: Ronald Jeninga <ronald.jeninga@schedulix.org>
location_href: schedulix-server-pg-2.8-25.el7.x86_64.rpm
checksum_type: sha256
description:
  schedulix is a production proof open source enterprise job scheduling system.
  It consists of a central scheduling server and several agents called jobservers,
  as well as a Zope application server which provides the access to the system
  by a standard web browser.
  For operation schedulix requires an installed RDBMS and a suitable JDBC driver.
  The server package to install should reflect the RDBMS that is installed.

  On installation a user called 'schedulix' is created. The password is set to
  'schedulix' (same as user name) and should be changed after installation.
  If one of the server packages is installed, it will restart the required DBMS.
  This might cause side effects if some other software that uses the database
  system is running.

  The schedulix server pg package installs a schedulix server based on an underlying Postgres RDBMS.
  It loads the convenience package, but does not load the examples.


  Within the scheduling system there will be a user called 'SYSTEM' with password 'G0H0ME'
  installed. It is advisable to change the password as soon as possible.  This is done by
  changing the SysPasswd property in the /opt/schedulix/etc/server.conf file.
  Afterwards it will be a good idea to change the corresponding entry in the ~/.sdmshrc
  file too.

  Another issue can be firewall related. In order to be able to access the scheduling
  server you might need to add a rule to the iptables like:

  -A INPUT -p tcp -m state --state NEW -m tcp --dport 2506 -j ACCEPT

  This will make the port 2506 accessible from other computers.
  (We don't do this, because we don't want to automagically introduce holes into
  your security concept).

  The configuration file will be changed. Instead of the 'ident' method we need the 'md5' method
  in order to be able to connect by jdbc.


pkgId: f9223c5f13d2c65829fe5650bf68ca269565420584ca274fd9be8e2b79fa0e9f
name: schedulix-zope
arch: x86_64
version: 2.8
epoch: 0
release: 25.el7
url: http://www.schedulix.org
rpm_license: AGPLv1
rpm_vendor: independIT Integrative Technologies GmbH
rpm_group: Applications/System
rpm_buildhost: ocelot
rpm_sourcerpm: schedulix-2.8-25.el7.src.rpm
rpm_packager: Ronald Jeninga <ronald.jeninga@schedulix.org>
location_href: schedulix-zope-2.8-25.el7.x86_64.rpm
checksum_type: sha256
summary:
  The schedulix zope package installs the zope application server and configures it to access a locally installed server

description:
  schedulix is a production proof open source enterprise job scheduling system.
  It consists of a central scheduling server and several agents called jobservers,
  as well as a Zope application server which provides the access to the system
  by a standard web browser.
  For operation schedulix requires an installed RDBMS and a suitable JDBC driver.
  The server package to install should reflect the RDBMS that is installed.

  On installation a user called 'schedulix' is created. The password is set to
  'schedulix' (same as user name) and should be changed after installation.
  If one of the server packages is installed, it will restart the required DBMS.
  This might cause side effects if some other software that uses the database
  system is running.

  The schedulix zope package installs the zope application server and configures
  it to access a locally installed server.
  Note: installing this package requires a working Internet connection as the Zope
  software will be downloaded from http://download.zope.org.

  The initial user is 'sdmsadm' with a password that equals the user name.
  The Zope server will listen on port 8080.

  Due to the nature of the Zope software, there will be some messages like

  warning: no previously-included files matching '*.dll' found anywhere in distribution
  warning: no previously-included files matching '*.pyc' found anywhere in distribution
  warning: no previously-included files matching '*.pyo' found anywhere in distribution
  warning: no previously-included files matching '*.so' found anywhere in distribution

  which can be ignored. (Or, even better, tell me how to circumvent these).

  Another issue can be firewall related. In order to be able to access the Zope
  server you might need to add a rule to the iptables like:

  -A INPUT -p tcp -m state --state NEW -m tcp --dport 8080 -j ACCEPT

  This will make the port 8080 accessible from other computers.
  (We don't do this, because we don't want to automagically introduce holes into
  your security concept).


