2017 R1

Configuration of Fabasoft Folio Backend ServicesPermanent link for this heading

Disable KerberosPermanent link for this heading

If a non-kerberized setup should be used (e.g. working without a Microsoft Windows domain using LDAP), Kerberos should be disabled, as the according settings of the Fabasoft Folio Server Management Service will be inherited to all services created for new domains.

To disable Kerberos, perform the following steps:

  1. Logon as user fscsrv.
    # sufscsrv
  2. Stop all running Fabasoft Folio Service.
    > /opt/fabasoft/bin/fscmgmt stop all
  3. Open the file /var/opt/fabasoft/instances/COOManagement/env/CommandLine in an editor.
  4. In the file change the option –j to –k and save the file.
  5. Open the file /var/opt/fabasoft/instances/WebManagement/env/CommandLine in an editor.
    If the file does not exist so far, create it.
  6. In the file type the option –x and save it.
  7. Start all Fabasoft Folio Service.
    > /opt/fabasoft/bin/fscmgmt start all

Now Kerberos is disabled.

Additional ConfigurationPermanent link for this heading

Administrative UsersPermanent link for this heading

Only users that are local to the system (via Pluggable Authentication Module (PAM), see according documentation shipped with Red Hat Enterprise Linux) and that are members of the group fsc are permitted to access the Fabasoft Folio Server Management Service.

Microsoft Windows domain users that should be permitted to administer the Fabasoft Folio Service must be added as local users with membership to the group fsc. Their login name must match exactly on the Linux side (case sensitive). The domain name has to be omitted.

To add an administrative Microsoft Windows domain user, perform the following steps:

  1. Create a local user on the Linux computer having exactly the same login name as in the Microsoft Windows domain and add it to the group fsc.
    # useradd –g fsc –G fsc <username>
    Repeat this command for every Microsoft Windows domain user that should be permitted to administer Fabasoft Folio Service.
  2. To check that the user has been added to the group fsc, execute the following command:
    # cat /etc/group
    At the very bottom of the file locate the line beginning with fsc. The username of the Microsoft Windows domain user should have been added to this line. Multiple users are separated by a comma.

A local user has now been created and added to the group fsc.

Alternatively to these commands, the tool system-config-users on Red Hat Enterprise Linux provides a graphical user interface for adding or modifying user accounts. For more information consult the Red Hat Enterprise Linux manuals on user management.

KerberosPermanent link for this heading

After the installation of the RPM packages the Fabasoft Folio Service user (fscsrv) is available. The ownership and permissions of the file /etc/fabasoft/krb5.keytab, that has been created during preparation of Linux (see document “Fabasoft on Red Hat Linux – Preparation Guide”), need to be adjusted. Therefore perform the following steps:

  1. Set the ownership of the file /etc/fabasoft/krb5.keytab to fscsrv by executing the following command:
    # chown fscsrv:fsc /etc/fabasoft/krb5.keytab
  2. Set the permission for the file /etc/fabasoft/krb5.keytab as only the user fscsrv can read and write it by executing the following command:
    # chmod 0600 /etc/fabasoft/krb5.keytab

The ownership and permissions for the file /etc/fabasoft/krb5.keytab have been changed.

Database PropertiesPermanent link for this heading

The file /etc/fabasoft/base.conf contains settings for the database. Ensure that these settings match the Oracle Instant Client installation and the database server environment.

Note: Reasonable defaults are provided as a reference only. Except for the Oracle SID, these default settings will be sufficient in most cases. Please consult the documentation provided by Oracle for further information on the required database settings.

In chapter “Installation and Configuration of Oracle Instant Client” the /usr/lib64/oracle/<version>/network/admin directory has been created. The environment variables in the file /etc/fabasoft/base.conf have to match this directory.

To check and, if necessary, adjust the configuration, perform the following steps:

  1. Open the file /etc/fabasoft/base.conf in an editor (e.g. vim). Therefore execute the following command:
    # vim /etc/fabasoft/base.conf
  2. Check the following environment variables and adjust if necessary:
    ORACLE_HOME=/usr/lib64/oracle/<version>
    TNS_ADMIN=${ORACLE_HOME}/network/admin

    ORACLE_HOME=/usr/lib64/oracle/<version> has to match the version number of the Oracle Instant Client.
    Note: The value of the environment variable ORACLE_HOME in /etc/fabasoft/base.conf will be overwritten during the setup by the value defined before running the setup.
  3. After doing the modifications save the file and close the editor.

The environment variables have been checked.

Character set

Make sure that the NLS_LANG parameter used by the Oracle Instant Client is set to “AMERICAN_AMERICA.AL32UTF8”. More information about the NLS_LANG parameter can be found here: http://www.oracle.com/technetwork/products/globalization/nls-lang-099431.html

To specify a NLS_LANG value different from the default value, adapt it in the file /etc/fabasoft/base.conf. The value must be “AMERICAN_AMERICA.AL32UTF8”.

This setting corresponds to the database settings as described in the white paper “Fabasoft on Microsoft Windows and Linux - Oracle Database Preparation Guide”.

Default Database IndexesPermanent link for this heading

Each Fabasoft Folio COO Service creates default database indexes which are documented in the indexes.txt file located in /opt/fabasoft/share/db.

The index usage for columns of type VARCHAR or NVARCHAR depends on the property “Queries Are Case-Insensitive” (COOSYSTEM@1.1:domaincisqry) which is configurable in the current domain object. When changing the value of this property, the indexes should be changed accordingly.