# packages

pkgId: 9a5cbf5aed7f87591e8de70a81acb3e1271f58d3a8b8f0cd4897b60a0b045cc9
name: schedulix-base
arch: ppc64le
version: 2.9
epoch: 0
release: 25.el8
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: ppccentos8.independit.de
rpm_sourcerpm: schedulix-2.9-25.el8.src.rpm
rpm_packager: Ronald Jeninga <ronald.jeninga@schedulix.org>
location_href: schedulix-base-2.9-25.el8.ppc64le.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: 4b8588737fb31d3568db3b1e239a624ff25f2a9b3fe712b42cb440e32ad5c079
name: schedulix-client
arch: ppc64le
version: 2.9
epoch: 0
release: 25.el8
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: ppccentos8.independit.de
rpm_sourcerpm: schedulix-2.9-25.el8.src.rpm
rpm_packager: Ronald Jeninga <ronald.jeninga@schedulix.org>
location_href: schedulix-client-2.9-25.el8.ppc64le.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: ff8d4ed1bd8386d12a5c0750d57639eea50032c8dd826bfa2a5bc81032269dd7
name: schedulix-server-mariadb
arch: ppc64le
version: 2.9
epoch: 0
release: 25.el8
url: http://www.schedulix.org
rpm_license: AGPLv1
rpm_vendor: independIT Integrative Technologies GmbH
rpm_group: Applications/System
rpm_buildhost: ppccentos8.independit.de
rpm_sourcerpm: schedulix-2.9-25.el8.src.rpm
rpm_packager: Ronald Jeninga <ronald.jeninga@schedulix.org>
location_href: schedulix-server-mariadb-2.9-25.el8.ppc64le.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: db60d5318b9770a6542ca5815c90e2420b38e636f20f8bebd25c8c71820da240
name: schedulix-server-pg
arch: ppc64le
version: 2.9
epoch: 0
release: 25.el8
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: ppccentos8.independit.de
rpm_sourcerpm: schedulix-2.9-25.el8.src.rpm
rpm_packager: Ronald Jeninga <ronald.jeninga@schedulix.org>
location_href: schedulix-server-pg-2.9-25.el8.ppc64le.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: 02c83de27afb18872821743fd874ea639d374276316bb632095d3966c8999139
name: schedulix-server-rmt
arch: ppc64le
version: 2.9
epoch: 0
release: 25.el8
url: http://www.schedulix.org
rpm_license: AGPLv1
rpm_vendor: independIT Integrative Technologies GmbH
rpm_group: Applications/System
rpm_buildhost: ppccentos8.independit.de
rpm_sourcerpm: schedulix-2.9-25.el8.src.rpm
rpm_packager: Ronald Jeninga <ronald.jeninga@schedulix.org>
location_href: schedulix-server-rmt-2.9-25.el8.ppc64le.rpm
checksum_type: sha256
summary:
  The schedulix server rmt package installs the schedulix server software but omits the creation of a database

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 rmt package installs a schedulix server without any initialisation or configuration of a database system.
  These steps have to be performed by the user himself. The installation guide describes all required steps.


  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: f909ef67cea2cfdcd7194ccae34a10c2cd3d8993b5b539ccf02afb294cc26c82
name: schedulix-zope
arch: ppc64le
version: 2.9
epoch: 0
release: 25.el8
url: http://www.schedulix.org
rpm_license: AGPLv1
rpm_vendor: independIT Integrative Technologies GmbH
rpm_group: Applications/System
rpm_buildhost: ppccentos8.independit.de
rpm_sourcerpm: schedulix-2.9-25.el8.src.rpm
rpm_packager: Ronald Jeninga <ronald.jeninga@schedulix.org>
location_href: schedulix-zope-2.9-25.el8.ppc64le.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).


pkgId: 4d1becdea3d4fa698d9d26943bfd7b7e7723c80deb9d9b5a5748eaf977e194a6
name: schedulix-zope4
arch: ppc64le
version: 2.9
epoch: 0
release: 25.el8
url: http://www.schedulix.org
rpm_license: AGPLv1
rpm_vendor: independIT Integrative Technologies GmbH
rpm_group: Applications/System
rpm_buildhost: ppccentos8.independit.de
rpm_sourcerpm: schedulix-2.9-25.el8.src.rpm
rpm_packager: Ronald Jeninga <ronald.jeninga@schedulix.org>
location_href: schedulix-zope4-2.9-25.el8.ppc64le.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 zope4 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 Zope4
  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).


